Bug 2263192 - 5 GHz Wi-Fi connection problems with 6.7 kernels
Summary: 5 GHz Wi-Fi connection problems with 6.7 kernels
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 39
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-02-07 13:40 UTC by Bruce Cowan
Modified: 2024-11-27 22:52 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-11-27 22:52:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Journal from a faulty boot (125.36 KB, text/plain)
2024-02-07 13:41 UTC, Bruce Cowan
no flags Details

Description Bruce Cowan 2024-02-07 13:40:56 UTC
1. Please describe the problem:

With both kernel versions 6.7.3-200 and 6.7.4-200, I've experienced problems with the wireless card. It initially connects, then disconnects and carries on retrying every 30 seconds or so.

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

The 6.7 series, I tested both versions which are available.

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 :

6.6.14-200 works.

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

Boot as normal.
Note that Wi-Fi connects.
Try to use as normal.
Wi-Fi disconnects and carries on asking for passwords and so on.

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

Haven't tested this.

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.

Reproducible: Always

Comment 1 Bruce Cowan 2024-02-07 13:41:39 UTC
Created attachment 2015644 [details]
Journal from a faulty boot

Comment 2 Bruce Cowan 2024-02-07 16:37:21 UTC
Upstream report from someone else: https://lore.kernel.org/all/a2ccb118-6e80-47f2-af51-c4490c0d7dc1@leemhuis.info/T/

Comment 3 Bruce Cowan 2024-02-08 13:34:43 UTC
I've found the same issue with a different driver. Forcing them to connect to the 2.4 GHz networks (I have an extender) makes it work. Attempting to connect to the 5 GHz network fails.

Comment 4 Aoife Moloney 2024-11-13 11:59:42 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Aoife Moloney 2024-11-27 22:52:57 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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