From 04b9471a640a1ece32af6e2795201c3629d8643e Mon Sep 17 00:00:00 2001 From: Chris Gray Date: Fri, 13 Nov 2026 10:18:47 -0600 Subject: [PATCH] device/bluejay: keep root-only gates independent of SDDM The SDDM drop-in requires hardware and GPU services that the root-only runbook does not install. Omit it from the snapshot, install and undo lists, and limit the expected result to root checks, SSH and marker cleanup. Desktop readiness belongs to the separate hardware integration. Validation: both documented shell blocks parse with bash -n; tools/pr-check origin/main passes. No phone changes. Co-Authored-By: Codex --- device/bluejay/bringup/README.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/device/bluejay/bringup/README.md b/device/bluejay/bringup/README.md index 952dd1a08..9b3fdc814 100644 --- a/device/bluejay/bringup/README.md +++ b/device/bluejay/bringup/README.md @@ -86,8 +86,7 @@ systemctl is-enabled omamobile-bluejay-check.service > "$backup/check.enabled" 2 systemctl is-enabled omamobile-bluejay-boot-ready.service > "$backup/ready.enabled" 2>&1 || true for path in /usr/bin/omamobile-bluejay-check /usr/bin/omamobile-bluejay-boot-ready \ /usr/lib/systemd/system/omamobile-bluejay-check.service \ - /usr/lib/systemd/system/omamobile-bluejay-boot-ready.service \ - /usr/lib/systemd/system/sddm.service.d/bluejay-check.conf; do + /usr/lib/systemd/system/omamobile-bluejay-boot-ready.service; do if [ -e "$path" ] || [ -L "$path" ]; then cp -a --parents "$path" "$backup/"; fi done touch "$backup/snapshot-complete" @@ -95,16 +94,17 @@ install -Dm755 device/bluejay/bringup/bin/omamobile-bluejay-check /usr/bin/omamo install -Dm755 device/bluejay/bringup/bin/omamobile-bluejay-boot-ready /usr/bin/omamobile-bluejay-boot-ready install -Dm644 device/bluejay/bringup/vendor/systemd/system/omamobile-bluejay-check.service /usr/lib/systemd/system/omamobile-bluejay-check.service install -Dm644 device/bluejay/bringup/vendor/systemd/system/omamobile-bluejay-boot-ready.service /usr/lib/systemd/system/omamobile-bluejay-boot-ready.service -install -Dm644 device/bluejay/bringup/vendor/systemd/system/sddm.service.d/bluejay-check.conf /usr/lib/systemd/system/sddm.service.d/bluejay-check.conf systemctl daemon-reload systemctl enable omamobile-bluejay-check.service omamobile-bluejay-boot-ready.service ) ``` Expect both units enabled and their installed `ExecStart` paths present. A real -boot must show the check passing, SSH available, the pending marker cleared -and the desktop ready. Stop on any failed prerequisite; do not clear the -marker merely to make a failing boot repeat. +boot must show the check passing, SSH available and the pending marker cleared. +The SDDM drop-in is outside this root-only set: desktop readiness requires the +separately staged hardware/GPU units and their hardware-ready marker. Stop on +any failed prerequisite; do not clear the marker merely to make a failing boot +repeat. To undo on the installed development root before another boot, restore the saved files below. If only RAM rescue is available, first recover access to @@ -123,8 +123,7 @@ backup=/var/lib/omamobile/bluejay-root-gates-before-test systemctl disable omamobile-bluejay-check.service omamobile-bluejay-boot-ready.service for path in /usr/bin/omamobile-bluejay-check /usr/bin/omamobile-bluejay-boot-ready \ /usr/lib/systemd/system/omamobile-bluejay-check.service \ - /usr/lib/systemd/system/omamobile-bluejay-boot-ready.service \ - /usr/lib/systemd/system/sddm.service.d/bluejay-check.conf; do + /usr/lib/systemd/system/omamobile-bluejay-boot-ready.service; do rm -f "$path" if [ -e "$backup$path" ] || [ -L "$backup$path" ]; then cp -a "$backup$path" "$path"; fi done