[SOLVED]: GRUB boot loader problem with 5.* kernels

[Moderator Brian Masinick]

For those who have experienced any issues booting Version 5 kernels, it appears that disabling the framebuffer capability solves this problem, and does not disturb booting other kernels into antiX.

Here are the particular steps used to fix this issue:
go into /etc/default/grub, eg.
sudo geany /etc/default/grub
and search for
GRUB_CMDLINE_LINUX_DEFAULT=”quiet”
change it to
GRUB_CMDLINE_LINUX_DEFAULT=”nofb”
instead, and for good measure, set

GRUB_GFXMODE=1024x768x32,auto
set GFXPAYLOAD=keep

save the file, and run sudo update-grub
and then
/boot/grub/grub.cfg
should contain
linux /boot/vmlinuz-5.10.142-antix.2-amd64-smp root=UUID=dadd5816-6e4a-468d-93ea-6639bf91d990 ro nofb
or something similar for the antiX kernels; it doesn’t hurt any of them, but it ensures that the 5.10 kernels will boot without the framebuffer, which has been causing problems, as I discovered when I took off the quiet flag.

Reference: https://support.digium.com/community/s/article/How-to-disable-the-Linux-frame-buffer-if-it-s-causing-problems

--
Brian Masinick

[Member oops]

Helpful

Up

0

::

Brian Masinick wrote:

For those who have experienced any issues booting Version 5 kernels, it appears that disabling the framebuffer capability solves this problem, and does not disturb booting other kernels into antiX.
…
GRUB_CMDLINE_LINUX_DEFAULT=”nofb”
…

Congratulations, good to know then.

[Member calciumsodium]

Helpful

Up

0

::

Thanks for the tip @Brian

[Author]

Posts