2.4 problems

[thully]

Hello,
I downloaded Kernel 2.4.0 and compiled it successfully, only to get a "kernel too big" message from lilo. I compiled everything I wanted into my kernel (not modules). I think that part of my problem is that I didn't use modules. How do I use them? I want to load all modules that I compile on startup, so that I can use the hardware without "modprobe". Can someone help me with this kernel compilation?

[demian]

Did you do a 'make bzImage' or 'zImage'. I know you said that it compiled ok but that's the place where you normally get the kernel too big message...
How big is the image btw ?

[thully]

I did make bzImage.
The kernel was about 2.4MB.

[demian]

Ooops, my browser only showed me half your post. (strange, but then it's mozilla). Anyway, I didn't see the part with the modules in the beginning. Normally you don't need to load the modules you want to use by hand. Be sure to check 'Kernel module loader support' during kernel config. And then, of course, build the new modules. Provided your /etc/modules.conf is up to date the modules should be loaded automatically on demand.

[SubPar]

Something looks wrong there. I also have everything I need compiled in and not as modules, but my image is only 620kB.

------------------
Got Konq (http://www.konqueror.org/)?

[demian]

GOSH. 2.4MB That is huge indeed. Ok, I never had probs with lilo telling me about too big kernel images, (and I never had images bigger than 700kB). So you really should concentrate on straightening out the problem with the modules. If you really need all that stuff. I mean, you must have compiled just about everthing to get a kernel this big.

[A_Lawn_GNOME]

Hehe, did you use /usr/src/linux/vmlinux or /usr/src/linux/arch/i386/boot/bzImage ? vmlinux is usually a meg or two while the bzImage should be 700ish.

Btw, I'm sitting at 627. My very first compile was at 735 but I wasn't aiming for a low size. Current size is 627 and I plan on cutting it down when I get a chance.

[mindwarp]

Dumb question comming: What is the diff between vmlinux and bzimage?

[Strike]

Originally posted by mindwarp:
Dumb question comming: What is the diff between vmlinux and bzimage?

bzImage is a compressed version of vmlinux

[sno]

yeah i always wondered that too

lol, cool u learn somethin new everyday

my 2.4.0 kernel is 854k is that good?
sound/nic/usb

ryanharron@yahoo.com

[Mountainman]

Ok, I am trying to compile 2.4. This is my first attempt at compiling my own kernal, so please bear with my ignorance. I uncompressed it, went through the make files and all but when I tried to do a make bzImage it comes up with errors. Now from the above posts I see that vmlinuz is basically the same thing as a bzImage. I am using mandrake 6.1, and it uses (i am almost 100% positive) vmlinuz. Is there anything special that I need to do? The NHF only goes through the bzImage. HELP!!!

------------------
---Meddle not in the affairs of Dragons, for thou art but a snack, and tasty with ketchup---
Http://www.geocities.com/mountainmancentral

[cs25x]

my 2.2.18 was 435K
my 2.4.0 is 750K
That is with everything modulated that i can find.

to make it with modules:

First make menuconfig
you can rotate either none or kernel or module selection with the space bar. check the help bit too, it helps.

If you think some gizmo might be nice to have, but are not certain, make it as a module. That way it wont increase the size of you rkernel.

You MUST NOT make your root file system as a module. This means <*> for e2fs

You should also be certain you only make it for a CPU that will work with your CPU. Like a 686L is not a pentium pro, and the thing will die before it boots.

Things that are moduable are marked with < > in the menu, if you can only say Y or [N] they are marked with [ ]


Save the config when it asks, this is saved
in .config

When you make a kernel, after make clean and dep, you make an image, make bzImage , because they are dropping zImage support in the future. Then , or at the same time, you make modules and make modules_install.

Save your old /etc/modules.conf you might want it again. save your old /boot/vmlinuz for the same reason.

Then copy or /usr/src/linux/arch/i386/boot/bzImage to ./vmlinuz

Then run lilo or whatever you use for a boot manager.

make a disk too, make it before you begin all of this so you can get your old system back.
dd if=/boot/vmlinuz of=/dev/fd0 bs=8192
I think that is what works for me. You can also put a floppy in and make zdisk

you might have to do
modprobe -c >/etc/modules.conf

reboot.

it doesnt work? put your old system back in and try make menuconfig again.

0000000000000000000000000000000000

[thully]

Ah, I see the problem.
I used vmlinux, not bzImage. I thought they were the same thing. When I compiled, it said Kernel = 835KB, and I was a bit confused that vmlinux was 2.4MB.

A side question:
What is the advantage to using modules if you are only going to use the kernel on one system? To me, going monolithic seems better.

[A_Lawn_GNOME]

Who said anything about one system?

Anyway, modules shrink the kernel (a plus) and gives you flexibility (no reboot).

If your hardware isn't going to change and your kernel doesn't ballon to an obscene size, then by all means, go ahead.

[The King Ant]

Advantage of modules: You can upgrade the module without rebooting. So if there's a new version of the module, you can just compile it, put it in your modules directory, rmmod the old one and insmod the new one.

You can change characteristics of an ethernet card with module parameters but just re-inserting the module rather than rebooting (change full/half duplex and 10/100).

[Ig0r]

Modules are also good for temporary stuff that you want to use without rebooting.
I have a zipdrive, but hardly ever use it. If I need it a simple "modprobe ppa" and I can.
The kernel stays smaller because I don't need it normally.

Also, some things require modules to be used. My two 3c509's require that I use a module to use them (no idea why). And my TV tuner card is nonstandard, so I need to use insmod options.