NetBSD on Apple's m68k based Macintosh machines (NetBSD/mac68k)

Hauke Fath | 20 Jul 2005 20:54

Re: hang during mouse detect?

At 1:13 Uhr -0400 18.7.2005, der Mouse wrote:
>So, I recently got a PowerBook 165.  Of course, I went to put NetBSD on
>it.

[...]

>So I told the booter to use serial console, and...it still goes
>catatonic, though slightly more informatively:
>
>System RAM: 12582912 bytes in 3072 pages.
>     Low = 0x0, high = 0xc00000
>Checking for Internal Video get_mapping(): PB/IIvx (0x60?00000).  False start.
>[ preserving 363353 bytes of netbsd a.out symbol table ]
>Copyright (c) 1996, 1997, 1998, 1999, 2000
>    The NetBSD Foundation, Inc.  All rights reserved.
>Copyright (c) 1982, 1986, 1989, 1991, 1993
>    The Regents of the University of California.  All rights reserved.
>
>NetBSD 1.4.2 (GENERIC) #4: Sat Mar 18 01:16:20 CST 2000
>    fredb <at> corwin.home:/s/src/sys/arch/mac68k/compile/GENERIC
>Apple Macintosh PowerBook 165  (68030)
>cpu: delay factor 355
>real mem = 12582912
>avail mem = 8388608
>using 179 buffers containing 733184 bytes of memory
>mrg: kernel has no ROM vectors for this machine!
>mainbus0 (root)
>obio0 at mainbus0
>adb0 at obio0 (direct, PowerBook): 2 targets
>aed0 at adb0 addr 0: ADB Event device

(Continue reading)

headers

der Mouse | 21 Jul 2005 02:04

Re: hang during mouse detect?

[PowerBook hang during boot of 1.4.2 kernel at...]
>> kbd0 at adb0 addr 2: PowerBook keyboard
>> ms0 at adb0 addr 3:
> Did you touch the mouse (trackball) during boot?

No - or at least not until multiple seconds into the hang.

> But, to repeat myself: Keep your hands off the mouse during boot.

I'll try again, making certain to not touch anything once the booter
starts its countdown.

> Downloading and booting a 1.6 GENERIC kernel should show you.

I was hoping to avoid that.  But I now have tried a 1.4T GENERIC
kernel, and it uses different device names but hangs at the analogous
point:

fpu0 at mainbus0 (emulator)
adb0 (direct, PowerBook): 2 targets
aed0 at adb0 addr 0: ADB Event device
akbd0 at adb0 addr 2: PowerBook keyboard
wskbd0 at akbd0
ams0 at adb0 addr 3: 

so I guess I'll shelve it until I collect the round tuits to try a 1.6
kernel and see what it does.

I do find it slightly suspicious that adb0 says "2 targets" and then
tries to find devices at three different "addr"s, but that could be

(Continue reading)