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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,162
Original Poster
Rep:
Year 2022, Round 12.
Another batch of updates has been scheduled for release on Wednesday, 16 February 2022, at approximately 09:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).
5.16.10 on slackware64-14.2 is running fine (4 days uptime now) with nvidia 340.108 + patches from https://aur.archlinux.org/packages/nvidia-340xx. My card is a GeForce GT 240, about 12 years old now.
Xorg server 1.20.x (slackware64-15.0) is supposed to work with nvidia 340.108 + patches on linux kernel 5.15.y. Is anyone running this combination, and is it stable? I'd prefer to hear that it works before I upgrade to Slackware64-15.0 or -current. It would be nice if nvidia would just make a 340.109 release that brings in those patches and more support, maybe for xorg 1.21.x. I like slackare-current right now, but I'm afraid it will suddenly move to xorg 1.21.
edit: the new version is 21.1, they flipped the numbers
Another batch of updates has been scheduled for release on Wednesday, 23 February 2022, at approximately 09:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).
root@a285:~# uname -a
Linux a285.s8r.uk 5.17.0-rc5 #1 SMP PREEMPT Mon Feb 21 16:39:30 CET 2022 x86_64 AMD Ryzen 5 PRO 2500U w/ Radeon Vega Mobile Gfx AuthenticAMD GNU/Linux
root@a285:~#
I got as far as this, and to the untrained eye it seems to behave - I'm running Firefox and typing, that's not a bad start. I'm just wondering what might be considered adequate as a test harness.
root@a285:~# uname -a
Linux a285.s8r.uk 5.17.0-rc5 #1 SMP PREEMPT Mon Feb 21 16:39:30 CET 2022 x86_64 AMD Ryzen 5 PRO 2500U w/ Radeon Vega Mobile Gfx AuthenticAMD GNU/Linux
root@a285:~#
I got as far as this, and to the untrained eye it seems to behave - I'm running Firefox and typing, that's not a bad start. I'm just wondering what might be considered adequate as a test harness.
Here, I consider that a kernel works well when these below work well on my setup (AMD ryzen 7):
- wifi (intel AX200)
- bluetooth (intel AX200)
- amdgpu
- sound
- nfs, samba
- hibernate
And, ditto after resume
note: of course, other stuff like keyboard, touchpad, etc ...
I am also with kernel 5.17.0-rcX, the bluetooth still has problems after suspend/resume with 5.16. But as soon as this problem is fixed, I will stay on the one provided by Slackware.
That's very useful, thank you marav. That sounds checkable within a couple of hours, which would make for a timely response.
The naming convention on 5.x-rcn needs 5.x.0-rcn for the modules and consequently for mkinitrd? Which differs from the normal kernel naming convention 5.x.y and 5.x.y-rcn? Or is that just me going astray. The extra .0 was unexpected at that point.
That's very useful, thank you marav. That sounds checkable within a couple of hours, which would make for a timely response.
The naming convention on 5.x-rcn needs 5.x.0-rcn for the modules and consequently for mkinitrd? Which differs from the normal kernel naming convention 5.x.y and 5.x.y-rcn? Or is that just me going astray. The extra .0 was unexpected at that point.
Right
"Mainline" kernels are always named like this : X.Y.0-rcZ
and Z goes from 1 to 7 (sometimes 8)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.