Comment 10 for bug 261710
Revision history for this message
| Nelson Villoria (nvilloria) wrote Re: [Bug 261710] Re: Corsair Flash Voyager 8GB USB key causes device descriptor read/64, error -110 | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
Dear James, sorry I could not do this earlier, in any case, attached
are the log files you indicated (dmesg.log and lspci-vvnn.log). Also:
uname -a
Linux chiquita 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008
x86_64 GNU/Linux
One last thing, Corsair agreed to change the hardware as a solution to
the incompatibility with Ubuntu --- today I just received the new key:
I just plugged it in, and it just does not work. Hopefully we can find
a solution to this. In the meantime I'll try this low level format
strategy to see what happens. Thanks for your help, and just let me
know if you need anything else from my end. I may be able to respond
quicker now.
Also, for those interested in the Corsair response to this issue, info
is available at:
http://
Nelson.
On Fri, Aug 29, 2008 at 3:58 AM, James Collier
<email address hidden> wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately we can't fix it without more information.
>
> Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
> 1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
> 2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
> 3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
>
> For your reference, the full description of procedures for kernel-
> related bug reports is available at
> https:/
>
> ** Changed in: linux (Ubuntu)
> Sourcepackagename: None => linux
> Status: New => Incomplete
>
> --
> Corsair Flash Voyager 8GB USB key causes device descriptor read/64, error -110
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "linux" source package in Ubuntu: Incomplete
>
> Bug description:
> Hi,
>
> I have a Corsair Flash Voyager 8GB that works nicely in Windows (XP and Vista). In principle, it was not recognized in any of my two machines with Ubuntu Hardy Heron 8.04 64 Bits (other usb keys work fine). After a fresh format with fat32, both machines recognize it, but after a while ( using the disk 3 or 4 times), Ubuntu does not recognized them anymore. the typical dmesg is:
>
> [ 552.433613] usb 5-8: new high speed USB device using ehci_hcd and address 7
> [ 567.536417] usb 5-8: device descriptor read/64, error -110
> [ 582.743163] usb 5-8: device descriptor read/64, error -110
> [ 582.959038] usb 5-8: new high speed USB device using ehci_hcd and address 8
> [ 598.061834] usb 5-8: device descriptor read/64, error -110
> [ 613.268593] usb 5-8: device descriptor read/64, error -110
> [ 613.484458] usb 5-8: new high speed USB device using ehci_hcd and address 9
> [ 623.886103] usb 5-8: device not accepting address 9, error -110
> [ 623.998033] usb 5-8: new high speed USB device using ehci_hcd and address 10
> [ 634.399702] usb 5-8: device not accepting address 10, error -110
>
> An I should add that tried it in:
> 1) Knoppix 5.1 (kernel 2.6.19) in a DELL Optiplex GX280,
> 2) Ubuntu 8.04-64 bit (kernel 2.6.24-19) in a XPS M13330 and in a DELL DImension E510, and
> 3) Ubuntu (32 bit) 6.06 LTS Dapper Drake in a DELL Optiplex GX280.
> and in all of them the pattern is the same, after a fresh format fat32, the systems do not recognize the usb key yielding a device descriptor read/64, error -110.
>
> I followed the webpage https:/
>
> In advance, many many thanks!
>
> Nelson Villoria
>