Manjaro Mate Running In Virtualbox

@clatterfordslim
I am not surprised between the working difference between Manjaro and Linux Lite or any other Debian based distro. My machine is UEFI capable but is running bios_boot for several reasons. Out curiosity and of wanting something to do, I moved EndeavourOS and Manjaro over to a 1tb gpt drive on two separate partitions. I also used MXlinux and Mint for this experiment. I can run MXlinux and Mint
without any problem, but when EndeavourOS or Manjaro is thrown into the mix, everything changes.
I realize this is in part of the bios_boot I am using with a gpt drive. In order to get either EndeavourOS
or Manjaro to boot on a gpt drive, they have to have a 8MiB unformatted bios_grub partition, for grub
to write too, I believe this is true for any Arch based distro. I find it almost impossible, to even get the
two Arch base distro to sync and boot, while the Debian based distros work just fine. I can use a
Rescatux CD and boot any vmlinuz it may find and even W10.
I will now try using a msdos 120GB SSD with four partitions and see if EndeavourOS and Manjaro
will write and boot with Mint and MXlinux.


I finally have the booting sorted. I have found that Arch based Grub and Debian based Grub, do not
play well together. Arch based Grub will boot a Debian based distro, but it doesn’t work the other way.
The fix is to put the boot flag on, I chose Manjaro, and set /etc/default/grub.
GRUB_DEFAULT=saved
GRUB_TIMEOUT=30
GRUB_SAVEDEFAULT=true
GRUB_DISABLE_OS_PROBER=false
All other OS’s /etc/default/grub are set with
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISABLE_OS_PROBER=true
You then run, in my case grub-install /dev/sdb and then run grub-mkconfig -o /boot/grub/grub.cfg to
update Manjaro /boot.
Stuff like this can get crazy but I fixed the problem, and gained a little knowledge along the way.

1 Like