[SOLVED] Current (Live): kernel 4.9.36 update problem

Sefid par · 07-08-2017, 08:58 AM

I've updated the kernel 4.9.36 in last update of great Slackware Current (slackware live).
There was a problem.

Code:

uname -a

says: the kernel is 4.9.34;
Another problem is about loading kernel modules. while the system works fine, When I tried to load new module (named usblp), an error appears:

Code:

# modprobe usblp
modprobe: FATAL: Module usblp not found in directory /lib/modules/4.9.34

I know the system has updated the kernel:

Code:

ls /var/log/packages/kernel-*
/var/log/packages/kernel-firmware-20170626git-noarch-1
/var/log/packages/kernel-generic-4.9.36-x86_64-1
/var/log/packages/kernel-headers-4.9.36-x86-1
/var/log/packages/kernel-huge-4.9.36-x86_64-1
/var/log/packages/kernel-modules-4.9.36-x86_64-1
/var/log/packages/kernel-source-4.9.36-noarch-1

I don't know how to fix this. I need help :-)

Sefid par · 07-08-2017, 09:26 AM

I found the solution :-D
I had not restart the system. I know it doesn't need to restart the system after kernel update. But I don't know how to do it yet. I've rebooted system anyway. Apologize.

THanks

orbea · 07-08-2017, 09:59 AM

You should restart the system after a kernel update if you want to use the new kernel. Also its advisable to not use upgradepkg when installing a new kernel, but rather installpkg so that the old kernel is still there. It would prevent this issue and offer a fallback in case the new kernel introduces new problems.

bassmadrigal · 07-08-2017, 11:28 PM

Quote:

Originally Posted by Sefid par

I found the solution :-D
I had not restart the system. I know it doesn't need to restart the system after kernel update. But I don't know how to do it yet. I've rebooted system anyway. Apologize.

Live kernel patching (allowing you to patch the kernel without rebooting) has been included in the kernel since the 4.0 series and has been available in other forms even before that, however, Slackware does not use that method when putting out kernel updates (websites seem to imply live patching can cause instabilities, which is anti-Slackware

). To use the new kernel, you need to reboot the system for that to take effect.

If you did want to look into the live patching, it would need to be something you do yourself as Slackware currently has no official support for it. I'm not even aware of any documentation on doing it in Slackware...