Cyril Brulebois <k...@debian.org> (2023-05-23): > > Since it's filed at severity normal I think I'll stick to my initial > > assessment which was: adjust hw-detect during the Trixie release cycle, > > and consider cherry-picks for Bookworm, once we get a better picture.
> Given the first follow-up to #1036589, I'm even more convinced trying to > rush something for 12.0 would be a bad idea. > Having an extra component enabled and an extra package installed in some > environments doesn't really justify trying to get an immediate fix, > which could jeopardize all other installation scenarios. I hope this can be resolved for Trixie. Patch attached. Tested with QEMU. Thank you! Daniel Lewart Urbana, Illinois
diff -ru a/hw-detect.post-base-installer.d/50install-firmware b/hw-detect.post-base-installer.d/50install-firmware --- a/hw-detect.post-base-installer.d/50install-firmware 2023-05-09 15:01:46.000000000 -0500 +++ b/hw-detect.post-base-installer.d/50install-firmware 2024-12-24 22:00:00.000000000 -0600 @@ -15,6 +15,12 @@ exit 0 fi +virt=$(chroot /target systemd-detect-virt || true) +if [ -n "$virt" ]; then + log "detected virtualization '$virt', firmware lookup disabled, exiting" + exit 0 +fi + # copy any loose firmware files to /target (incl. subdirs) if [ -d /lib/firmware ]; then for f in /lib/firmware/*; do
