LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Updating through slackpkg didnt upgraded the kernel in slackware64-current (https://www.linuxquestions.org/questions/slackware-14/updating-through-slackpkg-didnt-upgraded-the-kernel-in-slackware64-current-4175573299/)

sinar.kk 02-26-2016 03:08 AM
Updating through slackpkg didnt upgraded the kernel in slackware64-current
 
Hi all,

Today i upgraded my slackware64-current , i was using 17-jan-2016 slackware64-current

today i went and uncommented a mirror for slackware64-current from /etc/slackpkg/mirror

and run as root slackpkg update

everything was downloading correctly and in var/lib/slackpkg/ChangeLog.txt it is showing

"a/kernel-generic-4.4.2-x86_64-1.txz: Upgraded.
a/kernel-huge-4.4.2-x86_64-1.txz: Upgraded.
a/kernel-modules-4.4.2-x86_64-1.txz: Upgraded"

and so on others , i rebooted my machine when i do uname -r it is still showing "4.4.0"

what could have gone wrong?

willysr 02-26-2016 03:16 AM
Have you ran /sbin/lilo ?

sinar.kk 02-26-2016 03:23 AM
no, will run now and let you know

sinar.kk 02-26-2016 03:26 AM
Ran /sbin/lilo this is the output

Quote:
Warning: LBA32 Addressing assumed
Added linux *
One warning was issued

And after i checked its still 4.4.0

Didier Spaier 02-26-2016 03:41 AM
That an upgrade shows in the Changelog do not tell if it was applied. You should look in /var/log/packages instead

Either the kernel is blacklisted in /etc/slackpkg/blacklist and was not installed or for some reason the symlink /boot/linux does not point to the new kernel.

Anyway people who run Slackware current are expected to be able to solve themselves this kind of issue and furthermore it is not recommended to upgrade to a new kernel, but instead to first install it alongside the previous one, just in case. Only when you are sure you can boot with the new kernel you can get rid of the old one.

slacker1337 02-26-2016 04:00 AM
Any chance it was blacklisted?

sinar.kk 02-26-2016 04:01 AM
No it is not blacklisted , i dont know what to do next :(

Didier Spaier 02-26-2016 04:07 AM
Show the results of following commands, typed as root:
Code:
ls -l /var/log/packages/kernel*
cat /etc/lilo.conf
ls -l /boot/vmlinuz*

phenixia2003 02-26-2016 04:56 AM
Hello,

Quote:
Originally Posted by sinar.kk (Post 5506400)
Today i upgraded my slackware64-current , i was using 17-jan-2016 slackware64-current

today i went and uncommented a mirror for slackware64-current from /etc/slackpkg/mirror

and run as root slackpkg update

everything was downloading correctly and in var/lib/slackpkg/ChangeLog.txt it is showing

"a/kernel-generic-4.4.2-x86_64-1.txz: Upgraded.
a/kernel-huge-4.4.2-x86_64-1.txz: Upgraded.
a/kernel-modules-4.4.2-x86_64-1.txz: Upgraded"

and so on others , i rebooted my machine when i do uname -r it is still showing "4.4.0"

what could have gone wrong?
Correct me if I'm wrong but it seems you didn't run slackpkg upgrade-all after slackpkg update.

slackpkg update only download metadata from slackware mirror. To install the updates you need to run slackpkg upgrade-all or, slackpkg upgrade kernel to only upgrade the kernel.

--
SeB

sinar.kk 02-26-2016 05:58 AM
Yes !!! @phenixia2003 Thank you , i forgot give the upgrade-all , now it works , thanks , marking this thread as solved

kevison 02-26-2016 06:08 AM
sometimes it just something simple ;)


All times are GMT -5. The time now is 12:10 PM.