2

I have a AMD 6800U based handheld. It has 2 x USB-C ports. Any USB type device I plug into either of these ports does not get "discovered" automatically. I have found that the ONLY way to get them to discover USB devices connected is to run either sudo lsusb -v or sudo cat /dev/bus/usb/009/001 (which is the root of the USB device).

I can see this by running sudo dmesg -w plug in the USB-C device and I get no output, as soon as I run either of the above, all the devices appear in the kernel logs.

Either of these cause the USB devices attached to the port to get discovered by the kernel. I have never seen this behaviour on Linux before. Any ideas what causes it? I am running Arch with Kernel 6.3.9-arch1-1.

EDIT: Added output from dmesg -k -w while booting with a USB-C SSD plugged in. The device is 6-2. Of note, after unplugging it, I plugged it again (nothing) and unplugged it againl which also doesn't show up at all in the output.

dmesg output

Improve this question
10
  • that sounds like a kernel bug, possibly a regression. When you boot from a USB drive with a more conservative kernel (say, the Ubuntu 23.04 live USB image), does it work?
    – Marcus Müller
    Commented Jun 27, 2023 at 8:53
  • I just tested 6.1.35-1-lts on the same hardware. Has exactly the same behaviour. This is not booting a live cd, I just installed the arch LTS kernel.
    – Steven Johnson
    Commented Jun 27, 2023 at 10:55
  • The intentionally different OS would help try other xinput/evdev/… configurations as well. But you could run sudo evtest to see whether that gives some insight!
    – Marcus Müller
    Commented Jun 27, 2023 at 11:20
  • I am having this exact same issue, began after force downgrading a 23.10 install back to 23.04, via apt pinning. Of note, neither lsusb, nor lsusb -vnor sudo lsusb work. It has to be sudo lsusb -v
    – Gregorio Litenstein
    Commented Oct 25, 2023 at 21:40
  • @GregorioLitenstein weird bug, do you have any hibernation/sleep option turned on?
    – tukan
    Commented Oct 26, 2023 at 12:12

1 Answer 1

Reset to default
-1

If SELinux is on, relabeling can resolve unexplained behavior.

sudo restorecon -Rv /
Improve this answer
1
  • Sorry but OP stated "Kernel 6.3.9-arch1-1" I just cannot see what SELinux would have to do in that stuff.
    – MC68020
    Commented Oct 26, 2023 at 20:34

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .