vmlinuz too big

[Matthew Weier O'Phinney]

I am using Slackware 8 with kernel 2.4.5, and tried to recompile the
kernel with some hardware/netware specific options I needed. (I used
"make xconfig" and "make bzImage") When I finished, I moved my old kernel
to /vmlinuz.old, copied the new kernel to the root directory as /vmlinuz, and
edited /etc/lilo.conf to add the new image. When I ran lilo to update, I
received the message "Fatal: Kernel /vmlinuz is too big".

I cannot find any information on this anywhere -- any help?

Thanks,
Matthew

[Jonas Due Vesterheden]

In article <fy4R7.36398$un.73...@typhoon.nyroc.rr.com>, Matthew Weier

O'Phinney wrote:
> I am using Slackware 8 with kernel 2.4.5, and tried to recompile the
> kernel with some hardware/netware specific options I needed. (I used
> "make xconfig" and "make bzImage") When I finished, I moved my old kernel
> to /vmlinuz.old, copied the new kernel to the root directory as /vmlinuz, and
> edited /etc/lilo.conf to add the new image. When I ran lilo to update, I
> received the message "Fatal: Kernel /vmlinuz is too big".

What new kernel did you copy? linux/arc/i386/boot/bzImage?

> I cannot find any information on this anywhere -- any help?

Are you sure you haven't added support for anything you don't need? If not so
you'll probably have to put some (as many as possible) drivers into modules.

Regards Jonas

--
"A conservative is a man who is too cowardly to fight and too fat to run."
-- Elbert Hubbard

Registered Linux user #198786 (http://counter.li.org)

[Jerry Peters]

> Thanks,
> Matthew

What exactly did you copy? You should have copied bzImage. Sounds like
you copied vmlinux, which is not a bootable kernel.

Jerry

[Matthew Weier O'Phinney]

Indeed, even though I've compiled kernels over a dozen times, I managed
to forget what I was supposed to copy. Thanks everyone for pointing out
my **faulty memory** -- everything's working now.

In article <8BaR7.290344$W8.97...@bgtnsc04-news.ops.worldnet.att.net>,

[Richard]

Don't forget you can make bzlilo

Richard :)

Matthew Weier O'Phinney wrote:

[Gary D. Watland, Jr.]

As others have already stated don't compile what you don't need.
Try Gujin instead of lilo.
Get a working/bootable system and install Gujin-loads large kernels
http://gujin.sourceforge.net

P.S. It doesn't matter what or where you put the boot img file. /boot
is typical, but putting in /vmlinuz is fine it's just a boot image.

Hope this helps. My boot image is 1024165/bytes pretty big.
-Gary Watland, Jr.

"Matthew Weier O'Phinney" <weiero...@griffdog.net> wrote in message news:<fy4R7.36398$un.73...@typhoon.nyroc.rr.com>...

[Jerry Peters]

Matthew Weier O'Phinney <weiero...@griffdog.net> wrote:
> Indeed, even though I've compiled kernels over a dozen times, I managed
> to forget what I was supposed to copy. Thanks everyone for pointing out
> my **faulty memory** -- everything's working now.

> In article <8BaR7.290344$W8.97...@bgtnsc04-news.ops.worldnet.att.net>,
> "Jerry Peters" <gape...@worldnet.att.net> wrote:

>> Matthew Weier O'Phinney <weiero...@griffdog.net> wrote:
>>> I am using Slackware 8 with kernel 2.4.5, and tried to recompile the
>>> kernel with some hardware/netware specific options I needed. (I used
>>> "make xconfig" and "make bzImage") When I finished, I moved my old
>>> kernel to /vmlinuz.old, copied the new kernel to the root directory as
>>> /vmlinuz, and edited /etc/lilo.conf to add the new image. When I ran
>>> lilo to update, I received the message "Fatal: Kernel /vmlinuz is too
>>> big".
>>
>>> I cannot find any information on this anywhere -- any help?
>>
>>> Thanks,
>>> Matthew
>>
>> What exactly did you copy? You should have copied bzImage. Sounds like
>> you copied vmlinux, which is not a bootable kernel.
>>
>> Jerry

Solved that problem - I have scripts to do all of the dirty work. Only
problem is if the location of the bzImage System.map etc changes in
the kernel tree.

Jerry