[SOLVED] Newbie Request, but Think I want it from Slackware People
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.
Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 41945087 41943040 20G 83 Linux
/dev/sda2 41945088 962594815 920649728 439G 83 Linux
I am not sure what an EFI System Partition is, and I don't think I have one, and maybe that's a nice chunk of my problem....?
I think the sda1 partition was meant to be your EFI partition, but it has the wrong partition type (it should be a VFAT one, not Linux) and it must be formatted as fat32, with the right EFI files IN them. After that, it normally is mounted in Linux as /boot/EFI (with sda2 being yoour root (/) partition).
ehartman gave me a clue that my problem was I configured my disk per BIOS system instructions and not for EFI. I am organizing all my files and backing them up with a new storage location. When I am done with that, I will start all over from scratch, configuring my disk and installing slackware, and will need a nice source of instructions for setting up for EFI and elilo. Because I set up for BIOS, I believe, I was not able to get Slack to run without creating a boot stick. When I do it over, I think I will not need a boot stick.
Just adding a note - gparted has a flags column; mine is empty. It should have a boot flag, I believe, on my root partition. I have no flags at all. I see how to flag the proper partition for boot but I am not going to bother trying it before doing what business kid said:
Quote:
OK. make sure tp partition with GPT partitions (use gdisk).Also set the partitions as required for EFI.
Let's make that: lilo and/or grub do not care for ....
They determine the "bootable" partition from their config files.
If you've installed lilo or grub to a partition instead of the MBR, and you've left the MBR untouched except for partition table stuff, then the code in the MBR does care. In order to load LILO, or the zeroeth GRUB stage from a partition, that partition has to be bootable.
I am still trying to figure out how I want to boot. I seem to have read everything I can easily find regarding lilo, elilo, MBR, EFI, UEFI, BIOS, GPT, syslinux, rEFInd, (I would include GRUB but GRUB sounds like the only thing I am sure I want to stay away from), and how to configure and install a boot system.
I guess I must kinda understand it all but ..... it doesn't click for me what my choice should be.
I can't figure out the mechanics for installing any of the options, anyway. I would have been up and running by now with elilo, which is apparently what my boot stick uses, if what I read on docs.slackware.com was true:
Quote:
During the installation Slackware prompts you about installing ELILO to the EFI partition. If you choose to install it, a directory will be created on the EFI partition (EFI/Slackware) and the ELILO EFI binary (elilo.efi) will be placed there. The directory will also hold an elilo.conf file and a copy of the kernel image (vmlinuz). You should be able to boot into your Linux system right away.
[By the way, what are the (what is a) disadvantage(s) of having the kernel in my EFI partition? I heard that was a downside.]
Fact is, when I am in setup, I can find no place where ELILO is mentioned; I cannot after all these weeks figure out a way to install it. So my main question is, when I had my son create an installation USB drive for me (to help earn his way to go to Italy), was it possible for him to create an outdated one with no ELILO option? But if that were the case, how could this installation disk then create a USB boot drive that uses ELILO?
This time, I used fdisk to create a GPT and partition my /dev/sda, and I formatted them as follows:
sda1 EFI 500M type efi FAT32
sda2 / 30G type Linux filesystem EXT4
sda3 /home 427.3G type Linux filesystem EXT4
sda4 Swap 8G type Linux swap EXT4
[By the way, what are the (what is a) disadvantage(s) of having the kernel in my EFI partition? I heard that was a downside.]
I don't know of any downsides with this... just that you would typically have the kernel in /boot/ and on the EFI partition. Although, technically, the kernel doesn't need to be on /boot/ since it is already on the EFI, but most do it for historical reasons.
Quote:
Originally Posted by samtsco
Fact is, when I am in setup, I can find no place where ELILO is mentioned; I cannot after all these weeks figure out a way to install it. So my main question is, when I had my son create an installation USB drive for me (to help earn his way to go to Italy), was it possible for him to create an outdated one with no ELILO option? But if that were the case, how could this installation disk then create a USB boot drive that uses ELILO?
From my own testing, some motherboards may provide two methods of booting a USB drive. EFI and legacy. I HAD to choose EFI if I wanted to install elilo. If I didn't, it would boot in legacy mode and then you can't install elilo.
The ISO, if provided by Alien Bob for -current or on a Slackware mirror for 14.1 and newer will already support EFI booting if you simply dd it to a device. If you generate your own ISO, there's probably ways to disable EFI, but I've not looked into them.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.