You are not logged in.

#1 2020-02-07 04:27:15

Fryguy
Member
Registered: 2008-04-15
Posts: 13

[SOLVED] All devices connected to usb hub stopped working after update

Just did an update and after rebooting, no devices connected to my usb hub (a game controller, keyboard, mouse, and dac) worked.  They all seemed to show up in dmesg, but weren't actually functional.

The one exception was that the keyboard worked when typing in a tty.

Unplugging the devices and plugging them into non-hub usb ports causes them to work fine.

I'd love to avoid buying a new hub (if that's even the problem), and I don't have enough usb ports on this laptop to physically connect everything.

Here's output of plugging my mouse in via journalctl to the hub:

Feb 06 23:22:17 balves-work-laptop kernel: usb 1-2.2: new full-speed USB device number 36 using xhci_hcd
Feb 06 23:22:17 balves-work-laptop kernel: usb 1-2.2: New USB device found, idVendor=1038, idProduct=1720, bcdDevice= 1.21
Feb 06 23:22:17 balves-work-laptop kernel: usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 06 23:22:17 balves-work-laptop kernel: usb 1-2.2: Product: SteelSeries Rival 310 eSports Mouse
Feb 06 23:22:17 balves-work-laptop kernel: usb 1-2.2: Manufacturer: SteelSeries
Feb 06 23:22:17 balves-work-laptop kernel: usb 1-2.2: SerialNumber: 000000000000
Feb 06 23:22:17 balves-work-laptop kernel: hid-generic 0003:1038:1720.0033: hiddev0,hidraw1: USB HID v1.11 Device [SteelSeries SteelSeries Rival 310 eSports Mouse] on usb-0000:00:14.0-2.2/input0
Feb 06 23:22:17 balves-work-laptop kernel: input: SteelSeries SteelSeries Rival 310 eSports Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:1.1/0003:1038:1720.0034/input/input86
Feb 06 23:22:17 balves-work-laptop kernel: hid-generic 0003:1038:1720.0034: input,hidraw2: USB HID v1.11 Mouse [SteelSeries SteelSeries Rival 310 eSports Mouse] on usb-0000:00:14.0-2.2/input1
Feb 06 23:22:17 balves-work-laptop kernel: input: SteelSeries SteelSeries Rival 310 eSports Mouse Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:1.2/0003:1038:1720.0035/input/input87
Feb 06 23:22:17 balves-work-laptop mtp-probe[10097]: checking bus 1, device 36: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2"
Feb 06 23:22:17 balves-work-laptop mtp-probe[10097]: bus: 1, device: 36 was not an MTP device
Feb 06 23:22:17 balves-work-laptop kernel: input: SteelSeries SteelSeries Rival 310 eSports Mouse Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:1.2/0003:1038:1720.0035/input/input88
Feb 06 23:22:17 balves-work-laptop kernel: hid-generic 0003:1038:1720.0035: input,hidraw3: USB HID v1.11 Keyboard [SteelSeries SteelSeries Rival 310 eSports Mouse] on usb-0000:00:14.0-2.2/input2
Feb 06 23:22:18 balves-work-laptop systemd-logind[519]: Watching system buttons on /dev/input/event22 (SteelSeries SteelSeries Rival 310 eSports Mouse Consumer Control)
Feb 06 23:22:18 balves-work-laptop systemd-logind[519]: Watching system buttons on /dev/input/event21 (SteelSeries SteelSeries Rival 310 eSports Mouse Keyboard)
Feb 06 23:22:18 balves-work-laptop mtp-probe[10120]: checking bus 1, device 36: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2"
Feb 06 23:22:18 balves-work-laptop mtp-probe[10120]: bus: 1, device: 36 was not an MTP device

and the output for plugging it in directly to a usb port on the laptop (which causes it to work):

Feb 06 23:22:43 balves-work-laptop kernel: usb 1-1: new full-speed USB device number 37 using xhci_hcd
Feb 06 23:22:43 balves-work-laptop kernel: usb 1-1: New USB device found, idVendor=1038, idProduct=1720, bcdDevice= 1.21
Feb 06 23:22:43 balves-work-laptop kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 06 23:22:43 balves-work-laptop kernel: usb 1-1: Product: SteelSeries Rival 310 eSports Mouse
Feb 06 23:22:43 balves-work-laptop kernel: usb 1-1: Manufacturer: SteelSeries
Feb 06 23:22:43 balves-work-laptop kernel: usb 1-1: SerialNumber: 000000000000
Feb 06 23:22:43 balves-work-laptop kernel: hid-generic 0003:1038:1720.0036: hiddev0,hidraw1: USB HID v1.11 Device [SteelSeries SteelSeries Rival 310 eSports Mouse] on usb-0000:00:14.0-1/input0
Feb 06 23:22:43 balves-work-laptop kernel: input: SteelSeries SteelSeries Rival 310 eSports Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:1038:1720.0037/input/input89
Feb 06 23:22:43 balves-work-laptop kernel: hid-generic 0003:1038:1720.0037: input,hidraw2: USB HID v1.11 Mouse [SteelSeries SteelSeries Rival 310 eSports Mouse] on usb-0000:00:14.0-1/input1
Feb 06 23:22:43 balves-work-laptop kernel: input: SteelSeries SteelSeries Rival 310 eSports Mouse Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2/0003:1038:1720.0038/input/input90
Feb 06 23:22:43 balves-work-laptop mtp-probe[10160]: checking bus 1, device 37: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
Feb 06 23:22:43 balves-work-laptop mtp-probe[10160]: bus: 1, device: 37 was not an MTP device
Feb 06 23:22:43 balves-work-laptop kernel: input: SteelSeries SteelSeries Rival 310 eSports Mouse Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2/0003:1038:1720.0038/input/input91
Feb 06 23:22:43 balves-work-laptop kernel: hid-generic 0003:1038:1720.0038: input,hidraw3: USB HID v1.11 Keyboard [SteelSeries SteelSeries Rival 310 eSports Mouse] on usb-0000:00:14.0-1/input2
Feb 06 23:22:43 balves-work-laptop systemd-logind[519]: Watching system buttons on /dev/input/event21 (SteelSeries SteelSeries Rival 310 eSports Mouse Keyboard)
Feb 06 23:22:43 balves-work-laptop systemd-logind[519]: Watching system buttons on /dev/input/event22 (SteelSeries SteelSeries Rival 310 eSports Mouse Consumer Control)
Feb 06 23:22:43 balves-work-laptop mtp-probe[10183]: checking bus 1, device 37: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
Feb 06 23:22:43 balves-work-laptop mtp-probe[10183]: bus: 1, device: 37 was not an MTP device










The output is essentially identical. I'm so confused.  Again, this is a hub i've had for a long time that worked completely fine before the most recent update.  Any suggestions about things to try would be appreciated.  Only thing I can think of is usb 2.0 hub in usb 3.0 port and some (new) incompatibility around that?

Last edited by Fryguy (2020-02-11 19:25:56)

Offline

#2 2020-02-07 05:04:53

Fryguy
Member
Registered: 2008-04-15
Posts: 13

Re: [SOLVED] All devices connected to usb hub stopped working after update

Here is the output when I connect the hub:

Feb 07 00:03:50 balves-work-laptop kernel: usb 1-2: new high-speed USB device number 12 using xhci_hcd
Feb 07 00:03:50 balves-work-laptop kernel: usb 1-2: New USB device found, idVendor=1a40, idProduct=0201, bcdDevice= 1.00
Feb 07 00:03:50 balves-work-laptop kernel: usb 1-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Feb 07 00:03:50 balves-work-laptop kernel: usb 1-2: Product: USB 2.0 Hub [MTT]
Feb 07 00:03:50 balves-work-laptop kernel: hub 1-2:1.0: USB hub found
Feb 07 00:03:50 balves-work-laptop kernel: hub 1-2:1.0: 7 ports detected

Last edited by Fryguy (2020-02-07 15:15:02)

Offline

#3 2020-02-07 05:11:17

Fryguy
Member
Registered: 2008-04-15
Posts: 13

Re: [SOLVED] All devices connected to usb hub stopped working after update

And here are the packages that were upgraded when this happened:

[2020-02-06T22:00:07-0500] [ALPM] upgraded iana-etc (20191231-1 -> 20200117-1)
[2020-02-06T22:00:07-0500] [ALPM] upgraded libutil-linux (2.35-1 -> 2.35.1-1)
[2020-02-06T22:00:07-0500] [ALPM] upgraded krb5 (1.17-2 -> 1.17.1-1)
[2020-02-06T22:00:08-0500] [ALPM] upgraded python-botocore (1.14.9-1 -> 1.14.11-1)
[2020-02-06T22:00:08-0500] [ALPM] upgraded aws-cli (1.17.9-1 -> 1.17.11-1)
[2020-02-06T22:00:08-0500] [ALPM] upgraded systemd-libs (244.1-1 -> 244.2-1)
[2020-02-06T22:00:08-0500] [ALPM] upgraded cryptsetup (2.2.2-1 -> 2.3.0-1)
[2020-02-06T22:00:08-0500] [ALPM] upgraded shadow (4.8-1 -> 4.8.1-1)
[2020-02-06T22:00:08-0500] [ALPM] upgraded util-linux (2.35-1 -> 2.35.1-1)
[2020-02-06T22:00:08-0500] [ALPM] upgraded systemd (244.1-1 -> 244.2-1)
[2020-02-06T22:00:09-0500] [ALPM] upgraded linux (5.4.15.arch1-1 -> 5.5.2.arch1-1)
[2020-02-06T22:00:09-0500] [ALPM] upgraded bbswitch (0.8-283 -> 0.8-287)
[2020-02-06T22:00:09-0500] [ALPM] upgraded bison (3.5-1 -> 3.5.1-1)
[2020-02-06T22:00:09-0500] [ALPM] upgraded boost-libs (1.71.0-4 -> 1.72.0-1)
[2020-02-06T22:00:09-0500] [ALPM] upgraded sqlite (3.30.1-2 -> 3.31.1-1)
[2020-02-06T22:00:09-0500] [ALPM] upgraded libtasn1 (4.15.0-1 -> 4.16.0-1)
[2020-02-06T22:00:09-0500] [ALPM] upgraded p11-kit (0.23.19-2 -> 0.23.20-2)
[2020-02-06T22:00:09-0500] [ALPM] upgraded gnutls (3.6.11.1-1 -> 3.6.12-1)
[2020-02-06T22:00:09-0500] [ALPM] upgraded libsecret (0.20.0-1 -> 0.20.1-1)
[2020-02-06T22:00:09-0500] [ALPM] upgraded buildah (1.13.1-1 -> 1.13.2-1)
[2020-02-06T22:00:09-0500] [ALPM] upgraded ca-certificates-mozilla (3.49.2-2 -> 3.49.2-3)
[2020-02-06T22:00:09-0500] [ALPM] upgraded nspr (4.24-1 -> 4.25-1)
[2020-02-06T22:00:09-0500] [ALPM] upgraded nss (3.49.2-2 -> 3.49.2-3)
[2020-02-06T22:00:09-0500] [ALPM] upgraded ceph-libs (14.2.6-1 -> 14.2.7-1)
[2020-02-06T22:00:09-0500] [ALPM] upgraded dhcpcd (8.1.5-1 -> 8.1.6-1)
[2020-02-06T22:00:09-0500] [ALPM] upgraded python-docker (4.1.0-3 -> 4.2.0-1)
[2020-02-06T22:00:09-0500] [ALPM] upgraded docker-compose (1.25.3-1 -> 1.25.4-1)
[2020-02-06T22:00:09-0500] [ALPM] upgraded file (5.38-1 -> 5.38-3)
[2020-02-06T22:00:09-0500] [ALPM] upgraded mtdev (1.1.5-2 -> 1.1.6-1)
[2020-02-06T22:00:09-0500] [ALPM] upgraded xkeyboard-config (2.28-1 -> 2.29-1)
[2020-02-06T22:00:10-0500] [ALPM] upgraded nvidia-utils (440.44-3 -> 440.59-1)
[2020-02-06T22:00:10-0500] [ALPM-SCRIPTLET] If you run into trouble with CUDA not being available, run nvidia-modprobe first.
[2020-02-06T22:00:10-0500] [ALPM] upgraded mesa (19.3.2-2 -> 19.3.3-1)
[2020-02-06T22:00:10-0500] [ALPM] upgraded libgusb (0.3.2-2 -> 0.3.3-1)
[2020-02-06T22:00:10-0500] [ALPM] upgraded girara (0.3.3-1 -> 0.3.4-1)
[2020-02-06T22:00:10-0500] [ALPM] upgraded gn (0.1576.81ee1967-1 -> 0.1634.ad9e442d-1)
[2020-02-06T22:00:10-0500] [ALPM] upgraded imagemagick (7.0.9.20-1 -> 7.0.9.21-1)
[2020-02-06T22:00:10-0500] [ALPM] upgraded lib32-mesa (19.3.2-1 -> 19.3.3-1)
[2020-02-06T22:00:10-0500] [ALPM] upgraded lib32-systemd (244.1-1 -> 244.2-1)
[2020-02-06T22:00:10-0500] [ALPM] upgraded lib32-util-linux (2.35-1 -> 2.35.1-1)
[2020-02-06T22:00:10-0500] [ALPM] upgraded libmpdclient (2.17-1 -> 2.18-1)
[2020-02-06T22:00:10-0500] [ALPM] upgraded libmtp (1.1.16-1 -> 1.1.17-1)
[2020-02-06T22:00:10-0500] [ALPM] upgraded libnm (1.22.4-1 -> 1.22.6-1)
[2020-02-06T22:00:10-0500] [ALPM] upgraded libsynctex (2019.51075-5 -> 2019.51075-6)
[2020-02-06T22:00:10-0500] [ALPM] upgraded libxnvctrl (440.44-1 -> 440.59-1)
[2020-02-06T22:00:11-0500] [ALPM] upgraded linux-firmware (20191220.6871bff-1 -> 20200122.1eb2408-1)
[2020-02-06T22:00:12-0500] [ALPM] upgraded linux-headers (5.4.15.arch1-1 -> 5.5.2.arch1-1)
[2020-02-06T22:00:12-0500] [ALPM] upgraded make (4.2.1-4 -> 4.3-1)
[2020-02-06T22:00:12-0500] [ALPM] upgraded mariadb-libs (10.4.11-1 -> 10.4.12-1)
[2020-02-06T22:00:12-0500] [ALPM] upgraded ncmpcpp (0.8.2-10 -> 0.8.2-11)
[2020-02-06T22:00:12-0500] [ALPM] upgraded ninja (1.9.0-2 -> 1.10.0-1)
[2020-02-06T22:00:12-0500] [ALPM] upgraded nvidia (440.44-15 -> 440.59-3)
[2020-02-06T22:00:12-0500] [ALPM] upgraded nvidia-settings (440.44-1 -> 440.59-1)
[2020-02-06T22:00:12-0500] [ALPM] upgraded openal (1.20.1-1 -> 1.20.1-2)
[2020-02-06T22:00:13-0500] [ALPM] upgraded openexr (2.4.0-6 -> 2.4.0-7)
[2020-02-06T22:00:13-0500] [ALPM] upgraded openresolv (3.9.2-2 -> 3.10.0-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded opusfile (0.11-1 -> 0.11-2)
[2020-02-06T22:00:13-0500] [ALPM] upgraded packer (1.5.1-1 -> 1.5.1-2)
[2020-02-06T22:00:13-0500] [ALPM] upgraded poppler (0.84.0-1 -> 0.85.0-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded poppler-glib (0.84.0-1 -> 0.85.0-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded protobuf (3.11.2-1 -> 3.11.3-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded python-boto3 (1.11.9-1 -> 1.11.11-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded python-dbus-common (1.2.14-1 -> 1.2.16-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded python-dbus (1.2.14-1 -> 1.2.16-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded python-jinja (2.11.0-1 -> 2.11.1-1)
[2020-02-06T22:00:13-0500] [ALPM] installed python-pyqt5-sip (12.7.1-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded qt5-base (5.14.0-3 -> 5.14.1-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded python-pyqt5 (5.14.1-1 -> 5.14.1-2)
[2020-02-06T22:00:13-0500] [ALPM] upgraded python-ruamel-yaml (0.16.6-1 -> 0.16.7-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded python-wheel (0.34.1-1 -> 0.34.2-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded qt5-declarative (5.14.0-3 -> 5.14.1-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded qt5-imageformats (5.14.0-1 -> 5.14.1-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded qt5-location (5.14.0-1 -> 5.14.1-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded qt5-multimedia (5.14.0-1 -> 5.14.1-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded qt5-sensors (5.14.0-1 -> 5.14.1-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded qt5-svg (5.14.0-1 -> 5.14.1-1)
[2020-02-06T22:00:13-0500] [ALPM] upgraded qt5-tools (5.14.0-2 -> 5.14.1-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded qt5-wayland (5.14.0-3 -> 5.14.1-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded qt5-webchannel (5.14.0-1 -> 5.14.1-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded qt5-webkit (5.212.0alpha3-8 -> 5.212.0alpha3-9)
[2020-02-06T22:00:14-0500] [ALPM] upgraded qt5-x11extras (5.14.0-1 -> 5.14.1-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded qt5-xmlpatterns (5.14.0-1 -> 5.14.1-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded rust (1:1.40.0-1 -> 1:1.41.0-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded semver (7.1.1-1 -> 7.1.2-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded sudo (1.8.30-1 -> 1.8.31-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded systemd-sysvcompat (244.1-1 -> 244.2-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded vulkan-icd-loader (1.2.131-1 -> 1.2.132-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded telegram-desktop (1.9.8-1 -> 1.9.9-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded uglify-js (3.7.6-1 -> 3.7.7-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded unrar (1:5.8.5-1 -> 1:5.9.1-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded virtualbox-host-modules-arch (6.1.2-5 -> 6.1.2-9)
[2020-02-06T22:00:14-0500] [ALPM] upgraded vulkan-intel (19.3.2-2 -> 19.3.3-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded xterm (352-1 -> 353-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded yarn (1.21.1-1 -> 1.22.0-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded zathura (0.4.4-1 -> 0.4.5-1)
[2020-02-06T22:00:14-0500] [ALPM] upgraded zathura-pdf-poppler (0.2.9-1 -> 0.3.0-1)

I've already tried downgrading my kernel back to 5.4.15 and that didn't help.  I also downgraded linux-firmware and linux-headers.  I'm running out of ideas for what package might have even caused this.

Last edited by Fryguy (2020-02-07 15:15:17)

Offline

#4 2020-02-07 09:10:58

sabroad
Member
Registered: 2015-05-24
Posts: 111

Re: [SOLVED] All devices connected to usb hub stopped working after update

What's the multi-seat configuration when plugged into the hub?

loginctl list-seats
loginctl seat-status seat0

--
saint_abroad

Offline

#5 2020-02-07 09:13:43

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 8,713

Re: [SOLVED] All devices connected to usb hub stopped working after update

Please wrap outputs in [ code ] [ /code ] tags without the spaces and edit and append to the original post rather than making a new one if no one has answered in between (that said it's good that you are actively trying to find things that might relate to it on  your own.

I'd also have suggested the kernel at first glance, but maybe you are just unlucky and it's a hardware issue, can you test the hub on some other machine? FWIW what's your output for

sudo lsusb -t

Offline

#6 2020-02-07 15:16:23

Fryguy
Member
Registered: 2008-04-15
Posts: 13

Re: [SOLVED] All devices connected to usb hub stopped working after update

I tried the hub on another machine, and as a reminder the keyboard works when connected to the hub when I'm in a TTY, so it doesn't appear to be a hardware problem, but some sort of xorg driver problem?  I don't see any suspect packages though that would cause something like that.

Offline

#7 2020-02-08 00:39:41

Fryguy
Member
Registered: 2008-04-15
Posts: 13

Re: [SOLVED] All devices connected to usb hub stopped working after update

loginctl list-seats specifies only seat0 and no other seats when things are connected to the hub.  And the devices connected to the hub don't appear in `seat-status`

Here is the output of `lsusb -t`

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
    |__ Port 1: Dev 16, If 0, Class=Hub, Driver=hub/7p, 480M
        |__ Port 1: Dev 20, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 1: Dev 20, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 1: Dev 20, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 2: Dev 21, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 2: Dev 21, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 2: Dev 17, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 2: Dev 17, If 3, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 2: Dev 17, If 1, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 8: Dev 5, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 8: Dev 5, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 9: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M
    |__ Port 11: Dev 7, If 0, Class=Chip/SmartCard, Driver=, 12M
    |__ Port 14: Dev 8, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 14: Dev 8, If 1, Class=Wireless, Driver=btusb, 12M

From a bit of experimentation (unplugging and plugging), Bus 01 Port 1 (line 2) is the usb hub, and the children of that are my mouse and keyboard.

So, it shows up in lsusb, but not seat status?

I brought the machine to my office today -- where my hardware is connected via a different hub -- and that hub behaved normally and nothing adverse happened.  Everything worked as expected.


Looking at 71-seat.rules, it appears as though my hub at home matches this entry:

# 'Plugable UD-160' USB hub, sound, network, graphics adapter
SUBSYSTEM=="usb", ATTR{idVendor}=="2230", ATTR{idProduct}=="000[13]", ENV{ID_AUTOSEAT}="1"

Which isn't right.  My hub is a normal 7-port hub, not a Plugable device, and it certainly doesn't have sound, network, or graphics.  How can I mask/ignore this rule?

Last edited by Fryguy (2020-02-08 01:04:32)

Offline

#8 2020-02-08 06:27:06

Ropid
Member
Registered: 2015-03-09
Posts: 687

Re: [SOLVED] All devices connected to usb hub stopped working after update

Are there interesting messages in the Xorg log file? You could experiment by disconnecting and connecting things while Xorg is already running, and see what messages Xorg logs while you connect stuff.

Offline

#9 2020-02-08 07:42:51

Riyadth
Member
From: Seattle, WA
Registered: 2020-02-08
Posts: 1
Website

Re: [SOLVED] All devices connected to usb hub stopped working after update

I just updated Arch and have a very similar problem, but with slightly different symptoms. My trackball would not work after rebooting until I moved it from the hub I normally use to a port on the computer. However, my keyboard was working fine, and my audio DAC is also working fine through the external hub.

The thing that caught my eye was the output of lsusb when I plugged in a different (HP) mouse to test. With it plugged in to the hub (and non-functional), the output of lsusb identifies the mouse as a hub:

$ lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 013: ID 046d:c404 Logitech, Inc. TrackMan Wheel
Bus 002 Device 014: ID 04b4:0101 Cypress Semiconductor Corp. Keyboard/Hub
Bus 002 Device 012: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 002 Device 011: ID 0409:0059 NEC Corp. HighSpeed Hub
Bus 002 Device 004: ID 08bb:2704 Texas Instruments PCM2704 16-bit stereo audio DAC
Bus 002 Device 019: ID 03f0:2003 HP, Inc USB 2.0 Hub [MTT]
Bus 002 Device 002: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

But with the mouse plugged in to the computer, it is correctly identified (and works fine):

$ lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 013: ID 046d:c404 Logitech, Inc. TrackMan Wheel
Bus 002 Device 014: ID 04b4:0101 Cypress Semiconductor Corp. Keyboard/Hub
Bus 002 Device 012: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 002 Device 011: ID 0409:0059 NEC Corp. HighSpeed Hub
Bus 002 Device 004: ID 08bb:2704 Texas Instruments PCM2704 16-bit stereo audio DAC
Bus 002 Device 002: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub
Bus 002 Device 020: ID 03f0:2003 HP, Inc HP f2100a Optical USB Travel Mouse
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

What really caught my attention is the mention above of the Plugable USB hub. My hub is a 7-port Plugable USB 2.0 hub.

And now, after switching the keyboard and trackball back to the original hub, neither keyboard nor mouse are working.

Offline

#10 2020-02-08 11:06:49

hpfmn
Member
Registered: 2017-02-10
Posts: 3

Re: [SOLVED] All devices connected to usb hub stopped working after update

Same issue here. Can reproduce on desktop system and laptop system. Keyboard and mouse connected to a USB-Hub do not work in Xorg but in BIOS/getty/etc.

Offline

#11 2020-02-08 11:09:30

hpfmn
Member
Registered: 2017-02-10
Posts: 3

Re: [SOLVED] All devices connected to usb hub stopped working after update

Ropid wrote:

Are there interesting messages in the Xorg log file? You could experiment by disconnecting and connecting things while Xorg is already running, and see what messages Xorg logs while you connect stuff.

On my machine nothing happens when connecting the keyboard to the USB Hub. Nothing as I'm doing a tail -f on /var/log/X11/Xorg.0.log and when I plug the keyboard into the hub nothing new gets displayed.


But when connection to another free USB Port it is something like this is displayed:

[  2019.744] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: always reports core events
[  2019.744] (**) Option "Device" "/dev/input/event2"
[  2019.744] (**) Option "_source" "server/udev"
[  2019.745] (II) event2  - Lenovo ThinkPad Compact USB Keyboard with TrackPoint: is tagged by udev as: Keyboard
[  2019.745] (II) event2  - Lenovo ThinkPad Compact USB Keyboard with TrackPoint: device is a keyboard
[  2019.745] (II) event2  - Lenovo ThinkPad Compact USB Keyboard with TrackPoint: device removed
[  2019.745] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:17EF:6047.0009/input/input27/event2"
[  2019.745] (II) XINPUT: Adding extended input device "Lenovo ThinkPad Compact USB Keyboard with TrackPoint" (type: KEYBOARD, id 8)
[  2019.745] (**) Option "xkb_model" "pc105"
[  2019.745] (**) Option "xkb_layout" "us"
[  2019.745] (**) Option "xkb_variant" "mac"
[  2019.745] (**) Option "xkb_options" "lv3:caps_switch"
[  2019.746] (II) event2  - Lenovo ThinkPad Compact USB Keyboard with TrackPoint: is tagged by udev as: Keyboard
[  2019.746] (II) event2  - Lenovo ThinkPad Compact USB Keyboard with TrackPoint: device is a keyboard
[  2019.753] (II) config/udev: Adding input device Lenovo ThinkPad Compact USB Keyboard with TrackPoint (/dev/input/event3)
[  2019.753] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "evdev pointer catchall"
[  2019.753] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "evdev keyboard catchall"
[  2019.753] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "libinput pointer catchall"
[  2019.753] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "libinput keyboard catchall"
[  2019.753] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "system-keyboard"
[  2019.753] (II) Using input driver 'libinput' for 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint'
[  2019.754] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 49 paused 0
[  2019.754] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: always reports core events
[  2019.754] (**) Option "Device" "/dev/input/event3"
[  2019.754] (**) Option "_source" "server/udev"
[  2019.755] (II) event3  - Lenovo ThinkPad Compact USB Keyboard with TrackPoint: is tagged by udev as: Keyboard Mouse Pointingstick
[  2019.755] (II) event3  - Lenovo ThinkPad Compact USB Keyboard with TrackPoint: is an external pointing stick
[  2019.755] (II) event3  - Lenovo ThinkPad Compact USB Keyboard with TrackPoint: device is a pointer
[  2019.755] (II) event3  - Lenovo ThinkPad Compact USB Keyboard with TrackPoint: device is a keyboard
[  2019.755] (II) event3  - Lenovo ThinkPad Compact USB Keyboard with TrackPoint: device removed
[  2019.755] (II) libinput: Lenovo ThinkPad Compact USB Keyboard with TrackPoint: needs a virtual subdevice
[  2019.755] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:17EF:6047.000A/input/input28/event3"
[  2019.755] (II) XINPUT: Adding extended input device "Lenovo ThinkPad Compact USB Keyboard with TrackPoint" (type: MOUSE, id 9)
[  2019.756] (**) Option "AccelerationScheme" "none"
[  2019.756] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: (accel) selected scheme none/0
[  2019.756] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: (accel) acceleration factor: 2.000
[  2019.756] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: (accel) acceleration threshold: 4
[  2019.757] (II) event3  - Lenovo ThinkPad Compact USB Keyboard with TrackPoint: is tagged by udev as: Keyboard Mouse Pointingstick
[  2019.757] (II) event3  - Lenovo ThinkPad Compact USB Keyboard with TrackPoint: is an external pointing stick
[  2019.757] (II) event3  - Lenovo ThinkPad Compact USB Keyboard with TrackPoint: device is a pointer
[  2019.757] (II) event3  - Lenovo ThinkPad Compact USB Keyboard with TrackPoint: device is a keyboard
[  2019.758] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "evdev pointer catchall"
[  2019.758] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "evdev keyboard catchall"
[  2019.758] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "libinput pointer catchall"
[  2019.758] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "libinput keyboard catchall"
[  2019.758] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: Applying InputClass "system-keyboard"
[  2019.758] (II) Using input driver 'libinput' for 'Lenovo ThinkPad Compact USB Keyboard with TrackPoint'
[  2019.758] (II) systemd-logind: returning pre-existing fd for /dev/input/event3 13:67
[  2019.758] (**) Lenovo ThinkPad Compact USB Keyboard with TrackPoint: always reports core events
[  2019.758] (**) Option "Device" "/dev/input/event3"
[  2019.758] (**) Option "_source" "_driver/libinput"
[  2019.758] (II) libinput: Lenovo ThinkPad Compact USB Keyboard with TrackPoint: is a virtual subdevice
[  2019.758] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:17EF:6047.000A/input/input28/event3"
[  2019.758] (II) XINPUT: Adding extended input device "Lenovo ThinkPad Compact USB Keyboard with TrackPoint" (type: KEYBOARD, id 11)
[  2019.758] (**) Option "xkb_model" "pc105"
[  2019.758] (**) Option "xkb_layout" "us"
[  2019.758] (**) Option "xkb_variant" "mac"
[  2019.758] (**) Option "xkb_options" "lv3:caps_switch"

I already downgraded xkeyboard-config from 2.29-1 to 2.28-1 but it didn't change anything.


Downgrading systemd 244.2-1 -> 244.1-1 fixes the issue. I'll file an issue.

There seems to be an upstream issue.

Last edited by hpfmn (2020-02-08 11:41:01)

Offline

#12 2020-02-10 08:26:51

Mr.Smith1974
Member
Registered: 2013-04-13
Posts: 16

Re: [SOLVED] All devices connected to usb hub stopped working after update

Same issue here.

Offline

#13 2020-02-10 14:55:04

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 8,713

Re: [SOLVED] All devices connected to usb hub stopped working after update

Update your systems, systemd 244.2-2 should contain the fix for this.

Offline

Board footer

Powered by FluxBB