Feat/t400 and macpro31 hosts #17
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: lyrathorpe/nixfiles#17
Reference in New Issue
Block a user
Delete Branch "feat/t400-and-macpro31-hosts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Split the T400 bootloader into self-contained, importable modules so the host can match whatever firmware is flashed (switch by changing one import): - boot-bios.nix stock BIOS / coreboot+SeaBIOS -> GRUB on the MBR (default) - boot-coreboot-grub.nix coreboot GRUB payload -> config-only GRUB (device=nodev) - boot-coreboot-uefi.nix coreboot Tianocore/UEFI payload -> systemd-boot; carries its own ESP (/boot vfat) so it travels with the mode Cover the optional discrete ATI Mobility Radeon HD 3470 (RV620): load the open `radeon` KMS driver in the initrd for early modesetting (firmware via enableRedistributableFirmware), with a note on the T400's switchable graphics. All three boot variants evaluate; nixfmt clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>Add system/machine/{T400,MacPro31}/README.md covering the placeholder hardware-configuration regeneration, partition labels, bootloader selection (T400 boot variants; Mac Pro EFI quirks), and GPU notes. Link each from its configuration.nix header, and refresh the top-level README host table (T400 replaces X1, Mac Pro 3,1 added) with links to both. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>Only `menu` was set, which the module's default keybindings run on Mod+d; Mod+Space defaulted to `focus mode_toggle`, so sway-launcher-desktop was never reachable from Mod+Space. Add an explicit Mod+Space -> exec ${menu} binding at normal priority (via mkMerge) so it overrides the default. Mod+d still launches it as well. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>Replace the mismatched theming (gruvbox i3status-rust, unthemed foot, default Sway borders) with a single Catppuccin Mocha palette so the desktop matches the Vim colorscheme. A `ctp` let-binding holds the raw hex once; consumers add "#" as needed. Themed: foot (16-colour + selection/cursor), i3status-rust ("plain" base + overrides, idle blocks on mantle, loud bg only for warning/critical), Sway window borders and the bar/workspace buttons, swaylock (full ring/inside/text set) and dunst (base/text bg, blue/peach frames). Lives in the shared home/sway.nix, so every Sway host is themed consistently. Vim already uses catppuccin_mocha, so the editor is unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>Two desktop-config fixes found together: 1. Keybindings: the previous Mod+Space launcher bind wrapped the set in `lib.mkMerge [ { ... } (mkOptionDefault ...) ]`. A normal-priority definition there wins over (and discards) the home-manager module's default keybindings, which are at mkOptionDefault priority -- so every default bind (terminal Mod+Return, movement, workspaces, kill, ...) and even the custom swaylock/volume binds silently vanished; only Mod+Space survived. That is why Super+Enter opened nothing. Restore the single mkOptionDefault wrapper (so it merges with the module defaults) and override just Mod+Space via lib.mkForce to beat the module's default focus-mode_toggle without a same-priority conflict. Generated config goes from 1 bindsym back to 57. 2. foot 1.27: the bare [colors] section is deprecated in favour of [colors-dark], and `[cursor] color` is rejected ("not a valid option: color"). Move the palette to colors-dark and set the cursor colour via its `cursor` key ("<text> <cursor>"). `foot --check-config` now passes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>