Jump to content
Corsair Community

2GB Flash Voyager sometimes mounts as USB 1.1


jharr

Recommended Posts

I have a Flash Voyager 2 GB USB 2.0 stick. When I plug it into my IBM Thinkpad T40, it usually mounts as USB 1.1. This has also happened on my desktop (Asus A7V600 motherboard) and on a few other computers. However, sometimes it does appear as a 2.0 device. It even mounts differently on my Asus's front panel and back panel ports (I checked, they're all 2.0-capable). System log errors say that the device is refusing its address:

 

Sep 26 15:11:18 oobleck kernel: usb 1-8: new high speed USB device using ehci_hcd and address 119

Sep 26 15:11:19 oobleck kernel: usb 1-8: device not accepting address 119, error -71

Sep 26 15:11:19 oobleck kernel: usb 1-8: new high speed USB device using ehci_hcd and address 120

Sep 26 15:11:19 oobleck kernel: usb 1-8: device not accepting address 120, error -71

 

This repeats about once a second. If I unload ehci_hcd and allow uhci_hcd to handle it, it works fine at USB 1.1. Plugged into the back of the same machine, it mounts fine as 2.0:

 

Sep 26 15:13:05 oobleck kernel: Vendor: Corsair Model: Flash Voyager Rev: 1.00

Sep 26 15:13:05 oobleck kernel: Type: Direct-Access ANSI SCSI revision: 00

Sep 26 15:13:05 oobleck kernel: SCSI device sdb: 4063232 512-byte hdwr sectors (2080 MB)

Sep 26 15:13:05 oobleck kernel: sdb: Write Protect is off

Sep 26 15:13:05 oobleck kernel: sdb: assuming drive cache: write through

Sep 26 15:13:05 oobleck kernel: SCSI device sdb: 4063232 512-byte hdwr sectors (2080 MB)

Sep 26 15:13:05 oobleck kernel: sdb: Write Protect is off

Sep 26 15:13:05 oobleck kernel: sdb: assuming drive cache: write through

Sep 26 15:13:05 oobleck kernel: sdb: sdb1

Sep 26 15:13:05 oobleck kernel: Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0

Sep 26 15:13:05 oobleck scsi.agent[18036]: disk at /devices/pci0000:00/0000:00:10.4/usb1/1-3/1-3.1/1-3.1:1.0/host2/target2:0:0/2:0:0:0

Sep 26 15:13:05 oobleck fstab-sync[18087]: added mount point /media/CORSAIR for

/dev/sdb1

Sep 26 15:13:05 oobleck kernel: FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!

Sep 26 15:13:05 oobleck kernel: SELinux: initialized (dev sdb1, type vfat), uses genfs_contexts

 

A thread on Red Hat's Bugzilla found that some devices were having this behavior due to drawing too much current from the USB power lines, and that they got good performance using powered USB hubs. However, I should not need a powered USB hub to use my memory stick. My problem is with at least two computers, so I don't think it's the computers. Further, the Asus board was certified as good by a recent Asus RMA for another problem (that turned out to be the power supply). I had similar behavior in WinXP on the Thinkpad.

 

Is this a known failure mode, and should I RMA my stick?

 

Thanks,

 

--jh--

Link to comment
Share on other sites

Can you tell me the version of operation system and the kernel version you have installed?

 

Fedora Core 3,

 

kernel-2.6.9-1.667

kernel-2.6.10-1.741_FC3

kernel-2.6.10-1.760_FC3

kernel-2.6.10-1.766_FC3

kernel-2.6.10-1.770_FC3

kernel-2.6.11-1.14_FC3

kernel-2.6.11-1.27_FC3

kernel-2.6.11-1.35_FC3

kernel-2.6.12-1.1372_FC3

kernel-2.6.12-1.1378_FC3

 

Same behavior on all those, plus WinXP with the latest service pack.

 

--jh--

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...