My 2.4.31 kernel doesn't load after installing kernel 2.6.13. I have them
both configured in lilo. But no matter wich one I choose 2.6.13 takes over.
This isn't my first time installing and configuring a kernel from source.

:iferences::
What I had before:
-Slack 10.1
-Booting kernels; 2.4.29 and 2.6.11
-ex3 fs
-everything installed on hda2 with hda1 as swap
-kernel 2.6.11 was installed and configured as per:
----/usr/src/linux-2.6.11/README

What I have now
-Slack 10.2
-Booting kernels; 2.4.31 and 2.6.13
-reiserfs
-everyting in hda3 with hda2 as swap
----/home in a new partition and
----/home/west/seagate is a patition on hdb

Here is my lilo.conf:

# LILO configuration file
boot = /dev/hda
#compact # faster, but won't work on all systems.
prompt
timeout = 300
# VESA framebuffer console @ 1024x768x256
vga = 773
# End LILO global section
# Linux bootable partition config begins
image = /boot/bzImage
root = /dev/hda3
label = Linux-2.6.13
read-only
image = /boot/vmlinuz
root = /dev/hda3
label = Linux-2.4.31
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda1
label = Windows_XP
table = /dev/hda
# Windows bootable partition config ends

My /etc/fstab file:

/dev/hda2 swap swap defaults 0 0
/dev/hda3 / reiserfs defaults 1 1
/dev/hda4 /home reiserfs defaults 1 2
/dev/hdb5 /home/west/seagate reiserfs defaults 1 2
/dev/hdb6 /mnt/windows ntfs ro 1 0
/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0


My `df -H' command output:

Filesystem Size Used Avail Use% Mounted on
/dev/hda3 15G 2.4G 13G 17% /
/dev/hda4 28G 2.2G 26G 8% /home
/dev/hdb5 21G 398M 20G 2% /home/west/seagate

What I have tryed: Changing back to ext3. -Problem persist so I changed
back to reiserfs.

I thing it should be good to mention that before this problem, I had a
kernel panic problem. Which made boot process stop with a panic message
stating that block (0, 0) was not found. It happended after kernel 2.6.13 installation
and happened on both 2.4.31 and 2.6.13 booting processes

Problem was corrected by configuring reiserfs in the kernel configuration.

Thanks to all.

West.

Just a tip: To make it easier for yourself, how about naming your kernels vmlinuz-2.4.31 and vmlinuz-2.6.13? Also, make sure you have the System.map file under /boot for each kernel with names like System.map-2.4.31 and System.map-2.6.13. I also copy the kernel config to that location. And delete the symlinks Pat puts in there. IMO they're a bad idea.
Odd. Pat's stock 2.4.31 kernel has support for reiserfs built in. I don't know about the 2.6 which came with 10.2, but the 2.6.10 which came with Slackware 10.1 did not include reiserfs in the basic kernel. It was included as a module, requiring an 'initrd' to be built if you wanted to use the stock kernel.

Thanks a lot rkelsen

I'm going to try the tips. I thaught about the
system.map, but dind't do it beacuse 2.6.11 don't need it.

I'll post the outcome.

West.

Wanna make a bet?

The System.map file for any new kernels should always be copied to the /boot directory as well as the kernel image. That means that for every kernel image file under /boot you should have a corresponding System.map file. To avoid overwriting files, I put the version numbers in the filenames, i.e: vmlinuz-x.x.xx and System.map-x.x.xx. You can't go wrong doing it this way.

BTW - The ability to boot into 2.4 and 2.6 (and fully utilise the features of either) is a strength of Slackware, and an outstanding achievement by Pat.

-
Thanks for the help so far, rkelsen.

I made a fresh install. When I was looking at /usr/src/linux-2.4.31
to rename System.map I didn't find it there. I searched for the file in
other direcotories but didn't find it.

Any ideas where to look?

West

Try pointing in lilo.conf to vmlinuz-ide-2.4.31 instead of vmlinuz, maybe you replaced the image. Remember to run /sbin/lilo to apply the changes after editing lilo.conf

Are you using Pat's kernel or one you compiled yourself?

Pat always puts the System.map file in /boot.

-
-
Thank you very much rkelsen.

You were right all along. I used vmlinuz-ide-2.4.31 from
/boot I was looking at the incorrect dir. And the System.map
for that image was there too.

I apreciate your help very much. Now I'm having a problem
with the 2.6.13 kernel wich is having the kernel panic trouble
again. Says hdb1 not recognized. hdb is a 40gig seagate
I use for storate. It is an extended hdb1 with logical drives
hdb5 formated as reiserfs and hdb6 formated as ntfs.

Kernels trys to apply ext2, ext3, reiserfs and ntfs but all
fails to recognize hdb1.

I'll try and do my research on this one I know I've abused
your patience too much. Thank you very much any ways
Mr. rkelsen you have been very helpful.

West.
-

Support for reiserfs is not in Pat's standard 2.6 configuration. You need to make an initrd. Boot with your 2.4 kernel and read this file: /boot/README.mkinitrd

Have fun.

_
Hi rkelsen

Here is what I did.

2.4.31 fresh install

2.6.31 install and configure. In the filing systems section I configured
reiserfs as built-in (this way initrd is not necesary)

Configured lilo same way as before but for vmlinuz, used vmlinuz-ide-2.4.31
as the final procedure of kernel installation and configuration.

Done. Now both of them are loading.

Thanks for the help and support.