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.
Interesting. Does that mean that upstream fixed the efi boot stub, if the boot stub works for booting?
No. IMO all is because of this:
Code:
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.
Thanks to PiterPunk.
Now my system works well with patched elilo, refind and 5.19.1 kernel.
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.
Thanks to PiterPunk.
Now my system works well with patched elilo, refind and 5.19.1 kernel.
He talks about direct booting the kernel using UEFI, with no bootloader at all.
Yes, it's possible, because thanks to mentioned EFI stub, any kernel is also a valid EFI binary, capable to be executed by UEFI firmware.
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.
Thanks to PiterPunk.
Now my system works well with patched elilo, refind and 5.19.1 kernel.
Yeah, the poster above (Chuck) mentioned booting via the stub, so elilo wouldn't factor in. That booting the kernel directly worked with the 5.19.1 kernel made me wonder if something were changed upstream.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,164
Original Poster
Rep:
FWIW: Just built and installed the 6.0-rc1 kernel.
As expected, the Nvidia driver did not build.
OTOH, I was pleasantly surprised to see VirtualBox-Test-Build-6.1.37-152741, build and run as it should.
Using the nouveau driver for now and so far, so good.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,164
Original Poster
Rep:
Year 2022, Round 49.
Another batch of updates has been scheduled for release on Wednesday, 17 August 2022, at approximately 18:00 GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,164
Original Poster
Rep:
If you are using the 5.18.y kernel, be forewarned.
Quote:
From: Greg Kroah-Hartman
Date: Wed Aug 17 2022 - 09:34:28 EST
.............
5.18 is only going to be alive for one more week at most, so I wouldn't
worry too much about this.
thanks!
greg k-h
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,164
Original Poster
Rep:
Year 2022, Round 50.
Another batch of updates has been scheduled for release on Sunday, 21 August 2022, at approximately 15:00 GMT. If no problems are found while testing the release candidates, they might be available sometime on Saturday (depending on your time zone).
-------------------
NOTE, this is the LAST 5.18.y stable release. This tree will be
end-of-life after this one. Please move to 5.19.y at this point in time
or let us know why that is not possible.
-------------------
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.