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,180
Original Poster
Rep:
It would appear to me, as an "end user," there is a lot of unnecessary work being done by some board members.
I try and keep it simple, with one exception, as I use f2fS for the system and /home partitions.
I have a small, 200mg, /boot partition formatted with ext4 as LILO cannot boot a f2fs partition.
When they become available I download the new kernel files for -current (or roll my own).
Once the kernel (huge), headers, modules and source are installed, lilo.conf is edited accordingly and lilo is ran.
Before rebooting, the Nvidia driver is uninstalled. Once rebooted with the new kernel the Nvidia driver is installed, e.g., sh ./NVIDIA-Linux-x86_64-470.161.03.run
Then it is time to log out as root and log back in as user and run, startx.
Always works.
Of course, if you are trying to install a driver that hasn't been updated for the newest kernel, you will have problems (of your own creation).
But what do I know, I'm just a "end user".
Last edited by cwizardone; 01-22-2023 at 06:42 AM.
Reason: Typo.
To try to narrow down the issue: echo "blacklist ipv6" > /etc/modprobe.d/ipv6.conf then reboot with the problematic kernel.
I finally solved the issue
Because I use to compile kernels *not provided* by Slackware (6.1.4 vs. 5.19.17) without the suffix "-1".
Usually, I always have a superior version
Before I upgraded to 6.1.4 provided by Slackware, I recompiled my own kernel with the suffix, 6.1.4-1
It was a collision between my previous modules, compiled with compression (*.ko.zst) and the new ones (*.ko) for some of them, that I noticed when generating the initrd.gz
After rm -rf /lib/modules/6.1.4 and reinstalling kernel-modules
All works fine now
Before I upgraded to 6.1.4 provided by Slackware, I recompiled my own kernel with the suffix, 6.1.4-1
For what it's worth, I am running a kernel 6.1.4. The attached scripts builds two packages: "kernel" bundles the kernel, the modules and the sanitized header and "kernel-source".
The kernel package, despite its content, is not heavy[1]:
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,180
Original Poster
Rep:
FWIW: Built and installed the 6.2-rc3 kernel and so far, so good with the nouveau driver. Even VirtualBox-7.0.4-154605-Linux_amd64.run works as it should.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.