LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 03-20-2022, 01:16 AM   #1
breaker
Member
 
Registered: Mar 2022
Distribution: Slackware 15.0
Posts: 87

Rep: Reputation: 29
after # slackpkg upgrade-all upgrades kernel, making a new initramfs is necessary, but not automatic, right?


On Slackware 15.0 x64

Code:
# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all
After the 'slackpkg upgrade-all' I did get this warning, which was nice:
Code:
Your kernel image was updated, and lilo does not appear to be used on 
your system.  You may need to adjust your boot manager (like GRUB) to 
boot the appropriate kernel (after generating an initrd if required).
Press the "Enter" key to continue...
It updated my kernel from 5.15.19 to 5.15.27 but I use ELILO and the EFI System Partition isn't in the fstab nor mounted automatically, and so ELILO was using the wrong kernel next boot.

But, I couldn't mount the ESP at that moment after the upgrade:
Code:
bash-5.1# mount -t vfat /dev/sdb2 /boot/efi
mount: /boot/efi: unknown filesystem type 'vfat'
I had to use a USB pen drive with GRUB to boot the new kernel in /boot because in the ESP, it had the old. Then I used /usr/share/mkinitrd/mkinitrd_command_generator.sh to suggest a mkinitrd command line, which I used to build a new initrd.gz, mounted the ESP under /boot/efi, and copied the new initrd.gz over the old one in the ESP, and copied the new vmlinuz-generic-5.15.27 to the ESP renaming it to vmlinuz since that is what the elilo.conf is using for the name.

Is this pretty much the routine, or is there a way to automate this? I guess before I run slackpkg upgrade-all next time, I could have a script ready to do everything, like mount the ESP under /boot/efi, make the initrd.gz, and copy the files.

I'm using LVM and the filesystems are ext4.

I guess, in a way this is really a limitation of UEFI only being able to use FAT32, etc. filesystems. Stupid UEFI, lol.

Last edited by breaker; 03-20-2022 at 01:24 AM.
 
Old 03-20-2022, 03:05 AM   #2
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, others
Posts: 5,897
Blog Entries: 1

Rep: Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081
Sounds like a limitation of not keeping kernels and initrds in a native filesystem, either on the root filesystem in the /boot directory, or on a native filesystem mounted to /boot/. Most distros mount the ESP on /boot/efi/, and put no kernels there. My Slackware kernels are also in the root filesystem in /boot/.

Had the ESP been mounted when the initrd was generated, I would expect vfat support would have been included in the new initrd.
 
Old 03-20-2022, 03:35 AM   #3
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,922

Rep: Reputation: 5040Reputation: 5040Reputation: 5040Reputation: 5040Reputation: 5040Reputation: 5040Reputation: 5040Reputation: 5040Reputation: 5040Reputation: 5040Reputation: 5040
Yes, that caught me out once. After you upgrade the kernel-modules package the FAT filesystem driver is no longer present, so if you've not already loaded it into the kernel you will no longer be able to access FAT partitions.

Workaround is to make sure you mount your efi partition before you run upgrade against a kernel-modules packages.

The other, safer, option is to always update your kernel packages with installpkg rather than upgradepkg/upgrade-all, and then removepkg the old ones after you've booted into the new kernel. This is why some folks prefer to blacklist the kernel packages in slackpkg and handle them manually.
 
2 members found this post helpful.
Old 03-20-2022, 05:20 AM   #4
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,079

Rep: Reputation: Disabled
Quote:
Originally Posted by breaker View Post
I guess, in a way this is really a limitation of UEFI only being able to use FAT32, etc. filesystems. Stupid UEFI, lol.
Quite the opposite, this was a very wise decision from the writers of the specification. This allows the developers of EFI applications, including but not limited to OS loaders, to follow only one well known specification to write their code, thus drastically reducing the amount of work to do.

Last edited by Didier Spaier; 03-20-2022 at 05:22 AM.
 
2 members found this post helpful.
Old 03-20-2022, 10:36 AM   #5
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado, USA
Distribution: Slackware
Posts: 930

Rep: Reputation: 479Reputation: 479Reputation: 479Reputation: 479Reputation: 479
Quote:
Originally Posted by GazL View Post
The other, safer, option is to always update your kernel packages with installpkg rather than upgradepkg/upgrade-all, and then removepkg the old ones after you've booted into the new kernel. This is why some folks prefer to blacklist the kernel packages in slackpkg and handle them manually.
To quote the Mandalorian: “This Is The Way”

I install multiple kernels & change the kernel naming convention used by Slackware in the ESP.

For new kernels I use installpkg along with blacklisting kernel-generic, huge, modules & source in slackpkg. To generate the new initrd file I use /etc/mkinitrd.conf with: "KRNL="5.16.16" mkinitrd -F -k $KRNL -o /boot/initrd-$KRNL.gz"

Next mount the ESP & copy the newly installed kernel files to the ESP. Finish by modifying elilo.conf for the new kernels.

If you want to keep 2 kernel versions, remove the kernel versions older than those 2 & the associated ESP files & reboot.

Here's my /boot/efi/EFI/Slackware/elilo.conf:
Code:
prompt
timeout=50
default=Gen5.16.16
image=vmlinuz-generic-5.16.15
  label=Gen5.16.15
  initrd=initrd-5.16.15.gz
  append="root=/dev/sda2 resume=/dev/sda1"
  read-only
image=vmlinuz-generic-5.16.16
  label=Gen5.16.16
  initrd=initrd-5.16.16.gz
  append="root=/dev/sda2 resume=/dev/sda1"
  read-only
Here's my /etc/mkinitrd.conf:
Code:
SOURCE_TREE="/boot/initrd-tree"
CLEAR_TREE="1"
KEYMAP="us"
MODULE_LIST="ext4"
ROOTDEV="/dev/sda2"
ROOTFS="ext4"
UDEV="1"
WAIT="1"
MODCONF="1"
Here's my /etc/fstab ESP entry with the "noauto" option. Mounting the ESP with "mount /boot/efi":
Code:
UUID=1234-5678   /boot/efi         vfat        defaults,noauto         1   0
This process is all scripted.
 
Old 03-20-2022, 01:46 PM   #6
breaker
Member
 
Registered: Mar 2022
Distribution: Slackware 15.0
Posts: 87

Original Poster
Rep: Reputation: 29
Thanks to all of you friendly and helpful gurus on LinuxQuestions.org!

@mrmazda

Others may correct me if I'm wrong, but I think with ELILO the kernel needs to be in the ESP (EFI System Partition) for booting, and not in the /boot directory. This morning I tried adding another image stanza to my elilo.conf, but it couldn't boot it at all:
Code:
image=/dev/ace0/boot/vmlinuz
        label=vmlinuz
        initrd=/dev/ace0/boot/initrd.gz
        read-only
        root=/dev/ace0/root
        append=""
While the working stanza is:
Code:
image=vmlinuz
        label=efi
        initrd=initrd.gz
        read-only
        root=/dev/ace0/root
The page here seems to confirm this in the section UEFI and ELILO.
Unless it is because I'm using LVM? The LVM and Slackware are on /dev/sda while Windows Server and the ESP live on /dev/sdb, and I use F12 at boot to pick Windows on occasion.
Code:
root@ace:~# lsblk -f
NAME        FSTYPE      FSVER    LABEL    UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
sda         LVM2_member LVM2 001          dqCChJ-I02s-r3hR-IXBh-o4ye-LrVb-cfw7S7                
├─ace0-swap swap        1                 dd90506d-3f21-42e6-b4d0-30ed3b81197a                  [SWAP]
├─ace0-boot ext4        1.0      boot     b19b2345-03f7-4602-bff7-165f8567eade    117.7M    41% /boot
├─ace0-root ext4        1.0      root     6d9a1c9b-3407-4276-914d-fcca0422f9ab        3G    80% /
├─ace0-home ext4        1.0      home     8ba0252a-ba70-4f75-9fdf-a31378ea6fba     44.5G     4% /home
└─ace0-temp ext4        1.0      temp     47c054f1-66c1-4ed7-9ced-bde3dd734ccc                  
sdb                                                                                             
├─sdb1      ntfs                 Recovery A01EBA041EB9D40E                                      
├─sdb2      vfat        FAT32    EFI      1ABA-2C7F                                51.4M    46% /boot/efi
├─sdb3                                                                                          
└─sdb4      ntfs                          F21ABC211ABBE0B1                                      
sr0                                                                             

root@ace:~# gdisk /dev/sda
GPT fdisk (gdisk) version 1.0.8

Partition table scan:
  MBR: not present
  BSD: not present
  APM: not present
  GPT: not present
@GazL

Got it, I can mount the ESP before upgrade, or blacklist and use installpkg. I think I will do the later.

@Didier Spaier

That's true, and also the FAT specification was released by Microsoft to the public.

@Chuck56

Thanks so much for your detailed real world config file examples.
I would be inclined to use /etc/mkinitrd.conf but I have not yet read all about that script yet, as I should. I shall do so, but the '/usr/share/mkinitrd/mkinitrd_command_generator.sh' worked for me. Here is the output:
Code:
mkinitrd -c -k 5.15.27 -f ext4 -r /dev/ace0/root -m jbd2:mbcache:crc32c_intel:crc32c_generic:ext4 -L -u -o /boot/initrd.gz
I do really appreciate the scripts provided by the Slackware team! But also I do want to learn to edit my own mkinitrd.conf. The '/usr/share/mkinitrd/mkinitrd_command_generator.sh' says it takes into account LVM, which is nice:
Code:
root@ace:~# head -n 35 /usr/share/mkinitrd/mkinitrd_command_generator.sh
#!/bin/sh
# $Id: mkinitrd_command_generator.sh,v 1.45 2011/02/17 09:27:05 eha Exp eha $
# Copyright 2013  Patrick J. Volkerding, Sebeka, Minnesota, USA
# Copyright 2008, 2009, 2010, 2011  Eric Hameleers, Eindhoven, Netherlands
#                                   Contact: <alien@slackware.com>
# Copyright 2008, 2009  PiterPUNK, Sao Paulo, SP, Brazil
#                       Contact: <piterpunk@slackware.com>
# All rights reserved.
#
#   Permission to use, copy, modify, and distribute this software for
#   any purpose with or without fee is hereby granted, provided that
#   the above copyright notice and this permission notice appear in all
#   copies.
#
#   THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
#   WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
#   MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
#   IN NO EVENT SHALL THE AUTHORS AND COPYRIGHT HOLDERS AND THEIR
#   CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
#   SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
#   LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
#   USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
#   ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
#   OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
#   OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
#   SUCH DAMAGE.
# -----------------------------------------------------------------------------
#
# Create an initrd which fits the system.
# Take into account the use of LVM/LUKS/RAID.
# Find out about any hardware drivers the system may need in an initrd when
# booting from a generic lightweight kernel.
#
# -----------------------------------------------------------------------------
Output is the same whether or not I had the ESP mounted when running it.

Is there anything else to add to the mkintrd.conf for LVM?

Great, Chuck56 that you have it scripted! Do you run it as a cron job so you don't have to do anything at all manually?

I would say my question is "solved" but additional comments are always welcome.

Thanks again to all.

Last edited by breaker; 03-20-2022 at 01:52 PM.
 
Old 03-20-2022, 01:55 PM   #7
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado, USA
Distribution: Slackware
Posts: 930

Rep: Reputation: 479Reputation: 479Reputation: 479Reputation: 479Reputation: 479
Quote:
Originally Posted by breaker View Post
I would be inclined to use /etc/mkinitrd.conf but I have not yet read all about that script yet, as I should. I shall do so, but the '/usr/share/mkinitrd/mkinitrd_command_generator.sh' worked for me.
To create your 1st /etc/mkinitrd.conf file try:
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh -c > /etc/mkinitrd.conf
It's kinda the best of both scripts, use one to feed the other.
 
1 members found this post helpful.
Old 03-20-2022, 02:07 PM   #8
breaker
Member
 
Registered: Mar 2022
Distribution: Slackware 15.0
Posts: 87

Original Poster
Rep: Reputation: 29
Quote:
Originally Posted by Chuck56 View Post
To create your 1st /etc/mkinitrd.conf file try:
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh -c > /etc/mkinitrd.conf
It's kinda the best of both scripts, use one to feed the other.
Ah, nice one, thanks!
 
Old 06-06-2024, 10:11 PM   #9
elbci
LQ Newbie
 
Registered: May 2024
Location: in a house
Distribution: Slackware
Posts: 19
Blog Entries: 1

Rep: Reputation: 1
" Please note that this thread has not been replied to in over 6 months. Please ensure your reply is still relevant and timely. "
well... it's relevant and quite timely for me. tnx for understanding.

Now,
I do:
read mail > search web for 'Slackware how to update' > https://docs.slackware.com/slackware:slackpkg

then do from "Regular Updates" section on page above:
Code:
slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system
then do > watch a bunch of stuff happening on screen (konsole terminal) > at some point read this

"Your kernel image was updated, and lilo does not appear to be used on
your system. You may need to adjust your boot manager (like GRUB) to
boot the appropriate kernel (after generating an initrd if required).
Press the "Enter" key to continue..."


then do > PANIC! > still press enter ) > search web > change browser to the one working on LQ site > get here


Dear tolerant ppl of internet, I'm at
root@my_single_harddrive_laptop_withSlackware15stable:~#
I'm almost sure (yeah..) I use elilo. Pls, does the initrd stuff concern me? Do I dare to reboot? How do I know if generating initrd is required?

PS I am as you probably guessed a Linux guru, I can even exit Vim so... pls explain slowly )
 
Old 06-06-2024, 11:59 PM   #10
hazel
LQ Guru
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 7,702
Blog Entries: 19

Rep: Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503
Don't panic. As long as you haven't rebooted yet, you're OK.

If you're using a generic kernel in Slackware, you do need an initrd to go with it. If you use the huge kernel, you don't. You can make the initrd in /boot using the mkinitrd script and Patrick's helper script, then mount your ESP on /boot/efi and copy over both the kernel and the initrd. Finally add a new stanza to elilo.conf for the new kernel/initrd combo. Adding a stanza is safer than changing the existing one because you will still have that to fall back on if the new kernel has a problem booting.

If the new kernel boots successfully, you can delete the old kernel and initrd afterwards and comment out that stanza in elilo.conf.

Last edited by hazel; 06-07-2024 at 12:01 AM.
 
1 members found this post helpful.
Old 06-07-2024, 12:42 AM   #11
elbci
LQ Newbie
 
Registered: May 2024
Location: in a house
Distribution: Slackware
Posts: 19
Blog Entries: 1

Rep: Reputation: 1
Quote:
Originally Posted by hazel View Post
If you're using a generic kernel in Slackware, you do need an initrd to go with it. If you use the huge kernel, you don't.
I always suspected they all were just polite..
From here I get:

Code:
root@slack:~# man cat
root@slack:~# cat /var/log/messages |grep BOOT_IMAGE
Jun  2 12:29:13 slack kernel: Command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz  root=/dev/nvme0n1p3 vga=normal ro ro
Jun  2 12:29:13 slack kernel: Kernel command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz  root=/dev/nvme0n1p3 vga=normal ro ro
Jun  2 12:29:13 slack kernel: Unknown kernel command line parameters "BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz vga=normal", will be passed to user space.
Jun  4 16:13:40 slack kernel: Command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz  root=/dev/nvme0n1p3 vga=normal ro ro
Jun  4 16:13:40 slack kernel: Kernel command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz  root=/dev/nvme0n1p3 vga=normal ro ro
Jun  4 16:13:40 slack kernel: Unknown kernel command line parameters "BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz vga=normal", will be passed to user space.
Jun  4 17:46:58 slack kernel: Command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz  root=/dev/nvme0n1p3 vga=normal ro ro
Jun  4 17:46:58 slack kernel: Kernel command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz  root=/dev/nvme0n1p3 vga=normal ro ro
Jun  4 17:46:58 slack kernel: Unknown kernel command line parameters "BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz vga=normal", will be passed to user space.
Jun  4 20:53:01 slack kernel: Command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz  root=/dev/nvme0n1p3 vga=normal ro ro
Jun  4 20:53:01 slack kernel: Kernel command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz  root=/dev/nvme0n1p3 vga=normal ro ro
Jun  4 20:53:01 slack kernel: Unknown kernel command line parameters "BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz vga=normal", will be passed to user space.
Jun  6 20:00:55 slack kernel: Command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz  root=/dev/nvme0n1p3 vga=normal ro ro
Jun  6 20:00:55 slack kernel: Kernel command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz  root=/dev/nvme0n1p3 vga=normal ro ro
Jun  6 20:00:55 slack kernel: Unknown kernel command line parameters "BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz vga=normal", will be passed to user space.
root@slack:~# cat /var/log/messages |grep Command
Jun  2 12:29:13 slack kernel: Command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz  root=/dev/nvme0n1p3 vga=normal ro ro
Jun  4 16:13:40 slack kernel: Command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz  root=/dev/nvme0n1p3 vga=normal ro ro
Jun  4 17:46:58 slack kernel: Command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz  root=/dev/nvme0n1p3 vga=normal ro ro
Jun  4 20:53:01 slack kernel: Command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz  root=/dev/nvme0n1p3 vga=normal ro ro
Jun  6 20:00:55 slack kernel: Command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz  root=/dev/nvme0n1p3 vga=normal ro ro
root@slack:~# man uname
root@slack:~# uname -a 
Linux slack.locanhost 5.15.145 #1 SMP PREEMPT Sun Dec 24 00:07:06 CST 2023 x86_64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz GenuineIntel GNU/Linux
root@slack:~# cat /proc/version
Linux version 5.15.145 (root@z-mp.slackware.lan) (gcc (GCC) 11.2.0, GNU ld version 2.37-slack15) #1 SMP PREEMPT Sun Dec 24 00:07:06 CST 2023
so... be honest, is it huge?

seriously now: Thank you!

PS what's that: "root@z-mp.slackware.lan" ? (last line above - I already f*ckup my PS1 variable but that looks wierd)
 
Old 06-07-2024, 12:50 AM   #12
hazel
LQ Guru
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 7,702
Blog Entries: 19

Rep: Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503Reputation: 4503
You're looking in the wrong place. Those messages will tell you the kernel version but not how it's been configured. Look in the /boot directory: vmlinuz is a symbolic link, not an actual kernel file, but you can use the readlink command to show what it's pointing to. It will be either vmlinuz-generic-x.y.z or vmlinuz-huge.x.y.z.
 
1 members found this post helpful.
Old 06-07-2024, 01:50 AM   #13
elbci
LQ Newbie
 
Registered: May 2024
Location: in a house
Distribution: Slackware
Posts: 19
Blog Entries: 1

Rep: Reputation: 1
Quote:
Originally Posted by hazel View Post
Look in the /boot directory: vmlinuz is a symbolic link, not an actual kernel file, but you can use the readlink command to show what it's pointing to. It will be either vmlinuz-generic-x.y.z or vmlinuz-huge.x.y.z.
Hello, is this AOL customer support? I need Google Maps and I use Nokia 311...

Code:
root@slack:/boot/efi/EFI# cd Boot/
root@slack:/boot/efi/EFI/Boot# ls -a
./  ../  LenovoBT.EFI*  License.txt*  ReadMe.txt*  bootx64.efi*
root@slack:/boot/efi/EFI/Boot# vim bootx64.efi 
root@slack:/boot/efi/EFI/Boot# vim LenovoBT.EFI 
root@slack:/boot/efi/EFI/Boot# cd ..
root@slack:/boot/efi/EFI# ls -a
./  ../  Boot/  Microsoft/  Slackware/  debian/
root@slack:/boot/efi/EFI# cd Slackware/
root@slack:/boot/efi/EFI/Slackware# ls -a
./  ../  elilo.conf*  elilo.efi*  initrd.gz*  vmlinuz*
root@slack:/boot/efi/EFI/Slackware# readlink vmlinuz 
root@slack:/boot/efi/EFI/Slackware# man readlink
root@slack:/boot/efi/EFI/Slackware# man realpath 
root@slack:/boot/efi/EFI/Slackware# realpath vmlinuz 
/boot/efi/EFI/Slackware/vmlinuz
root@slack:/boot/efi# cd ..
root@slack:/boot# ls -a
./              System.map@                  config@                      efi/               grub/         inside.bmp    onlyblue.dat  tuxlogo.dat       vmlinuz-generic-5.15.160
../             System.map-generic-5.15.160  config-generic-5.15.160.x64  elilo-ia32.efi*    initrd-tree/  inside.dat    slack.bmp     vmlinuz@          vmlinuz-huge@
README.initrd@  System.map-huge-5.15.160     config-huge-5.15.160.x64     elilo-x86_64.efi*  initrd.gz     onlyblue.bmp  tuxlogo.bmp   vmlinuz-generic@  vmlinuz-huge-5.15.160
root@slack:/boot# witch damn vmlinuz is the simlink I'm suppose to read?
> ^C
root@slack:/boot#
I was convinced there will be no microsoft or debian there. There is no partition for them, or options for them on elilo start-up so I assume no stanza(entry?) on elilo(?).conf wherever it may hide from me.

Regardless, Little Red Hood is lost now...
 
Old 06-07-2024, 03:01 AM   #14
BrunoLafleur
Member
 
Registered: Apr 2020
Location: France
Distribution: Slackware
Posts: 428

Rep: Reputation: 388Reputation: 388Reputation: 388Reputation: 388
> cd /boot
> ls -l

And you should see the real name for vmlinuz
 
1 members found this post helpful.
Old 06-07-2024, 03:08 AM   #15
ctrlaltca
Member
 
Registered: May 2019
Location: Italy
Distribution: Slackware
Posts: 338

Rep: Reputation: 394Reputation: 394Reputation: 394Reputation: 394
Quote:
Jun 4 20:53:01 slack kernel: Command line: BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz root=/dev/nvme0n1p3 vga=normal ro ro
Seems like you're booting using EFI, and the kernel is at \EFI\Slackware\vmlinuz
The efi partition is mounted at /boot/efi, so that translates to the full path /boot/efi/EFI/Slackware/vmlinuz
Inside that partition you also have an initrd:
Quote:
root@slack:/boot/efi/EFI/Slackware# ls -a
./ ../ elilo.conf* elilo.efi* initrd.gz* vmlinuz*
So what you need to do is:
Code:
# generate a new initrd for the new kernel version
geninitrd
# copy the new kernel into the EFI partition:
cp /boot/vmlinuz /boot/efi/EFI/Slackware/vmlinuz
# copy the new initrd into the EFI partition:
cp /boot/initrd.gz /boot/efi/EFI/Slackware/initrd.gz
I'd also give a look at the contents of /boot/efi/EFI/Slackware/elilo.conf to ensure it's actually pointing to the correct vmlinuz / initrd.gz.
There are still two things to figure out: if you were using the generic or the huge kernel before, and if you were actually using the initrd or it was sitting there unused.

Forget about the symlink, that's only used for legacy booting (not EFI).

Last edited by ctrlaltca; 06-07-2024 at 03:12 AM.
 
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
I stopped a slackpkg upgrade-all in midstream and now I cannot slackpkg upgrade-all jkh2cpu Slackware 5 02-13-2022 03:05 AM
Weird slackpkg upgrade message during a slackpkg upgrade-all process. frtorres Slackware 8 02-13-2021 11:36 AM
SARPI on Pi3 - Ran slackpkg update & slackpkg upgrade-all and now won't boot, can't find init petejc Slackware - ARM 11 03-25-2020 04:30 AM
[SOLVED] Slackpkg upgrade-all returns 'no packages to upgrade' after slackpkg-update has downloaded files san2ban Slackware 8 11-01-2019 05:44 AM

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

All times are GMT -5. The time now is 05:51 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