68 points
*

EFI is so much better

permalink
report
reply
31 points

GPT you mean. Linux can boot in a non-EFI machine that has GPT disk partitions… Windows can’t because it’s dumb.

permalink
report
parent
reply
33 points

Yes but by doing so you’re using the same principles as MBR boot. There’s still this coveted boot sector Windows will attempt to take back every time.

What’s nice about EFI in particular is that the motherboard loads the file from the ESP, and can load multiple of them and add them to its boot menu. Depending on the motherboard, even browse the ESP and manually go execute a .efi from it.

Which in turn makes it a lot less likely to have bootloader fuckups because you basically press F12 and pick GRUB/sd-boot and you’re back in. Previously the only fix would be boot USB and reinstall syslinux/GRUB.

permalink
report
parent
reply
10 points

I just had a bug on both of my EFI computers where they wouldn’t boot any more and a grub-install fixed it, apparently the regular update processes do not update the version on the ESP for some reason and my assumption is that it became incompatible with the modules in /boot

Adding an EFI Boot Entry for netboot.xyz after it happened on the first one really helped fix the second one though.

permalink
report
parent
reply
19 points

I’m not having an AI boot my computer!

permalink
report
parent
reply
14 points

GPT is a partitioning table. EFI is a bootloader firmware interface.

permalink
report
parent
reply
2 points

MBR is also a partitioning table.

permalink
report
parent
reply
4 points

No I mean EFI. It is a much simpler than MBR.

permalink
report
parent
reply
-4 points

Not in my experience… and apparently a lot of people that dual boot 🤷.

My main boot partitions are far from the 2TB threshold of MBR, I’m not that rich.

permalink
report
parent
reply
6 points

Yeah cause that’s the only benefit 🙄

permalink
report
parent
reply
1 point

I can’t see any other really 🤷.

permalink
report
parent
reply
-8 points

Not sure if serious.

permalink
report
parent
reply
26 points

Start using and efistub and never worry about boot loaders again!

permalink
report
reply
32 points

systemd-boot is a reasonable compromise. i like it

permalink
report
parent
reply
9 points

The reality is that a bootloader will seemingly always be needed to account for difficult BIOS’ and legacy setups (I’m looking at you, dual-booted Ubuntu 20.04).

permalink
report
parent
reply
7 points

Naah I just disable secure boot altogether, then you don’t have to worry about all that TPM security theatre.

permalink
report
parent
reply
21 points

You don’t need secure boot to use EFI. It’s better all around regardless of SB.

permalink
report
parent
reply
4 points

Fair enough I don’t miss the old BIOS.

permalink
report
parent
reply
3 points
*

Yeah, but Windows 11 needs it.

Can be disabled though. Easiest way - use Rufus when burning the USB.

Fun fact, you can also install Win11 in MBR mode, no UEFI needed whatsoever.

permalink
report
parent
reply
17 points

Do we really ever fix the bootstrap, or does the bootstrap fix us?

permalink
report
reply
17 points

Ah yes, simplicity. MBR, with all its limitations had one killer feature: it was extremely simple.

UEFI, as powerful as it is, is the opposite of simple. Many moving parts, so many potential failure points. Unfortunately, it seems like modern software is just that: more complex and prone to failure.

permalink
report
reply
7 points

Exactly why old devices are so hard to break - they’re incredibly simple.

To be honest, I see nothing wrong with MBR boot, it does the job, I’ll use it till I can or till it doesn’t do the job I want/need.

permalink
report
parent
reply
6 points

I work in IT for many years and I think your last sentence is very true. And is also why the industry is so lucrative haha

permalink
report
parent
reply
3 points

True, but… When MBR Grub drops to rescue or doesn’t appear at all, it’s not only difficult (at least for newbies) but somewhat random if you can actually boot a given OS. With EFI Grub, I’ve often managed to boot using BIOS boot override to launch a usable Grub configuration.

permalink
report
parent
reply
1 point

Actually grub 0.x series had much more useful rescue shell tab completion than the latest release. You could easily list all boot devices, partitions, and even filesystems and their contents. All from the rescue shell. Consequently, you could boot into Linux and reinstall grub in the MBR to fix it. All that without using a boot CD/USB! Good luck doing that with the latest version of grub and UEFI.

Also getting into the BIOS on legacy firmware was also very simple. On most machines it’s the three finger salute followed by either F1, Delete or rarely F11 or F12.

The boot process was simple, and the BIOS had just one simple task: load and execute the first 512 bytes of the disk that was designated as the boot device. That’s it.

permalink
report
parent
reply
3 points

Asus --> Del - Enter BIOS, F8 - Boot menu (very confusing since Windows also uses F8 for the recovery mode boot menu, so you have to press F8, then when the boot menu appears, chose the boot device, then have one hand on Enter and the other on F8 again, so that you hit Enter and start tapping like crazy on F8 to enter the rescue mode menu… annoying as hell)

GigaByte --> Del or F2 - Enter BIOS, F12 - Boot menu, Alt + F10 - Copy main BIOS to backup BIOS

MSI --> Del or F2 - Enter BIOS, F11 - Boot menu

ASRock --> Del or F2 - Enter BIOS, F11 or F10 - Boot menu

Biostar --> Del - Enter BIOS, F9 - Boot menu

Intel --> F2 - Enter BIOS, F10 or F12 - Boot menu

I used to remember some of the brand name PCs as well, but time has gotten the best of me 🤷.

The boot process was simple, and the BIOS had just one simple task: load and execute the first 512 bytes of the disk that was designated as the boot device. That’s it.

This is actually what I love about MBR nowadays. It’s simple enough so no one wants to mess with it and render the rig unbootable and obscure enough so no one (MS) actually checks if there is anything there that might trigger warnings (non-MS code).

permalink
report
parent
reply
1 point

You just fix grub with a live usb, it’s not that difficult.

permalink
report
parent
reply
3 points

“Not that difficult” but still more difficult than being able to boot without a separate live USB drive.

permalink
report
parent
reply
15 points

I once fucked up my grub.cfg, wrote over the part needed to unencrypt. Had no idea what had happened. Was a fun night :)

permalink
report
reply
1 point
*

This was probably before you used BTRFS, right? RIGHT?!?

permalink
report
parent
reply
1 point

I don’t know much about btrfs, how would that help ?

permalink
report
parent
reply
2 points

You can use snapshots. Like f up something, roll back a snapshot from an hour ago, all is good and dandy 😉.

permalink
report
parent
reply

linuxmemes

!linuxmemes@lemmy.world

Create post

I use Arch btw


Sister communities:
Community rules
  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

Community stats

  • 7.3K

    Monthly active users

  • 1.2K

    Posts

  • 65K

    Comments