[SOLVED] USB 3.0 ports do not work

[Kactux]

I have a problem with USB 3.0 not working. Here's what happens. They initially come up one time where you can mount and see the contents of the drive but as soon as you click any file it disappears and never returns. The system lets you mount once and then the drive disappears never to return again. All the ports continue to work for charging devices. All the USB2 ports work as normal. The USB3 ports work if I boot into Windows. I have an Icy Dock where I boot to other OS. The problem also happens when I boot into KDE Neon which leads me to believe it's an Ubuntu issue and not a hardware, software, or Plasma problem. I have updated BIOS to the latest version.

Here's my specs:
OS: Kubuntu 23.04 x86_64
Host: MS-7693 4.0
Kernel: 6.2.0-23-generic
Shell: bash 5.2.15
DE: Plasma 5.27.4
CPU: 2015 Piledriver-Based AMD FX-8350 Black Edition Vishera 8-Core 4.0GHz (4.2GHz Turbo) Socket AM3+ Processor
Motherboard” 2015 MSI 970 Gaming AM3+ AMD 970 SATA 6Gb/s USB 3.0 ATX AMD
Memory: 2015 GSkill Sniper Series 4x4 DDR3 PC3-14900U
XHCI is enabled

This is lsusb where I don't see where a 3.0 controller is?
Bus 004 Device 002: ID abcd:1234 LogiLink UDisk flash drive
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 1e7d:3098 ROCCAT ROCCAT Vulcan AIMO
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 046d:0892 Logitech, Inc. C920 HD Pro Webcam
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1b1c:0a51 Corsair CORSAIR VOID ELITE Wireless Gam
ing Dongle
Bus 001 Device 002: ID 320f:2002 SONiX USB DEVICE
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 010 Device 003: ID abcd:1234 LogiLink UDisk flash drive
Bus 010 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Not sure what I should do at this point. Maybe it's a specific immou for the kernel I am on? Is there different commands to input based on the brand of processor you are using. Like should I enable grub to add boot flag `amd_iommu=on`

[claydoh]

This is lsusb where I don't see where a 3.0 controller is?

lsusb shows connected devices, not the on-board controllers. You will see that in lspci.

Here are mine, for example:

Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
...
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub

leads me to believe it's an Ubuntu issue

or a general Linux one, barring other distros working (or not) on this old hardware.
Hopefully it is a simple config edit or tweak for it to work properly.

What filesystem are these drives formatted with?


For the moment, you might try running Dolphin from a terminal and see if anything happens when reproducing this.

Also, you also might want to see what dmesg logs show. You can use a GUI tool such as KSystemLog to view this ("system log") as you plug/unplug. and attempt to access things.

[Schwarzer Kater]

Welcome!

lsusb -vvt outputs a better overview.

[gnomek]

I am not sure if this is the same problem but maybe worth mentioning. I could use USB2 ports but not USB3 ports with Seagate disk that had usb adapter. When I plugged it to USB2 it worked normally but when plugged it to USB3 it was not seen at all by blkid nor by motherboard. This solution helped me and I can use Sata3.

[Kactux]

Filesystem: ext4
Yes, old hardware and yes, probably a linux kernel xHCI problem
If I reboot and plug in the usb3 hub it works momentarily. xHCI seems to have trouble staying powered "on"
dmesg logs show:

6/29/23 12:26 AM            2023-06-29T00:26:03.221780-07:00 kubuntu kernel: [  982.808383] xhci_hcd 0000:02:00.0: Host halt failed, -110
6/29/23 12:26 AM            2023-06-29T00:26:18.474186-07:00 kubuntu kernel: [  998.029005] xhci_hcd 0000:02:00.0: xHCI host not responding to stop endpoint command
6/29/23 12:26 AM            2023-06-29T00:26:18.474210-07:00 kubuntu kernel: [  998.061020] xhci_hcd 0000:02:00.0: Host halt failed, -110
6/29/23 12:26 AM            2023-06-29T00:26:18.474213-07:00 kubuntu kernel: [  998.061026] xhci_hcd 0000:02:00.0: xHCI host controller not responding, assume dead
6/29/23 12:26 AM            2023-06-29T00:26:18.474215-07:00 kubuntu kernel: [  998.061065] xhci_hcd 0000:02:00.0: HC died; cleaning up
6/29/23 12:26 AM            2023-06-29T00:26:18.474241-07:00 kubuntu kernel: [  998.061137] usb 8-1: USB disconnect, device number 2
6/29/23 12:26 AM            2023-06-29T00:26:18.474272-07:00 kubuntu kernel: [  998.061145] usb 8-1.1: USB disconnect, device number 7
6/29/23 12:26 AM            2023-06-29T00:26:18.474276-07:00 kubuntu kernel: [  998.061150] usb 8-1.1.4: USB disconnect, device number 8
6/29/23 12:26 AM            2023-06-29T00:26:18.474279-07:00 kubuntu kernel: [  998.061156] usb 8-1.1.4.4: USB disconnect, device number 9
6/29/23 12:26 AM            2023-06-29T00:26:18.474281-07:00 kubuntu kernel: [  998.061161] usb 8-1.1.4.4.4: USB disconnect, device number 10
6/29/23 12:26 AM            2023-06-29T00:26:18.474284-07:00 kubuntu kernel: [  998.061166] usb 8-1.1.4.4.4.4: USB disconnect, device number 11
6/29/23 12:26 AM            2023-06-29T00:26:18.477790-07:00 kubuntu kernel: [  998.061539] usb 9-1: USB disconnect, device number 6
6/29/23 12:26 AM            2023-06-29T00:26:18.477813-07:00 kubuntu kernel: [  998.061546] usb 9-1.4: USB disconnect, device number 7
6/29/23 12:26 AM            2023-06-29T00:26:18.477816-07:00 kubuntu kernel: [  998.061552] usb 9-1.4.4: USB disconnect, device number 8
6/29/23 12:26 AM            2023-06-29T00:26:18.477818-07:00 kubuntu kernel: [  998.061556] usb 9-1.4.4.4: USB disconnect, device number 9
6/29/23 12:26 AM            2023-06-29T00:26:18.581742-07:00 kubuntu kded5[1408]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdc”" for "/org/freedesktop/UDisks2/block_devices/sdc"
6/29/23 12:26 AM            2023-06-29T00:26:18.582230-07:00 kubuntu plasmashell[1454]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdc”" for "/org/freedesktop/UDisks2/block_devices/sdc"
6/29/23 12:26 AM            2023-06-29T00:26:18.583838-07:00 kubuntu org_kde_powerdevil[1476]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdc”" for "/org/freedesktop/UDisks2/block_devices/sdc"
6/29/23 12:26 AM            2023-06-29T00:26:18.584950-07:00 kubuntu kded5[1408]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdc”" for "/org/freedesktop/UDisks2/block_devices/sdc"
6/29/23 12:26 AM            2023-06-29T00:26:18.591433-07:00 kubuntu plasmashell[1454]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdc”" for "/org/freedesktop/UDisks2/block_devices/sdc"​

[claydoh]

I would look at that hub, maybe it wants more current than the usb2 ports can supply, maybe? But that would happen on Windows, you's think.
Do individual items plugged directly into the computer's ports work properly (just to check)?
The hub itself may just have poor linux support via cheap/crappy controllers.

But, it also looks quite similar to what some people experience with some Android phones sometimes. One possible fix is to try is to disable USB autosuspend, which can be set by a kernel parameter edit in Grub:


run:

cat /sys/module/usbcore/parameters/autosuspend

(if the result is 2, then autosuspend is enabled)

if so,
Open /etc/default/grub in kate/Kwrite,

Change
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1"
and save file

Run

sudo update-grub

reboot system

then check :

cat /sys/module/usbcore/parameters/autosuspend

(result should be -1)

To revert, repeat the above, to remove the added text and update grub.

[Kactux]

All USB 3.0 ports on the back and front panel act the same as the hub. When anything is plugged any 3.0 port works for a few seconds and then turns off never to return. Camera, mouse, mic, flash drive all experience the same result. I tried disabling autosuspend to no avail. Same result. Also, the power to the USB 3.0 ports works fine. The USB 2 ports all work perfectly as well.

[Kactux]

I tried. Guess it's time to save up for a new mobo, proc, and RAM.

[Schwarzer Kater]

[…]
The USB3 ports work if I boot into Windows. I have an Icy Dock where I boot to other OS. The problem also happens when I boot into KDE Neon which leads me to believe it's an Ubuntu issue and not a hardware, software, or Plasma problem.
[…]

Before you start buying new hardware - did you try booting with a Kubuntu 23.04 or Kubuntu 22.04 LTS live USB stick or another Linux live USB stick (Debian, Fedora, openSUSE Tumbleweed, …), even with another desktop environment on those live USB sticks like for example a standard Ubuntu or Fedora with GNOME?

[Kactux]

Yes, every Linux distro I've tried will not boot from the USB 3.0. It starts to boot fine from USB 3.0 but then after a while I get an error

/init:line 38: can't open /dev/sdb: No medium found
Unable to find a medium containing a live file system
Attempt interactive netboot from a URL?
yes no (default yes):

I can only load linux from a USB 2.0 port and once loaded every Linux distro: Kubuntu 23.04, Neon, and Garuda all do not work properly. As I said, it works momentarily but then stops working completely until a reboot then the same thing happens it will work for a few seconds then stops and never comes back until a reboot which then only works for a few seconds again and again.
Windows works perfectly, which is really upsetting.

[claydoh]

It may be a general hardware compatibility issue, even with Windows sometimes. These hits are mostly old, but there are quite a few for this board specifically. If your BIOS is up to date, it might be worth trying the iommu=soft option added to Grub, as many of these point to.

[Kactux]

I read those posts too and iommu=soft added to grub was one of the first things I tried. I just can't understand how it works for some with exact same motherboard but not for me. And the fact that everything works as it should in Windows is just perplexing. I know someone has the answer. I just don't know enough to fix it.

[claydoh]

Hmm... I wonder if using amd_iommu=on, or probably =off might be worth trying, or even disabling/enabling it in the BIOS (the grub kernel option to do so may be easier and safer)? Not 100% sure if the =soft parameter is even valid in modern kernels.

I don't think iommu is overly useful in general uses, mainly it is for virtualization in regards to hardware apps-through, iirc.

[claydoh]

I just can't understand how it works for some with exact same motherboard but not for me

There is the chance that different revision for the board uses a different USB3 chip. I am assuming a VIA chipset, which seems to have issues across a wide range of devices, including Raspberry PIs. They do supply a wide range of slightly different usb3 chipsets, it seems.

[Snowhog]

If I reboot and plug in the usb3 hub

I try to never assume anything, so...

Are you plugging the usb3 hub into one of the USB3 ports?