Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2047878 - [Lenovo] Support for Qualcomm NFA765 Wifi (kernel)
Summary: [Lenovo] Support for Qualcomm NFA765 Wifi (kernel)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 35
Hardware: x86_64
OS: All
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-28 19:04 UTC by Mark Pearson
Modified: 2022-02-12 01:18 UTC (History)
20 users (show)

Fixed In Version: kernel-5.16.8-100.fc34 kernel-5.16.8-200.fc35
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2048666 (view as bug list)
Environment:
Last Closed: 2022-02-12 01:15:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
hw 2.1 patch (deleted)
2022-02-07 07:25 UTC, Íñigo Huguet
no flags Details | Diff

Description Mark Pearson 2022-01-28 19:04:00 UTC
1. Please describe the problem:
The Qualcomm NFA765 is used on a number of 2021 AMD platforms and will be used on some 2022 platforms.
Support for this device has landed upstream (both kernel driver and FW) so I'd like to get supported added to Fedora.

I've tested a build from os-build from kernel-ark and all that is needed is to install the firmware files to make it work. I don't believe the driver support is present in the F35 branch yet.

I think the upstream commit (if needed) is this:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fc95d10ac41d75c14a81afcc8722333d8b2cf80f
but I haven't proven that is the only commit needed - there may be others.

On the FW side of things I've tested the updates here:
https://github.com/kvalo/ath11k-firmware/tree/master/WCN6855/hw2.0

I needed:
 - board-2.bin and regdb.bin from WCN6855/hw2.0
 - amss.bin and m3.bin from WCN6855/hw2.0/1.1/WLAN.HSP.1.1-02892.1-QCAHSPSWPL_V1_V2_SILICONZ_LITE-1 (though the 03003 version is good too)
to be placed in /lib/firmware/ath11k/WCN6855/hw2.0

Unfortunately I don't see these in the linux-firmware repository yet

2. What is the Version-Release number of the kernel:
5.16

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
No

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Yes - and happy to help with testing for this one.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Yes - though I believe the kernel is good, it's just missing the FW. I'm hoping doing the enablement makes things better

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
I'll add these if you need them - but they're not very exciting and I'll have to go extract them from the DUT

Comment 1 Íñigo Huguet 2022-01-31 15:03:56 UTC
Hi, not sure what kernel version are you working on now for F35, but we needed this commit for RHEL. It's a post v5.16 commit, included in stable version 5.16.3:
63550aa49351 ath11k: add string type to search board data in board-2.bin for WCN6855

Also, to support the new hw revision 2.1, this commit is needed, not yet in stable branch:
d1147a316b53 ath11k: add support for WCN6855 hw2.1

Additionally, for hw2.1 support, a symlink in firmware folder needs to be done, as explained in the previous commit's message.

Comment 2 Justin M. Forbes 2022-01-31 16:43:35 UTC
The kernel patches are queued for the 5.16 rebases and will show up in 5.16.5 and later builds. You need to open a separate bug against linux-firmware to get the the firmwares in.

Comment 3 Mark Pearson 2022-01-31 17:03:30 UTC
Thanks Justin - will do on the FW

Do you have a timeline on the 5.16.5 release likely date please?

Mark

Comment 4 Mark Pearson 2022-01-31 17:11:27 UTC
Note for myself: FW tracked thru https://bugzilla.redhat.com/show_bug.cgi?id=2048666

Comment 5 Justin M. Forbes 2022-02-04 22:51:01 UTC
So 5.16.5 is released. Unfortunately I had to back out the patch for hw revision 2.1.  While the patch applied cleanly, it doesn't actually compile with 5.16 because it incorporates other changes which are not in 5.16. It is expected that 5.16.6 will release this weekend, and I won't have time to get the backport cleaned up before then, but I will work on it early next week and expect to get the hw revision 2.1 patch in 5.16.7.  It is too early to tell for sure, but patterns would say next Wednesday or Thursday will be 5.16.7.

Comment 6 Mark Pearson 2022-02-05 13:09:13 UTC
Thanks for the update Justin. As we're blocked by the firmware not being in the linux-firmware repository it's not a problem if it's taking a bit longer - I think that's going to be the gating item.
Mark

Comment 7 Íñigo Huguet 2022-02-07 07:25:07 UTC
Created attachment 1859516 [details]
hw 2.1 patch

This should be the correct patch to apply on top of 5.16.7, according to what we've done on RHEL. Note: untested with Fedora kernel, but it should work.

Comment 8 Justin M. Forbes 2022-02-07 17:21:43 UTC
(In reply to Íñigo Huguet from comment #7)
> Created attachment 1859516 [details]
> hw 2.1 patch
> 
> This should be the correct patch to apply on top of 5.16.7, according to
> what we've done on RHEL. Note: untested with Fedora kernel, but it should
> work.

It builds, though no hardware to test. It is queued for 5.16.8, which is out for review and should ship Wednesday.

Comment 9 Mark Pearson 2022-02-07 17:54:26 UTC
I can help with testing if that helps.

Comment 10 Íñigo Huguet 2022-02-08 07:19:14 UTC
I'm happy to help with testing, as well, and also with other wireless stuff if we have it in our lab.

Comment 11 Fedora Update System 2022-02-09 03:07:43 UTC
FEDORA-2022-33ec204d7d has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-33ec204d7d

Comment 12 Fedora Update System 2022-02-09 03:07:47 UTC
FEDORA-2022-7a25525651 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-7a25525651

Comment 13 Fedora Update System 2022-02-10 02:43:09 UTC
FEDORA-2022-7a25525651 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-7a25525651`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-7a25525651

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 14 Fedora Update System 2022-02-10 02:56:39 UTC
FEDORA-2022-33ec204d7d has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-33ec204d7d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-33ec204d7d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 15 Fedora Update System 2022-02-12 01:15:38 UTC
FEDORA-2022-7a25525651 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2022-02-12 01:18:54 UTC
FEDORA-2022-33ec204d7d has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.