Package: netcfg Version: 1.176 I tried to install unofficial (due to various drivers, in particular the Intel WiFi network driver) Debian bullseye. During the installation, I was asked for the network card, and I chose a wireless one: wlp179s0, which is in my case WLAN/Bluetooth Adapter PCIe (WL-PCI ASUS PCE-AX3000 BT5.0) Dual-Band (2,4 GHz/5 GHz), Bluetooth-Version 5.0. I was asked for the WLAN ID, which I provided (the SSID of my router). Then I was asked for the type, which I provided as WPA/WPA2 PSK in my case (WPA2 for my router). Then I was asked for the WPA-Passphrase, which I typed in (WPA2 password for my router). Then a progress bar depicting an authentication attempt with the access point appeared. For a few minutes the bar continuously made progress (the messages on the fourth console are attached) and finally reached 100%. Then I saw a failure message asking me to verify the WPA-parameters which I input. I repeated the process several times, with the same result: no network during installation. The wireless card itself and the SSID-password combination are o.k. because I got connection using Debian live from the same installation drive. (Moreover, on a similar machine with the same network card the nerwork happily starts with NetworkManager, though with ifupdown there is a delay of several minutes at boot; cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993826). Any bugfix? Any help? Peter
Hi Peter, and thanks for your report. A couple of things: please avoid sending HTML messages in general. And since you included a large picture (by mailing list configuration standards), your report was not delivered to our list. Peter Mueller <petermueller@ro.ru> (2022-03-16): Over the course of the installation process, did you get any messages regarding missing firmware? I'm not sure this would explain the issue you're describing, but that's an easy item to check for… The live test is quite useful, thanks for mentioning it. I'm wondering whether this could be due to missing crypto modules inside our image, which I've seen to be the reason for failure to associate from the installer, while the installed system was fine. Any chance you could start the live image again, save the output of `lsmod`, and attach it here, using reply-all? Cheers,
Dear Cyril, thanks for the quick answer! I apologize; so far, unable to. (I found no option to switch to plain text from HTML in the Web interface, and my e-mail client so far failed to send from that domain for an unknown reason.) No such messages in the user interface. As for the console, I'll try to check. Will do, though not immediately. In several days I'm likely to get again to the machine on which the installation fails. As for the very similar machine with the same network card (and for which I recall the installer had similar problems), there is an lsmod log in the aforementioned bug report. If netcfg uses the same logic as ifupdown on an installed system, that bug report is probably connected. Cheers, Peter
The last message got through, though, from my e-mail client, so the sending failure is apparently random. I could to try to re-send the report as plain to the list (debian-boot@lists.debian.org, right?), but, as there's go guarantee of success, it'd be better if I could kindly ask you to do this on my behalf.
The output of lsmod from the same Debian live is attached. I apologize for the delay. Cheers, Peter The live test is quite useful, thanks for mentioning it. I'm wondering whether this could be due to missing crypto modules inside our image, which I've seen to be the reason for failure to associate from the installer, while the installed system was fine. Any chance you could start the live image again, save the output of `lsmod`, and attach it here, using reply-all?
Cyril, in the attachment you find a screenshot with more messages. Does that make sense to you? Sorry for the HTML (I couldn't send as plain text this time.) Peter.