Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#11394 - USB flash drives not recognized in kernel26 - 2.6.26.3
Attached to Project:
Arch Linux
Opened by Tom (tom_nyskelo) - Thursday, 04 September 2008, 08:49 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 06 September 2008, 07:58 GMT
Opened by Tom (tom_nyskelo) - Thursday, 04 September 2008, 08:49 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 06 September 2008, 07:58 GMT
|
DetailsDescription:
After upgrading to kernel 2.6.26.3 none of my flash drives is recognized. I tested two of them (iriver T30 and sansa e130) on different OSes (knoppix, slackware) and they were fine. Wonder if somebody else has this problem. Dmesg doesn't show anything useful for both drives: < usb 1-5: new high speed USB device using ehci_hcd and address 5 usb 1-5: configuration #1 chosen from 1 choice > Additional info: kernel26-2.6.26.3-1-i686 Steps to reproduce: Well, just plug any USB drive in. If everythin's OK, then you're a lucky one ;) |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Saturday, 06 September 2008, 07:58 GMT
Reason for closing: Not a bug
Saturday, 06 September 2008, 07:58 GMT
Reason for closing: Not a bug
Comment by Tom (tom_nyskelo) -
Friday, 05 September 2008, 08:29 GMT
Well, tried it today, and everythings works fine. The interesting thing is that I did _nothing_. Damn mystery. Not sure if it's solved.
Comment by Roman Kyrylych (Romashka) -
Saturday, 06 September 2008, 07:58 GMT
I remember I had the same weird issue after upgrading kernel, but it was "fixed" after reboot.