Repository navigation
Releases
v0.5.1
v0.5.1 — tofu-free forky glyphs, greeter power & cursor polish, and 4-target ARM64 release
A focused maintenance and milestone release building on v0.5.0: every TUI
icon, notification glyph, multi-field cursor, and console power control works
cleanly on live Debian forky/arm64 hardware, while four release images
(google-asurada, google-kukui, arm64-uefi, arm64-extlinux) bring LazyOS
not only to Google Hayato (MT8192) and Kukui/Duet (MT8183) Chromebooks,
but also to Raspberry Pi 4/5 (via EDK2 UEFI or U-Boot), ARM64 UEFI laptops/VMs,
and U-Boot Single-Board Computers.
What changed since v0.5.0
Tofu-free icon rendering on Debian forky (3.4.0+dfsg2-1)
- Remapped all 73 stripped Codicon codepoints (
U+EA60..U+EC1E): Debianforky
upgradedfonts-nerd-symbolsfrom3.4.0+dfsg1-2to3.4.0+dfsg2-1, which
removed Codicons while retaining Octicons, Devicons, Seti, Powerline, and IEC.
make-glyphs.shnow maps all 101
UIGlyphvariants to non-shadowed BMP codepoints covered by bothforky's
Symbols Nerd Font MonoandFont Awesome 6 Free Solid/Brands Regular
(101 drawn, 0 text fallbacks), andfoot.ini.tplincludes
Font Awesome 6 Brands Regular:size=12alongside Solid. - Full symbol fallback in
lazyos-notify:
FontRenderernow loadsfa-6.7.2-solid-900.ttfandfa-6.7.2-brands-400.ttf
afterSymbolsNerdFontMono-Regular.ttf, and notification/OSD cards resolve
icons fromlazyos_ui::Glyphplus Octicon mute (U+F466) and Font Awesome
close (U+F00D) instead of hardcoded Codicon escapes. - Resilient glyph verification in
check-desktop.sh:
30-desktop.shverifies everylazyos --glyphscodepoint against installed
font charsets first and toleratesdfsg1/dfsg2build-pin hash differences
when 100% of codepoints are present, failing with the exact missing codepoints
if a future font update drops coverage.
Greeter & installer UI/UX polish
- Blinking focus-aware cursors & accessible contrast:
Added sharedInput::render_field(..., focused, blink_on, bg_role, ...)
acrossInstallerScreen,GreeterScreen, andGreeterSettingsScreen: only
the focused input shows the accent bar and 500 ms blinking cursor (solidwhen
LAZYOS_REDUCED_MOTION=1),ListStatefills selection rows uniformly with a
2-space glyph gap, and+ Other/ input boxes useColorRole::Bginside
ColorRole::Surfacecards for Solarized Dark contrast. - Installer
80x24responsiveness, header readability & ChromeOS safety polish:
Compact responsive layouts at80x24, single-line breadcrumbs without
overlap, mouse hit/click support on list rows and buttons, higher-contrast
header titles, sysfstype/scopepower detection for ChromeOSUSBPD
chargers & SBS batteries (ignoring stylus/HIDDevicebatteries),
check_machine_safetyenforcement in headlessapply, dynamic
deviceinfopartition diagram sizing, and Depthcharge boot instructions
covering both"internal disk"menus and legacyCtrl+D. - Clean console power actions in
lazyos-greeter:
GreeterScreen::execute_powernow passes-itosystemctl, redirects
stdin/stdout/stderrso systemd inhibitor notices never corrupt the raw
Ratatui terminal, formats error details cleanly without duplicateexit
prefixes, and ships/etc/polkit-1/rules.d/49-lazyos-greeter-power.rules
authorizing local active_greetd/greetdSleep / Reboot / Shut down actions.
Google Kukui (MT8183) Chromebook Family & Target-Direct Home Profiles
- New target
google-kukui(devices/google-kukui/): Adds Depthcharge image
support for the MediaTek MT8183 Chromebook family (Lenovo IdeaPad Duet
krane,kodama,kakadu,katsu, andjacuzzi-*variants) sharing our
7.2.7-mt81kernel (mediatek-mt81),firmware-atheros+firmware-mediatek,
QCA6174 BT I2S NVM &mt8183_da7219_mALSA UCM2 symlinks, Google Hammer
detachable keyboardkeydbindings,11230000.mmc/11240000.mmcIRQ
affinity, andDSI-1internal panel handling inlazyos. - Developer menu home-folder backup & target-direct streaming:
lazyos-profile/ Developer menu supports optional--include-homebackups
and streams archives directly to the target drive without staging multi-GB
tarballs on the local root filesystem.
Generic ARM64 Reach (arm64-uefi & arm64-extlinux)
Alongside our dedicated Chromebook builds, two generic forky/arm64 targets
open LazyOS up to a wide range of ARM64 hardware using Debian's mainline
linux-image-arm64 (7.2.15+deb14-arm64), synced Devicetree bundles, automatic
apt upgrade kernel refresh (/etc/kernel/postinst.d/zz-lazyos-boot), and
broad multi-vendor firmware (firmware-brcm80211, firmware-qcom-soc,
firmware-atheros, firmware-iwlwifi, firmware-mediatek, firmware-realtek,
firmware-linux-free, firmware-linux-nonfree, firmware-misc-nonfree):
arm64-uefi.img.xz(UEFI Systems, VMs & EDK2 Boards): Ships a 256 MiB
FAT32ESP withsystemd-boot(BOOTAA64.EFI) and full/boot/efi/dtb/
support—ready for ACPI/EBBR ARM64 laptops and workstations, QEMUvirt/
UTM / Parallels virtual machines, and Raspberry Pi 4 / Pi 5 boards running
EDK2/Tianocore UEFI firmware (or U-Boot EFI).arm64-extlinux.img.xz(U-Boot / Devicetree SBCs): Ships a 512 MiB
ext2/bootstarting at16 MiBwith/boot/extlinux/extlinux.conf
(FDTDIR /dtbs/), targeting U-Boot Single-Board Computers (Rockchip,
Allwinner, Amlogic, Raspberry Pi U-Boot, etc.). Boards without U-Boot in
SPI/eMMC can flash their board's U-Boot SPL into the reserved1–16 MiB
pre-partition gap afterdd.
Build & landing site updates
- Rootfs
DEVICE_ARCHexport fix (lazyos-core):
Defined and exportedDEVICE_ARCH="$ARCH"andARCHincore/scripts/lib.sh,
fixing unboundDEVICE_ARCHerrors inbuild-rootfs.sh. - Landing page (
site/index.html):
Updated forv0.5.1with interactive live surface spotlights (Root Menu,
Native Greeter,16-Theme Engine,System Installer) and crispv0.5.1
captures from the live font stack underdocs/screenshots/.
Validation
Verified across core/, desktop/, devices/, and umbrella checks:
cargo fmt --all --check, cargo clippy --workspace --all-targets -- -D warnings,
full cargo test --workspace --all-targets (566 passed, 0 failed, 1 pre-existing
ignored test), ./desktop/scripts/make-glyphs.sh --check
(101 drawn, 0 text), and ./build.sh validate. Local hardware SD build and
flash tested on google-asurada (Google Hayato MT8192, Debian forky/arm64,
kernel 7.2.7-mt81, signed depthcharge FIT kpart verified by futility), and
google-kukui (MT8183), arm64-uefi, and arm64-extlinux release images
verified with xz -t and sha256sum.
Assets
| asset | what it is |
|---|---|
google-asurada.img.xz |
6 GiB Hayato Chromebook image (ChromeOS GPT + signed FIT kpart, /boot, root), ready for dd |
google-kukui.img.xz |
6 GiB Google Kukui / Lenovo IdeaPad Duet MT8183 image (ChromeOS GPT + signed FIT kpart, /boot, root), ready for dd |
arm64-uefi.img.xz |
8 GiB generic ARM64 UEFI disk image (linux-image-arm64 + systemd-boot + multi-vendor firmware for UEFI PCs/laptops, VMs, and EDK2-UEFI boards like Raspberry Pi 4/5), ready for dd |
arm64-extlinux.img.xz |
8 GiB generic ARM64 U-Boot SBC image (linux-image-arm64 + extlinux.conf + /boot/dtbs/ + 1–16 MiB SPL gap for U-Boot boards), ready for dd |
SHA256SUMS |
Combined SHA-256 checksums across all release images |
sha256sum -c --ignore-missing SHA256SUMS
xz -dc <target>.img.xz | sudo dd of=/dev/sdX bs=4M status=progress conv=fsyncLive account: user brunux, password debian, passwordless sudo.
Change the password before daily use. Install onto internal storage from
the booted external card via Alt+Space → Install LazyOS (lazyos installer)
or headlessly with sudo lazyos installer apply --clone --confirm.
What it does not carry
Release artifacts are sanitized and asserted clean by
scripts/lib-dist.sh: no Wi-Fi profiles, no
SSH host keys, no machine-id (regenerated on first boot), and no personal files
beyond the default session configuration.
Known limitations
lazyos-notifyis resident for the session next tocliphistand
workstyleto ownorg.freedesktop.Notifications; it idles without redrawing.- MT8192 external display gamma: OVL1→RDMA1→DPI has no gamma block bound, so
wlsunsetapplies night light on the built-in panel only. - Wayvnc is loopback-only and read-only (
lazyos menu vncprints the SSH
tunnel command). - Camera portal & Xwayland gestures: Flatpak camera portal is absent (native
browsers work), and three-finger Firefox tab swipes require native Wayland. - Fixed image sizes:
google-asurada/google-kukui(6144 MiB) and mainline ARM64 images
(8192 MiB) leave extra card space unallocated unless written via
scripts/write-sd.sh. - Generic ARM64 board firmware/SPL:
arm64-extlinux.img.xzintentionally leaves
the1–16 MiBpre-partition gap empty (SBCs without SPI/eMMC U-Boot must flash
their board U-Boot/SPL there), and Raspberry Pi 4/5 requires RPi EDK2 UEFI firmware
(arm64-uefi) or U-Boot (arm64-extlinux). - MT81 GPU codecs: No hardware video decoder, and Panfrost GL/EGL handles
compositing (PanVK does not support Mali-G57/G72).
v0.5.0
v0.5.0 — frictionless in-window UX and native lazyos-greeter
Everything interactive stays inside its window, anticipates what you opened it
for, and keeps tool actions separate from domain results. At boot, tuigreet
is retired: greetd now launches lazyos-greeter, a native Ratatui login
surface themed from the same palette engine as the desktop session, with its
own defaults editor.
What changed since v0.4.3
Frictionless in-window UX (spec 020)
- Anticipate primary intent on open:
lazyos menu netrenders cached Wi-Fi networks immediately while triggering a
background rescan in-place.lazyos menu bluetoothscans automatically on open and right after power-on.lazyos menu cleancomputes reclaimable cache space asynchronously before
confirmation.lazyos menu calcevaluates expressions live as you type with a movable
cursor and Python-style operators.
- In-window tool lifecycle and transient/persistent notices (
ActionNotice):- Short actions show an in-window braille spinner and status banner instead of
closing the menu and emitting externalnotify-sendtoasts. - Heavy multi-step or streaming tasks run inside
TaskViewwith step checklists,
progress bars, and persistent completion cards. - Routine discovery clears its status on completion, positive transitions
auto-clear after 3 seconds, and actionable errors or space-freed summaries
persist until dismissed.
- Short actions show an in-window braille spinner and status banner instead of
- Separate actions from domain results (
ActionStrip):- Tool-level actions (
Rescan,Share QR,Clean all safe,Mute,Mixer,
Refresh,Save PNG,Settings, …) live in a dedicated horizontal
ActionStrip(Tab/Ctrl+<Key>/ mouse click), leavingListStatestrictly
for domain rows. - Generated QR codes (
menu qrandmenu netShare QR) save high-resolution
PNGs (s/Ctrl+S) under~/Pictures/Screenshots/<YYYY-MM-DD>/.
- Tool-level actions (
- Headless voice-to-text dictation (
dictate,Alt+Ctrl+X):- Holding
Alt+Ctrl+Xrecords push-to-talk and transcribes on release via
taskset -c 4-7 whisper-cli -t 4without stealing Wayland keyboard focus
fromwtype. - A quick tap or Root Menu launch starts hands-free recording with synchronized
stop/cancel controls acrosslazyos-notifyaction buttons, Waybar's
custom/busyspinner (bar-busy), and the Root Menu's dynamic
Stop dictationrow.
- Holding
- UI & build fixes: adopted
footauto-copy defaults, isolated the private
D-Bus test bus intests/notify.rsover abstract/tmp/dbus-*sockets for CI
runners, and polished density-aware card geometry, live window resizing, and
inline previews.
Native lazyos-greeter & Greeter Settings (spec 021)
lazyos-greeterreplacestuigreet0.9.1:- Implemented as the
greetercommand insidelazyos(/usr/bin/lazyos-greeter -> /usr/bin/lazyos,Shape::Full) over a pure-RustUnixStreamJSONgreetd
IPC client (src/greeter/ipc.rs). /usr/bin/lazyos-greeter --sessiongenerates theme-matchedfoot.ini,
sway.conf, and wallpaper PNG assets, then launches minimalsway+
fullscreenfooton VT7—automatically falling back to inline Ratatui TUI on
the raw console ifswayorfootcannot start (--ttyforces the TTY
path).- Supports clickable user pills +
[+ Other]manual login, masked PAM
secrets and multi-step challenges, Wayland/X11.desktopsession discovery
(DesktopNamesexported asXDG_CURRENT_DESKTOP), live theme cycling across
all 16 palettes (F4/Ctrl+T), session switching (F2/Ctrl+S),
Cancel-first confirmations for Sleep / Reboot / Shut down, and safe
in-session testing vialazyos greeter --preview.
- Implemented as the
- Interactive Greeter Settings (
lazyos menu greeter/lazyos greeter settings):- Accessible from Settings → Login screen (Greeter), the Command Palette
(Greeter settings), orCtrl+G/F9/ Settings inside
lazyos greeter --preview. - Configures
/etc/lazyos/greeter.toml(follow_user_theme, fixed/default
theme,show_user_pills,remember_user,default_session,
remember_session,clock_24h24h/12h toggle,show_power_actions, and
customgreetingtext) with inline searchable pickers and Cancel-first reset
to defaults.
- Accessible from Settings → Login screen (Greeter), the Command Palette
Validation
The rootfs and distributable image are built on the Chromebook from this
repository (scripts/build-rootfs.sh, install-kernel.sh,
install-swayfx.sh, install-workstyle.sh, install-lazyos.sh, and
scripts/make-release.sh): mainline Linux 7.2.7 (7.2.7-mt81), swayfx 0.6
on scenefx 0.5, workstyle 0.8.2, debootstrap for Debian forky/arm64,
and a signed depthcharge FIT kpart (futility: dev-signed FIT, preamble 2.2, body verification succeeded). The image, its .img.xz, the root filesystem
tarball, and the standalone .kpart are sanitized and asserted clean by
scripts/lib-dist.sh, and SHA256SUMS covers
the four disk artifacts.
VERSION is 0.5.0, matching lazyos --version. All 530 workspace tests
pass (cargo test --workspace --all-targets, with 1 pre-existing ignored test
in tests/files.rs), and cargo fmt --all --check and
cargo clippy --workspace --all-targets -- -D warnings are clean.
Assets
| asset | what it is |
|---|---|
google-asurada.img.xz |
6 GiB disk image (3.3G data): the three ChromeOS GPT partitions (kernel, /boot, root), ready for dd |
google-asurada-rootfs.tar.zst |
the same root filesystem as a tarball (with /boot inside), for writing your own card with scripts/write-sd.sh |
google-asurada.vmlinuz.kpart |
the signed FIT kernel partition of that image; it embeds the image's root=UUID, so it belongs to this image and no other |
SHA256SUMS |
SHA-256 of the three assets |
sha256sum -c SHA256SUMS
xz -dc google-asurada.img.xz | sudo dd of=/dev/mmcblk1 bs=4M conv=fsyncOn the Chromebook: developer mode, crossystem dev_boot_usb=1 dev_boot_signed_only=0,
insert the card, and pick external disk in the firmware menu. It boots
into lazyos-greeter on VT7 — user brunux, password debian, passwordless
sudo. Change the password before using it for anything real.
scripts/install-emmc.sh installs it to internal storage, and on the card
Alt+Space → Install LazyOS (or lazyos installer) is the same call with
interactive pre-flight and confirmation gates.
What it does not carry
The artifact is sanitized and asserted clean by
scripts/lib-dist.sh: no Wi-Fi profiles (a released
image knows no network and asks for one), no SSH host keys and no machine-id
(both generated on first boot, so every installation has its own identity), no
OpenCode sign-in, and no personal files beyond the session configuration this
repository ships.
Known limitations
lazyos-notifyis resident for the session, because a notification
daemon is what owns the bus name; it is an agreed exception next to
cliphist's watcher andworkstyle, and idles without redrawing when no
card is up.- The night light cannot reach the external monitor. MT8192's second display
path (OVL1→RDMA1→DPI) has no gamma block bound, sowlsunsetcannot set
gamma on an external 1080p monitor. - The camera portal is not implemented, so Flatpak apps do not see a
camera while Firefox and native apps work. - The three-finger tab swipes do nothing when Firefox runs on Xwayland
(MOZ_ENABLE_WAYLAND=0): the criteria need anapp_id, and an X11 window has
none. - The profile archive does not carry OpenCode's sign-in (it lives in
~/.local/share/opencode/opencode.db), and a Firefox profile copied while
running is each database at its last checkpoint. - Wayvnc is loopback-only and read-only (
lazyos menu vncshows the SSH
tunnel command). - The installer refuses to run from the disk it would overwrite: install to
eMMC from a booted microSD card. - The image is 6 GiB (
IMAGE_SIZE_MIB=6144), leaving unused space on larger
cards unless written viascripts/write-sd.sh. The tarball's/etc/fstabis
the unconfigured one left by the build. - Artifacts are not byte-reproducible yet (FIT timestamp, filesystem UUIDs).
- There is no hardware video decoder, and Vulkan is not usable (PanVK answers
Mali-G57 not supported); rendering uses EGL and Panfrost.
Upstream
Vendored from pmaports commit 0e458a2417d6f5ed61c7b70621d5632e30136091
(2026-10-15), mainline Linux 7.2.7, swayfx 0.6 on scenefx 0.5, workstyle 0.8.2,
OpenCode 2.1.3.
v0.4.3
v0.4.3 — one binary, one theme engine, no rofi
The session is now entirely LazyOS. The last rofi surfaces and the mako
notifier are retired: every menu, picker and window is a subcommand of
/usr/bin/lazyos, the notifications are drawn by lazyos-notify on a
layer-shell surface, the installer is a full-screen TUI wizard, and the theme
engine carries 16 palettes with a live picker that repaints the desktop.
What changed since v0.4.2
The framework is the session (specs 014, 017)
rofiis retired in full. The package leftuis/sway/packages.list, and
lib-rofi.sh,bar-pickand~/.config/rofi/are deleted. The ~55 keyboard
shortcuts and the bar's panel actions did not change: each old name
(rofi-files,rofi-power,bar-menu, …) is a symlink to/usr/bin/lazyos,
which resolves a command fromargv[0]or from the words after it. The
command table is 52 rows, 50 installed names, and--help/--symlinksprint
the same table the checks read.- The final 10 interactive surfaces are native: network, places, clean,
kill, download, layout, file actions, agents, translate and dictation. Each
filters as you type with case folding, acts on an enum instead of a shell
string, and offers headless query flags (--status,--dry-run,--rows,
--languages) for waybar and scripts. - 13 theme surfaces are generated from
theme.toml(foot, waybar, mako-free
notifications, starship, btop, lazygit, nvim, fzf, swaylock, greeter, the sway
wallpaper/frame drop-in and both GTK stylesheets), so a new palette is one
TOML file and no code.
Notifications are LazyOS (spec 019)
lazyos-notifyreplacesmako. It owns
org.freedesktop.Notificationson the session bus and draws antialiased,
rounded cards with soft shadows on a layer-shell surface anchored top-right
under the bar. Urgency borders and dots, action buttons, progress tracks and
theme pictures are drawn withtiny-skia; the pointer is released when the
stack is empty, so nothing is occluded.- History without a daemon to ask: cards are logged to
$XDG_STATE_HOME/lazyos/notify/history.jsonland read back by
lazyos menu notify(Alt+Ctrl+N). Do-not-disturb is one file under
$XDG_RUNTIME_DIR, and critical alerts still pass through. - The OSD is one HUD card: volume and brightness draw a single card with a
level bar instead of a stack of toasts, and the theme's own icons.
The installer is a wizard (spec 018)
lazyos installeris a full-screen six-phase wizard: pre-flight (it
refuses when the root filesystem is the eMMC it would overwrite),
localization (searchable IANA timezones, locale, keyboard layout with a
keypress test), account (POSIX-validated user, masked password, hostname),
a visual ChromeOS GPT diagram with a confirmation that defaults to Cancel and
unlocks only after the disk's name is typed, a TaskView with an overall gauge,
six phases and a streaming log from a detached worker, and a completion
screen.--checkand--dry-runverify the safety rules and simulate the
install without touching storage.
Themes: 16 palettes, a live picker, live terminals
- Eight new Omarchy ports: Catppuccin Latte, Dracula, Flexoki Light,
Hackerman, Lumon, Matte Black, Omacon and One Dark, next to the existing
Solarized Dark, Catppuccin Mocha, Tokyo Night, Rose Pine, Nord, Gruvbox,
Everforest and Kanagawa. lazyos menu theme(Alt+Shift+C) is a dual-pane browser: the left pane
filters and marks the active theme, the right pane renders a live preview
(the 16 ANSI swatches, the semantic role pills, a simulated bar, card and
prompt) and verifies WCAG contrast.wcycles wallpapers,ppeeks at the
desktop with the candidate palette and rolls back on Escape, Enter commits and
reloads the session.- Running terminals follow the theme: the active palette is pushed to open
footwindows through OSC sequences, so a theme change repaints the
terminals that are already open. - Every theme has a generated wallpaper (gradient plus the wordmark, the
accent in the mark), cached per theme, and the greeter and lock screen consume
the same palette.
The local model is Qwen3.5-0.8B
lazyos-model(Alt+Ctrl+M) runs Qwen3.5-0.8B (weight-space
programming, Q4_K_M, 517 MB) in a floating window: 17.3 tok/s generation
and 92 tok/s prefill on the four Cortex-A76 cores, 1.2 GB RSS at 4k
context, so it coexists with the browser. Weights are fetched and verified
against a pinned SHA-256; they are never committed or built.
Fixes worth naming
- Monospace queries resolve to text fonts again. Upstream's
10-nerd-font-symbols.confaliased 50+ monospace families to the
DFSG-stripped symbol font, so web pages and code blocks rendered as tofu or
blank lines; LazyOS removes the alias, shipsfonts-liberationand installs
its own monospace fallback. Terminals still name the symbol font explicitly. - Bluetooth discovery is asynchronous and scans on demand, so the panel
opens at once and stops scanning when it closes. - Region capture, OCR, QR and the colour picker detach from the menu before
slurpgrabs the screen, so the floating window is gone from the shot. - The Developer menu resolves the profile and
PATH, uses structured
pickers for restore, and the busy notifications take their subcommands. - Wi-Fi scanning is cached, waybar's JSON escapes are fixed, and detached
children no longer inheritLAZYOS_UI. - Test runs suppress desktop notifications.
Validation
The tree builds with scripts/build.sh on the card's own port: Linux 7.2.7,
swayfx 0.6 on scenefx 0.5, workstyle 0.8.2, debootstrap for forky, and the
kpart signed with the vboot developer keys — futility show answers
Body verification succeeded. The image, its xz, the root filesystem tarball
and the kpart are sanitized and asserted clean by scripts/lib-dist.sh, and
SHA256SUMS covers the four.
lazyos --version prints 0.4.3, the same string as the committed VERSION.
All 497 tests pass (cargo test --workspace), and cargo fmt --all --check
and cargo clippy --workspace --all-targets -- -D warnings are clean.
Assets
| asset | what it is |
|---|---|
google-asurada.img.xz |
6 GiB disk image: the three ChromeOS GPT partitions (kernel, /boot, root), ready for dd |
google-asurada-rootfs.tar.zst |
the same root filesystem as a tarball (with /boot inside), for writing your own card with scripts/write-sd.sh |
google-asurada.vmlinuz.kpart |
the signed FIT kernel partition of that image; it embeds the image's root=UUID, so it belongs to this image and no other |
SHA256SUMS |
SHA-256 of the three assets |
sha256sum -c SHA256SUMS
xz -dc google-asurada.img.xz | sudo dd of=/dev/mmcblk1 bs=4M conv=fsyncOn the Chromebook: developer mode, crossystem dev_boot_usb=1 dev_boot_signed_only=0,
insert the card and pick external disk in the firmware menu. It comes up to
a greetd prompt — user brunux, password debian, passwordless sudo.
Change the password before using it for anything real. scripts/install-emmc.sh
installs it to internal storage, and on the card Alt+Space → Install LazyOS
(or lazyos installer) is the same call with the questions asked first.
What it does not carry
The artifact is sanitized and asserted clean by
scripts/lib-dist.sh: no Wi-Fi profiles (a released
image knows no network and asks for one), no SSH host keys and no machine-id
(both generated on first boot, so every installation has its own identity), no
OpenCode sign-in and no personal files beyond the session configuration this
repository ships.
Known limitations
lazyos-notifyis resident for the session, because a notification
daemon is what owns the bus name; it is the third agreed exception to the
no-daemon rule, next tocliphist's watcher andworkstyle, and it idles
without redrawing when no card is up.- The night light cannot reach the external monitor. MT8192's second display
path (OVL1→RDMA1→DPI) has no gamma block bound, somodetest -M mediatek -p
listsGAMMA_LUTon the 1366x912 CRTC and nothing on the 1920x1080 one;
wlsunsetlogsgamma control of output … failedand the monitor keeps its
own colour temperature. - The camera portal is not implemented (there is no access backend), so a
Flatpak application sees no camera while Firefox and other native programs
work. This is a limitation, not a bug to wait on. - The three-finger tab swipes do nothing when Firefox runs on Xwayland
(MOZ_ENABLE_WAYLAND=0): the criteria need anapp_id, and an X11 window has
none. - The profile archive does not carry OpenCode's sign-in (it lives in
~/.local/share/opencode/opencode.dbwith the session history), and a Firefox
profile copied while the browser is open is each database at its last
checkpoint. - Wayvnc is loopback-only and read-only: the way in is an
ssh -Ltunnel
(lazyos menu vnchas the command on a row), and the menu's input is
deliberately off. - The installer refuses to run from the disk it would overwrite, which is the
correct answer when it is opened on the eMMC install; the installation is made
from the microSD, which can always be selected again in the firmware menu. The
copy cannot be stopped: killingrsyncormkfsleaves a disk that looks
written and is not. - The image is 6 GiB (
IMAGE_SIZE_MIB=6144), which leaves about 2 GiB in the
root partition; a larger card keeps the space afterp3unused unless the
tarball is written withscripts/write-sd.sh, which sizesp3to the whole
card. The tarball's/etc/fstabis the unconfigured one the build leaves
behind. - Artifacts are not byte-reproducible yet (FIT timestamp, filesystem UUIDs).
- The battery gauge's chemistry and time-to-empty pr...
v0.4.2
v0.4.2 — eight themes, generated wallpapers and a themed greeter
The session now has eight built-in themes, each with its own generated
wallpaper, and the greeter (tuigreet) and lock screen (swaylock) consume the
active theme — no code changes when a theme is added.
What changed since v0.4.1
-
Eight themes as pure data: Solarized Dark (default, brand), Catppuccin
Mocha, Tokyo Night, Rose Pine, Nord, Gruvbox, Everforest Dark and Kanagawa.
Each is atheme.tomlwith the 16 ANSI colours, the semantic roles
(background, text, accent, danger, …), an accent pair and a gradient pair.
Adding a theme is one TOML file — the generator (lazyos-theme) parses it,
derives missing roles, checks the contrast floor (4.5:1 fortext, 3:1 for
signal roles) and refuses the theme if it cannot be read. -
Generated wallpapers: Each theme gets a deterministic wallpaper at build
time — a vertical gradient from the theme's background to a slightly lighter
version, with the LazyOS wordmark centered. Thezof the mark uses the
theme's accent colour, the_cursor uses the orange (warn) accent. Wallpapers
are cached at~/.cache/lazyos/wallpapers/andtheme setgenerates them on
the first switch. The first wallpaper becomes the desktop background and the
lock screen image. -
Themed greeter: The greeter (Debian's tuigreet 0.9.1, which has no
--config
support) receives its colours through generated flags in
~/.config/lazyos/greeter. The wordmark is rendered in the theme's colours.
No code changes when a theme is added — the template is data. -
Themed lock screen: swaylock reads its colours from the theme palette
(ring colours for the indicator, text colours for the prompt, the wallpaper
from the theme's wallpaper list). The photograph (mountains.jpg) remains the
default lock image for the brand; themes provide their own wallpaper. -
Theme menu preview:
lazyos menu theme(Alt+Shift+T) renders a live
preview with a 128px sixel wallpaper thumbnail for the highlighted theme.
The thumbnail is generated alongside the full wallpaper and decoded once. -
Pure data theme engine: The engine owns every surface — foot, waybar,
mako, rofi, btop, lazygit, nvim, fzf, swaylock, the sway wallpaper and frame
drop-in, the greeter flags, starship — all generated from the single
theme.toml. Writes are atomic (<target>.newthen rename), idempotent (a
secondtheme setis a no-op), and a hand edit is reported not silently
overwritten (--forcereplaces it). -
Manual page updated:
04-software.md§ Themes documents the eight
themes, the wallpaper cache, the greeter and lock screen theming, and the
idempotent write rules. -
AGENTS.md bullet added: Documents the pure data theme engine and the
eight built-in themes.
Validation
The tree builds with scripts/build.sh on the card's own port: Linux 7.2.7,
swayfx 0.6 on scenefx 0.5, workstyle 0.8.2, debootstrap for forky, and the
kpart signed with the vboot developer keys — futility show answers Body verification succeeded. The image, its xz, the root filesystem tarball and the
kpart are sanitized and asserted clean by scripts/lib-dist.sh, and
SHA256SUMS covers the four.
All tests pass: 450+ (cargo test --workspace), cargo fmt --all --check
clean, cargo clippy --workspace --all-targets -- -D warnings clean. Golden
fixture files updated for the greeter and swaylock surfaces across all eight
themes.
scripts/check-system.sh on the built image reports the new theme surfaces
(greeter, swaylock, wallpaper) as present and correct.
Assets
| asset | what it is |
|---|---|
google-asurada.img.xz |
6 GiB disk image: the three ChromeOS GPT partitions (kernel, /boot, root), ready for dd |
google-asurada-rootfs.tar.zst |
the same root filesystem as a tarball (with /boot inside), for writing your own card with scripts/write-sd.sh |
google-asurada.vmlinuz.kpart |
the signed FIT kernel partition of that image; it embeds the image's root=UUID, so it belongs to this image and no other |
SHA256SUMS |
SHA-256 of the three assets |
sha256sum -c SHA256SUMS
xz -dc google-asurada.img.xz | sudo dd of=/dev/mmcblk1 bs=4M conv=fsyncOn the Chromebook: developer mode, crossystem dev_boot_usb=1 dev_boot_signed_only=0, insert the
card and pick external disk in the firmware menu. It comes up to a greetd prompt — user
brunux, password debian, passwordless sudo. Change the password before using it for
anything real. scripts/install-emmc.sh installs it to internal storage, and on the card
Alt+Space → Install LazyOS is the same call with the questions asked first.
What it does not carry
The artifact is sanitized and asserted clean by scripts/lib-dist.sh:
no Wi-Fi profiles (a released image knows no network and asks for one), no SSH host keys and no
machine-id (both generated on first boot, so every installation has its own identity), no
OpenCode sign-in and no personal files beyond the session configuration this repository ships.
Known limitations
- The night light cannot reach the external monitor. MT8192's second display path
(OVL1→RDMA1→DPI) has no gamma block bound, somodetest -M mediatek -plists
GAMMA_LUTon the 1366x912 CRTC and nothing on the 1920x1080 one;wlsunsetlogs
gamma control of output … failedand the monitor keeps its own colour
temperature. - The camera portal is not implemented (there is no access backend), so a
Flatpak application sees no camera while Firefox and other native programs work.
This is a limitation, not a bug to wait on. - The three-finger tab swipes do nothing when Firefox runs on Xwayland
(MOZ_ENABLE_WAYLAND=0): the criteria need anapp_id, and an X11 window has
none. - The profile archive does not carry OpenCode's sign-in (it lives in
~/.local/share/opencode/opencode.dbwith the session history), and a Firefox
profile copied while the browser is open is each database at its last
checkpoint. - Wayvnc is loopback-only and read-only: the way in is an
ssh -Ltunnel
(rofi-vnchas the command on a row), and the menu's input is deliberately
off. - Install LazyOS refuses to run from the disk it would overwrite, which is the
correct answer when the menu is opened on the eMMC install; the installation is
made from the microSD, which can always be selected again in the firmware menu.
The copy cannot be stopped: killingrsyncormkfsleaves a disk that looks
written and is not. - The image is 6 GiB (
IMAGE_SIZE_MIB=6144), which leaves about 2 GiB in the
root partition; a larger card keeps the space afterp3unused unless the
tarball is written withscripts/write-sd.sh, which sizesp3to the whole
card. The tarball's/etc/fstabis the unconfigured one the build leaves
behind. - Artifacts are not byte-reproducible yet (FIT timestamp, filesystem UUIDs).
- The battery gauge's chemistry and time-to-empty properties are upstream failures;
waybar reads the capacity directly, which works. - There is no hardware video decoder, and Vulkan is not usable (PanVK answers
Mali-G57 not supported); the session renders through EGL and Panfrost, and
video is CPU work.
Upstream
Vendored from pmaports commit 0e458a2417d6f5ed61c7b70621d5632e30136091 (2026-10-15), mainline
Linux 7.2.7, swayfx 0.6 on scenefx 0.5, workstyle 0.8.2, OpenCode 2.1.3.
v0.4.1 — the rest of the machine
v0.4.1 — the rest of the machine
A patch number, but the largest batch since the port first booted: this is the
release where the session caught up with the hardware around it. A second screen
on either Type-C port and the menu that arranges it; the camera that was a USB
device all along; the translation of the selected text; the screen reachable
read-only from another machine; the idle screen that finally ends on a mouse move
and stops holding the lock chain behind it; and the Developer menu, which turns
the account into one encrypted archive on a stick.
The kernel and the compositor are the ones v0.4.0 shipped — Linux
7.2.7 with the same configuration, swayfx 0.6 on scenefx 0.5 — with one
device-tree patch this release adds for the external display.
What changed since v0.4.0
- A second screen, on both ports. The port shipped no external-display
pipeline at all:dpi@14016000was disabled and there was no ANX7625, so the
kernel created one connector andcard1-DP-1did not exist.
kernels/mediatek-mt81/patches/mt8192-asurada-external-display.patchadds the
three nodes ChromeOS's asurada DTSI carries — the DPI output with its 16 pins
at 6 mA, the bridge oni2c@11d00000with itspp*_dpbrdgrails and GPIO
8/9/7, and the DPI input endpoint — to the shared asurada dtsi. The bridge then
has one DP transmitter and two downstream Type-C ports, and
TCPC_SWITCH_0/1(7-bit0x2coni2c-7) pick which one it reaches:0x21
is the left port,0x12the right, and the chip powers up on the left.
Mainline registers a typec port and no mux, so nothing ever wrote them:
measured, a monitor on the right reported HPD, answered EDID over AUX and got
1920x1080@60 while the panel showed its no-signal pattern, and the same monitor
on the left worked./usr/local/sbin/lazyos-dp-mux, run by a udev rule when a
port's DisplayPort alt mode appears, writes the registers withi2cset -f
after the page sync ChromeOS'si2c_access_workaround()does. The timing is
the feature: the connector's hotplug arrives before the alt-mode device (46 ms,
measured) and the chip trains the link when it is enabled, so a write afterwards
retrains nothing. A resume is the half udev cannot see — the bridge powers down
with the pipeline and returns to its default crosspoint — so
~/.config/bin/lazyos-dp-resumeruns from the idle chain'safter-resumeand
does the crosspoint plus one 1280x720 modeset, which is what retrains the link
(a disable/enable would move the workspace to the internal panel). Where it
sits is Settings → Display arrangement (rofi-display): right, left, above,
below, mirrored, resolution and scale, with--statusas the single copy of the
answer the Settings row reads. The panel is never moved, only the monitor, and
every arrangement is also written to~/.config/sway/config.d/40-display.conf,
because a runtime position dies with the session. Only the monitor can leave
a picture-less machine when the cable comes out, so the no-monitor branch brings
the panel back andAlt+Ctrl+Shift+Drunsrofi-display --panel-onblind for
the case where every output is off.wdisplaysis the manual row. - The camera needed no driver, only a window. The Hayato's camera is a USB
UVC device on the internal hub (0408:30d5 Quanta USB2.0 HD UVC WebCam), so
uvcvideobinds it and udev creates/dev/video0; the tablet'svideo2/video3
are the SoC's encoder and decoder, which is whylazyos-cameraselects the node
by driver and never by number. The device tree carries no MIPI sensor, so
the rear camera a detachable is expected to have is not a missing module — it
has no sensor to drive. The window isguvcview(GTK3, so it inherits
gtk-3.0/gtk.css, and it brings the camera's own exposure, gain and white
balance controls); the wrapper keeps its photos out of$HOME(into
~/Pictures/Camera/~/Videos), forces-g gtk3 -r sdlbecause guvcview
remembers a headless run and would reopen with no window and the device held,
raises a card when the window dies at once, and focuses an existing instance
instead of opening a second one. The camera portal stays closed (this image has
no access backend, so the portal logs one line per session); native programs do
not care: Firefox reads V4L2 directly (verified: a 640x480 stream at 30 fps
with the portal missing), so a video call works while a Flatpak app sees no
camera. Rows: the root menu's Camera,org.lazyos.camera.desktopand a
camera-webicon in the LazyOS theme. - Translate is a key, not a right-click (
Alt+Ctrl+T). The mouse selection —
the primary selection, which a drag already writes — or the clipboard goes into
one language (target=enunless~/.config/lazyos/translate.confsays
otherwise) and the answer is copied; a long answer opens in a read window. The
engine was chosen by measurement, not taste: Google'stranslate_a/single
answers this machine with a captcha page, while
clients5.google.com/translate_a/t?client=dict-chrome-exanswers plain JSON,
auto-detects the source and echoes it, so the card can saySpanish → English
and an English selection can answer Already English. It takes GET only
(POST 302s to/sorry), which is why the selection rides in the URL and is
capped at 3000 characters; MyMemory is the fallback in 450-character pieces, and
when neither answers the card says so instead of showing half a translation.
Settings → Translate is the same list astranslate configfrom a terminal.
A busy card with a stop button, both endpoints, and nothing resident. - The screen can be looked at from another machine, read-only and only over
ssh:wayvnc(312 kB + libneatvnc 218 kB + libaml 82 kB), started and stopped
fromrofi-vnc(Settings → Share this screen, and the root menu). It binds
127.0.0.1 only — wayvnc 0.10 authenticates only through a certificate, a
private key and a password file this image does not ship, and a server on the
network address would be an unauthenticated desktop on every network the
machine joins; the loopback address is reached through the ssh login the image
already answers, which makes the tunnel the authentication — and it runs
--disable-input, because remote input would arrive as a keyboard nobody
can attribute.nohupso the server outlives the menu and$!is wayvnc's own
pid, pid and log in$XDG_RUNTIME_DIR/lazyos-vnc, the pid trusted only after
kill -0and/proc/PID/commsayswayvnc, and anss -ltnH "sport = :5900"
read-back instead of believing the pid. The bar'scustom/vnceye appears while
it runs and a right click stops it. No busy card on purpose: a card older than
five minutes is dropped as stale, and a share can last an afternoon. - Agents (
Alt+Ctrl+Shift+A): launch, install (npm install -g --prefix ~/.local, with--allow-scriptsbecause npm 12 blocks the postinstall that
picks OpenCode's platform binary), pick a default, and keep accounts. An account
is a directory under~/.local/share/lazyos/agents/<agent>/<name>used through
the variable the CLI documents —CLAUDE_CONFIG_DIRfor Claude Code,
CODEX_HOMEfor Codex; Gemini and Copilot have no such variable and the menu
says so instead of pretending. Every row carries a glyph and a display/key TSV
maps the rendered row back to its action. The root menu's AI group now opens
with Agent session (rofi-agents --default, in~/Work), and with no CLI
at all it raises a card instead of opening a terminal that closes at once.
OpenCode is the one agent the image ships, at~/.opencode/bin:
opencode upgraderewrites the binary in place only from there and answers
installation method not found anywhere else (measured on 2.1.3), so
tools/opencode/pins the arm64 tarball of the npm platform package, verifies
its SHA256, androotfs-setup.shextracts it into the user's home. The image is
signed out — the credentials live in the data directory, which
lib-dist.shexcludes from anything published. - The idle screen ends on the pointer, and the chain stops waiting for it.
A pty hears the mouse only when the program inside asks for it, so the
dismissal is\033[?1003h\033[?1006h(all-motion tracking, SGR encoding; foot
implements both), printed with the raw-mode setup and turned off from anEXIT
trap so a--runin a real shell does not leave escapes in the prompt. Without
it the loop saw key bytes only — motion and clicks were the terminal's own
business, which is exactly the report ("the screensaver does not end with mouse
movement"). Andswayidle -wwaits for each timed command in its own event
loop (main.c,cmd_exec→waitpid), so a 150 s command that stayed in the
foreground held the 300 s lock, the 360 s DPMS, theresumelines and
before-sleepfor as long as the wordmark animated: a session left alone never
locked and the panel never went dark. The launcher now starts its foot and
returns (foot … </dev/null &) — measured on a headless sway, with-wa
timeout 1 'sleep 100'kept a 2 s timeout from firing within 5 s, and without
-wit fired at 2 s.swaylockis pointer-blind on purpose (seat.canswers
motion, buttons and the wheel with// Who cares), so typing is the unlock and
a mouse move at five minutes only turns the panel back on. - The Developer menu (
Alt+Ctrl+D, the root menu's Developer row and
org.lazyos.dev.desktop): export my profile, restore a profile, save
a diagnostics bundle. The archive istar --zstdencrypted with gpg
symmetric AES256 — a tar because the sticks are exFAT, which drops modes and
symlinks (a copiedid_ed25519without its0600is a key ssh refuses), and
encrypted because it carries~/.ssh,~/.gnupgand the Firefox password
store; the pas...
v0.4.0 — the z_ mark and Install LazyOS
v0.4.0 — the z_ mark and Install LazyOS
A minor release. The boot chain, the kernel and the compositor are the ones
v0.3.1 shipped; what changed is the project's face and the one menu
that writes a disk. The arcade button gives way to the z_ prompt, drawn in the
session's own Solarized and carried on every surface the system can draw; and the
root menu gains Install LazyOS, a front end to the installer this port already
has that reports the machine, hides itself when a write would be unsafe and reads
the result back instead of believing that the copy worked.
What changed since v0.3.1
- The mark is the
z_prompt. A cyanzand an orange cursor on a base02
tile, with the wordmarklazyOS_. The cursor orange is#e8743b, lifted from
#cb4b16so it passes 4.5:1 on base03 and can be used as text rather than only
as an accent.brand/README.mdis the brand itself - the mark, the wordmark,
the palette, the type and the rules - andbrand/lazyos.svgis the one source
every other file is rendered from. - The wallpaper is a keyboard in the dark with one lit key carrying the mark.
1366x912, the panel's own mode, so nothing is resampled; the wordmark,
lazy by designand the arcade continue line sit bottom left. The lock screen
keepsmountains.jpg: the desktop is the surface the brand owns, and the
photograph is what is up when nobody is looking. - Each surface asks for the form it can draw. The PNGs and the SVG where
pictures go (the launcher and About icon, the GTK theme's scalable copy, the
wallpaper), thez_in full and half blocks in fastfetch's logo and on the idle
screen (box and block characters lay out the same in every monospace font), and
plain text in/etc/issue. The idle screen centres line by line, so every row of
the art is padded to one width. scripts/make-brand.shrenders all of it withrsvg-convert, and ImageMagick
is no longer needed for the brand. The outputs are committed, because
build-rootfs.shstagesgit archive HEADand a build host without
rsvg-convertstill has to build; this release is the rerun of the script on
the build host thate707026left as a note, so the committed pictures are
librsvg's output of the same SVGs.- The project has a landing page:
site/plus.github/workflows/pages.yml,
published to GitHub Pages on every push that touchessite/,brand/or the
screenshots. JetBrains Mono is self-hosted (no third-party font request), and
the page carries its Open Graph and Twitter cards, JSON-LD,robots.txt,
sitemap.xml, a 404 page, the web manifest and the touch icon. The social
preview isbrand/social-preview.svg, 1280x640. - Install LazyOS is a front end, not a second installer (
rofi-install, the
root menu's red row andorg.lazyos.install.desktop). The target is fixed
(/dev/mmcblk0; a list of disks is a list of ways to erase the wrong one) and
the menu only reads before it offers anything: the room the copy needs (dfon
/and/boot, minus a build tree), the charger and the battery (below half
says so, below 20 % on battery refuses),/lib/modules/<release>+
vmlinuz-+initrd.img-(the kpart is built after the copy), the installer's
tools and asudothat would not prompt. Those rows carrynoneas their key,
so Enter re-checks instead of closing, which is what makes "Cannot install yet"
an honest row and not a dead one. Cancel is the first row and it is selected,
and the last gate is the disk's own name typed in full (mmcblk0). - The runner is the only writer, and what it writes with is the documented
installer.setsid lazyos-install-run TARGET REPOcalls
scripts/install-emmc.shonce withCONFIRM=yesafterenvand nothing else;
check-system.shFAILs ifparted,mkfs,cgpt,rsyncorddever appears
in that file, which is what makes "byte for byte the documented install" a test
instead of a promise. Around the call it does exactly the two things
disk_release()refuses to start with: stopudisks2and mask it for the
length of the run (stopping alone does not stop D-Bus from mounting p2/p3
mid-write) and unmount every mounted partition of the target. A failure in
either aborts before a byte is written, a trap restoresudisks2on every exit
path, andsystemd-inhibitholds a sleep lock meanwhile. - The copy is neither stoppable nor believed. A killed copy leaves a disk half
written, so no stop button is offered (like Format a disk and the apt install);
progress is the installer's own==>lines turning intobusycards under a
bar spinner, and the log can be opened live in a floatedfoot
(lazyos-install-log,less -R +Fwhile it runs, over
$XDG_STATE_HOME/lazyos/install-<timestamp>.log). Success is read back: the
threePARTLABELs one at a time andfutility showon p1 must say
Body verification succeeded; a failure carries the installer's last
ERROR:line, ANSI-stripped and un-prefixed, becausefail()puts one back.
Reopening the menu shows what the last run left (running,failed,
did-not-finish), and a stale pid is not taken for a running install. - The session gained the
lazyos-installwindow and the icon language that goes
with it:UI_I_SHIELDandUI_I_CHECKinlib-rofi.sh, the
system-software-installicon in the LazyOS theme, the drop-in that floats the
log, and05-system.md§ Install LazyOS in the manual.
Validation
The install path was exercised end to end on a loop device carrying the real pmOS
layout and a signed kpart copied from this machine's own kernel partition: the
success path (status done, the three labels and Body verification succeeded),
the failure path, the udisks2 window (inactive/masked-runtime while writing,
active/enabled after, no leftover mask), and the wizard's blocked, Enter-rechecks,
wrong-name, right-name and running-menu paths. That is how the empty "$@" that
made bash read DEVICE= as the command name - Failed to execute 'DEVICE=' - and
the doubled ERROR: prefix on the failure card were found. The seven install
checks of check-system.sh pass in the same harness.
The brand is a visual change and was checked as one: the four renders are the
output of scripts/make-brand.sh on this build host, and the two text forms come
out byte-identical. The card written from this build is the first real installation
test; docs/test-checklist.md § Install LazyOS lists what
to try, and scripts/check-system.sh runs on the booted card as always.
Assets
| asset | what it is |
|---|---|
google-asurada.img.xz |
6 GiB disk image: the three ChromeOS GPT partitions (kernel, /boot, root), ready for dd |
google-asurada-rootfs.tar.zst |
the same root filesystem as a tarball (with /boot inside), for writing your own card with scripts/write-sd.sh |
google-asurada.vmlinuz.kpart |
the signed FIT kernel partition of that image; it embeds the image's root=UUID, so it belongs to this image and no other |
SHA256SUMS |
SHA-256 of the three assets |
sha256sum -c SHA256SUMS
xz -dc google-asurada.img.xz | sudo dd of=/dev/mmcblk1 bs=4M conv=fsyncOn the Chromebook: developer mode, crossystem dev_boot_usb=1 dev_boot_signed_only=0, insert the
card and pick external disk in the firmware menu. It comes up to a greetd prompt — user
brunux, password debian, passwordless sudo. Change the password before using it for
anything real. scripts/install-emmc.sh installs it to internal storage, and on the card
Alt+Space → Install LazyOS is the same call with the questions asked first.
What it does not carry
The artifact is sanitized and asserted clean by scripts/lib-dist.sh:
no Wi-Fi profiles (a released image knows no network and asks for one), no SSH host keys and no
machine-id (both generated on first boot, so every installation has its own identity), and no
personal files beyond the session configuration this repository ships.
Known limitations
- Install LazyOS refuses to run from the disk it would overwrite, which is the
correct answer when the menu is opened on the eMMC install: it says so and
stops. The installation is made from the microSD, which can always be selected
again in the firmware menu. - The install cannot be stopped. Killing
rsyncormkfsleaves a disk that
looks written and is not, so the card explains that the copy is not interruptible
instead of offering a button that lies. - The image is 6 GiB (
IMAGE_SIZE_MIB=6144), which leaves about 2 GiB in the
root partition; a larger card keeps the space afterp3unused unless the
tarball is written withscripts/write-sd.sh, which sizesp3to the whole card. - The tarball's
/etc/fstabis the unconfigured one the build leaves behind:
write-sd.shgenerates the real one. - Artifacts are not byte-reproducible yet (FIT timestamp, filesystem UUIDs).
- The battery gauge's chemistry and time-to-empty properties are upstream failures;
waybar reads the capacity directly, which works. - There is no hardware video decoder, and Vulkan is not usable (PanVK answers Mali-G57 not
supported); the session renders through EGL and Panfrost, and video is CPU work.
Upstream
Vendored from pmaports commit 0e458a2417d6f5ed61c7b70621d5632e30136091 (2026-10-15), mainline
Linux 7.2.7, swayfx 0.6 on scenefx 0.5.
v0.3.1 — tablet mode folds both ways
v0.3.1 — tablet mode folds both ways
A maintenance release. The boot chain, the kernel and the compositor are the ones
v0.3.0 shipped; what changed is the session, and the largest change is
the one the 2026-10-22 card found: tablet mode could be entered by folding the
keyboard back and not left by folding it forward again.
What changed since v0.3.0
- Folding the keyboard back exits tablet mode again.
cros_ec_buttonsreports
the power and volume keys and the tablet switch on one libinput device, and
wlroots builds both halves over the same handle - soinput type:keyboard events disabledsuspended the switch with the keys, andtablet:offnever arrived.
The mode now switches the typing keyboards off one identifier at a time
(cros_ecand keyd's virtual keyboard) and leaves every identifier a switch
also carries alone, which is why the volume keys keep working in tablet mode and
the mode can always be left.check-system.shFAILs on a type-wide disable and
on a suspended switch, and the troubleshooting page has the folding back does
nothing case with the way out. The on-screen keyboard is opaque now: with
transparency the window underneath showed through the keys. - The desktop wears the mountain photograph again. v0.3.0 drew the mark as the
wallpaper, and a wallpaper is a surface to live on rather than a logo. The mark
stays as the launcher icon, the scalable SVG and the About card; the lock screen
keeps the same photograph, which is what is up when nobody is looking. - Format a disk writes exFAT (
mkfs.exfat -F -L LAZYOS) instead of FAT32,
which refuses a file over 4 GB, and the candidate list no longer depends on the
ChromeOS kernel partition alone:ui_disk_systemrefuses every disk that is
built into the machine (the device-levelremovableattribute,TRAN=usb) or
that the running system depends on (root,/boot, the partition named by
kern_guid=, every active swap, each resolved withlsblk -s). Both Format and
Auxiliary swap ask it again after the pick, because that step repartitions. Alt+Searchanswers in either press order: keyd maps the Search key toF20
under[alt]and sway binds that on the press, while a Search-then-Alt release
falls through to the same window list. A search that cannot start now says why
and waits for Enter instead of closing the window, which is what "the key does
nothing" looked like.- The emoji picker only offers what the font draws.
fonts-noto-color-emoji
omits the text symbols inside the emoji blocks (chess pieces, arrows, alchemical
signs, several ballot boxes), so 692 of 1988 rows inserted a tofu box;
scripts/make-emojis.shfilters the table against the character map fontconfig
resolves foremoji, and~/.config/emojis.fontpins the font so an upgrade is
reported instead of leaving the table stale. 1296 rows remain. - The night light survives a suspend: the panel comes back with its own gamma
table, soafter-resumerestarts the schedule and does nothing when the light
was off. One helper now owns the command line and the mode, so the login line,
the Settings switch and the resume hook cannot disagree. The idle screen's
pkillis bracketed ([o]rg...) after the unbracketed one killed the shell
that ran it before the restart. - The first boot opens one welcome page, once per installation rather than once
per login: eight keys, the marker holds/etc/machine-id, and it is written only
after the page closes, so afootthat failed tries again next login. - Tablet mode's
offrestores the rotation and both inputs with no state
directory left, kills a leftover on-screen keyboard by name, and stops its
poller first so nothing turns the screen back after it has been put upright. - The file browser remembers the last directory (one line in
~/.local/state/lazyos/files-last,--searchexcepted), andimv's keys are
said once per session the first time a picture opens. - A match found with
Alt+Ctrl+Gopens at its line:bat | less +Nanswered
Cannot seek to line number N because less cannot seek a pipe, so bat writes
the page to a real file and less opens that file, which is removed when the
window closes. - Notification cards carry a picture: the file browser's eight messages were
the lastnotify-send -a APPcalls without an icon, andcheck-system.shwarns
when a new one appears. - Small repairs from the card's list: the About windows name
Alt+Q(foot's
Ctrl+Shift+Wdoes not reach them on this keyboard), the root menu has a
launcher entry (org.lazyos.menu.desktop),ejectis installed so pcmanfm's
Unmount works, the reminder prompts explain their formats and keep the title and
note while asking, andzoxideis initialised afterstarshipsocd -works. - The agents menu carries the session's glyphs on its rows (agent, accounts,
install, default, terminal, remove, back) and a display/action table behind them,
because rofi hands back the rendered row and markup cannot be parsed back.
Validation
The tablet failure was diagnosed from the upstream sources rather than guessed:
wlroots creates one wlr_input_device per capability over a single libinput
handle, sway's input ... events is
libinput_device_config_send_events_set_mode(), and libinput's
evdev_device_suspend() closes that handle when the mode is disabled - which
is why the switch went quiet with the keyboard. The script was then exercised
against a stub of swaymsg, jq and wvkbd-mobintl with the identifiers this
unit reports (0:0:cros_ec, 0:0:cros_ec_buttons, keyd's virtual keyboard and
the headset jack): on disables the two typing keyboards and touches neither
cros_ec_buttons nor the jack, off restores them, and repeated runs leave
nothing behind. The new check-system.sh checks were run against both the fixed
script and the old one.
The hardware run that signs this release off is
docs/test-checklist.md § Tablet mode on this card: fold
back out of the mode, the volume keys, the Lock key, the on-screen keyboard and
the rotation. The rest of the batch was verified on the build host and against the
card's report in reports/.
Assets
| asset | what it is |
|---|---|
google-asurada.img.xz |
6 GiB disk image: the three ChromeOS GPT partitions (kernel, /boot, root), ready for dd |
google-asurada-rootfs.tar.zst |
the same root filesystem as a tarball (with /boot inside), for writing your own card with scripts/write-sd.sh |
google-asurada.vmlinuz.kpart |
the signed FIT kernel partition of that image; it embeds the image's root=UUID, so it belongs to this image and no other |
SHA256SUMS |
SHA-256 of the three assets |
sha256sum -c SHA256SUMS
xz -dc google-asurada.img.xz | sudo dd of=/dev/mmcblk1 bs=4M conv=fsyncOn the Chromebook: developer mode, crossystem dev_boot_usb=1 dev_boot_signed_only=0, insert the
card and pick external disk in the firmware menu. It comes up to a greetd prompt — user
brunux, password debian, passwordless sudo. Change the password before using it for
anything real. scripts/install-emmc.sh installs it to internal storage.
What it does not carry
The artifact is sanitized and asserted clean by scripts/lib-dist.sh:
no Wi-Fi profiles (a released image knows no network and asks for one), no SSH host keys and no
machine-id (both generated on first boot, so every installation has its own identity), and no
personal files beyond the session configuration this repository ships.
Known limitations
- The image is 6 GiB, and that is a fix in itself. The v0.3.0 artifact was 4 GiB and its root
partition came out with 32 MB free (dfsaid 100%): enough to boot and not enough to write a log,
a screenshot or a browser cache.IMAGE_SIZE_MIB=6144leaves about 2 GiB, and a larger card
still keeps the space afterp3unused; write the tarball withscripts/write-sd.shto size
p3to the whole card. - The tarball's
/etc/fstabis the unconfigured one the build leaves behind:write-sd.sh
generates the real one. - Artifacts are not byte-reproducible yet (FIT timestamp, filesystem UUIDs).
- The battery gauge's chemistry and time-to-empty properties are upstream failures; waybar reads
the capacity directly, which works. - There is no hardware video decoder, and Vulkan is not usable (PanVK answers Mali-G57 not
supported); the session renders through EGL and Panfrost, and video is CPU work.
Upstream
Vendored from pmaports commit 0e458a2417d6f5ed61c7b70621d5632e30136091 (2026-10-15), mainline
Linux 7.2.7, swayfx 0.6 on scenefx 0.5.
v0.3.0 — LazyOS
v0.3.0 — LazyOS
The distribution has a name, a mark and a wallpaper, and everything that said
Nureb now says LazyOS: the prose, the identifiers, the directories, the desktop
entries, the icon theme, the manual's path and the idle screen's wordmark. The
boot chain, the kernel and the session are the ones v0.2.0 validated; the
identity changed as a clean break, and the session gained auxiliary swap (a card
becomes extra memory without editing a partitioning tool by hand).
Coming from Nureb
This release does not read the old names, and that is deliberate: a
half-renamed card installs a half-renamed eMMC, and the two names then live in
the tree at once. If the card you are holding was written before this release,
write a new one (or scripts/install-emmc.sh from a v0.3.0 card, which clones
the running system) instead of upgrading it in place.
Three things a person can still notice on an old card:
~/.config/mimeapps.listkeeps the old default applications. GIO merges
a user file over/etc/xdg/mimeapps.list, so a double click keeps opening
the old viewer until the file is removed. The new card does not carry one.- The swap label is
lazyos_swap.resume=LABEL=lazyos_swapis the
hibernate wiring; a partition labellednureb_swapstays usable as swap but
cannot be resumed from.sway-hibernatesays so instead of failing quietly. - The agents' accounts moved with the data directories
(~/.local/share/lazyos/agents), so an account directory keeps working only
after the tree is copied; the menu creates a new one in one row.
What changed
- The mark is an arcade button: a cyan bezel, an orange dome, a base03
crescent for depth and a base1 highlight, drawn in the session's own four
colours.brand/lazyos.svgis the source and
scripts/make-brand.shrenders everything from it, so the launcher, the
wallpaper and the About card cannot disagree about the picture. - The icon theme is
LazyOSand carrieslazyos.pngnext to the 219
Font Awesome names (220 files in48x48/appsand inscalable/apps, the
latter with the SVG for GTK at larger sizes). - The wallpaper is the brand, at the panel's real mode (1366x912): the mark,
lazy by designin cyan and» press any key to continue «underneath it. The
lock screen keeps the mountain photograph on purpose: the desktop is the
surface the brand owns, and the photograph is what is up when nobody is
looking. - The distribution says its own name:
/etc/os-releaseis a regular file
withID=lazyos,PRETTY_NAME="LazyOS <version>"andID_LIKE=debian, the
greeter greets withLazyOS · lazy by design,/etc/issuesays the same to a
virtual terminal, and the default hostname islazyos. - The version has one source: the committed
VERSIONfile.build-rootfs.shreads it, forwards it
through sudo into the chroot and records it asversionin
/etc/debian-aarch64-revision, so/etc/os-release, the build record and the
tag cannot disagree. - The identifiers:
org.lazyos.*desktop entries,lazyos-view,
lazyos-findandlazyos-thumbnail,/usr/share/doc/lazyos/for the manual,
~/Dev/LazyOSfor the repository snapshot,lazyos-busy/lazyos-tablet/
lazyos-capturein$XDG_RUNTIME_DIR,~/.config/lazyosand
~/.local/share/lazyosfor state,LAZYOSas the format label and
lazyos_swapas the swap label. The swayfx packaging revision is
1lazyos1, so installing over an old.debis an upgrade. - The root menu grows an
aigroup, with Agents and Dictation together
instead of scattered between the openers and the session actions. - Auxiliary swap turns a card into memory:
rofi-swap(Places, and the root
menu's system section) picks a disk and a size, then creates a
lazyos_swappartition and the/etc/fstabblock that activates it now and on
every boot (nofail, a 15 s device timeout, priority 10 - below zram's 100, so
compressed RAM is used first). The candidate list is the sameui_disks
function Format a disk uses, so neither menu offers the eMMC, the card the
system is running from, the SPI flash (mtd*) or the eMMC's hardware boot
partitions. The status row turns it off again.resume=LABEL=lazyos_swapis
still the hibernate wiring, and adding it is a kernel command line change and a
rebuilt kpart. - About LazyOS is a new launcher entry: the mark as its icon, and a
fastfetchcard whose wordmark, colours and module order are the branded
ones — the machine's facts, with the distribution's name on the left. check-system.shgrows "The brand", and it is the release's witness: it
FAILs when/etc/os-releaseis Debian's again, when the wallpaper or the mark
is missing, and when anorg.nureb.*entry survived the rename; it WARNs when
the greeter,/etc/issue, the fastfetch files or the lock's decision lose the
brand, because those are a hand edit away.
Validation
The rename was swept with git grep: outside the release notes (which describe
the rename on purpose), reports/ and the plan that documents it, the old name
does not appear. The brand was exercised on the build host — scripts/make-brand.sh
renders the three files, the icon reads at 48 px, the wallpaper composes at the
panel's mode, and the fastfetch card was run against the shipped configuration.
The hardware run that signs this release off is the one in
reports/, with
docs/test-checklist.md § The brand as the list: the
desktop wallpaper, the lock keeping the photograph, the About row and its card,
/etc/os-release, the greeter's greeting, the console banner and hostname.
Assets
| asset | what it is |
|---|---|
google-asurada.img.xz |
the disk image: the three ChromeOS GPT partitions (kernel, /boot, root), ready for dd |
google-asurada-rootfs.tar.zst |
the same root filesystem as a tarball (with /boot inside), for writing your own card with scripts/write-sd.sh |
google-asurada.vmlinuz.kpart |
the signed FIT kernel partition of that image; it embeds the image's root=UUID, so it belongs to this image and no other |
SHA256SUMS |
SHA-256 of the three assets |
sha256sum -c SHA256SUMS
xz -dc google-asurada.img.xz | sudo dd of=/dev/mmcblk1 bs=4M conv=fsyncOn the Chromebook: developer mode, crossystem dev_boot_usb=1 dev_boot_signed_only=0, insert the
card and pick external disk in the firmware menu. It comes up to a greetd prompt — user
brunux, password debian, passwordless sudo. Change the password before using it for
anything real. scripts/install-emmc.sh installs it to internal storage.
What it does not carry
The artifact is sanitized and asserted clean by scripts/lib-dist.sh:
no Wi-Fi profiles (a released image knows no network and asks for one), no SSH host keys and no
machine-id (both generated on first boot, so every installation has its own identity), and no
personal files beyond the session configuration this repository ships.
Known limitations
- An old card keeps the old names until it is rewritten; see Coming from Nureb.
- The image size is fixed by the build, and a larger card keeps the space after
p3unused. Write
the tarball withscripts/write-sd.shto sizep3to the whole card. - Artifacts are not byte-reproducible yet (FIT timestamp, filesystem UUIDs).
- The battery gauge's chemistry and time-to-empty properties are upstream failures; waybar reads
the capacity directly, which works. - There is no hardware video decoder, and Vulkan is not usable (PanVK answers Mali-G57 not
supported); the session renders through EGL and Panfrost, and video is CPU work.
Upstream
Vendored from pmaports commit 0e458a2417d6f5ed61c7b70621d5632e30136091 (2026-10-15), mainline
Linux 7.2.7, swayfx 0.6 on scenefx 0.5.
v0.2.0 — the session release
v0.2.0 — the session release
The boot chain, the disk layout and the install/backup tools are the ones
v0.1.1 validated; what changed is everything above the compositor. The machine now
boots into a session with one picker instead of two, a file browser that draws the picture of what
it lists, a manual rendered in the terminal, capture and download menus, dictation, tablet mode,
and an idle screen that is a small animation instead of a still frame.
What changed since v0.1.1
- The session runs on swayfx. Debian's plain sway cannot round a window's corners, draw a
shadow under it or blur what is behind it.compositors/swayfx/pins swayfx 0.6 (a fork of
sway 1.12) on scenefx 0.5, and the packages keep sway's names, sosway,/etc/swayand apt
all still work. Blur is on, with two measured paths: a tiled window samples a wallpaper that was
blurred once (0.07-0.11 ms full screen on the Mali-G57), a floating one is re-blurred from what is
behind it (2.1-2.2 ms full screen, only while visible). The numbers are in
docs/optimization.md§7. - One picker: rofi 2.0 replaces tofi and fuzzel.
$mod+dlaunches applications,$mod+Tab
switches windows,$mod+Shift+druns a command, and the bar's popups are rofi's dmenu. The theme
is solarized, the launcher and window switcher show the real icons, andglobal-kbis on so a
menu keeps the keyboard instead of the session's bindings acting behind it (verified: with it
off,Alt+1switched workspace instead of reaching the menu). - Files, in two shapes on purpose.
Alt+Ctrl+Fand the Search key openrofi-files: one
directory per run, every row carrying a thumbnail or a mimetype icon from the small Nureb
icon theme (219 names, generated byscripts/make-icons.sh), Enter opening it in the program that
fits it - a document in papers, a picture in imv (withchafa's sixels as the fallback),
a video in mpv, text in bat. Search+Shift opens pcmanfm for the window people
expect, and a double click resolves through the same rules vianureb-view.Alt+Searchis the
same question in a terminal:fdstreaming into fzf with a preview pane. - The menus are short-lived rofi scripts, each one process while it is open and nothing
afterwards: capture (screenshots to a dated folder, annotation, OCR, QR, recording), download
(yt-dlp, video or audio), search inside files (rg), clipboard history (cliphist), emoji, quick
settings, notifications, places (mount a stick withudisks2, unmount it, or format a disk),
power (lock, suspend, hibernate, log out, reboot, shut down, behind a confirmation), calculator,
colour picker, DNS, packages, reminders, about, agents and the key view. Slow actions show a
busy card with a bar spinner, and the spinner is also the stop button. - The idle screen is the LazyOS screen, and it loops. 150 s without input and the screen fills
with the LAZYOS wordmark,:: lazy by design ::and» press any key to continue «, in
solarized orange, one terminal-text effect rebuilding the letters after another. Any key ends it
at once. It runs at 30 fps: a full cycle of the seven effects is 70 s of wall time and 8.5 s of
CPU (about 12 % of one core), against 32 % for Deboma's 120 fps loop. This is the one surface
that says LazyOS; the rest of the distribution still says Nureb until the rename lands. - The lock waits for the lock. Every lock entry point (the 300 s timer,
Alt+Ctrl+L, the Lock
key, the two suspend shortcuts, the bar and the power menu) now goes through
~/.config/bin/sway-lock, which uses swaylock's-Rreadiness line sobefore-sleepcannot
return while the screen is still drawing, stops the idle screen first, refuses to stack a second
surface, draws the session's own wallpaper on base03, and raises a critical notification if the
lock never comes up. The suspend shortcuts lock before they sleep, and a lock that fails blocks
the suspend. - Tablet mode folds:
bindswitchstarts wvkbd with the solarized colours and the
mobile-international layout, turns the touchpad and the physical keyboard off (the folded keys
are on the table), and runs a 1 Hz poller over the accelerometer that rotates the output. The
rotation frame is calibrated on the unit (tablet-mode calibrate) because the panel's
accelerometer is not aligned the way the first table assumed; the fold that produced that row is
inreports/feedback-2026-10-21-batch.txt. - Dictation (
Alt+Ctrl+X) records, normalises the level, transcribes with whisper.cpp and
types the result; the model is fetched once and verified against a pinned SHA-256. Hibernate
refuses unless there is a disk swap andresume=on the command line, and says which condition
is missing. Agents starts Claude Code, Codex or another CLI in~/Work, installs one with
npm into~/.local, and keeps per-account config directories. - The manual is rendered, not printed.
rofi-learnopens the seven pages with glow in the
solarized palette (a glamour style with truecolour values), and the same menu searches the
machine's ownmanpages withapropos.Alt+Ctrl+Klists every binding, generated from the
live configuration. - The kernel and the memory story changed. HZ 1000,
schedutil,transparent_hugepage=madvise,
LRU_GEN, and swap is a compressed zram device created bysystemd-zram-generator(not
zram-tools, which failed on every boot next to it);systemd-oomdhandles the 4 GB machine
under pressure. Audio goes through the MT8192 UCMBootSequencethatalsa-utilsdrives, so the
speaker is a real sink and not Dummy Output. - The fixes the cards found: the session gets its locale through
pam_env, SSH host keys are
generated on the first boot that lacks them, the backlight is writable by thevideogroup, the
Wi-Fi profiles are rebound to whatever the interface is called, night light uses 4000 K, a time
zone change restarts the bar, andcheck-system.shreports the outcome of the SCP firmware load
rather than its first attempt. - The image carries this repository at
~/Dev/Nureb, the commit it was built from in
/etc/debian-aarch64-revision, andcheck-system.shinstalled as
/usr/local/sbin/check-system.sh, because the scripts that install to the eMMC and rewrite the
kernel partition are meant to run on the device.
Validation
The latest hardware report in reports/ is the 2026-10-21 card:
95 OK, 2 WARN, 0 FAIL. The two WARNs are upstream noise, not gaps: the sbs-8-000b fuel gauge
logs Unknown chemistry: OTC0 (Nura's own log carries the same lines) and reads correctly, and the
Wi-Fi is on the world regulatory domain until an access point provides a country.
The idle screen and the lock helper landed after that card was written. They were exercised on the
build host - the loop, the immediate dismissal, the centring and the static fallback under a pty -
and the rows that need the panel are the first ones in
docs/test-checklist.md: the 150 s screen, a key during an effect, the
300 s lock, and a suspend that lands on a locked screen.
Assets
| asset | what it is |
|---|---|
google-asurada.img.xz |
6 GiB disk image: the three ChromeOS GPT partitions (kernel, /boot, root), ready for dd |
google-asurada-rootfs.tar.zst |
the same root filesystem as a tarball (with /boot inside), for writing your own card with scripts/write-sd.sh |
google-asurada.vmlinuz.kpart |
the signed FIT kernel partition of that image; it embeds the image's root=UUID, so it belongs to this image and no other |
SHA256SUMS |
SHA-256 of the three assets |
sha256sum -c SHA256SUMS
xz -dc google-asurada.img.xz | sudo dd of=/dev/mmcblk1 bs=4M conv=fsyncOn the Chromebook: developer mode, crossystem dev_boot_usb=1 dev_boot_signed_only=0, insert the
card and pick external disk in the firmware menu. It comes up to a greetd prompt - user
brunux, password debian, passwordless sudo. Change the password before using it for
anything real. scripts/install-emmc.sh installs it to internal storage.
What it does not carry
The artifact is sanitized and asserted clean by scripts/lib-dist.sh,
because the build rootfs does carry the maintainer's state:
- no Wi-Fi profiles - a released image knows no network and asks you for one;
- no SSH host keys - generated on first boot, so every installation has its own;
- no
machine-id- systemd generates a fresh one on first boot; - no personal files: no notes, no keys, no shell history, no agent accounts or model files. What is
in/homeis the ported session configuration, which lives in this repository.
Known limitations
- The image is 6 GiB. A larger card keeps the space after
p3unused; write the tarball with
scripts/write-sd.shto sizep3to the whole card. - The tarball's
/etc/fstabis the unconfigured one the build leaves behind:write-sd.sh
generates the real one. - Artifacts are not byte-reproducible yet (FIT timestamp, filesystem UUIDs).
- Battery percentage is the capacity reading only; the gauge's chemistry and time-to-empty
properties are upstream failures, and waybar reads the capacity directly. - There is no hardware video decoder, and Vulkan is not usable (PanVK answers Mali-G57 not
supported), which is why the session renders through EGL and Panfrost and why video is CPU work. - The published Wi-Fi profile import is one-directional:
scripts/wifi.sh importbinds a saved
profile to any interface, but a profile the image does not carry is entered at first login.
Upstream
Vendored from pmaports commit 0e458a2417d6f5ed61c7b70621d5632e30136091 (2026-10-15), mainline
Linux 7.2.7, swa...
v0.1.1 — install to the eMMC, and a way back
v0.1.1 — install to the eMMC, and a way back
A maintenance release. The boot chain, the kernel and the sway session are the same as
v0.1.0; what changed is the part that installs the system onto internal storage, the
SSH host keys, and two new tools that back the running machine up and put it back.
What changed since v0.1.0
- Install to internal storage works, and it is now pmbootstrap's method.
scripts/lib-cgpt.shreproduces pmbootstrap's ChromeOS install path part by part: the root
partition is sizeddev_size - root_start - 33(the secondary GPT survives, as pmbootstrap
leaves it),partproberuns after thecgpt adds, themkfslines and the/etc/fstaboptions
are the onespmb/install/*.pybuilds, and a target with a mounted partition is refused instead
of silently unmounted. - Partitions are resolved by number, not by their order in
lsblk.lsblklists a disk's
partitions in the order the kernel handed out their minors, and thepartx -d/-around
reorders them: over 16 attaches of one loop device, 5 came back as2 3 1or3 1 2, which
formatted the boot partition as the root filesystem and wrote the kpart into the wrong partition.
The layout now looks each partition up by number and asserts the threepmOS_*labels, so a
wrong resolution dies instead of destroying a card. install-emmc.shrecreates the mount pointsrsyncdrops (/dev,/proc,/sys,/run,
/mnt,/media) and refuses to write the kernel partition unless/devexists and/sbin/init
resolves. Without them the installed system mounted its root and then died inrun-initwith
No init foundand no console to say why, which read as a firmware or kernel failure.- The SSH host keys are generated on the first boot that lacks them. Debian's
sshd-keygen.serviceis gated onConditionFirstBoot=yes, and an image written to a card or the
eMMC is always a copy of a tree that already generated/etc/machine-id, so the condition was
never true, the keys were never made, andssh.servicedied on every boot with
sshd: no hostkeys available -- exiting.rootfs-setup.shships a drop-in that keys on the host
keys being absent instead, which is the thing that actually matters. scripts/backup-system.sh(new) backs the running installation up into a directory: the
kernel partition it booted from, the GPT areas,/bootand the root filesystem as gzip tars with
owners, ACLs and xattrs preserved, plus a README andSHA256SUMS.scripts/restore-system.sh
(new) is the other half: it rebuilds the three partitions from such a backup with the original
filesystem UUIDs, so the restored machine boots with its own fstab and command line.install-kpart.sh's chroot guard actually fires (stat -Land the corrected comparison, with
both sides read before refusing), andCONFIRMsurvives thesudore-exec in both
install-emmc.shandinstall-kpart.sh.build-rootfs.shships an empty/etc/machine-idand no host keys, so every card and every
install gets its own identity instead of sharing one journal and one SSH identity.scripts/00-deps.shinstalls the host build dependencies fromapkorapt, so the
toolchain is installable from the Debian system this port itself runs.
Validation
The hardware evidence this port publishes lives in reports/, taken with
scripts/check-system.sh on the reference Hayato. The kernel, the boot chain and the session are
unchanged from v0.1.0 — whose report of the booted image is clean (51 OK, 2 WARN, the
two WARNs being the upstream sbs-8-000b fuel-gauge noise and the world regulatory domain) — so
what this release changes was verified on the hardware and on loop devices instead:
- the eMMC install reaches the desktop: the running card installed onto
/dev/mmcblk0boots by
picking internal disk in the firmware menu, the same greetd prompt as the card; - the layout and its refusals were rehearsed on a loop device: 16 of 16 attaches resolve the
partitions correctly (including the 5 that came back reordered), and the geometry, partition
types, labels andcgptflags match pmbootstrap's; scripts/backup-system.shandscripts/restore-system.shwere rehearsed on a loop device over a
sparse copy of the original disk's geometry: the GPT, the kernel partition and the file count
come out identical andtar -dagrees with both archives.
Assets
| asset | what it is |
|---|---|
google-asurada.img.xz |
4 GiB disk image: the three ChromeOS GPT partitions (kernel, /boot, root), ready for dd |
google-asurada-rootfs.tar.zst |
the same root filesystem as a tarball (with /boot inside), for writing your own card with scripts/write-sd.sh |
google-asurada.vmlinuz.kpart |
the signed FIT kernel partition of that image; it embeds the image's root=UUID, so it belongs to this image and no other |
SHA256SUMS |
SHA-256 of the three assets |
sha256sum -c SHA256SUMS
xz -dc google-asurada.img.xz | sudo dd of=/dev/mmcblk1 bs=4M conv=fsyncOn the Chromebook: developer mode, crossystem dev_boot_usb=1 dev_boot_signed_only=0, insert the
card, turn it on and pick external disk in the firmware menu. It comes up silently to a greetd
prompt: user brunux, password debian, passwordless sudo — change the password before using it
for anything real. (scripts/install-emmc.sh then installs it to internal storage.)
What it does not carry
Unchanged from v0.1.0: the artifact is sanitized and asserted clean (scripts/lib-dist.sh). No
Wi-Fi profiles, no SSH host keys, no machine-id, no personal files — the machine identity and the
SSH host keys are generated on first boot.
Known limitations
- The image is 4 GiB. A larger card keeps the space after
p3unused; writing the tarball with
scripts/write-sd.shsizesp3to the whole card. - The tarball's
/etc/fstabis the unconfigured one the build leaves behind:
write-sd.shgenerates the real one. - Artifacts are not byte-reproducible yet (FIT timestamp, filesystem UUIDs).
- Battery percentage is the capacity reading only; the gauge reports
Unknown chemistry: OTC0and
spams the journal on upstream kernels — Nura's own log has the same lines.
Upstream
Vendored from pmaports commit 0e458a2417d6f5ed61c7b70621d5632e30136091 (2026-10-15).