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.
Each installation of nvidia will remove previous installation. In past you could keep previously installed nvidia drivers for different kernels. If this switch is still available (-K), you could keep two kernels with installed nvidia drivers.
Nice. Very useful.
I no longer need performance video so I use intel card in my laptop which is pure intel as I found out that intel has least compatibility issues with linux kernel.
It does seem to work but I couldn't figure out how to force the NVidia Blob to build 32-bit Libraries from the CommandLine
I'll stick with the tried-and-true, rerun the Blob whenever I switch to a new Kernel
They're already installed! When you install the blob the first time, it does the full install with module, 32-bit libs, and X configuration. If you just give it the -K switch, it'll leave everything else alone and just build the module for the new kernel.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,023
Rep:
after issues related to kernel speed being fixed, slowness is creeping back. e.g. at the peak of kernel being slow, compilation (on my system) took 12min, then improved to 4min and now is 6min. This is between 6.0 to 6.1. I did not test 6.2 obviously as this is rc meaning slow by definition (a lot of debugging enabled) but I suspect that this trend of slowing down is progressing.
this is on 11th Gen Intel Core i7-1185G7 with 32GB RAM so depending on hardware experience may vary.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,183
Original Poster
Rep:
Year 2023, Round 5.
Another batch of updates has been scheduled for release on Wednesday, 18 January 2023, at approximately 15:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (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.