On Wed 29 Mar 2023 at 09:39:01 (-0600), Ismael Farfán wrote:
> I tried with these 2 installers:
> 7da925a34f6f7ab6e39ad64514139afb  debian-bookworm-DI-alpha2-amd64-DVD-1.iso
> 547c0e2f85ec04ffec6d08a1e84c64e6
>  debian-bookworm-DI-alpha2-amd64-netinst.iso
> 
> both contain firmware-misc-nonfree_20230117-2_all.deb
> which is, I guess, where it's trying to load the firmware from.

I don't know how to access that file. Currently, bullseye
has version 20210315-3, and the files that I quoted,

> >  * MediaTek MT7921 hdr firmware, version 20230117170855a
> >    (mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin)
> >  * MediaTek MT7921 firmware, version 20230117170942
> >    (mediatek/WIFI_RAM_CODE_MT7961_1.bin)

are from a page that's slightly older than the version of the
package that it leads to, which you reference here:

> There's a newer version of the firmware in testing though:
> firmware-misc-nonfree_20230210-4_all.deb
> 
> I noticed there's a second installer in the *snapshots* section, it also
> fails to load the firmware but the *installation continues correctly* to
> the next step
> aa5e3fe762300ba87fce77a6bf260a3e  debian-testing-amd64-DVD-1.iso

. What version of firmware-misc-nonfree does that include?

. Does it try to load the two .bin files listed above?
  It doesn't help to write "(lots of this)" unless
  indicating whether any of the failures mention /your/
  device name, as opposed to similar-looking ones.
  It's normal for one module to try loading many .bins
  before the right one is found.

I have noticed that those .bin files vary between packages having
different dates:

$ ls -GlgR /tmp/202*
/tmp/20210315-3:
total 792
-rw-r--r-- 1  90464 Jul 25  2021 WIFI_MT7961_patch_mcu_1_2_hdr.bin
-rw-r--r-- 1 712832 Jul 25  2021 WIFI_RAM_CODE_MT7961_1.bin

/tmp/20230210-4:
total 796
-rw-r--r-- 1  92192 Mar 11 08:15 WIFI_MT7961_patch_mcu_1_2_hdr.bin
-rw-r--r-- 1 719156 Mar 11 08:15 WIFI_RAM_CODE_MT7961_1.bin
$ 

I haven't looked at which kernel modules try to load that firmware,
and whether they have changed.

Cheers,
David.

Reply via email to