FS#64739 - [linux-firmware] ath10k QCA9377 random disconnects on latest linux-firmware

Attached to Project: Arch Linux
Opened by Jasperro (Jasperro) - Thursday, 05 December 2019, 08:59 GMT
Last edited by Toolybird (Toolybird) - Monday, 29 May 2023, 04:47 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Laurent Carlier (lordheavy)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
I'm having an issue where my laptop with QCA9377 wifi chip randomly disconnects mostly on enterprise (mschapv2) wifi with the latest linux-firmware (issue seems to have existed for a long time). This issue can be fixed by downloading an older (arbitrarily chosen 2017-06-22) version of the driver (https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ath10k/QCA9377/hw1.0/firmware-5.bin?id=dd5fba3a56bbb4c4a72576faa19f8bd45fed7ef6) and replacing /usr/lib/firmware/ath10k/QCA9377/hw1.0/firmware-6.bin and /usr/lib/firmware/ath10k/QCA9377/hw1.0/firmware-5.bin with the downloaded firmware file. I found this information here: https://www.reddit.com/r/voidlinux/comments/bh2vdf/help_wireless_connection_keeps_dropping_after/elqabpe?utm_source=share&utm_medium=web2x, a lot of people seem to be having the same issue.

Is it possible to use the older file instead of the new file in the package, or does this have to be fixed upstream?

I attached the working firmware file I'm using now.

Additional info:
* package version(s) 20191022.2b016af-3
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
Connect to mschapv2 enterprise wifi with the newest arch linux firmware file, and see connection drop in 10-30 seconds.
When connecting using the provided firmware file, the connection doesn't drop.
This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 29 May 2023, 04:47 GMT
Reason for closing:  Upstream
Additional comments about closing:  Clearly an upstream problem. Plus it's old and stale. If still an issue, please report upstream.
Comment by [-_-] (Adcock) - Wednesday, 08 January 2020, 14:06 GMT

Loading...