diff --git a/WORKAROUNDS.md b/WORKAROUNDS.md index 11c526b2..afcfd2d8 100644 --- a/WORKAROUNDS.md +++ b/WORKAROUNDS.md @@ -53,6 +53,7 @@ A setting that works around a bug or a hardware quirk. | WA-036 | catppuccin eval-time ports kept in the home closure (`home.extraDependencies`) — `home/base/core/theme.nix` | catppuccin/nix reads some ports at eval time (`lib.importTOML "${sources.starship}/.toml"`) and inlines the result, so the built port, catppuccin's build/install hooks and the fetched port source stay unreachable: every gc deletes them, and the deploy after it rebuilds them (build logs: 2026-10-16). `home.extraDependencies` records the port in the generation, which is a gc root. Also read at eval time upstream: `bottom`, `element` (option `element-desktop`), `firefox`, `rio`, `palette` (options `skim`, `tty`), `spotify-player`. | Drop once catppuccin/nix stops reading port files at eval time, or those ports come from a binary cache | 2026-10-16 | on a catppuccin bump | active | | WA-039 | niri's NVIDIA free-buffer pool bounded (`GLVidHeapReuseRatio` 0) — `hosts/idols-ai/hardware-nvidia.nix` | the driver does not return freed vidmem buffers to its free pool, so niri's VRAM grows to ~1.1 GiB instead of the ~100 MiB its NVIDIA notes expect (measured 1137 MiB after 24 h uptime; [NVIDIA/egl-wayland#126](https://github.com/NVIDIA/egl-wayland/issues/126)) | Drop once a driver stops growing niri's VRAM without the profile, or niri ships its own default | 2026-10-19 | on an nvidia driver bump | active | | WA-040 | NixOS root CA blacklist — `modules/base/security.nix` | eMudhra intermediate keys were compromised; [NixOS/nixpkgs#576390](https://github.com/NixOS/nixpkgs/pull/576390) and [#576401](https://github.com/NixOS/nixpkgs/pull/576401) merged before reaching release channels | Drop once every consumed NixOS nixpkgs revision includes the upstream root blacklist | 2026-10-20 | on nixpkgs bump | active | +| WA-041 | Monitor OSD "no-signal auto power-off" disabled — no code in this repo (the P32A2V OSD setting) | during a DPMS-off idle the panel drops and re-adds HPD every ~13 s, and after wake niri keeps scanning out while the panel stays dark until the monitor is power cycled; the panel's own auto power-off drives that state, so it is now disabled. Pinning the mode to 120 Hz did not change the symptom | Drop once a driver retrains the DP link after a DPMS wake, the monitor firmware stops cycling HPD, or this monitor is replaced | 2026-10-21 | confirm on the next full idle cycle, then on an nvidia or monitor firmware update | active | If WA-008 freezes recur, the fallback is to restore the parameters commented out in `hosts/idols-ai/hardware-configuration.nix` — diff --git a/hosts/idols-ai/niri-hardware.kdl b/hosts/idols-ai/niri-hardware.kdl index 6f0d7911..b5ab17a1 100644 --- a/hosts/idols-ai/niri-hardware.kdl +++ b/hosts/idols-ai/niri-hardware.kdl @@ -23,10 +23,10 @@ output "Beihai Century Joint Innovation Technology Co.,Ltd P32A2V 0000000000000" // for the resolution. // If the mode is omitted altogether or is invalid, niri will pick one automatically. // Run `niri msg outputs` while inside a niri instance to list all outputs and their modes. - // Take the exact value from `niri msg outputs` on this host: niri matches - // refresh rates exactly, so this panel's 120 Hz mode is 119.880 (120/1.001) - // and "@120" falls back to 144 Hz, whose DSC link stays dark on wake. - mode "3840x2160@119.880" + // Pin the exact value from `niri msg outputs` on this host: niri matches + // refresh rates exactly, so a nominal "144" can miss and fall back silently + // (this panel's 120 Hz mode, for example, is 119.880, not 120). + mode "3840x2160@144.000" // Position of the output in the global coordinate space. // This affects directional monitor actions like "focus-monitor-left", and cursor movement.