- Joined
- Aug 18, 2016
- Messages
- 23
- Motherboard
- Optiplex 3020
- CPU
- i5-4590
- Graphics
- Intel HD 4600
- Mac
https://en.m.wikipedia.org/wiki/Master_boot_record
MBR is the first 512 bytes of the disk where Ms DOS and such legacy stuff load from. When you tell the Dell BIOS to boot in legacy mode that's where it transfers control to.
Most operating systems leave that first sector alone no matter how the disk is partitioned. A GUID partitioned disk can still have DOS/Linux/whatever/Clover bootloader code stored there.
I've found on my 990s and a couple of Dell notebook that can't seem to boot in UEFI mode that using bios legacy mode with clover installed to the boot sector (MBR) of an otherwise normal GUID / EFI setup solves the problem.
YMMV
edit: I'm not saying start from scratch, run the clover or multibeast installer and tell it to install clover to the MBR. Then run it again doing the correct UEFI install. That should put clover in both locations, so no matter where the BIOS tries to go it finds clover.
MBR is the first 512 bytes of the disk where Ms DOS and such legacy stuff load from. When you tell the Dell BIOS to boot in legacy mode that's where it transfers control to.
Most operating systems leave that first sector alone no matter how the disk is partitioned. A GUID partitioned disk can still have DOS/Linux/whatever/Clover bootloader code stored there.
I've found on my 990s and a couple of Dell notebook that can't seem to boot in UEFI mode that using bios legacy mode with clover installed to the boot sector (MBR) of an otherwise normal GUID / EFI setup solves the problem.
YMMV
edit: I'm not saying start from scratch, run the clover or multibeast installer and tell it to install clover to the MBR. Then run it again doing the correct UEFI install. That should put clover in both locations, so no matter where the BIOS tries to go it finds clover.