Repository navigation
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).