XPost: linux.debian.bugs.dist, linux.debian.maint.boot   
   From: kibi@debian.org   
      
   Hi,   
      
   Frederik Himpe  (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)               
   D-I release manager -- Release team member -- Freelance Consultant   
      
   -----BEGIN PGP SIGNATURE-----   
      
   iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmlROqwACgkQ/5FK8MKz   
   VSDXLg/+P8vQN9FOENT/wVAErMpoeGMECqyZxM0oC3s80MCaZVZh9DAvK+KHC5YJ   
   VVvYo1DRqO10c8jXG/p+xfxcQnMathxht2hbRPHF4wYTIJTfkiP0dweb1yVjqaDv   
   0NAGu4CP9tF4X3Z54u1Hh6TuI3ulcMnT9L7Bd2rQuD+J+EU3ldiXMPI0gAv7TfW8   
   LNKienjJcl9bPgrZo36sD78FxQEYnugyCFyn8sd6rbgG/KgCGYim36VZuUhtELgf   
   uhqxVaaEQVSaxxZ0w9Gj+4oqenYWxy2XcoeEynQLPEuvBo7fCqxNZFqmzZWpm29l   
   WffSYn419dfU+b6CJJy2JijwfoKuWS13u5QQ/PhVlPbyav1dMHFhKA3wHGsWVk3J   
   GXdU7p95HPtY0Ue5GKkBZEgleVYDHuSBJY+Nr9J6o53nFIalyKDRoRsvI7RZMBXj   
   iqF0S90S2YBwjwQFn/2iRwWsIQPyOCYaltumGF5ko/ax/66tp5+ZHNfl7WVanx5u   
   djbcF2hCLtIEScK9H3ulL/KCzT19TW6ISTd8cC/rSNjjbZ61qdGfhtbB1wHmvL5s   
   u5yKatW6Zq4KxSM2O++04DC51RBpUy7rBkMNThwS2sjWlMd0+RDWiVqiYx8aJ7n2   
   10nocRjH+IHY5p5VrnxMYIHYIVqUzRev3aw5z1LL0L2q2tB0gW8=   
   =V4OL   
   -----END PGP SIGNATURE-----   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)