I did a fresh install of slack 10.2 and kernel 2.4.31. I then downlaoded the source of 2.4.34 so I could recompile with highmemory support, and work with a quicker, more efficient kernel. Turns out, I cannot get it right. I've read through numerous tutorials on kernel compiling, and none of them worked for me.. I'll try my best to reinact my commands for what I was doing when compiling. Here's a few details first though:

all FS are ext2
Partition scheme:
sda1 - swap
sda2 - /boot
sda3(extended partition)
sda5 - /root
sda6 - /home
sda7 - /tmp
using lilo bootloader

Here's what I did..


cd /usr/src/
rm linux
ln -s /usr/src/linux-2.4.34 /usr/src/linux
cd linux
make mrproper
pico /usr/src/linux/Makefile
I then uncommented (which means to take away the '#', right?) "#export INSTALL_PATH=/boot"
and in the same file i changed export ROOT_DEV = /dev/sda5
ctrl + O, then ctrl + X to save and exit
make menuconfig
make dep
make bzImage
cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.4.34
rm /boot/vmlinuz
rm /boot/vmlinuz-2.4.31
ln -s /boot/vmlinuz-2.4.34 vmlinuz
make modules
make modules_install
(still in /usr/src/linux)
cp System.map /boot/System.map-2.4.34
cp .config /boot/config-2.4.34
cd /boot
ln -s System.map-2.4.34 System.map
ln -s config-2.4.34 config
cd /usr/src/linux
make install (i dont think i had to do this, but made me feel better..i guess)

it ran the /sbin/lilo command for me and it checked out okay

Here's what my lilo.conf looks like though:

at the top there's

"#Start LILO global section
append="sata.i"
boot = /dev/sda
message = /boot/boot_message.txt
prompt
timeout = 1200
#Override dangerous defaults that rewrite the partition table:
change-rules
reset
#VESA... blah blah
vga = 773"

and towards the bottom I have:

"#Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda5
label = Slack-2.4.34
read-only
#Linux bootable partition config ends"

And now, I reboot

things are flying by the screen, going fast, quicker, then halts to:

VFS: Cannot open root device "805" or 08:05
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 08:05

I am sure most of you have seen complaints about this message billians of times and concured it yourselves. But I have not. In order to boot back to multiuser mode, I have to pop in the cd and type "sata.i root=/dev/sda5 noinitrd ro" and stuff's great.. but still.. i'm at 2.4.31..

I've spent several days and a couple all nighters.. installing, reinstalling, headaches.. missing study time for hopes of it to work.

Can someone please help.

This seems to be the standard kernel panic when you forget to include the file system of your root in your kernel .config. Also have you included SATA/SCSI support , cos sda5 means its SATA/SCSI
Recompile and make sure you have ext2 and SATA/SCSI support built in.

Now about your kernel upgrade.... here's wat I use and find the easiest method to recompile....

forget make mrproper,make oldconfig

do the foll:
#if you have X running then better do make xconfig
Read thru everythin properly and customise correcrtly . See bottom of post
Then do ...
edit your lilo.conf ..... copy the existing linux config once more and just change the kernel name...
i.e :
will become
Restart... if you get a kernel panic ... tinker with your config more , google and ask around.


Also see this very useful guide ...
http://www.techenclave.com/forums/co...-2-a-5099.html

Also read Linux Kernel in a nutshell (www.kroah.com)

Dury,

Thank you, your response and time given is greatly appreciated. I think you're right about the config and needing to redo my config because I was hitting enter quite a few times (rushing through). I just finished reinstalling slackware 10.2 with 2.4.31 on a fresh, formatted partitioned hard disk. I'm going to use that link you supplied to me -- the link to techendave.com -- while I upgrade my kernel. Thanks a million for that link, it was very similar to something I was hoping to come across soon.

One quick question: Let's say I have my kernel upgraded and everything's cool. And now I want to add one or two things to my kernel. This re-recompile one would do just to make a small, minor mod for a specific purpose. How would this be done? you'd have to do make oldconfig, edit whatever it is, and then..? make dep, modules, install, and run lilo again? Pretty much, the whole procedure? or can some steps be eliminated?

oops sorry I didn't see you were using 2.4 kernel. Then I think you will have to do "make dep" as well (which is automatic in 2.6.x). Why dont you upgrade to 2.6 kernel , it is pretty stable!

If you want to just add a MOD then just do make modules_install and make dep. No need to change lilo all over again , IMHO. But I might be wrong! I would say why don't you install it on lilo all over again... it takes hardly any time, the compilation would be only for the new modules and not for the whole kernel. You will be done in a minute.