Kernel 2.4 compiles buit give me "loading linux....." on reboot

[UnderScore]

I have a Celeron 450, 128MB RAM, 6GB HD dedicated to linux, Matrox G200 8MB Millennium, Voodoo2 12MB, SB Live! Value, DLink DFE-503+ 10/100, RH 7.0 with all the updates as of Jan 6, 2001.

I dl'ed the kernel fropm ftp.kerenel.org, did a tar xzvf to it, did a

make mrproper
# no problems

make xconfig
# no problems

make dep
# no problems

make clean
# no problems

make bzImage
# no problems

make modules
# no problems

make modules_install
# no problems

renamed the old System.map & vmlinuz-2.2.xx as per the NHF
# no problems

cp'ed the bzImage & new System.map as per the NHF
# no problems

setup lilo to give me the option of dropping back to the old 2.2.16-22 kernel.
# no problems

I reboot. Select the new kernel and the bootscreen and I get:
Loading Linux .............


and that is it.

Have I done anything wrong??
Should I have done something differently??
Anyone else move to the new 2.4 kernel on RH 7.0??

Are there any particular kernel compilation snags to watch out for?? Are there kernel pieces I should have kept as modules or vice versa??

It know that I dont need SCSI or any odd things but maybe I messed something up.

Any help is appreciated.

James

------------------
UnderScore
_

[The King Ant]

I'm running 2.4 prerelease on RH 7.0 with no problems. Did you run "/sbin/lilo" as root after changing your /etc/lilo.conf file around?

How long have you waited when it says "Loading Linux...."? Maybe you just have to wait for something to time out?

You can still boot into your old kernel right?

A listing of your /etc/lilo.conf file and ls /boot might help.

You might also want to try deleting your kernel config file and starting over from scratch, just in case you left out something that you really needed. You can always make a backup of the old config file first.

[UnderScore]

Reinstalled RH7.0, updated using the RH Updater, dl'ed kernel 2.4.0, this time it got to:
Loading Linux.....
Decompressing Kernel .. OK

and that is it.

make mrproper
# no problems

make xconfig
#no problems

make dep
#no problems

make clean
# no problems

make bzImage
# no problems

make modules
# no problems

make modules_install
# no problems

renamed the old System.map & vmlinuz-2.2.xx as per the NHF
# no problems

cp'ed the bzImage & new System.map as per the NHF
# no problems

setup lilo to give me the option of dropping back to the old 2.2.16-22 kernel.
# no problems


*** begin lilo.conf ****
boot=/dev/hdc1
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=linux

image=/boot/vmlinuz-2.4.0
label=linux
read-only
root=/dev/hdc7

image=/boot/vmlinuz-2.2.16-22
label=linuxold
read-only
root=/dev/hdc7

other=/dev/hda1
label=dos
****** end lilo.conf ******


***** begin ls -l /boot ******
total 3915
lrwxrwxrwx 1 root root 20 Jan 6 23:51 System.map -> System.map-2.2.16-22
-rw-r--r-- 1 root root 200285 Aug 22 16:56 System.map-2.2.16-22
-rw-r--r-- 1 root root 458559 Jan 6 23:33 System.map-2.4.0
-rw-r--r-- 1 root root 512 Jan 6 14:05 boot.1601
-rw-r--r-- 1 root root 5824 Aug 23 10:59 boot.b
-rw-r--r-- 1 root root 612 Aug 23 10:59 chain.b
lrwxrwxrwx 1 root root 15 Jan 6 13:57 kernel.h -> kernel.h-2.2.16
-rw-r--r-- 1 root root 405 Jan 6 20:14 kernel.h-2.2.16
-rw-r--r-- 1 root root 0 Aug 25 08:43 kernel.h-2.4.0
drwxr-xr-x 2 root root 12288 Jan 6 13:47 lost+found
-rw------- 1 root root 25088 Jan 6 23:36 map
-rw-r--r-- 1 root root 23108 Aug 23 10:59 message
lrwxrwxrwx 1 root root 21 Jan 6 13:56 module-info -> module-info-2.2.16-22
-rw-r--r-- 1 root root 11773 Aug 22 16:56 module-info-2.2.16-22
-rw-r--r-- 1 root root 640 Aug 23 10:59 os2_d.b
-rwxr-xr-x 1 root root 1621492 Aug 22 16:56 vmlinux-2.2.16-22
lrwxrwxrwx 1 root root 13 Jan 6 23:35 vmlinuz -> vmlinuz-2.4.0
-rw-r--r-- 1 root root 627392 Aug 22 16:56 vmlinuz-2.2.16-22
-rw-r--r-- 1 root root 991422 Jan 6 23:33 vmlinuz-2.4.0
******* end ls -l /boot *******

Do I need to RAM disk built into the kernel?

The NHF says that I should create /boot/initrd.2.4.0
Why?

------------------
UnderScore
_

[This message has been edited by UnderScore (edited 07 January 2001).]

[A_Lawn_GNOME]

I just compiled 2.4 on RH7 too. The only difference I can see is that you didn't copy vmlinux-2.4 to /boot. I'm new to this compiling stuff but I don't see how that would make a difference.

A RAM disk shouldn't matter either.

As for initrd, I didn't do anything with that and don't even remember reading that in the NHF.

As I said, I'm new to this. Wish I could help more but this hits me where I'm weak.

[Mr CrankyPants]

If you have used any modules in your kernel I usually
"depmod -a" (update the module dependanies tree)
Just before updating my lilo.conf

[Sterling]

Check to make sure the versions of everything you've got installed match the versions needed for the new kernel. (Several things have changed in incompatible ways) Also check your kernel configuration - compiling won't necessarily fail if you have a bad option selected, but boot might. Reading through some of the files in the Documentation directory may also suggest a solution.

------------------
-Sterling
-This post made with the Lizard! (http://www.mozilla.org)

[cs25x]

did you run lilo?
your problem looks to be system map -> 2.2
modules -> 2.2

vmlinuz -> 2.4

depmod -a should have run when you did make modules_install

another thing is /etc/modules.conf you might need modprobe -c >modules.conf

of course you save the old one first

000000000000000000000000000