On one of our machines:
Nov 7 11:51:33 yoda kernel: Memory: 127668k/131072k available (1008k
kernel code, 412k reserved, 1640k data, 64k init)
uname -a output:
Linux yoda..com 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 i686
unknown
Clean, no re-compilation of kernel, RedHat 6.1 Dist.
Also
> AJ>> I'm running a plain RH6 installation. No special drivers/patches
> AJ>> and if I remember correctly I didn't recompile the kernel since
> AJ>> installation (though I'm not absolutely sure about this).
>
> 1. Are you sure you haven't edited lilo.conf?
I think its something I would have r
I know that some mb's work some not. AFAIK kernel gets the amount of
memory from what bios reports in page_zero - I believe it supposed to be
somewhere in setup.c file under asm/i386 dir. I have ASUS P2B mb - it
works fine - no parameter to kernel needed.
On Fri, 12 Nov 1999, Stanislav Malyshev a
AJ>> I'm running a plain RH6 installation. No special drivers/patches
AJ>> and if I remember correctly I didn't recompile the kernel since
AJ>> installation (though I'm not absolutely sure about this).
1. Are you sure you haven't edited lilo.conf?
2. What motherboard is it?
--
[EMAIL PROTECTED]
"Stanislav Malyshev a.k.a Frodo" <[EMAIL PROTECTED]>
To: "Linux-IL Mailing List" <[EMAIL PROTECTED]>
Sent: Friday, November 12, 1999 3:08 PM
Subject: 64M again
> Good `date`!
>
> I know it looks like a silly FAQ question, but it isn't:
> Does an
Good `date`!
I know it looks like a silly FAQ question, but it isn't:
Does anybody know, what happens with Linux detection of above 64M memory?
I know about "appemd=" solution, but it is not what I want - I want it to
know the memory size by itself. I heard that later kernels know to detect
memor
