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
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.
Quoted 26 lines · 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Compile more things as modules, your kernel has too many things compiled statically into it and is therefore too large to boot.
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" <[email protected]>
To: <[email protected]>
Cc: <[email protected]>
Sent: November 23, 2001 3:25 PM
Subject: Re: Sparc64 Compiles OK, but won't boot new kernel
Quoted 5 lines
Compile more things as modules, your kernel has too many things compiled statically into it and is therefore too large to boot.