On Mon, 9 Oct 2000, Charles Boening wrote:
> try a "make bzImage" instead and use the kernel generaged by that.
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 09, 2000 10:15 AM
> To: [EMAIL PROTECTED]
> Subject: lilo won't install a new kernel
>
>
> a friend used the red hat embedded dev kit 1.0 to create a new
> kernel and a root filesystem. the root filesystem was placed in a
> small (40M) partition on /dev/hdb, and we're now trying to run lilo
> to register the new kernel.
>
> this kernel is a "zImage" (created by the dev kit), only 461K, so
> not overly large. but every attempt to run lilo generates the error
> message "Kernel too big."
>
> on the other hand, i dd'ed the kernel to a floppy, used "rdev"
> to set its root filesystem to /dev/hdb1, and it has no problem starting to
> boot the kernel off of floppy.
>
> so the kernel seems fine. in that case, what precisely causes
> the "kernel too big" error?
that doesn't appear to be an option. that was, of course, the
first thing i thought of, but it appears that the embedded dev kit
doesn't give you that option -- looks like you're stuck with a
zImage.
and it still doesn't explain why a relatively small zImage (460K)
doesn't work with lilo. one possibility that we toyed with is that
the kernels built by the dev kit, because they're supposed to be
embedded, have no capacity for dealing with lilo *whatsoever*.
could that be a possibility?
rday
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
