ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Sven Eckelmann <sven.eckelmann@openmesh.com>
Cc: Anil Duggirala <anilduggirala@fastmail.fm>,
	ath10k@lists.infradead.org, debian-kernel@lists.debian.org
Subject: Re: missing firmware in debian 9
Date: Wed, 28 Nov 2018 16:03:42 +0200	[thread overview]
Message-ID: <87h8g170zl.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <6892054.LxBMB1ZCDT@bentobox> (Sven Eckelmann's message of "Mon,  26 Nov 2018 09:48:17 +0100")

Sven Eckelmann <sven.eckelmann@openmesh.com> writes:

> On Freitag, 16. November 2018 08:38:51 CET Anil Duggirala wrote:
>> hello,
>> I am getting this message at boot.
>> 
>> [ 10.678576] ath10k_pci 0000:03:00.0: firmware: failed to load
>> ath10k/pre-cal-pci-0000:03:00.0.bin (-2)
>> [ 10.678631] ath10k_pci 0000:03:00.0: Direct firmware load for
>> ath10k/pre-cal-pci-0000:03:00.0.bin failed with error -2
>> [ 10.678655] ath10k_pci 0000:03:00.0: firmware: failed to load
>> ath10k/cal-pci-0000:03:00.0.bin (-2)
>> [ 10.678699] ath10k_pci 0000:03:00.0: Direct firmware load for
>> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
>> [ 10.681081] ath10k_pci 0000:03:00.0: firmware: failed to load
>> ath10k/QCA6174/hw3.0/firmware-5.bin (-2)
>> [ 10.681127] ath10k_pci 0000:03:00.0: Direct firmware load for
>> ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
>> [ 10.681131] ath10k_pci 0000:03:00.0: could not fetch firmware file
>> 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
>> 
>> I have installed the firmware-atheros package from backports in
>> Debian 9, I had installed the package from the main repository
>> before but I was also getting this message. I have also installed
>> the firmware-linux-free package.
>
> Where should Debian take it when QCA is not providing a firmware-5.bin? Kalle 
> Valo's repo [1] contains different firmware-6.bin (which your ath10k version 
> doesn't seem to support yet) and firmware-4.bin. And Debian ships both - I 
> think the ones which were in linux-firmware [2] at the time of the release.
>
> I don't have a QCA6174 hw3.0 but I would guess that ath10k loaded the
> firmware-4.bin after it failed to load the firmware-5.bin.

That's what I'm guessing as well. And these warnings should be visible
anymore with this commit:

c8e028026387 ath10k: use firmware_request_nowarn() to load firmware

https://git.kernel.org/linus/c8e028026387

It was introduced in v4.18 so once you upgrade the kernel to v4.18 or
later you should not see the warnings anymore.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2018-11-28 14:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 13:38 missing firmware in debian 9 Anil Duggirala
2018-11-26  8:48 ` Sven Eckelmann
2018-11-28 14:03   ` Kalle Valo [this message]
2018-11-28 14:17     ` Anil Duggirala
2018-11-28 14:25     ` Anil Duggirala
2018-11-28 15:17       ` Kalle Valo
2018-11-28 16:47         ` Anil Duggirala

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=87h8g170zl.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=anilduggirala@fastmail.fm \
    --cc=ath10k@lists.infradead.org \
    --cc=debian-kernel@lists.debian.org \
    --cc=sven.eckelmann@openmesh.com \
    /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