LinuxQuestions.org - Install precompiled kernel

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Install precompiled kernel (https://www.linuxquestions.org/questions/slackware-14/install-precompiled-kernel-265556/)

Install precompiled kernel

Hello,

I have a Slackware 10 installation with the default 2.4.26 bare.i kernel. I would like to add also the 2.4.27 kernel. I downloaded the files

System.map.gz
bzImage
config

from ftp://ftp.slackware.com/pub/slackwar...rnels/bare.i/, but have no real idea how to install them. I want to add the new kernel to lilo so that I can choose between "Slack-2.4.26" and "Slack-2.4.27" and not to upgrade the existing one. It would be great if the new one was the default choice.

This is my lilo.conf:

Code:

# LILO configuration file

# generated by 'liloconfig'

#

# Start LILO global section

boot="/dev/hda"

message = /boot/boot_message.txt

prompt

timeout="100"

# Override dangerous defaults that rewrite the partition table:

change-rules

  reset

# VESA framebuffer console @ 1024x768x256

vga="773"

# Normal VGA console

# vga = normal

# VESA framebuffer console @ 1024x768x64k

# vga=791

# VESA framebuffer console @ 1024x768x32k

# vga=790

# VESA framebuffer console @ 1024x768x256

# vga=773

# VESA framebuffer console @ 800x600x64k

# vga=788

# VESA framebuffer console @ 800x600x32k

# vga=787

# VESA framebuffer console @ 800x600x256

# vga=771

# VESA framebuffer console @ 640x480x64k

# vga=785

# VESA framebuffer console @ 640x480x32k

# vga=784

# VESA framebuffer console @ 640x480x256

# vga=769

# End LILO global section

# Linux bootable partition config begins



image="/boot/vmlinuz"

        root="/dev/hda3"

        label="Slack-2.4.26"

  read-only

# Linux bootable partition config ends

This is my /boot folder:

Code:

lars@desktop:~$ ll /boot

total 3150

lrwxrwxrwx  1 root root      37 Jul 31 15:32 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd

lrwxrwxrwx  1 root root      21 Jul 31 15:32 System.map -> System.map-ide-2.4.26

-rw-r--r--  1 root root  620999 Jun 15 02:29 System.map-ide-2.4.26

-rw-r--r--  1 root root    512 Jul 31 15:50 boot.0300

-rw-r--r--  1 root root    168 Jul 31 15:50 boot_message.txt

lrwxrwxrwx  1 root root      17 Jul 31 15:32 config -> config-ide-2.4.26

-rw-r--r--  1 root root  41017 Jun 15 02:29 config-ide-2.4.26

-rw-r--r--  1 root root    5032 May 21  2004 diag1.img

drwx------  2 root root  12288 Jul 31 14:54 lost+found/

-rw-------  1 root root  27648 Dec 12 03:14 map

-r--------  1 root root 1248111 Jul 31 15:44 vmlinuz

-rw-r--r--  1 root root 1248111 Jun 15 02:29 vmlinuz-ide-2.4.26

I searched for a while, but couldn't find a step-by-step guide of how to install the additional kernel without replacing the existing one. I don't want to do some try and error with that thing. It would be great if you could help me.

Thanks a lot :)

Copy bzImage to /boot/bzImage-2.4.27

Edit /etc/lilo.conf -- add:

image=/boot/bzImage-2.4.27
root="/dev/hda3"
label="Slack-2.4.27"
read-only

Run lilo

reboot and enjoy ;)

Wow, I thought that it must be easy, but didn't know that it is that easy. Thank you very much :) .

not a problem. Enjoy ;)

I can't boot the kernel due to missing dependencies:

Code:

modprobe: Can't open dependencies file /lib/modules/2.4.27/modules.dep (No such file or directory)

In /lib/modules is only 1 the folder 2.4.26. Output of /lib/modules/2.4.26 is:

Code:

lars@desktop:~$ ll /lib/modules/2.4.26/

total 532

lrwxrwxrwx  1 root root    21 Jul 31 15:32 build -> /usr/src/linux-2.4.26/

drwxr-xr-x  9 root root  4096 Jun 14 01:39 kernel/

-rw-r--r--  1 root root 140553 Jul 31 18:03 modules.dep

-rw-r--r--  1 root root  60663 Jul 31 18:03 modules.generic_string

-rw-r--r--  1 root root    443 Jul 31 18:03 modules.ieee1394map

-rw-r--r--  1 root root  21941 Jul 31 18:03 modules.isapnpmap

-rw-r--r--  1 root root    29 Jul 31 18:03 modules.parportmap

-rw-r--r--  1 root root  88495 Jul 31 18:03 modules.pcimap

-rw-r--r--  1 root root    24 Jul 31 18:03 modules.pnpbiosmap

-rw-r--r--  1 root root 185369 Jul 31 18:03 modules.usbmap

drwxr-xr-x  2 root root  4096 Jul 31 15:32 pcmcia/

Is it safe to just copy the 2.4.26 to 2.4.27 via

cp -R /lib/modules/2.4.26 /lib/modules/2.4.27

or is there anything else I have to do?

I would try that first. There can't be that much difference between them.

Unfortunately that doesn't work. I get a lot of kernel mismatches and can't boot with the kernel. Do you have any ideas what else I could try?

I know that there is a 2.6.x kernel in slackware-current.
AFAIK -- this is kernel should work -- I normally compile my own kernels

i've got this package installed for the 2.4.26

kernel-modules-2.4.26-i486-3

you should look for : kernel-modules-2.4.27-i486-?.tgz at the Slackware-site ( ? =version )
and install that one.

egag

Thanks, I also have the

kernel-modules-2.4.26-i486-3

installed. Is found the

kernel-modules-2.4.27-i486-1.tgz

on the Slackware site. Is it safe to install them without breaking the modules of my existing, running, 2.4.26 kernel? At least I always need one kernel that works =).

I would imagine that this would be safe.

if you look in "/lib/modules ", there is a dir. 2.4.26 and 2.4.27 (you copied that if i understand ok ? )
if so, just delete the 2.4.27 dir,
then use " #installpkg kernel-modules-2.4.27-i486-1.tgz " to install them.

that should work.....

egag

Ok, I will give that a try when the download of the modules is done. Sounds logical. Just wanted to be sure.

So, I installed the kernel modules and get no errors when booting with the new kernel. The problem now is, that it doesn't start X. It ends saying:

Code:

Starting X11 Session manager...

Here is some output of /var/log/syslog

Code:

Dec 12 19:17:24 desktop kdm: :0[1630]: IO Error in XOpenDisplay

Dec 12 19:17:24 desktop kdm[1626]: Display :0 cannot be opened

Dec 12 19:17:24 desktop kdm[1626]: Unable to fire up local display :0; disabling.

Any ideas?

You'll have to look at your xorg log. It's possible that the 2.4.27 kernel is loading modules differently. It could be a number of things, but when I compiled 2.6.9, I ran into a couple issues that prevented X from loading successfully. If I remember right, some of the usb settings were screwy and X couldn't find the mouse. And there were some problems with video. What output do you get from:

Code:

grep -e "(EE)" -e "(WW)" /var/log/Xorg.0.log

Edit:
LOL...you must have been editing that post as I was writing this one.
The kdm errors are likely due to problems with the X setup itself, rather than with kdm. The info in Xorg.0.log should point you in the right direction.