¡Esta es una revisión vieja del documento!
Tabla de Contenidos
Opciones del kernel de Linux para UEFI y ELILO
El propósito de este artículo es informar al usuario sobre las opciones de kernel necesarias para el arranque desde UEFI, y cierta información sobre cómo funcionan ELILO y quizás otros cargadores de arranque EFI, ya que actualmente es difícil de encontrar y entender en línea.
Opciones de kernel requeridas para el soporte UEFI
Las siguientes opciones son necesarias para arrancar un kernel desde UEFI. Estos ya están establecidos en los núcleos de Slackware.
- Enable the block layer
- Partition Types
- Advanced partition selection
- EFI GUID Partition support (CONFIG_EFI_PARTITION [=y])
- Processor type and features
- EFI runtime service support (CONFIG_EFI [=y])
- EFI stub support (CONFIG_EFI_STUB [=y])
- Build a relocatable kernel (CONFIG_RELOCATABLE [=y])
- Device Drivers
- Graphics support
- Support for frame buffer devices (CONFIG_FB [=y])
- EFI-based Framebuffer Support (CONFIG_FB_EFI [=y])
- File systems
- Miscellaneous filesystems
- EFI Variable filesystem (CONFIG_EFIVAR_FS [=y])
- Firmware Drivers
- EFI (Extensible Firmware Interface) Support
- EFI Variable Support via sysfs (CONFIG_EFI_VARS [=n])
ya que está en desuso a favor de CONFIG_EFIVAR_FS, porque tiene un límite de tamaño de variable de 1024 bytes, y porque puede causar problemas de inconsistencia de datos.
Sin embargo, si lo deshabilita, necesitará un enlace del programa efibootmgr
que admite el nuevo sistema de archivos Variable EFI.
Usando el nuevo sistema de archivos variable EFI
Para utilizar la nueva interfaz del sistema de archivos de variables EFI, debe eliminar el antiguo programa “efibootmgr” y reemplazarlo por uno nuevo que admita el sistema de archivos de variables EFI.
- Descargue e instale: https://github.com/vathpela/efivar
- Descargue e instale: https://github.com/vathpela/efibootmgr/tree/libefivars
- Correr:
modprobe efivarfs mount -t efivarfs efivarfs /sys/firmware/efi/efivars efibootmgr
The EFI System Partition (ESP)
In order to boot from UEFI you need to create an EFI System Partition (ESP) using gdisk
or cgdisk
instead of the old fdisk
and cfdisk
. The Slackware README_UEFI.TXT recommends a size of 100M, which is also the minimum partition size (except for 4K native drives, where it is 260M). You also need to set the partition hex code to EF00
, which identifies it as the ESP.
UEFI and ELILO
During the install procedure of Slackware 14.1 for ELILO (the eliloconfig
script), the following happens and is required for booting from UEFI using ELILO.
- The EFI System Partition (ESP) is located and mounted. On a running system it is usually found already mounted at
/boot/efi
. This is a special FAT partition that is basically the UEFI firmware replacement of what the MBR was for BIOS. However, it can not only hold a bootloader (all the MBR was capable of), but also config files, the kernel, and other things you might want to access using the UEFI firmware. - The three items required by ELILO (and other bootloaders) are copied onto the ESP to
/boot/efi/EFI/Slackware
. These include:- The bootloader. In the case of ELILO it is
elilo.efi
- The config file. In the case of ELILO it is
elilo.conf
- The kernel, usually titled
vmlinuz
- A boot entry variable is registered in the UEFI firmware using
efibootmgr
. The exact command that is run isEFI_DEVICE=$(mount | grep vfat | grep -w /boot/efi | cut -b 1-8) EFI_PARTITION=$(mount | grep vfat | grep -w /boot/efi | cut -f 1 -d ' ' | cut -b 9-) efibootmgr -q -c -d $EFI_DEVICE -p $EFI_PARTITION -l "\\EFI\\Slackware\\elilo.efi" -L "Slackware"
so if
mount
outputs/dev/sda1 on /boot/efi type vfat (rw)
EFI_DEVICE would be
/dev/sda
and EFI_PARTITION would be1
, each components of/dev/sda1
, which is the ESP.
/EFI/boot/bootx64.efi
. This special location allows the UEFI firmware to run the bootloader without any boot entry.
Upgrading your kernel
This task is now much easier than it used to be. All you really need to do is copy vmlinuz
onto the ESP on top of the old kernel. No need to edit any configs or add any boot entries, unless you want to. Note that you can edit the config in place and ELILO will pick up the changes on next boot, no need to run any commands like with the old lilo.
Updating your UEFI firmware
As all UEFI firmware has a flashing utility built-in, it is now much easier to update the firmware. All you have to do is copy the new firmware onto the ESP and the UEFI firmware should recognize it when you go to the flashing utility menu. However, remember that flashing the firmware can still potentially brick the system, especially if it is interrupted during the flashing process.
My UEFI settings were reset and I can't boot, or planning ahead to avoid surprises
This can happen either after updating the UEFI firmware or after replacing the CMOS battery. There are three main ways to fix it:
- Probably the easiest and most convenient way is to use the default boot location. Note that some UEFI firmwares do NOT support the default boot location, so this will not work. However, if it does, you won't have to worry about the system not booting again. To do this you can boot into the Slackware install DVD, mount the ESP and copy the files to the following places:
elilo.efi
→/EFI/boot/bootx64.efi
elilo.conf
→/EFI/boot/elilo.conf
vmlinuz
→/EFI/boot/vmlinuz
- You can boot into the Slackware install DVD, run through the menus, and reinstall elilo.
- You can download and install one of the following EFI shells to the root directory of your ESP (that is
/
NOT/EFI
).- Boot into the shell and run:
bcfg boot add 0 fs0:\EFI\Slackware\elilo.efi Slackware