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 08-07-2019, 12:23 PM   #16
wirelessmc
Member
 
Registered: Aug 2008
Posts: 76

Rep: Reputation: 10

Quote:
Originally Posted by hazel View Post
You use elilo just the same way that you would use lilo on a BIOS system. Go to root, edit your /etc/elilo.conf file to point to the new kernel, then run /sbin/elilo.
It sure would be nice to know where this executable "/sbin/lilo" comes from, because *it* sure is **NOT** included in the stock slackware package (see below). The doc /usr/doc/elilo-3.16/elilo.txt does reference it however.

I would like to know how to re-install elilo from within the booted OS instead of having to run it from the klunky setup script. I think I will post another thread on this topic if I cannot find and copy the executable from the boot DVD.



/var/log/packages_} cat elilo-3.16-x86_64-2
PACKAGE NAME: elilo-3.16-x86_64-2
COMPRESSED PACKAGE SIZE: 148.0K
UNCOMPRESSED PACKAGE SIZE: 620K
PACKAGE LOCATION: /var/log/mount/slackware64/a/elilo-3.16-x86_64-2.txz
PACKAGE DESCRIPTION:
elilo: elilo (Linux Loader for EFI-based platforms)
elilo:
elilo: This is elilo, a boot loader originally developed by HP for IA-64
elilo: systems. This is used to load the kernel and initial ramdisk on
elilo: machines that use UEFI. Since most UEFI implementations are 64-bit,
elilo: the 64-bit EFI binary is generally the one to use (even for loading
elilo: a 32-bit kernel).
elilo:
elilo: Homepage: http://elilo.sourceforge.net
elilo:
elilo:
FILE LIST:
./
boot/
boot/elilo-ia32.efi
boot/elilo-x86_64.efi
install/
install/slack-desc
usr/
usr/doc/
usr/doc/elilo-3.16/
usr/doc/elilo-3.16/ChangeLog
usr/doc/elilo-3.16/LIMITATIONS
usr/doc/elilo-3.16/README
usr/doc/elilo-3.16/README.gnu-efi
usr/doc/elilo-3.16/README.txt
usr/doc/elilo-3.16/TODO
usr/doc/elilo-3.16/devschemes.txt
usr/doc/elilo-3.16/edd30.txt
usr/doc/elilo-3.16/elilo.txt
usr/doc/elilo-3.16/eliloalt.txt
usr/doc/elilo-3.16/elilovars.txt
usr/doc/elilo-3.16/examples/
usr/doc/elilo-3.16/examples/netboot/
usr/doc/elilo-3.16/examples/netboot/dhcpd-pxe.conf
usr/doc/elilo-3.16/examples/netboot/dhcpd.conf
usr/doc/elilo-3.16/examples/textmenu_chooser/
usr/doc/elilo-3.16/examples/textmenu_chooser/elilo-textmenu.conf
usr/doc/elilo-3.16/examples/textmenu_chooser/general.msg
usr/doc/elilo-3.16/examples/textmenu_chooser/params.msg
usr/doc/elilo-3.16/examples/textmenu_chooser/textmenu-message.msg
usr/doc/elilo-3.16/fpswa.txt
usr/doc/elilo-3.16/netbooting.txt
usr/doc/elilo-3.16/simple_chooser.txt
usr/doc/elilo-3.16/textmenu_chooser.txt
usr/sbin/
usr/sbin/eliloalt
usr/sbin/eliloconfig
var/
var/log/
var/log/setup/
var/log/setup/setup.ll.eliloconfig
 
Old 08-07-2019, 02:40 PM   #17
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado, USA
Distribution: Slackware
Posts: 629

Rep: Reputation: 206Reputation: 206Reputation: 206
Quote:
Originally Posted by wirelessmc View Post
It sure would be nice to know where this executable "/sbin/lilo" comes from ...
Look for a different package:

slackware64-14.2: lilo-24.2-x86_64-2

slackware64-current: lilo-24.2-x86_64-8
 
Old 08-09-2019, 08:03 AM   #18
wirelessmc
Member
 
Registered: Aug 2008
Posts: 76

Rep: Reputation: 10
[SOLVED] update kernel but how configure elilo?

Chuck,

Thanks for your response but the original post I was questioning referred to the executable '/sbin/elilo'. The lilo packages you cite do indeed contain the executable '/sbin/lilo' but no '/sbin/elilo'.

As I am sure you are aware you cannot install elilo with lilo. They are separate packages.
 
Old 08-09-2019, 08:06 AM   #19
wirelessmc
Member
 
Registered: Aug 2008
Posts: 76

Rep: Reputation: 10
[SOLVED] update kernel but how configure elilo?

Ahh typo's will kill you every time...

I was asking about /sbin/lilo in my original post. That was a typo. I meant to ask about /sbin/elilo. I am pretty sure this doesn't exist in any slackware package.
 
Old 08-09-2019, 09:28 AM   #20
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,824

Rep: Reputation: 853Reputation: 853Reputation: 853Reputation: 853Reputation: 853Reputation: 853Reputation: 853
run eliloconfig

http://www.rodsbooks.com/efi-bootloaders/elilo.html
https://sourceforge.net/projects/elilo/
 
Old 06-24-2020, 10:53 AM   #21
shevegen
Member
 
Registered: May 2004
Distribution: Slackware / GoboLinux / LFS / VoidLinux
Posts: 127

Rep: Reputation: 26
Personally I would prefer to merge lilo and elilo together, and use only one layout. Right now I
always have to remember whether I use lilo or elilo.
 
1 members found this post helpful.
Old 06-24-2020, 11:42 AM   #22
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,520

Rep: Reputation: Disabled
Quote:
Originally Posted by shevegen View Post
Personally I would prefer to merge lilo and elilo together, and use only one layout. Right now I always have to remember whether I use lilo or elilo.
Then use grub. The u in grub means unified.
 
Old 06-24-2020, 02:27 PM   #23
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 3,107

Rep: Reputation: 3132Reputation: 3132Reputation: 3132Reputation: 3132Reputation: 3132Reputation: 3132Reputation: 3132Reputation: 3132Reputation: 3132Reputation: 3132Reputation: 3132
Quote:
Originally Posted by Didier Spaier View Post
Then use grub. The u in grub means unified.

Funny... I thought the "u" was for "unnecessarily complex"



I know... I know... with the exception of that dastardly OSProber GRUB does a good job. I'd just prefer that the job description stop at Bootloader. I really don't need nor enjoy all the frills that just happen to require grub-specific language and syntax.
 
Old 06-24-2020, 03:13 PM   #24
kevmccor
Member
 
Registered: Aug 2004
Location: Texas
Distribution: slackware
Posts: 120

Rep: Reputation: 36
My very recent experience on updating a -current installation required that I change the motherboard bios to be compatible with UEFI and the mbr boot methods. This computer has an nvme drive with a pci connection (Asrock B450 mini-itx with Ryzen 2400G processor)

Now, I have decided there appears to be no good reason to use UEFI for booting. How placing your kernel on a VFAT formatted partition enhances security is beyond me. I think the security advantage is solely to place a secure boot password in the motherboard bios so that the computer OS can't be changed, which is mostly useless outside a corporate environment. The Slackware UEFI documentation is terrible, scattered, old, and lacks background information. I suspect that if anyone actually knows what it is or how it works, they're not telling. But since I formatted my drives for UEFI and have successfully used it, I am sticking with it because I am not going to re-partition my drives. What I also suspect is a lot of people are finding themselves forced into -current because 14.2 is too old. It worked so well for so long that we are a bit unprepared.

FYI: GPT partition (how is this done right anyway?)
/dev/nvme0n1p1 /boot/efi vfat 400 MB EF00
/dev/nvme0n1p2 swap 16GB 8200
/dev/nvme0n1p3 / ext4 64GB 8300
/dev/nvme0n1p4 /home ext4 all the rest 8300

Prior to this upgrade I had installed a large number of slackbuilds from https://github.com/Ponce/slackbuilds on another computer. This is also running -current. I had the luck to have all these packages still in my /tmp folder which I moved to a usb thumbdrive. I installed all these packages as the last step of the upgrade process. # upgradepkg --install-new /path/to/usb/*.tgz

Note: it would be great to have a sbopkg queue list for these constant upgrades of -current. Just the thirty or so most common or obviously desired packages in dependency order.

I generally followed the advice of this How-to.

Step 1 -- comment kernel-* in /etc/slackpkg/blacklist so kernel-* will be dealt with by slackpkg (also comment everything else)
Step 2 -- # slackpkg update
Step 3 -- downloaded the kernel packages with # slackpkg download kernel
Step 4 -- uncomment kernel-* in /etc/slackpkg/blacklist so kernel-* will be ignored by slackpkg
Step 5 -- # slackpkg install-new
Step 6 -- # slackpkg upgrade-all
Step 7 -- # slackpkg clean-system

Step 8 -- # cd /var/cache/packages/slackware64/a/
Code:
# 
# installpkg kernel-huge-5.4.47-x86_64-1.txz
# installpkg kernel-modules-5.4.47-x86_64-1.txz
# installpkg kernel-generic-5.4.47-x86_64-1.txz
# upgradepkg kernel-firmware-20200619_3890db3-noarch-1.txz
# cd ../k
# installpkg kernel-source-5.4.47-noarch-1.txz
# cd /boot
# cp vmlinuz-huge-5.4.47 efi/EFI/Slackware/vmlinuz-huge-5447
# cp vmlinuz-generic-5.4.47 efi/EFI/Slackware/vmlinuz-generic-5447
# cd /usr/share/mkinitrd
# sh mkinitrd_command_generator.sh -k 5.4.47
# cd 
# mkinitrd -c -k 5.4.47 -f ext4 -r /dev/XXXX -m vfat:mbcache:jbd2:ext4 -u -o /boot/initrd-5447.gz
(add a -P intel-ucode.cpio for intel processors -- requires intel-microcode and iucode_tool)
# cp /boot/initrd-5447.gz /boot/efi/EFI/Slackware/
Note that I added the vfat module to the initrd. Prior to doing that, the generic kernel would not boot. It either stopped on the elilo screen or had a panic being unable to find the root filesystem. I don't know what the error was or why it was fixed.

Step 9 -- # eliloconfig (has the effect of replacing your existing elilo.conf file -- who knows what vmlinuz is really?)

Step 10 -- edit the /boot/efi/Slackware/elilo.conf file
Quote:
chooser=simple
delay=1
timeout=1
default=Modular5447
#vga=833 vga=normal
### upgraded kernel
image=vmlinuz-generic-5447
label=Modular5447
initrd=initrd-5447.gz
append="root=/dev/XXXX ro"

image=vmlinuz-huge-5447
label=Huge5447
# initrd=intel-ucode.cpio
append="root=/dev/XXXX vga=833 ro"

### old kernel
image=vmlinuz-generic
label=Modular5443
initrd=initrd-5443.gz
append="root=/dev/XXXX vga=833 ro"

image=vmlinuz
label=Huge5443
initrd=initrd.gz
append="root=/dev/XXXX vga=normal ro"
No doubt my elilo.conf file could be improved. I only boot the generic kernel so any other errors are never experienced. When it is time to upgrade the kernel again, the lines below ### old kernel will be replaced.

Step 11 -- reboot and deal with nvidia packages if necessary
Step 12 -- enjoy your now truly -current Slackware system.
 
Old 06-26-2020, 06:16 AM   #25
chrisVV
Member
 
Registered: Aug 2010
Posts: 431

Rep: Reputation: 239Reputation: 239Reputation: 239
Quote:
Originally Posted by enorbet View Post
... with the exception of that dastardly OSProber GRUB does a good job. I'd just prefer that the job description stop at Bootloader. I really don't need nor enjoy all the frills that just happen to require grub-specific language and syntax.
You don't have to use all of the scripts in /etc/grub.d, and in particular you don't need to run 30_os-prober - just make it unexecutable. For that matter, you don't need to run grub-mkconfig at all: you can write your own grub.cfg file. The basic syntax is more or less as simple as elilo's - see slackware64-current/EFI/BOOT/grub.cfg or slackware64-14.2/EFI/BOOT/grub.cfg for the one that the slackware installer uses: but if you adopt those as an example you will want to add a 'set root=...' clause in the relevant boot stanzas to enable grub to find /boot/vmlinuz (you won't be embedding the path to the kernel). The only weirdity in doing so is that disk numbering begins at 0 (hd0) but partition numbering begins at 1 (gpt1).

I recommend using unicode.pf2 in place of slackware's dejavusansmono.pf2 if you want something other than the default menu style. You can search for unicode.pf2 on the internet.
 
  


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
how to update elilo ?? BW-userx Slackware 13 11-18-2016 08:20 PM
[SOLVED] elilo broken on Slackware 14.2 after Windows 10 update on dual boot UEFI system hyperhead Slackware 5 08-03-2016 01:45 PM
[SOLVED] ELILO and kernel upgrade cgorac Slackware 3 01-26-2016 12:59 AM
Kernel Not Starting in 14.1 with EFI/elilo Skazi Slackware 1 11-21-2013 10:53 PM

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

All times are GMT -5. The time now is 05:41 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
Open Source Consulting | Domain Registration