Laptop integrated USB keyboard not working when sys-usb is running

harrim4n · May 27, 2024, 10:24pm

I tried setting up a split sys-usb and sys-net config on Qubes 4.2 on my (Framework 16) laptop - in my mind this was already set up like this after the initial install.
I changed the setup due to some other issues and then tried to return to the split setup, but for some reason the integrated (attached via USB) keyboard stops working as soon as I get to the login screen. The LUKS password prompt works fine.
I can only sign in by disabling the autostart with qubes.skip_autostart - as soon as I start the sys-usb qube, it stops working again. Except for “inside” the USB qube.

Thinks I’ve tried / checked:

recreating / resetting the config with sudo qubesctl state.sls qvm.usb-keyboard
any combination of existence / absence of usbcore.authorized_default=0 and rd.qubes.hide_all_usb
checking the config in “Qubes Global Config” / /etc/qubes/policy.d/50-config-input.policy (the files mentioned in the documentation in /etc/qubes-rpc/ seem to be deprecated in Qubes 4.2+). Keyboard is set to “enabled” / “allow”.
considered attaching the entire USB controller pci device to dom0. However, since several other external ports also attach to this controller, this would defeat the purpose of the sys-usb qube entirely.

I’m kind of lost, especially since a lot of threads / docu I found seems to be for either Qubes 4.1 or earlier, is talking about external USB devices on desktop hosts attached to a single controller, suggests setting the correct policy (in the new or old policy files) or assumes that the problem is already present when trying to enter the LUKS password.
Any pointers?

apparatus · May 28, 2024, 4:51am

Check the USB keyboard policy for sys-usb in Qubes Global Config → USB Devices tab.

harrim4n · May 28, 2024, 6:01am

It’s set to enabled.

apparatus · May 28, 2024, 6:30am

Check the journalctl in dom0, maybe there is some error in policy files and it’s causing this issue?
Run this command in dom0:

journalctl -f -n0

Start sys-usb.
Check the journalctl output.
You can write the output to file like this to check the file later:

journalctl -f -n0 > log

If you’re unable to get the keyboard working in dom0 after starting sys-usb.

harrim4n · May 28, 2024, 5:42pm

Nothing that I’m able to spot…

May 28 19:29:07 dom0 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
May 28 19:29:07 dom0 kernel: audit: type=1131 audit(1716917347.070:525): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 28 19:29:07 dom0 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 28 19:29:07 dom0 audit: BPF prog-id=74 op=UNLOAD
May 28 19:29:07 dom0 audit: BPF prog-id=73 op=UNLOAD
May 28 19:29:07 dom0 audit: BPF prog-id=72 op=UNLOAD
May 28 19:29:07 dom0 kernel: audit: type=1334 audit(1716917347.104:526): prog-id=74 op=UNLOAD
May 28 19:29:07 dom0 kernel: audit: type=1334 audit(1716917347.104:527): prog-id=73 op=UNLOAD
May 28 19:29:07 dom0 kernel: audit: type=1334 audit(1716917347.104:528): prog-id=72 op=UNLOAD
May 28 19:29:22 dom0 qubesd[2957]: vm.sys-usb: Starting sys-usb
May 28 19:29:22 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb2/2-2" device_rule=616C6C6F7720696420303565333A30363235206E616D652022555342332E322048756222207669612D706F72742022322D322220776974682D696E746572666163652030393A30303A303020776974682D636F6E6E6563742D74797065202268617264776972656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:22 dom0 kernel: xhci_hcd 0000:c1:00.3: remove, state 4
May 28 19:29:22 dom0 kernel: usb usb2: USB disconnect, device number 1
May 28 19:29:22 dom0 kernel: usb 2-2: USB disconnect, device number 2
May 28 19:29:22 dom0 kernel: audit: type=1137 audit(1716917362.591:529): pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb2/2-2" device_rule=616C6C6F7720696420303565333A30363235206E616D652022555342332E322048756222207669612D706F72742022322D322220776974682D696E746572666163652030393A30303A303020776974682D636F6E6E6563742D74797065202268617264776972656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:22 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb2" device_rule=616C6C6F7720696420316436623A30303033206E616D6520227848434920486F737420436F6E74726F6C6C657222207669612D706F72742022757362322220776974682D696E746572666163652030393A30303A303020776974682D636F6E6E6563742D74797065202222 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:22 dom0 kernel: xhci_hcd 0000:c1:00.3: USB bus 2 deregistered
May 28 19:29:22 dom0 kernel: audit: type=1137 audit(1716917362.595:530): pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb2" device_rule=616C6C6F7720696420316436623A30303033206E616D6520227848434920486F737420436F6E74726F6C6C657222207669612D706F72742022757362322220776974682D696E746572666163652030393A30303A303020776974682D636F6E6E6563742D74797065202222 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:22 dom0 kernel: xhci_hcd 0000:c1:00.3: remove, state 1
May 28 19:29:22 dom0 kernel: usb usb1: USB disconnect, device number 1
May 28 19:29:22 dom0 kernel: usb 1-1: USB disconnect, device number 2
May 28 19:29:22 dom0 kernel: usb 1-2: USB disconnect, device number 3
May 28 19:29:22 dom0 kernel: audit: type=1137 audit(1716917362.596:531): pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-1" device_rule=626C6F636B20696420333261633A30303033206E616D652022446973706C6179506F727420457870616E73696F6E204361726422207669612D706F72742022312D312220776974682D696E74657266616365207B2031313A30303A30302030333A30303A3030207D20776974682D636F6E6E6563742D747970652022686F74706C756722 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:22 dom0 kernel: audit: type=1137 audit(1716917362.596:532): pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-2" device_rule=616C6C6F7720696420303565333A30363130206E616D652022555342322E312048756222207669612D706F72742022312D322220776974682D696E74657266616365207B2030393A30303A30312030393A30303A3032207D20776974682D636F6E6E6563742D74797065202268617264776972656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:22 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-1" device_rule=626C6F636B20696420333261633A30303033206E616D652022446973706C6179506F727420457870616E73696F6E204361726422207669612D706F72742022312D312220776974682D696E74657266616365207B2031313A30303A30302030333A30303A3030207D20776974682D636F6E6E6563742D747970652022686F74706C756722 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:22 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-2" device_rule=616C6C6F7720696420303565333A30363130206E616D652022555342322E312048756222207669612D706F72742022312D322220776974682D696E74657266616365207B2030393A30303A30312030393A30303A3032207D20776974682D636F6E6E6563742D74797065202268617264776972656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:22 dom0 kernel: usb 1-3: USB disconnect, device number 4
May 28 19:29:22 dom0 kernel: usb 1-3.2: USB disconnect, device number 7
May 28 19:29:23 dom0 kernel: audit: type=1137 audit(1716917363.072:533): pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-3/1-3.2" device_rule=616C6C6F7720696420333261633A30303134206E616D6520224C6170746F70203136204E756D706164204D6F64756C6522207669612D706F72742022312D332E322220776974682D696E74657266616365207B2030333A30313A30312030333A30303A30302030333A30303A30302030333A30303A3030207D20776974682D636F6E6E6563742D7479706520226E6F74207573656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-3/1-3.2" device_rule=616C6C6F7720696420333261633A30303134206E616D6520224C6170746F70203136204E756D706164204D6F64756C6522207669612D706F72742022312D332E322220776974682D696E74657266616365207B2030333A30313A30312030333A30303A30302030333A30303A30302030333A30303A3030207D20776974682D636F6E6E6563742D7479706520226E6F74207573656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-3" device_rule=616C6C6F7720696420303565333A30363130206E616D652022555342322E302048756222207669612D706F72742022312D332220776974682D696E74657266616365207B2030393A30303A30312030393A30303A3032207D20776974682D636F6E6E6563742D74797065202268617264776972656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 kernel: audit: type=1137 audit(1716917363.092:534): pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-3" device_rule=616C6C6F7720696420303565333A30363130206E616D652022555342322E302048756222207669612D706F72742022312D332220776974682D696E74657266616365207B2030393A30303A30312030393A30303A3032207D20776974682D636F6E6E6563742D74797065202268617264776972656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 kernel: usb 1-4: USB disconnect, device number 5
May 28 19:29:23 dom0 kernel: usb 1-4.1: USB disconnect, device number 8
May 28 19:29:23 dom0 kernel: usb 1-4.2: USB disconnect, device number 9
May 28 19:29:23 dom0 kernel: audit: type=1137 audit(1716917363.124:535): pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-4/1-4.1" device_rule=626C6F636B20696420323763363A36303963206E616D652022476F6F64697820555342322E30204D49534322207669612D706F72742022312D342E312220776974682D696E746572666163652066663A30303A303020776974682D636F6E6E6563742D7479706520226E6F74207573656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-4/1-4.1" device_rule=626C6F636B20696420323763363A36303963206E616D652022476F6F64697820555342322E30204D49534322207669612D706F72742022312D342E312220776974682D696E746572666163652066663A30303A303020776974682D636F6E6E6563742D7479706520226E6F74207573656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-4/1-4.2" device_rule=616C6C6F7720696420333261633A30303138206E616D6520224C6170746F70203136204B6579626F617264204D6F64756C65202D2049534F22207669612D706F72742022312D342E322220776974682D696E74657266616365207B2030333A30313A30312030333A30303A30302030333A30303A30302030333A30303A3030207D20776974682D636F6E6E6563742D7479706520226E6F74207573656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 kernel: audit: type=1137 audit(1716917363.571:536): pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-4/1-4.2" device_rule=616C6C6F7720696420333261633A30303138206E616D6520224C6170746F70203136204B6579626F617264204D6F64756C65202D2049534F22207669612D706F72742022312D342E322220776974682D696E74657266616365207B2030333A30313A30312030333A30303A30302030333A30303A30302030333A30303A3030207D20776974682D636F6E6E6563742D7479706520226E6F74207573656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-4" device_rule=616C6C6F7720696420303565333A30363130206E616D652022555342322E302048756222207669612D706F72742022312D342220776974682D696E74657266616365207B2030393A30303A30312030393A30303A3032207D20776974682D636F6E6E6563742D74797065202268617264776972656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 kernel: audit: type=1137 audit(1716917363.604:537): pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-4" device_rule=616C6C6F7720696420303565333A30363130206E616D652022555342322E302048756222207669612D706F72742022312D342220776974682D696E74657266616365207B2030393A30303A30312030393A30303A3032207D20776974682D636F6E6E6563742D74797065202268617264776972656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 kernel: usb 1-5: USB disconnect, device number 6
May 28 19:29:23 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-5" device_rule=626C6F636B20696420306538643A65363136206E616D652022576972656C6573735F44657669636522207669612D706F72742022312D352220776974682D696E74657266616365207B2065303A30313A30312065303A30313A30312065303A30313A30312065303A30313A30312065303A30313A30312065303A30313A30312065303A30313A30312065303A30313A30312065303A30313A30312065303A30313A3031207D20776974682D636F6E6E6563742D74797065202268617264776972656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1" device_rule=616C6C6F7720696420316436623A30303032206E616D6520227848434920486F737420436F6E74726F6C6C657222207669612D706F72742022757362312220776974682D696E746572666163652030393A30303A303020776974682D636F6E6E6563742D74797065202222 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 kernel: audit: type=1137 audit(1716917363.636:538): pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-5" device_rule=626C6F636B20696420306538643A65363136206E616D652022576972656C6573735F44657669636522207669612D706F72742022312D352220776974682D696E74657266616365207B2065303A30313A30312065303A30313A30312065303A30313A30312065303A30313A30312065303A30313A30312065303A30313A30312065303A30313A30312065303A30313A30312065303A30313A30312065303A30313A3031207D20776974682D636F6E6E6563742D74797065202268617264776972656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 kernel: xhci_hcd 0000:c1:00.3: USB bus 1 deregistered
May 28 19:29:23 dom0 kernel: pciback 0000:c1:00.3: xen_pciback: seizing device
May 28 19:29:23 dom0 kernel: xen: registering gsi 37 triggering 0 polarity 1
May 28 19:29:23 dom0 kernel: Already setup the GSI :37
May 28 19:29:23 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.4/usb4" device_rule=616C6C6F7720696420316436623A30303033206E616D6520227848434920486F737420436F6E74726F6C6C657222207669612D706F72742022757362342220776974682D696E746572666163652030393A30303A303020776974682D636F6E6E6563742D74797065202222 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 kernel: xhci_hcd 0000:c1:00.4: remove, state 4
May 28 19:29:23 dom0 kernel: usb usb4: USB disconnect, device number 1
May 28 19:29:23 dom0 kernel: xhci_hcd 0000:c1:00.4: USB bus 4 deregistered
May 28 19:29:23 dom0 kernel: xhci_hcd 0000:c1:00.4: remove, state 1
May 28 19:29:23 dom0 kernel: usb usb3: USB disconnect, device number 1
May 28 19:29:23 dom0 kernel: usb 3-1: USB disconnect, device number 2
May 28 19:29:23 dom0 kernel: xhci_hcd 0000:c1:00.4: USB bus 3 deregistered
May 28 19:29:23 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.4/usb3/3-1" device_rule=626C6F636B20696420306264613A35363334206E616D6520224C6170746F702043616D65726122207669612D706F72742022332D312220776974682D696E74657266616365207B2030653A30313A30302030653A30323A30302030653A30323A30302030653A30323A30302030653A30323A30302030653A30323A30302030653A30323A30302030653A30323A30302030653A30323A3030207D20776974682D636F6E6E6563742D74797065202268617264776972656422 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.1/0000:c1:00.4/usb3" device_rule=616C6C6F7720696420316436623A30303032206E616D6520227848434920486F737420436F6E74726F6C6C657222207669612D706F72742022757362332220776974682D696E746572666163652030393A30303A303020776974682D636F6E6E6563742D74797065202222 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 kernel: pciback 0000:c1:00.4: xen_pciback: seizing device
May 28 19:29:23 dom0 kernel: xen: registering gsi 38 triggering 0 polarity 1
May 28 19:29:23 dom0 kernel: Already setup the GSI :38
May 28 19:29:23 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb6" device_rule=616C6C6F7720696420316436623A30303033206E616D6520227848434920486F737420436F6E74726F6C6C657222207669612D706F72742022757362362220776974682D696E746572666163652030393A30303A303020776974682D636F6E6E6563742D74797065202222 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 kernel: xhci_hcd 0000:c3:00.3: remove, state 4
May 28 19:29:23 dom0 kernel: usb usb6: USB disconnect, device number 1
May 28 19:29:23 dom0 kernel: xhci_hcd 0000:c3:00.3: USB bus 6 deregistered
May 28 19:29:23 dom0 kernel: xhci_hcd 0000:c3:00.3: remove, state 1
May 28 19:29:23 dom0 kernel: usb usb5: USB disconnect, device number 1
May 28 19:29:23 dom0 kernel: usb 5-1: USB disconnect, device number 2
May 28 19:29:23 dom0 kernel: xhci_hcd 0000:c3:00.3: USB bus 5 deregistered
May 28 19:29:23 dom0 kernel: pciback 0000:c3:00.3: xen_pciback: seizing device
May 28 19:29:23 dom0 kernel: xen: registering gsi 46 triggering 0 polarity 1
May 28 19:29:23 dom0 kernel: Already setup the GSI :46
May 28 19:29:23 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb5/5-1" device_rule=626C6F636B20696420333261633A30303033206E616D652022446973706C6179506F727420457870616E73696F6E204361726422207669612D706F72742022352D312220776974682D696E74657266616365207B2031313A30303A30302030333A30303A3030207D20776974682D636F6E6E6563742D747970652022686F74706C756722 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb5" device_rule=616C6C6F7720696420316436623A30303032206E616D6520227848434920486F737420436F6E74726F6C6C657222207669612D706F72742022757362352220776974682D696E746572666163652030393A30303A303020776974682D636F6E6E6563742D74797065202222 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 kernel: xhci_hcd 0000:c3:00.4: remove, state 4
May 28 19:29:23 dom0 kernel: usb usb8: USB disconnect, device number 1
May 28 19:29:23 dom0 kernel: xhci_hcd 0000:c3:00.4: USB bus 8 deregistered
May 28 19:29:23 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.3/0000:c3:00.4/usb8" device_rule=616C6C6F7720696420316436623A30303033206E616D6520227848434920486F737420436F6E74726F6C6C657222207669612D706F72742022757362382220776974682D696E746572666163652030393A30303A303020776974682D636F6E6E6563742D74797065202222 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 kernel: xhci_hcd 0000:c3:00.4: remove, state 4
May 28 19:29:23 dom0 kernel: usb usb7: USB disconnect, device number 1
May 28 19:29:23 dom0 kernel: xhci_hcd 0000:c3:00.4: USB bus 7 deregistered
May 28 19:29:23 dom0 kernel: pciback 0000:c3:00.4: xen_pciback: seizing device
May 28 19:29:23 dom0 kernel: xen: registering gsi 47 triggering 0 polarity 1
May 28 19:29:23 dom0 kernel: Already setup the GSI :47
May 28 19:29:23 dom0 audit[2930]: USER_DEVICE pid=2930 uid=0 auid=4294967295 ses=4294967295 msg='op="removed-device" device="/devices/pci0000:00/0000:00:08.3/0000:c3:00.4/usb7" device_rule=616C6C6F7720696420316436623A30303032206E616D6520227848434920486F737420436F6E74726F6C6C657222207669612D706F72742022757362372220776974682D696E746572666163652030393A30303A303020776974682D636F6E6E6563742D74797065202222 exe="/usr/sbin/usbguard-daemon" hostname=? addr=? terminal=? res=success'
May 28 19:29:23 dom0 kernel: pciback 0000:c3:00.5: xen_pciback: seizing device
May 28 19:29:23 dom0 kernel: xen: registering gsi 44 triggering 0 polarity 1
May 28 19:29:23 dom0 kernel: Already setup the GSI :44
May 28 19:29:23 dom0 kernel: pciback 0000:c3:00.6: xen_pciback: seizing device
May 28 19:29:23 dom0 kernel: xen: registering gsi 45 triggering 0 polarity 1
May 28 19:29:23 dom0 kernel: Already setup the GSI :45
May 28 19:29:24 dom0 lvm[2177]: No longer monitoring thin pool qubes_dom0-vm--pool-tpool.
May 28 19:29:24 dom0 lvm[2177]: Monitoring thin pool qubes_dom0-vm--pool-tpool.
May 28 19:29:24 dom0 lvm[2177]: No longer monitoring thin pool qubes_dom0-vm--pool-tpool.
May 28 19:29:24 dom0 lvm[2177]: Monitoring thin pool qubes_dom0-vm--pool-tpool.
May 28 19:29:24 dom0 kernel: pciback 0000:c3:00.3: xen_pciback: seizing device
May 28 19:29:24 dom0 kernel: xen: registering gsi 46 triggering 0 polarity 1
May 28 19:29:24 dom0 kernel: Already setup the GSI :46
May 28 19:29:24 dom0 kernel: pciback 0000:c3:00.4: xen_pciback: seizing device
May 28 19:29:24 dom0 kernel: xen: registering gsi 47 triggering 0 polarity 1
May 28 19:29:24 dom0 kernel: Already setup the GSI :47
May 28 19:29:24 dom0 kernel: loop4: detected capacity change from 0 to 1244600
May 28 19:29:25 dom0 kernel: loop5: detected capacity change from 0 to 1244600
May 28 19:29:25 dom0 kernel: pciback 0000:c1:00.3: xen_pciback: vpci: assign to virtual slot 0
May 28 19:29:25 dom0 kernel: pciback 0000:c1:00.3: registering for 6
May 28 19:29:25 dom0 kernel: pciback 0000:c1:00.4: xen_pciback: vpci: assign to virtual slot 0 func 4
May 28 19:29:25 dom0 kernel: pciback 0000:c1:00.4: registering for 6
May 28 19:29:25 dom0 kernel: pciback 0000:c3:00.3: xen_pciback: vpci: assign to virtual slot 1
May 28 19:29:25 dom0 kernel: pciback 0000:c3:00.3: registering for 6
May 28 19:29:25 dom0 kernel: pciback 0000:c3:00.4: xen_pciback: vpci: assign to virtual slot 1 func 4
May 28 19:29:25 dom0 kernel: pciback 0000:c3:00.4: registering for 6
May 28 19:29:25 dom0 kernel: pciback 0000:c3:00.5: xen_pciback: vpci: assign to virtual slot 1 func 5
May 28 19:29:25 dom0 kernel: pciback 0000:c3:00.5: registering for 6
May 28 19:29:25 dom0 kernel: pciback 0000:c3:00.6: xen_pciback: vpci: assign to virtual slot 1 func 6
May 28 19:29:25 dom0 kernel: pciback 0000:c3:00.6: registering for 6
May 28 19:29:25 dom0 kernel: xen-blkback: backend/vbd/6/51712: using 1 queues, protocol 1 (x86_64-abi) persistent grants
May 28 19:29:25 dom0 kernel: xen-blkback: backend/vbd/6/51728: using 1 queues, protocol 1 (x86_64-abi) persistent grants
May 28 19:29:25 dom0 kernel: xen: registering gsi 37 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :37
May 28 19:29:25 dom0 kernel: xen-blkback: backend/vbd/6/51744: using 1 queues, protocol 1 (x86_64-abi) persistent grants
May 28 19:29:25 dom0 kernel: xen: registering gsi 37 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :37
May 28 19:29:25 dom0 kernel: xen: registering gsi 37 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :37
May 28 19:29:25 dom0 kernel: xen: registering gsi 37 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :37
May 28 19:29:25 dom0 kernel: xen: registering gsi 37 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :37
May 28 19:29:25 dom0 kernel: xen: registering gsi 37 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :37
May 28 19:29:25 dom0 kernel: xen: registering gsi 37 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :37
May 28 19:29:25 dom0 kernel: pciback 0000:c1:00.3: xen-pciback: Driver tried to write to a read-only configuration space field at offset 0x2a6, size 2. This may be harmless, but if you have problems with your device:
                             1) see permissive attribute in sysfs
                             2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.
May 28 19:29:25 dom0 kernel: xen: registering gsi 38 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :38
May 28 19:29:25 dom0 kernel: xen-blkback: backend/vbd/6/51760: using 1 queues, protocol 1 (x86_64-abi) persistent grants
May 28 19:29:25 dom0 kernel: xen: registering gsi 38 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :38
May 28 19:29:25 dom0 kernel: xen: registering gsi 38 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :38
May 28 19:29:25 dom0 kernel: xen: registering gsi 38 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :38
May 28 19:29:25 dom0 kernel: xen: registering gsi 38 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :38
May 28 19:29:25 dom0 kernel: xen: registering gsi 38 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :38
May 28 19:29:25 dom0 kernel: xen: registering gsi 38 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :38
May 28 19:29:25 dom0 kernel: pciback 0000:c1:00.4: xen-pciback: Driver tried to write to a read-only configuration space field at offset 0x2a6, size 2. This may be harmless, but if you have problems with your device:
                             1) see permissive attribute in sysfs
                             2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.
May 28 19:29:25 dom0 kernel: xen: registering gsi 46 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :46
May 28 19:29:25 dom0 kernel: xen: registering gsi 46 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :46
May 28 19:29:25 dom0 kernel: xen: registering gsi 46 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :46
May 28 19:29:25 dom0 kernel: xen: registering gsi 46 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :46
May 28 19:29:25 dom0 kernel: xen: registering gsi 46 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :46
May 28 19:29:25 dom0 kernel: xen: registering gsi 46 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :46
May 28 19:29:25 dom0 kernel: xen: registering gsi 46 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :46
May 28 19:29:25 dom0 kernel: pciback 0000:c3:00.3: xen-pciback: Driver tried to write to a read-only configuration space field at offset 0x2a6, size 2. This may be harmless, but if you have problems with your device:
                             1) see permissive attribute in sysfs
                             2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.
May 28 19:29:25 dom0 kernel: xen: registering gsi 47 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :47
May 28 19:29:25 dom0 kernel: xen: registering gsi 47 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :47
May 28 19:29:25 dom0 kernel: xen: registering gsi 47 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :47
May 28 19:29:25 dom0 kernel: xen: registering gsi 47 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :47
May 28 19:29:25 dom0 kernel: xen: registering gsi 47 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :47
May 28 19:29:25 dom0 kernel: xen: registering gsi 47 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :47
May 28 19:29:25 dom0 kernel: xen: registering gsi 47 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :47
May 28 19:29:25 dom0 kernel: pciback 0000:c3:00.4: xen-pciback: Driver tried to write to a read-only configuration space field at offset 0x2a6, size 2. This may be harmless, but if you have problems with your device:
                             1) see permissive attribute in sysfs
                             2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.
May 28 19:29:25 dom0 kernel: xen: registering gsi 44 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :44
May 28 19:29:25 dom0 kernel: xen: registering gsi 44 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :44
May 28 19:29:25 dom0 kernel: xen: registering gsi 44 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :44
May 28 19:29:25 dom0 kernel: xen: registering gsi 44 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :44
May 28 19:29:25 dom0 kernel: xen: registering gsi 44 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :44
May 28 19:29:25 dom0 kernel: xen: registering gsi 44 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :44
May 28 19:29:25 dom0 kernel: xen: registering gsi 44 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :44
May 28 19:29:25 dom0 kernel: pciback 0000:c3:00.5: xen-pciback: Driver tried to write to a read-only configuration space field at offset 0x2a6, size 2. This may be harmless, but if you have problems with your device:
                             1) see permissive attribute in sysfs
                             2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.
May 28 19:29:25 dom0 kernel: xen: registering gsi 45 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :45
May 28 19:29:25 dom0 kernel: xen: registering gsi 45 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :45
May 28 19:29:25 dom0 kernel: xen: registering gsi 45 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :45
May 28 19:29:25 dom0 kernel: xen: registering gsi 45 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :45
May 28 19:29:25 dom0 kernel: xen: registering gsi 45 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :45
May 28 19:29:25 dom0 kernel: xen: registering gsi 45 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :45
May 28 19:29:25 dom0 kernel: xen: registering gsi 45 triggering 0 polarity 1
May 28 19:29:25 dom0 kernel: Already setup the GSI :45
May 28 19:29:25 dom0 kernel: pciback 0000:c3:00.6: xen-pciback: Driver tried to write to a read-only configuration space field at offset 0x2a6, size 2. This may be harmless, but if you have problems with your device:
                             1) see permissive attribute in sysfs
                             2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.
May 28 19:29:27 dom0 qubesd[2957]: vm.sys-usb: Setting Qubes DB info for the VM
May 28 19:29:27 dom0 qubesd[2957]: vm.sys-usb: Starting Qubes DB
May 28 19:29:27 dom0 audit[6218]: CRED_ACQ pid=6218 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="USERNAME" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
May 28 19:29:27 dom0 runuser[6218]: pam_unix(runuser:session): session opened for user USERNAME(uid=1000) by (uid=0)
May 28 19:29:27 dom0 audit[6218]: USER_START pid=6218 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_unix acct="USERNAME" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
May 28 19:29:27 dom0 runuser[6218]: pam_unix(runuser:session): session closed for user USERNAME
May 28 19:29:27 dom0 audit[6218]: USER_END pid=6218 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_unix acct="USERNAME" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
May 28 19:29:27 dom0 audit[6218]: CRED_DISP pid=6218 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="USERNAME" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
May 28 19:29:27 dom0 qubesd[2957]: vm.sys-usb: Activating the sys-usb VM
May 28 19:29:27 dom0 audit[6222]: CRED_ACQ pid=6222 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="USERNAME" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
May 28 19:29:27 dom0 runuser[6222]: pam_unix(runuser:session): session opened for user USERNAME(uid=1000) by (uid=0)
May 28 19:29:27 dom0 audit[6222]: USER_START pid=6222 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_unix acct="USERNAME" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
May 28 19:29:29 dom0 kernel: xen-blkback: backend/vbd/5/51712: using 2 queues, protocol 1 (x86_64-abi) persistent grants
May 28 19:29:29 dom0 kernel: xen-blkback: backend/vbd/5/51728: using 2 queues, protocol 1 (x86_64-abi) persistent grants
May 28 19:29:29 dom0 kernel: xen-blkback: backend/vbd/5/51744: using 2 queues, protocol 1 (x86_64-abi) persistent grants
May 28 19:29:29 dom0 kernel: xen-blkback: backend/vbd/5/51760: using 2 queues, protocol 1 (x86_64-abi) persistent grants
May 28 19:29:31 dom0 runuser[6222]: pam_unix(runuser:session): session closed for user USERNAME
May 28 19:29:31 dom0 kernel: kauditd_printk_skb: 15 callbacks suppressed
May 28 19:29:31 dom0 kernel: audit: type=1106 audit(1716917371.934:554): pid=6222 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_unix acct="USERNAME" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
May 28 19:29:31 dom0 kernel: audit: type=1104 audit(1716917371.934:555): pid=6222 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="USERNAME" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
May 28 19:29:31 dom0 audit[6222]: USER_END pid=6222 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_unix acct="USERNAME" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
May 28 19:29:31 dom0 audit[6222]: CRED_DISP pid=6222 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="USERNAME" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
May 28 19:29:33 dom0 qrexec-policy-daemon[3044]: qrexec: qubes.WindowIconUpdater+: sys-usb -> @adminvm: allowed to dom0
May 28 19:30:09 dom0 qrexec-policy-daemon[3044]: qrexec: qubes.GetDate+nanoseconds: sys-usb -> @default: allowed to dom0
May 28 19:30:09 dom0 audit: BPF prog-id=75 op=LOAD
May 28 19:30:09 dom0 kernel: audit: type=1334 audit(1716917409.181:556): prog-id=75 op=LOAD
May 28 19:30:09 dom0 kernel: audit: type=1334 audit(1716917409.181:557): prog-id=76 op=LOAD
May 28 19:30:09 dom0 kernel: audit: type=1334 audit(1716917409.181:558): prog-id=77 op=LOAD
May 28 19:30:09 dom0 audit: BPF prog-id=76 op=LOAD
May 28 19:30:09 dom0 audit: BPF prog-id=77 op=LOAD
May 28 19:30:09 dom0 systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
May 28 19:30:09 dom0 systemd[1]: Started systemd-hostnamed.service - Hostname Service.
May 28 19:30:09 dom0 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 28 19:30:09 dom0 kernel: audit: type=1130 audit(1716917409.235:559): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 28 19:30:10 dom0 systemd[1]: /usr/lib/systemd/system/qubes-suspend.service:9: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.

For reference

$ sudo lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e8
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 14e9
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14ea
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14ea
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14ee
00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14ee
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14ea
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 19h USB4/Thunderbolt PCIe tunnel
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14ea
00:04.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 19h USB4/Thunderbolt PCIe tunnel
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14ea
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14eb
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14eb
00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14eb
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 71)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14f0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14f1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14f2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14f3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14f4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14f5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14f6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14f7
01:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal]
c1:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 (rev c1)
c1:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller
c1:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 19h (Model 74h) CCP/PSP 3.0 Device
c1:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15b9
c1:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15ba
c1:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor (rev 63)
c1:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller
c2:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 14ec
c2:00.1 Signal processing controller: Advanced Micro Devices, Inc. [AMD] AMD IPU Device
c3:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 14ec
c3:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15c0
c3:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15c1
c3:00.5 USB controller: Advanced Micro Devices, Inc. [AMD] Pink Sardine USB4/Thunderbolt NHI controller #1
c3:00.6 USB controller: Advanced Micro Devices, Inc. [AMD] Pink Sardine USB4/Thunderbolt NHI controller #2

$ sudo lsusb
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0bda:5634 Realtek Semiconductor Corp. Laptop Camera
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05e3:0625 Genesys Logic, Inc. USB3.2 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0e8d:e616 MediaTek Inc. Wireless_Device
Bus 001 Device 009: ID 32ac:0018 Framework Laptop 16 Keyboard Module - ISO
Bus 001 Device 008: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 001 Device 005: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 007: ID 32ac:0014 Framework Laptop 16 Numpad Module
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ sudo lsusb -t
/:  Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M
/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/3p, 10000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/5p, 480M
    |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
    |__ Port 3: Dev 4, If 0, Class=Hub, Driver=hub/3p, 480M
        |__ Port 2: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 2: Dev 7, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 2: Dev 7, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 2: Dev 7, If 3, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 4: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 2: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 2: Dev 9, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 2: Dev 9, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 2: Dev 9, If 3, Class=Human Interface Device, Driver=usbhid, 12M

apparatus · May 28, 2024, 5:51pm

Check the log in sys-usb. Specifically anything related to qubes-input-sender.
Also what’s your sys-usb template?

harrim4n · May 28, 2024, 9:21pm

The template was set to default-dvm, and the template of that was set to debian-12-xfce.

The pointer re: qubes-input-sender was a great one. I noticed that the last logs from that service were from several days ago and then I vaguely remembered that I ran some apt commands in the template at that time. After having a look at the history.log of apt on the template, I noticed that I ran some removal command and accidentally removed some qubes default packages along with that, including the qubes-input-sender proxy

I have now reinstalled all required packages in the template and everything is now working again as expected.

Thank you very much for your insights and help, I really do appreciate it tremendously!