I grabbed the 5/9 sys tarball and built a GENERIC kernel and have had
mixed success with it on my Blue & White G3 (350MHz), but figured I'd report
what I've found.

	First off, the kernel booted, and detected my wd0 disk.  I've since installed 
NetBSD on a partition and can use it as the root device.  I'm not sure how or 
if I can point Open Firmware at this partition to boot without a bootp server, 
if anybody has any suggestions I'd love to hear it.

	One problem my machine has is that if the root device is not specifically 
mentioned it will fail at the root device prompt.  Provided I boot with a 
kernel that's hard-coded to bm0 or wd0 I can boot and use the system just 
fine.  If I use a default GENERIC kernel I'm stuck at the root device prompt 
with a shimmering cursor.  So something's still wrong here.

	Also, my mouse has also stopped working with the newer kernels.  With older 
kernels (I can try some to see what versions worked if anybody cares) NetBSD 
properly detected my keyboard and mouse (MacAlly iKey and Logitech M-BA47).  
Now if the mouse is plugged in to the keyboard it reports an error on boot, 
yet when plugged into the second port on the back of the machine it is 
detected.  Running usbd I see messages like "uhub1: device problem, disabling 
port 2".  If I then connect the mouse to the back of the machine, I get more 
syslog messages than normal, and they acctually indicate the mouse being 
detected at the keyboard, then removed, then detected at the root hub.  Dunno 
if that helps anybody.

	When the mouse is connected and properly detected, I've noticed that in X I 
have use of the 3 buttons (pushing the scroll wheel counts as the middle 
button).  However, if I roll the wheel, the X server immediately dies.  The 
fourth button doesn't do anything, but it doesn't crash the server either..  =)

	Additionally if I boot with an ADB keyboard/mouse connected the machine no 
longer crashes.  The system comes up with only the ADB keyboard and mouse 
functional, I do not know if this is the expected behavior.  But at least it 
doesn't crash anymore..  =)

	So thank you very much to all the folks who have worked to get this working.  
Seems like there are still a bunch of small issues to work out, but it's great 
to see the machine not only booting but having all devices in a rather 
functional state.

	Thanks again.


                                                          Will Ferry

-----------------
woferry@iname.com