[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.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
howtos:installing_on_uefi_hardware [2012/09/18 08:41 (UTC)] – [Sources] ruario | howtos:installing_on_uefi_hardware [2012/09/20 06:54 (UTC)] – [Tips on install when not using BIOS legacy mode] / Slackware 14.0RC5 uses kenel 3.2.29 so I switched the example to match it ruario | ||
---|---|---|---|
Line 1: | Line 1: | ||
<!-- Add your text below. We strongly advise to start with a Headline (see button bar above). --> | <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). --> | ||
- | ====== | + | ====== |
Some modern computers have started to offer motherboards that use Unified Extensible Firmware Interface (UEFI) as a replacement for the traditional BIOS. Slackware is perfectly capable or running on such machines, albeit with the provisos that the official install media cannot be booted via UEFI directly and no UEFI bootloader is provided as part of the official selection of packages. | Some modern computers have started to offer motherboards that use Unified Extensible Firmware Interface (UEFI) as a replacement for the traditional BIOS. Slackware is perfectly capable or running on such machines, albeit with the provisos that the official install media cannot be booted via UEFI directly and no UEFI bootloader is provided as part of the official selection of packages. | ||
Line 16: | Line 16: | ||
===== Creating your own install media ===== | ===== Creating your own install media ===== | ||
- | The easiest way to make your own Slackware UEFI-capable install media is to create a USB boot disk. To do so you may need to use a second machine. Alternatively you can use the target machine directly if it has another OS installed that provides a GPT (GUID Partition Table) capable | + | The easiest way to make your own Slackware UEFI-capable install media is to create a USB boot disk. To do so you may need to use a second machine. Alternatively you can use the target machine directly if it has another OS installed that provides a GPT (GUID Partition Table) capable |
- | The USB disk you are going to use as install media will need to be partitioned with a GPT partitioning | + | The USB disk you are going to use as install media will need to be partitioned with a GPT scheme. It will need to have a UEFI System Partition as a bare minimum. This system partition is used by UEFI to hold a UEFI-capable bootloader(s) and configuration file(s), along with one or more kernels. The system partition must use a FAT32 filesystem (or it can be HFS+ if your machine is using Apple-based hardware) and must be big enough to hold the Slackware install media' |
- | Once the system partition has been created add a ./EFI/BOOT/ directory structure to this partition, into which you use place an EFI-capable bootloader which should be named BOOTX64.EFI if your PC is x86_64 capable. This exact naming (./ | + | Once the system partition has been created add a ./EFI/BOOT/ directory structure to this partition, into which you place an EFI-capable bootloader, which should be named BOOTX64.EFI if your PC is x86_64 capable. This exact naming (./ |
- | Whilst you can use any EFI-capable bootloader, it is recommend you use Elilo. Elilo is very simple to use and configure, it is reliable and works in a similar manor to Lilo. As such it should feel familiar to most Slackware users, given that Lilo is Slackware' | + | Whilst you can use any EFI-capable bootloader, it is recommend |
Into the same directory on your system partition (./ | Into the same directory on your system partition (./ | ||
Line 37: | Line 37: | ||
</ | </ | ||
- | You should now have a USB disk that you can boot from, though you may need to configure your UEFI to consider this the first boot disk (refer to your manufacturer' | + | You should now have a USB disk that you can boot from, though you may need to configure your UEFI to consider this the first boot disk (refer to your manufacturer' |
- | In addition to the system partition you may wish to have a second partition that holds the rest of the Slackware installation files. This can be formatted with any filesystem supported by the the huge.s kernel. This partition can be mounted after you have booted from your installation partition, | + | In addition to the system partition you may wish to have a second partition that holds the rest of the Slackware installation files. This can be formatted with any filesystem supported by the the huge.s kernel. This partition can be mounted after you have booted from your install media and used as a source of packages during installation. Alternatively you can insert an official Slackware CD or DVD once setup is up and running, or perform a network installation. |
- | ===== Bootstrap the Slackware installation via another distro' | + | ===== Bootstrap the Slackware installation |
Making your own boot media is almost always preferable but if this does not suit you for some reason, you can often use the UEFI-capable install media from another distro. The steps are as follows: | Making your own boot media is almost always preferable but if this does not suit you for some reason, you can often use the UEFI-capable install media from another distro. The steps are as follows: | ||
Line 68: | Line 68: | ||
</ | </ | ||
- | After umounting and removing the install media you should now be able to reboot into your new Slackware install (you may need to change the boot order in your UEFI). | + | After umounting and removing the install media you should now be able to reboot into your new Slackware install (you may need to change the boot order in your UEFI again if you adjusted it previously). |
- | Finally, after booting into Slackware remember to configure an initrd for the generic kernel and copy both over to the local system partition. A further adjustment to the elilo.conf to account for this could look something like the following (assuming a 3.2.28 kernel): | + | Finally, after booting into Slackware remember to configure an initrd for the generic kernel and copy both over to the local system partition. A further adjustment to the elilo.conf to account for this could look something like the following (assuming a 3.2.29 kernel): |
< | < | ||
Line 77: | Line 77: | ||
default=generic | default=generic | ||
- | image=vmlinuz-generic-3.2.28 | + | image=vmlinuz-generic-3.2.29 |
label=generic | label=generic | ||
initrd=initrd.gz | initrd=initrd.gz | ||
Line 94: | Line 94: | ||
<!-- Authors are allowed to give credit to themselves! --> | <!-- Authors are allowed to give credit to themselves! --> | ||
* Originally written by [[wiki: | * Originally written by [[wiki: | ||
- | <!-- * Contributions by [[wiki: | ||
* Further UEFI Linux booting options: [[http:// | * Further UEFI Linux booting options: [[http:// | ||
+ | <!-- * Contributions by [[wiki: | ||
<!-- Please do not modify anything below, except adding new tags.--> | <!-- Please do not modify anything below, except adding new tags.--> | ||
<!-- You must remove the tag-word " | <!-- You must remove the tag-word " | ||
- | {{tag> | + | {{tag> |