[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
Next revision
Previous revision
Last revisionBoth sides next revision
howtos:slackware_admin:installing_with_gpt_without_uefi [2013/11/13 09:03 (UTC)] – [Extlinux (Syslinux)] ruariohowtos:slackware_admin:installing_with_gpt_without_uefi [2013/11/13 20:35 (UTC)] – [Extlinux (Syslinux)] ruario
Line 1: Line 1:
 ====== Installing Slackware Using GPT with a BIOS motherboard ====== ====== Installing Slackware Using GPT with a BIOS motherboard ======
  
-It is possible to install Slackware to a disk that uses a GUID Partition Table (GPT), even on a machine that uses BIOS (i.e. you do not need a UEFI-based machine). Using GPT allows you to install Slackware onto very large disk drives (the theoretical maximum addressable disk size is 2 ZiB). Partitioning should be done prior to starting the 'install' script. However you must use a GPT aware partitioning tool, e.g. gdisk, cgdisk or parted. The main sections below explain how to setup various popular boot loaders. +It is possible to install Slackware to a disk that uses a GUID Partition Table (GPT), even on a machine that uses BIOS (i.e. you do not need a UEFI-based machine). Using GPT allows you to install Slackware onto very large disk drives (the theoretical maximum addressable disk size is 2 ZiB). As always, partitioning should be done prior to starting the 'setup' script, however you must use a GPT aware partitioning tool, e.g. gdisk, cgdisk or parted (all of which are included with Slackware). The main sections below explain how to setup various popular boot loaders. 
  
 ==== LILO ==== ==== LILO ====
  
-Skip the bootloader (LILO) section during install (LILO works but as of Slackware 14.1, liloconfig doesn't detect GPT partitions)After installation is complete, [[#Accessing the Slackware install, prior to bootloader installation|enter your local Slackware install]]. From here, customize the example /etc/lilo.conf to put LILO into the protective MBR and add entries for your chosen kernel(s). Finally, issue the 'lilo' command.+LILO should just workHowever some people have reported issues with liloconfig not detecting GPT partitions. If you encounter this issue skip automatic LILO configuration. Then after installation is complete, [[#Accessing the Slackware install, prior to bootloader installation|enter your local Slackware install]]. From here, customize /etc/lilo.conf_example and save it as /etc/lilo.conf. You will need to set LILO to install to the protective MBR of your primary disk and add entries for your chosen kernel(s), in addition to any other changes you see fitOnce you have done this, issue the 'lilo' command. 
 + 
 +<note warning>Whilst LILO works well with any file system format that is compatible with the FIBMAP ioctl (required to map files to block numbers), you are likely to have issues when /boot is located on XFS, Btrfs or Nilfs2. You can avoid this by making an ext2 /boot partition or using a different bootloader.</note>
  
 ==== Grub 2 ==== ==== Grub 2 ====
  
-If you want to use Grub 2, make sure you have a 'BIOS boot partition' (partition type EF02 in gdisk or cgdisk) somewhere on disk (at the start seems sensible). It should be at least 1MiB. Skip the bootloader (LILO) section during install. After installation is complete, [[#Accessing the Slackware install, prior to bootloader installation|enter your local Slackware install]]. Finally, issue the following to actually install Grub 2 as your bootloader:+If you want to use Grub 2, make sure you have a 'BIOS boot partition' (partition type EF02 in gdisk or cgdisk). This can be anywhere on disk though putting it at the start seems sensible. It is recommended that it be at least 1MiB. Skip the bootloader (LILO) section during install. After installation is complete, [[#Accessing the Slackware install, prior to bootloader installation|enter your local Slackware install]]. Finally, issue the following to actually install Grub 2 as your bootloader:
  
 <code> <code>
Line 72: Line 74:
 </code> </code>
  
-<note important>This assumes you are using the disk /dev/sd**a** and the **3.10.17-smp** kernels, adjust as needed.</note>+<note important>The assumes Slackware is installed on your /dev/sd**a1** partition and you are using the **3.10.17-smp** kernels, adjust as needed.</note>
  
 ==== Accessing the Slackware install, prior to bootloader installation ==== ==== Accessing the Slackware install, prior to bootloader installation ====
  
-In all of the examples, final installation of the bootloader is done from //within// the installed Slackware system. There are two ways to get into your Slackware install, prior to the installation of the bootloader. You can use chroot ('//chroot /mnt//') from the shell prompt provided by the install media, after you have finished the basic installation, i.e. after the message “Installation of Slackware Linux is complete”. Alternatively Slackware's install media 'boot: ' prompt includes help text explaining how to boot the installed Slackware system, rather than the install environment (i.e. at the boot prompt type something like '//**hugesmp.s** root=/dev/sd**a1** rdinit= ro//').+In all of the bootloader installation examples above, final installation of the bootloader is done from //within// the installed Slackware system. There are two ways to get into your Slackware install, prior to the installation of the bootloader. You can use chroot ('//chroot /mnt//') from the shell prompt provided by the install media, after you have finished the basic installation, i.e. after the message “Installation of Slackware Linux is complete”. Alternatively Slackware's install media 'boot: ' prompt includes help text explaining how to boot the installed Slackware system, rather than the install environment (i.e. at the boot prompt type something like '//**hugesmp.s** root=/dev/sd**a1** rdinit= ro//').
  
-<note important>The final example assumes you are using /dev/sd**a1** and the **hugesmp.s**, adjust as needed.</note>+<note important>The final example assumes Slackware is installed on your /dev/sd**a1** partition and you wish to boot with the **hugesmp.s** kernel, adjust as needed.</note>
  
 ====== Sources ====== ====== Sources ======
 howtos:slackware_admin:installing_with_gpt_without_uefi ()