NOTE: If you never installed a sys-usb because qubes setup grayed it out (as you are using a USB keyboard) then I would love for you to reply to this answering the questions in the bottom numbered list. Otherwise I will have to reinstall qubes on another drive in the near future and look closely at that. Thanks.
I followed some instructions at USB qubes | Qubes OS specifically
sudo qubesctl state.sls qvm.usb-keyboard
Which caused troubles. I just want to 100% reverse what I did. But I don’t quite know how.
The trouble started when I rebooted afterwards and got this:
Warning: /dev/mapper/qubes_dom0-root does not exist Warning: /dev/qubes_dom0/root does not exist Warning: /dev/qubes_dom0/swap does not exist
I have qubes installed and booting from a USB SSD device. So I thought maybe it is locking itself out of finding the partitions it needs.
I also discovered that I have 2 different USB controllers. Not sure how relevant that is.
BTW, I have a PS/2 keyboard plugged in just in case, but I haven’t needed it.
So I got back in by removing
usbcore.authorized_default=0 and adding
qubes.skip_autostart to the kernel command line. Thank god for that.
This seems serious enough and easy enough to happen that there should be some warning on this page I think. It points you to “How to remove a USB qube” which is incomplete… hence this post.
I re-ran the salt thing to see all the steps it takes, so I can reverse each one of them.
To reverse this I might need to do these, but maybe not, I cannot tell now:
- edit /etc/default/grub and remove the part where it adds “usbcore.authorized_default=0”
- If I have to do 1, then I have to do the grub2-mkconfig thing
- Remove the sys-usb qube
- Edit /etc/qubes-rpc/policy/qubes.InputKeyboard … but to what? Having ‘sys-usb’ lines without a ‘sys-usb’ qube seems wrong to me.
- Edit /etc/qubes-rpc/policy/qubes.InputMouse … but to what?
- Get rid of /email@example.com/50_autostart.conf (manually? systemd disable?)