LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-07-2017, 05:32 AM   #1
mick1945
LQ Newbie
 
Registered: May 2017
Posts: 4

Rep: Reputation: Disabled
Linux version prompt before login wrong version


I have upgraded from version 14.2 because LibreOffice asking for version 1.59.0 of boost libraries while my version is 1.63.0. Kernel was upgraded to version 4.9.30. Rebooting I am still receiving messages that I am using Linux 4.4.14. I simply don't know what is going on. Can anyone enlighten me?

Seems like original version 4.4.14 was left in /boot and name only was changed to 4.9.30 as all kernel structures are set as version 4.4.14
 
Old 06-07-2017, 05:42 AM   #2
pan64
LQ Guru
 
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 9,577

Rep: Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816
you have several different kernel versions to use, usually the default one is used. You may need to specify the 4.9.30 as default or you need to choose what to boot (do you have grub installed?)
 
Old 06-07-2017, 08:23 AM   #3
mick1945
LQ Newbie
 
Registered: May 2017
Posts: 4

Original Poster
Rep: Reputation: Disabled
In /boot there is only linux-4.9.30 meaning System.map, config and vmlinuz for both generic and huge have 4.9.30 apended where previously 4.4.14 was. There are none other versions there. vmlinuz is link to vmlinuz-huge-4.9.30. Upgrade actualy removes previous version.

That is why I don't understand why uname -r prints 4.4.14, even /usr/src contain linux-4.9.30
 
Old 06-07-2017, 08:26 AM   #4
pan64
LQ Guru
 
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 9,577

Rep: Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816
what is in /boot/grub/grub.cfg ?
 
Old 06-07-2017, 08:40 AM   #5
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 2,668

Rep: Reputation: 1109Reputation: 1109Reputation: 1109Reputation: 1109Reputation: 1109Reputation: 1109Reputation: 1109Reputation: 1109Reputation: 1109
@pan64, Slackware doesn't use grub by default.

Did you re-run lilo after the upgrade after making sure that lilo.conf matched the new kernel? Did you re-boot as well?
 
1 members found this post helpful.
Old 06-07-2017, 08:47 AM   #6
pan64
LQ Guru
 
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 9,577

Rep: Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816Reputation: 2816
Quote:
Originally Posted by Richard Cranium View Post
@pan64, Slackware doesn't use grub by default.

Did you re-run lilo after the upgrade after making sure that lilo.conf matched the new kernel? Did you re-boot as well?
thanks, I missed that. but anyway it is an issue with the boot loader.
 
Old 06-07-2017, 08:48 AM   #7
kjhambrick
Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 953

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
mick1945 --

I am Too Slow again

Please post the output of: ls -la /boot

Best results if you post the listing between [code] and [/code] tags ...

How did you install 4.9.30 ( installpkg ? upgradepkg ? or one of the package managers ? )

Do you run lilo, elilo or grub or something else ?

-- kjh

Last edited by kjhambrick; 06-07-2017 at 08:50 AM. Reason: too slow ... Richard Cranium beat me to it ...
 
Old 06-07-2017, 11:04 AM   #8
mick1945
LQ Newbie
 
Registered: May 2017
Posts: 4

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by kjhambrick View Post
mick1945 --

I am Too Slow again

Please post the output of: ls -la /boot

Best results if you post the listing between [code] and [/code] tags ...

How did you install 4.9.30 ( installpkg ? upgradepkg ? or one of the package managers ? )

Do you run lilo, elilo or grub or something else ?

-- kjh
No need for grub or lilo, computer boots directly on switch on.Instaled by "slackpkg upgrade-all"

[code]
bash-4.4$ ls -la /boot
total 36293
drwxr-xr-x 5 root root 4096 Jun 7 10:27 .
drwxr-xr-x 23 root root 4096 Jun 7 17:32 ..
lrwxrwxrwx 1 root root 37 May 11 05:12 README.initrd -> /usr/doc/mkinitrd-1.4.9/README.initrd
lrwxrwxrwx 1 root root 22 Jun 7 10:27 System.map -> System.map-huge-4.9.30
-rw-r--r-- 1 root root 2916435 May 26 21:55 System.map-generic-4.9.30
-rw-r--r-- 1 root root 4246271 May 26 22:05 System.map-huge-4.9.30
-rw-r--r-- 1 root root 137 Jan 17 21:27 boot_message.txt
lrwxrwxrwx 1 root root 18 Jun 7 10:27 config -> config-huge-4.9.30
-rw-r--r-- 1 root root 169175 May 26 21:55 config-generic-4.9.30
-rw-r--r-- 1 root root 169175 May 26 22:05 config-huge-4.9.30
drwxr-xr-x 3 root root 1024 Jan 1 1970 efi
-rwxr-xr-x 1 root root 214120 Mar 29 2013 elilo-ia32.efi
-rwxr-xr-x 1 root root 239720 Apr 1 2016 elilo-x86_64.efi
drwxr-xr-x 2 root root 4096 Apr 26 20:43 grub
drwxr-xr-x 14 root root 4096 May 14 15:15 initrd-tree
-rw-r--r-- 1 root root 8181163 May 14 15:15 initrd.gz
lrwxrwxrwx 1 root root 19 Jun 7 10:27 vmlinuz -> vmlinuz-huge-4.9.30
lrwxrwxrwx 1 root root 22 Jun 7 10:27 vmlinuz-generic -> vmlinuz-generic-4.9.30
-rw-r--r-- 1 root root 4856096 May 26 21:55 vmlinuz-generic-4.9.30
lrwxrwxrwx 1 root root 19 Jun 7 10:27 vmlinuz-huge -> vmlinuz-huge-4.9.30
-rw-r--r-- 1 root root 8194336 May 26 22:05 vmlinuz-huge-4.9.30
bash-4.4$
bash-4.4$uname -r
4.4.14
bash-4.4$
[/code]
 
Old 06-07-2017, 11:50 AM   #9
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,632

Rep: Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571Reputation: 2571
Quote:
Originally Posted by mick1945 View Post
No need for grub or lilo, computer boots directly on switch on.
That doesn't mean that a boot loader is not installed. There is certainly one unless you be using an EFI stub (a kernel that also acts as an EFI boot image) which is very unlikely.

Type as root:
Code:
lilo -t -v
Then if there is no error or warning:
Code:
lilo
After that the kernel 4.9.30 should be used. Else (and in case the first command displays an error), please provide output of
Code:
cat /etc/lilo.conf

Last edited by Didier Spaier; 06-07-2017 at 11:51 AM.
 
1 members found this post helpful.
Old 06-07-2017, 11:57 AM   #10
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,213

Rep: Reputation: 2177Reputation: 2177Reputation: 2177Reputation: 2177Reputation: 2177Reputation: 2177Reputation: 2177Reputation: 2177Reputation: 2177Reputation: 2177Reputation: 2177
Lilo operates by noting the location of a file on the harddrive. This is the physical address on the harddrive, not the location within a folder structure. When you delete a file, it only removes references to that file, not the file itself (unless you run some form of secure delete, but that's another topic). So, even though the file has been "deleted", the file still exists on the harddrive, and that is what lilo is pointing to and why you're booting that kernel.

(Side note: These "deleted" files stay on the drive until that "empty" space is overwritten by a new file, so this would only work until that space is overwritten, then you'd get a kernel panic when you try and boot.)

When you install or upgrade a new kernel, you'll need to ensure your /etc/lilo.conf is up-to-date and then you can run lilo to install the updated bootloader information pointing to the new kernel location. You can also run lilo -t to test the configuration before you actually install the updated bootloader information.
 
2 members found this post helpful.
Old 06-07-2017, 10:02 PM   #11
Paulo2
Member
 
Registered: Aug 2012
Distribution: Slackware64-current (started with 13.37(32))
Posts: 323

Rep: Reputation: 86
Quote:
Originally Posted by mick1945 View Post
No need for grub or lilo, computer boots directly on switch on.Instaled by "slackpkg upgrade-all"
Did you suspend or hibernate?
 
Old 06-08-2017, 05:13 AM   #12
laprjns
Member
 
Registered: Oct 2005
Location: Connecticut USA
Distribution: SalixOS
Posts: 99

Rep: Reputation: 51
Quote:
Originally Posted by mick1945 View Post
Code:
drwxr-xr-x  3 root root    1024 Jan  1  1970 efi
Since the old kernel is booting and it is not in the /boot directory then you are most likely running in efi mode Check for the contents of /boot/efi/EFI/Slackware. If there are files there (vmlinuz,elilo.conf and elilo.efi) then you need to run eliloconfig to copy over the kernel from boot to your ESP partition (/boot/efi/EFI/salckware/)
 
Old 06-08-2017, 11:20 AM   #13
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware, Xubuntu
Posts: 195

Rep: Reputation: 28
Quote:
Rebooting I am still receiving messages that I am using Linux 4.4.14.
Which messages exactly? From "uname -a" -- which comes from the kernel actually running? At boot -- which comes from /etc/motd? ...

Last edited by burdi01; 06-08-2017 at 11:26 AM.
 
Old 06-18-2017, 01:22 PM   #14
mick1945
LQ Newbie
 
Registered: May 2017
Posts: 4

Original Poster
Rep: Reputation: Disabled
On installing Slackware, I have chosen what is called
"Slackware Linux custom USB boot stick".

I have empty /boot/grub directory, no /etc/lilo.conf and no lilo.

After length of time I have been using computer, simply switching it on and booting elilo.conf was taking care of it until upgrade. Didn't even remember it.

Real culprit was vmlinuz on USB stick which was from original installation and version 4.4.14 which remained.

Replacing it with version 4.9.30 solved the problem.
 
Old 06-18-2017, 04:29 PM   #15
Nille_kungen
Member
 
Registered: Jul 2005
Posts: 397

Rep: Reputation: 127Reputation: 127
You could also run eliloconfig and then you shouldn't need an USB boot stick.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
cat /proc/version - displays wrong version babu198649 Linux - Newbie 2 11-10-2008 04:10 AM
Regarding distribution + kernel version + gcc version + glib version. JCipriani Linux - General 8 04-19-2008 02:54 PM
slackware startx starts the wrong version, i didn't even know i had another version edman007 Linux - Software 3 05-16-2004 07:38 PM
display wrong linux version jorisb Linux - Software 2 03-09-2004 10:28 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:14 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration