Quote:
Originally Posted by glorsplitz
out of curiosity, you had a phantom/ghost kernel in your lilo.conf, as "slackpkg search kernel" did not show anything 4.14.67
which kernel is attached to /boot/vmlinuz as this is a link?
|
My /boot directory is now:
Code:
lrwxrwxrwx 1 root root 21 2024-01-20 21:06 vmlinuz -> vmlinuz-huge-5.15.145
lrwxrwxrwx 1 root root 24 2024-01-20 21:06 vmlinuz-generic -> vmlinuz-generic-5.15.145
-rw-r--r-- 1 root root 7812416 2023-12-24 01:38 vmlinuz-generic-5.15.145
lrwxrwxrwx 1 root root 21 2024-01-20 21:06 vmlinuz-huge -> vmlinuz-huge-5.15.145
-rw-r--r-- 1 root root 8671136 2018-09-03 03:09 vmlinuz-huge-4.14.67
-rw-r--r-- 1 root root 11622048 2023-12-24 01:35 vmlinuz-huge-5.15.145
I hadn't deleted vmlinuz-huge-4.14.67, but I think I'm going to right now! And my lilo.conf is:
Code:
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/md1
label = Linux
append="rcu_nocbs=0-11"
read-only
# Linux bootable partition config ends
Quote:
you have no fallback?
I boot generic kernel and huge as fallback
|
I guess not. I don't really know what that means! Do you mean more than one "image" configured in the "# Linux bootable partition config" section, selectable from the boot menu? I've done such boot menu things to boot either Windows or Linux, but in this case having a boot option menu is not useful since this is an unattended remote file server ... if that's the idea you mean.
