- cross-posted to:
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
How to test and safely keep using your janky RAM without compromising stability using memtest86+ and the memmap kernel param.
Well done. I recently revived the BadRAM kernel patch in order to do something similar; memtest86+ supports that functionality too, using <F4>, <F4>, <F10>, <F10>.
I’m curious: What`s motivating you to do that when the memmap param can do the same without patching?
Ooh, that rasdaemon looks interesting. thank for sharing!
This is amazing!! I had no idea this was possible!
One point of feedback: not having worked with memmap before, it is not immediately obvious to me which hex means what (I am guessing RANGE@START? ). Would be nice to have a link to an explanation there.
I am definitely sharing this, thank you for writing the blog!
Thank you, I’m glad you like!
not having worked with memmap before, it is not immediately obvious to me which hex means what (I am guessing RANGE@START? ). Would be nice to have a link to an explanation there.
I just have the link to the kernel docs because I think they do a better job explaining it than I would 😁
But yeah, basically. Except for this use-case you want
RANGE$STARTnot. And you can use human sizes like128M$RANGE.

