The Omarchy Robots Manual

Chapter 11

Troubleshooting

Start with the checklist. It names what is wrong more often than not:

sudo omarchy-robot validate

These are the failure points expected at bring-up. The first board, an AGX Orin developer kit, met one more, now in the table: it booted its system instead of entering recovery mode.

Symptom First command
The board boots its system instead of entering recovery mode From a Linux running on the board: sudo systemctl reboot --reboot-argument=forced-recovery; otherwise the buttons again
Firmware and L4T disagree: jetson.l4t fails, NVIDIA’s logo instead of ours at power-on, or the board stops in UEFI or early in the kernel ota-check-firmware -b (or cat /sys/class/dmi/id/bios_version), then flash again with step 2 of the bring-up
gpu.device fails, no GPU device node lsmod \| grep nvgpu; ls -l /dev/nvgpu/igpu0; dmesg \| grep -i nvgpu
The NVMe is not seen by UEFI or the installer In the installer: lsblk; dmesg \| grep -i nvme; lspci. Reseat the SSD in the Key M slot
The installer does not appear on the network On the serial console: ip -br addr; networkctl
The board’s USB ID is in no table Stop. There is no mapping for that board here
Building on the robot is slow (Orin Nano) Build on your computer and deploy with --target-host. To see what a deploy would build: nix build --dry-run .#nixosConfigurations.robot.config.system.build.toplevel
A change broke the robot sudo omarchy-robot rollback, or pick the previous generation in the boot menu

The VM

Reporting a problem

Bring the output of omarchy-robot info --json and validate --json, plus, on a board, the flash script’s output, the serial console log, dmesg and journalctl -b -p warning. Open an issue on GitHub.