sys-net cannot be started (shuts down very soon) after installation of 4.2.2 and 4.2.3 #9495
Labels
affects-4.2
This issue affects Qubes OS 4.2.
C: other
hardware support
needs diagnosis
Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed.
P: default
Priority: default. Default priority for new issues, to be replaced given sufficient information.
T: bug
Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
How to file a helpful issue
Qubes OS release
4.2.3
Brief summary
I installed Qubes OS 4.2.2 on an external NVME SSD connected via USB (I had used the same device successfully for n older Qubes OS on a different computer). After reboot there was an error displayed.
Installation finished, but
sys-net
would shutdown itself rather quickly, and withoutsys-net
no qube can be started. Obviously anything fixable through a downloadable update would not work.Maybe it has to do with some disk that cannot be mounted, like this:
Maybe this message causes it, but I don't know:
I suspect that it might also be CPU-related, as the Laptop (Lenovo ThinkPad P16 Gen2) has an Intel i9-13980HX CPU.
As other Linux shows 32 CPUs, and the machine has 96GB RAM, it would be a nice machine to run Qubes OS, I guess.
Here are some more details:
After that I connected the NVME device to the other computer that ran Qubes OS before, but there also
sys-net
won't start, so maybe it's not really a CPU issue.The only difference was that I had to repartition the NVME for GPT (before it was MBR) as the new laptop does not support "legacy boot" any more.
After that I downloaded the latest 4.2.3 installation medium, installed Qubes OSagain, but the result was the very same:
sys-net
terminates rather quickly.Steps to reproduce
Install Qubes OS
Expected behavior
Qubes OS starts after installation
Actual behavior
Qubes OS is unusable after installation.
The text was updated successfully, but these errors were encountered: