SRS 2.5.0 - The Big Top, live tray meters and an IR Blaster

SRS 2.5.0 - The Big Top, live tray meters and an IR Blaster

An update to SRS 2.4. Everything from 2.4 is still there, and your settings, tabs and lineups carry
over. 2.4.1 was never released on its own; its changes (benchmark times up to 60 s, a Cache & Memory
fix) are part of this release.

What's new

• The Big Top (Ctrl+G, or the button next to the search box): a live window for the whole PC
  and each graphics card.
  • Its Performance tab works like a task manager:
    • Summary and Performance: live meters and graphs for the CPU, memory, CPU power,
      temperatures, every disk, network adapter and GPU.
    • Processes: End Task, Force Kill, End Process Tree, Suspend / Resume, Priority, CPU
      Affinity and Properties. It always asks first, never touches PID 1 or kernel threads, and asks
      for a password (polkit) before acting on another user's process. A zombie process is explained
      in plain words, with End Parent Process.
    • Startup Apps: everything that starts at login, one-click on / off, Add, Remove to a
      trash you can restore from, Restore Default, and an Undo that survives a restart. It never
      writes to /etc.
    • Users (sessions, Disconnect), Services (Start / Stop / Restart, asks first) and
      Run New Task.
  • Its GPU tabs are a C reimplementation of amdgpu_top by Umio Yasuno (MIT) for AMD cards,
    with NVIDIA cards through NVML. They show busy engines, video memory, which programs use the
    card, clocks, power, temperatures, every gpu_metrics field, an SMI table of all cards, the
    display connectors, the PowerPlay table and the XDNA NPU.
  • Everything in the GPU tabs is read-only.
  • A card that can sleep is left asleep while it is idle.
  • The GRBM performance counters are off by default; turn them on when you need the GRBM panels.
  • The window starts on the first awake card and wakes a sleeping one only when you pick it.
  • On the command line: sysreport-search gpu-top (or big-top). It reads the GRBM counters only
    with --pc, and opens a sleeping card only with --device N --wake.
• Live tray meters, off by default. CPU, cores, CPU temperature, memory, GPU busy /
  temperature / video memory, disk and network can each be their own updating icon in the
  notification area, even while SRS is hidden.
  • Turn them on in Menu -> Options -> Customize Task Manager (Performance tab, tray meters)... ->
    Live Telemetry Icons.
  • The same dialog sets the update speed, keep running in the tray, start minimised at login and a
    summon shortcut.
  • The SRS icons stay together, in the order of the settings. Tray Position puts them with the
    hardware icons (Normal) or first in the tray. The desktop still decides the final order.
  • On Plasma, if they hide under the tray arrow: right-click the arrow > Configure System Tray >
    Entries > Always shown.
  • srs-gui --tray starts with only the tray icons.
• IR Blaster (USB & PCI devices page; sysreport-search ir): use an ELK Smart / OCRUSTAR USB
  infrared dongle as a remote control.
  • Learn a button from your TV remote, name it, and send it again (with Repeat, or Dry Run to see
    the USB packets only).
  • Type in a code, and import or export your codes.
  • The codes are shared with the IR Remote app.
  • The tab is greyed while no dongle is plugged in, and shows the udev rule (with a Copy Install
    Command button) when access is missing.
• One startup manager. Operating system -> Startup programs -> Manage now opens Startup Apps.
  The old 2.2 Startup manager is gone; Startup Apps has its Restore Default, and its Restore Removed
  brings back the copies the old manager saved.
• All Cores (Max) (Alt+X) beside Threads on the CPU benchmarks and on Stress & Burnin: every
  logical CPU for one run, without changing a saved setting. On Crypto, CPU Compute and Everyday Work it runs only
  the all-threads pass (the 1-thread cells say "skipped"; about half the time). Command line: --all-threads-only.
• Benchmark times up to 60 s on every benchmark, in the window and on the command line.
• One load at a time. While a benchmark or Stress & Burnin runs, the other pages' Run / Start buttons are greyed
  (the tooltip names the running test); a lock file also warns when another SRS window or sysreport-search is running one.
• Stop on every benchmark page (CPU Benchmark, IPI Delay, Latency and Crypto too) and Run All on Everyday Work and
  the GPU Compute comparison.
• Cache & Memory fix. With kernel same-page merging (KSM) switched on for every program, long
  runs could show impossible memory speeds (over 1,000,000 MB/s). SRS now keeps its benchmark
  memory out of merging before every test. A result faster than the installed memory can deliver
  shows as not valid in red.
• The ten "Benchmark: mode" tabs are gone from the window. The CPU Benchmarks tab's Mode list runs
  the same modes and shows their last results.
• The tray menu's Exit is now Quit SRS.
• Fixes from the pre-release reviews: the benchmark lock never lives in /tmp; stopped Crypto and CPU
  Benchmark runs mark what they did not measure; a reused process number is never mistaken for the
  old process; IR Blaster finds the udev rule in /etc too and says when the dongle is busy; per-process
  GPU use on more drivers; Alt letters that no longer clash.

Full list in CHANGELOG.md.

Tested on one PC (and what that means)

Tested on one PC (Ryzen 7 7800X3D, RX 9070 XT, ASUS X870, KDE Plasma 6 Wayland). I've done
everything I can for the rest: tests on recorded data, fake devices and stand-in libraries,
careful reading of the docs, and test builds. But I can't try what I don't own. These parts were
not tried on real hardware and may have a bug or two I haven't met yet:

• NVIDIA graphics cards (only a stand-in for NVIDIA's library) and Intel GPUs
• other AMD generations (the RX 5000 / 6000 / 7000 PowerPlay tables), APUs (processors with
  built-in graphics), and NPUs (Ryzen AI / XDNA)
• several graphics cards in one PC, laptops and hybrid graphics
• other desktops' trays (GNOME with the AppIndicator extension, XFCE, waybar ...) and the summon
  shortcut
• HiDPI screens and panels
• other IR dongle models: only one OCRUSTAR / ELKSMART 045c:0132 (plain protocol) was used, with
  one TV, where status, probe, send, repeat and learn all worked. The 045c:0184, 045c:0195 and
  045c:0134 models are untested.
• the password (pkexec) path of the process actions, other users' processes, Disconnect, and
  Start / Stop / Restart of system services

If you find a bug, please tell me: open an issue on
GitHub with your hardware and the
report SRS made, and I'll fix it.

Upgrading from 2.4.x

Install the new package over the old one; nothing has to be set up again. For the IR Blaster,
install the udev rule (the tab's Copy Install Command, or the elksmart-comm-git package or
IR Remote), then unplug and replug the dongle.

SRS is Copyright (C) 2026 by Eugene Flanagin. Licensed under GPL-2.0-or-later.

SIV is the work of Ray Hinchliffe, RH Software (https://rh-software.com).

Credits: CREDITS.md lists every library and the public data. New in 2.5:

• The Big Top's GPU view reimplements amdgpu_top and the parts of libdrm_amdgpu_sys it uses, both
  by Umio Yasuno (MIT, https://github.com/Umio-Yasuno/amdgpu_top).
• The gpu_metrics and PowerPlay table layouts come from the Linux kernel's AMD headers (MIT).
  libdrm and NVIDIA's NVML are loaded at run time when present and are never shipped.
• The Performance tab's layout is inspired by classic task-manager designs; its code and drawing
  are SRS's own.
• IR Blaster's dongle protocol is a port of elksmart-comm by Přemysl Eric Janouch (janouch)
  (0BSD, https://git.janouch.name/p/usb-drivers). Its codes file, wording and udev rule follow IR
  Remote (MIT, https://github.com/eugenesflanagin-spec/irremote).

SRS 2.4.0 - Memory Timings, a much harder GPU Burnin, stop limits up to 110 C

SRS 2.4.0 - Memory Timings, a much harder GPU Burnin, stop limits up to 110 C

An update to SRS 2.3. Everything from 2.3 is still there, and settings, tabs and lineups carry over.

What's new

• Memory Timings: the live DDR5 timings. On AMD Ryzen 7000 / 9000 desktop processors the
  Memory page's Memory Timings tab now shows what the memory really runs at: every timing of
  each channel (CL, tRCD, tRP, tRAS, tRC, the refresh timings and about 30 more, each with a short
  meaning and the time in nanoseconds), the memory, controller and fabric clocks (MEMCLK, UCLK,
  FCLK and their ratio), the SoC voltages, and the controller settings (Gear Down Mode, command
  rate, power down ...). It needs the ryzen_smu driver (AUR ryzen_smu-dkms-git) and one
  Run as root; everything is only read. For every DDR5 module, without root: maker, part
  number, size, DRAM maker, date, temperature and its JEDEC, EXPO and XMP profiles - so you can
  see the profile next to what the BIOS set.
  • BIOS memory settings (ProcODT, drive strengths, RTT values, the DIMM voltages the BIOS set)
    come from the BIOS's AMD AOD table when the kernel allows reading it (see below).
  • DIMM voltages from the modules' own power chips (PMIC) are an opt-in under Options,
    off by default, and ask first.
  • Intel Core 6th gen to Core Ultra: live speed and CL-RCD-RP-RAS, experimental.
• GPU Burnin loads the graphics card much harder. A faster matrix multiply on all four back
  ends (Vulkan, ROCm / HIP, CUDA / ZLUDA, OpenCL). On my Radeon RX 9070 XT, FP32, 0 errors on every
  back end: CUDA via ZLUDA 5.3 -> 17.2 TFLOPS, Vulkan 6.2 -> 16.2, OpenCL 3.4 -> 13.4 and
  ROCm / HIP 3.4 -> 13.0. The card draws more power and gets hotter, as a burn-in should. The GPU Compute
  comparison keeps the old kernel, so its numbers stay comparable. The live readout no longer
  shows 0.0 multiplications per second.
• Stop limits up to 110 C. The CPU and GPU stop limits of Stress & Burnin now go up to 110 C.
  Over 100 C, SRS asks once whether you accept the risk (No puts both back to 100). The CPU limit
  is remembered, and the folded GPU options line now shows the GPU's own limit, so it is never
  hidden. Command line: --accept-high-limit for burn and gpu-burn.
• Pages that said "not read" now show their data: System CMOS (no root needed any more),
  System EBDA, the GPU's VBIOS image (from the driver's own copy: signature, checksum, images, part
  number), the GPIO pin states, the factory core ranking on AMD Fuses (no root needed), package and
  per-core power from the RAPL counters on MSR Setup (with a plain-English legend on MSRs), and the
  UEFI System Table and firmware-update (ESRT) details on Firmware.
• Update hardware lists (Tools page, or sysreport-search update-lists): fetches the newest
  PCI, USB and monitor maker name lists from their official sources, only when you ask, into your
  own folder. SRS then uses whichever copy is newer, yours or the system's.
• ACPI method evaluation, for experts (Tools page): run one ACPI method of your BIOS as root
  through the acpi_call module and see its result. Off until you accept a warning once; every
  call is logged.
• Read the embedded controller (Options, off by default, asks first): a read-only copy of the
  EC's 256 registers on the ACPI Embedded Controller page.
• Fixes: the Power & Cost estimates note no longer opens taller than the screen; the OpenCL page
  works with both kinds of clinfo; Redact Reports also masks hexdump lines in copied text; the
  CPU flags are wrapped and the GPIO table lines up.

Full list in CHANGELOG.md.

Tested on one PC (and what that means)

I build and test SRS on a single machine: a Ryzen 7 7800X3D with a Radeon RX 9070 XT, on a wired
connection. I've done everything I can for the rest (checks that don't need the hardware, careful
reading of the docs, test builds), but I can't try what I don't own. So anything that needs other
hardware, such as NVIDIA CUDA, Intel graphics, ROCm/HIP or OpenCL setups other than mine, Wi-Fi or
VPN network tests, or ARM and 32-bit builds, may have a bug or two I haven't met yet. If you find
one, please tell me: open an issue on
GitHub with your hardware and the
report SRS made, and I'll fix it.

What this means for 2.4 in particular:

• Intel memory timings are EXPERIMENTAL and untested on real Intel hardware. I have no Intel
  PC; the decoding was checked with made-up register values only. If you have an Intel Core
  6th gen to Core Ultra PC, please compare the Memory Timings page with your BIOS and report what
  you see, right or wrong.
• AMD memory timings were checked on one Ryzen 7 7800X3D with DDR5-6000 EXPO. The Ryzen 9000
  PM table layout (which gives the clocks and SoC voltages) is not checked, so some of those rows
  may be missing or wrong there. Other AMD processors say "not supported yet".
• The BIOS memory settings (AOD table) sit in memory that most Linux kernels keep from programs
  (kernels built with IO_STRICT_DEVMEM). Reading them needs the kernel option iomem=relaxed,
  which weakens that protection. SRS never asks you to change it; without it the page says why
  that part is missing, and everything else works. The table's layout was checked on one BIOS and
  is only shown when its timings match the live ones.
• ACPI method evaluation can change hardware state. A method can switch devices on or off,
  change fan, power or performance settings, write BIOS settings, or hang or reboot the PC. It is
  for experts who know which method they run; the authors are not responsible for any damage.
• The PMIC and embedded controller opt-ins were not checked on real hardware yet, and the EBDA dump
  was not either (my UEFI PC has none).
• GPU Burnin's new kernel ran on my real card with all four back ends (AMD only: NVIDIA's own CUDA
  driver was not tried). A stronger load also finds a shaky overclock sooner: during testing my
  own memory-fabric overclock (FCLK) reset the PC under this load and had to go back down.

Upgrading from 2.3.x

Install the new package over the old one; nothing has to be set up again. Run Menu -> Run as
root once to collect the new root data (memory timings, VBIOS image, GPIO pins, RAPL power,
EBDA, UEFI tables). For the AMD live timings install the ryzen_smu driver first; for ACPI method
evaluation the acpi_call module.

SRS is Copyright (C) 2026 by Eugene Flanagin. Licensed under the GNU General Public License v2.0 or later.

SIV is the work of Ray Hinchliffe, RH Software (https://rh-software.com).

Credits: CREDITS.md lists every library and the public data. New in 2.4: the AMD
memory controller, SPD and AOD layouts follow ZenStates-Core / ZenTimings by Ivan Rusanov, and
the AMD and Intel memory controller layouts memtest86+ by Sam Demeulemeester and contributors
(facts only, no code copied). The live AMD values are read through the ryzen_smu driver (leogx9r,
amkillam fork) and ACPI methods are evaluated through the acpi_call module; neither is shipped.
Update hardware lists downloads from the PCI ID Repository (pci-ids.ucw.cz), the Linux USB ID list
(linux-usb.org) and hwdata's pnp.ids. ROCm, CUDA (or ZLUDA), OpenCL drivers and CLBlast are the
system's own, loaded at run time when installed, never shipped.

SRS 2.3.1 - One Stress & Burnin for CPU and GPU, tools as tabs, columns that line up

SRS 2.3.1 - One Stress & Burnin for CPU and GPU, tools as tabs, columns that line up

An update to SRS 2.3. Everything from 2.3 is still there, and settings, tabs and lineups carry over.

What's new

• Stress & Burnin: the CPU and the graphics card in one place. CPU Burnin, CPU Stress and GPU
  Burnin are now one window (a tab in the new main window). Tick CPU load and choose Timed
  (burn and cool cycles, Pass or Fail) or Until Stop; tick GPU Burnin to load the graphics
  card at the same time, for its own Time or with Sync to CPU stress time. The GPU's back end,
  card, precision and temperature limit sit under a folded GPU options. Untick CPU load to test
  only the GPU. Your own GPU stress program still works as Custom GPU command. The GPU part runs
  as its own small process, so a GPU driver that hangs cannot freeze SRS, and Stop always works.
• Every tool is a tab. In the new main window the Benchmarks & Stress page shows each tool as a
  tab with its controls and live results in the page - no more pop-up windows - and compact sections
  at the top to jump to them. Leaving a test that is still running asks whether to stop it. Classic
  View keeps the separate windows.
• Use at your own risk. Stress tests and benchmarks push the PC to its limits. The first time you
  start one, SRS shows plain-English terms (provided as is, without warranty; save your work first)
  with I Agree / I Disagree; nothing starts until you agree. Options -> Load test terms
  (warranty)... shows them again. On the command line, --yes counts as agreeing.
• Columns line up on every page. Each column is as wide as its longest entry, so long device names
  no longer push the next columns out of line (PCI bus, PnP Manager, USB, Processes and more). Very long
  entries end in "..." - hover for the full text; Copy always gives it in full.
• NUMA memory speed can run the memory latency test right on its page; MSR Setup now explains
  the CPU registers SRS read (P-state clocks, boost, SVM, CPPC ranking) in plain English.
• The mouse wheel over a side tab list moves to the tab above or below. The first time the close button
  only hides SRS to the tray, it says so and how to quit. Page names are capitalised: Benchmarks &
  Stress, Power & Cost, Graphics & Audio.

Tested on one PC (and what that means)

I build and test SRS on a single machine: a Ryzen 7 7800X3D with a Radeon RX 9070 XT, on a wired
connection. I've done everything I can for the rest (checks that don't need the hardware, careful
reading of the docs, test builds), but I can't try what I don't own. So anything that needs other
hardware, such as NVIDIA CUDA, Intel graphics, ROCm/HIP or OpenCL setups other than mine, Wi-Fi or
VPN network tests, or ARM and 32-bit builds, may have a bug or two I haven't met yet. If you find
one, please tell me: open an issue on
GitHub with your hardware and the
report SRS made, and I'll fix it.

What this means for 2.3.1 in particular: the built-in GPU Burnin inside Stress & Burnin was tested on
Mesa's software renderer (lavapipe), not on a real graphics card; the custom GPU command path was run
on the author's card together with a CPU Burnin and passed. The MSR decoding was checked on one AMD
Zen 4 CPU only.

Upgrading from 2.3.0

Install the new package over the old one; nothing has to be set up again. The first stress test or
benchmark you start asks you to agree to the load test terms once.

SRS is Copyright (C) 2026 by Eugene Flanagin. Licensed under GPL-2.0-or-later.

SIV is the work of Ray Hinchliffe, RH Software (https://rh-software.com).

Credits: CREDITS.md lists every library and the public data. ROCm, CUDA (or ZLUDA),
OpenCL drivers and CLBlast are the system's own, loaded at run time when installed, never shipped.

SRS 2.3.0 - CUDA without the NVIDIA toolkit, clearer OpenCL FP64, an explained CUDA toolkit option

SRS 2.3.0 - CUDA without the NVIDIA toolkit, clearer OpenCL FP64, an explained CUDA toolkit option

An update to SRS 2.2 for the GPU tests. Everything from 2.2 is still there, and settings, tabs and
lineups carry over.

What's new

• CUDA works without the NVIDIA runtime compiler. SRS's own small GPU test programs (the
  "kernels") now come pre-built inside SRS, as PTX - NVIDIA's portable GPU code, which the graphics
  driver (or ZLUDA) finishes for your card when a test starts. Before, SRS needed NVIDIA's runtime
  compiler (NVRTC, libnvrtc) to build them, and ZLUDA does not have one, so every CUDA (ZLUDA) row
  said "not available". Now GPU Burnin and every CUDA row of the GPU Compute comparison, including
  the cuBLAS rows, run without it. The kernels are exactly the ones NVRTC builds (same source,
  names and parameters); NVRTC is only used if a driver refuses the pre-built ones. They are made
  with clang for PTX ISA 6.0 / sm_50, which current NVIDIA drivers (CUDA 9 and newer) accept and
  compile on to any newer card.
• OpenCL FP64 is clearer. On OpenCL drivers without double precision (often Mesa's Rusticl)
  the FP64 rows said "failed" with an empty reason. They now say "not available: this OpenCL
  driver has no FP64 (double precision)", the CLBlast FP64 row too, and a kernel that does not
  build always shows the OpenCL error code.
• The NVIDIA CUDA toolkit, explained and optional. The NVIDIA CUDA toolkit is NVIDIA's free set
  of developer tools for running programs on NVIDIA graphics cards. SRS only needs one small part
  of it, the runtime compiler (NVRTC), and since 2.3 only as a fallback, so most people do not
  need it. When it is missing and it could matter (an NVIDIA card or a CUDA library is there), SRS
  asks once, the first time you run a CUDA test: Install..., Not now or Don't ask
  again. If you skip it, you can install it later from Options -> NVIDIA CUDA toolkit for GPU
  tests... (or sysreport-search cuda-toolkit --install). SRS shows the exact command first
  (Arch: sudo pacman -S --needed cuda, about 2.4 GB to download; Debian / Ubuntu: sudo apt-get install libnvrtc12 or libnvrtc11.2, about 20 MB; Fedora, openSUSE: instructions for NVIDIA's
  repository), runs it in a terminal window only after you confirm, and tells you how it went. It
  will not start while a benchmark or burn-in runs, while another update holds the package
  database, or without a network connection. The package manager, sudo and pkexec are only
  taken from /usr/bin, /usr/sbin, /bin or /sbin and run by their full path: a program of
  the same name in your own folders (for example ~/.local/bin) is never run as administrator.
  Without a terminal program it uses pkexec and the package manager's "no questions" switch;
  pacman's --noconfirm then answers its questions with the defaults, which means no to
  removing a conflicting package (the install stops instead). With ZLUDA, pkexec is never used.
• The CUDA and HIP columns' "software" line now says whether the own kernels are built in or need
  the runtime compiler.

ZLUDA users (AMD cards): do not install the NVIDIA CUDA toolkit. It can break or remove
ZLUDA: on Arch the cuda package puts NVIDIA's own cuBLAS on the library path, where it can take
the place of ZLUDA's, and anything that brings NVIDIA's driver libraries (nvidia-utils) removes
ZLUDA, which conflicts with them. SRS 2.3's built-in CUDA tests already work with ZLUDA. SRS warns
about this in red, makes Cancel the default and asks twice before it installs anything.

Full list in CHANGELOG.md.

Tested on the real card (2026-10-29): with ZLUDA (preview build, no NVRTC) on the Radeon RX 9070 XT,
every CUDA row of the GPU Compute comparison ran from the built-in kernels - own-kernel FP32 matrix multiply 5377 GFLOPS, cuBLAS FP32 16392, cuBLAS FP16 77046, own-kernel FP64 860 GFLOPS. ZLUDA's cuBLAS has no FP64
matrix multiply (it answers "not supported", error 15), so that one row says "not available". GPU
Burnin with the CUDA back end was not run on the real card.

Tested on one PC (and what that means)

I build and test SRS on a single machine: a Ryzen 7 7800X3D with a Radeon RX 9070 XT, on a wired
connection. I've done everything I can for the rest (checks that don't need the hardware, careful
reading of the docs, test builds), but I can't try what I don't own. So anything that needs other
hardware, such as NVIDIA CUDA, Intel graphics, ROCm/HIP or OpenCL setups other than mine, Wi-Fi or
VPN network tests, or ARM and 32-bit builds, may have a bug or two I haven't met yet. If you find
one, please tell me: open an issue on
GitHub with your hardware and the
report SRS made, and I'll fix it.

What this means for 2.3 in particular:

• The built-in CUDA kernels were checked without a GPU (their PTX text against the kernel
  source: names, order, parameter types, nothing outside called; and against a fake CUDA driver in
  the automatic tests), and then run through ZLUDA on my AMD RX 9070 XT in the GPU Compute
  comparison (above). They were never run on NVIDIA hardware: "PTX ISA 6.0 / sm_50" is what
  NVIDIA's drivers compile on for the card, not something the toolkit version decides. If your
  NVIDIA driver (or another ZLUDA version) refuses them, SRS falls back to NVRTC when it is
  installed, and tells you so when it is not - please report it with your driver version.
• GPU Burnin with CUDA (built-in kernels) ran only against the fake driver; not on the real
  card, neither through ZLUDA nor on NVIDIA.
• The NVIDIA CUDA toolkit install was tested with fake package managers only (nothing was
  installed); the Debian package names come from Debian's package archive, Ubuntu's are inferred
  from the versions of its nvidia-cuda-toolkit source (SRS asks apt which one exists before it
  offers one), and Fedora and openSUSE get instructions only.
• The OpenCL FP64 check was tested against a fake OpenCL driver, not on Rusticl itself.
• Everything else as in 2.2: the Vulkan tests, GPU Burnin and the GPU Compute comparison were run
  only on lavapipe (the Mesa software renderer); ROCm/HIP, NVIDIA CUDA and OpenCL only as far as
  loading their libraries and the fake-runtime tests (CUDA through ZLUDA: the GPU Compute
  comparison, above). Not run on real hardware: Vulkan on a real GPU, GPU Burnin on a real GPU (any
  back end, CUDA through ZLUDA included), CUDA on NVIDIA, ROCm/HIP on AMD, OpenCL on AMD (ROCm) and
  Mesa Rusticl, anything on Intel graphics, and the NVIDIA and Intel sensor read-outs. ARM (aarch64)
  and 32-bit (i686) builds: compile-checked only.

Downloads

File	For
srs-sysinfo-2.3.0-1-x86_64.pkg.tar.zst	Arch Linux and Arch-based distros (same as the AUR package, prebuilt)
srs-sysinfo_2.3.0-1.deb13_amd64.deb	Debian 13 (trixie)
srs-sysinfo_2.3.0-1.ubuntu24.04_amd64.deb	Ubuntu 24.04 LTS (and derivatives such as Mint 22)
srs-sysinfo-2.3.0-1.fc44.x86_64.rpm	Fedora 44
srs-sysinfo-2.3.0-1.tw.x86_64.rpm	openSUSE Tumbleweed
srs-sysinfo-2.3.0-linux-x86_64.tar.gz	Any other distribution (run in place or copy to /usr/local)
srs-sysinfo-2.3.0-x86_64.AppImage	Any distribution from about 2022 on (glibc 2.35+): one file, nothing to install, can update itself
srs-sysinfo-2.3.0-x86_64.AppImage.zsync	Used by AppImageUpdate to update the AppImage; you do not need to download it
SRS-User-Guide.pdf	The user guide on its own
SHA256SUMS	checksums

Each package was built and install-tested in a clean container for its distro (the AppImage was
started in clean Debian 12 and Fedora 44 containers), for generic x86-64 (no CPU-specific
instructions), so they run on any 64-bit Intel or AMD PC.

Install

Arch Linux

sudo pacman -U srs-sysinfo-2.3.0-1-x86_64.pkg.tar.zst
# or from the AUR:  yay -S srs-sysinfo

Debian / Ubuntu

sudo apt install ./srs-sysinfo_2.3.0-1.deb13_amd64.deb        # or the .ubuntu24.04 file

Fedora / openSUSE

sudo dnf install ./srs-sysinfo-2.3.0-1.fc44.x86_64.rpm
sudo zypper install ./srs-sysinfo-2.3.0-1.tw.x86_64.rpm

Any other distribution

tar xf srs-sysinfo-2.3.0-linux-x86_64.tar.gz
cd srs-sysinfo-2.3.0-linux-x86_64
./usr/bin/srs-gui                     # run in place, or install:
sudo cp -r usr/bin usr/share /usr/local/

INSTALL.txt in the tarball covers the optional boot-time service and uninstalling.

AppImage (any distribution)

chmod +x srs-sysinfo-2.3.0-x86_64.AppImage
./srs-sysinfo-2.3.0-x86_64.AppImage

With arguments it is the command line (--version, find ..., srs-sysreport). Run as root
works from it; the boot-time refresh needs the package for your distro. AppImageUpdate (or a
manager that uses it, such as AppImageLauncher) keeps it up to date.

Requirements

• 64-bit x86 Linux. Use the package for your distro; the generic linux-x86_64.tar.gz is built from the
  Ubuntu 24.04 package and needs glibc 2.38 or newer (check with ldd --version)
• GTK 3, GLib, Pango, Cairo, SQLite 3 (for Power & cost), and hwdata
• Optional, for more detail: polkit (for srs-root), dmidecode, smartmontools, nvme-cli, i2c-tools,
  pciutils, usbutils, lm-sensors, vulkan-tools, clinfo, mesa-utils, libayatana-appindicator (tray icon);
  zlib, zstd, lz4 and xz (liblzma) for the Everyday Work benchmark's compression rows (almost every
  system has them); libcurl for the Network benchmark's internet speed test; the Vulkan loader and
  your GPU's Vulkan driver for the GPU benchmarks; ROCm (HIP), CUDA (the NVIDIA driver, or ZLUDA)
  or an OpenCL driver (with CLBlast) only if you want those back ends in GPU Burnin and the GPU
  Compute comparison. The NVIDIA CUDA toolkit is not needed (see above)
• For guide links at the exact page: Okular, Evin...

SRS 2.2.2 - fix for a crash in GPU Comparison and GPU Burnin

SRS 2.2.2 - fix for a crash in GPU Comparison and GPU Burnin

A small update to SRS 2.2 with one fix, found by a user who ran the GPU Comparison with CUDA on
an AMD card through ZLUDA. Nothing else changes: everything from 2.2 is still there, and settings,
tabs and lineups carry over.

What's fixed

• GPU Comparison and GPU Burnin could crash (the program ended with a segmentation fault) when
  the vendor GEMM library (hipBLAS or cuBLAS) was measured before SRS's own kernels had been
  loaded. The library test checks every result with one of SRS's own small kernels, and that
  kernel was only loaded for the own-kernel test; when the own-kernel test did not run first or
  failed, the library test handed the GPU driver an empty kernel and the driver crashed. The
  kernels are now always loaded first, and SRS refuses to start a kernel that is not loaded, with
  a message instead of a crash.
• Without the runtime compiler (libnvrtc for CUDA, libhiprtc for ROCm / HIP) the library test
  now says "needs the runtime compiler (...) for the error check, and it is not installed", in the
  GPU Comparison result and in GPU Burnin, instead of failing in a confusing way.
• GPU Comparison now says why a test is "not available" (for example that FP16 is measured through
  the GEMM library only) in the notes under the table.

Full list in CHANGELOG.md; CREDITS.md lists the public data and the credits.

Tested on one PC (and what that means)

I build and test SRS on a single machine: a Ryzen 7 7800X3D with a Radeon RX 9070 XT, on a wired
connection. I've done everything I can for the rest (checks that don't need the hardware, careful
reading of the docs, test builds), but I can't try what I don't own. So anything that needs other
hardware, such as NVIDIA CUDA (and ZLUDA), Intel graphics, ROCm/HIP or OpenCL setups other than
mine, Wi-Fi or VPN network tests, or ARM and 32-bit builds, may have a bug or two I haven't met yet. If you find one, please tell me: open an issue on
GitHub with your hardware and the
report SRS made, and I'll fix it.

Not tried on real hardware so far:

• GPU benchmarks: the Vulkan tests, GPU Burnin and the GPU Compute comparison were run only on
  lavapipe (the Mesa software renderer, which runs on the CPU), with small sizes, so the logic, the
  error counting, Stop and the result pages are checked; the Vulkan type layouts were checked
  against the official Khronos header for 64-bit and 32-bit builds. ROCm/HIP, CUDA and OpenCL were
  tried only in part: the libraries load and every function SRS needs is found in them (on my own
  ROCm, my ZLUDA and my OpenCL loader too), and a missing library or an OpenCL loader with no
  driver is handled cleanly, but no HIP, CUDA or OpenCL work was run on a GPU (since 2.2.2 the HIP and CUDA code paths are also run in an automatic test against a fake GPU runtime, which checks the logic, not the speed or a real driver). Not run on real
  hardware: Vulkan on a real GPU, GPU Burnin on a real GPU, CUDA on NVIDIA, ZLUDA, ROCm/HIP on AMD,
  OpenCL on AMD (ROCm) and Mesa Rusticl, anything on Intel graphics, and the temperature, power,
  clock and fan read-outs for NVIDIA and Intel.
• ARM (aarch64) and 32-bit (i686) builds: compile-checked only.
• OS Latency: run only with the scx_lavd scheduler; BORE, EEVDF and CFS are recognised but were
  not run here.
• CPU Compute: the AVX-512 code has only run on a Zen 4 CPU; the SSE2 and AVX2 code was checked by
  forcing it on that same CPU, not on older CPUs.
• Everyday Work: run with the compression libraries of one Arch Linux system; other versions
  should work but give different speeds.
• Network: run on one wired Ethernet connection only; Wi-Fi, VPN and metered or mobile
  connections are untested. The internet speed test was run once on that connection, against
  Cloudflare, with sensible results (download several hundred Mbit/s, upload about 60 Mbit/s), and
  the report showed no IP address, host name or MAC address.

Things to know about the GPU tests

• A back end that is not installed shows as "not installed" with a one-line hint (for example
  "install ROCm"); the others still run.
• If your CUDA library is really ZLUDA (CUDA calls translated to an AMD GPU), the column is
  labelled "CUDA (ZLUDA)".
• Every OpenCL driver is its own column, for example "OpenCL (ROCm)" and "OpenCL (Rusticl)" on the
  same GPU; CPU drivers (PoCL) are marked CPU.
• Speeds are only comparable between alike SRS builds and the same GPU driver / runtime versions.
• GPU Burnin ends by itself on a driver error, a GPU that stops answering, a piece of work that
  takes far too long, or a temperature at the limit (default 100 °C). It never changes clocks,
  voltages or fans. It asks before it starts. It never burns a software renderer (such as
  llvmpipe) as if it were a GPU, and when a card reports no temperature to SRS the result says that
  the temperature limit was not active.
• Opening a GPU window's list of GPUs, or pressing Run, reads the list of GPUs through Vulkan, the
  way vulkaninfo does: the GPUs are named, no work is sent to them until you answer Yes. ROCm /
  HIP, CUDA and OpenCL are started only after Yes (in GPU Burnin the GPU you picked is found in
  their own list by its PCI address).

Downloads

File	For
srs-sysinfo-2.2.2-1-x86_64.pkg.tar.zst	Arch Linux and Arch-based distros (same as the AUR package, prebuilt)
srs-sysinfo_2.2.2-1.deb13_amd64.deb	Debian 13 (trixie)
srs-sysinfo_2.2.2-1.ubuntu24.04_amd64.deb	Ubuntu 24.04 LTS (and derivatives such as Mint 22)
srs-sysinfo-2.2.2-1.fc44.x86_64.rpm	Fedora 44
srs-sysinfo-2.2.2-1.tw.x86_64.rpm	openSUSE Tumbleweed
srs-sysinfo-2.2.2-linux-x86_64.tar.gz	Any other distribution (run in place or copy to /usr/local)
srs-sysinfo-2.2.2-x86_64.AppImage	Any distribution from about 2022 on (glibc 2.35+): one file, nothing to install, can update itself
srs-sysinfo-2.2.2-x86_64.AppImage.zsync	Used by AppImageUpdate to update the AppImage; you do not need to download it
SRS-User-Guide.pdf	The user guide on its own
SHA256SUMS	checksums

Each package was built and install-tested in a clean container for its distro (the AppImage was
started in clean Debian 12 and Fedora 44 containers), for generic x86-64 (no CPU-specific
instructions), so they run on any 64-bit Intel or AMD PC.

Install

Arch Linux

sudo pacman -U srs-sysinfo-2.2.2-1-x86_64.pkg.tar.zst
# or from the AUR:  yay -S srs-sysinfo

Debian / Ubuntu

sudo apt install ./srs-sysinfo_2.2.2-1.deb13_amd64.deb        # or the .ubuntu24.04 file

Fedora / openSUSE

sudo dnf install ./srs-sysinfo-2.2.2-1.fc44.x86_64.rpm
sudo zypper install ./srs-sysinfo-2.2.2-1.tw.x86_64.rpm

Any other distribution

tar xf srs-sysinfo-2.2.2-linux-x86_64.tar.gz
cd srs-sysinfo-2.2.2-linux-x86_64
./usr/bin/srs-gui                     # run in place, or install:
sudo cp -r usr/bin usr/share /usr/local/

INSTALL.txt in the tarball covers the optional boot-time service and uninstalling.

AppImage (any distribution)

chmod +x srs-sysinfo-2.2.2-x86_64.AppImage
./srs-sysinfo-2.2.2-x86_64.AppImage

With arguments it is the command line (--version, find ..., srs-sysreport). Run as root
works from it; the boot-time refresh needs the package for your distro. AppImageUpdate (or a
manager that uses it, such as AppImageLauncher) keeps it up to date.

Requirements

• 64-bit x86 Linux. Use the package for your distro; the generic linux-x86_64.tar.gz is built from the
  Ubuntu 24.04 package and needs glibc 2.38 or newer (check with ldd --version)
• GTK 3, GLib, Pango, Cairo, SQLite 3 (for Power & cost), and hwdata
• Optional, for more detail: polkit (for srs-root), dmidecode, smartmontools, nvme-cli, i2c-tools,
  pciutils, usbutils, lm-sensors, vulkan-tools, clinfo, mesa-utils, libayatana-appindicator (tray icon);
  zlib, zstd, lz4 and xz (liblzma) for the Everyday Work benchmark's compression rows (almost every
  system has them); libcurl for the Network benchmark's internet speed test; the Vulkan loader and
  your GPU's Vulkan driver for the GPU benchmarks; ROCm (HIP), CUDA or an OpenCL driver (with
  CLBlast) only if you want those back ends in GPU Burnin and the GPU Compute comparison
• For guide links at the exact page: Okular, Evince or Papers (other viewers open the HTML guide)

Upgrading from 2.2.0 or 2.2.1

Install the new package over the old one; nothing has to be set up again.

SRS is Copyright (C) 2026 by Eugene Flanagin. Licensed under GPL-2.0-or-later.

SIV is the work of Ray Hinchliffe, RH Software (https://rh-software.com).

SRS 2.2.1 - fixes for GPU Burnin, CPU Burnin and the main window

SRS 2.2.1 - fixes for GPU Burnin, CPU Burnin and the main window

A small update to SRS 2.2 with fixes found in the final review of 2.2.0. Nothing else changes:
everything from 2.2 is still there, and settings, tabs and lineups carry over.

What's fixed

• After a GPU driver call that never came back, the next GPU test no longer says "GPU Burnin is
  running; wait for it to finish". It says that a GPU call did not return earlier and that SRS (or the
  PC) must be restarted. CPU Burnin / Stress, which does not start while a GPU test holds the GPU,
  now shows why in its status line instead of doing nothing when you press Start.
• GPU Burnin on All GPUs: a card that cannot start (for example it cannot do FP64) is marked
  "COULD NOT START" in the table, and the verdict comes from the cards that did run. Before, the whole
  run was reported as "ended early by a safety rule" although the other cards had passed. If no card
  can start, the run says so. The command line prints the same note.
• GPU Compute comparison: pressing Run while SRS is still checking which back ends are installed
  says "Checking which back ends are installed..." instead of asking you to tick a back end that is
  still greyed out.
• The main window (and the other windows) no longer ask for more room than the screen has: the
  default size is limited to about 90% of the monitor's work area.
• The "CPU Burnin and GPU tests never start together" check no longer relies on x86 memory ordering,
  so it holds on ARM as well (the flag is now a proper atomic).
• The screenshots in the user guide that show the Benchmarks and Tools pages and the classic menu
  are retaken for the 2.2 look.

Full list in CHANGELOG.md; CREDITS.md lists the public data and the credits.

Tested on one PC (and what that means)

I build and test SRS on a single machine: a Ryzen 7 7800X3D with a Radeon RX 9070 XT, on a wired
connection. I've done everything I can for the rest (checks that don't need the hardware, careful
reading of the docs, test builds), but I can't try what I don't own. So anything that needs other
hardware, such as NVIDIA CUDA (and ZLUDA), Intel graphics, ROCm/HIP or OpenCL setups other than
mine, Wi-Fi or VPN network tests, or ARM and 32-bit builds, may have a bug or two I haven't met yet. If you find one, please tell me: open an issue on
GitHub with your hardware and the
report SRS made, and I'll fix it.

Not tried on real hardware so far:

• GPU benchmarks: the Vulkan tests, GPU Burnin and the GPU Compute comparison were run only on
  lavapipe (the Mesa software renderer, which runs on the CPU), with small sizes, so the logic, the
  error counting, Stop and the result pages are checked; the Vulkan type layouts were checked
  against the official Khronos header for 64-bit and 32-bit builds. ROCm/HIP, CUDA and OpenCL were
  tried only in part: the libraries load and every function SRS needs is found in them (on my own
  ROCm, my ZLUDA and my OpenCL loader too), and a missing library or an OpenCL loader with no
  driver is handled cleanly, but no HIP, CUDA or OpenCL work was run on a GPU. Not run on real
  hardware: Vulkan on a real GPU, GPU Burnin on a real GPU, CUDA on NVIDIA, ZLUDA, ROCm/HIP on AMD,
  OpenCL on AMD (ROCm) and Mesa Rusticl, anything on Intel graphics, and the temperature, power,
  clock and fan read-outs for NVIDIA and Intel.
• ARM (aarch64) and 32-bit (i686) builds: compile-checked only.
• OS Latency: run only with the scx_lavd scheduler; BORE, EEVDF and CFS are recognised but were
  not run here.
• CPU Compute: the AVX-512 code has only run on a Zen 4 CPU; the SSE2 and AVX2 code was checked by
  forcing it on that same CPU, not on older CPUs.
• Everyday Work: run with the compression libraries of one Arch Linux system; other versions
  should work but give different speeds.
• Network: run on one wired Ethernet connection only; Wi-Fi, VPN and metered or mobile
  connections are untested. The internet speed test was run once on that connection, against
  Cloudflare, with sensible results (download several hundred Mbit/s, upload about 60 Mbit/s), and
  the report showed no IP address, host name or MAC address.

Things to know about the GPU tests

• A back end that is not installed shows as "not installed" with a one-line hint (for example
  "install ROCm"); the others still run.
• If your CUDA library is really ZLUDA (CUDA calls translated to an AMD GPU), the column is
  labelled "CUDA (ZLUDA)".
• Every OpenCL driver is its own column, for example "OpenCL (ROCm)" and "OpenCL (Rusticl)" on the
  same GPU; CPU drivers (PoCL) are marked CPU.
• Speeds are only comparable between alike SRS builds and the same GPU driver / runtime versions.
• GPU Burnin ends by itself on a driver error, a GPU that stops answering, a piece of work that
  takes far too long, or a temperature at the limit (default 100 °C). It never changes clocks,
  voltages or fans. It asks before it starts. It never burns a software renderer (such as
  llvmpipe) as if it were a GPU, and when a card reports no temperature to SRS the result says that
  the temperature limit was not active.
• Opening a GPU window's list of GPUs, or pressing Run, reads the list of GPUs through Vulkan, the
  way vulkaninfo does: the GPUs are named, no work is sent to them until you answer Yes. ROCm /
  HIP, CUDA and OpenCL are started only after Yes (in GPU Burnin the GPU you picked is found in
  their own list by its PCI address).

Downloads

File	For
srs-sysinfo-2.2.1-1-x86_64.pkg.tar.zst	Arch Linux and Arch-based distros (same as the AUR package, prebuilt)
srs-sysinfo_2.2.1-1.deb13_amd64.deb	Debian 13 (trixie)
srs-sysinfo_2.2.1-1.ubuntu24.04_amd64.deb	Ubuntu 24.04 LTS (and derivatives such as Mint 22)
srs-sysinfo-2.2.1-1.fc44.x86_64.rpm	Fedora 44
srs-sysinfo-2.2.1-1.tw.x86_64.rpm	openSUSE Tumbleweed
srs-sysinfo-2.2.1-linux-x86_64.tar.gz	Any other distribution (run in place or copy to /usr/local)
srs-sysinfo-2.2.1-x86_64.AppImage	Any distribution from about 2022 on (glibc 2.35+): one file, nothing to install, can update itself
srs-sysinfo-2.2.1-x86_64.AppImage.zsync	Used by AppImageUpdate to update the AppImage; you do not need to download it
SRS-User-Guide.pdf	The user guide on its own
SHA256SUMS	checksums

Each package was built and install-tested in a clean container for its distro (the AppImage was
started in clean Debian 12 and Fedora 44 containers), for generic x86-64 (no CPU-specific
instructions), so they run on any 64-bit Intel or AMD PC.

Install

Arch Linux

sudo pacman -U srs-sysinfo-2.2.1-1-x86_64.pkg.tar.zst
# or from the AUR:  yay -S srs-sysinfo

Debian / Ubuntu

sudo apt install ./srs-sysinfo_2.2.1-1.deb13_amd64.deb        # or the .ubuntu24.04 file

Fedora / openSUSE

sudo dnf install ./srs-sysinfo-2.2.1-1.fc44.x86_64.rpm
sudo zypper install ./srs-sysinfo-2.2.1-1.tw.x86_64.rpm

Any other distribution

tar xf srs-sysinfo-2.2.1-linux-x86_64.tar.gz
cd srs-sysinfo-2.2.1-linux-x86_64
./usr/bin/srs-gui                     # run in place, or install:
sudo cp -r usr/bin usr/share /usr/local/

INSTALL.txt in the tarball covers the optional boot-time service and uninstalling.

AppImage (any distribution)

chmod +x srs-sysinfo-2.2.1-x86_64.AppImage
./srs-sysinfo-2.2.1-x86_64.AppImage

With arguments it is the command line (--version, find ..., srs-sysreport). Run as root
works from it; the boot-time refresh needs the package for your distro. AppImageUpdate (or a
manager that uses it, such as AppImageLauncher) keeps it up to date.

Requirements

• 64-bit x86 Linux. Use the package for your distro; the generic linux-x86_64.tar.gz is built from the
  Ubuntu 24.04 package and needs glibc 2.38 or newer (check with ldd --version)
• GTK 3, GLib, Pango, Cairo, SQLite 3 (for Power & cost), and hwdata
• Optional, for more detail: polkit (for srs-root), dmidecode, smartmontools, nvme-cli, i2c-tools,
  pciutils, usbutils, lm-sensors, vulkan-tools, clinfo, mesa-utils, libayatana-appindicator (tray icon);
  zlib, zstd, lz4 and xz (liblzma) for the Everyday Work benchmark's compression rows (almost every
  system has them); libcurl for the Network benchmark's internet speed test; the Vulkan loader and
  your GPU's Vulkan driver for the GPU benchmarks; ROCm (HIP), CUDA or an OpenCL driver (with
  CLBlast) only if you want those back ends in GPU Burnin and the GPU Compute comparison
• For guide links at the exact page: Okular, Evince or Papers (other viewers open the HTML guide)

Upgrading from 2.2.0

Install the new package over the old one; nothing has to be set up again.

SRS is Copyright (C) 2026 by Eugene Flanagin. Licensed under GPL-2.0-or-later.

SIV is the work of Ray Hinchliffe, RH Software (https://rh-software.com).

SRS 2.2 - Power & cost, new benchmarks, and tabs your way

SRS 2.2 - Power & cost, new benchmarks, and tabs your way

SRS 2.2 shows what your PC's power use costs, adds new benchmarks (among them Cache & Memory,
Storage, OS Latency and GPU tests), and lets you arrange the main window the way you like it: sort any table,
keep the tabs you want, and manage what starts with your PC. Everything from 2.0 is still there,
and the classic SIV-style windows too.

2.1 was never released on its own: this release also contains everything announced for 2.1.

What's new

Power & cost (a new page right under Sensors, Alt+9)

• How much power the whole PC uses at the wall, with its likely range, and what that costs per
  hour, day, month and year at your price. The processor and graphics card are measured; the rest
  is estimated from a parts list and your power supply's efficiency.
• Recording (off, for a while, or always) into a small database on your PC, with history by
  hour, day, week or month, busy sessions such as games or renders, CSV export, alarms, and
  typical electricity prices for your area that work offline. Nothing is sent anywhere.
• These are estimates, not a meter reading and not a bill. The page says so the first time it
  opens and on every export.

New benchmarks (Benchmarks & stress page, Alt+=)

• Cache & Memory: read, write and copy speed and latency of the RAM and the L1, L2 and L3
  caches, with the measured base clock and Infinity Fabric clock. The Linux System Audit (LSA)
  project is now part of SRS.
• Storage: read and write speed of a drive (sequential and 4K random, with response times),
  using only its own temporary test file, which can never be left behind.
• OS Latency: how quickly Linux answers a program - system calls, switching between
  programs, starting threads and programs, wake-ups, how late timers fire (with the CPU scheduler
  you use, such as scx_lavd, BORE or EEVDF), page faults and small-file operations. Light: one or
  two CPUs for about 6 seconds, and it changes nothing on your system.
• CPU Compute: number crunching - matrix multiply, FFT, gravity simulation, a fractal and a
  small ray tracer - on one thread and on all threads, with the fastest vector code your CPU has
  (up to AVX-512). Every answer is checked, so an unstable overclock or undervolt shows up as
  WRONG instead of a fast score.
• Everyday Work: the work your PC does all day - compressing and unpacking files (zlib, zstd,
  lz4 and xz, whichever your system has), sorting, checksums, searching and checking text, and
  running a small script-like program - on one thread and on all threads, every result checked.
  It uses data it makes itself, never your files.
• Network: how fast your PC moves network data on itself (nothing leaves the computer), and
  an optional internet speed test - name lookup, connect time, download and upload with one and
  several connections - against Cloudflare's public speed test. The internet test asks
  separately, tells you how much data it may use (up to about 1000 MB) and never runs without
  your yes. No addresses or network names are shown or saved.
• GPU Benchmark: how fast your graphics card does sums (single, half and double precision and
  whole numbers), how fast its memory reads, writes and copies, how fast data moves to and from it,
  and how quickly it answers - through Vulkan, with every result checked. About 15 seconds at full
  GPU load. Vulkan is used only if your system has it.
• GPU Burnin: a stress test for the graphics card. It keeps the GPU fully busy and checks
  every result, so a GPU overclock or undervolt that is not stable shows up as errors (0 errors =
  PASS), with the temperatures, power, clock and fan speed live. It runs through Vulkan, ROCm /
  HIP, CUDA or OpenCL - whichever you have. It asks first, stops by itself at a temperature limit
  (100 °C unless you change it) or when the driver reports a problem, and never changes clocks,
  voltages or fans.
• GPU Compute: Vulkan vs HIP vs CUDA vs OpenCL: the same GPU work through every way of
  programming your card that you have installed, side by side - SRS's own code and the maker's
  tuned library, the fastest marked and each compared with Vulkan. It recognises ZLUDA (CUDA on an
  AMD card) and shows every OpenCL driver separately.
• SRS Pi (with SuperPi's sizes too), Crypto (AES and SHA-256), Prime Sieve, and a
  benchmark history of your runs.
• Every benchmark asks before it starts and tells you what it does, how long it takes, how
  busy it makes your PC and (SRS Pi) how much memory it needs. For the heavy runs (all CPU threads
  at once, SRS Pi from 8 million digits, Prime Sieve from 10 billion, GPU Burnin) and for the
  internet speed test No is the default answer.
  The command line asks too; --yes starts a benchmark without the question, for scripts. Only one
  benchmark runs at a time, and CPU Burnin and GPU Burnin never run together.

The main window, your way

• Sortable tables: click a column heading (▲ then ▼). Sizes, clocks, temperatures, fan speeds
  and dates sort by value. Reset view puts the original order back; reports and Copy keep it.
• Tabs and lineups: add a tab with + (Ctrl+T), close, replace, drag and keep tabs; pick a
  tab bar of one scrolling row, wrapped rows or a side list. Lineups save the lot: Basic,
  Enthusiast and Expert (the default) are built in, and you can save, export and import your own.
  All N items is a searchable jump list.
• Less clutter: Windows-only items and hardware your PC does not have are hidden.
  Options -> Check now also hides items that come out empty on your PC (or turn on Check
  daily; it is off unless you do). The check never touches the network items.
  Options -> Show hidden items lists everything hidden.
• Startup manager (Operating system -> Startup programs): the tab opens on the read-only
  Report; Manage, one click away, switches autostart entries and services off and on
  without deleting anything, with Undo, Restore default and Add to startup....
• CPU Clocks: stock and in effect now: the measured base clock, core base, boost and current
  clock at stock and in effect, and FCLK, UCLK and MCLK from the SMU.
• Full access / Limited badge in the title bar, with a Run as root... button when root data
  is missing.

With Power & cost under Sensors, the page keys follow the sidebar: USB & PCI devices is now
Alt+0, Operating system Alt+-, Benchmarks & stress Alt+= and Tools Alt+Backspace.

Existing commands, options, item IDs and report formats are unchanged; the CPU Clocks item gains
its new table in reports too. New commands: sysreport-search cachemem, storage,
os-latency, compute, work, net, gpu, gpu-burn, gpu-compare, pi, crypto and prime. Settings carry over from 2.0.

The user guide has new sections on Power & cost, the new benchmarks, arranging tabs and lineups,
sortable tables, the Startup manager and the badge. CREDITS.md lists the public
data behind the price and CO2 tables and their licences.

Full list in CHANGELOG.md.

Tested on one PC (and what that means)

I build and test SRS on a single machine: a Ryzen 7 7800X3D with a Radeon RX 9070 XT, on a wired
connection. I've done everything I can for the rest (checks that don't need the hardware, careful
reading of the docs, test builds), but I can't try what I don't own. So anything that needs other
hardware, such as NVIDIA CUDA (and ZLUDA), Intel graphics, ROCm/HIP or OpenCL setups other than
mine, Wi-Fi or VPN network tests, or ARM and 32-bit builds, may have a bug or two I haven't met yet. If you find one, please tell me: open an issue on
GitHub with your hardware and the
report SRS made, and I'll fix it.

Not tried on real hardware so far:

• GPU benchmarks: the Vulkan tests, GPU Burnin and the GPU Compute comparison were run only on
  lavapipe (the Mesa software renderer, which runs on the CPU), with small sizes, so the logic, the
  error counting, Stop and the result pages are checked; the Vulkan type layouts were checked
  against the official Khronos header for 64-bit and 32-bit builds. ROCm/HIP, CUDA and OpenCL were
  tried only in part: the libraries load and every function SRS needs is found in them (on my own
  ROCm, my ZLUDA and my OpenCL loader too), and a missing library or an OpenCL loader with no
  driver is handled cleanly, but no HIP, CUDA or OpenCL work was run on a GPU. Not run on real
  hardware: Vulkan on a real GPU, GPU Burnin on a real GPU, CUDA on NVIDIA, ZLUDA, ROCm/HIP on AMD,
  OpenCL on AMD (ROCm) and Mesa Rusticl, anything on Intel graphics, and the temperature, power,
  clock and fan read-outs for NVIDIA and Intel.
• ARM (aarch64) and 32-bit (i686) builds: compile-checked only.
• OS Latency: run only with the scx_lavd scheduler; BORE, EEVDF and CFS are recognised but were
  not run here.
• CPU Compute: the AVX-512 code has only run on a Zen 4 CPU; the SSE2 and AVX2 code was checked by
  forcing it on that same CPU, not on older CPUs.
• Everyday Work: run with the compression libraries of one Arch Linux system; other versions
  should work but give different speeds.
• Network: run on one wired Ethernet connection only; Wi-Fi, VPN and metered or mobile
  connections are untested. The internet speed test was run once on that connection, against
  Cloudflare, with sensible results (download several hundred Mbit/s, upload about 60 Mbit/s), and
  the report showed no IP address, host name or MAC address.

Things to know about the GPU tests

• A back end that is not installed shows as "not installed" with a one-line hint (for example
  "install ROCm"); the others still run.
• If your CUDA library is really ZLUDA (CUDA calls translated to an AMD GPU), ...

SRS 2.0 - a new main window

SRS 2.0 - a new main window

SRS gets a friendlier main window. Everything SRS showed before is still there, one click away, and
the classic SIV-style windows are still available.

What's new

• One window with a sidebar of pages: Overview, Processor, Memory, Motherboard & BIOS,
  Graphics & audio, Storage, Network, Sensors, USB & PCI devices, Operating system, Benchmarks &
  stress, and Tools. It follows your desktop's light or dark theme.
• "Is my PC OK?" on the Overview: a status light for CPU and graphics temperature, drive health
  (SMART) and temperature, hardware errors, free disk space, memory in use and sensor alarms, each
  explained in plain words, with a Details button that shows the readings behind it. Temperatures
  are judged against each sensor's own limit (the CPU's maximum, the card's critical hotspot
  temperature, each drive's warning temperature). Cards below give the key numbers for the
  processor, graphics, memory, storage, operating system and motherboard.
• Every page starts with a short explanation and the key facts, then the same detailed panels
  as before as tabs: same text, colours and live updates, with Refresh, Copy, Guide (F1) and
  Open in window. All N items on each page lists every item, the expert ones included.
• Search in the title bar (Ctrl+F): type "temperature", "SMART", "BIOS"... and pick an item, or
  press Enter to find text on the current tab.
• Classic view: Menu -> Classic View, the button under the sidebar, or srs-gui --gui-classic.
  Options -> Start in classic view makes it the default; --gui-new opens the new window anyway.
• Clearer names: the "Windows (OS) panel" is now General Info, and "About SIV" is now
  About SRS, which starts with who made SRS, its licence and its home page. Their IDs
  (windows, about) are unchanged.

Existing commands, options and item IDs are unchanged (srs-gui gains two start options, --gui-classic
and --gui-new); saved reports only show the two new names. The Redact option works as before for
Save Report, the Copy button and right-click Copy / Ctrl+C.

The user guide has a new tour of the main window with screenshots, and every section of it says where
to find things in the new window and in the classic view.

Full list in CHANGELOG.md.

Downloads

File	For
srs-sysinfo-2.0.0-1-x86_64.pkg.tar.zst	Arch Linux and Arch-based distros (same as the AUR package, prebuilt)
srs-sysinfo_2.0.0-1.deb13_amd64.deb	Debian 13 (trixie)
srs-sysinfo_2.0.0-1.ubuntu24.04_amd64.deb	Ubuntu 24.04 LTS (and derivatives such as Mint 22)
srs-sysinfo-2.0.0-1.fc44.x86_64.rpm	Fedora 44
srs-sysinfo-2.0.0-1.tw.x86_64.rpm	openSUSE Tumbleweed
srs-sysinfo-2.0.0-linux-x86_64.tar.gz	Any other distribution (run in place or copy to /usr/local)
srs-sysinfo-2.0.0-x86_64.AppImage	Any distribution from about 2022 on (glibc 2.35+): one file, nothing to install, can update itself
srs-sysinfo-2.0.0-x86_64.AppImage.zsync	Used by AppImageUpdate to update the AppImage; you do not need to download it
SRS-User-Guide.pdf	The user guide on its own
SHA256SUMS	checksums

Each package was built and install-tested in a clean container for its distro (the AppImage was
started in clean Debian 12 and Fedora 44 containers), for generic x86-64 (no CPU-specific
instructions), so they run on any 64-bit Intel or AMD PC.

Install

Arch Linux

sudo pacman -U srs-sysinfo-2.0.0-1-x86_64.pkg.tar.zst
# or from the AUR:  yay -S srs-sysinfo

Debian / Ubuntu

sudo apt install ./srs-sysinfo_2.0.0-1.deb13_amd64.deb        # or the .ubuntu24.04 file

Fedora / openSUSE

sudo dnf install ./srs-sysinfo-2.0.0-1.fc44.x86_64.rpm
sudo zypper install ./srs-sysinfo-2.0.0-1.tw.x86_64.rpm

Any other distribution

tar xf srs-sysinfo-2.0.0-linux-x86_64.tar.gz
cd srs-sysinfo-2.0.0-linux-x86_64
./usr/bin/srs-gui                     # run in place, or install:
sudo cp -r usr/bin usr/share /usr/local/

INSTALL.txt in the tarball covers the optional boot-time service and uninstalling.

AppImage (any distribution)

chmod +x srs-sysinfo-2.0.0-x86_64.AppImage
./srs-sysinfo-2.0.0-x86_64.AppImage

With arguments it is the command line (--version, find ..., srs-sysreport). Run as root
works from it; the boot-time refresh needs the package for your distro. AppImageUpdate (or a
manager that uses it, such as AppImageLauncher) keeps it up to date.

Requirements

• 64-bit x86 Linux. Use the package for your distro; the generic linux-x86_64.tar.gz is built from the
  Ubuntu 24.04 package and needs glibc 2.38 or newer (check with ldd --version)
• GTK 3, GLib, Pango, Cairo, and hwdata
• Optional, for more detail: polkit (for srs-root), dmidecode, smartmontools, nvme-cli, i2c-tools,
  pciutils, usbutils, lm-sensors, vulkan-tools, clinfo, mesa-utils, libayatana-appindicator (tray icon)
• For guide links at the exact page: Okular, Evince or Papers (other viewers open the HTML guide)

Upgrading from 1.1.x

Nothing to do: settings, the boot-time service and saved benchmark results carry over. If you prefer
the old layout, tick Options -> Start in classic view.

SRS is Copyright (C) 2026 by Eugene Flanagin. Licensed under the GNU General Public License v2.0 or later (GPL-2.0-or-later).

SIV is the work of Ray Hinchliffe, RH Software (https://rh-software.com).

SRS 1.1.4 - redaction for copied text

SRS 1.1.4 - redaction for copied text

A small update to 1.1.3.

What's new

• Copy is now private too. Turn on Menu -> Options -> Redact identifiers in saved reports and
  copied text, and the Copy button, right-click Copy and Ctrl+C hide serial numbers, UUIDs, MAC
  addresses (vendor half kept), boot / machine IDs and your computer's name, just like Save Report.
  Handy for pasting sensor readings into a forum post. The panels themselves still show everything.

Full list in CHANGELOG.md.

Downloads

File	For
srs-sysinfo-1.1.4-1-x86_64.pkg.tar.zst	Arch Linux and Arch-based distros (same as the AUR package, prebuilt)
srs-sysinfo_1.1.4-1.deb13_amd64.deb	Debian 13 (trixie)
srs-sysinfo_1.1.4-1.ubuntu24.04_amd64.deb	Ubuntu 24.04 LTS (and derivatives such as Mint 22)
srs-sysinfo-1.1.4-1.fc44.x86_64.rpm	Fedora 44
srs-sysinfo-1.1.4-1.tw.x86_64.rpm	openSUSE Tumbleweed
srs-sysinfo-1.1.4-linux-x86_64.tar.gz	Any other distribution (run in place or copy to /usr/local)
SRS-User-Guide.pdf	The user guide on its own
SHA256SUMS	checksums

Each package was built and install-tested in a clean container for its distro, for generic x86-64 (no CPU-specific
instructions), so they run on any 64-bit Intel or AMD PC.

Install

Arch Linux

sudo pacman -U srs-sysinfo-1.1.4-1-x86_64.pkg.tar.zst
# or from the AUR:  yay -S srs-sysinfo

Debian / Ubuntu

sudo apt install ./srs-sysinfo_1.1.4-1.deb13_amd64.deb        # or the .ubuntu24.04 file

Fedora / openSUSE

sudo dnf install ./srs-sysinfo-1.1.4-1.fc44.x86_64.rpm
sudo zypper install ./srs-sysinfo-1.1.4-1.tw.x86_64.rpm

Any other distribution

tar xf srs-sysinfo-1.1.4-linux-x86_64.tar.gz
cd srs-sysinfo-1.1.4-linux-x86_64
./usr/bin/srs-gui                     # run in place, or install:
sudo cp -r usr/bin usr/share /usr/local/

INSTALL.txt in the tarball covers the optional boot-time service and uninstalling.

Requirements

• 64-bit x86 Linux. Use the package for your distro; the generic linux-x86_64.tar.gz is built from the
  Ubuntu 24.04 package and needs glibc 2.38 or newer (check with ldd --version)
• GTK 3, GLib, Pango, Cairo, and hwdata
• Optional, for more detail: polkit (for srs-root), dmidecode, smartmontools, nvme-cli, i2c-tools,
  pciutils, usbutils, lm-sensors, vulkan-tools, clinfo, mesa-utils, libayatana-appindicator (tray icon)
• For guide links at the exact page: Okular, Evince or Papers (other viewers open the HTML guide)

Upgrading from 1.1.1 or 1.1.0

Nothing to do: settings, the boot-time service and saved benchmark results carry over.

SRS is Copyright (C) 2026 by Eugene Flanagin. Licensed under the GNU General Public License v2.0 or later (GPL-2.0-or-later).

SIV is the work of Ray Hinchliffe, RH Software (https://rh-software.com).

SRS 1.1.3 - guide tidy-up

SRS 1.1.3 - guide tidy-up

A small update to 1.1.2. No changes to what SRS shows or measures.

What's new

• User guide: the example screenshots and example values now use a generic computer name (MYPC)
  throughout.

Full list in CHANGELOG.md.

Downloads

File	For
srs-sysinfo-1.1.3-1-x86_64.pkg.tar.zst	Arch Linux and Arch-based distros (same as the AUR package, prebuilt)
srs-sysinfo_1.1.3-1.deb13_amd64.deb	Debian 13 (trixie)
srs-sysinfo_1.1.3-1.ubuntu24.04_amd64.deb	Ubuntu 24.04 LTS (and derivatives such as Mint 22)
srs-sysinfo-1.1.3-1.fc44.x86_64.rpm	Fedora 44
srs-sysinfo-1.1.3-1.tw.x86_64.rpm	openSUSE Tumbleweed
srs-sysinfo-1.1.3-linux-x86_64.tar.gz	Any other distribution (run in place or copy to /usr/local)
SRS-User-Guide.pdf	The user guide on its own
SHA256SUMS	checksums

Each package was built and install-tested in a clean container for its distro, for generic x86-64 (no CPU-specific
instructions), so they run on any 64-bit Intel or AMD PC.

Install

Arch Linux

sudo pacman -U srs-sysinfo-1.1.3-1-x86_64.pkg.tar.zst
# or from the AUR:  yay -S srs-sysinfo

Debian / Ubuntu

sudo apt install ./srs-sysinfo_1.1.3-1.deb13_amd64.deb        # or the .ubuntu24.04 file

Fedora / openSUSE

sudo dnf install ./srs-sysinfo-1.1.3-1.fc44.x86_64.rpm
sudo zypper install ./srs-sysinfo-1.1.3-1.tw.x86_64.rpm

Any other distribution

tar xf srs-sysinfo-1.1.3-linux-x86_64.tar.gz
cd srs-sysinfo-1.1.3-linux-x86_64
./usr/bin/srs-gui                     # run in place, or install:
sudo cp -r usr/bin usr/share /usr/local/

INSTALL.txt in the tarball covers the optional boot-time service and uninstalling.

Requirements

• 64-bit x86 Linux. Use the package for your distro; the generic linux-x86_64.tar.gz is built from the
  Ubuntu 24.04 package and needs glibc 2.38 or newer (check with ldd --version)
• GTK 3, GLib, Pango, Cairo, and hwdata
• Optional, for more detail: polkit (for srs-root), dmidecode, smartmontools, nvme-cli, i2c-tools,
  pciutils, usbutils, lm-sensors, vulkan-tools, clinfo, mesa-utils, libayatana-appindicator (tray icon)
• For guide links at the exact page: Okular, Evince or Papers (other viewers open the HTML guide)

Upgrading from 1.1.1 or 1.1.0

Nothing to do: settings, the boot-time service and saved benchmark results carry over.

SRS is Copyright (C) 2026 by Eugene Flanagin. Licensed under the GNU General Public License v2.0 or later (GPL-2.0-or-later).

SIV is the work of Ray Hinchliffe, RH Software (https://rh-software.com).