From 9e9123003cb88a8d86d85cd82532c2d787ac2efb Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Wed, 10 Jun 2026 17:46:54 -0500 Subject: fix(install): keep linux-firmware-realtek in the Framework trim MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit velox's first post-trim boot showed r8152 failing to load rtl_nic/rtl8156b-2.fw — the Framework Ethernet expansion card is a Realtek RTL8156B, so the trim list was wrong to drop realtek firmware. The driver runs on internal defaults without the blob, so nothing broke, but the package is back on velox and out of the removal list. --- archsetup | 10 ++++++---- todo.org | 8 ++------ 2 files changed, 8 insertions(+), 10 deletions(-) diff --git a/archsetup b/archsetup index 19d79dc..d0a2e3d 100755 --- a/archsetup +++ b/archsetup @@ -2390,9 +2390,11 @@ EOF fi # Firmware trim — Framework 13 Intel only (matched by DMI), where the - # hardware set is known: i915 graphics (linux-firmware-intel) and ath9k - # wifi (linux-firmware-atheros, firmware-free driver but kept for safety). - # Saves ~600MB. The meta package needs -Rdd because mkinitcpio-firmware + # hardware set is known: i915 graphics (linux-firmware-intel), ath9k wifi + # (linux-firmware-atheros, firmware-free driver but kept for safety), and + # the RTL8156 Ethernet expansion card (linux-firmware-realtek — its r8152 + # firmware load fails without it; found on velox's first post-trim boot). + # Saves ~550MB. The meta package needs -Rdd because mkinitcpio-firmware # declares a dependency on it; the dangling dep is cosmetic and the # subsequent mkinitcpio warnings cover hardware this machine doesn't have. if grep -qi "framework" /sys/class/dmi/id/product_name 2>/dev/null && \ @@ -2403,7 +2405,7 @@ EOF linux-firmware-cirrus linux-firmware-liquidio linux-firmware-mediatek \ linux-firmware-mellanox linux-firmware-nfp linux-firmware-nvidia \ linux-firmware-other linux-firmware-qlogic linux-firmware-radeon \ - linux-firmware-realtek >> "$logfile" 2>&1 || error_warn "$action" "$?" + >> "$logfile" 2>&1 || error_warn "$action" "$?" action="rebuilding initramfs after firmware trim" && display "task" "$action" mkinitcpio -P >> "$logfile" 2>&1 || error_warn "$action" "$?" fi diff --git a/todo.org b/todo.org index 1b928a5..678528f 100644 --- a/todo.org +++ b/todo.org @@ -997,12 +997,8 @@ What we're verifying: the new Chrome theme's colors look right in a real browser - Look at the window frame, toolbar, tab strip, and a new tab page Expected: near-black frame (#151311), dark toolbar/omnibox (#252321), gold links on the new-tab page, steel-gray inactive tab text — coherent with the rest of the dupre desktop. -*** velox boots clean after the firmware trim -What we're verifying: removing 13 linux-firmware packages didn't take any boot-time firmware velox actually needs (wifi and graphics were verified live, but module loads at boot are the real test). -- Reboot velox at the next natural opportunity -- Log in, confirm wifi associates and the desktop renders -- Run: dmesg | grep -iE "firmware.*(fail|error|not found)" -Expected: normal boot, wifi up, graphics fine, and no firmware load failures in dmesg. +*** 2026-06-10 Wed @ 17:46:34 -0500 velox post-trim reboot verified; realtek firmware restored +Craig rebooted velox (passphrase at console); checks ran over SSH after boot. Wifi connected, TLP active, graphics fine. One dmesg hit: r8152 failed to load rtl_nic/rtl8156b-2.fw — the Framework Ethernet expansion card (RTL8156B) is Realtek, so the trim list wrongly dropped linux-firmware-realtek (a Realtek laptop camera is on USB too). Reinstalled the package on velox (its hook rebuilt the initramfs) and removed realtek from archsetup's trim list. The driver worked even without the blob (internal-defaults fallback), so this was correctness, not breakage. * Archsetup Resolved -- cgit v1.2.3