From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 69436139083 for ; Mon, 18 Dec 2017 21:52:10 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 095D7E10F1; Mon, 18 Dec 2017 21:52:04 +0000 (UTC) Received: from mx2.mailbox.org (mx2.mailbox.org [80.241.60.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 96821E1005 for ; Mon, 18 Dec 2017 21:52:03 +0000 (UTC) Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.mailbox.org (Postfix) with ESMTPS id 39B6A4CAD8 for ; Mon, 18 Dec 2017 22:52:01 +0100 (CET) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp1.mailbox.org ([80.241.60.240]) by spamfilter01.heinlein-hosting.de (spamfilter01.heinlein-hosting.de [80.241.56.115]) (amavisd-new, port 10030) with ESMTP id Sf9kmkLtnD8S for ; Mon, 18 Dec 2017 22:51:59 +0100 (CET) Date: Mon, 18 Dec 2017 22:51:59 +0100 From: Floyd Anderson To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Loading a Firmware Module By hand? Message-ID: <20171218215158.mpi2ytjcuoas2k2c@31c0.net> Mail-Followup-To: gentoo-user@lists.gentoo.org References: <20171217092840.GA1759@starlite> <3798554.ljX4XG9pTd@dell_xps> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Archives-Salt: f3cb7f59-bb5f-436c-9921-8d22c5f7b4fb X-Archives-Hash: 5d771251ea1342aad7b46be40c337dd6 On Mon, 18 Dec 2017 19:15:04 +0000 Hunter Jozwiak wrote: >On 12/18/17, Mick wrote: >> On Monday, 18 December 2017 05:11:20 GMT Hunter Jozwiak wrote: >>> 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'd think they are both too new? >> >>> I tried copying the firmware my live iso was using, but >>> that didn't help either. >> >> If the live iso works, start with using the same kernel release and linux- >> firmware version, to see if this works as expected on your installation. >> Then >> update kernel sources and firmware to the latest stable and see if this >> works >> too. >> >> From there on you can move into ~arch to find the version at which things >> break. >> -- >> Regards, >> Mick >Okay, here are the dmesg messages: >https://paste.pound-python.org/show/nrNfBAEPfh9W7ZIeItJC/ >The present kernel configuration, as of yesterday evening: >https://paste.pound-python.org/show/NmNB8nzLuEjmsz74kRVE/ >Make and model of the offending card: Qualcomm 6174 revision 20. >Not exactly what the -2 error means, but I will try as Mick suggested >and work my way forwards to see what I can get working. > Hi, I was a little bit confused from your earlier mentioned /lib/firmware/ath10k/QCABLEFAGD/HW3.0 I wonder where this firmware come from. I cannot find it, neither with the identifier ‘QCABLEFAGD’ nor an upper cased ‘HW3.0’ directory in [1][2][3][4]. Your log tells an other story now. As far as I can tell: “Direct firmware load for […] failed with error -2” comes from _request_firmware and fw_get_filesystem_firmware functions in file [5]. The symbolic error name ENOENT, see `man 3 errno`, means something like ‘No such element’ or ‘No such file or directory’. Even CONFIG_EXTRA_FIRMWARE_DIR defaults to ‘/lib/firmware’, there should be whether an entry ‘# CONFIG_EXTRA_FIRMWARE_DIR is not set’ or something like ‘CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"’ in your config. Its unclear to me why it is not there. If you want to build into the kernel again, check ‘/lib/firmware/ath10k/QCA6174/hw2.1/firmware-6.bin’ exists and set: CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="ath10k/QCA6174/hw2.1/firmware-6.bin" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" Hope that helps. [1] [2] [3] [4] [5] -- Regards, floyd