Trying to get my WLAN adapter into sys-net, I made a fatal mistake: The USB
host added also has the boot device (and mouse) connected. Now as soon as
sys-net starts (maybe even earlier) the PV for qubes becomes inaccessible.
Mounting the device in another Linux system, I tried to prevent the start of
sys-net by renaming the systemd link for multi-user target, but that did not
help. The kernel panics shortly after boot.
Before I had tried to find (and edit) the settings that cause the problem, but
could not find them.
My idea was to prevent start of sys-net, then use the qubes manager to undo my
Unfortunately I don't get that far.
first. If that doesn't work, make a copy of /var/lib/qubes/qubes.xml,
and edit it by hand to remove autostarting sys-net (and all other
autostarts that depend on it such as sys-firewall), and/or remove the
WLAN binding to sys-net. It's XML so a somewhat fragile file; pay
attention to the <>/ etc.
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit