resolved hdmi issues on tvbox

This commit is contained in:
ari committed 2026-09-14 10:24:37 -04:00
1 parent 288e822f39
commit a05e166e1a
10 files changed
+157 -56

No files matched your search

+34 -13
View File
@@ -10,6 +10,7 @@ Read this file before making any changes.
Before making **any** change to this repository, you MUST present a short plan to the user and wait for their approval. This applies to every task, no matter how small.
Your plan must include:
1. **What** you intend to change (files, options, packages)
2. **Why** the change is needed
3. **How** you will do it (which files you will edit, in what order)
@@ -22,20 +23,23 @@ Only after the user approves the plan may you proceed with edits.
## Hard Rules — Never Break These
### ❌ NEVER run builds or system switches — ZERO EXCEPTIONS
**DO NOT RUN ANY OF THESE COMMANDS AT ANY TIME, FOR ANY REASON:**
```
nixos-rebuild switch / test / build / dry-build
nh os switch / test / build
skyg os switch / test / build
skyg remote switch / test / build
skyg remote switch / test / build / boot / install
skyg hm switch / build
nix build
nix flake check
docker/podman build
nixos-anywhere
```
**Why:**
**Why:**
- These commands take 20–40+ minutes
- They consume significant CPU/RAM on the user's machine
- They can block the user from their own work
@@ -46,26 +50,35 @@ docker/podman build
**Even if the user says "go ahead":** Do NOT run these. Your role is to write good Nix, not execute it.
### ❌ NEVER run `skyg remote install` or nixos-anywhere — ZERO EXCEPTIONS
This wipes every disk in `hosts/<profile>.disko.nix`. A second run is as destructive as the first.
Always make the user run it. Do not invoke it, even with `--force-wipe`, even if asked.
### ❌ NEVER edit `flake.lock` by hand
This file is managed exclusively by `nix flake update`. Editing it manually will corrupt
the lock file and break all builds.
### ❌ NEVER edit `*.hardware-configuration.nix` files
These are generated by `nixos-generate-config` and reflect the physical hardware. Edits
will be overwritten on the next hardware scan and can render a system unbootable.
### ❌ NEVER touch secrets
Do not read, write, or delete files in `secrets/`. Encrypted `.age` files must only be
managed with `agenix` via the `skyg secrets` commands. Do not modify `secrets.nix` unless
the user explicitly asks and explains the full context.
### ❌ NEVER add `imports = [...]` to host files
Host files (`hosts/<hostname>.nix`) do not use `imports`. All modules are composed through
the `makeNixOs` call in `flake.nix` via `modules/main.nix`. Adding imports to a host file
breaks the composition model.
### ❌ NEVER modify `GUIDELINES.md` unless explicitly requested by the user
You must **live and die by these rules** and hold yourself accountable to them.
These are not suggestions — they are non-negotiable.
@@ -98,6 +111,7 @@ Instead: describe what you would do and ask the user for permission.
## NixOS Conventions in This Repo
### Option Namespace
All custom options live under `skyg.*`. Never introduce options under any other top-level
namespace. Check `modules/lib.nix` for the full `skyg.*` structure.
@@ -111,25 +125,31 @@ myOptions.desktop.enable = true;
```
### Enable/Disable Pattern
All modules follow `lib.mkIf cfg.enable { ... }`. Always gate config behind an `enable`
option. Default should be `false` unless the feature is universally required.
### Host Files vs Shared Modules
- **Host-specific** (one machine only): goes in `hosts/<hostname>.nix`
- **Shared** (multiple hosts): goes in the appropriate `modules/nixos/` or `modules/core/` submodule
- When in doubt, keep it in the host file and extract later if reuse emerges
### Package Placement
- Packages needed on all desktops → `modules/nixos/desktop/default.nix` (non-slim mode)
- Packages for one host only → `environment.systemPackages` in the host file
- Custom/third-party packages not in nixpkgs → `pkgs/<name>/default.nix` with an overlay in `modules/core/default.nix`
### Home Manager
Home Manager config lives inside `home-manager.users.<name>` blocks. Do not mix
system-level and HM-level options. The HM entry point is `modules/home/default.nix`.
### Greeter
Both desktop hosts (`fwbook`, `hl-fwdesk`) use DankMaterialShell greeter via:
```nix
services.displayManager.dms-greeter = {
enable = true;
@@ -137,22 +157,23 @@ services.displayManager.dms-greeter = {
configHome = "/home/<username>";
};
```
Do not configure `services.greetd` manually on these hosts — the DMS module handles it.
---
## Navigation Tips
| Question | Where to look |
|---|---|
| What hosts exist? | `hosts/` + `docs/hosts/README.md` |
| What does a `skyg.*` option do? | `modules/` — find the defining `.nix` file |
| What flake inputs are available? | Top of `flake.nix` |
| What binary caches are configured? | `modules/core/nix-substituters.nix` |
| What secrets exist? | `secrets.nix` (lists files + authorized keys) |
| What custom packages exist? | `pkgs/` |
| Full API reference | `docs/modules/README.md` |
| Host details (ports, services, hardware) | `docs/hosts/README.md` |
| Question | Where to look |
| ---------------------------------------- | --------------------------------------------- |
| What hosts exist? | `hosts/` + `docs/hosts/README.md` |
| What does a `skyg.*` option do? | `modules/` — find the defining `.nix` file |
| What flake inputs are available? | Top of `flake.nix` |
| What binary caches are configured? | `modules/core/nix-substituters.nix` |
| What secrets exist? | `secrets.nix` (lists files + authorized keys) |
| What custom packages exist? | `pkgs/` |
| Full API reference | `docs/modules/README.md` |
| Host details (ports, services, hardware) | `docs/hosts/README.md` |
---