> OK - we have a problem, but we don't know which :( > Add USB_DEBUG to your kernel and you should get more data out of this > case. I'll send output tomorrow or later tonight. > > If I boot with the device attached, 'usbdevs -v' pauses for quite > > a long time and gives the correct probe line: > > > > [brane-dead] ~ # usbdevs -v > > Controller /dev/usb0: > > addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x 0000), rev 1.00 > > port 1 powered > > port 2 addr 2: full speed, power 500 mA, config 1, Flash Reader(0xa600), D ATAFAB(0x07c4), rev 1.19 > > Interesting. > > > However, the device is still unusable. > > Mmm - but usbdevs gets it's data by directly talking to the device, so > everytime you invoke usbdevs the device is involved. > What excactly is _unuseable_? Just did enough stuff to get these, but now the machine has locked up, so I can do no more before I get home. 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 umass0: BBB bulk-in clear stall failed, TIMEOUT umass0: BBB bulk-out clear stall failed, TIMEOUT umass0: BBB reset failed, TIMEOUT Ian -- Ian FreislichReceived on Thu Jun 17 2004 - 11:50:38 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:57 UTC