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-26-2022, 05:00 PM   #1
trollog
Member
 
Registered: Oct 2014
Posts: 151

Rep: Reputation: Disabled
elilo problems and 5.19.x kernels


anyone else having problems booting in -current?

has elilo gone EOL for practical purposes?

I know there was a thread in here about this, it was a kernel bug that was supposed to be fixed approx 2 5.19.x kernels ago.

5.18.x kernels boot without issues in -current

Last edited by trollog; 08-26-2022 at 05:02 PM.
 
Old 08-26-2022, 05:24 PM   #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 trollog View Post
anyone else having problems booting in -current?

has elilo gone EOL for practical purposes?

I know there was a thread in here about this, it was a kernel bug that was supposed to be fixed approx 2 5.19.x kernels ago.

5.18.x kernels boot without issues in -current
Believe or not, it was NOT a kernel bug, BUT an ELILO bug. Or, rather ELILO needed to be patched to work with the modern kernels.

Let's do not blame the kernels because some rotten code abandoned since 2014 by its authors.

Anyway, it's not enough to just upgrade the ELILO package, but you need also to update the binary in your UEFI ESP partition. Manually.

Last edited by LuckyCyborg; 08-26-2022 at 05:27 PM.
 
1 members found this post helpful.
Old 08-26-2022, 05:41 PM   #3
trollog
Member
 
Registered: Oct 2014
Posts: 151

Original Poster
Rep: Reputation: Disabled
replacing the binary was the step I missed.
 
Old 08-26-2022, 06:19 PM   #4
gauchao
Member
 
Registered: Dec 2009
Location: Veneto
Distribution: Slackware64
Posts: 364

Rep: Reputation: 138Reputation: 138
After upgrading elilo with the package from Aug 5th, under -Current tree, you can run eliloconfig again (or manually copy the binary to EFI):

Quote:
Fri Aug 5 21:04:39 UTC 2022
a/elilo-3.16-x86_64-13.txz: Rebuilt.
Patched to disable the Confidential Computing blob for SEV-SNP, which
fixes booting a 5.19 kernel with the EFI stub enabled. If you use elilo,
be sure to either run eliloconfig again or manually copy (and rename) the
proper elilo binary to your EFI System Partition.
Job done.
 
2 members found this post helpful.
Old 08-27-2022, 12:29 AM   #5
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 4,421
Blog Entries: 7

Rep: Reputation: 2535Reputation: 2535Reputation: 2535Reputation: 2535Reputation: 2535Reputation: 2535Reputation: 2535Reputation: 2535Reputation: 2535Reputation: 2535Reputation: 2535
Quote:
Originally Posted by trollog View Post
has elilo gone EOL for practical purposes?
No, thankfully it has been patched.

I'm spared from learning how GRUB works after >20 years of using (e)LILO.

 
3 members found this post helpful.
Old 08-27-2022, 03:10 AM   #6
Thom1b
Member
 
Registered: Mar 2010
Location: France
Distribution: Slackware
Posts: 479

Rep: Reputation: 333Reputation: 333Reputation: 333Reputation: 333
Quote:
Originally Posted by rkelsen View Post
No, thankfully it has been patched.

I'm spared from learning how GRUB works after >20 years of using (e)LILO.

Hi, like you I used lilo/elilo until linux 5.19. I switched to grub in 5 minutes. Now lilo/elilo has gone forever on my computers.
 
2 members found this post helpful.
Old 08-27-2022, 03:42 AM   #7
cycojesus
Member
 
Registered: Dec 2005
Location: Lyon, France
Distribution: Slackware-current
Posts: 116

Rep: Reputation: 79
Quote:
Originally Posted by Thom1b View Post
Hi, like you I used lilo/elilo until linux 5.19. I switched to grub in 5 minutes. Now lilo/elilo has gone forever on my computers.
Me too, the learning I feared all these years barely took a few minutes and I'm no longer relying on code everyone has long forgotten about.
 
2 members found this post helpful.
Old 08-27-2022, 05:33 AM   #8
truepatriot76
Member
 
Registered: Apr 2014
Location: California, USA
Distribution: slackware64-current
Posts: 228

Rep: Reputation: 192Reputation: 192
My switch to GRUB2 a few years ago was due to FS errors I was occasionally getting due repeatedly writing to the EFI partition. With current, and multiple kernels, using eLILO was pretty hard on that small partition. Microsoft's FAT FS isn't exactly robust. I grew tired of fixing that partition every month or so, so I switched to GRUB2. Problem solved, no more hammering the EFI partition, it just gets read.
 
3 members found this post helpful.
Old 08-27-2022, 10:23 AM   #9
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,357

Rep: Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739
Quote:
Originally Posted by LuckyCyborg View Post
Believe or not, it was NOT a kernel bug, BUT an ELILO bug. Or, rather ELILO needed to be patched to work with the modern kernels.

Let's do not blame the kernels because some rotten code abandoned since 2014 by its authors.

Anyway, it's not enough to just upgrade the ELILO package, but you need also to update the binary in your UEFI ESP partition. Manually.
A kernel change affecting user space IS a kernel bug. Recompiling ELILO with a changed option is a work around.

Code that has been working since 2014 and then stops working IS to be blamed on the kernel changes. The code is not rotten. The endeavour to implement new features in the kernel is flawed.

Gott in himmel! Fancy needing to understand the boot process enough that undertaking a manual intervention is a chore. Geez, that is so old hat that I might as well run Slackware. If the automation in GRUB is so great, why does the Newbie forum get constant threads about boot problems?
 
9 members found this post helpful.
Old 08-27-2022, 11:08 AM   #10
Jan K.
Member
 
Registered: Apr 2019
Location: Esbjerg
Distribution: Windows 7...
Posts: 762

Rep: Reputation: 487Reputation: 487Reputation: 487Reputation: 487Reputation: 487
Quote:
Originally Posted by allend View Post
A kernel change affecting user space IS a kernel bug. Recompiling ELILO with a changed option is a work around.
This has been concluded before and agreed upon by the kernel devs, but has it been reported upstream via the official channels?

"We do not change user space"
 
Old 08-27-2022, 11:25 AM   #11
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 allend View Post
A kernel change affecting user space IS a kernel bug. Recompiling ELILO with a changed option is a work around.
The catch is that the bootloaders aren't "user space" , but (like I read somewhere in this forum), they are rather "god space" .

Quote:
Originally Posted by allend View Post
Code that has been working since 2014 and then stops working IS to be blamed on the kernel changes. The code is not rotten. The endeavour to implement new features in the kernel is flawed.
Um, what?

There shall NOT be any progress on kernels, trying to respect the quirks of some bootloaders abandoned long time ago?

The software world does NOT frozen in AD 2014, you know...

Quote:
Originally Posted by allend View Post
Gott in himmel! Fancy needing to understand the boot process enough that undertaking a manual intervention is a chore. Geez, that is so old hat that I might as well run Slackware. If the automation in GRUB is so great, why does the Newbie forum get constant threads about boot problems?
Instead to looking on the others garden, you aren't astonished that the Slackware forum is full of booting failures, when we we represent, being told with great enthusiasm, somewhere around 0.1% of the Linux users?

Compared with the overall number of users, is obviously that Slackware have an extremely high number of boot failures. We should do nothing about this?

Last edited by LuckyCyborg; 08-27-2022 at 11:43 AM.
 
Old 08-27-2022, 11:37 AM   #12
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 Jan K. View Post
"We do not change user space"
I do not think that the bootloaders are user space.

No user space software have an absolute control over hardware system like a bootloader.
 
Old 08-27-2022, 11:53 AM   #13
Aeterna
Senior Member
 
Registered: Aug 2017
Location: Terra Mater
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,000

Rep: Reputation: Disabled
Actually the only way to isolate VM client from hypervisor is to run type 1. Everything else is a waste of time.
SEV-SNP is undone already (as is SGX).
In other words, SEV-SNP should be optional available for people who are willing to compile custom kernels. Not to mention that most (Slackware?) users are not affected by VM issues.

..and I think that one needs AMD EPYC 7003 "Milan" processor. How many users have it?
If this is the case (CPU requirement), then this option can be disabled for most of the uses.

Last edited by Aeterna; 08-27-2022 at 12:02 PM.
 
Old 08-27-2022, 11:54 AM   #14
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,048

Rep: Reputation: Disabled
Quote:
Originally Posted by allend View Post
If the automation in GRUB is so great, why does the Newbie forum get constant threads about boot problems?
I don't know. What I know is that since Sunday 6 September 2020 in the distribution I maintain kernel upgrades are handled automatically, which includes building an initrd for the new kernel and updating the GRUB config file accordingly, with no issue reported with respect to this change.
 
Old 08-27-2022, 12:05 PM   #15
Aeterna
Senior Member
 
Registered: Aug 2017
Location: Terra Mater
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,000

Rep: Reputation: Disabled
Quote:
Originally Posted by Didier Spaier View Post
I don't know. What I know is that since Sunday 6 September 2020 in the distribution I maintain kernel upgrades are handled automatically, which includes building an initrd for the new kernel and updating the GRUB config file accordingly, with no issue reported with respect to this change.
shrug, and I have 5.19.x kernel that never had an issue with elilo (in fact I never upgraded elilo). The fact that you do not have issues with GRUB, does not mean that users don't complain about it.

Last edited by Aeterna; 08-27-2022 at 12:16 PM.
 
2 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
disk thrashing on 5.15.x kernels (but not on 4.4.x or 4.19.x kernels) twy Slackware 12 06-29-2022 02:31 AM
How to upgrade kernels & its assundary other packages WITHOUT removing the old kernels ? babydr Slackware 14 03-16-2022 01:33 AM
Getting Assertion `kernels [x] == kernels [x]' failed with emulator in Slackware 14 Holering Slackware 1 05-10-2013 03:43 PM
backward compatibility in kernels + custom kernels + more queries mmp_3341 Linux - Kernel 1 04-12-2007 07:28 AM
RH 8 kernels and their relation to 'stock' kernels psweetma Linux - Distributions 1 03-29-2003 10:46 PM

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

All times are GMT -5. The time now is 07:44 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