Hi, Frederik Himpe <frederik@frehi.be> (2025-12-28): > Boot method: USB > Image version: installer build 20251217-00:02:28 > Date: 20251217 If you could share the full URL, that'd be nice to have. > The installer did not install the package firmware-cirrus. Without > this package, sound was not working on this system. Thanks for the report. The firmware lookup (in general) seems to be working given: > ============================================== > Installer firmware-summary: > ============================================== > #Package Component Reason > firmware-mediatek non-free-firmware dmesg > firmware-realtek non-free-firmware dmesg > firmware-amd-graphics non-free-firmware modalias > firmware-mediatek non-free-firmware modalias > firmware-realtek non-free-firmware modalias > firmware-sof-signed non-free-firmware modalias > amd64-microcode non-free-firmware cpu Looking at a recent trixie-based debian-cd build, firmware-cirrus is indeed spotted in the list of firmware packages, but there's no *.patterns file built for it. It ships metadata: /usr/share/metainfo/org.debian.firmware_cirrus.metainfo.xml so that should make its way into the dep-11 thing, but checking what we do with such information in debian-cd, it's about extracting modalias information, while that file only lists firmware files (checked in unstable). Loop += debian-kernel@ for input. That means the modalias code path cannot do anything there, but the dmesg one might have spotted missing firmware files if they were mentioned in the kernel logs. I suppose that'd depend on whether the relevant modules are indeed available in whatever image you used, if they were loaded, if they requested firmware files, if that generated kernel logs that the installer could pick up, etc. Attaching a compressed /var/log/installer/syslog might shed some light. Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature