Hello!
I installed 15 in EFI mode and ran slackpkg upgrade-all, which removed
the old kernel.
I ran eliloconfig, LILO works, the kernel 5.15.209 loads, but says no
kernel modules found.
mount failes with no such device, the device is there, but I cannot
mount it manually. lsmod shows nothing.
Is maybe the part for ext4 missing?
How can I fix this?
Did you remember to recreate the initrd if you are booting a kernel
that uses an initrd (lack of modules implies you are using a kernel
that needs the correct initrd).
Am 04.07.26 um 21:12 schrieb Rich:
Did you remember to recreate the initrd if you are booting a kernel
that uses an initrd (lack of modules implies you are using a kernel
that needs the correct initrd).
No, I didn't. I had a BIOS machine (dunno if that used the huge kernel)
that didn't need that.
How can I do that now?
Boot the install image, switch to the virtual console and chroot into
the installed OS?
Also, after rebuilding the initrd you'll need to rerun the lilo update
to make sure the boot code knows where to find the newly created
initrd.
This is also a good reason why, instead of replacing the existing
bootable kernel, the upgrade process should add a second (or third,
etc.) along side and an additional boot line in elilo. Then if the new kernel fails, you can always reboot into the old, working one.
Am 04.07.26 um 22:54 schrieb Rich:
Also, after rebuilding the initrd you'll need to rerun the lilo update
to make sure the boot code knows where to find the newly created
initrd.
Thanks, that worked.
Does that need to run every time I update a kernel?
How did that work on another BIOS machine?
I did not generate initrd manually and it worked. Was that maybe the
huge kernel?
I've the huge kernel and the generic kernel installed.
elilo seems to have booted the generic kernel in the first attempt.
The elilo config now lists vmlinuz, which is a link to the huge kernel
in /boot.
In /boot/efi/EFI/Slackware there is vmlinuz file (not a link).
How can I find out which kernel I really booted?
This is also a good reason why, instead of replacing the existing
bootable kernel, the upgrade process should add a second (or third,
etc.) along side and an additional boot line in elilo. Then if the new
kernel fails, you can always reboot into the old, working one.
Why isn't that triggered when installing the kernel modules package?
How can I find out which kernel I really booted?cat /proc/cmdline
"Working" and "Last Known Good" are always a smart and safeThis is also a good reason why, instead of replacing the existing
bootable kernel, the upgrade process should add a second (or third,
etc.) along side and an additional boot line in elilo. Then if the new
kernel fails, you can always reboot into the old, working one.
Why isn't that triggered when installing the kernel modules package?There may have been a discussion about this on LQ wrt to Current but I
cat /proc/cmdline
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:25:36 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,563 |