- lightweight and fast memory information tool written in rust
- colorful and easy-to-read terminal output using the colored crate
- displays total and available system memory from /proc/meminfo
- detailed info about memory modules (dimms) via dmidecode
- shows slot, size, speed, type, bank locator, ecc status, and configured voltage
- minimal dependencies and straightforward to build
- requires root privileges to access detailed hardware info via dmidecode
mfetch
github.com/xdearboy/mfetch
ββββββββββββββββββββββββββββββ
memory
total: 15.54 gb
available: 9.02 gb
usage: ||||||......... 41.9%
modules
β slot dimm 1 (spd)
π maker: crucial technology
π dram: micron technology
π·οΈ part: bl8g32c16u4bl.m8fe
β±οΈ timings: 19-19-19-43
π¦ size: 8 gb
β‘ speed: 3733 mt/s
π voltage: 1.2 v
β slot dimm 1 (spd)
π maker: crucial technology
π dram: micron technology
π·οΈ part: bl8g32c16u4bl.m8fe
β±οΈ timings: 19-19-19-43
π¦ size: 8 gb
β‘ speed: 3733 mt/s
π voltage: 1.2 v
please note that mfetch displays spd timings, not the active (real-time) timings from your bios.
- what does it mean?: you are seeing the "factory passport" data burned into the ram chip by the manufacturer (crucial, micron, samsung, etc.).
- why not real timings?: active timings (like xmp, docp, or manual overclocking) are stored in the cpu's memory controller. accessing them requires complex, hardware-specific drivers that vary for every cpu generation.
- the result: if you tightened your timings in the bios,
mfetchwill still show the default factory profiles fetched from the spd eeprom.
if the modules section is empty, your system lacks access to the i2c bus. follow these steps:
- load the drivers (for ddr4/ddr5):
sudo modprobe i2c-dev sudo modprobe ee1004
Build from source:
cargo build --releaseOr install via AUR (once package is added):
yay -S mfetch# Requires root privileges to see detailed memory module info
sudo mfetchMIT License. See LICENSE file for details.