A basic suggestion would be to disable legacy usb3 ib uef and see if that helps,but there are more posts concerned with usb 3. and etron ,if not on this page then the previous one.
I am having trouble getting my Extreme4-M motherboard to work with either the front or rear USB 3.0 connections. I am using a SilverStone TS07B external case with Seagate 1 TB hard drives to perform back ups. I can get the external hard drives to work with the USB 2.0 connections but not the 3.0(external enclosure has USB 3.0 compatibility). When I try to connect using USB 3.0 the drive tries over and over to mount with the drive appearing onscreen and then disappearing and reappearing in a new window. I am using Ubuntu 12.04 64 bit. here is the output of lsusb:
desktop:~$ lsusb
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 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 001 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 002 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 004: ID 046d:c01b Logitech, Inc. MX310 Optical Mouse
Bus 002 Device 005: ID 04f9:01f5 Brother Industries, Ltd
Am I correct to say that there is an issue with the Asmedia USB controllers and Linux or does the problem lie elsewhere. I replaced the motherboard with an RMA once and had the same issue.
A basic suggestion would be to disable legacy usb3 ib uef and see if that helps,but there are more posts concerned with usb 3. and etron ,if not on this page then the previous one.
I see you have a Linux foundation 3.0 root hub, which means Linux see your USB 3 controller.
I do not see in this list however anything connected to it.
Looks to me like you have a USB hub with mostly everything except the UPS connected to it.
make sure you are using the XHCI_HCD driver for the USB3 devices.
You can find out by running this command:
lspci -k
A sample snip of output would look like this:
Code:05:00.0 USB controller: Etron Technology, Inc. EJ188/EJ198 USB 3.0 Host Controller Subsystem: ASRock Incorporation Device 7052 Kernel driver in use: xhci_hcd
I disabled USB 3 legacy , I will try a drive this afternoon and see how it works out
I don't see USB 3.0 controller listed
Code:$ lspci -k 00:00.0 Host bridge: Intel Corporation Ivy Bridge DRAM Controller (rev 09) Subsystem: ASRock Incorporation Device 0150 Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller: Intel Corporation Ivy Bridge Graphics Controller (rev 09) Subsystem: ASRock Incorporation Device 0162 Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller: Intel Corporation Panther Point USB xHCI Host Controller (rev 04) Subsystem: ASRock Incorporation Device 1e31 Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation Panther Point MEI Controller #1 (rev 04) Subsystem: ASRock Incorporation Device 1e3a Kernel driver in use: mei Kernel modules: mei 00:1a.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #2 (rev 04) Subsystem: ASRock Incorporation Device 1e2d Kernel driver in use: ehci_hcd 00:1b.0 Audio device: Intel Corporation Panther Point High Definition Audio Controller (rev 04) Subsystem: ASRock Incorporation Device 1898 Kernel driver in use: snd_hda_intel Kernel modules: snd-hda-intel 00:1c.0 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 1 (rev c4) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.5 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 6 (rev c4) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.7 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 8 (rev c4) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #1 (rev 04) Subsystem: ASRock Incorporation Device 1e26 Kernel driver in use: ehci_hcd 00:1f.0 ISA bridge: Intel Corporation Panther Point LPC Controller (rev 04) Subsystem: ASRock Incorporation Device 1e44 Kernel modules: iTCO_wdt 00:1f.2 SATA controller: Intel Corporation Panther Point 6 port SATA Controller [AHCI mode] (rev 04) Subsystem: ASRock Incorporation Device 1e02 Kernel driver in use: ahci 00:1f.3 SMBus: Intel Corporation Panther Point SMBus Controller (rev 04) Subsystem: ASRock Incorporation Device 1e22 Kernel modules: i2c-i801 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) Subsystem: ASRock Incorporation Motherboard (one of many) Kernel driver in use: r8169 Kernel modules: r8169 03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) Subsystem: ASRock Incorporation Device 0612 Kernel driver in use: ahci
appears to be a USB3 device, Intel and not ASmedia as you previously thought. and I note that you appear to only have one USB3 controller.Code:00:14.0 USB controller: Intel Corporation Panther Point USB xHCI Host Controller (rev 04) Subsystem: ASRock Incorporation Device 1e31 Kernel driver in use: xhci_hcd
lsusb -v -s 4:
will give you a lot more detail about the controller and it's capabilities.
value iSerial will probably = 0000:00:14.0
which is the PCI device it is on (00:14.0 as above)
tail -n 0 -f /var/log/messages
before you connect the device will output the system logs, you will be able to see here for any errors.
ctrl-c gets you out again.
while doing the "tail follow" you could probably connect to usb2 first to see what a normal connection looks like. and then try USB3 to see what errors or differences appear.
I guess I should elaborate.
lsusb -v -s 4:
because the "root" bus is 4 as you shown above from your lsusb. -v is verbose
If you wanted to show verbose information of device 2 on usb bus 4, it would be lsusb -v -s 4:2
tail (command to display last 10 lines of file)
-n 0 (change default 10 lines to zero lines)
-f (follow. don't close file and exit, display any new lines added to file)
@kick
Disabling USB 3 Legacy mode may have worked. I tried a backup with the USB connection and had no issues with disconnects (or dismounts)as I had previously. Is it correct to say that the USB 3 is in fact still performing as USB 3 (ie disabling Legacy mode did not disable USB 3 completely and make it USB 2)? I am fairly new to building computers (this is my second build) so please excuse me if the answer to my question is obvious
@synack
Sorry I am not very clever with computers and I am afraid I am confused with the instructions. Here is the output of lsusb -v -s 4:Code:Bus 002 Device 004: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 2 TT per port bMaxPacketSize0 64 idVendor 0x0424 Standard Microsystems Corp. idProduct 0x2514 USB 2.0 Hub bcdDevice 0.00 iManufacturer 0 iProduct 0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 41 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 1 Single TT iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 12 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 1 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 2 TT per port iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 12
Last edited by AsIf123; 01-22-2013 at 03:21 AM. Reason: add info
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks