Home

NebulaOS-firmware

Role in NebulaOS: Canonical integration and build repository. Pins exact commits of the three component repos (kernel, Klipper, GuppyScreen), fetches them fresh on every build, applies the accepted kernel variants, and produces the final flashable rootfs + kernel + app-stack image. This is the only one of the five repos that alone produces a complete, flashable NebulaOS image.

Canonical branch: main

Complete OS build: Yes — git clone + ./build.sh from this repo, nothing else, reproduces the current qualified baseline. See Build From Source.

Related repos:

• NebulaOS — end-user release repo (not a source tree)
• NebulaOS-kernel — Linux 6.6 fork, openke branch
• NebulaOS-klipper — Klipper runtime fork, master branch
• NebulaOS-guppyscreen — touchscreen UI fork, main branch

Audience: Developers and advanced testers. Nothing on this wiki (or in this repo's docs/) is a consumer installer — every install/flash/recovery procedure documented here exposes raw firmware images, A/B boot partitions, and SSH/root access on real hardware.

---

Navigation

Building

• Build From Source — the ./build.sh entry point, what it does, prerequisites
• Build Environment — the unified nebulaos-build container
• Build Provenance — identifying exactly what produced a given artifact

Installing, updating, recovering a real device

• A/B Slot Model — the partition layout and boot-marker mechanism
• Developer Install From Stock — first flash onto a device
• Developer Update — component updates vs. whole-image updates
• Developer Recovery — the recovery ladder, including known limitations

Reference

• Repository Map — how the five NebulaOS repos relate

All of the above are summaries. The tracked docs under this repo's own docs/ directory are the canonical, versioned source of truth — this wiki exists for navigation and quick reference, not as a second copy. Where the two ever disagree, the repo wins.