Fix Grub-Customizer ARCH entries for multibooters  [Solved]

Here is where you can post tips and tricks to share with other users of MX. Do not ask for help in this Forum.
Message
Author
User avatar
1-DOT.C0M
Posts: 30
Joined: Wed Jun 08, 2022 11:22 am

Fix Grub-Customizer ARCH entries for multibooters  [Solved]

#1 Post by 1-DOT.C0M »

I always keep a few Linux distros installed on a 11+ year old Lenovo notebook. That currently includes MX 21 Fluxbox, MXDE 21, KDE Neon 221023, and two Arch-based distros, CachyOS KDE (based on ArcoLinux) and MaBox (Manjaro Openbox). All use the EXT4 file system.

The ancient Grub Customizer utility using OS-Prober previously generated a nice Grub boot menu using a modified StylishDark_mx theme. When I run Grub Customizer from CachyOS, it still generates a fully functional Grub boot menu. However, if I now run Grub Customizer using MX 21 Fluxbox, both Arch-based distos will fail upon bootup with a KERNEL PANIC message.

I suspect that this has something to do with the Arch community's recent problems with GRUB.

From MX Fluxbox Grub-Customizer, I edited the original CachyOS entry shown below:

Code: Select all

insmod part_msdos
insmod ext2
set root='hd0,msdos8'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos8 --hint-efi=hd0,msdos8 --hint-baremetal=ahci0,msdos8  2e479209-d086-4167-a100-b463c6e24d63
else
  search --no-floppy --fs-uuid --set=root 2e479209-d086-4167-a100-b463c6e24d63
fi
linux /boot/vmlinuz-linux-cachyos root=UUID=2e479209-d086-4167-a100-b463c6e24d63 rw quiet
initrd /boot/intel-ucode.img^/boot/amd-ucode.img^/boot/initramfs-linux-cachyos.img
The problem is the LAST LINE. To fix it, replace the ^ characters with spaces.

Code: Select all

initrd /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-linux-cachyos.img
This tries 3 img files until it finds one that works. For my old Lenovo, only the last one works. So, for me, the following is quicker/better.

Code: Select all

initrd /boot/initramfs-linux-cachyos.img
I made the same fix editing the MaBox Linux entry. Both now boot correctly.
12+ year old Lenovo IdeaPad -- MX 23 Fluxbox + CachyOS (Arch) 230709 KDE + Sparky (Debian) 7.01 KDE + Debian 12.1 Gnome
Image -- Honor (Huawei) Matebook -- AV Linux MX (waiting for Debian 12 update) + Win10 -- HP Chromebase ChromeOS

User avatar
fehlix
Developer
Posts: 12578
Joined: Wed Apr 11, 2018 5:09 pm

Re: Fix Grub-Customizer ARCH entries for multibooters

#2 Post by fehlix »

1-DOT.C0M wrote: Mon Nov 07, 2022 4:04 am I suspect that this has something to do with the Arch community's recent problems with GRUB.

From MX Fluxbox Grub-Customizer, I edited the original CachyOS entry shown below:

Code: Select all

initrd /boot/intel-ucode.img^/boot/amd-ucode.img^/boot/initramfs-linux-cachyos.img
Actually, MX ships with some adjustments to make µcode-initrd entries show up properly for Arch-based distributions.
At least tests with Manjaro have shown to generate GRUB menu entries properly.
Would you mind showing this listing:

Code: Select all

ls -l /etc/grub.d/*
It may be a simple fix, just to copy one file into the right position, in case you have replaced MX provided versions with Debian's version during last GRUB packages upgrade.
Otherwise a next GRUB menu rebuild e.g. during kernel upgrade or driver upgrade will overwrite your manually changes.

Post Reply

Return to “Tips & Tricks by users”