[Forgot to compress the logs so that the mail reaches debian-boot, so
resending to the list only. Please reply to 1033...@bugs.debian.org]
Hello,
On 04/04/2023 à 19:39, Cyril Brulebois wrote:
I'm attaching syslog again, so that it reaches the BTS and interested
people can look at those debconf exchanges.
I tested too, not with firmware-ipw2x00 which was not convenient for me,
but with a custom firmware-prism54 package based on the same model.
With Contents-firmware, the license text is not shown and cannot be
accepted. syslog extract:
Apr 6 16:23:16 check-missing-firmware: lookup with
/media/firmware/Contents-firmware
Apr 6 16:23:16 check-missing-firmware: installing firmware package
/media/firmware/firmware-prism54_2_all.deb (non-free)
Apr 6 16:23:16 debconf: --> X_LOADTEMPLATEFILE
/var/lib/dpkg/info/firmware-prism54.templates firmware-prism54
Apr 6 16:23:16 debconf: <-- 0 OK
Apr 6 16:23:16 debconf: --> X_SAVE
Apr 6 16:23:16 check-missing-firmware: removing and loading kernel module usb
Apr 6 16:23:16 kernel: [ 153.930919] usbcore: deregistering interface driver
p54usb
Apr 6 16:23:16 kernel: [ 153.982470] usb 2-4: Loading firmware file isl3886usb
Apr 6 16:23:16 kernel: [ 153.982497] usb 2-4: firmware: failed to load
isl3886usb (-2)
Apr 6 16:23:16 kernel: [ 153.982507] usb 2-4: firmware: failed to load
isl3886usb (-2)
Apr 6 16:23:16 kernel: [ 153.982509] usb 2-4: Direct firmware load for
isl3886usb failed with error -2
Apr 6 16:23:16 kernel: [ 153.982511] p54usb 2-4:1.0: failed to initialize
device (-2)
Apr 6 16:23:16 kernel: [ 153.982574] usbcore: registered new interface driver
p54usb
Apr 6 16:23:16 check-missing-firmware: removing and loading kernel module
usbcore as well (actual module for usb)
Apr 6 16:23:16 check-missing-firmware: modprobe: FATAL: Module usbcore is in
use.
Apr 6 16:23:16 debconf: <-- 0 OK
Apr 6 16:23:16 debconf: --> VERSION 2.0
Apr 6 16:23:16 debconf: <-- 0 2.0
Apr 6 16:23:17 check-missing-firmware: looking at dmesg again, restarting from
timestamp: [ 92.116707]
Without Contents-firmware, the license text is shown and can be
accepted. syslog extract:
Apr 6 16:32:49 check-missing-firmware: lookup without
/media/firmware/Contents-firmware
Apr 6 16:32:49 check-missing-firmware: installing firmware package
/media/firmware/firmware-prism54_2_all.deb
Apr 6 16:32:49 debconf: --> X_LOADTEMPLATEFILE
/var/lib/dpkg/info/firmware-prism54.templates firmware-prism54
Apr 6 16:32:49 debconf: <-- 0 OK
Apr 6 16:32:49 debconf: --> X_SAVE
Apr 6 16:32:50 debconf: <-- 0 OK
Apr 6 16:32:50 debconf: --> VERSION 2.0
Apr 6 16:32:50 debconf: <-- 0 2.0
Apr 6 16:32:50 debconf: --> CAPB backup
Apr 6 16:32:50 debconf: <-- 0 multiselect backup progresscancel align escape
plugin-terminal
Apr 6 16:32:50 debconf: --> GET firmware-prism54/license/accepted
Apr 6 16:32:50 debconf: <-- 0 false
Apr 6 16:32:50 debconf: --> GET firmware-prism54/license/accepted
Apr 6 16:32:50 debconf: <-- 0 false
Apr 6 16:32:50 debconf: --> FSET firmware-prism54/license/accepted seen false
Apr 6 16:32:50 debconf: <-- 0 false
Apr 6 16:32:50 debconf: --> INPUT critical firmware-prism54/license/accepted
Apr 6 16:32:50 debconf: <-- 0 question will be asked
Apr 6 16:32:50 debconf: --> GO
Apr 6 16:35:25 debconf: <-- 0 ok
Apr 6 16:35:25 debconf: --> GET firmware-prism54/license/accepted
Apr 6 16:35:25 debconf: <-- 0 true
Apr 6 16:35:25 check-missing-firmware: removing and loading kernel module usb
A difference between the two relevant sections in check-missing-firmware
is that install_firmware_pkg() is executed in a pipeline when a
Contents-firmware file is present, and not when it is not present. I do
not know enough about debconf to figure out how the pipeline may
interfere with it. Maybe something to do with standard input and output ?
Full syslogs attached.
syslog.tar.gz
Description: application/gzip
