you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 3 years ago (1 child)

UEFI forum made it a requirement for motherboard constructors (hp, dell, msi...) to make their UEFI implementation to be able to at least read fat(12/16/32) filesystems. That is why you need a fat(12/16/32) partition flagged ESP (efi system partition) for holding your boot files.

So, I dont think you can do that unless you fall back to the old outdated BIOS or you have some *nix filesystem in your uefi implementation which I dont trust.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 3 years ago (2 children)

    You're only partially correct. /boot doesn't have to also be your EFI partition. In fact, most distros by default will separate the two, with the EFI partition mounted at /boot/efi and /boot being a separate ext4 based partition. My suggestion is that, if you're running BTRFS, you should merge /boot and / as one partition. You're still free to have a FAT32-based EFI mounted at /boot/efi or better yet /efi.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 3 years ago (1 child)

    I use systemd-boot and my mount point is /efi. /efi/EFI/ is where my bootloaders live.

    If I rollback to an old enough snapshot, I have to reinstall my kernels from a chroot. It'd be cool if I could get around that.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 3 years ago (1 child)

    It has been a while since I used grub that I forgot tgat esp could only be used to hold the boot files residing on /boot/efi.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 3 years ago (1 child)

    I am guessing you're on systemd-boot? Yeah, one of the reasons why I hesitate to use it is how it requires EFI contain the kernel images. I am currently using refind.

  • source
  • parent
  • hideshow 2 child comments