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