Messages in this thread |  | | Date | Fri, 24 Jan 1997 03:20:19 +0000 (GMT) | From | Bryn Paul Arnold Jones <> | Subject | Re: Question about Boot Time Options: |
| |
On Thu, 23 Jan 1997, Scott T. Traynor wrote:
> I recently have gotten a machine with 256 megs of ram, and i was > wondering if one of you could help me? > basicily linux 2.0.27 is telling me i still have only 64 megs of ram in > the machine? i heard that there was a boot time option to > pass through,
Yep add mem=256M to the commandline (proberbly with append="mem=256M" in your lilo.conf)
> and also, my kernel i compiled is way to big, does anyone > know what size it has to be in K, in order for me to be able to > use lilo? > > Thanks for the time, and effort, >
Hmm, is this a first time on a resent kernel (ie just come up from 1.2.x)? The compressed kernel image is not produced in linux/zImage anymore, but in linux/arch/i386/boot/zImage.
If that's too large (the real zImage) then you have to either use modules, or start using a bzImage. To use bzImage you have to have lilo version 18 or later (lilo -V for the version). If you have, then go make a bzImage, and treat it like a zImage (all the usall make targets are supported: bzImage, bzlilo, ...).
The reason for the bzImage is the loaders can be loaded high at an earlier stage when compared with a zImage's, and so the kernel can be bigger (ie we get rid of realmode loader problem by getting to protected mode earlier).
> Scott Traynor >
Bryn -- PGP key pass phrase forgotten, \ Overload -- core meltdown sequence again :( and I don't care ;) | initiated. / This space is intentionally left | blank, apart from this text ;-) \____________________________________
|  |