[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

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 revisionPrevious revision
howtos:slackware_admin:set_up_syslinux_as_boot_loader_on_uefi_based_hardware [2016/08/18 23:46 (UTC)] – typos tonberryhowtos:slackware_admin:set_up_syslinux_as_boot_loader_on_uefi_based_hardware [2016/08/18 23:53 (UTC)] (current) – typo tonberry
Line 117: Line 117:
 </code> </code>
  
-That is pretty much it for EFI boot partition. You can do whatever you like with /dev/sda3 (RAID, LUKS, LVM, any filesystem) and install Slackware there, but leave EFI partition alone, that partition needs to be unencrypted and FAT32 formatted.+That is pretty much it for EFI boot partition. You can do whatever you like with /dev/sda2 (RAID, LUKS, LVM, any filesystem) and install Slackware there, but leave EFI partition alone, that partition needs to be unencrypted and FAT32 formatted.
  
  
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 .
 howtos:slackware_admin:set_up_syslinux_as_boot_loader_on_uefi_based_hardware ()