On Sun, 1 Jun 2003 [EMAIL PROTECTED] wrote: > Hello, > I have problems connecting the Pontis SP600 mp3-player (with inserted 256MB > Compact > Flash Card) with my PC through USB. The SP600 caused kernel panic with > 2.4.19 and 2.4.20 on Debian testing.
As you've seen, 2.4.21-recent is more reliable. > With kernel 2.4.21-rc1 the SP600 caused no kernel panic but other errors. > Now with 2.4.21-rc1 I can use the device but I get ugly messages, > especially "Device not ready" and "test WP failed". Therefore I'm not sure > if the device works stable and the data transmission is secure. > Please take a look at the messages below! They are only regarding USB. Note > that I have also harddisk problems with 2.4.21-rc1 but I think this is not > important for USB. "Test WP failed" might not be bad. "Device not ready" is bad, though. > 2B) booting finished. I connect the device: > -------------------------------------------- > May 7 16:25:37 debian kernel: hub.c: new USB device 00:04.2-1, assigned > address > 3 > May 7 16:25:42 debian kernel: usb_control/bulk_msg: timeout > May 7 16:25:42 debian kernel: usb-uhci.c: interrupt, status 2, frame# 297 > May 7 16:25:42 debian kernel: scsi1 : SCSI emulation for USB Mass Storage > devices > May 7 16:25:42 debian kernel: Vendor: PONTIS - Model: SP600 - USB DISK > Rev: > 0001 > May 7 16:25:42 debian kernel: Type: Direct-Access > ANSI > SCSI revision: 02 > May 7 16:25:42 debian kernel: Attached scsi removable disk sdb at scsi1, > channel 0, id 0, lun 0 > May 7 16:25:42 debian kernel: SCSI device sdb: 503808 512-byte hdwr sectors > (258 MB) > May 7 16:25:42 debian kernel: sdb: test WP failed, assume Write Enabled > May 7 16:25:42 debian kernel: sdb:<7>usb-storage: queuecommand() called > May 7 16:25:42 debian kernel: sdb1 > > 2C) Now I mount the device: > ---------------------------- > May 7 16:26:09 debian kernel: Device not ready. Make sure there is a disc > in the drive. > This message repeats a few times. I see that you've got usb-storage debugging enabled, but your syslog.conf file is apparently set to ignore debugging messages. If you can change it so that the debugging messages are included with the kernel log, it will be easier to diagnose the source of your problem. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
