"Kernel /boot/vmlinux too big"
Aaron M. Johnson
I just complied because of a "Kernel /boot/vmlinux too big" error
message. The only irregularity I encountered before this was that I had
to use linear mode to get around a slightly out of bound cylinder
count. The kernel is 1.2M in size, and had a 497K system size, small
enough to use make zImage. Any idea why this would be happening?
Jakob Borg
Because you didn't read the README-file?
I'll spare you the trouble and qoute it for you:
- In order to boot your new kernel, you'll need to copy the kernel
image (found in /usr/src/linux/arch/i386/boot/zImage after compilation)
to the place where your regular bootable kernel is found.
--
Jakob Borg <jb...@df.lth.se> http://jb.replicant.nu
----
Each kiss is as the first.
-- Miramanee, Kirk's wife, "The Paradise Syndrome",
stardate 4842.6
Mike Esler
> >message. The only irregularity I encountered before this was that I had
> >to use linear mode to get around a slightly out of bound cylinder
> >count. The kernel is 1.2M in size, and had a 497K system size, small
> >enough to use make zImage. Any idea why this would be happening?
>
> Because you didn't read the README-file?
>
> I'll spare you the trouble and qoute it for you:
>
> - In order to boot your new kernel, you'll need to copy the kernel
> image (found in /usr/src/linux/arch/i386/boot/zImage after compilation)
> to the place where your regular bootable kernel is found.
>
> --
> Jakob Borg <jb...@df.lth.se> http://jb.replicant.nu
Be easy on him, for we're all guilty of not reading the README sometimes.
Apparently you are guilty of not reading something b/c you didn't answer his question.. :)
Instead of doing a make zImage, do a make bzImage.
Here is your quote out of the README for RH 6.1:
- Do a "make zImage" to create a compressed kernel image. If you want
to make a boot disk (without root filesystem or LILO), insert a floppy
in your A: drive, and do a "make zdisk". It is also possible to do
"make zlilo" if you have lilo installed to suit the kernel makefiles,
but you may want to check your particular lilo setup first.
- If your kernel is too large for "make zImage", use "make bzImage"
instead.
--
Mike Esler
System Administrator
Sverdrup Technology
Jakob Borg
>> >I just complied because of a "Kernel /boot/vmlinux too big" error
>> >message. The only irregularity I encountered before this was that I had
>> >to use linear mode to get around a slightly out of bound cylinder
>> >count. The kernel is 1.2M in size, and had a 497K system size, small
>> >enough to use make zImage. Any idea why this would be happening?
>>
>> Because you didn't read the README-file?
>>
>> I'll spare you the trouble and qoute it for you:
>>
>> - In order to boot your new kernel, you'll need to copy the kernel
>> image (found in /usr/src/linux/arch/i386/boot/zImage after compilation)
>> to the place where your regular bootable kernel is found.
>>
>> --
>> Jakob Borg <jb...@df.lth.se> http://jb.replicant.nu
>
>Be easy on him, for we're all guilty of not reading the README sometimes.
>
>Apparently you are guilty of not reading something b/c you didn't answer his question.. :)
>
>Instead of doing a make zImage, do a make bzImage.
Ah, well, as I read the question, the original poster had actually done some
reading and drawn the conclusion that zImage would work. The error was that he
didn't use the created zImage in arch/i386/boot, but instead the vmlinux file
in the kernel root. That file won't boot from lilo no matter how you make the
kernel. :)