Bug 1928574

Summary: no Wi-Fi on Dell XPS 13 9310 with Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)]
Product: [Fedora] Fedora Reporter: Peter F. Patel-Schneider <pfpschneider>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, itamar, jarodwilson, jeremy, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-27 12:44:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
kernel log none

Description Peter F. Patel-Schneider 2021-02-14 22:49:08 UTC 
Created attachment 1757013 [details]
kernel log

Created attachment 1757013 [details]
kernel log

1. Please describe the problem:

On my new DELL XPS 13 9310 the Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] Wi-Fi chip is not working.


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

Kernel version 5.10.14-200.fc33.x86_64


3. Did it work previously in Fedora? 

Almost certainly not


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Power up the laptop - no wireless.


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``:

Installing the rawhide kernel needed --nogpg

In rawhide (kernel 5.12.0-0.rc0!) the wireless comes up fine. and comes back after suspend!
So if Fedora 34 is going to have 5.12, then the problem is solved.   I haven't tested Fedora 34 alpha.

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.