Two Linux systems - Grub problem

First of all, sorry for my English. I looked everywhere for information, but did not find it.
I have two Linux: Manjaro and Mint.
I really only use Manjaro and Mint is only “in case of trouble”. Unfortunately, /boot/grub/grub.cfg only reads what is on Grub configuration files from Mint (sda 4), not from Manjaro (sda2). In theory, sudo update-grub
on Mint should be the solution, but it’s not.

How can I make /boot/grub/grub.cfg read what I update on Manjaro (sda2)?

Can you start update-grub on Manjaro ?

1 Like

No, Manjaro’s GRUB must take precedence for the two systems to coexist peacefully. :wink:

1 Like

~ >>> sudo update-grub [1] Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.9-x86_64 Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.9-x86_64.img Found initrd fallback image: /boot/initramfs-5.9-x86_64-fallback.img Found linux image: /boot/vmlinuz-5.8-x86_64 Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.8-x86_64.img Found initrd fallback image: /boot/initramfs-5.8-x86_64-fallback.img Found linux image: /boot/vmlinuz-5.7-x86_64 Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.7-x86_64.img Found initrd fallback image: /boot/initramfs-5.7-x86_64-fallback.img Found linux image: /boot/vmlinuz-5.4-x86_64 Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img Found linux image: /boot/vmlinuz-4.14-x86_64 Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.14-x86_64.img Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img Found Linux Mint 20 Ulyana (20) on /dev/sda4 Found memtest86+ image: /boot/memtest86+/memtest.bin done ~ >>>

The operation is successful as you can see. Unfortunately, at boot time, where we have the choice of which system to boot, the kernels, it has no effect. Only what was previously entered in Mint is loaded.

Hello did you perform grub-install within Manjaro?

2 Likes

A friend fixed me using the remote desktop. It turned out that “someone” set the GPT partition table for me, and it should be MBR :wink: