Comet BIOS video capture, 2026-09-30

This record describes the real media used on the Bootscry home page. It is a separate run from the 2026-09-29 boot-menu benchmark.

Setup and method

• Target: the dedicated psycho mini PC at a Linux login prompt, with no logged-in user.
• Device: the GL.iNet Comet connected to its screen and USB input. The unit has no ATX board.
• Capture: one KVM session saved JPEG snapshots and UTC timestamps to manifest.json while the target rebooted.
• Reboot: a graceful systemctl reboot sent over SSH. The script sent no password to a command line or file.
• Input: immediately after the SSH command returned, the Comet sent Delete at 0.15-second intervals for 35 seconds. The tool reported 119 taps. This was a fixed loop; OCR did not decide when to stop.
• Result: a raw frame visibly shows the AMI Aptio Setup Utility. After inspection, Escape opened the "Exit Without Saving" dialog and Enter confirmed it. A later frame shows a clean Linux login prompt. No firmware setting was changed.

The capture has 559 raw JPEG frames over 285.5 seconds. It includes time spent inspecting the BIOS before exiting. Frame 41 shows setup 25.2 seconds after the first saved frame; that is not a reboot-to-setup latency measurement because the reboot command happened after frame capture began. The site video retains frames 1–100 and 250–375, omitting an idle inspection pause. It encodes those unaltered frames at a fixed six frames per second, so the retained sections play at about three times capture speed. No synthetic BIOS image or inserted event is used.

Integrity and limits

manifest.json records every frame name and UTC capture time. SHA256SUMS records hashes for all raw frames and the two verification frames. The full 92 MB raw JPEG set is retained with the operator and is not part of the public site. The public media are compressed and resized derivatives.

This is one successful capture on one board. It demonstrates timed input reaching firmware setup and a clean exit. It does not measure a success rate, prove autonomous menu recognition, or establish behavior on another KVM.