Follow on from my thread here, I am unable to boot due to sys-net essentially. Adding qubes.skip_autostart to grub startup config doesn’t seem to be stopping sys-net from starting.
Hi MajorMalfunctionQ
Which release of Qubes OS are you running?
Hi,
4.3
Are there any other qubes, like sys-firewall or downstream qubes that depend on sys-net for networking? That would result in sys-net still autostarting.
Yeah, that’s right. Whatever the standard Qubes-Whonix configuration is is how it loads.
Essentially in the other thread (Where hopefully I just continue this conversation - mistake making new threads though different topics now) I wrote that I stupidly added ALL the devices back to sys-net after managing to remove them all with a command, and now I can’t get past user login.
I was able to get past user login and to dom0 before that - so my only assumption is that skip_autostart is not working, as I was able to get to dom0 even with a faulty sys-net on one laptop.
I followed the documentation correctly multiple times and I still cannot get past the user password login using skip_autostart.
I think you mentioned some delay…
Do you have a cron entry that is starting one of the qubes?
Or something in rc.local?
Hi MajorMalfunctionQ
I’ve tested on both QubesOS 4.2.4 and QubesOS 4.3.0 – and in both cases replacing rhgb quiet with qubes.skip_autostart in GRUB boot menu, booted Qubes to a running dom0, without other running qubes. So I can’t reproduce the:
“Skip_autostart doesn’t seem to be stopping sys-net from starting”
I’ve tested on direct install of 4.2.4 and 4.3.0 – I’ve not tried in place upgrades.
A quick question: You are not moving a drive/usb-stick between machines … are you?
Hi, thanks for replying.
I did this on my Qubes backup, and the qubes booted alongside dom0 after user login - what am I doing wrong?
I am doing the same command on my corrupted Qubes - which also doesn’t have rhgb quiet in the pre-boot GRUB menu.
Hi MajorMalfunctionQ
I’m not sure what “pre-boot GRUB” menu is … when you see the:
Qubes (R4.3), with Xen hypervisor
hit the e key to edit the options for the boot, locate the line starting with module2 and scroll to the right there should be rhgb quiet as some of the last …
1 Like
I just looked back to the doc linked in the other thread - it is ambiguous when there are two module2 lines.
All the changes are for the line that begins with module2 /vmlinuz
Does that make a difference? In your photo, the end of the line is hidden off the screen… after “plymouth”.
Hi,
Did you see my photo (and the reply below)? I have added the code there at the end of the second module2, but it still opens the qubes on my working backup Qubes system.
From the picture, you added “qubes.skip_autostart” to the wrong line.
It should be added to the line starting with “module2 /vmlinuz-6.12...”, three lines up from the line you used.
1 Like
Hi MajorMalfunctionQ
I didn’t notice that you had added the qubes.skip_autostart to the second module2 line … the rhgb quiet should be on the first module2 line (starting with module2 /vmlinuz-.. – and that looked cut short on the photo.
2 Likes
That’s right, adding it to the first module2 line worked =).
Maybe the docs could be updated and clarified for idiots like me!
1 Like
Not idiot, just a victim of everybody round you knowing something they didn’t think to tell you…
I made my first docs PR earlier:
1 Like
I’ll second that! – I didn’t notice that both my machines had two module2 lines … and I looked at you image and scanned to the point in the first line, where I expected the qubes.skip_autostart to be … so I’ll plea “Guilty” on the charge of “not thinking to tell” … and I’m happy that it worked!
1 Like