Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware14.2-64bit on one HDD, Slackware64-current on anotherHDD, VoidLinux on Libreboot laptop
Posts: 169
Rep:
Slackware install on GPT HDD
Dear Slackers
My hand was itching to convert MBR to GPT. gdisk was saying some 33 blocks are overlapping, and that it has to be re-sized using other utilities. With system rescue CD, I moved my partitions, so that space was there between sdb1, sdb2. After doing this, slackware did not boot. 99 99 was displayed on monitor. Got fed up. Using gdisk, converted entire disk to GPT. re formatted. Made 3 partitions. Sdb1-swap, sdb2-ef02 for bios-gpt, sdb3 for /, install. Installed slackware14 64 bit. But, I did not install lilo, since I want to install grub2, which is not on install dvd.
I have stopped at this, and posting here. Pl. inform how and where on these three partitions, grub2 is to be installed
Tried to boot second hdd (sdb) from SystemRescue CD, but gave only 99 99 99
Distribution: Slackware14.2-64bit on one HDD, Slackware64-current on anotherHDD, VoidLinux on Libreboot laptop
Posts: 169
Original Poster
Rep:
No UEFI, BIOS
Businesskid,
I had earlier done this on Archlinux (before being banned due to systemd comments) I am familiar with GPT on funtoo linux also. But in slackware, documentation on this is not exhaustive, or I cannot find it
as a boot error is a symptom of an incorrectly set up lilo (or grub). I believe grub2 and some later lilo were for uefi, so you might do better sticking with earlier versions. The bios points the boot at the first 512 bytes of a selected disk. Lilo needs to be rerun each change, grub not so much - which is good because personally I find grub a pig.
The rest of the documentation on slackware is "Figure it out yourself." :-)). You promote yourself to slackware when that's not a big deal for you. Glad to have you on board. As a creature of habit, I always set up /boot as sda1, and swap maybe as sda2. If I go to a GPT disk, I wake up the UEFI in this box (Samsung) which might better be named NLFI (No Linux Firmware Interface
As grub2 is not shipped in Slackware but can be built on a running Slackware system using the SlackBuild available @ http://slackbuilds.org, I'd suggest you first install lilo, then build and install a grub2 package, then replace lilo with grub2.
Or you could skip the "install lilo" step and built grub2 just after you chrooted on your slackware 14, provided you first set up a network connection and download what you need to build a grub2 package.
I hope people don't mind but I am bumping this thread for the benefit of future users who stumble across it. I have now added a short tutorial on docs.slackware.com about using GPT and BIOS, with the various bootloaders now included with Slackware 14.1.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.