On 07/02/2025 at 02:35, Lennart Sorensen wrote:
On Thu, Feb 06, 2025 at 11:35:28PM +0100, Pascal Hambourg wrote:
The installer supports wifi. It is expected that it complains about the
missing firmware but this should not prevent the wireless interface from
being available if an alternative firmware file is present.
Can you compress and attach the installer log (/var/log/installer/syslog) so
that we can try to understand what went wrong ?
I wonder if it didn't realize that the 92 firmware existed and just tried
for the 93 firmware.
The kernel driver tried and failed to load 93 first and sent an error
message even though it successfully loader 92 right after. The installer
detected the error message about 93 without knowing that 92 was an
alternative. It is not trivial to detect whether two firwares are
alternatives or required.
It detected the network interface but looked like
it was trying to treat it as a wired ethernet port and ran dhcp on it
rather than ask about wifi. That of course did not work.
Yes, it looks like netcfg did not detect wlp9s0f0 as a wireless
interface. It may be related with this line:
> Feb 5 18:21:42 kernel: [ 105.579647] warning: `netcfg' uses
wireless extensions which will stop working for Wi-Fi 7 hardware; use
nl80211
and it seems that the wireless controller is wifi 7:
> 09:00.0 Network controller [0280]: Intel Corporation Wi-Fi
7(802.11be) AX1775*/AX1790*/BE20*/BE401/BE1750* 2x2 [8086:272b] (rev 1a)
So maybe netcfg needs an update for wifi 7 ?
I wonder why the firmware package doesn't have the version the kernel
is looking for. Perhaps it needs an update?
No clue. It has iwlwifi-gl-c0-fm-c0-92.ucode and
iwlwifi-gl-c0-fm-c0-94.ucode but not iwlwifi-gl-c0-fm-c0-93.ucode. But
this is definitely not the culprit.
Audio requires installing firmware-misc-nonfree for tas2781 firmware.
After that audio and volume keys and such works fine.
The installer has provisions to install firmware packages needed by hardware
components, but here I suspect that it requires that the sound driver is
loaded first, and sound drivers are not loaded by default.
Alternatively to Holger's suggestion, you can start the installer in
expert mode and select sound modules in the installer component screen.
Definitely possible. Odd that a sound chip needs firmware, but
unfortunate that it isn't handled automatically given installing the
firmware package needed was the only thing it required to fully work.
Do you know which kernel module requires this firmware, and can you post
the output of lsmod ?
