On Dec 14, 2004, at 11:30 PM, Michael wrote:

>> sd0: fabricating a geometry
>> sd0: no NetBSD disk label
>> umass0: BBB reset failed, TIMEOUT
>> umass0: BBB bulk-in clear stall failed, TIMEOUT
>> umass0: BBB bulk-out clear stall failed, TIMEOUT
>> umass0: BBB reset failed, TIMEOUT
>>
>> # usbdevs
>> addr 1: OHCI root hub, Opti
>> addr 3: product 0x0110, Samsung Electronics
>> addr 2: product 0x0095, Microsoft
> Argh, and the interrupt isn't even shared. This leaves three 
> possibilities - the USB stick is weird, you didn't get the interrupt 
> fixes or there's something wrong with them - yours would be the first 
> known G3 which has problems. Do other USB devices still work? If all 
> USB stuff is dead it's probably the interrupt code, if others continue 
> working it's almost certainly the drive and umass needs another quirks 
> entry.

I'll try a different one and try to get X set up so I can see if the 
mouse is doing anything interesting.

>> firewire code aside (we have experimental code enabled by default in
>> generic?), things are not quite right. I could do at least 60 kB/sec
>> with bm when it would cooperate under 2.0, now it's less than 10
>> kB/sec.
> When did you pull the kernel source from cvs? Or - which version does 
> src/sys.macppc/macppc/extintr.c show? It should be 1.45 from 12/09 or 
> newer, if you have an older one please update and try again. If not 
> then we're in trouble - well, Allen and I are. It's never been tested 
> with a Heathrow.

$NetBSD: extintr.c,v 1.45 2004/12/09 01:43:37 briggs Exp $

I compiled from sources dated 12/13/2004. I'm running unpatched so if I 
should be applying other patches let me know.