If I get it right, there's no need for badram patch unless bad bytes are spread all over the map. With a bit more manual effort one can use memmap=exactmap parameter already present in current kernels.
A howto for 2.6.25 kernels: http://groups.google.com/group/fa.linux.kernel/msg/d90e920265afafd8 . In 2.6.24 one needs to look up the bios provided memory map from the beginning of the dmesg output. Then convert the map to the memmap= format and merge with the bad memory block(s) to be reserved. And last but not least, if it's worth a couple of hundred dollars to you, if you provide a financial incentive, someone might as well step up and come up with something that'd serve your needs. -- [needs-packaging] BadRAM Linux Kernel Patch https://bugs.launchpad.net/bugs/185804 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
