When using a USB keyboard on a system with multiple USB controllers, we recommend that you designate one of them exclusively for the keyboard (and possibly the mouse) and keep other devices connected to the other controller(s). This is often an option on desktop systems, where additional USB controllers can be plugged in as PCIe cards. In this case, the designated controller for input devices should remain in dom0 but be limited to input devices only.
I guess you need to remove usbcore.authorized_default=0 option from your grub config as well:
Qubes 4.1 only: You should also add the usbcore.authorized_default=0 option, which prevents the initialization of non-input devices. (Qubes ships with a USBGuard configuration that allows only input devices when usbcore.authorized_default=0 is set.)
Did you make a new grub config with grub2-mkconfig after you removed usbcore.authorized_default=0 in /etc/default/grub?
Or maybe you still have old EFI grub.cfg instead of unified one and then you need to update it instead: grub-mkconfig -o /boot/efi/EFI/qubes/grub.cfg
Do you have external display connected with USB? Maybe you have this issue:
I had a USB hub issue in the past that was fixed by simply switching the USB devices. Is your USB keyboard and USB Yubikey on the same USB hub? What is your USB setup: All connected without adapter and hubs directly to a separate USB connector?
It could be a to a bad power supply since you have audio, storage, keyboard, mouse, yubikey connected.
But I doubt this since audio and storage could have a high power request but Yubikey almost nothing.
Anways, it is worth to disconnect all apart from keyboard, mouse and Yubikey for further debugging.
For some reason it did not overwrite efi file, did it again, and it did.
Usb storage devices work.
Yubi key absolutely does not work or appear in devices.
Any ideas how to get non block devices, like this Yubikey to work ?
I don’t know if there’s any way to make it work without sys-usb, but I’d still try to create a working sys-usb and find the source of your problem with sys-usb and display blanking.
Maybe you have multiple PCI USB controllers that are attached to sys-usb after creation and only one of them could cause your problem with display, so I’d try to create sys-usb in the same way as before but remove all USB controllers in sys-usb Qube Settings → Devices tab except for one USB controller and then try to start sys-usb with each USB controller separately to try and find the one that is causing the display issue.
Yes that absolutely sounds like what needs to be troubleshot.
To make absolutely certain that I am setting up sys-usb correctly what steps do I need to take, what kind of qube should it be / setttings / anything to do on command line
Do I plug kb + mouse into that same single controller I am testing.
As an aside I see only two USB: xxxxxx controllers one for 3.0 and one for 3.1 however I have 2.0 ports as well. Does this change the surface of how many tests I should be doing and how do I locate the 2.0 controller ?