I made the mistake to update my kernel on my Slackware 14.2 from 4.4.14 to 4.4.38. The new kernel causes coil whine in my laptop and I don't have the time to debug the reasons. What is the safe and proper way to downgrade the kernel with the one provided by the official release of 14.2.

Best to ask in LQ Slackware, but should be as easy as installing the old kernel Slackware Packages just like you installed the newer packages. upgradepkg(8) does not care about version numbers.

John

PS, requested a move to LQ Slackware

1 members found this post helpful.

4.4.14 has a few security flaws that are fixed in later versions. I wouldn't call it "safe" to downgrade. Maybe it's better to look in your logs and find out whats wrong with your system?

Anyway... You can search the word "kernel" on this site: http://packages.slackware.com/

Here is the generic x86 4.4.14 kernel:
http://packages.slackware.com/?r=sla....14-i586-1.txz

and the generic x86_64 4.4.14 kernel:
http://packages.slackware.com/?r=sla...4-x86_64-1.txz

You can also find this software on your Slackware installation disc/ISO.

To add to mralk3's post, to downgrade a package on Slackware is the same process as upgrading a package. You use upgradepkg. Upgradepkg doesn't actually check to see if the package version is newer or older, only that it is different. So you would just run upgradepkg on the kernel's, make sure your lilo.conf is accurate, rerun lilo, and reboot.

Keep in mind, in addition to the kernel's mralk3 linked to, you'll also want the modules, source, headers, and huge kernel.

But I would only do this as a temporary measure, because as mralk3 stated (again), there are serious security issues with the older kernels in the 4.4 series, and it would be wise to remain on them for as little time as possible.

You could also give 55020's kernels a shot, he has a system that will automatically build the latest 4.4 series kernel once announced by kernel.org. It is up to 4.4.63.

https://dusk.idlemoor.tk/linux-4.4/x86_64/

FWIW, I've had that happen when I set the timer frequency too high (1000hz).

I thought Slackware kernels have been tickless (CONFIG_NO_HZ) for years though.