2.4 Kernel 'Too big' - WTF?

[nanode]

Hey,

I was having some troubles w/ my 2.4.0 kernel which I recently built, so I recompiled it, this time, building some modules I had previous forgot.

I put everything in its places, but when I run /sbin/lilo I get a complaint, like "kernel too big"

Here's how I compiled 2.4.0:

make menuconfig (loaded old config, made some changes)
make dep
make modules
make modules_install
cp vmlinuz /boot/vmlinuz-2.4.0
cp System.map /boot/System.map-2.4.0
[added stuff to /etc/lilo.conf - it booted before]
lilo

[ColdPack]

How big is your /boot partition?
The only time I've seen the "kernel is too big" bit is when it says that it's too big for a floppy boot (then I know I need to do some trimming http://www.linuxnewbie.org/ubb/smile.gif ).

------------------
What if everything is an illusion and nothing exists? In that case, I
definitely overpaid for my carpet.
-- Woody Allen, "Without Feathers"

[demian]

Originally posted by nanode:

make dep
make modules
make modules_install
cp vmlinuz /boot/vmlinuz-2.4.0
cp System.map /boot/System.map-2.4.0
[added stuff to /etc/lilo.conf - it booted before]
lilo

Chamge the line cp vmlinuz /boot/vmlinuz-2.4.0 to cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.0 (in case you did a make zImage previously, replace bzImage with zImage (in case you don't have a PC replace i386 to something appropriate)).

The vmlinuz in the toplevel dir is not the compressed kernel image! We had this problem here only a day or two ago.

[mdwatts]

Doesn't look like you did 'make bzImage'.

[nanode]

Thanks people -

I was coding at work for a few hours, now I realized what I did.

People do dumb things, like cp the uncompressed kernel when they are desperate and deprived of sleep.

[battousai]

yea after you do menuconfig n stuff and save the configuration then just

"make dep clean modules modules_install bzImage"

put all that in the quotes not including the quotes in the terminal as one line and it will do them all, then just
cp System.map /boot
and
cp arch/i386/boot/bzImage /boot
then i'd make sure you have lilo to boot that image and then type lilo to initialize it. then reboot and have fun http://www.linuxnewbie.org/ubb/smile.gif