@HPOA909, yeah, what you said about “removing the ext4” is a little unclear what you mean exactly. Is there any chance you could clarify what you mean?
Do you mean:
- zeroing out the drive before installation?
- That shouldn’t make a difference. The Qubes OS standard installer won’t zero out the drive, because that would shorten the lifespan of an SSD
- removing the ext4 label from the partition when formatting the drive?
- That also should be done automatically when you install, unless you try something complex like dual-booting
- something else?
- Please explain. Happy to explore any suggestions
I’ve never been lucky enough to get my hands on a NitroPC to play around with it, so I can’t say for certain that “skipping a step” in the installation wouldn’t interact with NitroKey’s BIOS.
It’s highly unlikely, to be honest, but I don’t want to just “saying anything without any evidence”, because that doesn’t really help anyone….
@qubist, the fact that you’re able to read system logs tells me that you’re fairly familiar with Linux, which is good, because we can skip the long paragraphs I normally have to write (thank you!)
Maybe it might be worth contacting NitroKey and asking them what’s going on. It’s possible that you might have a small hardware defect (unlikely, but possible, and it can’t hurt contacting them just to confirm ).
The other possibility is that it might be worth seeing what the latest kernel build does when you try to reboot it.
If you’re comfortable with running a Qubes OS-patched Linux kernel 5.18.9 or newer in your dom0 (there isn’t really any reason why, but you never know, some people might not want to…), then type this command into a dom0 terminal:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing kernel-latest kernel-latest-qubes-vm
That will download RPM packages for kernel version 5.18.14 (I think we’re at that version now….) as a don0 and another package for the same version as an AppVM kernel.
(You can select your kernel at boot with GRUB like you’re probably familiar with, and select the AppVM kernel in the Qube Settings, too. And of course, you can also purge them from your system later if you wish…)
If that doesn’t solve it, well, maybe adding an extra systemd service at the very end to power cycle your machine might work (I’ll write that up in a minute so you can just copy and paste. It’s not something that’s easy to type up without sitting down at a proper keyboard😋)
Your other option is to “live with it”. But i don’t feel that’s a valid solution, and I wouldn’t want you to do that!