| 1 |
Hmm. I have kernel 4.14.7 and linux-firmware 20171206. I tried version |
| 2 |
999999999 as well, but that didn't help matters, either. Nor did |
| 3 |
compiling the firmware into the kernel; either 4.14 is too old, or it |
| 4 |
is too new. I tried copying the firmware my live iso was using, but |
| 5 |
that didn't help either. |
| 6 |
|
| 7 |
On 12/17/17, Andrey Utkin <andrey_utkin@g.o> wrote: |
| 8 |
> On Sun, Dec 17, 2017 at 12:34:14AM -0500, Hunter Jozwiak wrote: |
| 9 |
>> Hi, |
| 10 |
>> |
| 11 |
>> I have an ath10k_pci device that I'm trying to get hooked to the |
| 12 |
>> Internet, but I'm having some strange issues. It is trying to load the |
| 13 |
>> 2.1 firmware, but I don't think that is the proper firmware for the |
| 14 |
>> interface to have; I think it ought to be loading the 3.0 module, but |
| 15 |
>> am not quite sure on that either, or how I could go about injecting |
| 16 |
>> that into the modprobe; I wasn't able to pinpoint the firmware blob |
| 17 |
>> the ISO was using, so that wasn't much of a pointer in the right |
| 18 |
>> direction either. I see that the 3.0 blob does exist in |
| 19 |
>> /lib/firmware/ath10k/QCABLEFAGD/HW3.0, but there are many bin files, |
| 20 |
> |
| 21 |
> I have little to no idea about your actual case... But could it be that |
| 22 |
> you have a recent linux-firmware package (which provides /lib/firmware/ |
| 23 |
> files) and not recent enough kernel? I think kernel is what decides |
| 24 |
> which firmware file to load. |
| 25 |
> |
Archives