LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-07-2019, 02:14 AM   #1
shai-hulud
LQ Newbie
 
Registered: Apr 2019
Posts: 5

Rep: Reputation: Disabled
UEFI installation - elilo does not prompt when I skipped lilo


Hi,

I've been trying to install slackware64 14.2 for UEFI under GPT partition.
I created EFI partition, Swap, Data and started setup.
It seems that no problem so far but when I skipped lilo configuration and it should elilo configuration should be prompt but nothing happened.
Please advise if I missed something.
Thanks.

Hardware: Dell Latitude E5450
Slackware version: slackware64 14.2
 
Old 06-07-2019, 02:42 AM   #2
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 2,967
Blog Entries: 7

Rep: Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549
There is a script called eliloconfig in /usr/sbin. If you run this, it will install elilo for you.
Quote:
Originally Posted by eliloconfig
# This script installs the elilo boot loader, the kernel, and optionally
# an initrd into the EFI System Partition. A boot menu entry can also be
# installed using efibootmgr. The kernel used will be whatever the symlink
# /boot/vmlinuz points to, and if /boot/initrd.gz exists, that will be
# installed as the initrd.
#
# The EFI System Partition is expected to be mounted on /boot/efi before
# running this script.
Note that you will need an initrd image if you're using the generic kernel, but not if you use the huge kernel. If you are going to use an initrd, you must create it first (that's Slackware, folks!). There's an extremely helpful script in /usr/share/mkinitrd/ mkinitrd_command_generator.sh that will print out a suitable command for doing it.

Last edited by hazel; 06-07-2019 at 02:46 AM.
 
Old 06-07-2019, 05:26 AM   #3
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, puppy, ubuntu
Posts: 2,953

Rep: Reputation: 470Reputation: 470Reputation: 470Reputation: 470Reputation: 470
did you format the efi partition as fat32 before you started setup?
 
Old 06-07-2019, 06:10 AM   #4
trite
Member
 
Registered: Feb 2016
Location: Sweden
Distribution: Slackware64-current
Posts: 47

Rep: Reputation: 29
I think you can just run "eliloconfig" after the installation wizard?

Some things is needed so that it finds your EFI like you have to label the partition as EFI partition and format it as FAT32 as mentioned by colorpurple21859.

I think I also had problems with it not finding EFI and running elilo config. where I had a very old install dvd or booted the USB not in UEFI mode but in legacy mode, so make sure you boot your install media in UEFI mode if you want to install with UEFI.

Maybe check some other things in your BIOS like disabling secure boot and fast boot, also enable booting things in UEFI or even disable legacy mode if you want to.

Last edited by trite; 06-07-2019 at 06:13 AM.
 
2 members found this post helpful.
Old 06-07-2019, 08:21 AM   #5
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 2,967
Blog Entries: 7

Rep: Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549
I think trite has got it: you must have booted your install in legacy mode and that's why you were offered lilo instead of elilo. When you are in legacy mode, the directory /sys/firmware/efi does not exist and that's what installation scripts check for.

You need to go into your UEFI and make sure legacy mode is switched off. The other things trite mentioned like fastboot and secure boot must be off too. Then boot from the install disk, mount your EFI system partition on /boot/efi and run eliloconfig, first making sure that /boot/vmlinuz points to the huge kernel so that you won't need an initrd. You can switch to the generic kernel with initrd later if you like.

Last edited by hazel; 06-07-2019 at 08:22 AM.
 
1 members found this post helpful.
Old 06-07-2019, 09:24 AM   #6
Desiderius
Member
 
Registered: Jun 2017
Posts: 40

Rep: Reputation: Disabled
Elilo for Dell Latitude

Hi shai-hulud

I have a Dell Latitude 5490 under Slackware current and I had also problems with elilo at beginning.

What you need :

- no special initrd

- a boot hierarchy formatted in FAT32 : /boot/efi/EFI

- Under this repo, you create a Slackware repository

- In this repository put :

-> elilo-x86_64.efi ( you can find it in the /boot repository of Slackware )
-> vmlinuz-huge-4.x.x depends upon your version of kernel
-> elilo.conf containing ( modify with your locations of root partition and numbering of the kernel ):

chooser=simple
default=Linux
image=vmlinuz-huge-4.19.19
label=Linux
root=/dev/nvme0n1p7
append="root=/dev/nvme0n1p7 vga=normal ro"

Then I use refind which simplifies the boot sequence : http://www.rodsbooks.com/refind/
 
Old 06-07-2019, 09:29 AM   #7
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, puppy, ubuntu
Posts: 2,953

Rep: Reputation: 470Reputation: 470Reputation: 470Reputation: 470Reputation: 470
if everything is set up right should get a message about "adding efi partition to fstab" during the setup target partition stage of the setup
 
Old 06-07-2019, 02:03 PM   #8
pr0xibus
Member
 
Registered: Apr 2004
Location: Montrose, Scotland
Distribution: Slackware
Posts: 136

Rep: Reputation: 21
Couldnt say its the issue, but when I have formatted and had a clean install that issue usually comes about when I forget to format the (EFI) partition in Fat32
 
Old 06-08-2019, 12:16 AM   #9
aragorn2101
Member
 
Registered: Dec 2012
Location: Mauritius
Distribution: Slackware
Posts: 535

Rep: Reputation: 261Reputation: 261Reputation: 261
Hi folks,

Just wanted to say that I have done many install of Slackware64 14.2 in full UEFI mode on several machines, and it always showed me the screen for LILO during installation, except that it specifically mentioned that my system is using UEFI and that I should skip to ELILO installation, which I did.

Now I had the experience with a PC where the BIOS was in some funny mode labeled as Legacy/UEFI. Then, LILO installation was shown as usual, but after I skipped it, Slackware finished the installation without having installed a bootloader, similar to what shai-hulud is describing.

So, shai-hulud, check your UEFI firmware settings (aka BIOS) carefully for these things. Try to disable all sorts of fastboot/secure boot/legacy/BIOS/MBR, whatever.

Also, as colorpurple21859 rightly pointed out, your EFI partition might not be ready. It should be formatted to FAT32. One indication that the system recognized the UEFI setup and EFI partition is that around the screens for choosing partitions for swap and / the system asks you to confirm which partition is the EFI partition because it has to mount it at /boot/efi. So, if you remember getting this screen or not, it will help detecting the source of the problem.

Finally, if you can't install ELILO, or if you manage to install it but don't like it or if you want to multiboot several OS and you want something a bit more sophisticated, there is GRUB. You might want to check this out: https://docs.slackware.com/howtos:sl...slackware#grub

All the best.

Last edited by aragorn2101; 06-08-2019 at 12:21 AM.
 
Old 06-08-2019, 05:34 AM   #10
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 2,967
Blog Entries: 7

Rep: Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549
Quote:
Originally Posted by aragorn2101 View Post
Now I had the experience with a PC where the BIOS was in some funny mode labeled as Legacy/UEFI. Then, LILO installation was shown as usual, but after I skipped it, Slackware finished the installation without having installed a bootloader, similar to what shai-hulud is describing.
That's not a "funny mode". That's the legacy mode that all PC UEFIs have to support by law. It's often well hidden under some such name as csm (which stands for Compatibility Support Mode) because they don't actually want you to use it.

When UEFIs first came in, a lot of Linux installation discs couldn't handle them, which would have prevented Linux from ever being installed on these machines. So manufacturers were required to provide the legacy mode, where the UEFI emulates a BIOS. Nowadays all the major Linux distros support native UEFI booting but I don't know whether the smaller distros do.
 
Old 06-08-2019, 07:27 AM   #11
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 8,856

Rep: Reputation: Disabled
Quote:
Originally Posted by hazel View Post
That's not a "funny mode". That's the legacy mode that all PC UEFIs have to support by law.
I don't know any law about UEFI, just an Unified Extensible Firmware Interface (UEFI) Specification. Let's quote its current version (2.8 March 2019) on the topic of migation from Legacy to UEFI:
Quote:
1.7 Migration Requirements

Migration requirements cover the transition period from initial implementation of this specification to a future time when all platforms and operating systems implement to this specification. During this period, two major compatibility considerations are important:
  • The ability to continue booting legacy operating systems;
  • The ability to implement UEFI on existing platforms by reusing as much existing firmware code to keep development resource and time requirements to a minimum
1.7.1 Legacy Operating System Support

The UEFI specification represents the preferred means for a shrink-wrap OS and firmware to communicate during the boot process. However, choosing to make a platform that complies with this specification in no way precludes a platform from also supporting existing legacy OS binaries that have no knowledge of the UEFI specification.

The UEFI specification does not restrict a platform designer who chooses to support both the UEFI specification and a more traditional “PC-AT” boot infrastructure. If such a legacy infrastructure is to be implemented, it should be developed in accordance with existing industry practice that is defined outside the scope of this specification. The choice of legacy operating systems that are supported on any given platform is left to the manufacturer of that platform.

1.7.2 Supporting the UEFI Specification on a Legacy Platform

The UEFI specification has been carefully designed to allow for existing systems to be extended to support it with a minimum of development effort. In particular, the abstract structures and services defined in the UEFI specification can all be supported on legacy platforms.

For example, to accomplish such support on an existing and supported 32-bit-based platform that uses traditional BIOS to support operating system boot, an additional layer of firmware code would need to be provided. This extra code would be required to translate existing interfaces for services and devices into support for the abstractions defined in this specification.

Quote:
Originally Posted by hazel View Post
It's often well hidden under some such name as csm (which stands for Compatibility Support Mode) because they don't actually want you to use it
I do not assume anything about what "they" (who, exactly?) want. CSM means Compatibility Support Module and is defined in the Intel ® Platform Innovation Framework for EFI Compatibility Support Module Specification. This CSM as developed by Intel for its own usage is somehow an implementation of the the last quoted paragraph above of the UEFI specification.


I agree that it is often not easy to find one's way in the console interface of the firmware boot managers, and assume that's for following reasons:
  • The firmware developer do not always pay much attention to the ergonomics of the console boot manager interface.
  • The presentation of this interface varies across implementations, as the UEFI specification does not state any requirement on this regard.
But it is understandable that the firmware providers want to avoid the burden of supporting ad vitam aeternam this additional level of complexity, that represents a lot of work for them, in addition to the huge work of implementing the new interface.

To go half way back to the topic, in my opinion it's about time to say good bye to both lilo and elilo and use GRUB instead, as GRUB 2.04 release is nearing.

Have a good day.
 
Old 06-08-2019, 07:39 AM   #12
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 2,967
Blog Entries: 7

Rep: Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549
But GRUB is so bloody complicated! I really hate it.
 
Old 06-08-2019, 08:17 AM   #13
laprjns
Member
 
Registered: Oct 2005
Location: Connecticut USA
Distribution: SalixOS
Posts: 186

Rep: Reputation: 92
Quote:
Originally Posted by shai-hulud View Post
Hi,

I've been trying to install slackware64 14.2 for UEFI under GPT partition.
I created EFI partition, Swap, Data and started setup.
It seems that no problem so far but when I skipped lilo configuration and it should elilo configuration should be prompt but nothing happened.
Please advise if I missed something.
Thanks.

Hardware: Dell Latitude E5450
Slackware version: slackware64 14.2
Maybe this https://www.linuxquestions.org/quest...7/#post5810474
 
Old 06-08-2019, 09:05 AM   #14
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 8,856

Rep: Reputation: Disabled
Quote:
Originally Posted by hazel View Post
But GRUB is so bloody complicated!
If you want to write grub.cfg by hand or edit it, yes. But few users do that.
 
Old 06-08-2019, 12:55 PM   #15
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 2,967
Blog Entries: 7

Rep: Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549
Quote:
Originally Posted by Didier Spaier View Post
If you want to write grub.cfg by hand or edit it, yes. But few users do that.
Other way around, Didier! Writing a grub.cfg by hand is a relatively simple operation, provided that you know how to do it. The LFS chapter on booting with GRUB is very good on this. What is insanely complicated is the gaggle of shell scripts that most distros use to manage GRUB.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] First UEFI/elilo system (14.2/x86_64) will not boot after installation rshepard Slackware 8 09-06-2018 04:20 PM
lilo x elilo x grup2 x UEFI afreitascs Slackware 5 09-09-2012 10:55 AM
UEFI PXE server elilo.conf configuration miszum Linux - Networking 2 08-05-2011 11:31 AM
[SOLVED] LILO fails when run from live CD after installing Slack (skipped LILO during setup) sysfce2 Linux - Newbie 7 08-04-2009 12:16 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:01 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration