Skip to content

Hardware Testing

github-actions[bot] edited this page Nov 15, 2026 · 1 revision

Diagnostic, benchmarking, and reliability stress testing guides and scripts for PC test benches

Part of the ULTIMATE CYBERSECURITY MASTER GUIDE

Hardware Testing Manjaro Intel

๐ŸŽฏ Purpose

Index for hardware testing, diagnostics, and benchmarking tools on Manjaro Linux - covering stress testing, reliability validation, and performance benchmarking for dedicated test bench systems.

โš™๏ธ Function

Indexes the HardwareTesting section: the dedicated Intel test bench setup guide (Manjaro), Python orchestration scripts for automated diagnostic runs, and hardware-specific testing procedures for CPU, memory, storage, and GPU.

๐Ÿ† Goal

Provide a complete reference for hardware qualification testing on Linux, enabling repeatable diagnostics and benchmarks for system validation before production deployment.

๐Ÿ“‹ When To Use

  • Qualifying hardware for a dedicated security lab or test bench system
  • Running reliability stress tests on a new Linux system
  • Diagnosing intermittent hardware failures with structured testing

Overview

Board-level hardware fault diagnosis workflow

Reference fault-isolation sequence for hardware repair and test benches. Perform only measurements and rework within your training, equipment and electrical-safety limits; this is not a required step sequence for every device.

This section contains platform-specific cheat sheets and Python automation scripts for hardware diagnostics, benchmarking, stress testing, and reliability validation on dedicated PC test benches.

While hardware testing is often treated as a general repair or homelab task, it directly applies to cybersecurity work in several important ways. Security labs, forensic workstations, password-cracking rigs, virtualization hosts, local AI systems, network monitoring boxes, and incident-response machines all depend on stable, trusted, and properly matched hardware. A system that is unstable, overheating, misconfigured, underpowered, or using unreliable used parts can create false positives, failed workloads, corrupted data, inaccurate benchmarks, or wasted investigation time.

This process is especially useful for verifying functionality and performance of used, refurbished, repurposed, or donated hardware before trusting it in a work environment, home lab, cybersecurity lab, or production-adjacent role. It helps answer questions such as:

  • Is this CPU, RAM, GPU, SSD, NIC, or motherboard actually stable under load?
  • Is the hardware performing as expected for its generation and specifications?
  • Are there signs of overheating, throttling, failing storage, memory instability, PCIe issues, driver problems, or firmware-related problems?
  • Is this machine appropriate for general operations, virtualization, password hashing, packet capture, local AI, malware analysis, security monitoring, or backup/recovery tasks?
  • Is the hardware worth using, reselling, repairing, upgrading, or retiring?

For cybersecurity specifically, choosing the right hardware for the task matters. A password-cracking system may prioritize GPU performance and cooling. A Security Onion, Zeek, Suricata, or packet-capture box may depend heavily on NIC compatibility, storage throughput, and sustained uptime. A virtualization or malware-analysis host needs stable RAM, CPU virtualization support, disk I/O, and safe isolation. A local AI or log-analysis workstation may need GPU VRAM, system memory, and fast NVMe storage. A forensic workstation needs reliability, data integrity, and predictable behavior more than raw benchmark numbers.

These tests also help establish a baseline of trust before hardware is used for sensitive work. Used systems can have failing drives, unstable memory, outdated firmware, unsupported chipsets, poor thermal performance, or unknown configuration problems. Testing does not magically make hardware โ€œsecure,โ€ but it does reduce uncertainty and helps confirm that the equipment is reliable enough for the role it is being assigned.

Each platform combination, such as Manjaro + Intel or Debian + AMD, gets its own reference document for package management, driver setup, kernel notes, firmware considerations, GPU tooling, sensor support, stress-testing tools, and hardware-specific behavior.

The Python scripts in py/ are Linux-focused and designed to be portable where possible. The orchestration logic is shared across systems, but install commands, driver packages, kernel behavior, GPU tooling, sensor detection, and package availability can vary by distribution and hardware platform. The cheat sheets document those platform-specific differences so the same general testing workflow can be adapted across multiple Linux environments.

The overall goal of this section is to make hardware validation repeatable, practical, and useful for real-world repair work, homelab builds, cybersecurity labs, infrastructure planning, and choosing the best hardware for a specific technical role.


Contents

โœ… Available Now

Platform Cheat Sheet Scripts
Manjaro Linux - Intel CPU Platform (Z790 / 13thโ€“14th Gen i9) Manjaro_Intel_TestBench.md py/

๐Ÿ”œ Planned

Platform Status
Manjaro Linux - AMD CPU Platform (X670 / Ryzen 7000) Planned
Debian - Intel CPU Platform (Z790 / 13thโ€“14th Gen i9) Planned
Debian - AMD CPU Platform (X670 / Ryzen 7000) Planned

Manjaro Linux - Intel โœ…

Reference: Manjaro_Intel_TestBench.md

Covers Z790 motherboards with 13th/14th Gen Core i9 processors running Manjaro Linux. The guide is written for an Intel CPU test bench, but the GPU testing workflow also supports AMD Radeon and NVIDIA GPUs when the correct GPU tools are installed.

Includes:

  • pacman, pamac, and AUR package management for diagnostic tools.
  • Hardware diagnostics and system info with inxi, dmidecode, lscpu, lspci, lsusb, lshw, and hwinfo.
  • Thermal monitoring with lm_sensors / sensors.
  • Intel-focused monitoring notes for tools such as intel-gpu-tools, turbostat, and s-tui where applicable.
  • CPU and system stress testing with stress-ng, sysbench, and optional Prime95 / mprime.
  • Memory and storage diagnostics with memtester, nvme-cli, smartmontools, fio, and optional kdiskmark.
  • Fresh install provisioning one-liners for the test-bench tool stack.
  • Optional Phoronix Test Suite workflows for standardized benchmark runs.
  • Modern GPU testing paths using memtest_vulkan, vkmark, glmark2, vendor telemetry, and kernel PCIe/GPU fault scanning.
  • Python automation scripts that generate client-facing Markdown reports.

Python Scripts - Py/

Modular Python scripts that orchestrate CLI tools, stream output live, and compile results into clean Markdown reports.

Script What it does Sudo
full_hw_suite.py Full sequential diagnostic - system info, CPU, RAM, storage, GPU โœ…
standalone_gpu_tester.py Universal GPU first-pass benchmark - Vulkan/OpenGL validation, VRAM testing, kernel fault scanning โŒ
amd_gpu_tester.py Dedicated AMD Radeon GPU diagnostic with amdgpu telemetry and rigorous load testing โŒ
nvidia_gpu_tester.py Dedicated NVIDIA GPU diagnostic with nvidia-smi telemetry and rigorous load testing โŒ
standalone_ram_tester.py RAM bandwidth and multi-pass stability testing โœ…
stress_soak.py Reliability burn-in - simultaneous CPU/RAM/storage/GPU load with continuous thermal logging โœ…

See py/README.md for full installation instructions, usage, and per-script documentation.

If the vendor-specific GPU scripts are renamed in the repo, keep the table and examples aligned with the actual filenames in py/.


Quick Start

1. Install Base Diagnostics & System Tools

Run this on every Manjaro / Arch-based test bench:

sudo pacman -Syu --needed

sudo pacman -S --needed \
  base-devel git make gcc cmake ninja pkgconf rust cargo \
  python python-pip curl unzip jq \
  inxi dmidecode pciutils usbutils lshw hwinfo \
  lm_sensors smartmontools nvme-cli \
  sysbench memtester stress-ng fio \
  vulkan-tools mesa-utils \
  vkmark glmark2 \
  intel-gpu-tools nvtop

2. Detect Motherboard Sensors

Run once after installing the base tools:

sudo sensors-detect --auto
sensors

Without sensor detection, thermal reporting may be incomplete or empty.


GPU Tooling

Install the GPU block that matches the hardware being tested.

AMD Radeon Test Environments

sudo pacman -S --needed \
  mesa vulkan-radeon \
  amdsmi amdgpu_top radeontop

Useful AMD validation commands:

inxi -G -c0
lspci -nnk | grep -A4 -E "VGA|3D|Display"
vulkaninfo --summary
glxinfo -B
amd-smi list
amd-smi static --gpu 0
amd-smi metric --gpu 0
amdgpu_top --dump

NVIDIA Test Environments

sudo pacman -S --needed \
  nvidia-utils cuda opencl-nvidia

Useful NVIDIA validation commands:

nvidia-smi
nvidia-smi -q
nvcc --version
vulkaninfo --summary
glxinfo -B

Optional GUI / Deep Benchmark Tools

These are useful for manual benchmarking, client demonstrations, or deeper comparative testing. Availability can vary by Manjaro repository/AUR status, so verify with pamac search if any package fails.

pamac build mprime-bin kdiskmark unigine-superposition phoronix-test-suite

If phoronix-test-suite is available from your configured Manjaro repositories, it may also be installed with:

pamac install phoronix-test-suite

Source-built GPU Diagnostic Tools

memtest_vulkan - Cross-vendor Vulkan VRAM Stability Test

memtest_vulkan is used by the GPU scripts for VRAM stability testing. It is useful for AMD, NVIDIA, and Intel GPUs as long as the system exposes a working Vulkan device.

mkdir -p ~/src
cd ~/src

if [ ! -d memtest_vulkan ]; then
  git clone https://github.com/GpuZelenograd/memtest_vulkan.git
fi

cd memtest_vulkan
git pull
cargo build --release
sudo install -m 755 target/release/memtest_vulkan /usr/local/bin/memtest_vulkan

Verify:

command -v memtest_vulkan
memtest_vulkan

Stop the test with Ctrl+C after confirming it starts and detects the correct GPU.

gpu-burn - NVIDIA CUDA Stress Test

gpu-burn is NVIDIA/CUDA-specific. It is only needed for NVIDIA diagnostic runs that use the --gpu-burn option.

mkdir -p ~/src
cd ~/src

if command -v nvcc >/dev/null 2>&1; then
  if [ ! -d gpu-burn ]; then
    git clone https://github.com/wilicc/gpu-burn.git
  fi

  cd gpu-burn
  git pull
  make

  sudo install -m 755 gpu_burn /usr/local/bin/gpu-burn
  sudo ln -sf /usr/local/bin/gpu-burn /usr/local/bin/gpu_burn
else
  echo "nvcc was not found. Skipping gpu-burn build."
  echo "Install/repair CUDA first if this bench needs NVIDIA gpu-burn testing."
fi

Verify:

gpu-burn -l
gpu-burn 60

Verify Required & Optional Tools

Run this after installing the base tools, GPU tools, optional benchmark tools, memtest_vulkan, and gpu-burn.

echo "== Core script tools =="
for bin in \
  python git make gcc cmake ninja cargo rustc \
  inxi dmidecode lspci lsusb lshw hwinfo \
  sysbench memtester fio stress-ng \
  smartctl nvme sensors \
  glmark2 vkmark vulkaninfo glxinfo \
  intel_gpu_top nvtop; do
  printf "%-22s %s\n" "$bin" "$(command -v "$bin" || echo 'โŒ NOT FOUND')"
done

echo
echo "== AMD tools =="
for bin in amd-smi amdgpu_top radeontop; do
  printf "%-22s %s\n" "$bin" "$(command -v "$bin" || echo 'optional / not installed')"
done

echo
echo "== NVIDIA tools =="
for bin in nvidia-smi nvcc gpu-burn gpu_burn; do
  printf "%-22s %s\n" "$bin" "$(command -v "$bin" || echo 'optional / not installed')"
done

echo
echo "== GPU VRAM test =="
for bin in memtest_vulkan; do
  printf "%-22s %s\n" "$bin" "$(command -v "$bin" || echo 'โŒ NOT FOUND')"
done

Run The Scripts

Universal GPU Diagnostic - First Pass

python3 py/standalone_gpu_tester.py --client "Client Name"

Dedicated AMD GPU Diagnostic

python3 py/amd_gpu_tester.py --client "Client Name"

Dedicated NVIDIA GPU Diagnostic

python3 py/nvidia_gpu_tester.py --client "Client Name"

Optional NVIDIA CUDA stress path:

python3 py/nvidia_gpu_tester.py --client "Client Name" --gpu-burn

Full System Diagnostic

sudo python3 py/full_hw_suite.py --client "Client Name"

RAM-only Diagnostic

sudo python3 py/standalone_ram_tester.py --client "Client Name" --memtester-size 4G --passes 3

Reliability Soak Before Returning Hardware To A Client

sudo python3 py/stress_soak.py --mode standard --client "Client Name"

Quick smoke-test soak:

sudo python3 py/stress_soak.py --mode quick --client "Client Name"

Manjaro Linux - AMD CPU Platform ๐Ÿ”œ

Status: Planned

Will cover X670/X670E motherboards with Ryzen 7000 series processors. Key differences from the Intel guide will include:

  • AMD CPU platform monitoring and validation.
  • amd_pstate vs intel_pstate CPU frequency scaling.
  • k10temp / optional zenpower temperature and voltage reporting.
  • Optional Ryzen tuning tools such as ryzenadj, where appropriate.
  • EXPO vs XMP memory profile validation.
  • AMD chipset, IOMMU, and kernel parameter notes.
  • AMD integrated/discrete graphics considerations where relevant.

Debian - Intel CPU Platform ๐Ÿ”œ

Status: Planned

Will cover Z790/i9 hardware running Debian stable. Key differences from the Manjaro guide will include:

  • apt package management.
  • Backports or manual installation for newer kernels, Mesa, Vulkan, and hardware diagnostics.
  • Mesa/OpenGL stack differences affecting glmark2, vkmark, and Vulkan behavior.
  • systemd service configuration for persistent sensor monitoring.
  • Kernel version availability and hardware support timelines.

Debian - AMD CPU Platform ๐Ÿ”œ

Status: Planned

Will cover X670/Ryzen 7000 hardware on Debian stable. It will combine the AMD-specific platform notes and Debian packaging differences from the planned guides above.


Contributing

If adding a new platform guide, follow the naming convention:

Hardware Testing/
โ”œโ”€โ”€ {Distro}_{CPUPlatform}_TestBench.md    # cheat sheet
โ””โ”€โ”€ py/                                    # shared Python scripts

Where {Distro} is Manjaro, Debian, etc. and {CPUPlatform} is Intel, AMD, or another hardware platform label.

Examples:

Manjaro_Intel_TestBench.md
Manjaro_AMD_TestBench.md
Debian_Intel_TestBench.md
Debian_AMD_TestBench.md

โš ๏ธ Security & Legal Disclaimer

Authorized Use Only

These hardware testing guides and scripts are provided for:

โœ… AUTHORIZED USES:
   โ€ข Qualifying hardware you own or have explicit permission to test
   โ€ข Reliability testing for security labs, forensic workstations, and pentest rigs
   โ€ข Benchmarking and stress testing in controlled environments
   โ€ข Supporting authorized security operations and incident response

๐Ÿšซ STRICTLY PROHIBITED:
   โ€ข Running diagnostic or stress tools on hardware you do not own or control
   โ€ข Using hardware-level access techniques without authorization
   โ€ข Any activities violating applicable laws or regulations

Warranty Disclaimer: These guides are provided "AS IS" without warranty of any kind. The authors are not responsible for hardware damage, data loss, or other outcomes from running stress tests, diagnostic tools, or configuration changes on any system.


๐Ÿ“š Resources

Diagnostic & Benchmarking Tools

Manufacturer Tools

Manjaro / Arch References


Related Files


Pacific Northwest Computers ยท pnwcomputers.com ยท Vancouver, WA Last updated: 06-11-2026


๐Ÿ“– Use These Guides Responsibly: Test Only Hardware You Own or Control

Hardware diagnostics and stress testing - use them ethically and with proper authorization.

Repository: ULTIMATE CYBERSECURITY MASTER GUIDE

Maintained by: Pacific Northwest Computers


โš ๏ธ CRITICAL: These are ATTACK TECHNIQUES - Written authorization is REQUIRED โš ๏ธ

โš ๏ธ Unauthorized use is a FEDERAL CRIME with up to 10 years imprisonment โš ๏ธ

โš ๏ธ ALWAYS obtain explicit written authorization before using any technique โš ๏ธ

โญ Star this repo if you find it useful! โญ


๐Ÿ“‘ All Pages in Hardware Testing

Guides & Reference

py


๐Ÿ“‚ Folder: HardwareTesting | โœ๏ธ Suggest an edit | ๐Ÿ—บ๏ธ Browse by Topic

Clone this wiki locally