memtest86+ 4.10-1.1 --- included in the current debian stable distribution
--- still has the original #319837 (Date: Mon, 25 Jul 2005 06:03:06 UTC)
problem, now numbered as #549429 (Date: Sat, 3 Oct 2009 11:06:02 UTC).
Paolo Ornati <[email protected]> described on Mon, 1 Jan 2007, that
this is not really a bug of the free softwares, but some BIOS makers break
the rule, that reserverd area for BIOS is not allowed to start BELOW
09A000.
In the last 6 years it turned out that more and more motherboards are
delivered by a BIOS braking the standard, ... the very popular ASUS
appears to be a main source for this kind of motherboards.
On the other hand, ASUS is the only which provides BIOS support for ECC
memory modules in almost all of their motherboards.
The result in low end desktop boxes: either I can use ECC memory modules,
or I can use memtest86+.
In my case, tho motherboard is ASUS am3 M4A89GTD PRO/USB3 with 16GB ECC
memory and an AMD Phenom II X6 1100T Processor.
But reading the diverse communications in the last 6 years, it does not
really matter.
The only interesting factor is, that my situations is the USUAL situation:
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 0000000000098000 (usable)
[ 0.000000] BIOS-e820: 0000000000098000 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 00000000dfe90000 (usable)
[ 0.000000] BIOS-e820: 00000000dfe90000 - 00000000dfea8000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000dfea8000 - 00000000dfed0000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000dfed0000 - 00000000dff00000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000420000000 (usable)
[ 0.000000] DMI present.
[ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
Namely, 0000000000098000 << 000000000009a000, that is all what is relevant.
Tanks,
Peter.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
