1

I've tried to get my dualboot screen working for a while, to give some context:

  • I had the same Windows install for a few years now
  • Installed PopOs a couple of months ago
  • I have 2 drives and Windows is on my primary SSD and Pop!_OS on my HDD
  • Got tierd of switching boot priority on BIOS to change from Windows to Pop!_OS
  • Windows BIOS mode is on Legacy and Pop!_OS on UEFI

I followed this guide but my grub isn't working properly, I've tried different boot entrys and found that:

  • SATA6G_3: Samsung SS 850 EVO 2 (Boots to Windows)
  • UEFI OS (SATA6G_5: Toshiba DT101ACA100) (Boots to this GRUB Screen)
  • pop (SATA6G_5: Toshiba DT101ACA100) (Boots to Pop!_Os)
  • Pop!_OS 20.10 (SATA6G_5: Toshiba DT101ACA100) (Boots to Pop!_Os)

Note: I've tried to use sudo os-prober to get the path for Windows but that command doesn't return any ouput (I did mount the SSD drive before running the comand)

I don't really know what is going on, I'm guessing that grub and Pop!_OS can't find Windows and that's why I'm having trouble

André Clérigo
  • 111

2 Answers2

2

From Dual_boot_with_Windows

Most of the linux bootloaders installed for one firmware type cannot launch or chainload bootloaders of the other firmware type. That is, if Arch is installed in UEFI/GPT or UEFI/MBR mode in one disk and Windows is installed in BIOS/MBR mode in another disk, the UEFI bootloader used by Arch cannot chainload the BIOS installed Windows in the other disk. Similarly if Arch is installed in BIOS/MBR or BIOS/GPT mode in one disk and Windows is installed in UEFI/GPT in another disk , the BIOS bootloader used by Arch cannot chainload UEFI installed Windows in the other disk.

The only exceptions to this are GRUB in Apple Macs in which GRUB in UEFI mode can boot BIOS installed OS via appleloader command (does not work in non-Apple systems), and rEFInd which technically supports booting legacy BIOS OS from UEFI systems, but does not always work in non-Apple UEFI systems as per its author Rod Smith.

Hence my suggestion : use refind

pop-planet-REFInd

But there's more

However if Arch is installed in BIOS/GPT in one disk and Windows is installed in BIOS/MBR mode in another disk, then the BIOS boot loader used by Arch CAN boot the Windows in the other disk, if the boot loader itself has the ability to chainload from another disk.

Madhubala
  • 2,008
0

You can try using Refind as your main bootloader. By default, it automatically checks all disks and partitions (all it can read that is) for .efi and vmlinux files. As far as I remember, it can boot both legacy and Uefi installed OSes, if your BIOS(UEFI) supports Legacy/CSM mode. But I think you need to uncomment the option in refind.conf file. (The info about this option is inside the .conf file itself, it's self-explanatory). And just in case your PC doesn't support it, it will explicitly tell you so during boot.

Borie Poven
  • 11