From: Kalle Valo <kvalo@codeaurora.org>
To: Nicola Mori <nicolamori@aol.com>
Cc: ath10k@lists.infradead.org, Wen Gong <wgong@codeaurora.org>
Subject: Re: Killer WiFi card keeps disconnecting due to latest firmware
Date: Thu, 16 Apr 2020 15:34:54 +0300 [thread overview]
Message-ID: <87ftd3r4lt.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <b07a7ea1-7ab2-8ce3-95d7-6726e7708749@aol.com> (Nicola Mori's message of "Tue, 14 Apr 2020 09:26:16 +0200")
Nicola Mori <nicolamori@aol.com> writes:
> Hi, I have an issue with the WiFi card in my laptop, that keeps
> disconnecting from the network in a strange way: randomly every 1-2
> hours I can't access web pages or even ping the gateway, but existing
> connections (like existing ssh sessions or Zoom videoconferences)
> continue to work. The only solution is to restart the network
> connection.
>
> The fix for me has been to downgrade the firmware by removing
> /usr/lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin so that
> /usr/lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin is used; with
> this, I have no issues.
These firmware filenames tell nothing to me (-6 and -4 are just
interface version numbers), I need the exact firmware versions of which
works and which doesn't. 'dmesg | grep ath10k' is the best way to get
them.
Also adding Wen to the loop.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2020-04-16 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b07a7ea1-7ab2-8ce3-95d7-6726e7708749.ref@aol.com>
2020-04-14 7:26 ` Killer WiFi card keeps disconnecting due to latest firmware Nicola Mori
2020-04-16 12:34 ` Kalle Valo [this message]
2020-04-22 7:14 ` Kalle Valo
2020-04-23 9:14 ` Wen Gong
[not found] ` <cd1469bf-452c-5819-b5c2-b1ff8c48638f@aol.com>
2020-04-26 9:14 ` Nicola Mori
2020-05-05 8:46 Elia Geretto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftd3r4lt.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=nicolamori@aol.com \
--cc=wgong@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).