Re: Compiling Kernel 2.4.20
Sorry if I'm way off base on this one, but I've been paying around with
different kernels (mostly the 2.4.18 stuff) on an Ultra I. When I've
finished compiling the source, the resulting vmlinux file isn't
compressed, just like you've stated. Just for grins, I used gzip to
compress the file, then simply moved and renamed it to its proper
place/name (/boot/vmlinux-011503). I recreate the symbolic link from
/vmlinuz to my new kernel, check Silo.conf to make sure everything is
pointing to where it should and I can then reboot without any problems.
Since I've g'zipped the kernel, it's small enough, and the system knows
to decompress it.
Perhaps you might try the same thing with the 2.4.20 source.
Just a hunch.
Jeff Pickell
http://www.xionic.net/~jkp
On Sat, 2003-02-01 at 22:41, Steve Dunham wrote:
> David Johnson wrote:
> > unixed unixed wrote:
> >
> >> 2) compile by hand. (make config) (make dep) (make modules) (make
> >> install_modules) (make vmlinux)
> >> It compiles fine, no errors, but the image is larger, and SILO
> >> complains that the image is too large (uncompressed image too large
> >> for space). I’ve seen hints from other users on this list to use
> >> bzImage to compress the file, but to me that looks like an x86 tool
> >> only because it is not in the sparc64 directory space…
> >> Hopefully someone out there can help me get passed this kernel build
> >> problem… I would be tickled to learn –any- way to get past it.
> >>
> >
> > As I understand it, compressing the image won't help at all since its
> > the uncompressed image it needs to work with.
> > You just need to include as little as possible in your kernel and as
> > much as possible as modules to get it below the size limit. 2.4 kernels
> > do tend to be a little bulky, you may well have to make do with a 2.2
> > kernel...
>
> Ten minutes ago I had the same issue. I went through and modularized
> everything I could (there wasn't much more I could modularize), rebuilt
> the kernel, and then realized I'd never tried stripping the one that was
> too big. :)
>
> (That said, the kernel didn't run .. I'd be interested to know if anyone
> has gotten 2.5.x to run on a Blade100. I'd like to debug/use the IPSec
> stuff.)
>
>
> Steve
> dunham@cse.msu.edu
>
> --
> Steve Dunham
> http://www.cse.msu.edu/~dunham
>
>
> --
> To UNSUBSCRIBE, email to debian-sparc-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Reply to: