I tried to update the kernel 5.15.145 (generic) to kernel 5.15.152 by
following the instructions here

https://blog.paranoidpenguin.net/201...ackware-linux/

and needless to say, I really screwed it up somehow.

Right now I am trying to get back to the Kernel 5.15.145 but I am getting the following when the system tries to boot up:
------------------------------------------------
[ 3.565166] rodata_test: all test were successful
[ 3.565611] Run /init as init process
[ 3.578258] udevd[306]: starting eudev-3.2.12
/boot/initrd.gz: Loading kernel modules from initrd image:
insmod /lib/modules/5.15.145/kernel/fs/jdb2/jdb2.ko
[ 3.608569] jdb2: exports duplicate symbol jdb2__journal_restart (owned by kernel)
modprobe: ERROR: could not insert 'jdb2': Exec format error
insmod /lib/modules/5.15.145/kernel/fs/mbcache.ko
[ 3.658244] mbcache: exports duplicate symbol __mb_cache_entry_free (owned by kernel)
modprobe: ERROR: could not insert 'mbcache': Exec format error
insmod /lib/modules/5.15.145/fs/jdb2/jdb2.ko
[ 3.694984] jdb2: exports duplicate symbol jdb2__journal_restart (owned by kernel)
modprobe: ERROR: could not insert 'ext4': Exec format error
mount: mounting overlay on /mnt failed: No such device
ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead.
You can try to fix it. Type 'exit' when things are done.

/bin/sh: can't access tty: job control turned off
/#
----------------------------------------------------------
I am not sure where to go with this as of now.

I have removed all the references to the kernel "vanilla-5.15.152" in
the /boot and the EFI System:
I have the following on this system
/dev/nvme0n1p1 EFI system (VFAT)
/dev/nvme0n1p2 / (Ext 4)
/dev/nvme0n1p2 Swap

I changed elilo.conf under /boot/efi/EFI/Slackware to now go to
"image=vmlinuz-huge-5.15.145"

This is also the same in the EFI System (VFAT) drive.

I was going to go with huge-5.15.145 as I understand it, I would not need
to run the "mkinitrd" with the huge kernel.

Any and all advise appreciated to help me recover my 5.15.145 system.

Yeah, your boot loader still references incompatible initrd generated for 5.15.145 (generic), while huge variant doesn't need an initrd.

Well, I used my slackware64_15.0 DVD and reloaded various series and I can at least boot back up now,
however it is using the 5.15.19 kernel.

Just need to figure out how to get it to use the huge-5.15.145 kernel without the "mkinitrd".

and also for some reason it will not show or connect with my wifi router, even after running
the "rc.inet1 wlan0 start" so need to find that problem.

It is getting better.

Edit your /etc/slackpkg/mirrors file and make user you have only one mirror selected for 15.0. You can then run the standard slackpkg update, slackpkg install-new, and slackpkg upgrade-all. In the list ( it should be short depending what you had installed before ) you should see the individual kernel packages listed for 145, since that is what is the newest kernel Pat has rteleased for 15.0. Let the upgrade run.

Depending if this a legacy BIOS, Or UEFI system, you will need to update the boot loader before you reboot. I always make an initrd.gz file at this point. You do not have too, as long as you have set up the boot loader to load the huge kernel.

To make an initrd, I always use the mkinitrd script. You can find it at /usr/share/mkinitrd/mkinitrd.sh. Add the -k option for 5.15.145. The command will look like "/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 5.15.145" without quotes. It outputs a line of code. Copy and paste that at the command line, press enter, and the initrd file is created.

Get that far, try your wi-fi connection. If you need more help, post back how far you have got.

Well, I just loaded the Slackware65 15.0 DVD for the second time and my network problems seems to have now
gone away.

I did try upgrading the kernel to the "huge-5.15.145" but again when I reboot it crashes as in the 1st listing above.

I do not know what is going on as I had the "generic-5.15.145" running prior to this.

Right now I am on 5.15.19 from the DVD and it is working fine, but I would like to get the 5.15.145 series back up
and running.

question - modify the file /boot/efi/EFI/Slackware/elilo.conf should I add "image=vmlinuz-huge-5.15.145" and also
to the file v-fat drive under /EFI/Slackware?

When I modify both of those for the "huge-5.15.145" kernel, do I need to run "mkinitrd -c -k 5.15.145 -m ext4" or not?

when I get all of the above done, I then run "eliloconfig" - so does any of this really change just to use the "huge-5.15.145" kernel??

Thanks

WIth elilo, you need to move the kernels and your new initrd.gz to /boot/efi/EFI/Slackware and modify elilo.conf to match the kernel(s) you may wish to boot.

I will list what mine looks like. First the list of files.

Note, I have set up menues so I can select either kernel. You do not need to do that. You need elilo.conf, elilo.efi,
the initrd file, and at least 1 kernel.

My elilo.conf file.

You can use the simple chooser. The key parts are:

for the generic kernel and

for the huge kernel. FYI, the append= line allows you to pass parameters to the kernel. Try without using an append line. Also, I change the name of an initrd.gz file so I can tell what kernel it is for. That is not necessary, it just helps me know what initrd file belongs to what kernel.

Hope this helps.

Thank you Cliff, that really helps.

Right now I have the kernel 5.15.19 but everything else is up to date on 15.0

Tomorrow I will try and the slackpkg upgrade for the Kernels.

If that goes well, then I will mark this solved.

Thanks again

Chuck

Happy to help.