20210628 - Upgrade of php fixed the page rendering issue.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
howtos:slackware_admin:set_up_syslinux_as_boot_loader_on_uefi_based_hardware [2016/08/17 10:31 (UTC)]
tonberry typo
howtos:slackware_admin:set_up_syslinux_as_boot_loader_on_uefi_based_hardware [2016/08/18 23:53 (UTC)] (current)
tonberry typo
Line 15: Line 15:
  
 ===== Why UEFI ===== ===== Why UEFI =====
-It is not as though there is some choice; machines nowadays //are// UEFI. One can, however, chose to set UEFI to so called "CSM" or sometimes "Legacy" mode. In this mode, UEFI acts as BIOS, i.e. reads the first sector (MBR) of a hard drive and loads and executes non-UEFI boot loader such as LILO from there. As opposed to UEFI in, say, UEFI mode, when it reads, loads and executes UEFI-aware boot loader from //EFI boot partition//.+It is not as though there is some choice; machines nowadays //are// UEFI. One can, however, choose to set UEFI to so called "CSM" or sometimes "Legacy" mode. In this mode, UEFI acts as BIOS, i.e. reads the first sector (MBR) of a hard drive and loads and executes non-UEFI boot loader such as LILO from there. As opposed to UEFI in, say, UEFI mode, when it reads, loads and executes UEFI-aware boot loader from //EFI boot partition//.
  
 Frankly, there are no compelling reasons not to use CSM (note that it is possible to use [[http://docs.slackware.com/howtos:slackware_admin:installing_with_gpt_without_uefi | GPT partitions without UEFI]]). On the contrary, there are reasons to avoid UEFI booting, because: Frankly, there are no compelling reasons not to use CSM (note that it is possible to use [[http://docs.slackware.com/howtos:slackware_admin:installing_with_gpt_without_uefi | GPT partitions without UEFI]]). On the contrary, there are reasons to avoid UEFI booting, because:
Line 161: Line 161:
       * ''INITRD initrd.gz-4.4.14'' is an initrd image that is mounted as temporary / before the final / is mounted. Typically, an initrd is needed if kernel has to load some additional modules to access the root device, or has to perform some actions to make it accessible (think of RAID, LUKS, LVM). If you do not need initrd, simply delete this line.       * ''INITRD initrd.gz-4.4.14'' is an initrd image that is mounted as temporary / before the final / is mounted. Typically, an initrd is needed if kernel has to load some additional modules to access the root device, or has to perform some actions to make it accessible (think of RAID, LUKS, LVM). If you do not need initrd, simply delete this line.
     * The second menu entry is largely the same, except that there is no '4' in ''APPEND /dev/vgroot/V_ROOT''. Simply put, this is non-graphical safe mode. If X window system fails to start for whatever reason, you may end up with not only black screen, but also blocked keyboard and mouse and therefore unable to fix the cause. So it is a good idea to have this option prepared beforehand (another method to use otherwise unusable machine with broken X is to SSH-in, though it is a less reliable method).     * The second menu entry is largely the same, except that there is no '4' in ''APPEND /dev/vgroot/V_ROOT''. Simply put, this is non-graphical safe mode. If X window system fails to start for whatever reason, you may end up with not only black screen, but also blocked keyboard and mouse and therefore unable to fix the cause. So it is a good idea to have this option prepared beforehand (another method to use otherwise unusable machine with broken X is to SSH-in, though it is a less reliable method).
-<file /boot/efi/EFI/SYSLINUX/syslinux.cfg>+<file /boot/efi/EFI/SYSLINUX/syslinux.cfg>
 UI menu.c32 UI menu.c32
 PROMPT 0 PROMPT 0
Line 182: Line 182:
 </file> </file>
  
-  * Still in /boot/efi/EFI/SYSLINUX, copy kernel here. Huge is safer option. Generic may require initrd and more modules in it. If you do not know which they are, the machine might not boot, so go with the huge.+  * Still in /boot/efi/EFI/SYSLINUX, copy kernel here. Huge is the safer option. Generic may require initrd and more modules in it. If you do not know which they are, the machine might not boot, so go with the huge.
 <code> <code>
 # cp /boot/vmlinuz-huge-4.4.14 . # cp /boot/vmlinuz-huge-4.4.14 .

In Other Languages
QR Code
QR Code howtos:slackware_admin:set_up_syslinux_as_boot_loader_on_uefi_based_hardware (generated for current page)