I think I sorted out the problem. I could have sworn that I had the full
amount of memory before BadRam. Anyway, I compiled the kernel again with
HIGHMEM support. This time I get the following answer when using dmesg:
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009e800 (usable)
BIOS-e820: 000000000009e800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000d0000 - 00000000000d8000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003def0000 (usable)
BIOS-e820: 000000003def0000 - 000000003deff000 (ACPI data)
BIOS-e820: 000000003deff000 - 000000003df00000 (ACPI NVS)
BIOS-e820: 000000003df00000 - 000000003e000000 (usable)
BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
96MB HIGHMEM available.
896MB LOWMEM available.
I posted my problem to a forum, and I got an answer. The amount of
memory seems to be a problem, so having HIGHMEM not enabled, I would
loose 128MB. However they recommend not to enable HIGHMEM just because
of because of some memory mapping issues, which would probably cost more
RAM than I gain. It would just be profitable if I would have a
reasonable amount of memory (see also
http://kerneltrap.org/node/2450/7217
<http://www.linux-web.de/redir.php?url=http%3A%2F%2Fkerneltrap.org%2Fnode%2F2450%2F7217>)
Anyway, this issue is probably solved.
Best regards,
Torsten
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
