There, MBR has no code, and all loaders live on the special EFI partition (which typically should be 200M). AFAIK, UEFI+GPT boot mechanism (like tails.img, according to me) has no such need. When loading a drive, BIOS systems look for code on the first sector (MBR, 512 bytes), ahead of all partitions, which is where the first stage of grub would normally live.

Iso (both tails and all other distros) can only be mounted as cd9660, whereas img (from tails) is a GPT partitioned image with entire payload (1G+) on its single EFI partition (the special one, with partition type ef00): I'm on MBA2013.īoot happens only from tails.img (for USB sticks), but not from tails.iso (for DVD). So the fact that only Tails is working got me curious and I did some digging.

Apparently as read in #7, macs cant boot Ventoy because of their proprietary EFI (Classic Apple lol). I would buy a linux laptop, but I'm still in school so I can't afford one as they tend to be more expensive than parts for a pc. Yeah, the only reason I use a mac is because it's the only non-chromebook laptop I have, I have a PC but its handy to have a laptop to use around the house etc. (long story basically i cant use 'Install mac os' so i had to upgrade from Snow Leopard as its the last to come on DVD)

Sadly, AFAIK you can't downgrade mac firmware, I know because I installed snow leopard onto a mac with El Capitan era firmware. P.s.: Meanwhile i am thinking to leave my MacBook Pro, it's from 2015 and go for a Notebook, it's cheaper for new hardware plus easier to install Linux on it. The weird thing is that i still can enter the 'firmware password' and that works, for example to enter 'Recovery Mode' but i can't put it off or change it. If somebody can help with that i can test some of the possibilities out here. Searched the web but no fix for that one. So, i can't put it off or change it anymore. Since then when i try to put 'firmware password' off to test Ventoy it says that i can't use that symbol in a 'firmware password'. Years ago i have put a 'firmware password', with a symbol in it, because that's a nice extra securety but with one of the latest Catalina Security Updates the 'firmware' was updated. So, i am willing to test but first i have to fix the 'locked out firmware password' problem that i have. I imagin that all people in this discussion can and are willing to test.īut does Ventoy has time and energie to work on this?

Ventoy secure boot