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.
Linux 5.15.33 + NVidia 510.60.02 + VMWare Workstation 16 Pro 16.2.3 build-19376536 running fine on Slackware64 15.0 + Multilib
Also works fine on clean slackware64 without any of these things installed.
And I think whenever the free Workstation Player works fine, the pro version will work fine too.
Based on same thing with different license, no? Why specify pro, do you have shared key for slackware users to test?
Also works fine on clean slackware64 without any of these things installed.
And I think whenever the free Workstation Player works fine, the pro version will work fine too.
Based on same thing with different license, no? Why specify pro, do you have shared key for slackware users to test?
elcore --
I don't have a sharable key and I didn't know that VMWare Workstation Player and Pro are then same thing but that makes sense
I don't have a sharable key and I didn't know that VMWare Workstation Player and Pro are then same thing but that makes sense
-- kjh
It's not the exact same thing, workstation includes a player which is free for home user.
Workstation is for business, and not many of us here are able to test it because it's expensive.
Installer and release build-id are the same, so it's mostly the same thing but it costs nothing to test a vmware player.
It's all kinda offtopic here, since it's not part of kernel.
...........But at least it's not looking particularly odd, and we have fixes all over.
Drivers is the bulk of it, and there's a little bit of everything here, although the AMD GPU driver fixes are perhaps the most noticeable. But there's also networking, scsi, rdma, block, you name it........
Last edited by cwizardone; 04-10-2022 at 08:04 PM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,142
Original Poster
Rep:
Year 2022, Round 22.
Another batch of updates has been scheduled for release on Thursday, 14 April 2022, at approximately 06:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Wednesday (depending on your time zone).
From: Greg Kroah-Hartman
Date: Tue Apr 12 2022 - 03:42:56 EST
----------------------
Note, this will be the LAST 5.16.y kernel to be released. Please move
to the 5.17.y tree at this time.
----------------------
From: Greg Kroah-Hartman
Date: Wed Apr 13 2022 - 14:56:23 EST
----------------------------
Note, this is the LAST 5.16.y kernel release. It is now end-of-life.
Please move to the 5.17.y branch at this point in time.
----------------------------
On slackware64-14.2, I upgraded the kernel from 5.15.30, which ran fine, to 5.15.33 (I skipped .31 and .32). I upgraded because 5.15.33 looked like it fixes significant potential bugs. Performance seemed more sluggish on 5.15.33. I was beginning to upgrade to 5.15.34 by extracting the tarball, and then I started to get messages (dmesg) like shown in this post:
The problem has to do with the "clocksource". The ChangeLog-5.15.33 shows that some changes were made to "clocksource"-related drivers. I think they broke something on my hardware, which is an Intel Xeon X3450 (Lynnfield) on Intel 3420 chipset (Asus P7F-E motherboard). So, my system is old, 2009 era hardware.
I don't think 5.15.34 reverts or changes any of the clocksource-related stuff. So, for now, I'm going back to 5.15.30.
If anyone understands this clocksource problem, please explain more. If you have also had this problem, maybe post what hardware you were running. I wonder if this is just a problem on older hardware, or newer too?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,142
Original Poster
Rep:
Year 2022, Round 23.
Another batch of updates has been scheduled for release on Saturday, 16 April 2022, at approximately 11:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Friday (depending on your time zone).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.