Re: How to load 2.6.22 kernel (image too large to fit ...)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ben Collins wrote:
On Sat, 2007-05-19 at 23:44 +0200, Krzysztof Helt wrote:
Hi again,

I overcame the problem with too big kernel with the attached patch, but I run into another problem. Now, the silo says:

"Your kernel cannot fit into the memory destination. This
can be resolved by recompiling the kernel with more devices
built as modules, or upgrading your kernel to one that
supports being loaded to higher memory areas (currently
2.6.3+ or 2.4.26+)."

Does it mean, that 2.6.22-rc1 for sparc32 cannot be relocated?

The patch isn't complete. SILO checks to make sure that the kernel can
be relocated. You probably also need to patch up sparc kernel to allow
itself to be loaded at an alternate location. Whole lot of work.


The silo patch seems complete. It is now kernel hHdrS version, which says it is not relocatable. If the kernel fits 2.5MB size, the patch does not hurts (just allocate memory and copy kernel back to 2.5MB area).

Honestly, just compile it with less stuff. I don't have a sparc32 to
test anything on, so I'm of no help.

I thought I modularized everything but I rechecked my options and I left nfs compiled into the kernel statically.
Now, it fits for UP kernel.

Thank you for your time,
Krzysztof
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux