Few kernel questions on current with initrd
by Eeel from LinuxQuestions.org on (#566TR)
To update my kernel actually i do
Code:slackpkg update
slackpkg upgrade-allmy mkinitrd.conf:
Code:SOURCE_TREE="/boot/initrd-tree"
OUTPUT_IMAGE="/boot/initrd.gz"
KERNEL_VERSION="$(uname -r)"
KEYMAP="fr"
MODULE_LIST="ext4"
ROOTDEV="/dev/md0"
ROOTFS="ext4"
RAID="1"to update my initrd i do
Code:mkinitrd -F -c -k 5.4.53 -m ext4
liloCode:# LILO configuration file
raid-extra-boot = mbr-only
append="root=/dev/md0 vt.default_utf8=0"
boot = /dev/md3
# This option loads the kernel and initrd much faster:
compact
# Boot BMP Image.
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255
# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
timeout = 120
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# Linux bootable partition config begins
image = /boot/vmlinuz # (linked to huge kernel)
initrd = /boot/initrd.gz
root = /dev/md0
label = Linux
read-only
# Linux bootable partition config endsAt the boot time i get thoses error messages:
Code:insmod /lib/modules/5.4.53/kernel/fs/mbcache.ko
mbcache: exports duplicate symbol __mb_cache_entry_free (owned by kernel)
modprobe: ERROR: could not insert 'mbcache' : Exec format errorSame error for jbd2 and ext4
I'm almost shure that thoses messages doesn't exist after a fresh current install.
questions:
1- what does it mean? search for LQ doesn't really help me here.
2- Is there something in above command that are not adapted to my setup ?
3- I can't find error messages in any log once computer is booted, it seems to be initrd messages ? and seems not to be logged in /var/log/files because they happen before kernel boot ? Are they logged somewhere ?
4- I read in LQ a message from Alienbob saying i can do a SHIFT+PAGE UP at boot time, it works but message keep scrolling whithout being able to stop it, i probably miss something here, any idea ?
I actually use the Huge kernel, i understand how to use the mkinitrd_command_generator.sh to generate a suitable list of module to create an initrd for my setup and change apropriate line in lilo.conf to boot the generic kernel.
5- The only advantage i can read in documentation (in my setup) is to boot quicker, computer is always on so it's not usefull in my case, is there any other advantages to use the generic kernel ?
I have created a /boot partition, i do this since many years following advice from readme raid install, this partition is 100Mo...seems a bit small for current my partition is 76% full.
6- Can i removepkg generic-kernel package or huge-kernel package if i don't use it ? i can easily say yes on this one.
7- Can i delete the initrd-tree/ folder once my initrd.gz is created and lilo updated to save some space ?
that's a lot of questions :)


Code:slackpkg update
slackpkg upgrade-allmy mkinitrd.conf:
Code:SOURCE_TREE="/boot/initrd-tree"
OUTPUT_IMAGE="/boot/initrd.gz"
KERNEL_VERSION="$(uname -r)"
KEYMAP="fr"
MODULE_LIST="ext4"
ROOTDEV="/dev/md0"
ROOTFS="ext4"
RAID="1"to update my initrd i do
Code:mkinitrd -F -c -k 5.4.53 -m ext4
liloCode:# LILO configuration file
raid-extra-boot = mbr-only
append="root=/dev/md0 vt.default_utf8=0"
boot = /dev/md3
# This option loads the kernel and initrd much faster:
compact
# Boot BMP Image.
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255
# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
timeout = 120
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# Linux bootable partition config begins
image = /boot/vmlinuz # (linked to huge kernel)
initrd = /boot/initrd.gz
root = /dev/md0
label = Linux
read-only
# Linux bootable partition config endsAt the boot time i get thoses error messages:
Code:insmod /lib/modules/5.4.53/kernel/fs/mbcache.ko
mbcache: exports duplicate symbol __mb_cache_entry_free (owned by kernel)
modprobe: ERROR: could not insert 'mbcache' : Exec format errorSame error for jbd2 and ext4
I'm almost shure that thoses messages doesn't exist after a fresh current install.
questions:
1- what does it mean? search for LQ doesn't really help me here.
2- Is there something in above command that are not adapted to my setup ?
3- I can't find error messages in any log once computer is booted, it seems to be initrd messages ? and seems not to be logged in /var/log/files because they happen before kernel boot ? Are they logged somewhere ?
4- I read in LQ a message from Alienbob saying i can do a SHIFT+PAGE UP at boot time, it works but message keep scrolling whithout being able to stop it, i probably miss something here, any idea ?
I actually use the Huge kernel, i understand how to use the mkinitrd_command_generator.sh to generate a suitable list of module to create an initrd for my setup and change apropriate line in lilo.conf to boot the generic kernel.
5- The only advantage i can read in documentation (in my setup) is to boot quicker, computer is always on so it's not usefull in my case, is there any other advantages to use the generic kernel ?
I have created a /boot partition, i do this since many years following advice from readme raid install, this partition is 100Mo...seems a bit small for current my partition is 76% full.
6- Can i removepkg generic-kernel package or huge-kernel package if i don't use it ? i can easily say yes on this one.
7- Can i delete the initrd-tree/ folder once my initrd.gz is created and lilo updated to save some space ?
that's a lot of questions :)