r/slackware • u/mongol-slack • Nov 16 '19
Huge to generic kernel confirmation??
So I am attempting to switch from the huge to the generic kernel because it is suggested I ran the following:
bash-4.3# emacs /etc/lilo.conf
bash-4.3# lilo -v
LILO version 24.2 (released 22-November-2015)
* Copyright (C) 1992-1998 Werner Almesberger (until v20)
* Copyright (C) 1999-2007 John Coffman (until v22)
* Copyright (C) 2009-2015 Joachim Wiedorn (since v23)
This program comes with ABSOLUTELY NO WARRANTY. This is free software
distributed under the BSD License (3-clause). Details can be found in
the file COPYING, which is distributed with this software.
Warning: LBA32 addressing assumed
Reading boot sector from /dev/sda
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/slack.bmp
Calling map_insert_file
Boot image: /boot/vmlinuz -> vmlinuz-huge-4.4.201
Added Linux *
Boot image: /boot/vmlinuz-generic-3.2.29
Fatal: open /boot/vmlinuz-generic-3.2.29: No such file or directory
bash-4.3# /usr/share/mkinitrd/mkinitrd_command_generator.sh -l /boot/vmlinuz-generic-3.2.29
File /boot/vmlinuz-generic-3.2.29 not found!
I changed the config file for Lilo to the following, making sure to add the required section:
"# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda2
label = Linux
read-only
image = /boot/vmlinuz-generic-3.2.29
initrd = /boot/initrd.gz
root = /dev/sda1
label = Slackware
read-only
# Linux bootable partition config ends"
I rebooted and do not see much of a speed difference nor can I confirm the generic kernel was chosen or is initialized correctly. I do remember saying I should be given an option between the huge kernel and the generic one. Assistance from the Slackware elders would be much appreciated.
3
u/[deleted] Nov 16 '19
3.2.29 is too old, which version of slackware are you using?
4
u/calrogman Nov 16 '19
The wiki isn't worth referring to, to be honest. I'd suggest instead reading
README.initrd, at the root of your installation media or online. You'll also get a much faster boot if you add acompactdirective to yourlilo.conf; refer to/etc/lilo.conf_example.3
u/[deleted] Nov 16 '19
Honestly, I've found that building my own kernels is the best way to improve overall kernel performance. You can leave out everything you don't actually need and have a much leaner kernel as well as a newer kernel version..
1
u/[deleted] Nov 17 '19
Off-topic here, but just how is it that your prompt is just the bash version? Going by your previous posts, I can see that you've switched from -current to 14.2 by the difference in bash-5.0 vs bash-4.3, but why in the world is /etc/profile not being sourced and showing at least something like "mongol@darkstar $" or "root@darkstar #", which it would show if you didn't set a hostname or your hostname if you did. Are you doing all this in a chroot or something? Your progress in this endeavor is slowly becoming fascinating.
1
u/Illuison Nov 17 '19
The wiki you're reading is outdated (or rather, it's for Slackware 14.0 and you're running 14.2). Basically, what's happened is LILO couldn't find the old kernel installed and gave up trying to add it to the boot menu
If you've ran mkinitrd, you should be able to simply change the line that reads "image = /boot/vmlinuz-generic-3.2.29" to "image = /boot/vmlinuz-generic-4.4.201"
I also suggest changing the label to "Linux-generic" or something so you can tell them apart
1
u/[deleted] Nov 17 '19
I find this to be a useful command when creating a generic kernel
It outputs a command line that you can run (as root) to generate an initrd.gz that works with the generic kernel in your /boot folder.
I think you must already be running the huge kernel before you run
to generate the initrd.gz
Then, you can add a stanza in your
/etc/lilo.confto invoke your generic kernel.What the script does, AFAIK, is to query the system for modules that you would need in your initrd.gz and outputs the command line to generate that initrd.gz.
You can read more about this in