USB Port not working for mouse

porridgewithraisins · 2023-10-11 10:31:32

I have two physical USB-A ports. One of them works properly (called "good port" below) with both my 2.4ghz receiver for my mouse and normal pendrives. In the other one (called "bad port" below), if I connect a Pendrive it works but if I connect the 2.4ghz receiver, it doesn't even show up on lsusb

- When mouse is connected to good port

$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0bda:2852 Realtek Semiconductor Corp. Bluetooth Radio
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:0c00 Elan Microelectronics Corp. ELAN:ARM-M4
Bus 001 Device 002: ID 30c9:000e Luxvisions Innotech Limited HP Wide Vision HD Camera
Bus 001 Device 004: ID 25a7:fa67 Areson Technology Corp 2.4G Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

- When mouse is connected to bad port

$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0bda:2852 Realtek Semiconductor Corp. Bluetooth Radio
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:0c00 Elan Microelectronics Corp. ELAN:ARM-M4
Bus 001 Device 002: ID 30c9:000e Luxvisions Innotech Limited HP Wide Vision HD Camera
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

- When pendrive is connected to bad port (this bus 004 device 004 doesnt show up if I connect my 2.4ghz receiver in that port)

$ lsusb
Bus 004 Device 004: ID 0781:5590 SanDisk Corp. Ultra Dual
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0bda:2852 Realtek Semiconductor Corp. Bluetooth Radio
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:0c00 Elan Microelectronics Corp. ELAN:ARM-M4
Bus 001 Device 002: ID 30c9:000e Luxvisions Innotech Limited HP Wide Vision HD Camera
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

- Dmesg

$ sudo dmesg | curl -F'file=@-' http://0x0.st
http://0x0.st/H4Bx.txt

- Device

Hp Pavilion Aero 13

UPDATE:

This is happening for any input device. I connected a usb keyboard and the exact same thing happens.

Last edited by porridgewithraisins (2023-10-11 11:33:58)

V1del · 2023-10-11 10:41:56

The mouse reacting allergic to the increased current on the USB3 port? Does the mouse work in other usb 3 ports on other systems?

porridgewithraisins · 2023-10-11 11:30:11

Yes. Like I said, it even works on the other USB3 port in the same system (see the first lsusb)

V1del · 2023-10-11 11:40:57

This is why I asked, it's connected to a 2.0 hub in the first output.

porridgewithraisins · 2023-10-11 11:56:57

Oh, sorry. I will check properly and get back to you.

porridgewithraisins · 2023-10-11 12:09:46

I tried it on another linux machine (intel arch linux), and it didn't work on USB3, only worked on the USB2

Last edited by porridgewithraisins (2023-10-11 12:33:57)

porridgewithraisins · 2023-10-11 12:23:16

Both my USB-A ports on my laptop are USB3. It seems that linux adds both 3.0 and 2.0 root hubs for each of your USB3 ports.

Last edited by porridgewithraisins (2023-10-11 12:29:59)

porridgewithraisins · 2023-10-11 12:47:15

https://0x0.st/H4Mp.txt is what is logged when I connected and disconnected a keyboard on the good port.

The same command outputs _nothing_ when I connected and disconnected on the bad port.

porridgewithraisins · 2023-10-11 12:58:25

Oct 11 16:50:59 lappy kernel: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
Oct 11 16:50:59 lappy kernel: usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.

I picked this out of the first dmesg I sent. Could this be the issue? Is link power mgmt responsible for deciding whether to use usb2 or 3?

seth · 2023-10-11 13:52:24

LPM is disabled for both USB 3 hubs.

What is the output of "lsusb -tv" when attaching the pen drive (or anything that supports USB 3) to the *good* jack?
Cause the keyboard goes USB 2…

porridgewithraisins · 2023-10-11 15:12:26

sandy [~] $ lsusb -tv
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
        ID 0bda:2852 Realtek Semiconductor Corp. 
    |__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
        ID 0bda:2852 Realtek Semiconductor Corp. 
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
        ID 0781:5590 SanDisk Corp. Ultra Dual
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
        ID 30c9:000e Luxvisions Innotech Limited 
    |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
        ID 30c9:000e Luxvisions Innotech Limited 
    |__ Port 4: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 12M
        ID 04f3:0c00 Elan Microelectronics Corp.

Sandisk is the pendrive connected to the _good_ jack

Last edited by porridgewithraisins (2023-10-11 15:13:16)

seth · 2023-10-11 19:45:58

That shows up on the USB3 bus…

dmesg -W

and then connect the dongle to the bad port and post the output.
You can also try to disable https://wiki.archlinux.org/title/Power_ … utosuspend (usbcore.autosuspend=-1) and check the BIOS and the manual, some devices discrimintate the current to the usb jacks and the wifi dongle might simply draw more than the bad port is willing to deilver.

porridgewithraisins · 2023-10-12 15:37:50

dmesg -W is empty when I connect the dongle to the bad port. I had tried this earlier with the - equivalent, I guess - journalctl -fk and same thing - no logs when I connect it to the bad port.

I get https://0x0.st/H4Mp.txt as logs when I connect (and disconnect) it to the good port.

2) I will try disabling autosuspend.

3) What do I search in the manual, any keywords?

Last edited by porridgewithraisins (2023-10-12 15:38:43)

seth · 2023-10-12 15:52:10

dmesg -W is empty when I connect the dongle to the bad port

ie. the device doesn't get detected *at all*, disabling autosuspend is moot at this point.
You're looking for anything USB related, "always on" features and power related stuff in the usb section, there's a chance that this isn't configurable at all.

porridgewithraisins · 2023-10-12 16:17:17

Hmm, I couldn't find the manual. Its an AMI F.05 Bios Revision 15.5 Firmware Revision 79.29.

I found an old picture from when I ran windows of my setup with a more standard wired USB mouse ( a really old one ) connected to the "bad" USB port. It was working there.

I just retrieved that old mouse now and tried connecting it - it didn't work - empty dmesg -W, lsusb.

Last edited by porridgewithraisins (2023-10-12 16:24:16)

seth · 2023-10-12 19:43:03

A regular-ass wired mouse won't draw so much power.
Sanity check: when attaching a pendrive to the "bad" port you get output in "dmesg -W"?

Can you boot some live distro like grml or knoppix and test the behavior of the port there to rule out HW issues?

porridgewithraisins · 2023-10-13 13:42:41

[ 5400.843300] usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
[ 5400.860623] usb 4-1: New USB device found, idVendor=0781, idProduct=5590, bcdDevice= 1.00
[ 5400.860634] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5400.860637] usb 4-1: Product: Ultra
[ 5400.860639] usb 4-1: Manufacturer: SanDisk
[ 5400.860640] usb 4-1: SerialNumber: 4C531001530908113395
[ 5400.861434] usb-storage 4-1:1.0: USB Mass Storage device detected
[ 5400.861780] scsi host0: usb-storage 4-1:1.0
[ 5401.865210] scsi 0:0:0:0: Direct-Access     SanDisk  Ultra            1.00 PQ: 0 ANSI: 6
[ 5401.865968] sd 0:0:0:0: [sda] 121307136 512-byte logical blocks: (62.1 GB/57.8 GiB)
[ 5401.867334] sd 0:0:0:0: [sda] Write Protect is off
[ 5401.867339] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 5401.867699] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 5401.876721]  sda: sda1 sda2
[ 5401.877050] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 5409.801938] usb 4-1: USB disconnect, device number 3

Is what I get when attaching (and disconnecting) a pendrive to the bad port (I have automount with gvfs and thunar-volman hence the mounting messages)

2) Will the standard arch iso do? Can I test it in there?

Last edited by porridgewithraisins (2023-10-13 13:44:15)

seth · 2023-10-13 13:58:55

2) Will the standard arch iso do? Can I test it in there?

No, we want to get away from the current SW stack as far as possible.

porridgewithraisins · 2023-10-13 15:27:50

I tried it with crunchbang++ (Debian 12 + openbox basically) and same issue there (empty dmesg -W for input devices, but works properly with pendrives). So it's nothing to do with arch specifically. Must be a kernel/driver thing.

Last edited by porridgewithraisins (2023-10-13 15:28:15)

seth · 2023-10-13 15:29:14

I worry it's rather the HW

porridgewithraisins · 2023-10-13 16:34:29

You're probably right.

It's not really a blocker for me, so I don't mind. But I am still curious as it did work with windows. Do you know any reasons for why that may happen?

seth · 2023-10-13 18:22:46

The operative term would be "did" - do you know whether it still "does"?
(Cause that's the nature of things, they work and then they're broken…)

Arch Linux

#1 2023-10-11 10:31:32

USB Port not working for mouse

#2 2023-10-11 10:41:56

Re: USB Port not working for mouse

#3 2023-10-11 11:30:11

Re: USB Port not working for mouse

#4 2023-10-11 11:40:57

Re: USB Port not working for mouse

#5 2023-10-11 11:56:57

Re: USB Port not working for mouse

#6 2023-10-11 12:09:46

Re: USB Port not working for mouse

#7 2023-10-11 12:23:16

Re: USB Port not working for mouse

#8 2023-10-11 12:47:15

Re: USB Port not working for mouse

#9 2023-10-11 12:58:25

Re: USB Port not working for mouse

#10 2023-10-11 13:52:24

Re: USB Port not working for mouse

#11 2023-10-11 15:12:26

Re: USB Port not working for mouse

#12 2023-10-11 19:45:58

Re: USB Port not working for mouse

#13 2023-10-12 15:37:50

Re: USB Port not working for mouse

#14 2023-10-12 15:52:10

Re: USB Port not working for mouse

#15 2023-10-12 16:17:17

Re: USB Port not working for mouse

#16 2023-10-12 19:43:03

Re: USB Port not working for mouse

#17 2023-10-13 13:42:41

Re: USB Port not working for mouse

#18 2023-10-13 13:58:55

Re: USB Port not working for mouse

#19 2023-10-13 15:27:50

Re: USB Port not working for mouse

#20 2023-10-13 15:29:14

Re: USB Port not working for mouse

#21 2023-10-13 16:34:29

Re: USB Port not working for mouse

#22 2023-10-13 18:22:46

Re: USB Port not working for mouse

Board footer