TLDR; I’m not sure which instructions to read for my use case
I’m giving up on ps/2 keyboards, and instead planning on just using a sys-usb-keyboard (seperate from sys-usb)
So there would be:
sys-usb-keyboard (pass through of the one USB controller that goes to the keyboard) (later, usbguard can block everything except keyboards)
sys-usb-mouse (pass through of the one USB controller that goes to the mouse) (later, usbguard can block everything except mice)
sys-usb (all other USB controllers)
Note: I’ve tested the USB passthrough hardware before and I am not having the “IOMMU group” issue
However, there are lots of instructions and lots of questions on the matter, but it is not obvious which applies to my situation (for example, it’s possible that USB qubes | Qubes OS is trying to jack the USB controller directly into dom0 and eliminating sys-usb-keyboard (as opposed to connecting to it just for LUKS then waiting for sys-usb-keyboard to hand it the keyboard to continue)
So far, when I try to set this up, I either end up:
- At the LUKS screen without a working keyboard
- get past the LUKS screen, but have no keyboard at the login screen (this was after setting usbcore.authorized_default=0 and rd.qubes.dom0_usb= as said in document
USB qubes | Qubes OS )
(note: i am assuming that the “BDF” parameter for rd.qubes.dom0_usb is supposed to be a PCI address like: “05:00.0”, not a qubes usb address like sys-usb-keyboard:4-2 )
is rd.qubes.dom0_usb= conflicting with rd.qubes.hide_all_usb ?
Also note: I am still able to edit the grub configuration. when I remove rd.qubes.hide_all_usb and add qubes.skip_autostart, the keyboard and mouse work, so I can attempt the next configuration
Anyway, I find reading posts on this confusing with all the possible instructions for all the possible configurations