On Friday, 12 April 2024 13:51:37 BST Peter Humphrey wrote:
> On Tuesday, 9 April 2024 15:56:28 BST Wojciech Kuzyszyn wrote:
> > On Tue, 09 Apr 2024 14:23:31 +0100
> > 
> > Peter Humphrey <pe...@prh.myzen.co.uk> wrote:
> > > Hello list,
> > > 
> > > I want to move my Intel i5 NUC box to a place where Ethernet is not
> > > available, nor like to become so. That means I have to get WiFi
> > > working, but I've had no success so far. The wiki pages are many,
> > > confusing and contradictory, so I'd like the panel's advice on the
> > > way to proceed.
> > > 
> > > The first thing I tried was the traditional wpa_supplicant, which
> > > seemed to go well - except that I couldn't get the link out of the
> > > DOWN state.
> > > 
> > > Then I tried NetworkManager, and failed with that too.
> > > 
> > > This is the hardware:
> > > # lspci -v -s 00:14.3
> > > 00:14.3 Network controller: Intel Corporation Raptor Lake PCH CNVi
> > > WiFi (rev 01)
> > > --->8
> > > 
> > >         Kernel driver in use: iwlwifi
> > >         Kernel modules: iwlwifi
> > > 
> > > And this is dmesg:
> > > 
> > > $ dmesg | grep -i wifi
> > > [    1.622343] Intel(R) Wireless WiFi driver for Linux
> > > [    1.622432] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
> > > [    1.625069] iwlwifi 0000:00:14.3: Detected crf-id 0x400410, cnv-id
> > > 0x80400 wfpm id 0x80000020
> > > [    1.625121] iwlwifi 0000:00:14.3: PCI dev 51f1/0094, rev=0x370,
> > > rfid=0x2010d000
> > > [    1.625313] Loading firmware: iwlwifi-so-a0-gf-a0-86.ucode
> > > [    1.626644] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ
> > > Version: 0.0.2.41
> > > [    1.626902] iwlwifi 0000:00:14.3: loaded firmware version
> > > 86.fb5c9aeb.0 so- a0-gf-a0-86.ucode op_mode iwlmvm
> > > [    1.643426] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6E AX211
> > > 160MHz, REV=0x370
> > > [    1.651382] iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
> > > [    1.809375] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
> > > [    1.809385] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
> > > [    1.809394] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
> > > [    1.809401] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
> > > [    1.809403] Loading firmware: iwlwifi-so-a0-gf-a0.pnvm
> > > [    1.810724] iwlwifi 0000:00:14.3: loaded PNVM version e28bb9d7
> > > [    1.810817] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
> > > [    1.825831] iwlwifi 0000:00:14.3: Detected RF GF, rfid=0x2010d000
> > > [    1.897387] iwlwifi 0000:00:14.3: base HW address:
> > > f4:6d:3f:2a:33:3e
> > > 
> > > Would net-wireless/iwd get me a bit further?
> > > 
> > > Meanwhile, I'll keep on exploring with the results of
> > > sys-apps/hw-probe.
> > 
> > Hello!
> > 
> > I have never managed to get WiFi working with iwlwifi, but iwd works
> > great for me. Give it a try!
> 
> According to
> https://wiki.gentoo.org/wiki/Handbook:AMD64/Networking/Wireless, "the
> net-wireless/iw software...cannot connect to WPA-only Access Points."
> 
> I think my Fritz!Box 7530 router has that limitation, but It's hard to know.

For clarity:

The iwlwifi is a kernel driver for Intel wireless chips.

The net-wireless/iw software can be used to manage the wireless association 
with an AP if the latter has been configured to offer connections with the 
deprecated and insecure WEP, or no encryption.

The net-wireless/wpa_supplicant software can be used to manage the negotiation 
for a wireless connection with an AP when this has encryption enabled (WPA, 
WPA-2, WPA-3).

The net-wireless/iwd is a more modern software developed by Intel to replace 
wpa_supplicant.  In addition it will also create wireless interfaces as it 
needs to and manage these, as opposed to leaving this function to udev.  
Essentially iwd takes over the management of wireless interfaces and their 
encrypted communication with an AP in a standalone fashion.  I haven't tried 
this yet to find out how it behaves, but it is rumoured to be more polished 
than wpa_supplicant and can work without netifrc scripts or dhcpcd.

There are GUI front-ends for the above to suit various desktop and user 
preferences, some more polished than others.

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to