On 2/24/20 7:17 PM, ncmy...@gmail.com wrote:
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
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 options.
Unmounting before fsck is the
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
Is there a way to get reliable booting after a dom0 kernel
update?
I am afraid that there is no such way as the new Linux kernel adds new
features, changes the current ones, which are unlikely were thoroughly tested
(or if tested at all) for the whole range of HW out there or their
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
