Skip to content

LordOS — a free, fast and secure GNU/Linux distribution based on Debian, with its own desktop environment: display server and Wayland compositor in C, a React UI engine on QuickJS, and private native apps.

Roadmap: LordBench's x86 PC reference and hardware video decoding move from 0.8.6 to a new Release 0.8.7 (planned) section (decided by the maintainer on 2026-10-29); BENCHMARK, PAPER-VALIDATION, the paper (§7.5; en, es, pt) and CHANGELOG

Federico Pereira2d90ac6a5bfa
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 26dc553..8364dac 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -25,6 +25,10 @@ of the matching [GitHub release](https://github.com/lordbasex/LordOS/releases),
by LordBench (two monitors and 4K still not).
- **The 0.8.6 plan** (2026-10-28): `docs/ROADMAP.md` has a "Release 0.8.6 (in development)" section listing what is
built and what is left for LordBench and for the desktop under load on the Pi 5.
+- **The 0.8.7 plan** (2026-10-29, decided by the maintainer): LordBench's x86 PC reference (a modest PC still to be
+ chosen) and hardware video decoding (VA-API on PCs, the Pi 5's HEVC decoder) move from 0.8.6 to a new "Release 0.8.7
+ (planned)" section of `docs/ROADMAP.md`, next to the community hardware reports. `BENCHMARK.md`,
+ `PAPER-VALIDATION.md` and the paper (§7.5; en, es, pt) say so.
- **0.8.5-beta published** (2026-10-27): the GitHub release carries the live ISO, the Raspberry Pi 5 image
(`lordos-0.8.5-rpi5-arm64.img.xz`, the LordOS kernel 6.18.57-lordos.3 for the Pi 5; the Pi 4 still boots Raspberry
diff --git a/docs/BENCHMARK.md b/docs/BENCHMARK.md
index 9074c55..29619e3 100644
--- a/docs/BENCHMARK.md
+++ b/docs/BENCHMARK.md
@@ -1,12 +1,12 @@
# System Information, LordBench and hardware reports (proposal)
-**Status: design proposal. Built and released in 0.8.5-beta (2026-10-27; see "Work plan for 0.8.5" below): the collector, `lordos-sysreport report|fetch`, the System Information app (Overview, Hardware, Compatibility, Checks, Report), the Sandbox Probe and the shared measurement library `server/src/bench`. LordBench (0.8.6) is in development: the `lord-bench` helper, its CPU, memory, GPU, storage and sustained workloads, the interface (layout, paint, shaping) and video workloads, the desktop-impact mode (the compositor's frames, their phases and pointer-to-screen latency under load), the boot test, the guards, `lordos-sysreport bench` and System Information's Performance tab are built, with two of the three reference machines (VM 116 and the Raspberry Pi 5 16 GB; see "Built so far" under 0.8.6); the modest x86 PC reference is not. Community reports (0.8.7) and a `checks` subcommand of `lordos-sysreport` are not built.** It plans three releases and a later stage:
+**Status: design proposal. Built and released in 0.8.5-beta (2026-10-27; see "Work plan for 0.8.5" below): the collector, `lordos-sysreport report|fetch`, the System Information app (Overview, Hardware, Compatibility, Checks, Report), the Sandbox Probe and the shared measurement library `server/src/bench`. LordBench (0.8.6) is in development: the `lord-bench` helper, its CPU, memory, GPU, storage and sustained workloads, the interface (layout, paint, shaping) and video workloads, the desktop-impact mode (the compositor's frames, their phases and pointer-to-screen latency under load), the boot test, the guards, `lordos-sysreport bench` and System Information's Performance tab are built, with two of the three reference machines (VM 116 and the Raspberry Pi 5 16 GB; see "Built so far" under 0.8.6); the modest x86 PC reference is not, and moved to 0.8.7 with hardware video decoding (2026-10-29). Community reports (0.8.7) and a `checks` subcommand of `lordos-sysreport` are not built.** It plans three releases and a later stage:
| Release | What |
|---|---|
| **0.8.5 — System Information** | Every piece of hardware detected, what LordOS uses (above all the GPU), the services, the paper's claims checked on this machine, JSON/Markdown reports. |
| **0.8.6 — LordBench** | Measurements of CPU, memory, GPU, the compositor, video and storage under recorded, reproducible conditions, with versioned results. |
-| **0.8.7 — Community hardware reports** | Publishing reports as GitHub issues, validating them, and a tested-hardware catalogue on lordos.org that the app also reads. |
+| **0.8.7 — Community hardware reports** | Publishing reports as GitHub issues, validating them, and a tested-hardware catalogue on lordos.org that the app also reads. Also LordBench's x86 PC reference and hardware video decoding, moved from 0.8.6 (2026-10-29). |
| **Later — Lumo and AutoTune** | `ROADMAP.md`, "Lumo, the local assistant": explains a report and tunes settings from what the machine measured. |
Each claim of the paper, how it is checked today and what is still missing: `PAPER-VALIDATION.md`.
@@ -287,7 +287,7 @@ development package.
"skipped: no codec". lord-media answers only `MM_BENCH` records (a measurement, a kind, a rate in thousandths),
checked by `lbv_record_valid` before they become results. Hardware decoding is not measured: neither test
machine has it (no VA-API on VM 116; the Pi 5's HEVC decoder needs FFmpeg's `v4l2request`, which Debian's FFmpeg
- lacks).
+ lacks; hardware decoding moved to 0.8.7).
- **Desktop impact** (its own button, its own result file `lordbench-desktop.json`): after the quiet wait,
System Information opens a second window with a scene (cards, shadows and a square turned through
`lord.setStyle` with the engine's `rotate` key; until 0.8.6's frame-cost work it sent a `transform` key the engine
@@ -432,7 +432,7 @@ development package.
copied from the `lordbench.json` it wrote (numbers below). A measurement added after a machine's run is listed in
its `notMeasured` until it is measured again: VM 116's layout, paint and shaping numbers come from a later Full
run; the Pi 5's were measured only in Quick runs from a terminal (below), so its reference still lists them as not
- measured. The modest x86 PC is added when measured.
+ measured. The modest x86 PC is added when measured (moved to 0.8.7 on 2026-10-29).
VM 116, Full with 30 s sustained, LordBench 1 (2026-10-27, 159 s): SHA-256 166 MB/s on one core and 984 MB/s on
eight; matrix product 3.3 and 19.9 GFLOP/s; xz 60 and 363 MB/s; QuickJS 57 and 336 runs/s; memory copy
@@ -770,13 +770,16 @@ measurement (or the JSON with `--json`); exit 0 when the run finished, 1 when it
but the helper-sandbox self-test let a try through or one is missing (text output only; with `--json` the exit
code is 0 or 1 and the tries are in `sandboxTries`). On VM 116 a quick run took 46 s.
-Not built yet: hardware video decoding (no test machine has VA-API, and the Pi 5's HEVC decoder needs FFmpeg's
-`v4l2request`); detecting the Pi's firmware throttling during a run on kernels that don't expose it; a Full run of
-the Pi 5 with the layout, paint and shaping workloads for its reference (two Quick runs measured them, above); and
-the x86 PC reference.
+Not built yet: detecting the Pi's firmware throttling during a run on kernels that don't expose it; and a Full run
+of the Pi 5 with the layout, paint and shaping workloads for its reference (two Quick runs measured them, above).
+Moved to 0.8.7 (decided by the maintainer on 2026-10-29; `ROADMAP.md`, "Release 0.8.7 (planned)"): hardware video
+decoding (no test machine has VA-API, and the Pi 5's HEVC decoder needs FFmpeg's `v4l2request`) and the x86 PC
+reference.
## 0.8.7 — Community hardware reports
+- **Moved from 0.8.6** (decided by the maintainer on 2026-10-29): LordBench's modest x86 PC reference and
+ hardware video decoding in `lord-media` and the video workloads ("Built so far", the end of the 0.8.6 section).
- **Share on GitHub** saves the report as a small HTML page and opens it with the default browser
(the existing `lord.apps.launchWith('', path)` rule). That page opens GitHub's new-issue form with
the `hardware-report` template, title and summary filled in; the user attaches the JSON and
diff --git a/docs/PAPER-VALIDATION.md b/docs/PAPER-VALIDATION.md
index d0a2b98..5ff7be1 100644
--- a/docs/PAPER-VALIDATION.md
+++ b/docs/PAPER-VALIDATION.md
@@ -147,7 +147,7 @@ State in the 0.8.5 edition (`web/content/paper/paper.en.md`, checked 2026-10-26)
| Gap | Covers | Plan |
|---|---|---|
| A denied connection, tried on the user's machine | §6.6 effective | An app with network access and a temporary rule (Checks) |
-| Repeatable performance numbers | §7 | LordBench (0.8.6, in development: CPU, memory, GPU offscreen, storage, sustained load, software video decoding and encoders, the desktop's frame times and pointer-to-screen latency alone and under load (and the compositor's CPU weight and real-time priority they led to), the boot time per version, the N-boot test, `lordos-sysreport bench`, the interface layout/paint and shaping workloads and the helper-sandbox self-test are built, with VM 116 and the Pi 5 as references, `BENCHMARK.md` "Built so far"; idle memory and CPU, hardware video decoding and app start are not) |
+| Repeatable performance numbers | §7 | LordBench (0.8.6, in development: CPU, memory, GPU offscreen, storage, sustained load, software video decoding and encoders, the desktop's frame times and pointer-to-screen latency alone and under load (and the compositor's CPU weight and real-time priority they led to), the boot time per version, the N-boot test, `lordos-sysreport bench`, the interface layout/paint and shaping workloads and the helper-sandbox self-test are built, with VM 116 and the Pi 5 as references, `BENCHMARK.md` "Built so far"; idle memory and CPU, hardware video decoding and app start are not; hardware video decoding and the x86 PC reference moved to 0.8.7 on 2026-10-29) |
| Rendering, 3D and video on every GPU | §3.2, §7.2–7.3 | The visual test bench below |
| Every key, the mouse, touchpads, gamepads, and the Wayland protocols | §3.3–§3.4 | The visual test bench below |
| Real hardware | §10.2 | Reports from System Information (0.8.7) |
diff --git a/docs/ROADMAP.md b/docs/ROADMAP.md
index 22d02f6..a5d6f0a 100644
--- a/docs/ROADMAP.md
+++ b/docs/ROADMAP.md
@@ -562,8 +562,8 @@ LordBench and a desktop that stays smooth under load. Each item is described in
- [ ] The interface workloads measured on the Pi 5 for its reference. *Two Quick runs from a terminal (2026-10-29):*
layout and paint 39.3–39.4 fps on one core, 45.4 fps with the paint threads; shaping 630–632 runs/s on one core,
2,522–2,527 on four (`BENCHMARK.md`); the reference waits for a Full run.
-- [ ] The x86 PC reference (a modest PC still to be chosen; may move to 0.8.7).
-- [ ] Hardware video decoding (may move after 0.8.6).
+- The x86 PC reference and hardware video decoding moved to 0.8.7 (decided by the maintainer on 2026-10-29;
+ "Release 0.8.7 (planned)" below).
- [x] Detecting the Pi 5 firmware's throttling. *Built (2026-10-28/29), checked on the Pi 5 on 2026-10-29:* the
LordOS kernel (`rpi-6.18.y`) only exposes the firmware's under-voltage alarm (`rpi_volt`'s `in0_lcrit_alarm`, the
last 2 s), not its capped, throttled or soft-limit bits, so LordBench watches that alarm and `get_throttled` where
@@ -614,6 +614,13 @@ desktop fell to 24 fps under an all-core load:
- [ ] Re-measure the references after the release (results compare only within one LordOS version).
- [ ] Release cleanup, packages, the Pi 5 image and the ISO, as for 0.8.5.
+## Release 0.8.7 (planned)
+
+Community hardware reports (the item under "Before 1.0", `BENCHMARK.md`), and what LordBench left for after 0.8.6:
+- [ ] The x86 PC reference for LordBench (a modest PC still to be chosen; moved from 0.8.6 on 2026-10-29).
+- [ ] Hardware video decoding (VA-API on PCs; the Pi 5's HEVC decoder needs FFmpeg's `v4l2request`, which Debian's
+ FFmpeg lacks), in `lord-media` and LordBench's video workloads (moved from 0.8.6 on 2026-10-29).
+
## Before 1.0
- [x] **Monitor → Network, second generation (0.8.5)** — done 2026-10-19 on VM 118, see
@@ -779,14 +786,15 @@ desktop fell to 24 fps under an all-core load:
code, one core and with the paint threads, and shaping fixed paragraphs in five scripts, with the fonts built
into the helper; VM 116: 37.0 and 39.9 fps, 619 and 3,595 runs/s), and the helper-sandbox self-test inside
`lord-bench` (six tries that must fail, checked by the Stability verdict and `lordos-sysreport bench`). Left:
- hardware video decoding, the x86 PC reference, a Full run of the Pi 5 with the interface workloads for its reference
+ a Full run of the Pi 5 with the interface workloads for its reference
(two Quick runs measured them on 2026-10-29), and the rest of what it found on the Pi 5 (the desktop fell to 24 fps under load;
the compositor's CPU weight and its real-time priority fix it on VM 116; on the Pi 5 with its monitor they take it
to 29–30 fps; the frame-cost work cuts a drag frame's build under load to 12.9 ms and keeps 60 fps alone, but
under load the frames still miss the refresh, at about 31 fps, now on the GPU's side (its time per frame 1.5 → 14–16
ms under load, no throttling); the frame pipeline and GPU drag, measured on 2026-10-29, gave too little and are off
by default: `BENCHMARK.md` "The desktop under load" and "The drag frame's cost"). The firmware throttling
- detection was checked on the Pi 5 (the under-voltage alarm present, reading 0).
+ detection was checked on the Pi 5 (the under-voltage alarm present, reading 0). Hardware video decoding and the x86 PC
+ reference moved to 0.8.7 (2026-10-29, "Release 0.8.7 (planned)").
- [ ] **Community hardware reports (0.8.7)** — `BENCHMARK.md`. Share on GitHub with the
`hardware-report` template (the user submits it, LordOS sends nothing), schema validation and
labels in a workflow, and a tested-hardware catalogue on lordos.org that the Compatibility panel
diff --git a/web/content/paper/paper.en.md b/web/content/paper/paper.en.md
index c351d78..602570d 100644
--- a/web/content/paper/paper.en.md
+++ b/web/content/paper/paper.en.md
@@ -489,7 +489,7 @@ The Raspberry Pi 5 is the only supported board. Results on a real board (16 GB,
### 7.5 Modern PCs
-There are no measurements on real PCs in the repository yet. The ISO is tested on virtual machines (UEFI and BIOS); testing on a real AMD machine from the live USB is planned. LordBench (0.8.6) is designed to measure memory and CPU at idle, boot time, frame times, video and app start in a repeatable way, and community hardware reports (0.8.7) to collect them from real machines (`docs/BENCHMARK.md`). In development for 0.8.6 (unreleased; the latest release is 0.8.5-beta), its first part is built: a sandboxed `lord-bench` helper that measures the CPU, memory, the GPU offscreen, storage and a sustained load, stops near the temperature limit or when the processor throttles, and records the conditions of each run, shown in System Information → Performance as "×N" of reference machines; it also measures software video decoding and the remote desktop's encoders, the desktop's frame times and the time from a pointer move to the screen, alone and under a low-priority load, and boot time over several restarts; it also runs from a terminal (`lordos-sysreport bench`). Also in development, it times LordOS's own interface work with the engine's real code (the layout and paint of a fixed full-HD desktop scene, and the shaping of paragraphs in Latin, Arabic, Devanagari, Thai and Chinese with fonts built into the helper, which opens no files; on the reference virtual machine 37 frames per second on one core and 40 with the paint threads, 619 shaping runs per second on one core and 3,595 on eight; on the Raspberry Pi 5, in two quick runs, 39 and 45 frames per second and 630 and 2,520 shaping runs per second on one and four cores), compared with a reference only when it was measured with the same LordOS version, and `lord-bench` checks its own sandbox before any work: six things it must not be able to do (open a local socket or a network connection, run a program, start a process, create a file, read a system file) were all refused on that machine, and a run where one gets through is marked unstable. On a Raspberry Pi it watches the board's firmware during the whole run: the under-voltage alarm, the only flag the LordOS Pi kernel exposes, the firmware's full throttling flags where an older kernel has them, and 80 °C, where the firmware starts slowing the processor down, which stops a peak test as throttled; System Information's Raspberry Pi section reads the same alarm and flags and leaves out what the kernel doesn't show. This was tested on simulated system files and on the Pi 5, where the alarm is present and reads 0 with the official power supply; an actual under-voltage was not provoked. The references are a virtual machine and a Raspberry Pi 5 (§7.4); hardware video decoding and a real PC reference are not built yet.
+There are no measurements on real PCs in the repository yet. The ISO is tested on virtual machines (UEFI and BIOS); testing on a real AMD machine from the live USB is planned. LordBench (0.8.6) is designed to measure memory and CPU at idle, boot time, frame times, video and app start in a repeatable way, and community hardware reports (0.8.7) to collect them from real machines (`docs/BENCHMARK.md`). In development for 0.8.6 (unreleased; the latest release is 0.8.5-beta), its first part is built: a sandboxed `lord-bench` helper that measures the CPU, memory, the GPU offscreen, storage and a sustained load, stops near the temperature limit or when the processor throttles, and records the conditions of each run, shown in System Information → Performance as "×N" of reference machines; it also measures software video decoding and the remote desktop's encoders, the desktop's frame times and the time from a pointer move to the screen, alone and under a low-priority load, and boot time over several restarts; it also runs from a terminal (`lordos-sysreport bench`). Also in development, it times LordOS's own interface work with the engine's real code (the layout and paint of a fixed full-HD desktop scene, and the shaping of paragraphs in Latin, Arabic, Devanagari, Thai and Chinese with fonts built into the helper, which opens no files; on the reference virtual machine 37 frames per second on one core and 40 with the paint threads, 619 shaping runs per second on one core and 3,595 on eight; on the Raspberry Pi 5, in two quick runs, 39 and 45 frames per second and 630 and 2,520 shaping runs per second on one and four cores), compared with a reference only when it was measured with the same LordOS version, and `lord-bench` checks its own sandbox before any work: six things it must not be able to do (open a local socket or a network connection, run a program, start a process, create a file, read a system file) were all refused on that machine, and a run where one gets through is marked unstable. On a Raspberry Pi it watches the board's firmware during the whole run: the under-voltage alarm, the only flag the LordOS Pi kernel exposes, the firmware's full throttling flags where an older kernel has them, and 80 °C, where the firmware starts slowing the processor down, which stops a peak test as throttled; System Information's Raspberry Pi section reads the same alarm and flags and leaves out what the kernel doesn't show. This was tested on simulated system files and on the Pi 5, where the alarm is present and reads 0 with the official power supply; an actual under-voltage was not provoked. The references are a virtual machine and a Raspberry Pi 5 (§7.4); hardware video decoding and a real PC reference are not built yet and moved to 0.8.7.
### Source files
diff --git a/web/content/paper/paper.es.md b/web/content/paper/paper.es.md
index 1ba31b0..d61f8b2 100644
--- a/web/content/paper/paper.es.md
+++ b/web/content/paper/paper.es.md
@@ -489,7 +489,7 @@ La Raspberry Pi 5 es la única placa soportada. Resultados en una placa real (16
### 7.5 PC modernas
-Todavía no hay mediciones en PC reales en el repositorio. La ISO se prueba en máquinas virtuales (UEFI y BIOS); está planeado probarla en una máquina AMD real desde el USB live. LordBench (0.8.6) está diseñado para medir de forma repetible la memoria y la CPU en reposo, el tiempo de arranque, los tiempos de cuadro, el video y el inicio de apps, y los informes de hardware de la comunidad (0.8.7), para recolectar esas mediciones de máquinas reales (`docs/BENCHMARK.md`). En desarrollo para la 0.8.6 (sin publicar; la última versión es la 0.8.5-beta), su primera parte ya está construida: un ayudante aislado, `lord-bench`, que mide la CPU, la memoria, la GPU fuera de pantalla, el almacenamiento y una carga sostenida, se detiene cerca del límite de temperatura o cuando el procesador baja la velocidad, y registra las condiciones de cada prueba, que Información del sistema → Rendimiento muestra como «×N» de máquinas de referencia; también mide la decodificación de video por software y los codificadores del escritorio remoto, los tiempos de cuadro del escritorio y el tiempo de un movimiento del puntero hasta la pantalla, solo y bajo una carga de baja prioridad, y el tiempo de arranque en varios reinicios; también corre desde una terminal (`lordos-sysreport bench`). También en desarrollo, mide el trabajo de la propia interfaz de LordOS con el código real del motor (el diseño y dibujo de una escena de escritorio fija en full HD, y la composición tipográfica de párrafos en latín, árabe, devanagari, tailandés y chino con fuentes incluidas en el ayudante, que no abre archivos; en la máquina virtual de referencia 37 cuadros por segundo en un núcleo y 40 con los hilos de dibujo, 619 pasadas de composición por segundo en un núcleo y 3.595 en ocho; en la Raspberry Pi 5, en dos pruebas rápidas, 39 y 45 cuadros por segundo y 630 y 2.520 pasadas de composición por segundo en uno y cuatro núcleos), comparado con una referencia solo si se midió con la misma versión de LordOS, y `lord-bench` comprueba su propio aislamiento antes de cualquier trabajo: seis cosas que no debe poder hacer (abrir un socket local o una conexión de red, ejecutar un programa, iniciar un proceso, crear un archivo, leer un archivo del sistema) fueron todas rechazadas en esa máquina, y una prueba en la que alguna pase se marca como inestable. En una Raspberry Pi vigila el firmware de la placa durante toda la prueba: la alarma de bajo voltaje, el único indicador que expone el kernel de LordOS para la Pi, los indicadores completos de limitación del firmware donde un kernel más viejo los tiene, y los 80 °C, donde el firmware empieza a bajar la velocidad del procesador, que detienen una prueba de pico como limitada; la sección Raspberry Pi de Información del sistema lee la misma alarma y los mismos indicadores y deja afuera lo que el kernel no muestra. Esto se probó con archivos de sistema simulados y en la Pi 5, donde la alarma está presente y marca 0 con la fuente oficial; no se provocó un bajo voltaje real. Las referencias son una máquina virtual y una Raspberry Pi 5 (§7.4); la decodificación de video por hardware y una referencia de PC real todavía no están construidas.
+Todavía no hay mediciones en PC reales en el repositorio. La ISO se prueba en máquinas virtuales (UEFI y BIOS); está planeado probarla en una máquina AMD real desde el USB live. LordBench (0.8.6) está diseñado para medir de forma repetible la memoria y la CPU en reposo, el tiempo de arranque, los tiempos de cuadro, el video y el inicio de apps, y los informes de hardware de la comunidad (0.8.7), para recolectar esas mediciones de máquinas reales (`docs/BENCHMARK.md`). En desarrollo para la 0.8.6 (sin publicar; la última versión es la 0.8.5-beta), su primera parte ya está construida: un ayudante aislado, `lord-bench`, que mide la CPU, la memoria, la GPU fuera de pantalla, el almacenamiento y una carga sostenida, se detiene cerca del límite de temperatura o cuando el procesador baja la velocidad, y registra las condiciones de cada prueba, que Información del sistema → Rendimiento muestra como «×N» de máquinas de referencia; también mide la decodificación de video por software y los codificadores del escritorio remoto, los tiempos de cuadro del escritorio y el tiempo de un movimiento del puntero hasta la pantalla, solo y bajo una carga de baja prioridad, y el tiempo de arranque en varios reinicios; también corre desde una terminal (`lordos-sysreport bench`). También en desarrollo, mide el trabajo de la propia interfaz de LordOS con el código real del motor (el diseño y dibujo de una escena de escritorio fija en full HD, y la composición tipográfica de párrafos en latín, árabe, devanagari, tailandés y chino con fuentes incluidas en el ayudante, que no abre archivos; en la máquina virtual de referencia 37 cuadros por segundo en un núcleo y 40 con los hilos de dibujo, 619 pasadas de composición por segundo en un núcleo y 3.595 en ocho; en la Raspberry Pi 5, en dos pruebas rápidas, 39 y 45 cuadros por segundo y 630 y 2.520 pasadas de composición por segundo en uno y cuatro núcleos), comparado con una referencia solo si se midió con la misma versión de LordOS, y `lord-bench` comprueba su propio aislamiento antes de cualquier trabajo: seis cosas que no debe poder hacer (abrir un socket local o una conexión de red, ejecutar un programa, iniciar un proceso, crear un archivo, leer un archivo del sistema) fueron todas rechazadas en esa máquina, y una prueba en la que alguna pase se marca como inestable. En una Raspberry Pi vigila el firmware de la placa durante toda la prueba: la alarma de bajo voltaje, el único indicador que expone el kernel de LordOS para la Pi, los indicadores completos de limitación del firmware donde un kernel más viejo los tiene, y los 80 °C, donde el firmware empieza a bajar la velocidad del procesador, que detienen una prueba de pico como limitada; la sección Raspberry Pi de Información del sistema lee la misma alarma y los mismos indicadores y deja afuera lo que el kernel no muestra. Esto se probó con archivos de sistema simulados y en la Pi 5, donde la alarma está presente y marca 0 con la fuente oficial; no se provocó un bajo voltaje real. Las referencias son una máquina virtual y una Raspberry Pi 5 (§7.4); la decodificación de video por hardware y una referencia de PC real todavía no están construidas y pasaron a la 0.8.7.
### Archivos fuente
diff --git a/web/content/paper/paper.pt.md b/web/content/paper/paper.pt.md
index e822f9f..7473ca8 100644
--- a/web/content/paper/paper.pt.md
+++ b/web/content/paper/paper.pt.md
@@ -489,7 +489,7 @@ O Raspberry Pi 5 é a única placa suportada. Resultados numa placa real (16 GB,
### 7.5 PCs modernos
-Ainda não há medições em PCs reais no repositório. A ISO é testada em máquinas virtuais (UEFI e BIOS); está planejado testá-la numa máquina AMD real a partir do pendrive live. O LordBench (0.8.6) foi projetado para medir de forma repetível memória e CPU em repouso, tempo de boot, tempos de quadro, vídeo e abertura de apps, e os relatórios de hardware da comunidade (0.8.7), para coletar essas medições de máquinas reais (`docs/BENCHMARK.md`). Em desenvolvimento para a 0.8.6 (não publicada; a última versão é a 0.8.5-beta), sua primeira parte já está construída: um auxiliar isolado, `lord-bench`, que mede a CPU, a memória, a GPU fora da tela, o armazenamento e uma carga contínua, para perto do limite de temperatura ou quando o processador reduz a velocidade, e registra as condições de cada teste, que Informações do Sistema → Desempenho mostra como «×N» de máquinas de referência; também mede a decodificação de vídeo por software e os codificadores da área de trabalho remota, os tempos de quadro do desktop e o tempo de um movimento do ponteiro até a tela, sozinho e sob uma carga de baixa prioridade, e o tempo de boot em várias reinicializações; também roda a partir de um terminal (`lordos-sysreport bench`). Também em desenvolvimento, mede o trabalho da própria interface do LordOS com o código real do motor (o layout e o desenho de uma cena de desktop fixa em full HD, e a composição tipográfica de parágrafos em latim, árabe, devanágari, tailandês e chinês com fontes embutidas no auxiliar, que não abre arquivos; na máquina virtual de referência 37 quadros por segundo em um núcleo e 40 com as threads de desenho, 619 passagens de composição por segundo em um núcleo e 3.595 em oito; no Raspberry Pi 5, em dois testes rápidos, 39 e 45 quadros por segundo e 630 e 2.520 passagens de composição por segundo em um e quatro núcleos), comparado com uma referência só quando medido com a mesma versão do LordOS, e o `lord-bench` verifica o próprio isolamento antes de qualquer trabalho: seis coisas que não deve conseguir fazer (abrir um socket local ou uma conexão de rede, executar um programa, iniciar um processo, criar um arquivo, ler um arquivo do sistema) foram todas recusadas nessa máquina, e um teste em que alguma passe é marcado como instável. Num Raspberry Pi ele vigia o firmware da placa durante todo o teste: o alarme de subtensão, o único indicador que o kernel do LordOS para o Pi expõe, os indicadores completos de limitação do firmware onde um kernel mais antigo os tem, e os 80 °C, onde o firmware começa a reduzir a velocidade do processador, que param um teste de pico como limitado; a seção Raspberry Pi de Informações do sistema lê o mesmo alarme e os mesmos indicadores e deixa de fora o que o kernel não mostra. Isso foi testado com arquivos de sistema simulados e no Pi 5, onde o alarme está presente e marca 0 com a fonte oficial; uma subtensão real não foi provocada. As referências são uma máquina virtual e um Raspberry Pi 5 (§7.4); a decodificação de vídeo por hardware e uma referência de PC real ainda não estão construídas.
+Ainda não há medições em PCs reais no repositório. A ISO é testada em máquinas virtuais (UEFI e BIOS); está planejado testá-la numa máquina AMD real a partir do pendrive live. O LordBench (0.8.6) foi projetado para medir de forma repetível memória e CPU em repouso, tempo de boot, tempos de quadro, vídeo e abertura de apps, e os relatórios de hardware da comunidade (0.8.7), para coletar essas medições de máquinas reais (`docs/BENCHMARK.md`). Em desenvolvimento para a 0.8.6 (não publicada; a última versão é a 0.8.5-beta), sua primeira parte já está construída: um auxiliar isolado, `lord-bench`, que mede a CPU, a memória, a GPU fora da tela, o armazenamento e uma carga contínua, para perto do limite de temperatura ou quando o processador reduz a velocidade, e registra as condições de cada teste, que Informações do Sistema → Desempenho mostra como «×N» de máquinas de referência; também mede a decodificação de vídeo por software e os codificadores da área de trabalho remota, os tempos de quadro do desktop e o tempo de um movimento do ponteiro até a tela, sozinho e sob uma carga de baixa prioridade, e o tempo de boot em várias reinicializações; também roda a partir de um terminal (`lordos-sysreport bench`). Também em desenvolvimento, mede o trabalho da própria interface do LordOS com o código real do motor (o layout e o desenho de uma cena de desktop fixa em full HD, e a composição tipográfica de parágrafos em latim, árabe, devanágari, tailandês e chinês com fontes embutidas no auxiliar, que não abre arquivos; na máquina virtual de referência 37 quadros por segundo em um núcleo e 40 com as threads de desenho, 619 passagens de composição por segundo em um núcleo e 3.595 em oito; no Raspberry Pi 5, em dois testes rápidos, 39 e 45 quadros por segundo e 630 e 2.520 passagens de composição por segundo em um e quatro núcleos), comparado com uma referência só quando medido com a mesma versão do LordOS, e o `lord-bench` verifica o próprio isolamento antes de qualquer trabalho: seis coisas que não deve conseguir fazer (abrir um socket local ou uma conexão de rede, executar um programa, iniciar um processo, criar um arquivo, ler um arquivo do sistema) foram todas recusadas nessa máquina, e um teste em que alguma passe é marcado como instável. Num Raspberry Pi ele vigia o firmware da placa durante todo o teste: o alarme de subtensão, o único indicador que o kernel do LordOS para o Pi expõe, os indicadores completos de limitação do firmware onde um kernel mais antigo os tem, e os 80 °C, onde o firmware começa a reduzir a velocidade do processador, que param um teste de pico como limitado; a seção Raspberry Pi de Informações do sistema lê o mesmo alarme e os mesmos indicadores e deixa de fora o que o kernel não mostra. Isso foi testado com arquivos de sistema simulados e no Pi 5, onde o alarme está presente e marca 0 com a fonte oficial; uma subtensão real não foi provocada. As referências são uma máquina virtual e um Raspberry Pi 5 (§7.4); a decodificação de vídeo por hardware e uma referência de PC real ainda não estão construídas e passaram para a 0.8.7.
### Arquivos-fonte