How to test and safely keep using your janky RAM without compromising stability using memtest86+ and the memmap kernel param.

    • kumi@feddit.onlineOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      15 hours ago

      I’m curious: What`s motivating you to do that when the memmap param can do the same without patching?

  • F04118F@feddit.nl
    link
    fedilink
    arrow-up
    2
    ·
    2 days ago

    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!

    • kumi@feddit.onlineOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      2 days ago

      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$START not @. And you can use human sizes like 128M$RANGE.