Hello there,
I have the following problem: os-prober detects MX-Linux as Debian 11 (which was previously installed in place of MX, not sure how relevant that is).
$ sudo os-prober
/dev/sda5@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
/dev/sdb3:Debian GNU/Linux 11 (bullseye):Debian:linux
Upon selecting the Debian 11 entry in my grub, MX doesn’t load and I get dropped in the (initramfs) shell.When selecting directly MX’s grub (sdb2), it loads as it should. I can access fedora (but boot doesn’t complete, something something amdgpu drm message).
When comparing Fedora’s grub.cfg with MX’s grub.cfg, the entries are very similar:Am I missing something ?
Fedora grub.cfg:
menuentry 'Debian GNU/Linux 11 (bullseye) (on /dev/sdb3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-6.0.0-6mx-amd64--7cc60493-a401-41f7-926c-b38fa60a6e4d' {
insmod part_gpt
insmod btrfs
set root='hd1,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt3 --hint-efi=hd1,gpt3 --hint-baremetal=ahci1,gpt3 7cc60493-a401-41f7-926c-b38fa60a6e4d
else
search --no-floppy --fs-uuid --set=root 7cc60493-a401-41f7-926c-b38fa60a6e4d
fi
linux /boot/vmlinuz-6.0.0-6mx-amd64 root=/dev/sdb3
initrd /boot/initrd.img-6.0.0-6mx-amd64
MX grub.cfg:
menuentry 'MX 21.3 Wildflower' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-7cc60493-a401-41f7-926c-b38fa60a6e4d' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod btrfs
set root='hd1,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt3 --hint-efi=hd1,gpt3 --hint-baremetal=ahci1,gpt3 7cc60493-a401-41f7-926c-b38fa60a6e4d
else
search --no-floppy --fs-uuid --set=root 7cc60493-a401-41f7-926c-b38fa60a6e4d
fi
echo 'Loading Linux 6.0.0-6mx-amd64 ...'
linux /boot/vmlinuz-6.0.0-6mx-amd64 root=UUID=7cc60493-a401-41f7-926c-b38fa60a6e4d ro quiet splash
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.0.0-6mx-amd64
}
Furthermore grubby only displays fedora boot entries, no windows, no “Debian”;
sudo grubby --info=ALL
index=0
kernel="/boot/vmlinuz-6.2.12-300.fc38.x86_64"
args="ro loglevel=3 ${extra_cmdline}"
root="UUID=d0cdf429-d6c0-4a56-82f5-43cbfe3b41fc"
initrd="/boot/initramfs-6.2.12-300.fc38.x86_64.img"
title="Fedora Linux (6.2.12-300.fc38.x86_64) 38 (KDE Plasma)"
id="465125b6dc80477698faaf5211543315-6.2.12-300.fc38.x86_64"
index=1
kernel="/boot/vmlinuz-6.2.11-300.fc38.x86_64"
args="ro loglevel=3 ${extra_cmdline}"
root="UUID=d0cdf429-d6c0-4a56-82f5-43cbfe3b41fc"
initrd="/boot/initramfs-6.2.11-300.fc38.x86_64.img"
title="Fedora Linux (6.2.11-300.fc38.x86_64) 38 (KDE Plasma)"
id="465125b6dc80477698faaf5211543315-6.2.11-300.fc38.x86_64"
index=2
kernel="/boot/vmlinuz-6.2.11-100.fc36.x86_64"
args="ro loglevel=3 ${extra_cmdline}"
root="UUID=d0cdf429-d6c0-4a56-82f5-43cbfe3b41fc"
initrd="/boot/initramfs-6.2.11-100.fc36.x86_64.img"
title="Fedora Linux (6.2.11-100.fc36.x86_64) 36 (KDE Plasma)"
id="465125b6dc80477698faaf5211543315-6.2.11-100.fc36.x86_64"
index=3
kernel="/boot/vmlinuz-0-rescue-465125b6dc80477698faaf5211543315"
args="ro loglevel=3 ${extra_cmdline}"
root="UUID=d0cdf429-d6c0-4a56-82f5-43cbfe3b41fc"
initrd="/boot/initramfs-0-rescue-465125b6dc80477698faaf5211543315.img"
title="Fedora Linux (0-rescue-465125b6dc80477698faaf5211543315) 36 (KDE Plasma)"
id="465125b6dc80477698faaf5211543315-0-rescue"
Additional infos:
OS: Fedora Linux 38 (KDE Plasma) x86_64
Kernel: 6.2.12-300.fc38.x86_64
CPU: AMD Ryzen 5 5600X (12) @ 3.700GHz
Partitions
sda 465.8G
├─sda1 529M Récupération ntfs
├─sda2 /boot 1G boot ext4
├─sda3 16M
├─sda4 136G windows ntfs
├─sda5 /boot/efi 512M efi vfat
└─sda6 /var 327.1G fedora btrfs
sdb 447.1G
├─sdb1 416.6G EXT002 ext4
├─sdb2 513M vfat
├─sdb3 20.3G rootMX21 btrfs
└─sdb4 9.8G homeMX btrfs
More questions/hypothesis
-
How can I make grubby detect all OS’s ?
-
Why is my MX install displayed as “Debian 11” on fedora’s OS prober and how can I fix that ?
-
Is it possible that Fedora’s grub has troubles accessing MX’s kernel (which is on another disk/partition)
More infos:
MX was installed in UEFI mode.
Yes, I ran sudo grub2-mkconfig -o /etc/grub2-efi.cfg
Debian 11 was previously installed on sdb