LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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 04-02-2020, 09:36 AM   #1
gauchao
Member
 
Registered: Dec 2009
Location: Veneto
Distribution: SLACKWARE 14.2 64bit and 64-current
Posts: 249

Rep: Reputation: 54
Problem upgrading latest Slackware 64-current to kernel 5.4.29


Hi. Slackware 64-current with elilo (it is a UEFI machine) -

Today I have upgraded Slackware 64-current with the new Kernel 5.4.29 (It had 5.4.28)

After upgrading, I have ran #eliloconfig and then I rebooted

Upon reboot, I got the message "no kernel modules found" (I guess it was something like this) and the system froze.

I rebooted with Slackware install disk and took a look at /boot and /boot/efi/EFI/Slackware - I found that vmlinuz-* had different dates under /boot/efi/EFI/Slackware and /boot.

I figured that might be the problem (different copies of vmlinuz*) and so I followed the instructions in /boot/README.initrd by PV - #mkinitrd -c -k 5.4.29 -m etx4 in order to recreate a directory /boot/initrd-tree containing the initrd's filesystem.

System rebooted fine. No error messages anymore.

What could have happened? Hasn't eliloconfig work? I am new to current and elilo; all my machines are running 64-stable and lilo. I appreciate any suggestion!
 
Old 04-02-2020, 10:35 AM   #2
gbschenkel
LQ Newbie
 
Registered: Nov 2010
Location: Porto Alegre, RS - Brazil
Distribution: Slackware64-current & Proxmox
Posts: 16

Rep: Reputation: 8
You don't need run eliloconfig every time, you could just copy the files:
Code:
cp -v /boot/initrd.gz /boot/efi/EFI/Slackware/initrd.gz
cp -v /boot/vmlinuz-generic-Kernel_Version /boot/efi/EFI/Slackware/vmlinuz
Before that, since I have a /etc/mkinitrd.conf, I just run
Code:
mkinitrd -F -k Kernel_Version
or edit the /etc/mkinitrd.conf with the new kernel info and just run
Code:
mkinitrd -F

Last edited by gbschenkel; 04-02-2020 at 10:42 AM.
 
1 members found this post helpful.
Old 04-02-2020, 10:40 AM   #3
teoberi
Member
 
Registered: Jan 2018
Location: Romania
Distribution: Slackware64-current (servers) / Ubuntu (workstations)
Posts: 188

Rep: Reputation: 119Reputation: 119
You do not need to run eliloconfig after each kernel update.
After updating the kernel you can generate initrd.gz and copy the files manually.
Code:
cd /boot
cp vmlinuz-huge-5.4.29 efi/EFI/Slackware/vmlinuz
cp vmlinuz-generic-5.4.29 efi/EFI/Slackware/vmlinuz-generic
cp initrd.gz efi /EFI/Slackware
Of course you must have a properly configured elilo.conf!
 
1 members found this post helpful.
Old 04-02-2020, 12:47 PM   #4
ehartman
Senior Member
 
Registered: Jul 2007
Location: Delft, The Netherlands
Distribution: Slackware
Posts: 1,674

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
Quote:
Originally Posted by gauchao View Post
Today I have upgraded Slackware 64-current with the new Kernel 5.4.29 (It had 5.4.28)

After upgrading, I have ran #eliloconfig and then I rebooted

Upon reboot, I got the message "no kernel modules found" (I guess it was something like this) and the system froze.
Did you update kernel-modules too? Especially when you're using the -generic package (although the -huge kernel sometimes needs it too).
And with that generic kernel, REgenerate the initrd and make sure it is in the /boot/efi/EFI/Slackware directory, for an EFI boot to be able to find it. Using a newer kernel vs an older initrd will result in errors messages like that.

Last edited by ehartman; 04-02-2020 at 12:49 PM.
 
1 members found this post helpful.
Old 04-02-2020, 01:22 PM   #5
gauchao
Member
 
Registered: Dec 2009
Location: Veneto
Distribution: SLACKWARE 14.2 64bit and 64-current
Posts: 249

Original Poster
Rep: Reputation: 54
Thank you for the answers!

@gbschenkl and @teoberi: thank you for the answers. But, shouldn't eliloconfig do it automatically? Like "lilo" does?

@ehartman: I guess you've pointed the problem: I am using -huge kernel, and I do have upgraded kernel-modules. I guess the problem was solved when I have recreated initrd - initrd was probably outdated.

So, every time I have kernel upgraded I should recreate initrd and then copy vmlinuz* and initrd from /boot to /boot/efi/EFI/Slackware?
 
Old 04-02-2020, 01:44 PM   #6
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,240

Rep: Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932
Quote:
Originally Posted by gauchao View Post
@gbschenkl and @teoberi: thank you for the answers. But, shouldn't eliloconfig do it automatically? Like "lilo" does?
Neither lilo, liloconfig, or eliloconfig will create initrds for you, although, I was under the impression that slackpkg was starting to do that now, but maybe it is only done during installation of Slackware and any future buildings of the initrd need to be accomplished manually.

But, per a changelog entry, if an initrd exists in /boot/, then eliloconfig will move the generic kernel and initrd to the EFI partition, not the huge kernel. So, if your initrd was created when you installed Slackware, but you never updated it after upgrading kernels, it would've moved your old initrd and new generic kernel, which would prevent your system from working.

Code:
Mon Jul 29 23:17:22 UTC 2019
a/elilo-3.16-x86_64-10.txz:  Rebuilt.
  eliloconfig: If /boot/initrd.gz exists, install the generic kernel and initrd.
  Otherwise, install the huge kernel.
 
3 members found this post helpful.
Old 04-02-2020, 03:16 PM   #7
gauchao
Member
 
Registered: Dec 2009
Location: Veneto
Distribution: SLACKWARE 14.2 64bit and 64-current
Posts: 249

Original Poster
Rep: Reputation: 54
@bassmadrigal

Thank you again! Slacking and learning...

So exactly when should I run #eliloconfig in a system with EFI?

(I am used to run #lilo after every kernel upgrade with BIOS/MBR, which is not the case here.)
 
Old 04-02-2020, 03:21 PM   #8
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,240

Rep: Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932
eliloconfig is just a fancy script to copy the kernel and initrd (if there) to your EFI partition and ensure the elilo efi stub is registered with your firmware.

But it isn't required like it was with lilo. All you really need to do are ensure that the kernel (and initrd, if required) are in your /boot/efi/EFI/Slackware/ folder and that the elilo.conf in the same folder point to the right files.
 
2 members found this post helpful.
Old 04-03-2020, 09:06 AM   #9
gauchao
Member
 
Registered: Dec 2009
Location: Veneto
Distribution: SLACKWARE 14.2 64bit and 64-current
Posts: 249

Original Poster
Rep: Reputation: 54
Today I have successfully upgraded current to kernel 5.4.30.

I have recreated initrd with mkinitrd and then copied vmlinuz* and initrd.gz files from /boot to /boot/efi/EFI/Slackware.

Everything running fine.

Thank you, guys! For your answers and suggestions.

I will mark this as solved.
 
Old 04-03-2020, 10:04 AM   #10
teoberi
Member
 
Registered: Jan 2018
Location: Romania
Distribution: Slackware64-current (servers) / Ubuntu (workstations)
Posts: 188

Rep: Reputation: 119Reputation: 119
If you want and feel brave you should try to update the microcode for the processor if necessary!
https://www.linuxquestions.org/quest...de-4175621053/
https://www.linuxquestions.org/quest...re-4175654143/
 
1 members found this post helpful.
  


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
Upgrading Debian kernel to latest kernel Gaurishankar Linux - Newbie 2 09-18-2019 07:00 AM
[SOLVED] xterm throw errors with latest terminus-font in latest -current bakura_666 Slackware 10 01-02-2019 03:47 AM
[Slackware64 14.2] Loading error of ath10k firmware with latest kernel-firmware and latest kernel-huge pensador_13 Slackware 3 06-16-2018 12:31 PM
[SOLVED] Slackware 14.2 glibc-2.23 vs Slackware Current glibc-2.24 and the Current 4.4.17 Kernel kjhambrick Slackware 10 08-13-2016 01:00 AM
[SOLVED] Slackware-Current lost sound on latest kernel stormtracknole Slackware 7 08-09-2009 12:41 AM

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

All times are GMT -5. The time now is 08:31 PM.

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
Open Source Consulting | Domain Registration