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