Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm having some issues with my new 2.6.0-test9 kernel. I have compiled everything i need as modules, which isn't much, and after compiling my image is 4MB! Hardly anything is compiled in. I've never had a kernel so big before. It could just be me because though I've been using Linux for a while, every time I try to compile my own kernel it's always a mess and never works. If you'd like to see my .config I'll post it if requested.
From what I've heard, the new 2.6.x kernels are significantly larger this time around, more code, etc. If you've compiled everything you need and stripped out everything you don't need, well, then, I suppose your stuck with a 4mb kernel for now...
Thanks for the quick reply trickykid, but what am I supposed to do with a 4MB kernel? I can't boot it with lilo (unless there is an option I overlooked). Is there another way to boot it?
Im running 2.6-test9 and my kernel is 1.5MB, with ACPI enabled (this adds about .3MB)
What you should do is:
1. Remove everything you dont need/want. This is a long process, but it will probably be the best. Only include support for YOUR sound card, YOUR nic, YOUR ports, etc.
2. Build as much as you can as modules. Very little actually has to be built into the kernel. You need all the CPU stuff built in, and the filesystem built in, but almsot everything else can be built as a module.
3. Remove ACPI/APM. These take up quite a lot of space.
4. Turn off ALL debuging. The debuging options will increase kernel size and make it slower.
My problem was the dumbest thing ever: I copied the wrong file into /boot. I feel like such a noob.
I'm having a new problem though.
I compiled module support into the kernel, but when it boots it says QM_MODULES: function not implemented or something like that. The kernel loads my USB modules but modprobe/insmod/lsmod doesn't work. I think it might be my modtools package because it does the same thing when I compiled a 2.4.22 kernel, but I don't know where to get a new version for either 2.4.22 or 2.6.0. Any help would be appreciated.
I use version 2.4.25 with a 2.6 test9 kernel. It they work
The version isn't the same as the kernel version they are intended for. I think they would all work for 2.6 too.
I have test9 on my box at 1.3m that is the biggest kernel i have ever herd of.
will you post a lspci you must have a box full of hard ware.
You must have something in every slot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.