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.
Revert "drm/amdgpu: use dirty framebuffer helper"
This reverts commit c89849ecfd2e10838b31c519c2a6607266b58f02 which is
commit 66f99628eb24409cb8feb5061f78283c8b65f820 upstream.
It is reported to cause problems on 5.4.y so it should be reverted for
now.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,176
Original Poster
Rep:
Year 2022, Round 60.
Another batch of updates has been scheduled for release on Wednesday, 12 October 2022, at approximately 07: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: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,019
Rep:
Quote:
Originally Posted by teoberi
stable: 6.0.1-> could we have it in Slackware64-current?
Not that I am against 6 in Slackware (I run it), but what's so special about it except issues with nvidia (expected) and amd (not so expected).
In my opinion, 6 is just incremental upgrade so staying for a while with 5.19.x or moving to 6 does not matter much, unless the whole point is 6? I would just wait patiently for the upgrade. Whenever it comes it comes.
Not that I am against 6 in Slackware (I run it), but what's so special about it except issues with nvidia (expected) and amd (not so expected).
In my opinion, 6 is just incremental upgrade so staying for a while with 5.19.x or moving to 6 does not matter much, unless the whole point is 6? I would just wait patiently for the upgrade. Whenever it comes it comes.
Agreed
+ the fact that 5.19.15 works perfectly well here
From what I've read the patch will be back-ported, but they (those who do that sort of thing) seem to be taking their time.
It also appears the 6.1 series will be the next LTS kernel.
does not seem to be critical (AMD CPU fix) assuming that it took long time to correct. Also at this point one would have to choose between faster cpu and AMD video issues or slower cpu with working graphics and -current doesn't follow LTS (if I am correct - I don't use Slackware kernels)
does not seem to be critical (AMD CPU fix) assuming that it took long time to correct. Also at this point one would have to choose between faster cpu and AMD video issues or slower cpu with working graphics and -current doesn't follow LTS (if I am correct - I don't use Slackware kernels)
About what slower/faster CPUs you talk? The kernel 6.0.1 (and its predecessor) is as fast as usual. It's even faster, in my humble opinion.
However, how I do not run servers, I use since really long time "mitigations=off" and yet no rogue hacker taken over my boxes.
Yeah, too much paranoia around those (theoretical?) CPU vulnerabilities. Seems like after the great success of human made Global Warming, this is the new religion: CPU vulnerabilities
Last edited by LuckyCyborg; 10-12-2022 at 01:16 PM.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,019
Rep:
Quote:
Originally Posted by LuckyCyborg
About what slower/faster CPUs you talk? The kernel 6.0.1 (and its predecessor) is as fast as usual. It's even faster, in my humble opinion.
However, how I do not run servers, I use since really long time "mitigations=off" and yet no rogue hacker taken over my boxes.
Yeah, too much paranoia around those (theoretical?) CPU vulnerabilities. Seems like after the great success of human made Global Warming, this is the new religion: CPU vulnerabilities
Nothing to do with security. It fixes 20yrs old ACPI workaroud that is slowing down (in Tbench at least) modern AMD CPUs. Tbench may more televant to server than desktop environment (500k operations measured simulating server response to client).
Your argument is bizarre though for someone demanding secure boot implementation in Slackware for even though this s..t never worked and never will with current CPU design.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.