Added USB contoller to sys-net, and broke Qubes 4.0

Qubes OS 4.0 Issue – Need Help to Roll Back

I connected the USB controller of motherboard to sys-net in Qubes Manager.
Sys-net is set to autostart.

When I started sys-net, an error occurred, and my USB keyboard and mouse stopped working.

Now, after rebooting, before anything appears on the screen, the keyboard and mouse stop working, making the system unresponsive.

I need help to roll back to the state before this critical error.

I can boot into Ubuntu and access the filesystem.
Maybe I can edit some specific config files to deal with it?

P.S.
System boots instantly with EFI, without a GRUB menu, so I don’t know how to add qubes.skip_autostart

Ah, good ol’ 4.0. That takes me back… :smirk:


Ok, here’s what you need to do. I’m unsure whether this still works, because it’s been years since I’ve used 4.0, but here goes:

You’ll need to mount your EFI partition, and edit some config files.

If you’re unsure which partition this is, it’ll probably be partition 1. Failing that, just mount them one by one and the correct partition will be the one that only has a single directory in it called EFI.

You’ll need to edit either:
EFI/qubes/xen.cfg
OR
EFI/BOOT/BOOTX64.cfg
OR
EFI/qubes/grub.cfg

You need to put the qubes.skip_autostart parameter at the end of the lines that has kernelopts (I’m assuming you know what those are) in one of those files.


Sorry I couldn’t provide more help. I don’t have access to a 4.0 machine at the moment. Hope this helps :slight_smile:

1 Like