boring>BoringOS independent systems project
BoringKernel 0.0.62-dev · x86_64 · C · M66 PHYSICAL USB BASELINE

BoringOS

An independent desktop operating system built from scratch — not Linux, not BSD and not a wrapper around another kernel. BoringOS now boots on the real Cthulhu machine with independently owned xHCI controllers, enumerates the real Genesys Logic USB hub and receives movement from the real ROCCAT mouse behind it. That physical input moves the existing software cursor and changes BoringWM focus between live windows as the pointer crosses them. The proven BoringFS, reboot and ACPI S5 lifecycle remains intact.boring is not a bug. it's the entire operating system now.

  • PHYSICAL multi-xHCI
  • PHYSICAL Genesys USB hub
  • PHYSICAL ROCCAT mouse
  • PHYSICAL USB keyboard
  • LIVE persistent BoringFS
  • LIVE reboot + ACPI S5

The physically accepted M66 runtime is frozen at 8ccd618dfc4e8163821de552a3c912bab4e6f36a. Its 96 MiB USB image has SHA-256 84dfb521c2359364ba2f3f78718b686638d81f3d07f35050f32e5a2f91bd0c61. On Cthulhu the real hub-connected mouse visibly moves the cursor and BoringWM pointer hit-testing changes focus between two live windows.

BoringOS graphical terminal running boringfetch
BoringTerminal + boringfetch. This repository image is an earlier QEMU screenshot; the desktop stack is now physically proven on Cthulhu with real multi-xHCI USB, a Genesys hub and a downstream ROCCAT mouse. M66 physical validation: 2026-09-06.
01 · Physical proof

The USB topology is real now too.

Cthulhu boots into BoringWM with the existing durable USB root and now also proves multiple xHCI controllers, real hub enumeration and a real downstream mouse reaching the Ring3 desktop.

HW

Cthulhu

AMD Ryzen 7 5800X3D, Gigabyte B550 VISION D, 32 GiB installed memory detected through SMBIOS and 57 PCI devices reported by boringfetch.

USB

Real keyboard + mouse path

The direct Holtek keyboard and the ROCCAT mouse behind a real Genesys hub reach BoringOS through its own xHCI/HID stack. Mouse movement drives the cursor and live-window pointer focus.

PWR

Reboot + shutdown

reboot performs a real hardware reset and firmware re-entry. shutdown performs a real ACPI S5 power-off after storage synchronization.

02 · Native desktop

Kernel, services, WM and applications are all BoringOS.

PID 1 starts the Ring3 display stack from BoringFS. There is no X11 or Wayland underneath it.

bootLimineUEFI bootstrap + firmware framebuffer.
kernelBoringKernelMemory, scheduling, processes and syscalls.
storageBoringFSWritable USB-root on the physical M63 image.
serviceboring-displayInput ownership and software composition.
policyBoringWMTiling, focus, close and persistent empty desktop.
appsTerminal · Edit · FilesNative Ring3 applications.
BoringEdit on BoringOS
BoringEdit. Native editor with BoringFS load/save.
BoringFiles on BoringOS
BoringFiles. Native file manager using real VFS/BoringFS directory enumeration.

Physical shortcuts include Super+Return, Super+E, Super+F and Super+Q. M62 also physically proved seven terminals plus Edit and Files, full close-down and clean capacity reuse.

03 · USB

Multi-xHCI, the real hub and the real mouse now work physically.

M64 removed the single-controller assumption, M65 added bounded downstream hub topology and M66 proves the complete physical path on Cthulhu. M63 remains the separate durability baseline for USB Mass Storage and persistent BoringFS.

PROVENMulti-xHCIRelevant controllers are instance-owned with independent MMIO, command/event rings and device state.
PROVENGenesys hubReal hub-class descriptor, power, status and bounded asynchronous reset handling work on Cthulhu.
PROVENROCCAT mouseThe downstream physical mouse reaches HID Interrupt-IN and moves the existing BoringOS software cursor.
PROVENBoringWM focusWith two live windows, moving the pointer across them changes focus through real Ring3 pointer hit-testing.
04 · Graphics

Software-rendered today. Native GPU driver later.

BoringOS currently composes the desktop on the CPU and presents into the firmware/Limine framebuffer. The GPU scans that framebuffer out to the monitor, but BoringOS does not yet program AMD graphics hardware itself.

NOW800×600 framebufferThe current physical GOP/firmware mode is 800×600×32 with pitch 3328.
NOWCPU compositionboring-display/BoringWM render in software; the present path copies pixels into the scanout framebuffer.
NEXTBetter GOP modeGet a native or otherwise useful monitor resolution before building a full vendor GPU driver.
LATERAMD driverNative modesetting, VRAM/GTT and GPU command submission are intentionally much later work.
05 · Storage + BoringFS

The physical USB root now survives a full reboot cycle.

BoringFS is BoringOS's own filesystem. M63 physically proves mkdir/touch/write on the USB root, real reboot, a second successful mount and the original data still present afterwards.

FS

BoringFS

Own codec, validator, formatter, boringfsck, kernel mount support and writable operation.

USB

Physical root

xHCI USB Mass Storage, Bulk/BOT/SCSI and the fixed BoringFS slice are physically reached on Cthulhu.

SATA

Other path

Bounded synchronous AHCI/SATA read, write and flush support remains verified alongside VirtIO reference storage.

06 · After M66

USB topology is frozen. Polish input, then move on to graphics.

M61 proved the desktop, M62 capacity, M63 durability/power and M64–M66 now close the multi-xHCI → hub → real mouse chain on physical Cthulhu.

M66physical USB topology baseline
0.0.62-devcurrent BoringKernel banner
xHCI · HUB · MOUSEphysically proven on Cthulhu

M61 · Physical desktop

USB-root boot, real BoringWM, keyboard, native apps and persistent empty desktop.

DONE

M62 · Dynamic process/task capacity

Dynamic runtime objects, 64/64 policy limits and physical multi-application churn beyond the old fixed ceiling.

DONE

M63 · Persistent power lifecycle

Durable USB writes, real reboot, second boot with data intact and real ACPI S5 shutdown.

FROZEN

M64–M66 · Multi-xHCI + hub + physical mouse

Independent controllers, real Genesys hub enumeration and the real ROCCAT mouse driving cursor movement and pointer focus.

FROZEN

Next · Keyboard held-key repeat

Add bounded typematic repeat so Backspace, arrows and ordinary keys repeat naturally while held without repeating WM launcher shortcuts.

NEXT

Then · Better GOP resolution

Move beyond the current 800×600 firmware framebuffer while keeping the proven software-rendered desktop.

PLANNED

Later · Faster present, more RAM, native AMD

Optimize software presentation, use the installed 32 GiB more meaningfully and only much later build native GPU support.

LATER
07 · Current limits

The remaining rough edges are visible — and useful.

The physical machine is now exposing exactly which bootstrap assumptions should be removed next.

Processes

The old fixed arrays are gone. Current policy limits are 64 processes / 64 tasks, with 16 BoringWM clients and 16 WM/display IPC peers.

Keyboard repeat

Held USB keys do not typematically repeat yet; Backspace currently needs one press per deletion. This is input polish, not a topology failure.

Graphics

Firmware framebuffer + CPU composition. No native AMD/NVIDIA/Intel GPU driver yet.

System breadth

No networking, audio, NVMe or SMP runtime yet. BoringOS still prefers a truthful small system over pretend support.

Source of truth

main now contains the physically accepted M66 runtime plus documentation. The exact runtime is retained separately as an immutable-by-policy freeze branch.