On Thu, 31 Oct 2002, Dirk van den Brink Jr wrote: > Recompiled my kernel (2.4.20-pre6) with USB Debugging and usb-storage > debugging turned on. While most of this is greek to me, I'm sure some of it > may be of use to people here on the devel list.
With usb-storage debugging turned on, your kernel log should have lots and lots of messages generated by the usb-storage module. But for some reason, there's only one. > Now, let's insert the usb-storage module. > > ---CLIP--- > Oct 31 00:40:05 superfly kernel: Initializing USB Mass Storage driver... > Oct 31 00:40:05 superfly kernel: usb.c: registered new driver usb-storage > Oct 31 00:40:05 superfly kernel: scsi3 : SCSI emulation for USB Mass Storage > devices > Oct 31 00:40:05 superfly kernel: Vendor: Mega Model: DV > Rev: 1.00 > Oct 31 00:40:05 superfly kernel: Type: Direct-Access > ANSI SCSI revision: 02 > Oct 31 00:40:05 superfly kernel: Attached scsi removable disk sdb at scsi3, > channel 0, id 0, lun 0 > Oct 31 00:40:05 superfly kernel: SCSI device sdb: 16384 512-byte hdwr sectors > (8 MB) > Oct 31 00:40:05 superfly kernel: sdb: test WP failed, assume Write Enabled > Oct 31 00:40:05 superfly kernel: > /dev/scsi/host3/bus0/target0/lun0:<7>usb-storage: queuecommand() called That's the only message you get from usb-storage? Once you start doing things to the device (like trying to format it), the log should be full of all sorts of messages. Without them, there's no easy way to tell what really happened. Alan Stern ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
