Subject: Re: Q650/Slotman problem
To: Conrad Rehill <conrad@rehill.org>
From: Tom Jernigan <jernigantc@ornl.gov>
List: port-mac68k
Date: 06/05/2000 13:42:17
I don't know what distribution you're using, but with 1.4.2, I had to
use a serial console to get the slotman kernel working with my IIci
and Futura SX video card. See the msg below from Paul Goyette about
wscons. I've just got the april snapshot working after following the
advice in the archive about MAKEDEV, ttye0, and ttyE0 (and much
fumbling around). I never could get the may snapshot to work. It
always seemed to die at the ethernet card. I thought I had saved the
error msg, but I can't find it now.
Tom
>Date: Wed, 31 May 2000 17:20:55 -0700 (PDT)
>From: Paul Goyette <paul@whooppee.com>
>Subject: Re: Success with serial console
>To: Tom Jernigan <jernigantc@ornl.gov>
>Reply-to: paul@whooppee.com
>X-Secure: Never
>Original-recipient: rfc822;jernigantc@fed.ornl.gov
>
>Good news indeed, because I had no idea what was going on there!
>
>One thing to note it that the current SLOTMAN kernels are built with
>wscons support. These kernels are more -current than related to any
>particular 1.4.x.
>
>You'd probably be better off looking for a fairly current netbsd/mac68k
>snapshot than with the 1.4.1 or 1.4.2 stuff. wscons will be in future
>(ie, 1.5 and up) kernels by default.
>
>On Wed, 31 May 2000, Tom Jernigan wrote:
>
>> Paul,
>> I went back to 1.4.2 to try to get kde running. I then dug up a
>> serial cable to connect to another mac tried netbsd.SLOTMAN_HWD_SBC
>> again. This time it was successful. It booted all the way to this
>> point:
>> ...
>> >setting tty flags
>> >starting network
>> >hostname: emac-ornl02.gat.com
>> >configuring network interfaces: ae0ae0: starting DAD for
>> >fe80:0001::0060:8cff:fe16:a445
>> >ae0: DAD complete for fe80:0001::0060:8cff:fe16:a445 - no duplicates found
>> >.
>> >add net default: gateway 192.73.62.1
>> >adding interface aliases:
>> >starting system logger
>> >checking for core dump...
>> >May 31 13:25:26 emac-ornl02 /netbsd: ae0: NIC memory corrupt -
>> >invalid packet length 65280
>> >May 31 13:25:27 emac-ornl02 /netbsd: ae0: starting DAD for
>> >fe80:0001::0060:8cff:fe16:a445
>> >May 31 13:25:27 emac-ornl02 /netbsd: ae0: DAD complete for
>> >fe80:0001::0060:8cff:fe16:a445 - no duplicates found
>> >savecore: no core dump
>> >starting rpc daemons: portmap.
>> >starting nfs daemons:.
>> >creating runtime link editor directory cache.
>> >checking quotas: done.
>> >building databases...
>> >clearing /tmp
>> >updating motd.
>> >standard daemons: update cron.
>> >starting network daemons: inetd.
>> >starting local daemons:.
>> >Wed May 31 13:25:39 PDT 2000
>> >May 31 13:25:44 emac-ornl02 getty[175]: /dev/ttye0: Device not configured
>> >
>> >
>>
>> Then nothing else from the console. I then telneted in from my other
>> mac and it let me log in. I then started kde and the monitor on the
>> IIci came up with the kde desktop in color.
>>
>> So the problem must be in the tty setup instead of the ethernet. I
>> don't know enough about netbsd yet to know what getty is or how the
>> devices get configured, but I've noticed recent emails to the 68k
>> port list server about other tty problems particularly with ttye0 vs
>> ttyE0.
>> Tom
>> Tom Jernigan, jernigantc@ornl.gov
>> presently at General Atomics in San Diego, Bldg 13/551
>> Phone (858) 455-4122, FAX (858)455-4515 NOTE NEW AREA CODES
>>
>
>-----------------------------------------------------------------------
>| Paul Goyette | PGP DSS Key fingerprint: | E-mail addresses: |
>| Network Engineer| BCD7 5301 9513 58A6 0DBC | paul@whooppee.com |
>| & kernel hacker | 91EB ADB1 A280 3B79 9221 | pgoyette@juniper.net |
>-----------------------------------------------------------------------
Tom Jernigan, jernigantc@ornl.gov
presently at General Atomics in San Diego, Bldg 13/551
Phone (858) 455-4122, FAX (858)455-4515 NOTE NEW AREA CODES