Bug#1032071: ARM firmware packages included in amd64 installation images

[Pascal Hambourg]

Package: debian-cd
Version: 3.2.0
Severity: minor

debian-bookworm-DI-alpha2-amd64-netinst.iso includes firmware packages
for ARM platforms:

firmware-qcom-soc
firmware-samsung
firmware-ti-connectivity
raspi-firmware

These packages add 34 MB to the ISO image, which is not negligible.

Additionally, IIUC the installer only needs firmware for storage,
network/wireless and sound devices. It uses generic graphic drivers for
display so it does not need GPU firmware. The netinst image includes
firmware packages which do not seem to be needed by the installer:

bluez-firmware (Bluetooth)
dahdi-firmware-nonfree (VoIP)
firmware-amd-graphics (GPU)
firmware-ast (GPU)
firmware-ivtv (MPEG codec)
firmware-realtek-rtl8723cs-bt (Bluetooth)
firmware-siano (TV receiver)
hdmi2usb-fx2-firmware (?)

Among them, firmware-amd-graphics takes 12 MB.
Is it useful to include these packages in the netinst image ?
Couldn't they be downloaded from a mirror like other ordinary packages
when needed ?

Note: it also includes firmware-linux-nonfree which is a meta-package
not containing any firmware file.

[Steve McIntyre]

Post by Pascal Hambourg
Package: debian-cd
Version: 3.2.0
Severity: minor
debian-bookworm-DI-alpha2-amd64-netinst.iso includes firmware packages for
firmware-qcom-soc
firmware-samsung
firmware-ti-connectivity
raspi-firmware

Now all filtered in debian-cd unless we have an arm* architecture for
the build.

Post by Pascal Hambourg
These packages add 34 MB to the ISO image, which is not negligible.
Additionally, IIUC the installer only needs firmware for storage,
network/wireless and sound devices. It uses generic graphic drivers for
display so it does not need GPU firmware. The netinst image includes firmware
bluez-firmware (Bluetooth)
dahdi-firmware-nonfree (VoIP)
firmware-amd-graphics (GPU)
firmware-ast (GPU)
firmware-ivtv (MPEG codec)
firmware-realtek-rtl8723cs-bt (Bluetooth)
firmware-siano (TV receiver)
hdmi2usb-fx2-firmware (?)
Among them, firmware-amd-graphics takes 12 MB.
Is it useful to include these packages in the netinst image ?
Couldn't they be downloaded from a mirror like other ordinary packages when
needed ?

I'm not currently filtering by build type, so I'm leaving these in.

Post by Pascal Hambourg
Note: it also includes firmware-linux-nonfree which is a meta-package not
containing any firmware file.

That's been fixed separately by other changes - we now check the
contents of the firmware .debs too.

[Magnus Wallin]

Post by Steve McIntyre

Post by Pascal Hambourg
Package: debian-cd
Version: 3.2.0
Severity: minor
debian-bookworm-DI-alpha2-amd64-netinst.iso includes firmware packages for
firmware-qcom-soc
firmware-samsung
firmware-ti-connectivity
raspi-firmware

Now all filtered in debian-cd unless we have an arm* architecture for
the build.

Post by Pascal Hambourg
These packages add 34 MB to the ISO image, which is not negligible.
Additionally, IIUC the installer only needs firmware for storage,
network/wireless and sound devices. It uses generic graphic drivers for
display so it does not need GPU firmware. The netinst image includes firmware
bluez-firmware (Bluetooth)
dahdi-firmware-nonfree (VoIP)
firmware-amd-graphics (GPU)
firmware-ast (GPU)
firmware-ivtv (MPEG codec)
firmware-realtek-rtl8723cs-bt (Bluetooth)
firmware-siano (TV receiver)
hdmi2usb-fx2-firmware (?)
Among them, firmware-amd-graphics takes 12 MB.
Is it useful to include these packages in the netinst image ?
Couldn't they be downloaded from a mirror like other ordinary packages when
needed ?

I'm not currently filtering by build type, so I'm leaving these in.

Post by Pascal Hambourg
Note: it also includes firmware-linux-nonfree which is a meta-package not
containing any firmware file.

That's been fixed separately by other changes - we now check the
contents of the firmware .debs too.
--
"Managing a volunteer open source project is a lot like herding
kittens, except the kittens randomly appear and disappear because they
have day jobs." -- Matt Mackall

Just a head's up that this is starting to affect numerous people.
If at all possible to prioritize it would be great.

[Magnus Wallin]

Post by Magnus Wallin
Just a head's up that this is starting to affect numerous people.
If at all possible to prioritize it would be great.

Sorry: I somehow managed to not include links in my previous message.

Here below are examples of affected individuals and workarounds:
https://forums.debian.net/viewtopic.php?t=155195
https://forums.debian.net/viewtopic.php?t=154857

[Steve McIntyre]

Hi Magnus, and thanks for the heads-up

Post by Magnus Wallin

Post by Magnus Wallin
Just a head's up that this is starting to affect numerous people.
If at all possible to prioritize it would be great.

Sorry: I somehow managed to not include links in my previous message.
https://forums.debian.net/viewtopic.php?t=155195
https://forums.debian.net/viewtopic.php?t=154857

Just because the raspi-firmware package is included on the d-i
installation media, it shouldn't necessarily be installed on an amd64
host. Or is this coming from live images?

[Magnus Wallin]

Post by Steve McIntyre
Hi Magnus, and thanks for the heads-up
[ . . . ]
Just because the raspi-firmware package is included on the d-i
installation media, it shouldn't necessarily be installed on an amd64
host. Or is this coming from live images?

Hi Steve!

Speaking for myself: I installed from a live image on the release day of Debian 12.

[Steve McIntyre]

Control: severity 1035382 grave

Post by Steve McIntyre
Hi Magnus, and thanks for the heads-up
[ . . . ]
Just because the raspi-firmware package is included on the d-i
installation media, it shouldn't necessarily be installed on an amd64
host. Or is this coming from live images?
Hi Steve!
Speaking for myself: I installed from a live image on the release day of Debian 12.

OK, that explains it. Let's try to get this fixed before 12.1...

I can see that there is already #1035382 open on the live side, let's
bump the severity on that.

[Magnus Wallin]

Post by Steve McIntyre

Post by Magnus Wallin
Speaking for myself: I installed from a live image on the release day of Debian 12.

OK, that explains it. Let's try to get this fixed before 12.1...
I can see that there is already #1035382 open on the live side, let's> bump the severity on that.

Aha, yes. Bug #1035382 seems to be the _actual_ bug for this.
Sorry if I mailed in the wrong bug report!