> I've always been under the assumption that the size of the kernel image > doesn't matter, but it looks like that is not so. I've got a Sparc 20 > (sun4m) that I've compiled 2.4.20-pre9 with is a little of 2.5MB is size, > and it boots just fine. I've been trying to compile and boot 2.4.21-pre5 > with the k_map patch from ultralinux.org, and it came out to be a little > over 2.7MB, but when I try and boot it, I get an error of image to big to > fit into destination. > Has anyone else ever run up against this before? Is there a work around > for it? Everything that can be modularized is modularized in the kernel > and I'm at a loss to make this work.
I seem to remember something from a long time ago (and if I'm wrong, which is likely, I'm sure somebody will put me straight:) of something like this happening to me using lilo as a bootloader. I had compiled a new kernel, and placed it over an old one. I then FORGOT to run lilo again... Perhaps running lilo will help solve your problem. Regards, Pieter -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
