I guess we're all expecting this to be addressed in newer kernel this
Fall.
At least, that's what I've been reading...
Roman
Steve Howes wrote:
>
> Tom Brinkman wrote:
> >Keep in mind that the only reason you needed to append a mem
> > statement in the first place is because of a hardware
On Thu, 6 Jul 2000, Steve Howes wrote:
>Tom Brinkman wrote:
>>Keep in mind that the only reason you needed to append a mem
>> statement in the first place is because of a hardware deficiency.
>>
>
>I thought the reason for appending the 'mem=' was because the Linux
>kernal doesn't recognise
Tom Brinkman wrote:
>Keep in mind that the only reason you needed to append a mem
> statement in the first place is because of a hardware deficiency.
>
I thought the reason for appending the 'mem=' was because the Linux
kernal doesn't recognise more than 64Mb?
--
Steve - Cheltenham, UK
---
On Mon, 03 Jul 2000, you wrote:
>
> Everyone keeps asking this question over and over and I began to ask myself
> why? Well, everyone says add the line : append="mem=192M"
> to your lilo.conf. Here is the problem. The last "M" as in megabytes needs
> to be "m". Everyone steers wrong on this a
Title: append="mem=192m" For your memory problems.
Ive always used capital "M" and it
works...
- Original Message -
From:
James
Little
To: [EMAIL PROTECTED]
Sent: Monday, July 03, 2000 5:06 PM
Subject: [newbie] append="mem=192m&quo
Hi James,
M is used for Megabytes, and m for millibytes. Now one on this earth
uses that. You have a typo.
Personally I use append="128MB", and I have no problems. If you have 512
MB of RAM, try changing the append line to: append="mem=500MB"
This is a limitation in Linux which should be answered
Title: append="mem=192m" For your memory problems.
Everyone keeps asking this question over and over and I began to ask myself why? Well, everyone says add the line : append="mem=192M"
to your lilo.conf. Here is the problem. The last "M" as in megabytes needs to be "m". Everyone steers wr
