[SOLVED] Switching to generic-kernel with initrd.gz

Hasek39 · 08-06-2015, 06:54 AM

I'm using Slackware 14.1 with the 3.10.17 kernel and had a question how to proof that system uses generic-kernel for booting. After I had created an initrd.gz with /usr/share/mkinitrd/mkinitrd_command_generator.sh command and add line initrd = /boot/initrd.gz to /etc/lilo.conf is it necessary to substitute image = /boot/vmlinuz line with image = /boot/vmlinuz-generic-3.10.17? Or should I leave image = /boot/vmlinuz untouched?

bassmadrigal · 08-06-2015, 07:00 AM

You need to have your lilo.conf entry point to the correct kernel. /boot/vmlinuz is just a symlink, so you can either change the symlink to point it to the generic kernel or you can change the image line in lilo.conf to point to the actual kernel instead of vmlinuz. Don't forget to run lilo afterwards.

I'd keep an entry in there for the huge kernel until you know you have it working properly.

kikinovak · 08-06-2015, 07:12 AM

It's generally a good idea to replace the /boot/vmlinuz symlink in /etc/lilo.conf by the "real thing", e. g. /boot/vmlinuz-huge-3.10.17, /boot/vmlinuz-smp-3.10.17-smp, /boot/vmlinuz-generic-3.10.17, etc.

Here's a little HOWTO based on Slackware 14.0:

http://www.microlinux.fr/microlinux/...rnel-HOWTO.txt

Cheers,

Niki

allend · 08-06-2015, 07:13 AM

Our BDFL is now distributing generic kernel packages that, when installed, create a symlink in /boot so that /boot/vmlinuz points to the generic kernel.
If you use slackpkg to perform upgrades, and have the huge kernel packages blacklisted, then you can safely use the /boot/vmlinuz entry in lilo.conf
Warning! - You need to create a new initrd and rerun lilo after a kernel upgrade if you do this.
http://www.linuxquestions.org/questi...0/#post5327847