LinuxQuestions.org
Visit Jeremy's Blog.
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-02-2022, 10:12 AM   #1
ricky_cardo
Member
 
Registered: Feb 2006
Location: Syracuse, NY
Distribution: Slackware64-Current
Posts: 210

Rep: Reputation: 76
elilo boot issue after current update to 5.19.0


Currently not able to boot slackware64-current after 5.19.0 kernel upgrade.
- any chance it is an elilo size issue again?

- When I revert to kernel 5.18.15 - everything works)

Is anyone else seeing this ?

So it does seem to boot with Grub2 just not elilo.

I recover using boot-usb that I have setup with grub2 and autodiscover ...


Setup with problems:
UEFI
elilo - slackware64-current
my vmlinuz is a copy of generic-vmlinuz


cat /boot/efi/EFI/Slackware/elilo.conf
Code:
chooser=simple
delay=1
timeout=1
#
image=vmlinuz
        label=vmlinuz
        initrd=initrd.gz
        read-only
        append="root=/dev/sda3 vga=normal ro"


after I upgrade the kernel I usually run this:
Code:
#!/bin/bash
KERNEL_VER="5.18.15"  #update this as version changes 


# build a initrd.gz
/sbin/mkinitrd -c -k ${KERNEL_VER} -f ext4 -r "UUID=90b0...(id obsured for this post)" -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-asus:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:crc32c_intel:crc32c_generic:ext4 -u -o /boot/initrd.gz

/usr/bin/cp /boot/initrd.gz /boot/efi/EFI/Slackware/

/usr/bin/cp /boot/vmlinuz-generic /boot/efi/EFI/Slackware/vmlinuz

Last edited by ricky_cardo; 08-02-2022 at 11:32 AM. Reason: grammer and corrections in typing
 
Old 08-02-2022, 10:20 AM   #2
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,465

Rep: Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258Reputation: 3258
Quote:
Originally Posted by ricky_cardo View Post
Currently not able to boot slackware64-current after 5.19.0 kernel upgrade.
- any chance it is an elilo size issue again?

- When I revert to kernel 5.18.15 - everything works)

Is anyone else seeing this ?

So it does seem to boot with Grub just not elilo.
Yes, you are not alone. I was bitten 2 times too. And there are another people who bitten the dust.

I for one, I switched to Grub2 fully and I given to ELILO a long goodbye - life is too great to waste it playing with things abandoned 8 (eight) years ago.

Last edited by LuckyCyborg; 08-02-2022 at 10:28 AM.
 
7 members found this post helpful.
Old 08-02-2022, 02:40 PM   #3
byteporter
LQ Newbie
 
Registered: Jan 2019
Location: USA
Distribution: Slackware
Posts: 5

Rep: Reputation: Disabled
Same here, I only tried to upgrade one machine so far, an HP Z440 with an E5 v3 Xeon, but I have the issue. I assumed I forgot to add a driver to my ramdisk or something like that because I forget that somewhat often.

But after messing with it for a bit, I finally tried a USB boot stick based off the new kernel (I had had one based on the old one on hand and was using that to mess with my system via chroot). That one works, so I started suspecting it might just be elilo and came here to confirm. So looks like that must be the issue!

Now to decide if I want GRUB or rEFInd... hmmm...
 
Old 08-02-2022, 03:42 PM   #4
avian
Member
 
Registered: Aug 2014
Posts: 184

Rep: Reputation: Disabled
Quote:
Originally Posted by ricky_cardo View Post
Currently not able to boot slackware64-current after 5.19.0 kernel upgrade.
- any chance it is an elilo size issue again?

Is anyone else seeing this ?
I dont use the slackware kernels, but I got no problems booting a custom 5.19.0 kernel using elilo here, on a slackware64 15.0 system. No idea what the difference could be thats causing issues. Incase it helps, I dont use initrd, (although my initrd line points to an intel microcode bundle).

Last edited by avian; 08-02-2022 at 03:50 PM.
 
2 members found this post helpful.
Old 08-02-2022, 05:05 PM   #5
gildbg
Member
 
Registered: Aug 2017
Distribution: Slackware, OpenBSD
Posts: 146

Rep: Reputation: Disabled
I have the same problem, unable to boot 5.19 kernel. I use refind with elilo. I don't use initrd.
 
Old 08-02-2022, 05:13 PM   #6
lonestar_italy
Member
 
Registered: Nov 2010
Location: Italy
Distribution: Slackware64-current
Posts: 169

Rep: Reputation: 67
Quote:
Originally Posted by gildbg View Post
I have the same problem, unable to boot 5.19 kernel. I use refind with elilo. I don't use initrd.
Yes I do the same and it didn't work for me as well.
When I have time and patience I will see if it can work with rEFInd alone without any chainload, or with rEFInd + grub
 
Old 08-02-2022, 06:01 PM   #7
gildbg
Member
 
Registered: Aug 2017
Distribution: Slackware, OpenBSD
Posts: 146

Rep: Reputation: Disabled
I have dual booting with windows I fix it. It's seems the problem is in ELILO, so I did:

1. mount the EFI partition with: mountvol Z: /S
2. Enter the EFI partition and going to refind directory
3. Copy the refind.conf to my drive and open in with notepad++
4. Remove the ELILO boot and add my own in the end of config like:
Quote:
menuentry Slackware {
icon EFI/refind/icons/os_slackware.png
loader EFI/Slackware/vmlinuz
options "root=/dev/sda1 ro vt.default_utf8=1 usbcore.autosuspend=-1"
}
5. Save the file and copy him back to EFI partition (overwrite the original)
6. Reboot and Boot was success.
7. Enter as root and do: removepkg elilo

I hope this will help some one.

Last edited by gildbg; 08-02-2022 at 06:02 PM.
 
2 members found this post helpful.
Old 08-03-2022, 12:19 PM   #8
Mr.Gadgets
LQ Newbie
 
Registered: Oct 2018
Posts: 8

Rep: Reputation: 2
Hi,

I ran into the same issue with kernel v5.19.0 using elilo on sw15-cur. For me, it looked like the elilo.efi loader failed to find something useful when reading the contents of the efi partition and then just kept trying.

But I like the efi stub option in the kernel, since you don't need another bootloader at all... It causes the kernel to basically become an efi-executable binary itself, so you can immediately load it without using elilo/grub/whatever, just by adding the appropriate option via efibootmgr.

Something like the following worked for me (with sda1=efi, sda2=swap, sda3=ext4):

efibootmgr -d /dev/sda -p 1 -c -L "EFI Stub" -l "EFI/Slackware/vmlinuz" -u "root=/dev/sda3 resume=/dev/sda2 rw initrd=EFI/Slackware/initrd.gz" -v

So I'll be removing elilo.conf and elilo.efi from /boot/efi/EFI/Slackware, just leaving vmlinuz + initrd.gz there.
 
2 members found this post helpful.
Old 08-03-2022, 12:24 PM   #9
byteporter
LQ Newbie
 
Registered: Jan 2019
Location: USA
Distribution: Slackware
Posts: 5

Rep: Reputation: Disabled
I updated my home workstation, an hp z840 with dual e5 v3s, and that one worked perfectly fine. It's running root on ZFS even. That one was already using rEFInd though.

No idea what the issue is with elilo, I'm surprised to hear that it works just fine for some people. Curious what the issues is. Graphics/modesetting drivers maybe? I have to admit I barked up the wrong tree with that for a minute thinking it was a driver issue because it seemed like it was just outputting to the incorrect console or something. I'm running AMD gpus all the way around, WX 3200 in the machine here that I observed the issue on.

To get back into this machine, I just used the GRUB command line from the boot USB stick:

Code:
> root=(hd4,gpt1)
> linux /efi/Slackware/vmlinuz ro root=/dev/sdd2
> initrd /efi/Slackware/initrd.gz
> boot
These settings will vary on your machine of course, for me my EFI partition is on the first partition of my /dev/sdd drive. You also may or may not have an initrd, I build mine custom every time I update the kernel.
 
1 members found this post helpful.
Old 08-03-2022, 12:30 PM   #10
ricky_cardo
Member
 
Registered: Feb 2006
Location: Syracuse, NY
Distribution: Slackware64-Current
Posts: 210

Original Poster
Rep: Reputation: 76
Quote:
Originally Posted by Mr.Gadgets View Post
Hi,

I ran into the same issue with kernel v5.19.0 using elilo on sw15-cur. For me, it looked like the elilo.efi loader failed to find something useful when reading the contents of the efi partition and then just kept trying.

But I like the efi stub option in the kernel, since you don't need another bootloader at all... It causes the kernel to basically become an efi-executable binary itself, so you can immediately load it without using elilo/grub/whatever, just by adding the appropriate option via efibootmgr.

Something like the following worked for me (with sda1=efi, sda2=swap, sda3=ext4):

efibootmgr -d /dev/sda -p 1 -c -L "EFI Stub" -l "EFI/Slackware/vmlinuz" -u "root=/dev/sda3 resume=/dev/sda2 rw initrd=EFI/Slackware/initrd.gz" -v

So I'll be removing elilo.conf and elilo.efi from /boot/efi/EFI/Slackware, just leaving vmlinuz + initrd.gz there.
This looks really interesting, I've used grub2 and refined(when winblows dual was needed, or because I do like refined) but never before the EFI Stub. I'm going to give this a try


--update this works well thanks, as does adding the stub to refined. Might stick with the one Mr.Gadgets suggested for the time being. Seems like less is more.

Last edited by ricky_cardo; 08-03-2022 at 02:24 PM. Reason: works (update note)
 
Old 08-03-2022, 12:34 PM   #11
WhiteWolf1776
Member
 
Registered: Oct 2010
Location: Bowling Green, KY
Distribution: Slackware
Posts: 288

Rep: Reputation: 95
first time i've hard bricked failed to boot in years, but 5.19 and elilo just isn't working....

looks like grubby time
 
Old 08-03-2022, 01:08 PM   #12
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,882

Rep: Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988
There's also an option to append a "bootconfig" file to the end of the initrd/initramfs to specify kernel options, so you don't have to put them in the EFI entries directly. From 5.19 onwards it can even be imbedded directly in the kernel at compile time rather than the initrd.

See bootconfig.rst in the Documentation/admin-guide/ directory of the kernel source for details. I haven't tried this one yet, but it looks interesting.

If there is a problem with the EFI STUB at present then it's possible it could also upset some EFI firmwares as well as ELILO and rEFInd — which some folks have already reported having issues with in this forum — so I guess it's all a matter of suck it and see for the time being.

One thing I'm not clear on is whether one should append the bootconfig to the initrd before or after one prepends the early-fw file for the cpu microcode. The docs talk about alignment, so I'm guessing that doing it first is probably the way.

Last edited by GazL; 08-03-2022 at 01:16 PM. Reason: typo
 
Old 08-03-2022, 01:15 PM   #13
garpu
Senior Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 1,512

Rep: Reputation: 886Reputation: 886Reputation: 886Reputation: 886Reputation: 886Reputation: 886Reputation: 886
There's some speculation that this could be an efi stub bug in 5.19, too. I'm hanging out on 5.18.15, just to see what happens before I switch boot loaders. I'm not opposed, but elilo is the default, and if the default isn't working, people will need to potentially test a fix.
 
Old 08-03-2022, 01:56 PM   #14
WhiteWolf1776
Member
 
Registered: Oct 2010
Location: Bowling Green, KY
Distribution: Slackware
Posts: 288

Rep: Reputation: 95
Quote:
Originally Posted by garpu View Post
There's some speculation that this could be an efi stub bug in 5.19, too. I'm hanging out on 5.18.15, just to see what happens before I switch boot loaders. I'm not opposed, but elilo is the default, and if the default isn't working, people will need to potentially test a fix.
Any chance you have a mirror that still has the last 5.18 kernel?
 
1 members found this post helpful.
Old 08-03-2022, 02:04 PM   #15
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,048

Rep: Reputation: Disabled
Quote:
Originally Posted by WhiteWolf1776 View Post
Any chance you have a mirror that still has the last 5.18 kernel?
https://slackware.uk/cumulative/slac...t/slackware64/
 
4 members found this post helpful.
  


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
Elilo Slackware64-current boot issue on a system76 Pangolin 15 khronosschoty Slackware 11 11-05-2021 06:05 PM
Fresh -current setup issue (elilo, Plasma 5, bluetooth, fcitx) Zihen Slackware 20 12-24-2020 05:19 AM
[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
Dual boot OS X and Slackware64-current (Thu Jun 27 23:56:34 UTC 2013) with elilo? janucaria Slackware 2 07-03-2013 07:56 AM

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

All times are GMT -5. The time now is 05:20 PM.

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