4 ms·

Out of curiosity, why have you disabled it?

by btgeekboy 10y ago

Esau 10y ago
I can't speak for OP but for me, I disable it because UEFI is an over-engineered mess that solves no problems for me.
- swiley 10y ago
  I love EFI! No more bootloaders!!!! Just rename your bzimage bzimage.efi, put it on a FAT fs, and select it with the firmware!
  - alerighi 10y ago
    Yes, and if for some reason then you clear the CMOS (BIOS configuration error, discharged battery, or whatever) you can no longer boot your PC because the boot information regarding the parameters to pass to the kernel is lost...
    - floatboth 10y ago
      That's why EFI variables should never be used. Just put whatever you want to boot into BOOTX64.EFI!
      - hollander 10y ago
        Ah the lovely naming hacks of UEFI. :-P I remember the troubles it took to boot Ubuntu on a Lenovo laptop because the EFI was 32 bit, while the system supported 64 bit.
        floatboth 10y ago
        Yeah, old devices with 32-bit EFI… I have a Mac mini 2006 (upgraded to 2007). I compiled GRUB 2 for 32-bit EFI and it boots 64-bit FreeBSD from ZFS just fine :)
    - swiley 9y ago
      Then just select it again? It's maybe 4 key presses unless you have a lot of .efi files laying around...
    - JdeBP 9y ago
      EFI variables are not stored in the "CMOS", note (misnomer that that is). They are stored in flash RAM. * https://superuser.com/a/708332/38062 https://superuser.com/a/708332/38062
- abrowne 10y ago
  You realize that in most cases "disabling UEFI" is really enabling a poorly-tested emulation of BIOS running on top of UEFI?
int_19h 10y ago
Not OP, but I also disable it on my home boxes that run Linux, mainly because 1) I know how the BIOS boot process works very well (and I kinda like knowing how things work, especially on critical paths that can get broken sometimes), and 2) I know how to set up Linux with BIOS boot because I did it so many times before. So I guess it boils down to "it's not broken for me, why change it?"
- bitwize 10y ago
  Why would you do this? I doubt support for legacy mode will exist for much longer, either on motherboards or in distributions.
  - int_19h 9y ago
    I would be surprised if distros got rid of it anytime soon. There's still a vast amount of relatively old non-UEFI hardware that people still use, and it's not going to suddenly change, because that hardware is plainly "good enough" for all practical purposes - so it's only going to be replaced if and when it fails. Even Windows hasn't so much as announced a switch to UEFI boot only, and Linux generally supports old hardware for much longer. So I wouldn't be surprised if it's still there in a decade - maybe not in all distros, but at least in some mainstream ones, especially more "hackerish" like Arch and Gentoo. As for motherboards, I doubt they'd get rid of it that soon, either. If only because having it there means that OEMs can ship devices with FreeDOS preinstalled to dodge the licensing fees. As I understand, legacy mode is basically just an emulation layer on top of UEFI, and it's fairly cheap (and already there). This is different for mobile and tablet devices like Surface, which aren't really advertised as general-purpose PCs in the first place. Since they're only expected to run whatever's preinstalled on them, so long as it only needs UEFI, they will likely ship with UEFI only. But I'm not running Linux on such things.
- floatboth 10y ago
  Because it's old. Because it's painfully slow. Because messing with a FAT partition feels much better than messing with MBR or whatever weird "boot partition" thing that happens in a "legacy-BIOS-plus-GPT" situation.

Out of curiosity, why have you disabled it?

Esau 10y ago

I can't speak for OP but for me, I disable it because UEFI is an over-engineered mess that solves no problems for me.

swiley 10y ago
I love EFI! No more bootloaders!!!! Just rename your bzimage bzimage.efi, put it on a FAT fs, and select it with the firmware!
- alerighi 10y ago
  Yes, and if for some reason then you clear the CMOS (BIOS configuration error, discharged battery, or whatever) you can no longer boot your PC because the boot information regarding the parameters to pass to the kernel is lost...
  - floatboth 10y ago
    That's why EFI variables should never be used. Just put whatever you want to boot into BOOTX64.EFI!
    - hollander 10y ago
      Ah the lovely naming hacks of UEFI. :-P I remember the troubles it took to boot Ubuntu on a Lenovo laptop because the EFI was 32 bit, while the system supported 64 bit.
      - floatboth 10y ago
        Yeah, old devices with 32-bit EFI… I have a Mac mini 2006 (upgraded to 2007). I compiled GRUB 2 for 32-bit EFI and it boots 64-bit FreeBSD from ZFS just fine :)
  - swiley 9y ago
    Then just select it again? It's maybe 4 key presses unless you have a lot of .efi files laying around...
  - JdeBP 9y ago
    EFI variables are not stored in the "CMOS", note (misnomer that that is). They are stored in flash RAM. * https://superuser.com/a/708332/38062 https://superuser.com/a/708332/38062
abrowne 10y ago
You realize that in most cases "disabling UEFI" is really enabling a poorly-tested emulation of BIOS running on top of UEFI?

int_19h 10y ago

Not OP, but I also disable it on my home boxes that run Linux, mainly because 1) I know how the BIOS boot process works very well (and I kinda like knowing how things work, especially on critical paths that can get broken sometimes), and 2) I know how to set up Linux with BIOS boot because I did it so many times before. So I guess it boils down to "it's not broken for me, why change it?"

bitwize 10y ago
Why would you do this? I doubt support for legacy mode will exist for much longer, either on motherboards or in distributions.
- int_19h 9y ago
  I would be surprised if distros got rid of it anytime soon. There's still a vast amount of relatively old non-UEFI hardware that people still use, and it's not going to suddenly change, because that hardware is plainly "good enough" for all practical purposes - so it's only going to be replaced if and when it fails. Even Windows hasn't so much as announced a switch to UEFI boot only, and Linux generally supports old hardware for much longer. So I wouldn't be surprised if it's still there in a decade - maybe not in all distros, but at least in some mainstream ones, especially more "hackerish" like Arch and Gentoo. As for motherboards, I doubt they'd get rid of it that soon, either. If only because having it there means that OEMs can ship devices with FreeDOS preinstalled to dodge the licensing fees. As I understand, legacy mode is basically just an emulation layer on top of UEFI, and it's fairly cheap (and already there). This is different for mobile and tablet devices like Surface, which aren't really advertised as general-purpose PCs in the first place. Since they're only expected to run whatever's preinstalled on them, so long as it only needs UEFI, they will likely ship with UEFI only. But I'm not running Linux on such things.
floatboth 10y ago
Because it's old. Because it's painfully slow. Because messing with a FAT partition feels much better than messing with MBR or whatever weird "boot partition" thing that happens in a "legacy-BIOS-plus-GPT" situation.