Sparc64 Compiles OK, but won't boot new kernel

Sparc64 Compiles OK, but won't boot new kernel

[Norm Dressler]

Hi,

I have been able to successfully compile the 2.4.14 and 2.4.15 kernels
for Sparc64 but each gives me an error on boot-up:

Image to large for Destination  (twice)

It then kicks me back to the silo prompt.  My kernel is trimmed back
quite a bit and there isn't a lot there.  

It's not a compressed kernel -- should it be?  How do I do that since
the bzImage make is missing from the Sparc64 makefiles?

I am using Redhat 6.2 on an Enterprise 4000, 4 Ultrasparc-II CPU's and
2Gb of Ram.

Any suggestions??

Norm

Re: Sparc64 Compiles OK, but won't boot new kernel

[Luigi Genoni]

You did not enable LVM support, did you?
if you did enable, with 2.4.15, yyopu will see the bug i wrote about.

I had similar problems like you, I simply compiled as a module all I
could, and I solved.


On Fri, 23 Nov 2001, Norm Dressler wrote:

> Hi,
>
> I have been able to successfully compile the 2.4.14 and 2.4.15 kernels
> for Sparc64 but each gives me an error on boot-up:
>
> Image to large for Destination  (twice)
>
> It then kicks me back to the silo prompt.  My kernel is trimmed back
> quite a bit and there isn't a lot there.
>
> It's not a compressed kernel -- should it be?  How do I do that since
> the bzImage make is missing from the Sparc64 makefiles?
>
> I am using Redhat 6.2 on an Enterprise 4000, 4 Ultrasparc-II CPU's and
> 2Gb of Ram.
>
> Any suggestions??
>
> Norm
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Re: Sparc64 Compiles OK, but won't boot new kernel

[David S. Miller]

Compile more things as modules, your kernel has too many things
compiled statically into it and is therefore too large to boot.

Re: Sparc64 Compiles OK, but won't boot new kernel

[Norm Dressler]

I was able to solve it -- I also had freeswan patched into the kernel and
when you include the debug portions, it more then doubles the size of your
kernel.

Norm

----- Original Message -----
From: "David S. Miller" <davem@redhat.com>
To: <ndressler@dinmar.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: November 23, 2001 3:25 PM
Subject: Re: Sparc64 Compiles OK, but won't boot new kernel


>
> Compile more things as modules, your kernel has too many things
> compiled statically into it and is therefore too large to boot.
>
>

RE: Sparc64 Compiles OK, but won't boot new kernel

[Holzrichter, Bruce]

I've been manually gzipping the kernel for Sparc64, just gzip the built
kernel, and copy to your boot partition.  Then follow the normal setup
steps, and This works fine.  There is an initial size limit IIRC, of about
over 2mb.  Trimming it down, and gzipping has been working great for me.  

Hope this helps,
Bruce H.

-----Original Message-----
From: Norm Dressler [mailto:ndressler@dinmar.com]
Sent: Friday, November 23, 2001 10:09 AM
To: linux-kernel@vger.kernel.org
Subject: Sparc64 Compiles OK, but won't boot new kernel


Hi,

I have been able to successfully compile the 2.4.14 and 2.4.15 kernels
for Sparc64 but each gives me an error on boot-up:

Image to large for Destination  (twice)

It then kicks me back to the silo prompt.  My kernel is trimmed back
quite a bit and there isn't a lot there.  

It's not a compressed kernel -- should it be?  How do I do that since
the bzImage make is missing from the Sparc64 makefiles?

I am using Redhat 6.2 on an Enterprise 4000, 4 Ultrasparc-II CPU's and
2Gb of Ram.

Any suggestions??

Norm

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/