Does your bios have the setting memory hole at 64M activated? I'm not sure if
that's the exact option. I only vaguely remember something like that as I
haven't rebooted for such a long time - and sorry - I refuse to for this! ;-)
Cheers,
Jason.
--On Monday, September 11, 2000 9:20 -0700 Erik
On Wed, Aug 30, 2000 at 05:56:52PM -0600, Art Edwards wrote:
> I just purchased two Athalon-based systems, each with 768M of ram.
> However, under debian (potato runnin kernel 2.2.17) the OS sees only 65
> M of memory. I have tried to use the append command
>
> mem=768M
>
> but it still sees only
Aaron Lehmann wrote:
>
> On my Athlon, Linux 2.2 sees only 65M of memory without using mem=.
> Linux 2.4-test seems to fix the problem and detects the memory
> automatically.
Not sure this may do with Athlon, but for your info;
Enhanced memory detection patches
http://
On my Athlon, Linux 2.2 sees only 65M of memory without using mem=.
Linux 2.4-test seems to fix the problem and detects the memory
automatically.
On Wed, Aug 30, 2000 at 05:56:52PM -0600, Art Edwards wrote:
> I just purchased two Athalon-based systems, each with 768M of ram.
> However, under debia
Art,
On Wed, 30 Aug 2000, Art Edwards wrote:
> I just purchased two Athalon-based systems, each with 768M of ram.
> However, under debian (potato runnin kernel 2.2.17) the OS sees only 65
> M of memory. I have tried to use the append command
>
> mem=768M
>
> but it still sees only 65 M?
>
>
5 matches
Mail list logo
