Mailing List Archive

On 09.04.24 15:23, Peter Humphrey 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.
>
Hey Peter

This might be the wrong firmware being loaded.

Are you building your the iwlwifi driver not as a module but directly
into the kernel?

Are you including your firmware into the kernel?

If you do the above, try loading the driver as a module. Also enable
both DVM and MVM Firmware support.

Then emerge sys-kernel/linux-firmware without USE=savedconfig.

Finally reboot and check wther it works. If it works, check which
firmware is loaded in your dmesg.

Re: Getting WiFi to work [ In reply to ]

wkuz at op

Apr 9, 2024, 7:56 AM

Post #3 of 15 (128 views)

On Tue, 09 Apr 2024 14:23:31 +0100
Peter Humphrey <peter@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!

--
xWK

Re: Getting WiFi to work [ In reply to ]

Apr 11, 2024, 5:49 AM

Post #4 of 15 (113 views)

On Tuesday, 9 April 2024 14:44:05 BST Paul Sopka wrote:
> On 09.04.24 15:23, Peter Humphrey 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.
>
> Hey Peter
>
> This might be the wrong firmware being loaded.
>
> Are you building your the iwlwifi driver not as a module but directly
> into the kernel?
>
> Are you including your firmware into the kernel?
>
> If you do the above, try loading the driver as a module. Also enable
> both DVM and MVM Firmware support.
>
> Then emerge sys-kernel/linux-firmware without USE=savedconfig.
>
> Finally reboot and check wther it works. If it works, check which
> firmware is loaded in your dmesg.

I decided to establish a firm, clean system to fall back to after messing about
with the various wifi packages, so I built a fresh system building on the
merged-usr stage-3. I was surprised to find that kde-plasma/powerdevil now
insists on installing Network Manager unless I set USE=-wireless against it.

Why has this happened? Can't the poor power devil cope with any other way of
running WiFi?

--
Regards,
Peter.

Re: Getting WiFi to work [ In reply to ]

Apr 11, 2024, 8:08 AM

Post #5 of 15 (113 views)

On Thursday, 11 April 2024 13:49:18 BST Peter Humphrey wrote:
> On Tuesday, 9 April 2024 14:44:05 BST Paul Sopka wrote:
> > On 09.04.24 15:23, Peter Humphrey 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.
> >
> > Hey Peter
> >
> > This might be the wrong firmware being loaded.
> >
> > Are you building your the iwlwifi driver not as a module but directly
> > into the kernel?
> >
> > Are you including your firmware into the kernel?
> >
> > If you do the above, try loading the driver as a module. Also enable
> > both DVM and MVM Firmware support.
> >
> > Then emerge sys-kernel/linux-firmware without USE=savedconfig.
> >
> > Finally reboot and check wther it works. If it works, check which
> > firmware is loaded in your dmesg.
>
> I decided to establish a firm, clean system to fall back to after messing
> about with the various wifi packages, so I built a fresh system building on
> the merged-usr stage-3. I was surprised to find that kde-plasma/powerdevil
> now insists on installing Network Manager unless I set USE=-wireless
> against it.
>
> Why has this happened? Can't the poor power devil cope with any other way of
> running WiFi?

The USE="wireless" flag on powerdevil is needed to save energy when the
bluetooth/wireless chip is idle. This function could be useful with laptops
running on battery.

If you set USE="-networkmanager" in make.conf and USE="-wireless" for the
powerdevil package you won't be bothered by this again.

Re: Getting WiFi to work [ In reply to ]

Apr 11, 2024, 8:15 AM

Post #6 of 15 (113 views)

On Thursday, 11 April 2024 16:08:35 BST Michael wrote:
> On Thursday, 11 April 2024 13:49:18 BST Peter Humphrey wrote:
--->8
> > I decided to establish a firm, clean system to fall back to after messing
> > about with the various wifi packages, so I built a fresh system building
> > on the merged-usr stage-3. I was surprised to find that kde-plasma/
> > powerdevil now insists on installing Network Manager unless I set USE=-
> > wireless against it.
> >
> > Why has this happened? Can't the poor power devil cope with any other way
> > of running WiFi?
>
> The USE="wireless" flag on powerdevil is needed to save energy when the
> bluetooth/wireless chip is idle. This function could be useful with laptops
> running on battery.
>
> If you set USE="-networkmanager" in make.conf and USE="-wireless" for the
> powerdevil package you won't be bothered by this again.

I already had USE="-networkmanager" in make.conf.

This is not a laptop and it has no battery. Nowhere on the system is there any
hint to the contrary, so I still think this has not been thought through. The
logic should have included alternatives to Network Manager.

--
Regards,
Peter.

Re: Getting WiFi to work [ In reply to ]

Apr 11, 2024, 8:16 AM

Post #7 of 15 (113 views)

On Tuesday, 9 April 2024 15:56:28 BST Wojciech Kuzyszyn wrote:

> I have never managed to get WiFi working with iwlwifi, but iwd works
> great for me. Give it a try!

I will - thanks!

--
Regards,
Peter.

Re: Getting WiFi to work [ In reply to ]

Apr 11, 2024, 8:18 AM

Post #8 of 15 (113 views)

On Thursday, 11 April 2024 16:15:52 BST Peter Humphrey wrote:
> On Thursday, 11 April 2024 16:08:35 BST Michael wrote:
> > On Thursday, 11 April 2024 13:49:18 BST Peter Humphrey wrote:
> --->8
>
> > > I decided to establish a firm, clean system to fall back to after
> > > messing
> > > about with the various wifi packages, so I built a fresh system building
> > > on the merged-usr stage-3. I was surprised to find that kde-plasma/
> > > powerdevil now insists on installing Network Manager unless I set USE=-
> > > wireless against it.
> > >
> > > Why has this happened? Can't the poor power devil cope with any other
> > > way
> > > of running WiFi?
> >
> > The USE="wireless" flag on powerdevil is needed to save energy when the
> > bluetooth/wireless chip is idle. This function could be useful with
> > laptops running on battery.
> >
> > If you set USE="-networkmanager" in make.conf and USE="-wireless" for the
> > powerdevil package you won't be bothered by this again.
>
> I already had USE="-networkmanager" in make.conf.
>
> This is not a laptop and it has no battery. Nowhere on the system is there
> any hint to the contrary, so I still think this has not been thought
> through. The logic should have included alternatives to Network Manager.

Yes, I agree wholeheartedly. However, these decisions are taken upstream,
where there is a tendency of convergence to monoculture.

Re: Getting WiFi to work [ In reply to ]

Apr 11, 2024, 8:24 AM

Post #9 of 15 (113 views)

On Thursday, 11 April 2024 16:18:51 BST Michael wrote:
> On Thursday, 11 April 2024 16:15:52 BST Peter Humphrey wrote:
> > On Thursday, 11 April 2024 16:08:35 BST Michael wrote:
> > > On Thursday, 11 April 2024 13:49:18 BST Peter Humphrey wrote:
> > --->8
> >
> > > > I decided to establish a firm, clean system to fall back to after
> > > > messing
> > > > about with the various wifi packages, so I built a fresh system
> > > > building
> > > > on the merged-usr stage-3. I was surprised to find that kde-plasma/
> > > > powerdevil now insists on installing Network Manager unless I set
> > > > USE=-
> > > > wireless against it.
> > > >
> > > > Why has this happened? Can't the poor power devil cope with any other
> > > > way
> > > > of running WiFi?
> > >
> > > The USE="wireless" flag on powerdevil is needed to save energy when the
> > > bluetooth/wireless chip is idle. This function could be useful with
> > > laptops running on battery.
> > >
> > > If you set USE="-networkmanager" in make.conf and USE="-wireless" for
> > > the
> > > powerdevil package you won't be bothered by this again.
> >
> > I already had USE="-networkmanager" in make.conf.
> >
> > This is not a laptop and it has no battery. Nowhere on the system is there
> > any hint to the contrary, so I still think this has not been thought
> > through. The logic should have included alternatives to Network Manager.
>
> Yes, I agree wholeheartedly. However, these decisions are taken upstream,
> where there is a tendency of convergence to monoculture.

Sorry, but I disagree with that last. The ebuild could have contained suitable
logic, and it still could.

--
Regards,
Peter.

Re: Getting WiFi to work [ In reply to ]

Apr 12, 2024, 5:51 AM

Post #10 of 15 (112 views)

On Tuesday, 9 April 2024 15:56:28 BST Wojciech Kuzyszyn wrote:
> On Tue, 09 Apr 2024 14:23:31 +0100
>
> Peter Humphrey <peter@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.

--
Regards,
Peter.

Re: Getting WiFi to work [ In reply to ]

Apr 12, 2024, 6:35 AM

Post #11 of 15 (112 views)

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 <peter@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.

Re: Getting WiFi to work [ In reply to ]

Apr 12, 2024, 8:05 AM

Post #12 of 15 (112 views)

On Friday, 12 April 2024 14:35:02 BST Michael wrote:

> 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).

Yes, I was aware of those.

> 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.

That's a better explanation than I've seen before - thanks!

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

Hm. I haven't found one for iwd yet...

--
Regards,
Peter.

Re: Getting WiFi to work [ In reply to ]

Apr 12, 2024, 8:39 AM

Post #13 of 15 (111 views)

On Friday, 12 April 2024 16:05:46 BST Peter Humphrey wrote:
> On Friday, 12 April 2024 14:35:02 BST Michael wrote:

> > There are GUI front-ends for the above to suit various desktop and user
> > preferences, some more polished than others.
>
> Hm. I haven't found one for iwd yet...

There is net-wireless/iwgtk in portage. Other GUI applications exist (idwgui,
dmenu-iwd-gui), plus the general GUI front ends of networkmanager and connman.

Re: Getting WiFi to work [ In reply to ]

Apr 13, 2024, 7:49 AM

Post #14 of 15 (107 views)

On Friday, 12 April 2024 16:39:12 BST Michael wrote:
> On Friday, 12 April 2024 16:05:46 BST Peter Humphrey wrote:
> > On Friday, 12 April 2024 14:35:02 BST Michael wrote:
> > > There are GUI front-ends for the above to suit various desktop and user
> > > preferences, some more polished than others.
> >
> > Hm. I haven't found one for iwd yet...
>
> There is net-wireless/iwgtk in portage. Other GUI applications exist
> (idwgui, dmenu-iwd-gui), plus the general GUI front ends of networkmanager
> and connman.

Of course, I found iwgtk a minute after sending that last. Network Manager is
what I'm trying to avoid, mostly because it makes a mess of my existing wired
LAN with its static addresses. I may have to revisit that whole setup.

--
Regards,
Peter.

Re: Getting WiFi to work [ In reply to ]

Apr 13, 2024, 10:28 AM

Post #15 of 15 (107 views)