Bug 1928574 - no Wi-Fi on Dell XPS 13 9310 with Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)]
Summary: no Wi-Fi on Dell XPS 13 9310 with Qualcomm QCA6390 Wireless Network Adapter [...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-14 22:49 UTC by Peter F. Patel-Schneider
Modified: 2021-03-27 12:44 UTC (History)
19 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-03-27 12:44:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
kernel log (126.76 KB, text/plain)
2021-02-14 22:49 UTC, Peter F. Patel-Schneider
no flags Details

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.


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