Hi, I have been trying to compile a new 2.4.2 kernel. Mainly to see if I can do it. The first time I did this it appeared to work fine. However I wanted to tweak things and re-did the same steps: make xconfig (loading the previously saved configuration then changing a couple of small things) make dep make clean make bzImage make modules make modules_install This time when I tried to run lilo it reported error kernel too big. When I looked I discovered that the new vmlinuz file was over 2GB! I can't work out what I did differently the first time, but I have tried several times since and always get the same problem. I have checked that I am using modules and compiling almost everything I can as modules, so I don't think the kernel needs to be this size. Any help appreciated. I think someone recently posted a similar problem, but I couldn't find it when I searched the archives, so sorry if this is a FAQ. Regards, Mark
This seems to catch people out at odd but regular intervals -- me included -- /usr/src/linux/vmlinux is ALWAYS too big. Have a look in /usr/src/linux/arch/i386/boot. You will find your bzImage there. Copy it to /boot, and add configuration to lilo, and you are away! On Tuesday 27 March 2001 21:26, Mark Daglish wrote:
Hi,
I have been trying to compile a new 2.4.2 kernel. Mainly to see if I can do it. The first time I did this it appeared to work fine. However I wanted to tweak things and re-did the same steps:
make xconfig (loading the previously saved configuration then changing a couple of small things) make dep make clean make bzImage make modules make modules_install
This time when I tried to run lilo it reported error kernel too big. When I looked I discovered that the new vmlinuz file was over 2GB! I can't work out what I did differently the first time, but I have tried several times since and always get the same problem. I have checked that I am using modules and compiling almost everything I can as modules, so I don't think the kernel needs to be this size.
Any help appreciated. I think someone recently posted a similar problem, but I couldn't find it when I searched the archives, so sorry if this is a FAQ.
Regards,
Mark
* cll muzh [Tue, 27 Mar 2001 22:00:11 +1200]:
Have a look in /usr/src/linux/arch/i386/boot. You will find your bzImage there. Copy it to /boot, and add configuration to lilo, and you are away!
Why don't you people just use 'make bzlilo'? That'll do all that's needed including calling LILO. -- Penguins to save the dinosaurs -- Handelsblatt on Linux for S/390
On Sun, 1 Apr 2001, Philipp Thomas wrote:
* cll muzh [Tue, 27 Mar 2001 22:00:11 +1200]:
Have a look in /usr/src/linux/arch/i386/boot. You will find your bzImage there. Copy it to /boot, and add configuration to lilo, and you are away!
Why don't you people just use 'make bzlilo'? That'll do all that's needed including calling LILO.
Well, I didn't know that target existed! Tell me more... 1) What does it call the resulting kernel? Does it choose a new, unique name, or will it overwrite /boot/vmlinuz or some other standard name? 2) Does it give me a new, unique 'label='? I must admit I'm leery of anything automatic, until I understand what's going on under the covers. ESPECIALLY with kernel re-compiles, I want to make absolutely sure that my old kernel won't be over-written, and the new kernel will selectable, but not default, in the lilo config. I'm tired of pulling the rug out from under myself! I haven't attempted a compile on a 7.1 system yet. One look at lilo.conf, where I saw initrd= instead of image=, and I knew I had some reading to do before I attempted it. Can you point me to a good starting point? What's in an initrd, and how do I build one? I've heard it allows one to boot systems with module-supported root filesystems, so I'm assuming it's a ramdisk filesystem which includes the /boot files as well as the necessary modules and module-loading utilities. Can I mount one using the loopback device to see what's included? What fstype? -- Rick Green "I have the heart of a little child, and the brain of a genius. ... and I keep them in a jar under my bed"
* Rick Green (rtg@mich.com) [20010402 07:28]:
Well, I didn't know that target existed! Tell me more... 1) What does it call the resulting kernel? Does it choose a new, unique name, or will it overwrite /boot/vmlinuz or some other standard name? 2) Does it give me a new, unique 'label='?
Look back in the thread and you'll find everything. By default, it'll not give it a unique name. But I posted my changed zlilo rule for arch/i386/boot/Makefile that'll append the kernel release to vmlinuz and System.map, thus making them unique. The only thing you have to do manually is to create a new entry in /etc/lilo.conf.
point? What's in an initrd, and how do I build one? I've heard it allows one to boot systems with module-supported root filesystems, so I'm assuming it's a ramdisk filesystem which includes the /boot files as well as the necessary modules and module-loading utilities. Can I mount one using the loopback device to see what's included? What fstype?
Search our support database for the keyword initrd and you'll find an article I wrote that explains what initrd is all about, which would lead too far here. Philipp -- Philipp Thomas <pthomas@suse.de> Development, SuSE GmbH, Schanzaecker Str. 10, D-90443 Nuremberg, Germany Penguins shall save the dinosaurs -- Handelsblatt about Linux on S/390
participants (4)
-
cll muzh -
Mark Daglish -
Philipp Thomas -
Rick Green