| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 23 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:56:00 |
| Calls: | 583 |
| Files: | 1,139 |
| D/L today: |
179 files (27,921K bytes) |
| Messages: | 111,802 |
http://www.slackware.com/changelog/stable.php?cpu=x86_64 |Be sure to
upgrade your initrd after upgrading the kernel packages.
Is it enough to run
sudo geninitrd
or do I need to run additional stuff?
I am using GRUB2, so I had to run
sudo grub-mkconfig -o /boot/grub/grub.cfg
anyway.
Is it planned to automate that like the call of update-grub in current
after a kernel update?
On Wed, 16 Jul 2025 20:03:29 +0200, Marco Moock wrote:
http://www.slackware.com/changelog/stable.php?cpu=x86_64 |Be sure to upgrade your initrd after upgrading the kernel packages.
Is it enough to run
sudo geninitrd
or do I need to run additional stuff?
As allways, it depends upon your configuration how much you need to
do and what to do at a kernel update. I have choosen to make things
easy by using a huge kernel without any initrd in Slackware 15.0,
however I still need to update lilo or extlinux which are my
bootloaders of choice.
I am using GRUB2, so I had to run
sudo grub-mkconfig -o /boot/grub/grub.cfg
anyway.
Is it planned to automate that like the call of update-grub in
current after a kernel update?
I'm not running current, but in the Slackware forum at
linuxquestions.org I have seen some suggestions about calling a
script to update the booatloader from the kernel package. I can't say
for sure however, if any such suggestion has been implemented yet.
How can I find out which kernel image (not only version) in the running system?
uname doesn't show if I use the huge kernel
On Thu, 17 Jul 2025 12:23:13 +0200, Marco Moock wrote:
How can I find out which kernel image (not only version) in the running
system?
uname doesn't show if I use the huge kernel
Somehow you have configured your bootloader to load a kernel, or maybe
even to select between different kernels. I am not familiar with grub,
but my guess is that some configuration file points to a vmlinuz-huge-*
or vmlinuz-generic-*
If you are unable to find how you configured your boot loader there is
still a trick to check:
cat /proc/config.gz | gzip -d - | grep EXT4_FS
if CONFIG_EXT4_FS=y you have a huge kernel on Slackware 15.0, with a
generic kernel it is instead "m".
Marco Moock wrote to alt.os.linux.slackware <=-
From Newsgroup: alt.os.linux.slackware
On 17.07.2025 16:24 Uhr Henrik Carlqvist wrote:
if CONFIG_EXT4_FS=y you have a huge kernel on Slackware 15.0, with a
generic kernel it is instead "m".
Is y, so I booted huge. Do I need initrd at all?
What happens if I let it generate it?
To: Marco Moock -=> Marco Moock wrote to alt.os.linux.slackware <=-
From Newsgroup: alt.os.linux.slackware
On 17.07.2025 16:24 Uhr Henrik Carlqvist wrote:
if CONFIG_EXT4_FS=y you have a huge kernel on Slackware 15.0, with a generic kernel it is instead "m".
Is y, so I booted huge. Do I need initrd at all?
No, you do not.
What happens if I let it generate it?
Not sure, but I wouldn't do it.
On Thu, 17 Jul 2025 20:55:11 -0500, Gamgee wrote:
To: Marco Moock -=> Marco Moock wrote to alt.os.linux.slackware <=-it shouldnt do anything, unless you add the initrd= /boot/initrd.gz to
From Newsgroup: alt.os.linux.slackware
On 17.07.2025 16:24 Uhr Henrik Carlqvist wrote:
if CONFIG_EXT4_FS=y you have a huge kernel on Slackware 15.0, with a
generic kernel it is instead "m".
Is y, so I booted huge. Do I need initrd at all?
No, you do not.
What happens if I let it generate it?
Not sure, but I wouldn't do it.
your image in lilo.conf... cant comment on grub.
On Fri, 18 Jul 2025 16:59:50 +1000, noel wrote:
On Thu, 17 Jul 2025 20:55:11 -0500, Gamgee wrote:
To: Marco Moock -=> Marco Moock wrote to alt.os.linux.slackware <=-MM> From >>> Newsgroup: alt.os.linux.slackwareit shouldnt do anything, unless you add the initrd= /boot/initrd.gz to
On 17.07.2025 16:24 Uhr Henrik Carlqvist wrote:
if CONFIG_EXT4_FS=y you have a huge kernel on Slackware 15.0, with a
generic kernel it is instead "m".
Is y, so I booted huge. Do I need initrd at all?
No, you do not.
What happens if I let it generate it?
Not sure, but I wouldn't do it.
your image in lilo.conf... cant comment on grub.
looks like I was right, we still have the initial default initrd image
from when we installed this particular machine in 15.0 and it is not nor
has ever been used, always use huge kernels. we use to strip em down in a custom, but found it makes no difference to performance for past 15
years so dont bother anymore and use default huge, which I think is just
the default kernel-generic in -current now
lrwxrwxrwx 1 root root 38 Jan 27 2022 README.initrd -> /usr/doc/ mkinitrd-1.4.11/README.initrd--- Synchronet 3.21a-Linux NewsLink 1.2
lrwxrwxrwx 1 root root 24 Jul 16 16:27 System.map -> System.map- huge-5.15.188
-rw-r--r-- 1 root root 6940344 Jul 15 08:12 System.map-huge-5.15.188 -rw-r--r-- 1 root root 148480 Jul 15 04:18 amd-ucode.img
-rw-r--r-- 1 root root 512 Nov 21 2020 boot.0800
-rw-r--r-- 1 root root 167 Nov 21 2020 boot_message.txt
lrwxrwxrwx 1 root root 24 Jul 16 16:27 config -> config- huge-5.15.188.x64
-rw-r--r-- 1 root root 239739 Jul 15 07:54 config-huge-5.15.188.x64 -rwxr-xr-x 1 root root 216219 Jun 13 2018 elilo-ia32.efi*
-rwxr-xr-x 1 root root 238531 Jun 13 2018 elilo-x86_64.efi*
*drwxr-xr-x 14 root root 4096 Nov 21 2020 initrd-tree/ <----------> -rw-r--r-- 1 root root 8323602 Nov 21 2020 initrd.gz <----------*> -rw-r--r-- 1 root root 22578 Feb 13 2021 inside.bmp
-rw-r--r-- 1 root root 432 Feb 13 2021 inside.dat
-rw------- 1 root root 32768 Jul 16 16:44 map
-rw-r--r-- 1 root root 6878 Feb 13 2021 onlyblue.bmp
-rw-r--r-- 1 root root 424 Feb 13 2021 onlyblue.dat
-rw-r--r-- 1 root root 15634 Mar 27 2011 slack.bmp
-rw-r--r-- 1 root root 33192 Feb 13 2021 tuxlogo.bmp
-rw-r--r-- 1 root root 423 Feb 13 2021 tuxlogo.dat
lrwxrwxrwx 1 root root 21 Jul 16 16:27 vmlinuz -> vmlinuz- huge-5.15.188
lrwxrwxrwx 1 root root 21 Jul 16 16:27 vmlinuz-huge -> vmlinuz- huge-5.15.188
-rw-r--r-- 1 root root 11685312 Jul 15 08:12 vmlinuz-huge-5.15.188