Changeset ebbbf4f for content


Ignore:
Timestamp:
Nov 13, 2022, 11:57:43 PM (2 years ago)
Author:
w96k <w96k@…>
Branches:
master
Children:
197867d
Parents:
709b33e
Message:

Fix typos

File:
1 edited

Legend:

Unmodified
Added
Removed
  • content/en/posts/ram-fix.org

    r709b33e rebbbf4f  
    4343
    4444** How to understand that RAM is broken
    45 The most expected way to see RAM fail is [[https://computerhope.com/beep.htm][BIOS signalling]] that it is
    46 broken. It should beep using PC Speaker a special signal. You can read
    47 your motherboard manual to understand what does it mean. Usually it
    48 means that computer won't start with "completely" broken RAM module.
     45The most expected way to see RAM fail is [[https://computerhope.com/beep.htm][BIOS signaling]] that it is
     46broken. It should beep a special signal using a PC Speaker. You can read
     47your motherboard manual to understand what it mean. Usually, it means
     48that the computer won't start with a "completely" broken RAM module.
    4949
    50 If system loads just fine, but you experience problems along the way
    51 such as random segfaults and programs crashes, kernel panics and so on,
     50If the system loads just fine, but you experience problems along the way
     51such as random segfaults and programs crash, kernel panics, and so on,
    5252you might have broken segments of RAM. To detect such segments you can
    5353use several programs listed below. RAM checking is usually not a fast
    54 process, so you will probably need to left your device running for
     54process, so you will probably need to leave your device running for
    5555several hours.
    5656
    5757*** Memtest86+
    58 Memtest86+ runs from grub menu before your OS. It needs to run in such
    59 way because it needs whole range of RAM and your system can use a range
    60 of ram and would not allow to properly check it. It runs a lot of checks
    61 and checks every segment of your ram. While checking it logs the list of
    62 broken segments that you can write down.
     58Memtest86+ runs from the Grub menu before running your OS. It needs to
     59run in such way because it needs the whole range of RAM and your running
     60system is using that RAM range. It runs a lot of checks and checks every
     61segment of your ram. While checking it logs the list of broken segments
     62that you can write down.
    6363
    6464You can install it using your GNU+Linux package manager such as apt. The
    6565package is usually called ~memtest86+~. But there is a small caveat. If
    66 you use old version it wont work on UEFI systems.
     66you use the old version it won't work on UEFI systems.
    6767
    6868If it doesn't work you can download memtest86+ newer version
    69 distribution to your usb stick and load memtest from that. It should
    70 work on UEFI and BIOS systems. It can be downloaded from offical
     69distribution to your USB stick and load memtest from that. It should
     70work on UEFI and BIOS systems. It can be downloaded from the offical
    7171website.
    7272
     
    7575*** Memtester
    7676It has the same purpose as memtest86+, but it runs while your system is
    77 running, so it doesn't check whole RAM range, but only specified free
    78 ram available at your system at the moment of running this program. It
    79 can be installed using your package manager of choice by typing
    80 ~memtester~ as package name.
     77running, so it doesn't check the whole RAM range, but only specified
     78free ram available at your system at the moment of running this
     79program. It can be installed using your package manager of choice by
     80typing ~memtester~ as a package name.
    8181
    8282[[[https://pyropus.ca./software/memtester/][Official Website]]]
     
    8989error, congratulations! You don't have any problems with your RAM.
    9090
    91 If it shows small amount of errors like one or two, you can let Linux
    92 Kernel ignore such segments of RAM, so programs doesn't use such broken
    93 segments and programs work stable all the time. You need to use for that
    94 ~memmap~ kernel argument in your grub configuration. For example:
     91If it shows a small number of errors like one or two, you can let Linux
     92Kernel ignore such segments of RAM, so programs don't use such broken
     93segments and work stable all the time. You need to use for that ~memmap~
     94kernel argument in your grub configuration. For example:
    9595~memmap=0x100000$762ce9c38420,0x100000$34e03060,0x100000$87fce060,0x100000$23c63060,0x100000$87b6c060~. There
    9696is also grub config unit called ~GRUB_BADRAM~, but it looks like it is
    97 deprecated and memmap is preffered.
     97deprecated and memmap is prefered.
    9898
    9999For more details about blacklisting bad segments of RAM read [[https://unix.stackexchange.com/questions/75059/how-to-blacklist-a-correct-bad-ram-sector-according-to-memtest86-error-indicati][this
    100100comprehensive Stack Overflow answer]].
    101101
    102 If it shows huge amount of errors, like many thousand, it means that
    103 probably one of your sticks of RAM are broken. To detect which one is
    104 broken exactly you can probably figure it out looking at addresses or
    105 running another test using specific stick(s) of RAM and seeing if errors
     102If it shows a big number of errors, like many thousand, it means that
     103probably one of your sticks of RAM is broken. To detect which one is
     104broken exactly you can probably figure it out by looking at addresses or
     105running another test using a specific stick(s) of RAM and seeing if errors
    106106are gone.
    107107
    108 Be aware, that if you left with one RAM stick there is a chance, that it
    109 will only boot in specific RAM slot. Read your motherboard manual if
    110 something doesn't work.
     108Be aware, that if you leave with one RAM stick there is a chance, that
     109it will only boot in a specific RAM slot. Read your motherboard manual
     110if something doesn't work.
    111111
    112112If you have a RAM memory stick with tons of errors, you can try to
    113113repair it. I can't tell how exactly it is being done and why it is done
    114114in the way it should be done. You can find videos on fixing RAM sticks
    115 on YouTube and other resources. Here is [[https://youtu.be/KVR91p-Bd6M][the link to one of such videos]].
     115on YouTube and other resources. Here is [[https://youtu.be/KVR91p-Bd6M][the link to one of such video]].
    116116
    117117** RAM Optimizations of GNU+Linux system
    118 If your RAM was broken and you left with much less memory that you
     118If your RAM was broken and you left with much less memory than you
    119119expected, don't run and buy new RAM sticks. There is a chance that even
    120120with less RAM the system will work completely fine. Linux is pretty good
    121 at working on low end machines and it has different ways to handle lack
    122 of memory. It is often situation to have devices that outperform their
    123 tasks in modern world, like working on gaming laptop with very powerful
    124 CPU and GPU, that are used mostly to render text in a text editor.
     121at working on low-end machines and it has different ways to handle a
     122lack of memory. There is often a situation in a modern world, when a
     123person has devices that outperform their tasks, like working on gaming
     124laptop with very powerful CPU and GPU, that are used mostly to render
     125text in a text editor.
    125126
    126127*** Swap
    127 Swap is a partition on your hard drive that is being used in situation
     128Swap is a partition on your hard drive that is being used in a situation
    128129when there is no RAM left. It is used for other reasons too and such
    129130partition is recommended to have on most GNU+Linux systems.
    130131
    131132You can configure how often linux system will use swap changing
    132 ~swappiness~. You can read about changing that setting and to learn about
     133~swappiness~. You can read about changing that setting and learn about
    133134swap in general in the link below.
    134135
     
    146147
    147148*** Less bloat software
    148 Also as alternative way you can simply use less bloat software, so you
    149 don't need so much RAM in the first place. In many cases good software
    150 doesn't require a lot of RAM, but bad software always leak memory, so
    151 you would need many GiBs of RAM to use it properly. The most bloated
    152 software is a web-browser such as chromium and firefox and browser-based
    153 apps done in electron such as Slack, VSCode and other proprietary
    154 products.
     149Also as an alternative way you can simply use less bloat software, so
     150you don't need so much RAM in the first place. In many cases, good
     151software doesn't require a lot of RAM, but bad software always leaks
     152memory, so you would need many GiBs of RAM to use it properly. The most
     153bloated software is a web browser such as chromium and firefox and
     154browser-based apps done in electron such as Slack, VSCode, and other
     155proprietary products.
    155156
    156157** Conclusions
Note: See TracChangeset for help on using the changeset viewer.