Thank you for your kind attention.
I want to make clear that in each case, the new kernel has worked
fine once I persuaded my BIOS to boot it. The problem is always
that, after each kernel upgrade, the BIOS no longer recognizes any
bootable partition, not even listing the drive among its boot opti
I find that dom0's /var/lib/qubes/vm-kernels/ does not list a
5.4 kernel, despite that dom0 uname reports running it. After I run
# qubes-dom0-update kernel-latest-qubes-vm
a 5.4 kernel is now listed, and is now selectable using
Qube Settings/Advanced.
Thank you.
On Monday, February 24, 202
I find that, when I update dom0 with a new kernel, too
often my machine won't boot anymore, after the update.
Then I need to tinker with the boot partition. It seems as if,
this last time, what worked was to run fsck.vfat on the
partition. I am (I hope understandably) reluctant to mess
about
I recently succeeded in getting my dom0 upgraded to a 5.4 kernel.
(I can't recall how, because it would not boot for some days afterward.
More about that in another post.)
Now uname in dom0 reports the shiny new 5. 4 kernel.
I also got 5.4 kernels installed in some VM templates. However,
when I s
