Kernel panic after slackware-current update
 

Hello everyone, it's still me with a problem with my kernel!

This morning I did the last upgrade, including the upgrade from 5.4.40 to 5.4.41 kernel.

The last 2 upgrades were carried out without problems, after upgrading normally I did:

for my initrd.gz file. But strangely, it didn't work, error bash, command not found.

I created a bootable usb key with the latest Slackware64-current version, I found documentation: https://docs.slackware.com/howtos:sl...uefi_and_elilo

but I am not sure that this is necessary, because when I mount my SSD to access my partition which allows me to boot, I see that my initrd.gz file is not up to date while vmlinuz * them the are (5.4.41). (To understand what I mean with regard to the initrd.gz file, it is that the last modification date is May 12th, while vmlinuz * have been modified today)

In my opinion, the problem comes from initrd.gz, but I can't see how I can fix it.

I was finally able to boot on vmlinuz, and this is what I get

Attachment 33225

Honestly, I don't know what to do, I have another pc with Slackware 14.2 since November 2019, I never had a problem, or I was always able to solve them

Please tell us more about this error. When did it occur?

You will need to chroot into the system and re-run the mkinitrd generator and then lilo, or eliloconfig, or grub-mkconfig, depending on how you've set up booting.

Here's a recent post going over the basic chroot setup if you haven't done that before: https://www.linuxquestions.org/quest...ml#post6108585
Theres also a few pages at docs.slackware.com that go over chrooting into the system.

Also I generally run the mkinitrd generator as:
Hasn't given me a problem yet.

Thank you Alien Bob
The error occurred after the upgrade, normally when I type commands, I use the tab key for automatic completion, but it did not work so I entered the command by myself and I received this error.

I'm only new to Slackware, but it seems that the brackets, which surround the code should not be there. Nor should the -r at the end of your line of code

The command should, according to the beginners guide be run as root. Not as your code quote indicates as a normal user.

http://docs.slackware.com/slackware:beginners_guide

Once you get the above code corrected so it runs, the resultant code needs to be run as root to create a "new" intrd.gz, which is then added to lilo .

Thank you 0XBF

I managed to execute the commands, I mounted my partitions and I chroot /mnt, strangely eliloconfig does not work,
However, my laptop boot in EFI.
mkinitrd_command_generator.sh works, I tried to restart it shutdown -r -t sec 1, but I get an error, I also tried /etc/rc.d/rc.6 but I get the same error, but I'm not allowed to enter other commands afterwards

You can find this command in the Slackware docs, it's much faster

https://docs.slackware.com/howtos:sl...ge_for_generic

Sorry, I forgot to type exit before reboot, now I always have the same screen when I boot except that I have no error concerning the kernel

I modified elilo.conf, I deleted root = / dev / initramfs and I added a line root = / dev / nvme0n1p3 because my root partition is this and I had already configured my file like this before that I have this problem, but I have the same error message, it is only the partition which changes

I'm not saying this is best practice or anything, but when there's a kernel update all I do is copy the vmlinuz-huge-5.x.x from /boot to /boot/efi/EFI/Slackware/ named as just vmlinuz.

My elilo.conf
I commented out the initrd since I'm using kernel-huge.

Is this best practice? I really doubt it. Running liloconfig on an MBR system after kernel upgrade works. Running eliloconfig on an EFI system after kernel upgrade does not. It results in exactly the error you're showing right now. I've also never had success using mkinitrd with kernel-generic so I decided to just shelf it in favor of huge.. hasn't give me any issues yet.

I've found so many conflicting answers on how to properly update the kernel in slackware on an EFI system that I've just settled on what I know works.

In bash, the $( something ) construct means to run the output of something as a command. The -r option to the mkinitrd_command_generator.sh command means to output something that can be executed.

As an example, I run the following shell script named mkinit.sh after an upgrade (I use grub versus lilo/elilo)...

make-amd-ucode-cpio.sh contains...

and mkgrub.sh contains...
All of my commands above belong to root and are run as that user.

The OP's quote gave no indication of the shell prompt.

I honestly do thank you for trying to help a fellow Slackware user. Please don't give up trying to help others, despite my negative comments.

Hi ReFracture

Is that I did, it allowed me to boot but I still have the problem as mentioned in my other post. On my other laptop, I am still using my generic kernel and have never had a problem with this.

However you run that script (although it will only let you if you are root) there should be an output something like follows:
Note that if you run ...
... as a regular user it will tell you you need to be root to run it.
If you run ...
... as a regular user then you will miss the "must be root error" which ends up inside the $( ... ) and leads to an error message "command not found".

And yes, just fix the system in chroot and then exit the chroot to get back to the console.

Please make sure that /dev/nvme0n1p3 is the partition with the install on it, and put a line with the location of initrd.gz in your boot entry as well. You can use ReFracture's entry as an example (although he isn't using an initrd), or here's one from a machine I have running with EFI:
Hopefully you get this sorted.

@0XBF
My file is identical, only the root path is different and nvme0n1p3 is my root partition. I configured my elilo.conf file in 2 ways, the first, only by changing the path for root, and the second by indicating the path for vmlinuz as well as initrd.gz.

However, before the problem started, my generic kernel was well configured because I was booting on it.

I'm continuing the research, I don't want to reinstall from scratch again, I would update my thread