Removed monitor device from dom0...now QubesOS won't load

[whoami]

@serpentine

After first reboot, Heads gave me an “ERROR: Boot hash mismatch” error message, stating /boot/grub2/grub.cfg had been modified & asked me if I wanted to update the checksums. After not finding any threads describing similar behavior, I figured it had to do with initializing the dom0 user – or Qubes had automatically installed the downloaded updates without me realizing – && ended up updating the checksums and trying to boot the OS.

After entering the LUKS decryption password, the screen goes black, fans go full-tilt, and it just hangs like that forever (I let it do that for three hours before giving up and doing a hard reset using the power key).

First, make sure that you run not into this issue:
https://docs.nitrokey.com/nitropad/system-update.html
in simple words, when you did a dom0 update your kernel will be updated and then you have to follow this coreboot update (new signing)

Secondly, I have also a NitroPad T430 and I have issues with the latest kernels:

Boot issue with Coreboot and Linux 5.4.143-1

Qubes 4.0, T430, coreboot, nitrokey xen_version: 4.8.5-35.fc25 Linux 5.4.136-1.fc25.qubes.x86_64 works but with the latest dom0 update xen_version: 4.8.5-35.fc25 Linux 5.4.143-1.fc25.qubes.x86_64 does not work. It freezes at: [ xx.xxxxx] kexec_core: Starting new kernel Edit: With the latest QOS dom0 update I had to update my NK (verify new /boot) I went into a crash which forced me to make a power off to reboot.

I was not able to fix it. Currently, I just use an old kernel 5.4.136-1.fc25.qubes.x86_64