Bug 245304 - iwm(4): Add support for Intel 9462 (iwm) wireless devices
Summary: iwm(4): Add support for Intel 9462 (iwm) wireless devices
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-wireless (Nobody)
URL:
Keywords: feature, needs-qa
Depends on:
Blocks:
 
Reported: 2020-04-03 00:50 UTC by Blake
Modified: 2021-06-19 15:31 UTC (History)
8 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Blake 2020-04-03 00:50:56 UTC
The current IWM driver won't support Intel Corporation Wireless-AC 9262.
Comment 1 Blake 2020-04-03 00:51:53 UTC
This is the default wireless card of the NUC10i7 and probably other NUC10's as well.
Comment 2 Mark Johnston freebsd_committer 2020-04-03 13:30:22 UTC
Can you show the pciconf -lv entry for this device?
Comment 3 Blake 2020-04-08 02:45:15 UTC
none3@pci0:0:20:3:      class=0x028000 rev=0x00 hdr=0x00 vendor=0x8086 device=0x02f0 subvendor=0x8086 subdevice=0x0074
    vendor     = 'Intel Corporation'
    device     = 'Wireless-AC 9462'
    class      = network
Comment 4 Adriaan de Groot freebsd_committer 2020-04-11 21:06:51 UTC
In Linux, shows up from lspci as

```
00:14.3 Network controller: Intel Corporation Wireless-AC 9462
        Subsystem: Intel Corporation Device 0034
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at 6025104000 (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 driver in use: iwlwifi
        Kernel modules: iwlwifi
```

with dmesg showing

```
[    5.627409] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-52.ucode failed with error -2
[    5.627551] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-51.ucode failed with error -2
[    5.627564] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-50.ucode failed with error -2
[    5.627575] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-49.ucode failed with error -2
[    5.666325] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
[    5.666487] iwlwifi 0000:00:14.3: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm
[    6.006106] iwlwifi 0000:00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz, REV=0x354
[    6.164232] iwlwifi 0000:00:14.3: base HW address: 0c:dd:24:39:77:7c
[    6.827915] iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0
[    7.725416] iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
[    7.892586] iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
[   37.470805] iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
[   37.674667] iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
[   41.130784] iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
```

The device is *physically* labelled (on the m2 card in my laptop) as 9560. Adding the 0x02f0 device ID to the `iwm` driver -- and a config struct,

```
?       sys/contrib/dev/iwm/iwm-9462-48.fw.uu
M       sys/dev/iwm/if_iwm.c
?       sys/dev/iwm/if_iwm_9462.c
M       sys/dev/iwm/if_iwm_config.h
M       sys/modules/iwm/Makefile
M       sys/modules/iwmfw/Makefile
?       sys/modules/iwmfw/iwm9462fw
```

got me quickly to iwm trying to load some firmware and failing: `unknown firmware section 55`. The firmware I was trying to load was iwlwifi-QuZ-a0-jf-b0-48.ucode -- based on that **that** file exists in my Linux installation on the laptop, and the errors in dmesg.
Comment 5 Adriaan de Groot freebsd_committer 2020-04-11 21:18:48 UTC
- Shouldn't the bug title be 9462, rather than 9262?
- I went looking at the Intel firmware page, and the one listed for 9462 (for Linux kernels 4.14+ uuencodes to something different from what's in the FreeBSD -current tree)
Comment 6 Blake 2020-04-12 02:08:00 UTC
(In reply to Adriaan de Groot from comment #5)
You are correct.  Sorry about that.
Comment 7 Felipe N. Oliva 2020-12-24 17:38:40 UTC
Same problem here with Intel 9462.

Tested with 12.2R and latest snapshot 13-CURRENT today.

Any news?

Thanks.
Comment 8 Mark Johnston freebsd_committer 2020-12-27 03:33:49 UTC
(In reply to Felipe N. Oliva from comment #7)
No news at the moment.  These devices require either a substantial update of the iwm driver or an entirely new one.
Comment 9 Andreas Bjørnestad 2021-02-01 14:00:14 UTC
(In reply to Blake from comment #1)

I have a NUC10i7 and mine has AX201, not 9262.
Comment 10 Ed 2021-06-05 16:21:31 UTC
Hi all! Will there be support for Intel 9462? I want to try FreeBSD, but my Wifi does not work :(
Comment 11 Adriaan de Groot freebsd_committer 2021-06-11 14:18:48 UTC
it's probably worth figuring out which devices this PR applies to exactly. Blake says

none3@pci0:0:20:3:      class=0x028000 rev=0x00 hdr=0x00 vendor=0x8086 device=0x02f0 subvendor=0x8086 subdevice=0x0074
    vendor     = 'Intel Corporation'
    device     = 'Wireless-AC 9462'
    class      = network

at the start of this PR, and I have a **different** device:subdevice (0x02f0:0x0034) and a different descriptive string (Comet Lake PCH-LP CNVi WiFi). Details in https://bsd-hardware.info/?probe=80a9ba918e . Then there's 0x06f0:0x0074 (Comet Lake PCH CNVi WiFi) with a different device, from https://bsd-hardware.info/?probe=2be8cf963c . Sounds similar, even if the device number is different.

I should add that my comment #4 is no longer true: Linux now names this device as a Comet-Lake-whatchamacallit.