Bug 998281 - Connected device missing in /dev/ folder with the latest kernel.
Connected device missing in /dev/ folder with the latest kernel.
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
19
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-18 17:13 EDT by Adam
Modified: 2013-08-19 16:15 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-08-19 16:15:21 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam 2013-08-18 17:13:33 EDT
Hello!

With the latest kernel in Fedora 19 x64 I have a big problem. One of my pendrive can't be mounted beacuse I can't find the device file in /dev/ folder. With 3.9.5 kernel I had no  problem with it. Other pendrives are working well, but this one doesn't.

[adam@localhost ~]$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 04fc:0005 Sunplus Technology Co., Ltd USB OpticalWheel Mouse
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0c45:6441 Microdia 
Bus 001 Device 004: ID 0951:1643 Kingston Technology DataTraveler G3       <-- This is it!
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Adam
Comment 1 Josh Boyer 2013-08-19 15:11:22 EDT
Please try the 3.10.7 updates and let us know if you still have the issue.  There was a bug in the USB layer that was fixed with 3.10.7.
Comment 2 Adam 2013-08-19 16:15:21 EDT
After upgrade it's working fine. Thank you!

Note You need to log in before you can comment on or make changes to this bug.