Announcement

Collapse
No announcement yet.

Post K16.04 installation USB 3.0 ports are not recognized.

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Post K16.04 installation USB 3.0 ports are not recognized.

    Here is what I have done so far:

    I enabled EHCI in my BIOS as per a posting in Ubuntu forums. It did not change anything, so I disabled it again.

    I have a dual-boot K14.04LTS64bit/K16.04 64bit. Both OS's are affected by the lack of USB 3.0. USB 3.0 thumb drives are recognized in USB 2.0 ports, though.

    I installed:

    sudo apt-get install xserver-xorg-input-all with no positive results based on recommendation Ubuntu posting.

    I installed:

    sudo apt-get install linux-image-generic with no positive results based on the same posting.

    When I enabled the EHCI in my BIOS, I later found that that cure was only for installed boards not where USB is included in the Motherboard, as is my case, and the reason I later disabled it in my BIOS.

    Additional information about my computer:

    steven@stevenK14:~$ lsusb
    Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 011 Device 002: ID 062a:5918 Creative Labs
    Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 003 Device 002: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 009 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
    Bus 009 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
    Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 005 Device 002: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
    Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 008 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
    Bus 008 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
    Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    steven@stevenK14:~$ lspci
    00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B) (rev 02)
    00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port B)
    00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port D)
    00:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port E)
    00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port H)
    00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx1 port A)
    00:0b.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (NB-SB link)
    00:0d.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx1 port B)
    00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)
    00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
    00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
    00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
    00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
    00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 42)
    00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40)
    00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
    00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40)
    00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
    00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0)
    00:15.1 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 1)
    00:15.2 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 2)
    00:15.3 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 3)
    00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
    00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
    00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0
    00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1
    00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2
    00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3
    00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4
    00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5
    01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
    01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
    02:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
    03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
    04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
    06:00.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa)
    07:00.0 Multimedia audio controller: Creative Labs SB0400 Audigy2 Value
    09:05.0 Multimedia video controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
    09:05.1 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05)
    09:05.2 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05)
    09:05.4 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [IR Port] (rev 05)
    0b:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09)
    0c:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
    0d:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
    steven@stevenK14:~$

    Lots of users had/have this problem as of March 2015.

    Has anyone seen the fix? Thanks!

    #2
    Originally posted by Shabakthanai View Post
    I have a dual-boot K14.04LTS64bit/K16.04 64bit. Both OS's are affected by the lack of USB 3.0. USB 3.0 thumb drives are recognized in USB 2.0 ports, though.

    steven@stevenK14:~$ lsusb
    Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 011 Device 002: ID 062a:5918 Creative Labs
    Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 003 Device 002: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 009 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
    Bus 009 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
    Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 005 Device 002: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
    Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 008 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
    Bus 008 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
    Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    lsusb does report a 3.0 root hub. What makes you believe otherwise?
    Windows no longer obstructs my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #3
      When I put a USB 3.0 stick in a USB 3.0 port, it does not show in Dolphin under the list of active partitions and drives. That is the only place I have found USB connections in the past. When I put a USB 3.0 stick in a USB 2.0 slot, it appears in that column of drives in Dolphin.

      Is a USB hub the place I install a USB stick or the connection to the motherboard? I am not familiar with the term USB hub yet and have probably been using the term incorrectly in the past and still been understood? I have been calling the place you plug the USB stick in "port", an assumption on my part. Shab

      Comment


        #4
        On a 2013 post on ubuntu forums, it says some folks fixed it by adding "blacklist uas" to the /etc/modules/blacklist.conf file.

        Comment


          #5
          Hi, my friend, I did not have the file you mentioned in my computer. I had a 'modules-load.d' but that is the only file that contained the word 'modules'. I opened it anyway to see if there was anything relating to blacklist, and there was not. Thanks for the input. The information I got was more current, March 2015. There were a great number of posts confirming the same problem, but no one replied with a solution.

          I don't think this had anything to do with recent work being done on my computer, but it may relate to the K16.04 installation. I looked in the BIOS and all USB connections seem to be appropriately entered.

          Originally posted by dibl View Post
          On a 2013 post on ubuntu forums, it says some folks fixed it by adding "blacklist uas" to the /etc/modules/blacklist.conf file.

          Comment


            #6
            Originally posted by Shabakthanai View Post
            Hi, my friend, I did not have the file you mentioned in my computer. I had a 'modules-load.d' .....
            Ooops, you are correct there's no more /etc/modules/blacklist.conf. Blacklisting is now done (in Debian) in /etc/modprobe.d. There I have a file named intel-microcode-blacklist.d and it reads like this:

            Code:
            # The microcode module attempts to apply a microcode update when
            # it autoloads.  This is not always safe, so we block it by default.
            blacklist microcode
            I'm not sure whether *buntus are using /etc/modeprobe.d or whether that directory you found /etc/modules-load.d is your equivalent. But you can (as root) make a blacklist file similar to mine and save it there, and see if anything changes.

            # Make USB 3 work
            blacklist uas

            Comment


              #7
              I created a /etc/modules file because there was none. I was in sudo dolphin at the time. I then attempted to make an /etc/modules/blacklist.conf file, but was unable to make it. If that worked I intended to make a file /etc/modules/blacklist.conf/blacklist uas - was I attempting to do the right thing when I failed? Thanks!

              Originally posted by dibl View Post
              Ooops, you are correct there's no more /etc/modules/blacklist.conf. Blacklisting is now done (in Debian) in /etc/modprobe.d. There I have a file named intel-microcode-blacklist.d and it reads like this:

              Code:
              # The microcode module attempts to apply a microcode update when
              # it autoloads.  This is not always safe, so we block it by default.
              blacklist microcode
              I'm not sure whether *buntus are using /etc/modeprobe.d or whether that directory you found /etc/modules-load.d is your equivalent. But you can (as root) make a blacklist file similar to mine and save it there, and see if anything changes.

              # Make USB 3 work
              blacklist uas

              Comment


                #8
                Originally posted by Shabakthanai View Post
                I created a /etc/modules file because there was none. I was in sudo dolphin at the time. I then attempted to make an /etc/modules/blacklist.conf file, but was unable to make it. If that worked I intended to make a file /etc/modules/blacklist.conf/blacklist uas - was I attempting to do the right thing when I failed? Thanks!
                do not ever launch dolphin with "sudo" ,,,never , never , never ,,,,,,,,,,, use "kdesudo" allways.

                you want to make the file in /etc/modprobe.d so it would look like this ,,,,,, /etc/modprobe.d/yourfile ,,,,,we do not know for shure if it will work like you expect but you can make it like this .

                press alt+F2 to open krunner ,,,,,,,,, type "kdesudo kate /etc/modprobe.d/usb-uas-blacklist.conf" withought the quotes and press enter in the kate window that will open (after you type your password) copy and past this in it

                Code:
                # Make USB 3 work
                blacklist uas
                save the file and exit kate ,,,,,,reboot and test the usb ports with you usb3 stick .

                VINNY
                i7 4core HT 8MB L3 2.9GHz
                16GB RAM
                Nvidia GTX 860M 4GB RAM 1152 cuda cores

                Comment


                  #9
                  Thanks for the criticism Vinny, I forgot that Dolphin was among the kdesudo applications. I opened krunner and typed in kdesudo kate /etc/modprobe.d/usb-uas-blacklist.conf>pressed Enter>entered my password>Kate opened with # Make USB 3 work (next line) blacklist.uas>then I restarted my computer. When the login screen appeared, the background of that screen was different. Grey - Blue - Purple>I entered my password and the system opened. I then opened Dolphin to see if my USB ports were recognized. They were not. I just edited my reply. I believe when I made it I was having diabetic problems, because what I had printed was not what happened, in fact when I attempted to re-do the command steps, when I got to the final step, the code you recommended was already there, so I am pretty sure I followed your instructions.

                  Every once in a while my sugars go below safe standards. When that happens, I usually don't even notice it, in fact, fortunately, when I go through things to do, because my life is in jeopardy, the last thing I usually try is to read my sugars. I am not thinking properly at the time. I know I had to do this recently and it is the only thing I can think of that may have affected my reply. I have carefully retraced my steps and included an accurate happening above. Although it did not get the desired result, I suspect the result of the trial leads to another conclusion. Thanks for your patience. Hopefully when superuser is required in Dolphin, I will remember to use kdesudo. Shab

                  Originally posted by vinnywright View Post
                  do not ever launch dolphin with "sudo" ,,,never , never , never ,,,,,,,,,,, use "kdesudo" allways.

                  you want to make the file in /etc/modprobe.d so it would look like this ,,,,,, /etc/modprobe.d/yourfile ,,,,,we do not know for shure if it will work like you expect but you can make it like this .

                  press alt+F2 to open krunner ,,,,,,,,, type "kdesudo kate /etc/modprobe.d/usb-uas-blacklist.conf" withought the quotes and press enter in the kate window that will open (after you type your password) copy and past this in it

                  Code:
                  # Make USB 3 work
                  blacklist uas
                  save the file and exit kate ,,,,,,reboot and test the usb ports with you usb3 stick .

                  VINNY
                  Last edited by Shabakthanai; Apr 16, 2016, 05:13 PM.

                  Comment

                  Working...
                  X