efifs
mkinitcpio
efifs | mkinitcpio | |
---|---|---|
11 | 11 | |
495 | 194 | |
- | 0.5% | |
0.0 | 9.3 | |
20 days ago | 8 days ago | |
C | Shell | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
efifs
-
How to Boot ISO Files from GRUB2 Boot Loader
See also UEFI drivers that can read a bunch of other file systems (btrfs, ext2/3/4, HFS, ISO, NTFS, UFS/FFS, XFS, ZFS, etc):
* https://efi.akeo.ie
* https://github.com/pbatard/efifs
The UEFI spec specifies (ยง13.3) that firmware is only required to read FAT32/16/12, which is generally why your /boot/efi is VFAT/FAT32.
-
Is exFAT bootable?Can I boot WinPE with exFAT?
In theory you would still need a FAT32 efi 'stub' partition with the exFAT filesystem drivers which you have to load before loading the WinPE loader (bootmgfw.efi).
-
How do I configure the refind.conf and refind_linux.conf (and or config.yaml (for ZFSBootMenu)) files properly when installing Arch Linux with ZFS Native Encryption?
I am pretty sure that that I am doing something incorrectly with the configuration files for the rEFInd bootloader, but everything else should be correct. However, as I write this, I barely realized did I not use the following commands recommended from the "Usage" section from the aforementioned website where I downloaded the zfs_x64.efi driver file for rEFInd:
-
Grub vs Systemd-boot --removable question
I found the drivers here https://efi.akeo.ie/ . Which means, that any EFI bootloader able to load them will be able to use them. They are not for bootloader, but it is the firmware which will use them. As i said, i am little bit afraid that it will not work on any board as some manufacturers have pretty buggy firmware when talking about infrequently used features. Also i am bit unsure they will work with secure boot as they are gpl3 thus will be never signed by Microsoft and i don't know what UEFI requirements for drivers are in this regard.
-
Why use a bootloader? Just boot directly into a unified kernel image
Even for those using systemd-boot with custom efi drivers to provide functionality, it's worth noting that those drivers are being developed downstream of GRUB.
- Latest grub update on arch distros seems to cause boot issues
-
So why do so people still use GRUB?
I think you can also add btrfs filesystem support for sd-boot by including the EFI drivers for it on the EFI partition instead, from https://github.com/pbatard/efifs/releases I think. Haven't tried it myself though.
- Is any ESP filesystem other than vfat supported on coreboot? (lemp9)
-
Fedora considers deprecating legacy BIOS
EFI doesn't actually mandate FAT for the system partition. The system partition can be any filesystem that the firmware supports.
Of course, pretty much all EFI implementations only support FAT, so it's a bit of a moot point; the only one I'm aware of that supports anything else is the one on Intel Macs, which also understands HFS+.
You can find a huge selection of EFI filesystem drivers at https://efi.akeo.ie/ but they're derived from GRUB and hence GPL, so don't expect the likes of American Megatrends to be bundling these any time soon.
- Help Please! I rebooted my TrueNAS SCALE and get the following.
mkinitcpio
-
Secure boot -- Sign kernel with pacman hook
This file has been changed recently and the wiki still references the old line. You have to modify this line now:
-
Why use a bootloader? Just boot directly into a unified kernel image
mkinitcpio is an arch thing: https://github.com/archlinux/mkinitcpio
-
I share a pacman improvement idea
The Arch Linux devs don't have infinite time and energy, so yes less-important issues that affect less users get diprioritized. You're welcome to PR the fix yourself, here's the mkinitcpio repo: https://github.com/archlinux/mkinitcpio
- Fix for warnings when upgrading kernel?
-
NVIDIA power management not working when modules are in initramfs
The general logic was changed in the new mkinitcpio release. https://github.com/archlinux/mkinitcpio/pull/54/files
-
Problems when booting after every kernel update
That's an odd one since reinstalling the package fixes the issue. I wouldn't be so sure it's grub because it just loads the vmlinuz and initramfs that are suffixed with the pkgbase. That will not change based on the kernel version and pkgrel version. Someone brought up needing a hook. the mkinitcpio package already installs hooks and scripts necessary for maintaining a mkinitcpio prefix for each kernel for the initramfs image generation and installing vmlinuz to /boot/vmlinuz-${pkgbase} on upgrades. Everyone with the official mkinitcpio package is going to have the same /usr/share/libalpm/scripts/mkinitcpio-install shell script. Running grub-mkconfig is pointless for a kernel upgrade for the reason stated. All it does is export variables from /etc/default/grub and concatenates /etc/grub.d/* into a single config file. If there was a grub config issue it's unlikely you would ever be able to boot.
- mkinitcpio v31 released
-
Has your Arch system ever broken?
mkinitcpio made zstd the default on 2021-02-17
- What bootloader do you use and why?
-
Arch Linux - News: Moving to Zstandard images by default on mkinitcpio
The number of thread is, but the compression level isn't. Because -3 is a sane default for the compression level in time of compression time and output file size, but this can differ for your machine. I find that on my machine best compression level is -15 or -16 for size and compression time. Since it will take a 1 second more to compress but it will yield a file 80% more compressed than the default. Here is the pill request where the defaults where changed mkinitcpio#47
What are some alternatives?
uefi-elf-bootloader - UEFI ELF Bootloader example
dracut - dracut the event driven initramfs infrastructure
ReBarUEFI - Resizable BAR for (almost) any UEFI system
sbctl - :computer: :lock: :key: Secure Boot key manager
swtpm - Libtpms-based TPM emulator with socket, character device, and Linux CUSE interface.
mortar - Framework to join Linux's physical security bricks.
BootDuet - Boot sector program for booting Intel's EDK Developer's UEFI Emulation (DUET) from hard disk with LBA.
svntogit-packages - Automatic import of svn 'packages' repo (read-only mirror)
uefi-ntfs - UEFI:NTFS - Boot NTFS or exFAT partitions from UEFI
bootmgr - A configuration framework for EFI boot entries
edk2-platforms - EDK II sample platform branches and tags
UEFI_Basic - A BASIC programming language interpreter for UEFI