Hi Andrey, Andrey Rakhmatullin <[email protected]> (2023-04-24): > During the network hardware detection it said "cannot find your > network card" and provided the list of supported drivers, I chose > "None" and it happily proceeded to the WiFi network selection step.
Was it that one?
Template: netcfg/no_interfaces
Type: error
# :sl2:
_Description: No network interfaces detected
No network interfaces were found. The installation
system was unable to find a network device.
.
You may need to load a specific module for your network card, if you have
one. For this, go back to the network hardware detection step.
> There were a lot of firmware loading errors in
> the dmesg, about "mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin".
> /var/log/installer/syslog suggests it found the firmware later and
> loaded it, maybe there was some race condition or wrong check in the
> d-i module?
As far as I understand, everything looks correct in syslog (trimming
heavily), as in the module requests stuff, d-i notices, performs a
lookup, installs, checks again, is satisfied with the results and moves
on:
Apr 24 07:56:11 kernel: [ 98.839730] mt7921e 0000:02:00.0: Direct
firmware load for mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin failed with error
-2
…
Apr 24 07:56:12 kernel: [ 99.594055] mt7921e 0000:02:00.0: hardware init
failed
Apr 24 07:56:12 check-missing-firmware: looking at dmesg for the first time
Apr 24 07:56:12 check-missing-firmware: saving timestamp for a later use: [
99.594055]
Apr 24 07:56:12 check-missing-firmware: looking for firmware file
mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin requested by mt7921e
…
Apr 24 07:56:12 check-missing-firmware: missing firmware files
(mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin) for mt7921e
Apr 24 07:56:12 check-missing-firmware: mainloop iteration #1
Apr 24 07:56:12 check-missing-firmware: lookup with
/cdrom/firmware/Contents-firmware
Apr 24 07:56:12 check-missing-firmware: installing firmware package
/cdrom/firmware/firmware-misc-nonfree_20230210-4_all.deb (non-free-firmware)
Apr 24 07:56:14 check-missing-firmware: removing and loading kernel module
mt7921e
Apr 24 07:56:14 kernel: [ 102.538531] mt7921e 0000:02:00.0: ASIC revision:
79220010
Apr 24 07:56:15 kernel: [ 102.620936] mt7921e 0000:02:00.0: firmware:
direct-loading firmware mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin
Apr 24 07:56:15 kernel: [ 102.620945] mt7921e 0000:02:00.0: HW/SW Version:
0x8a108a10, Build Time: 20221227123154a
Apr 24 07:56:15 kernel: [ 102.620945]
Apr 24 07:56:15 kernel: [ 102.990004] mt7921e 0000:02:00.0: firmware:
direct-loading firmware mediatek/WIFI_RAM_CODE_MT7922_1.bin
Apr 24 07:56:15 kernel: [ 102.990024] mt7921e 0000:02:00.0: WM Firmware
Version: ____000000, Build Time: 20221227123243
Apr 24 07:56:15 kernel: [ 103.039238] mt7921e 0000:02:00.0: firmware:
direct-loading firmware mediatek/WIFI_RAM_CODE_MT7922_1.bin
Apr 24 07:56:16 check-missing-firmware: looking at dmesg again, restarting
from timestamp: [ 99.594055]
Apr 24 07:56:16 check-missing-firmware: timestamp found, truncating dmesg
accordingly
Apr 24 07:56:16 check-missing-firmware: saving timestamp for a later use: [
103.039238]
Apr 24 07:56:16 check-missing-firmware: no missing firmware in loaded
kernel modules
Apr 24 07:56:16 kernel: [ 104.087747] mt7921e 0000:02:00.0 wlp2s0: renamed
from wlan0
Apr 24 07:56:16 net/hw-detect.hotplug: Detected hotpluggable network
interface wlp2s0
What I find strange is that netcfg (that supplies the template mentioned
above) starts way after that:
Apr 24 07:56:38 main-menu[808]: INFO: Menu item 'netcfg' selected
Apr 24 07:56:38 netcfg[7385]: INFO: Starting netcfg v.1.184
at which time, wlp2s0 is definitely up. And from a quick glance I didn't
spot where the error message would be have displayed/where you would
have been prompted about modules.
Let's keep in mind mt7921e has been playing tricks on us in the past:
https://salsa.debian.org/kernel-team/linux/-/merge_requests/673
Maybe there's something (else) weird going on?
It would definitely be helpful if you could:
- confirm which message was presented;
- roughly at which point.
I realize it's probably not trivial for you to navigate the syslog, but
based on when network detection happened, etc. you might remember the
sequence of events.
(I think we should have least have an extra log line when we present the
screen you saw; unless I failed to spot it, which is entirely possible.)
Cheers,
--
Cyril Brulebois ([email protected]) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
