Ubuntu – USB 2.0 device is not working in USB 3.0 ports

driverslinuxUbuntuusb

I have a Ubuntu 12.04 system. On that system I have one USB 3.0 port. In this port I am trying use my USB 2.0 device, but every time when I plug in that USB 2.0 device into the USB 3.0 port, the system gets hung and I try to shutdown but it won't allow me to.

If I continue to match Port types to Device speeds (2.0 to 2.0) everything woks fine.

So my question is: How can I allow a USB 3.0 port to use a USB 2.0 device or is there any way to convert a USB 3.0 port to a USB 2.0 port like drivers or something?

Am I mistaking the issue I'm having for another type of problem?

Here is my lsub command output

Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 046d:0823 Logitech, Inc. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 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 002 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 009: ID 046d:0823 Logitech, Inc. 
Bus 002 Device 008: ID 5555:1110 Epiphan Systems Inc. VGA2USB
Bus 002 Device 006: ID 0d8c:0008 C-Media Electronics, Inc. 
Bus 002 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

and for dmesg command output you can refer this link

Suggestions would be appreciated. Thanks in advance.

Best Answer

This issue is retalted to the kernel. I have the same type of problem. To resovle this issue I updated my kernel. For this I reffred this link

Related Solutions

Linux – USB 3.0 ports not working

It might be that the driver for the chip that's running the USB 3.0 ports isn't compiled into kernel. You can check the chipset information using lspci command:

$ /usr/sbin/lspci  |grep -i usb
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 02)

Then check kernel configuration whether the USB 3.0 driver is indeed enabled...

How to mount a filesystem from a given USB bus:device

When you see the handlers like gphoto2:// and smb:// these are special interfaces that the GNOME desktop or whatever file browser you're using is making available to access these devices. In the case of gphoto2, the desktop is using the application gphoto2`

lsof

The only way I can think to gain access to a mount such as this would be to mount it as you did before using Nautilus or whatever file browser, and then using a tool such as lsof to see what files/devices are opened by Nautilus.

$ lsof -p $(pgrep nautilus)

But if you're having to connect to your phone via gphoto2 then you're likely not mounting the device a a mass storage device but rather a PTP - Picture Transfer Protocol. There's a Linux FUSE implementation for PTP too.

gvfs?

I would also look in your $HOME directory for a sub-directory called .gvfs. Usually when GNOME or Nautilus are doing the mounting this directory is created as a convenience.

In newer versions of GNOME (3+) this directory has moved and is now here, /run/user/$UID/gvfs.

Example

$ ls -l /run/user/$UID/gvfs/smb-share\:server\=tank\,share\=t 
total 2
drwx------. 1 saml saml    0 Oct 31 09:16 Development
drwx------. 1 saml saml    0 Nov 18 14:52 home
drwx------. 1 saml saml    0 May 14  2013 incoming
...

NOTE: That's a environment variable $UID that is often set in Bash on most modern systems. If it isn't set you can find your user's ID like so:

$ id
uid=1000(saml) gid=1000(saml) groups=1000(saml),10(wheel) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023