Bug 1403504 - could not fetch firmware file ath10k/QCA6174/hw3.0/firmware-5.bin
Summary: could not fetch firmware file ath10k/QCA6174/hw3.0/firmware-5.bin
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 25
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-10 19:17 UTC by Eric Remigino
Modified: 2019-01-09 12:54 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-11 15:45:57 UTC
Type: Bug


Attachments (Terms of Use)
camera shot of failing to load firmware-5.bin (953.47 KB, image/jpeg)
2016-12-10 19:17 UTC, Eric Remigino
no flags Details

Description Eric Remigino 2016-12-10 19:17:18 UTC
Created attachment 1230370 [details]
camera shot of failing to load firmware-5.bin

Description of problem:

Not all tests pass [OK] when computer boots.

When computer boots, i receive a message saying

[4.982195] ath10k_pci 0000:01:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2

My wireless so far works 100% just fine.  In fact I believe this error might be the cause of a simple typo, since I checked my /lib/firmware/ath10k/hw3.0/ folder, and there is a firmware-4.bin file there.  Is my wireless adapter falling back on using the firmware-4.bin when it doesn't find firmware-5.bin?

My wireless adapter is the Killer 1535 802.11ac on the new Razer Blade Stealth 2016

Version-Release number of selected component (if applicable):

Kernel 4.8.12

How reproducible:

Hardware dependent, but if you boot with the new kernel and have the same wireless adapter as me, you most likely are getting this message.


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

All [OK] on boot

Additional info:

Comment 1 Laura Abbott 2016-12-11 15:45:57 UTC
If your wireless is working 100% this is almost certainly not a bug. Often the drivers in the kernel will try multiple firmware versions and then fall back as you suggested. If you have concerns about the latest firmware being present, please check the linux-firmware tree at https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git,


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