Memtest86 is a very nice x86 RAM tester written by Chris Brady of SGI. See
http://reality.sgi.com/cbrady_denver/memtest86/ for more information. Since
bad RAM is extremely common on cheap PC hardware, this is quite useful to
The program runs stand-alone -- it's launched from LILO -- so that it can
get low-level access to test more RAM.
I've created an RPM at
http://www.mattdm.org/misc/memtest/memtest86-2.5-2.src.rpm -- feel free to
use this as a base. It would also be good to change the bit of the
installer that writes the initial lilo.conf.
Strongly seconded. We are not the only place where installing memtest86 in all
our servers LILO config is a standard procedure.
BTW, I think that would also serve RH Support when bugs are reported which smell
like RAM/bus problems. "Please enter 'memtest' on the LILO prompt and let it run
for a few hours to see if there are problems in this area"...
Will consider for next release cycle.
Did this get considered? I can't see it in rawhide.
considered, yes - but it will take some time to get it in place.
I've got a newer src RPM at http://www.mattdm.org/misc/memtest/ , by the way.
However, 2.7 seems to have a problem where it pops up an empty black box when it
starts, which is sort of confusing. (Not just my binaries, but the precompiled
one, on any machine I've tried it on.)
*** Bug 69346 has been marked as a duplicate of this bug. ***
FWIW, the RPM at
is now updated to version 3.0, and includes a few quick scripts to run grubby.
Oh, and the new version no longer has the black-box bug.
*** Bug 80566 has been marked as a duplicate of this bug. ***
It is suggested that this be added to the boot/install cd
as an initial option, and/or rescue option. Running memtest86
prior to installing Red Hat linux will save numerous
support calls due to bad/cheap RAM, and also therefore
improve the first user experience.
Suse also has memtest86 as an option on the install CD.
Red Hat was praised for "check media", similar praise would happen for "check
memory" - even if poorly documented.
Implemented in development branch.
So, resolving, since it's in Fedora Core.