I have a small block of bad RAM in a DDR2-800 dual channel pair, @930.6MB, that's causing me lockups when I try to use K3B to copy a DVD. I looked at: http://badmem.sourceforge.net/docu/BadMEM-HOWTO.html http://sourceforge.net/projects/badmem/ Then I tried to find a kernel with it already compiled in on http://software.opensuse.org/search but no luck. Has anyone tried using this in a recent openSUSE kernel? I'm using 11.0, but with a 2.6.27 kernel from http://download.opensuse.org/repositories/home:/ilya_41/openSUSE_11.0/i586/ to get around a CIFS bug in the stock 11.0 kernels. Is there any easier way to prevent use of a bad RAM block until replacement RAM shows up? -- " We have no government armed with power capable of contending with human passions unbridled by morality and religion." John Adams, 2nd US President Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 26 December 2009 11:19:53 Felix Miata wrote:
Is there any easier way to prevent use of a bad RAM block until replacement RAM shows up?
When I had this issue, several years and releases ago, I swapped the memory sticks about to make sure the bad part was in the upper end of the memory mam and then passed the mem=xxxM to the kernel when booting, where xxx was just below the bad memory. Regards, David Bolt -- Team Acorn: www.distributed.net OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s openSUSE 11.0 32b | | openSUSE 11.2 32b | openSUSE 11.0 64b | openSUSE 11.1 64b | openSUSE 11.2 64b | TOS 4.02 | openSUSE 11.1 PPC | RISC OS 4.02 | RISC OS 3.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
David Bolt -
Felix Miata