Hi Matthew, others! FWIW: My experiences with the usb-storage driver from the usb-2.3.50-1-for-2.2.14 backport + usbbp-empty-stor.patch: When connecting the Toshiba PDR-M4[1] digital still camera to my Dell Latitude notebook running 2.2.14 + above patches, I experienced a double oops, followed by a system unwilling to boot. I tried to download the pictures off the camera, which worked fine the first time[2]. When trying to download the second set of pictures one day later, I manually did Q> # modprobe usb-storage Q> # modprobe usb-uhci which resulted in Q> # lsmod Q> usb-storage (unused) Q> usb-uhci (unused) Q> usbcore [usb-storage usb-uhci] which I think of as normal. However, trying to mount the device: Q> # mount -tmsdos /dev/sda1 /toshiba Q> /dev/sda1 is not a valid block device and in the syslog there appeared a message telling me the the partition table could not be read. Multiple re-plugging did not help, as did switching the camera on and off. I next tried re-loading the modules, but this time I did the following (without any special intention) Q> # modprobe usb-uhci Q> Segmentation fault which left usb-uhci uninitialized: Q> # lsmod Q> usb-uhci (uninitialized) Q> usbcore [usb-uhci] # this dependency was probably missing... usb-uhci could not be removed, so I tried to reboot when I got a double oops from the usb stack and the system now complains: Q> Unable to open an initial console. Q> Kernel Panic: no init found. Try passing init= on the command line. on every try to boot it. Thus all error messages above are from memory and the oopsen are lost. I am aware of the fact that the current usb-backport is very old and so is the usb-storage driver in it, but it strikes be that it worked two times without any problems, other than the ones mentioned in footnote [2], but suddenly resited to read the partition table[3]. Maybe you know what went wrong or even fixed it in a later version, but I wanted you to know in case you can make anything of it. I will try to reproduce this with serial logging enabled once I get the notebook up'n'running again if you don't tell me "Stop, you don't need to. It was a well-known error and it went away in kernel version 2.3.99preX". [1] this device presents itself as a mass storage device with the pictures being in JPEG format. [2] although it was slow (speeds ranging from 41 to 54 K/s, where the win driver gets ten times this) and read-only (where the win driver allows read-write) [3] which may well be a symptom and not the real error occurring. Marc -- Marc Mutz <[EMAIL PROTECTED]> http://marc.mutz.com/Encryption-HOWTO/ University of Bielefeld, Dep. of Mathematics / Dep. of Physics PGP-keyID's: 0xd46ce9ab (RSA), 0x7ae55b9e (DSS/DH) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
