SlackwareThis Forum is for the discussion of Slackware Linux.
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.
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.
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.
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?
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
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
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.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,000
Rep:
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.
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.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,000
Rep:
Quote:
Originally Posted by Didier Spaier
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.