1 |
On Mon, 18 Dec 2017 19:15:04 +0000 |
2 |
Hunter Jozwiak <hunter.t.joz@×××××.com> wrote: |
3 |
>On 12/18/17, Mick <michaelkintzios@×××××.com> wrote: |
4 |
>> On Monday, 18 December 2017 05:11:20 GMT Hunter Jozwiak wrote: |
5 |
>>> Hmm. I have kernel 4.14.7 and linux-firmware 20171206. I tried version |
6 |
>>> 999999999 as well, but that didn't help matters, either. Nor did |
7 |
>>> compiling the firmware into the kernel; either 4.14 is too old, or it |
8 |
>>> is too new. |
9 |
>> |
10 |
>> I'd think they are both too new? |
11 |
>> |
12 |
>>> I tried copying the firmware my live iso was using, but |
13 |
>>> that didn't help either. |
14 |
>> |
15 |
>> If the live iso works, start with using the same kernel release and linux- |
16 |
>> firmware version, to see if this works as expected on your installation. |
17 |
>> Then |
18 |
>> update kernel sources and firmware to the latest stable and see if this |
19 |
>> works |
20 |
>> too. |
21 |
>> |
22 |
>> From there on you can move into ~arch to find the version at which things |
23 |
>> break. |
24 |
>> -- |
25 |
>> Regards, |
26 |
>> Mick |
27 |
>Okay, here are the dmesg messages: |
28 |
>https://paste.pound-python.org/show/nrNfBAEPfh9W7ZIeItJC/ |
29 |
>The present kernel configuration, as of yesterday evening: |
30 |
>https://paste.pound-python.org/show/NmNB8nzLuEjmsz74kRVE/ |
31 |
>Make and model of the offending card: Qualcomm 6174 revision 20. |
32 |
>Not exactly what the -2 error means, but I will try as Mick suggested |
33 |
>and work my way forwards to see what I can get working. |
34 |
> |
35 |
|
36 |
Hi, |
37 |
|
38 |
I was a little bit confused from your earlier mentioned |
39 |
|
40 |
/lib/firmware/ath10k/QCABLEFAGD/HW3.0 |
41 |
|
42 |
I wonder where this firmware come from. I cannot find it, neither with |
43 |
the identifier ‘QCABLEFAGD’ nor an upper cased ‘HW3.0’ directory in |
44 |
[1][2][3][4]. |
45 |
|
46 |
Your log tells an other story now. As far as I can tell: |
47 |
|
48 |
“Direct firmware load for […] failed with error -2” |
49 |
|
50 |
comes from _request_firmware and fw_get_filesystem_firmware functions in |
51 |
file [5]. The symbolic error name ENOENT, see `man 3 errno`, means |
52 |
something like ‘No such element’ or ‘No such file or directory’. |
53 |
|
54 |
Even CONFIG_EXTRA_FIRMWARE_DIR defaults to ‘/lib/firmware’, there should |
55 |
be whether an entry ‘# CONFIG_EXTRA_FIRMWARE_DIR is not set’ or |
56 |
something like ‘CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"’ in your |
57 |
config. Its unclear to me why it is not there. |
58 |
|
59 |
If you want to build into the kernel again, check |
60 |
‘/lib/firmware/ath10k/QCA6174/hw2.1/firmware-6.bin’ exists and set: |
61 |
|
62 |
CONFIG_FIRMWARE_IN_KERNEL=y |
63 |
CONFIG_EXTRA_FIRMWARE="ath10k/QCA6174/hw2.1/firmware-6.bin" |
64 |
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" |
65 |
|
66 |
Hope that helps. |
67 |
|
68 |
|
69 |
[1] <https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/ath10k> |
70 |
[2] <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/drivers/net/wireless/ath/ath10k/hw.h?h=v4.14.7> |
71 |
[3] <https://github.com/kvalo/ath10k-firmware> |
72 |
[4] <https://wireless.wiki.kernel.org/en/users/Drivers/ath10k/firmware> |
73 |
[5] <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/drivers/base/firmware_class.c?h=v4.14.7#n386> |
74 |
|
75 |
|
76 |
|
77 |
-- |
78 |
Regards, |
79 |
floyd |