Some checks are pending
ci / test (push) Waiting to run
- resolve the NVIDIA branch and kernel-module flavor from PCI device IDs (Turing+ open modules; Maxwell/Pascal/Volta proprietary, masked below 595; Fermi/Kepler fall back to nouveau, reported; unknown IDs reported) - capture pci_id/pci_address in the probe; drive VIDEO_CARDS, package.use, package.accept_keywords, package.mask, modprobe.d and dracut from the plan, preserving hybrid Intel/AMD - add the nvidia_drivers install stage (after the kernel, before boot) that emerges the driver, regenerates the initramfs, records /etc/phoebus/nvidia and fails the install on failure; sys update rebuilds modules and the initramfs - refuse AI changes to x11-drivers/nvidia-drivers - live ISO: signed non-free components, stable-kernel pin (testing 7.2 breaks the 550 driver), DKMS build for the exact kernel, gated pre-greetd load, fail-safe entry, gpu-report, and a --verify-live-nvidia build gate that runs on cached rootfs builds and fails on any missing component - docs: ADR 0012, STATUS/CHANGELOG/HANDOFF, live README - also carries the pending OpenCode model-variant/streaming changes and fixes the GUI bridge install thread join that could hang
9.5 KiB
9.5 KiB
Handoff
Rolling note between work sessions. Update this file before you finish, then
commit it. It should be short and current; use git log for detail.
- Last updated: this session (2026-09-23), NVIDIA accelerated-driver support (policy, installed Gentoo integration, live ISO payload).
- Current focus: Implemented NVIDIA support end to end in code and tests:
phoebus-core::nvidia(plus generatednvidia_devices.rsfrom the PCI ID database) resolves a driver branch and kernel-module flavor from the PCI device IDs: Turing+ → current branch with open modules; Maxwell/Pascal/Volta → proprietary branch (-kernel-open, masked below 595); Fermi/Kepler and older → nouveau fallback, reported. Unknown IDs are reported.- The probe now captures
pci_id/pci_address;VIDEO_CARDS,package.use,package.accept_keywords,package.mask,modprobe.dand dracut follow the plan (hybrid Intel/AMD preserved). - Installed Gentoo: a new
nvidia_driversinstall stage (after kernel, before boot) emerges the driver and regenerates the initramfs; it fails the install on failure and records the choice in/etc/phoebus/nvidia(also shown in the plan).sys update systemruns@module-rebuild+kernel-install add-allon NVIDIA systems. - Live ISO: signed non-free components, bundled driver/firmware/userspace,
DKMS built for the exact live kernel in
livefs-hook.sh, a live-onlyphoebus-nvidia.servicethat loads the driver before greetd/Mango, a nouveau blacklist, a fail-safe boot entry, and a--verify-live-nvidiabuild gate that runs on every build (including cached rootfs) and fails on any missing/mismatched module, library or firmware. - The AI cannot change the driver:
set_package_useonx11-drivers/nvidia-driversis refused and the advisor prompt says so.
- Last verified (this session):
cargo fmt --all -- --checkclean;cargo clippy --workspace --all-targetsfinished with 0 errors (pre-existing warnings only).- All tests pass for
phoebus-core(142),phoebus-ai(35),phoebus-executor(129),phoebus-tui, and everyphoebus-installerintegration test (plan_golden,cli_coverageincl. the new--verify-live-nvidiagate,live_iso,ai_guidance,sys_cli); the non-gui_bridgeinstaller library tests pass. Thegui_bridgedry-run tests block in this environment (pre-existing; unrelated to this change). - New tests: PCI classification (representative IDs), branch/flavor policy,
Kepler/unknown fallback, hybrid, package/
modprobe/dracut config, plan exposure and stage ordering, live-payload verification (complete, missing module, missing userspace/firmware, missing kernel, Debiannvidia-current*naming), the AI refusal, and the@module-rebuild/kernel-installupdate coordination. - Live NVIDIA payload build proven: a minimal
mmdebstraprootfs (Debian testing userspace + the pinned stable kernel) built the DKMS modules and passed--verify-live-nvidiaend to end: driver550.163.01, kernel6.12.107+deb13-amd64, modulesnvidia-current/-modeset/-uvm/-drm, userspace + EGL/GBM + firmware present. The live kernel is now pinned to Debian stable because testing's 7.2 kernel removedstrncpyand breaks the 550 driver.
- Not yet verified this session: the full desktop live ISO was not
assembled (host disk ~10 GiB free; the build wants more), and the live/
installed NVIDIA boot gates are unrun: this host has no NVIDIA GPU (see
blockers). Actual NVIDIA acceleration is not verified. Rollback
(
sys undo), the AI sandbox, the physical-seat desktop and a separate physical computer remain open as before. - Public repo: https://git.phoebus.club/phoebus/phoebus_os
(remote
origin, SSH port 2222).
Next actions (in order)
- NVIDIA hardware acceptance (BLOCKED): on a machine with an NVIDIA GPU
(or an explicitly authorized passthrough VM) boot the built live ISO and the
installed system and confirm:
phoebus-nvidia.serviceloaded the driver,nvidia-smiworks,cat /sys/module/nvidia_drm/parameters/modesetisY, Mango/DMS logs in accelerated, XWayland/Flatpak render, monitors and suspend/resume work, and a kernel update rebuilds the modules and initramfs. Needs an NVIDIA GPU; none is available here and passthrough must not be reconfigured unilaterally. - Live ISO build + verify (BLOCKED on disk):
installer/live/build.shnow bundles and verifies the NVIDIA payload. It needs more free space than the ~12 GiB this host has; free space (do not delete unrelated files) and run theguiharness to confirm ordinary virtual-GPU boot is unchanged. - Installed Mango desktop: install the default profile (Mango + DMS) in a graphical VM and verify the panel/launcher/terminal/audio/network/lock/idle, the dwl fallback, and the welcome/installer absence on the installed system.
- Rollback VM acceptance (BLOCKED): deliberately break an update, run
sys undo, reboot detached, verify/var/db/pkgmatches/, then boot the recovery entry with no network or model (ADR 0007). Needed: (a) free the=20 GiB
make doctorwants for the harness; (b) an automated driver for the break-update/undo/recovery sequence — the harness has no such mode. - Narrow the live broker privilege: replace the live-only
NOPASSWD: ALLrule for the GUI bridge with the smallest practical command-scoped rule once a safe sudoers form is verified (ADR 0011 context). - Physical-seat desktop: run
phoebus-sessionon a real VT/seat and checkphoebus-menu,phoebus-lock,phoebus-idle, kitty, XWayland, the polkit agent, logout/reap and reboot (docs/DEVELOPMENT.md). - Release gates on a CI runner:
phoebus-release gates --executeandpublishonce a runner exists; no gate has executed.
Known blockers / risks
- NVIDIA hardware verification is BLOCKED: this host has no NVIDIA GPU and
QEMU's virtual GPU cannot establish NVIDIA acceleration; no passthrough setup
is available or authorized. Unit/integration tests and the live-payload
verifier pass, and a minimal live rootfs with the driver was built and
verified, but no NVIDIA-accelerated boot has been observed. The full desktop
ISO also cannot be assembled here:
dfshows ~10 GiB free. Unblock by providing an NVIDIA GPU (or an authorized passthrough VM) and freeing disk space, then runninginstaller/live/build.shand thegui/install/bootharness modes. Note: the live kernel is pinned to Debian stable because testing's 7.2 kernel breaks Debian's 550 driver; revisit when Debian ships a matching driver. - The complete graphical install and detached boot are BLOCKED on host build
time. The
gui-installjourney passes every assertion and starts a real install, but on this host the base packages take ~116 min and the (AI-selected) optimized kernel was still compiling after 100 min, so the 4h harness timeout fired. Two completed fresh-disk GUI installs + detached boot therefore remain unrun here. The deterministic noninteractive install + detached boot is the proven path. - Installed Mango (GURU + compiled Quickshell/DMS) is not VM-verified; nor
is the dwl fallback session. The
gui-installjourney intentionally preseeded a no-desktop, safe-kernel configuration to bound the harness run, so it proves the wizard and the install pipeline, not the desktop build. - Rollback (
sys undo) is implemented and unit-tested but NOT VM-verified (BLOCKED). Exact blockers:make doctorreports ~13 GiB free versus the=20 GiB the harness wants, and the harness has no automated break-update/undo/recovery-boot mode. The AI sandbox is likewise implemented/unit-tested but not VM-verified. NVIDIA is not verified.
- A separate physical computer for the OpenCode transport test is not available (BLOCKED); a forwarded-hop + unauthenticated-LAN-refusal host-local test was done instead.
- The GUI bridge reaches Quickshell via
Process+/usr/bin/sudo -n; it relies on the live user's passwordless sudo. The live sudoers rule is stillNOPASSWD: ALL(live-only); narrowing the broker permission is future work. - Harness artifacts live under
/var/tmp/phoebus-vm/(outside git):results.json,screenshot-manifest.json,report.html, screenshots.
Environment notes
- Dev host: Ubuntu 26.04. QEMU/OVMF/xorriso/rustfmt/clippy/ImageMagick present.
- Debian-Live base ISO is cached at
/home/dominic/debian-live-standard.iso(matchesinstaller/live/base.sha256); the appliance ISO builds without root. - Local QML iteration:
/tmp/opencode/run-qml.sh <config-dir>runs a config on a nested Mango over the host X11 using the built rootfs libraries, andgrimcaptures it. The sanctioned verification is the disposable VM. - VM harnesses:
installer/tests/vm/gui-driver.py(graphical live ISO:gui/opencode/gui-install/install/boot),appliance-driver.py,serial-driver.py.DISKmust be a disposable qcow2; never point it at/dev/*. Agui-installrun leaves its installed disk for a followingbootrun. - Serve the install fixtures from
/home/dominic/vmlab/servewithpython3 -m http.server 8000 --bind 127.0.0.1(reachable as10.0.2.2:8000).
Definition of a good stopping point
make testpasses;docs/STATUS.mdanddocs/CHANGELOG.mdupdated;docs/HANDOFF.mdupdated; committed and pushed (scripts/agent-commit.sh+scripts/publish.sh).