Charles Curley <charlescur...@charlescurley.com> (2023-04-03):
> Grepping in the syslog indicates that the installer is looking in the
> wrong place on the CD-ROM.

No, it isn't.

> At approximately 21:50:11 syslog reports that
> 
> check-missing-firmware: installing firmware package 
> /cdrom/firmware/firmware-ipw2x00_20230210-4_all.deb
> 
> However, searching the CD-ROM indicates that the firmware package is
> elsewhere:
> 
> root@hawk:/crc/isos/debian/12.x/weekly# mkdir loop
> root@hawk:/crc/isos/debian/12.x/weekly# mount debian-testing-i386-netinst.iso 
> loop
> mount: /crc/isos/debian/12.x/weekly/loop: WARNING: source write-protected, 
> mounted read-only.
> root@hawk:/crc/isos/debian/12.x/weekly# grep ipw loop/md5sum.txt 
> 7e6f43f1dd1ec551f5eed63652f35ff0  ./firmware/dep11/firmware-ipw2x00.component
> e6eb2bebabf6d793ebd5ebe958461cde  ./firmware/dep11/firmware-ipw2x00.patterns
> 8ff7cc60a37ed026c84613021cd4eb05  
> ./pool/non-free-firmware/f/firmware-nonfree/firmware-ipw2x00_20230210-4_all.deb
> root@hawk:/crc/isos/debian/12.x/weekly# ll 
> loop/pool/non-free-firmware/f/firmware-nonfree/firmware-ipw2x00_20230210-4_all.deb
>  
> -r--r--r-- 2 root root 279224 Mar 11 14:40 
> loop/pool/non-free-firmware/f/firmware-nonfree/firmware-ipw2x00_20230210-4_all.deb
> root@hawk:/crc/isos/debian/12.x/weekly# 

That search is incomplete, you didn't even try to list the contents of
the /firmware directory, where firmware-ipw2x00_20230210-4_all.deb is
found…

    kibi@tokyo:/tmp$ sudo mount debian-testing-i386-netinst.iso /mnt
    mount: /mnt: WARNING: source write-protected, mounted read-only.
    
    kibi@tokyo:/tmp$ ls -l /mnt/firmware/firmware-ipw2x00_20230210-4_all.deb
    -r--r--r-- 2 root root 279224 Mar 11 22:40 
/mnt/firmware/firmware-ipw2x00_20230210-4_all.deb

> Apr  3 21:50:10 check-missing-firmware: looking at dmesg for the first time
> Apr  3 21:50:10 check-missing-firmware: saving timestamp for a later use: [  
> 238.216575]
> Apr  3 21:50:10 check-missing-firmware: looking for firmware file 
> ipw2200-bss.fw requested by ipw2200
> Apr  3 21:50:10 check-missing-firmware: looking for firmware file 
> ipw2200-bss.fw requested by ipw2200
> Apr  3 21:50:10 check-missing-firmware: missing firmware files 
> (ipw2200-bss.fw) for ipw2200
> Apr  3 21:50:10 check-missing-firmware: mainloop iteration #1
> Apr  3 21:50:10 check-missing-firmware: lookup with 
> /cdrom/firmware/Contents-firmware
> Apr  3 21:50:11 check-missing-firmware: installing firmware package 
> /cdrom/firmware/firmware-ipw2x00_20230210-4_all.deb (non-free-firmware)
> Apr  3 21:50:11 check-missing-firmware: removing and loading kernel module 
> ipw2200

Everything seems to be working as intended…

> Apr  3 21:50:11 kernel: [  241.336392] libipw: 802.11 data/management/control 
> stack, git-1.1.13
> Apr  3 21:50:11 kernel: [  241.336404] libipw: Copyright (C) 2004-2005 Intel 
> Corporation <jketr...@linux.intel.com>
> Apr  3 21:50:11 kernel: [  241.364937] ipw2200: Intel(R) PRO/Wireless 
> 2200/2915 Network Driver, 1.2.2kmprq
> Apr  3 21:50:11 kernel: [  241.364945] ipw2200: Copyright(c) 2003-2006 Intel 
> Corporation
> Apr  3 21:50:11 kernel: [  241.365239] ipw2200: Detected Intel PRO/Wireless 
> 2200BG Network Connection
> Apr  3 21:50:11 kernel: [  241.365334] ipw2200 0000:02:02.0: firmware: failed 
> to load ipw2200-bss.fw (-2)
> Apr  3 21:50:11 kernel: [  241.365363] ipw2200 0000:02:02.0: firmware: failed 
> to load ipw2200-bss.fw (-2)
> Apr  3 21:50:11 kernel: [  241.365367] ipw2200 0000:02:02.0: Direct firmware 
> load for ipw2200-bss.fw failed with error -2
> Apr  3 21:50:11 kernel: [  241.365374] ipw2200: Unable to load firmware: -2
> Apr  3 21:50:11 kernel: [  241.365478] ipw2200: probe of 0000:02:02.0 failed 
> with error -5

It'd be helpful to have the contents of /lib/firmware (in the installer
context) at this point.

    kibi@tokyo:/tmp$ dpkg --contents 
/mnt/firmware/firmware-ipw2x00_20230210-4_all.deb|grep ipw2200-bss.fw
    -rw-r--r-- root/root    191154 2023-03-11 15:15 
./lib/firmware/ipw2200-bss.fw

Arguably check-missing-firmware could be more verbose about what happens
around license accepting. What do debconf exchanges look like? You can
use DEBCONF_DEBUG=developer to see them all.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

Attachment: signature.asc
Description: PGP signature

Reply via email to