I cannot use my Toshiba USB HD with Fedora 7.
I am quoting here the relevant part of 'demsg': << usb 4-1: new high speed USB device using ehci_hcd and address 4 usb 4-1: configuration #1 chosen from 1 choice scsi3 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete scsi scan: INQUIRY result too short (5), using 36 scsi 3:0:0:0: CD-ROM Toshiba USB 2.0 CD-ROM 1.15 PQ: 0 ANSI: 0 usb 4-1: reset high speed USB device using ehci_hcd and address 4 usb 4-1: reset high speed USB device using ehci_hcd and address 4 usb 4-1: reset high speed USB device using ehci_hcd and address 4 usb 4-1: reset high speed USB device using ehci_hcd and address 4 usb 4-1: reset high speed USB device using ehci_hcd and address 4 sr2: scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray sr 3:0:0:0: Attached scsi CD-ROM sr2 sr 3:0:0:0: Attached scsi generic sg4 type 5
This is the output of 'lsusb': << Bus 004 Device 004: ID 0930:0b06 Toshiba Corp. Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 004: ID 0461:4d15 Primax Electronics, Ltd Bus 002 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000
Both the Primax thing, that is, the mouse and the HD are getting detected. But, no device file is generated. And obviously, the automount of USB HD-s is not working at all.
I'm taking a stab at it. You said HD but I'm guessing a CDROM?
I guess you don't see an icon on your desktop where you can mount or access files in the CD.
When all else fails, try
mkdir /mnt/sr2; mount /dev/sr2 /mnt/sr2; ls /mnt/sr2
HTH
On Nov 8, 2007 10:16 AM, dasd dasd.here@gmail.com wrote:
I cannot use my Toshiba USB HD with Fedora 7.
I am quoting here the relevant part of 'demsg': << usb 4-1: new high speed USB device using ehci_hcd and address 4 usb 4-1: configuration #1 chosen from 1 choice scsi3 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete scsi scan: INQUIRY result too short (5), using 36 scsi 3:0:0:0: CD-ROM Toshiba USB 2.0 CD-ROM 1.15 PQ: 0 ANSI: 0 usb 4-1: reset high speed USB device using ehci_hcd and address 4 usb 4-1: reset high speed USB device using ehci_hcd and address 4 usb 4-1: reset high speed USB device using ehci_hcd and address 4 usb 4-1: reset high speed USB device using ehci_hcd and address 4 usb 4-1: reset high speed USB device using ehci_hcd and address 4 sr2: scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray sr 3:0:0:0: Attached scsi CD-ROM sr2 sr 3:0:0:0: Attached scsi generic sg4 type 5
This is the output of 'lsusb': << Bus 004 Device 004: ID 0930:0b06 Toshiba Corp. Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 004: ID 0461:4d15 Primax Electronics, Ltd Bus 002 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000
Both the Primax thing, that is, the mouse and the HD are getting detected. But, no device file is generated. And obviously, the automount of USB HD-s is not working at all.
-- das http://ddts.randomink.org/ http://ddts.randomink.org/blog/
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
On Thu, 8 Nov 2007 10:29:05 -0500 "Kip Thomas" kip.thomas@gmail.com wrote:
I'm taking a stab at it. You said HD but I'm guessing a CDROM?
I guess you don't see an icon on your desktop where you can mount or access files in the CD.
Thank you pal, for replying so soon. But, in the mean time, my problem got autosolved. Just by chance, I plugged it to a differnt USB slot, and it got recognized, mounted and all. Sorry that I bothered you with it.
On Thu, 8 Nov 2007 10:29:05 -0500 "Kip Thomas" kip.thomas@gmail.com wrote:
I'm taking a stab at it. You said HD but I'm guessing a CDROM?
Oh, I forgot to mention it, it is both a CDROM and a HD (I don't know what it means). The CDROM is some kind of proprietary password protection thing. After it was purchased I actually had to go to a MSW-XP box and make that password protection thing off before the first time I used it some eight months back. But it is very fast. 'hdparm -tT' gave this:
<< [root@mamdo ~]# hdparm -tT /dev/sdc1
/dev/sdc1: Timing cached reads: 462 MB in 2.01 seconds = 230.06 MB/sec Timing buffered disk reads: 68 MB in 3.04 seconds = 22.35 MB/sec [root@mamdo ~]#
dasd wrote:
On Thu, 8 Nov 2007 10:29:05 -0500 "Kip Thomas" kip.thomas@gmail.com wrote:
I'm taking a stab at it. You said HD but I'm guessing a CDROM?
I guess you don't see an icon on your desktop where you can mount or access files in the CD.
Thank you pal, for replying so soon. But, in the mean time, my problem got autosolved. Just by chance, I plugged it to a differnt USB slot, and it got recognized, mounted and all. Sorry that I bothered you with it.
It sounds like ether the first socket didn't have enough power. With USB hard drives that are powered off the USB bus is that you have to let the drive spin up before things work correctly. I have two laptop drive enclosures that are powered this way, and I have to plug in the power-only plug and let the drive spin up, before plugging in the data plug. I also have a couple of 3-1/2" drive enclosures that have their own power supply. Most of them requiring turning on the drive power supply before plugging in the USB plug. I do have one that works fine plugging in the USB plug before turning on the power. But that one does not show up in lsusb before turning it on. I gues sit depends on how the electronics are powered, and if the firmware handles the drive powering up after the USB interface.
Mikkel
No, I am sorry, I was too fast to react. Somehow, once, by chance it got recognized. Now, I cannot once again get it. And dmesg is giving some kernel message:
<< usb 3-2: new full speed USB device using uhci_hcd and address 2 usb 3-2: not running at top speed; connect to a high speed hub usb 3-2: configuration #1 chosen from 1 choice scsi3 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 2 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete scsi scan: INQUIRY result too short (5), using 36 scsi 3:0:0:0: CD-ROM Toshiba USB 2.0 CD-ROM 1.15 PQ: 0 ANSI: 0 usb 3-2: reset full speed USB device using uhci_hcd and address 2 usb 3-2: USB disconnect, address 2 scsi 3:0:0:1: scsi: Device offlined - not ready after error recovery BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: c04f4f05 *pde = 25fa6067 *pte = 00000000 Oops: 0000 [#1] SMP Modules linked in: autofs4 hidp rfcomm l2cap bluetooth sunrpc nf_conntrack_ftp nf_conntrack_netbios_ns nf_conntrack_ipv4 ipt_REJECT iptable_filter ip_tables nf_conntrack_ipv6 xt_state nf_conntrack nfnetlink xt_tcpudp ip6t_REJECT ip6table_filter ip6_tables x_tables ipv6 dm_mirror dm_multipath dm_mod video output sbs battery ac snd_usb_audio snd_usb_lib snd_hwdep snd_via82xx gameport snd_ac97_codec ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_mpu401_uart via_ircc snd_rawmidi irda snd_seq_device 8139cp parport_pc crc_ccitt snd button parport usb_storage i2c_viapro soundcore i2c_core 8139too mii sr_mod cdrom sg ata_generic pata_via libata sd_mod scsi_mod ext3 jbd mbcache ehci_hcd ohci_hcd uhci_hcd CPU: 0 EIP: 0060:[<c04f4f05>] Not tainted VLI EFLAGS: 00010246 (2.6.23.1-21.fc7 #1) EIP is at strlen+0x8/0x11 eax: 00000000 ebx: 0000000b ecx: ffffffff edx: ee0695e4 esi: f0bc8706 edi: 00000000 ebp: ee0695e4 esp: efc23e54 ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0068 Process khubd (pid: 136, ti=efc23000 task=c16ecc20 task.ti=efc23000) Stack: ee0695e4 c0565bc2 ee0695dc f0bd196c f0bd1900 c0565cef 00000000 ee0695dc dd46bc00 00000296 dd46b400 c0565d81 ee069400 f0bbe6b4 ee069400 dd46bc00 f0bbc19b dd46bc30 dd46bc00 f0bb73aa dd46bebc 00000001 dd46bc00 f0c2f719 Call Trace: [<c0565bc2>] make_class_name+0x15/0x4f [<c0565cef>] class_device_del+0x97/0x121 [<c0565d81>] class_device_unregister+0x8/0x10 [<f0bbe6b4>] __scsi_remove_device+0x1d/0x60 [scsi_mod] [<f0bbc19b>] scsi_forget_host+0x2d/0x4a [scsi_mod] [<f0bb73aa>] scsi_remove_host+0x65/0xd7 [scsi_mod] [<f0c2f719>] quiesce_and_remove_host+0xb1/0xc0 [usb_storage] [<f0c2f7ec>] storage_disconnect+0xe/0x16 [usb_storage] [<c057d46f>] usb_unbind_interface+0x44/0x94 [<c0565423>] __device_release_driver+0x6e/0x8b [<c05657f6>] device_release_driver+0x32/0x48 [<c0564dee>] bus_remove_device+0x6a/0x7a [<c05635d9>] device_del+0x1ef/0x260 [<c057ae31>] usb_disable_device+0x5c/0xbb [<c057758f>] usb_disconnect+0x97/0x137 [<c0577caa>] hub_thread+0x3af/0xaa2 [<c043d3c5>] autoremove_wake_function+0x0/0x35 [<c05778fb>] hub_thread+0x0/0xaa2 [<c043d2fe>] kthread+0x38/0x5e [<c043d2c6>] kthread+0x0/0x5e [<c0405dbb>] kernel_thread_helper+0x7/0x10 ======================= Code: f0 48 5e c3 56 89 d1 89 c6 83 ec 04 31 d2 89 c8 88 c4 ac 38 e0 75 03 8d 56 ff 84 c0 75 f4 5e 89 d0 5e c3 57 83 c9 ff 89 c7 31 c0 <f2> ae f7 d1 49 5f 89 c8 c3 57 89 c7 89 d0 31 d2 85 c9 74 0c f2 EIP: [<c04f4f05>] strlen+0x8/0x11 SS:ESP 0068:efc23e54
And 'lsusb' has hanged the terminal. The command prompt has not returned for around ten mintues.
It is the same USB slot where it got discovered and mounted.
On Thu, 08 Nov 2007 22:35:13 +0530 dasd dasd.here@gmail.com wrote:
No, I am sorry, I was too fast to react. Somehow, once, by chance it got recognized. Now, I cannot once again get it. And dmesg is giving some kernel message:
It is quite possibly a power issue. If your unit is powered directly from the USB port then it may not be getting enough.
Mikkel L. Ellertson wrote:
dasd wrote:
On Thu, 8 Nov 2007 10:29:05 -0500 "Kip Thomas" kip.thomas@gmail.com wrote:
I'm taking a stab at it. You said HD but I'm guessing a CDROM?
I guess you don't see an icon on your desktop where you can mount or access files in the CD.
Thank you pal, for replying so soon. But, in the mean time, my problem got autosolved. Just by chance, I plugged it to a differnt USB slot, and it got recognized, mounted and all. Sorry that I bothered you with it.
It sounds like ether the first socket didn't have enough power. With USB hard drives that are powered off the USB bus is that you have to let the drive spin up before things work correctly. I have two
A USB CD-ROM would have to be self-powered; I'm yet to see even a 3.6" drive enclosure that's not.
laptop drive enclosures that are powered this way, and I have to plug in the power-only plug and let the drive spin up, before plugging in the data plug. I also have a couple of 3-1/2" drive enclosures that have their own power supply. Most of them requiring turning on the drive power supply before plugging in the USB plug. I do have one that works fine plugging in the USB plug before turning on the power. But that one does not show up in lsusb before turning it on. I gues sit depends on how the electronics are powered, and if the firmware handles the drive powering up after the USB interface.
The order of turning on power should not matter. After a power failure,them drive is almost certain to be up first. OTOH I'd not wish to remove the USB cable to power off/power on a drive (I may want it connected over time, but not necessarily with power).
dasd wrote:
scsi 3:0:0:1: scsi: Device offlined - not ready after error recovery BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000
There should be no NULL pointers. Read that word, BUG.
Looks like a good case for visiting bugzilla.
John Summerfield wrote:
Mikkel L. Ellertson wrote:
laptop drive enclosures that are powered this way, and I have to plug in the power-only plug and let the drive spin up, before plugging in the data plug. I also have a couple of 3-1/2" drive enclosures that have their own power supply. Most of them requiring turning on the drive power supply before plugging in the USB plug. I do have one that works fine plugging in the USB plug before turning on the power. But that one does not show up in lsusb before turning it on. I gues sit depends on how the electronics are powered, and if the firmware handles the drive powering up after the USB interface.
The order of turning on power should not matter. After a power failure,them drive is almost certain to be up first. OTOH I'd not wish to remove the USB cable to power off/power on a drive (I may want it connected over time, but not necessarily with power).
If the enclosure is properly designed, it should not make any difference. But many of the enclosures are not properly designed. The take shortcuts that save on production costs and/or have other design problems that results in the USB electronics not initializing properly if you power things up in the wrong order. The strange thing is that there does not seem to be a correlation between the price and the performance. I have run into cheap, no-name enclosures that perform well, and more expensive drives that have problems.
This is basically a case where theory says one thing, and experience shows something else. This is why some people run into problem when powering up the system with a USB drive connected, or the drive does not work when resuming from suspend. (You can get around it on some desktops by changing a jumper so that the USB socket is still powered during suspend.)
Mikkel