2023-04-07 19:30:54

by Aaron Dewell

[permalink] [raw]
Subject: ax204/Intel NUC13 i9

Hi all,

I've just received the new NUC13 and it's quite nice. However, the
wireless chip appears to be too new to have mainline support. To that
end, I've been ... messing with it. :)

I believe the marketing term is an AX204. I know for certain it's
0x7AF0 0x1692. I am using kernel source 6.3-rc4 and attempting to add a
line to iwlwifi/pcie/drv.c that looks like this:

IWL_DEV_INFO(0x7AF0, 0x1692, something?, iwl_ax204_name),

I have looked at:
https://www.intel.com/content/www/us/en/support/articles/000005511/wireless.html
However, this product isn't listed.

I know I'm missing the "something?" above and possibly on the wrong path
on other things. I've had a couple of guesses that didn't work out
(stabbing in the dark), so asking here. Any assistance appreciated!

Thanks!

00:14.3 Network controller [0280]: Intel Corporation Alder Lake-S PCH
CNVi WiFi [8086:7af0] (rev 11)
Subsystem: Rivet Networks Alder Lake-S PCH CNVi WiFi [1a56:1692]


2023-04-07 21:31:33

by James

[permalink] [raw]
Subject: Re: ax204/Intel NUC13 i9


On 2023-04-07 15:28, Aaron Dewell wrote:
> Hi all,
>
> I've just received the new NUC13 and it's quite nice. However, the
> wireless chip appears to be too new to have mainline support. To that
> end, I've been ... messing with it. :)
>
> I believe the marketing term is an AX204. I know for certain it's
> 0x7AF0 0x1692. I am using kernel source 6.3-rc4 and attempting to add a
> line to iwlwifi/pcie/drv.c that looks like this:
>
> IWL_DEV_INFO(0x7AF0, 0x1692, something?, iwl_ax204_name),
>
> I have looked at:
> https://www.intel.com/content/www/us/en/support/articles/000005511/wireless.html
> However, this product isn't listed.
>
> I know I'm missing the "something?" above and possibly on the wrong path
> on other things. I've had a couple of guesses that didn't work out
> (stabbing in the dark), so asking here. Any assistance appreciated!
>
> Thanks!
>
> 00:14.3 Network controller [0280]: Intel Corporation Alder Lake-S PCH
> CNVi WiFi [8086:7af0] (rev 11)
> Subsystem: Rivet Networks Alder Lake-S PCH CNVi WiFi [1a56:1692]


Intel bought Rivet Networks in 2020.

The card should be supported:

https://www.intel.ca/content/www/ca/en/support/articles/000088040/wireless.html

Have you installed the Intel wireless drivers?

I think Intel drivers are in kernel but they should be installed by most
distros.


2023-04-07 21:52:32

by Aaron Dewell

[permalink] [raw]
Subject: Re: ax204/Intel NUC13 i9


On Apr 7 2023, at 3:08 pm, James <[email protected]> wrote:

>
> On 2023-04-07 15:28, Aaron Dewell wrote:
>> Hi all,
>>
>> I've just received the new NUC13 and it's quite nice. However, the
>> wireless chip appears to be too new to have mainline support. To that
>> end, I've been ... messing with it. :)
>>
>> I believe the marketing term is an AX204. I know for certain it's
>> 0x7AF0 0x1692. I am using kernel source 6.3-rc4 and attempting to
>> add a
>> line to iwlwifi/pcie/drv.c that looks like this:
>>
>> IWL_DEV_INFO(0x7AF0, 0x1692, something?, iwl_ax204_name),
>>
>> I have looked at:
>> https://www.intel.com/content/www/us/en/support/articles/000005511/wireless.html
>> However, this product isn't listed.
>>
>> I know I'm missing the "something?" above and possibly on the wrong path
>> on other things. I've had a couple of guesses that didn't work out
>> (stabbing in the dark), so asking here. Any assistance appreciated!
>>
>> Thanks!
>>
>> 00:14.3 Network controller [0280]: Intel Corporation Alder Lake-S PCH
>> CNVi WiFi [8086:7af0] (rev 11)
>> Subsystem: Rivet Networks Alder Lake-S PCH CNVi WiFi [1a56:1692]
>
>
> Intel bought Rivet Networks in 2020.
>
> The card should be supported:
>
> https://www.intel.ca/content/www/ca/en/support/articles/000088040/wireless.html
>
> Have you installed the Intel wireless drivers?
>
> I think Intel drivers are in kernel but they should be installed by
> most
> distros.

It's Debian Bookworm (testing) which comes with 6.1.20, however, the
card is not recognized, thus why I started messing with it. I tried the
latest Xanmod kernel as well before I started diving into source in
6.3-rc4 (which also didn't recognize the card as shipped). I couldn't
find any reference to the PCI ID in the source either, which made sense
as to why it wouldn't be recognized.

2023-04-07 22:00:30

by Aaron Dewell

[permalink] [raw]
Subject: Re: ax204/Intel NUC13 i9


On Apr 7 2023, at 3:41 pm, Aaron Dewell <[email protected]> wrote:

>
> On Apr 7 2023, at 3:08 pm, James <[email protected]> wrote:
>
>>
>> On 2023-04-07 15:28, Aaron Dewell wrote:
>>> Hi all,
>>>
>>> I've just received the new NUC13 and it's quite nice. However, the
>>> wireless chip appears to be too new to have mainline support. To that
>>> end, I've been ... messing with it. :)
>>>
>>> I believe the marketing term is an AX204. I know for certain it's
>>> 0x7AF0 0x1692. I am using kernel source 6.3-rc4 and attempting to
>>> add a
>>> line to iwlwifi/pcie/drv.c that looks like this:
>>>
>>> IWL_DEV_INFO(0x7AF0, 0x1692, something?, iwl_ax204_name),
>>>
>>> I have looked at:
>>> https://www.intel.com/content/www/us/en/support/articles/000005511/wireless.html
>>> However, this product isn't listed.
>>>
>>> I know I'm missing the "something?" above and possibly on the wrong path
>>> on other things. I've had a couple of guesses that didn't work out
>>> (stabbing in the dark), so asking here. Any assistance appreciated!
>>>
>>> Thanks!
>>>
>>> 00:14.3 Network controller [0280]: Intel Corporation Alder Lake-S PCH
>>> CNVi WiFi [8086:7af0] (rev 11)
>>> Subsystem: Rivet Networks Alder Lake-S PCH CNVi WiFi [1a56:1692]
>>
>>
>> Intel bought Rivet Networks in 2020.
>>
>> The card should be supported:
>>
>> https://www.intel.ca/content/www/ca/en/support/articles/000088040/wireless.html
>>
>> Have you installed the Intel wireless drivers?
>>
>> I think Intel drivers are in kernel but they should be installed by
>> most
>> distros.
>
> It's Debian Bookworm (testing) which comes with 6.1.20, however, the
> card is not recognized, thus why I started messing with it. I tried the
> latest Xanmod kernel as well before I started diving into source in
> 6.3-rc4 (which also didn't recognize the card as shipped). I couldn't
> find any reference to the PCI ID in the source either, which made sense
> as to why it wouldn't be recognized.

Here are the errors from the shipping Debian kernel (unmodified):

[ 2.664162] Intel(R) Wireless WiFi driver for Linux
[ 2.664207] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 2.667274] AVX2 version of gcm_enc/dec engaged.
[ 2.667327] AES CTR mode by8 optimization enabled
[ 2.668601] iwlwifi: No config found for PCI dev 7af0/1692,
rev=0x430, rfid=0x3010d000
[ 2.668628] iwlwifi: probe of 0000:00:14.3 failed with error -22

2023-04-07 23:47:25

by James

[permalink] [raw]
Subject: Re: ax204/Intel NUC13 i9

https://www.google.com/search?client=firefox-b-d&q=iwlwifi%3A+No+config+found


I suspect a firmware problem.

Do you know how to install the latest firmware from git?

I would copy it to /lib/firmware if that is your distro keeps it:

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

2023-04-08 01:11:06

by Aaron Dewell

[permalink] [raw]
Subject: Re: ax204/Intel NUC13 i9


On Apr 7 2023, at 5:40 pm, James <[email protected]> wrote:
> https://www.google.com/search?client=firefox-b-d&q=iwlwifi%3A+No+config+found
>
>
> I suspect a firmware problem.
>
> Do you know how to install the latest firmware from git?
>
> I would copy it to /lib/firmware if that is your distro keeps it:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

Did that first thing.

2023-04-10 21:50:32

by Aaron Dewell

[permalink] [raw]
Subject: Re: ax204/Intel NUC13 i9

To summarize up to now and reboot the discussion:

I have installed firmware-git. This is the file that was extracted into /lib/firmware:
-rw-r--r-- 1 root root 429469981 Apr 2 10:47 linux-firmware-iwlwifi-fw-2023-03-30.tar.gz

The card is not successfully initialized by the stock (6.1.20) kernel:
[ 2.284183] Intel(R) Wireless WiFi driver for Linux
[ 2.284221] cryptd: max_cpu_qlen set to 1000
[ 2.284223] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 2.286133] iwlwifi: No config found for PCI dev 7af0/1692,
rev=0x430, rfid=0x3010d000
[ 2.286155] iwlwifi: probe of 0000:00:14.3 failed with error -22

The distribution is Debian Bookworm (testing), which has kernel:
Linux shrub 6.1.0-7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-1
(2023-03-19) x86_64 GNU/Linux

The card identifies as 0x7AF0, 0x1692:
00:14.3 Network controller [0280]: Intel Corporation Alder Lake-S PCH
CNVi WiFi [8086:7af0] (rev 11)
Subsystem: Rivet Networks Alder Lake-S PCH CNVi WiFi [1a56:1692]
Flags: fast devsel, IRQ 18, IOMMU group 6
Memory at 604c124000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [80] MSI-X: Enable- Count=16 Masked-
Capabilities: [100] Latency Tolerance Reporting
Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0
Len=014 <?>
Kernel modules: iwlwifi

Granted that I am no expert on this, but I know enough to get myself
into trouble, which is what I proceeded to do. I believe (but could
well be mistaken) that what is needed is a configuration line for that
PCI ID in iwlwifi/pcie/drv.c, something like this one:

IWL_DEV_INFO(0x7F70, 0x1692, iwlax411_2ax_cfg_so_gf4_a0, iwl_ax411_killer_1690i_name),

My attempt was to duplicate then change the new line from 7F70 to 7AF0,
but that was also not successful, with such errors as (clipping because
it's rather long):

[...]
[ 3.960164] iwlwifi 0000:00:14.3: Microcode SW error detected.
Restarting 0x0.
[...]
[ 3.960551] iwlwifi 0000:00:14.3: Starting mac, retry will be
triggered anyway
[ 3.960594] iwlwifi 0000:00:14.3: FW error in SYNC CMD ADD_STA
[ 3.960600] Call Trace:
[ 3.960602] <TASK>
[ 3.960602] dump_stack_lvl+0x36/0x50
[ 3.960606] iwl_trans_txq_send_hcmd+0x338/0x450 [iwlwifi]
[...]

It does produce an interface but it is unusable.

I assume (but I am definitely out of my depth at this point) that it is
due to the wrong firmware being referenced by that line of code (i.e.
it's a different firmware for 7F70 vs. 7AF0) but I also don't know what
the correct one is, thus I'm asking here. If I'm totally on the wrong
track, I'm fine with that too, I just want to get it working.

Thanks!


2023-04-11 09:11:54

by Greenman, Gregory

[permalink] [raw]
Subject: Re: ax204/Intel NUC13 i9

On Mon, 2023-04-10 at 15:45 -0600, Aaron Dewell wrote:
> To summarize up to now and reboot the discussion:
>
> I have installed firmware-git. This is the file that was extracted into /lib/firmware:
> -rw-r--r--  1 root  root 429469981 Apr  2 10:47 linux-firmware-iwlwifi-fw-2023-03-30.tar.gz
>
> The card is not successfully initialized by the stock (6.1.20) kernel:
> [    2.284183] Intel(R) Wireless WiFi driver for Linux
> [    2.284221] cryptd: max_cpu_qlen set to 1000
> [    2.284223] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
> [    2.286133] iwlwifi: No config found for PCI dev 7af0/1692,
> rev=0x430, rfid=0x3010d000
> [    2.286155] iwlwifi: probe of 0000:00:14.3 failed with error -22
>
> The distribution is Debian Bookworm (testing), which has kernel:
> Linux shrub 6.1.0-7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-1
> (2023-03-19) x86_64 GNU/Linux
>
> The card identifies as 0x7AF0, 0x1692:
> 00:14.3 Network controller [0280]: Intel Corporation Alder Lake-S PCH
> CNVi WiFi [8086:7af0] (rev 11)
>         Subsystem: Rivet Networks Alder Lake-S PCH CNVi WiFi [1a56:1692]
>         Flags: fast devsel, IRQ 18, IOMMU group 6
>         Memory at 604c124000 (64-bit, non-prefetchable) [size=16K]
>         Capabilities: [c8] Power Management version 3
>         Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
>         Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
>         Capabilities: [80] MSI-X: Enable- Count=16 Masked-
>         Capabilities: [100] Latency Tolerance Reporting
>         Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0
> Len=014 <?>
>         Kernel modules: iwlwifi
>
> Granted that I am no expert on this, but I know enough to get myself
> into trouble, which is what I proceeded to do.  I believe (but could
> well be mistaken) that what is needed is a configuration line for that
> PCI ID in iwlwifi/pcie/drv.c, something like this one:
>
> IWL_DEV_INFO(0x7F70, 0x1692, iwlax411_2ax_cfg_so_gf4_a0, iwl_ax411_killer_1690i_name),
>
> My attempt was to duplicate then change the new line from 7F70 to 7AF0,
> but that was also not successful, with such errors as (clipping because
> it's rather long):
>
> [...]
> [    3.960164] iwlwifi 0000:00:14.3: Microcode SW error detected.
> Restarting 0x0.
> [...]
> [    3.960551] iwlwifi 0000:00:14.3: Starting mac, retry will be
> triggered anyway
> [    3.960594] iwlwifi 0000:00:14.3: FW error in SYNC CMD ADD_STA
> [    3.960600] Call Trace:
> [    3.960602]  <TASK>
> [    3.960602]  dump_stack_lvl+0x36/0x50
> [    3.960606]  iwl_trans_txq_send_hcmd+0x338/0x450 [iwlwifi]
> [...]
>
> It does produce an interface but it is unusable.
>
> I assume (but I am definitely out of my depth at this point) that it is
> due to the wrong firmware being referenced by that line of code (i.e.
> it's a different firmware for 7F70 vs. 7AF0) but I also don't know what
> the correct one is, thus I'm asking here.  If I'm totally on the wrong
> track, I'm fine with that too, I just want to get it working.
>
> Thanks!
>
>
Hi Aaron,

Could you please provide the whole dmesg log? Actually, the best is to open
a bugzilla ticket (as described in [1]) and attach the log there. It's strange
that the card identifies as CNVi (meaning it's SoC - integrated), but killer
NICs should be discrete. Maybe you could also attach to the bugzilla ticket
a photo of the NIC itself with all the IDs etc that it has on it?

[1] https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging

2023-04-11 15:01:15

by Aaron Dewell

[permalink] [raw]
Subject: Re: ax204/Intel NUC13 i9


On Apr 11 2023, at 3:07 am, Greenman, Gregory
<[email protected]> wrote:

> On Mon, 2023-04-10 at 15:45 -0600, Aaron Dewell wrote:
>> To summarize up to now and reboot the discussion:
>>
>> I have installed firmware-git. This is the file that was extracted
>> into /lib/firmware:
>> -rw-r--r--  1 root  root 429469981 Apr  2 10:47 linux-firmware-iwlwifi-fw-2023-03-30.tar.gz
>>
>> The card is not successfully initialized by the stock (6.1.20) kernel:
>> [    2.284183] Intel(R) Wireless WiFi driver for Linux
>> [    2.284221] cryptd: max_cpu_qlen set to 1000
>> [    2.284223] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
>> [    2.286133] iwlwifi: No config found for PCI dev 7af0/1692,
>> rev=0x430, rfid=0x3010d000
>> [    2.286155] iwlwifi: probe of 0000:00:14.3 failed with error -22
>>
>> The distribution is Debian Bookworm (testing), which has kernel:
>> Linux shrub 6.1.0-7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-1
>> (2023-03-19) x86_64 GNU/Linux
>>
>> The card identifies as 0x7AF0, 0x1692:
>> 00:14.3 Network controller [0280]: Intel Corporation Alder Lake-S PCH
>> CNVi WiFi [8086:7af0] (rev 11)
>>         Subsystem: Rivet Networks Alder Lake-S PCH CNVi WiFi [1a56:1692]
>>         Flags: fast devsel, IRQ 18, IOMMU group 6
>>         Memory at 604c124000 (64-bit, non-prefetchable) [size=16K]
>>         Capabilities: [c8] Power Management version 3
>>         Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
>>         Capabilities: [40] Express Root Complex Integrated Endpoint,
>> MSI 00
>>         Capabilities: [80] MSI-X: Enable- Count=16 Masked-
>>         Capabilities: [100] Latency Tolerance Reporting
>>         Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0
>> Len=014 <?>
>>         Kernel modules: iwlwifi
>>
>> Granted that I am no expert on this, but I know enough to get myself
>> into trouble, which is what I proceeded to do.  I believe (but could
>> well be mistaken) that what is needed is a configuration line for that
>> PCI ID in iwlwifi/pcie/drv.c, something like this one:
>>
>> IWL_DEV_INFO(0x7F70, 0x1692, iwlax411_2ax_cfg_so_gf4_a0, iwl_ax411_killer_1690i_name),
>>
>> My attempt was to duplicate then change the new line from 7F70 to 7AF0,
>> but that was also not successful, with such errors as (clipping because
>> it's rather long):
>>
>> [...]
>> [    3.960164] iwlwifi 0000:00:14.3: Microcode SW error detected.
>> Restarting 0x0.
>> [...]
>> [    3.960551] iwlwifi 0000:00:14.3: Starting mac, retry will be
>> triggered anyway
>> [    3.960594] iwlwifi 0000:00:14.3: FW error in SYNC CMD ADD_STA
>> [    3.960600] Call Trace:
>> [    3.960602]  <TASK>
>> [    3.960602]  dump_stack_lvl+0x36/0x50
>> [    3.960606]  iwl_trans_txq_send_hcmd+0x338/0x450 [iwlwifi]
>> [...]
>>
>> It does produce an interface but it is unusable.
>>
>> I assume (but I am definitely out of my depth at this point) that it is
>> due to the wrong firmware being referenced by that line of code (i.e.
>> it's a different firmware for 7F70 vs. 7AF0) but I also don't know what
>> the correct one is, thus I'm asking here.  If I'm totally on the wrong
>> track, I'm fine with that too, I just want to get it working.
>>
>> Thanks!
>>
>>
> Hi Aaron,
>
> Could you please provide the whole dmesg log? Actually, the best is to open
> a bugzilla ticket (as described in [1]) and attach the log there. It's strange
> that the card identifies as CNVi (meaning it's SoC - integrated), but killer
> NICs should be discrete. Maybe you could also attach to the bugzilla ticket
> a photo of the NIC itself with all the IDs etc that it has on it?
>
> [1] https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging

Hi Gregory,

I'll open the ticket. Thanks!

It is definitely not discrete, it's integrated onto the board.

Aaron