On Mon, 18 Dec 2017 05:11:20 +0000
Hunter Jozwiak <[email protected]> wrote:
On 12/17/17, Andrey Utkin <[email protected]> wrote:
On Sun, Dec 17, 2017 at 12:34:14AM -0500, Hunter Jozwiak wrote:
Hi,
I have an ath10k_pci device that I'm trying to get hooked to the
Internet, but I'm having some strange issues. It is trying to load the
2.1 firmware, but I don't think that is the proper firmware for the
interface to have; I think it ought to be loading the 3.0 module, but
am not quite sure on that either, or how I could go about injecting
that into the modprobe; I wasn't able to pinpoint the firmware blob
the ISO was using, so that wasn't much of a pointer in the right
direction either. I see that the 3.0 blob does exist in
/lib/firmware/ath10k/QCABLEFAGD/HW3.0, but there are many bin files,
I have little to no idea about your actual case... But could it be that
you have a recent linux-firmware package (which provides /lib/firmware/
files) and not recent enough kernel? I think kernel is what decides
which firmware file to load.
!!! rearranged top-posting !!!
Hmm. I have kernel 4.14.7 and linux-firmware 20171206. I tried version
999999999 as well, but that didn't help matters, either. Nor did
compiling the firmware into the kernel; either 4.14 is too old, or it
is too new. I tried copying the firmware my live iso was using, but
that didn't help either.
I think you are a little bit too vague in your given info. If you don’t
show your firmware related kernel settings (those lines posted by Mick
earlier) nor what dmesg said about the firmware loading success of your
specified config, people tends to think you know what you are doing and
therefore may eliminate any errors based on syntactical mistakes or
similar from their thoughts.
For instance, you wrote “It is trying to load the 2.1 firmware” but
because trying != loaded successfully, nobody knows if 2.1 works or has
been failed (and why), so you have a need to try the 3.0 blob.
As Mick pointed out, look what is in your dmesg log and communicate that
(not only your own interpretation of it). Maybe there’s another module
configured that also supports and loads the 2.1 blob so it must be
blacklisted [1] or not built at all. Also the firmware must be available
on boot and module load, so a probably used initramfs must include it as
long as it is not built into the kernel.
[1] <https://wiki.gentoo.org/wiki/Kernel_Modules#Blacklist>
--
Regards,
floyd
