Subject: hang during mouse detect?
To: None <port-mac68k@netbsd.org>
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
List: port-mac68k
Date: 07/18/2005 01:13:57
So, I recently got a PowerBook 165.  Of course, I went to put NetBSD on
it.

For the first stab, I used the same installation I used on my IIci.  I
copied it to an external HFS drive and moved that to the PowerBook (for
some reason, SCSI disk mode on the PowerBook doesn't seem to work
reliably when connected to the IIci, though it seemed to be fine when
connected to a SPARCstation-10).

I got the drive partitioned, with a 60M HFS partition and the rest
split up into root and swap.  I used the installer - the same one I
used on my IIci - to make filesystems, unpack the sets, and make
devices.

Then I told it to reboot and it went catatonic on me.

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@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
kbd0 at adb0 addr 2: PowerBook keyboard
ms0 at adb0 addr 3: 

Yes, this is a rather old kernel.  I used it both because it was handy
and because this machine has only 12 megs, and it seems that nowadays
16 megs is considered "tiny" on i386 - a CISCer machine than the 68k -
so I don't expect -current to even crawl on it, much less run.

Have I done something stupid here, or is the 165 not really supported
in 1.4.2 and I'll need something newer, or does this mean my hardware
is broken (it seems to work fine in System 7), or what?  I'd rather not
go through the contortions involved in getting a newer distribution
onto this disk unless there's a reasonable chance it'll work better.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B