From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Getting WiFi to work
Date: Thu, 11 Apr 2024 16:08:35 +0100 [thread overview]
Message-ID: <3770559.MHq7AAxBmi@rogueboard> (raw)
In-Reply-To: <5794281.DvuYhMxLoT@cube>
[-- Attachment #1: Type: text/plain, Size: 3909 bytes --]
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.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-04-11 15:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 13:23 [gentoo-user] Getting WiFi to work Peter Humphrey
2024-04-09 13:44 ` Paul Sopka
2024-04-11 12:49 ` Peter Humphrey
2024-04-11 15:08 ` Michael [this message]
2024-04-11 15:15 ` Peter Humphrey
2024-04-11 15:18 ` Michael
2024-04-11 15:24 ` Peter Humphrey
2024-04-09 14:56 ` Wojciech Kuzyszyn
2024-04-11 15:16 ` Peter Humphrey
2024-04-12 12:51 ` Peter Humphrey
2024-04-12 13:35 ` Michael
2024-04-12 15:05 ` Peter Humphrey
2024-04-12 15:39 ` Michael
2024-04-13 14:49 ` Peter Humphrey
2024-04-13 17:28 ` Michael
2024-04-19 16:02 ` SOLVED: " Peter Humphrey
2024-04-21 22:30 ` Wol
2024-04-21 22:58 ` Peter Humphrey
2024-05-28 14:08 ` Peter Humphrey
2024-05-28 14:52 ` Dale
2024-05-28 15:58 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3770559.MHq7AAxBmi@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox