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 B7EC1138806 for ; Mon, 18 Dec 2017 21:59:21 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0E946E1129; Mon, 18 Dec 2017 21:59:10 +0000 (UTC) Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (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 A3476E10FA for ; Mon, 18 Dec 2017 21:59:04 +0000 (UTC) Received: by mail-vk0-x22a.google.com with SMTP id w75so9220002vkd.7 for ; Mon, 18 Dec 2017 13:59:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=iTgHqhzc2TQFDTgBl9ywNBepIeNabcIAkxmZOlM4pvw=; b=fclZ/IreUzOaepOpI0YZrW6+mKqVL+UNUQUJMSbE5imwIZpp7FZG8fcRFOysPmDq2h TBc72462C/HMp6AMofY+GdwgFbLkwhZ3Wjv2E72Hxe7W+gi2d8yxkW2vvSUJsfOSkMSV GlkUUN23TLeT0AdC94sUp6HuZnlwdiRIZhgBLz4OR569Br+uIvfshVPrBEvm98bnlQ+5 WSvmGnMRnaCOsiCCQedw5UB1cKtYyHP3OT8yBmsBJU0kKmA02pNzR+DOb30g7N5CqbRw FuDTItvb1kvTgvhcJC70UKnwWaERsnavAx3PtABWvRv0rrSIA3ylYBuArnLVvSAUVuAD B2Ig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=iTgHqhzc2TQFDTgBl9ywNBepIeNabcIAkxmZOlM4pvw=; b=s4doqpu6mPIUV98wEshdZHI8MUhLIms5gLPQdK6kQkEkiXx8Coy8PuHNrH0hWRwVVS 8Atf2KcW4strvVcxV6i5cIAFHCJFcE5r9op9BqVKJTKUXIYMRy95TbySgQ02d4lqNsai oOnbdVwXmE6EhujVm5OsleIyaSbdjqGYaQDcpBHkNftLuQYxrZlgXQ56GCfFByPufbPF /gtDUl6GbWtjWVT2zpXHzMT0mUxybqWNu/wzEp84QpJXJhwLQT4XI5XTjySISqFdBGTm IAVHLn6EvkqW8Rg4CbC2v/b74dWDiF+9xdCbEB6wOdmHsioc9pSnlUZ0ORjZPgBiLyeU 5/PA== X-Gm-Message-State: AKGB3mIYuZRK+DGV05NiSKOvFswhiwFdhUG8aiBIkFxxC7aM6HMYOvmN MXLEdP3ecZrirfM/9fK80Zpz+A7QgCcWMUAdZYY= X-Google-Smtp-Source: ACJfBotOQSxWaIVZY/MUOXs5myf6opY6OVkXu4ehK/M2I0vVCw5tNz/mDMax+qkdF/b9wtMSztHtdqvbPP8BHyOm9CU= X-Received: by 10.31.198.1 with SMTP id w1mr1264961vkf.101.1513634343687; Mon, 18 Dec 2017 13:59:03 -0800 (PST) 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 Received: by 10.159.40.225 with HTTP; Mon, 18 Dec 2017 13:59:02 -0800 (PST) In-Reply-To: <20171218215158.mpi2ytjcuoas2k2c@31c0.net> References: <20171217092840.GA1759@starlite> <3798554.ljX4XG9pTd@dell_xps> <20171218215158.mpi2ytjcuoas2k2c@31c0.net> From: Hunter Jozwiak Date: Mon, 18 Dec 2017 16:59:02 -0500 Message-ID: Subject: Re: [gentoo-user] Loading a Firmware Module By hand? To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Archives-Salt: b1055c58-9850-474c-8969-66820d8cd724 X-Archives-Hash: ac59370d31d38cf1b9c56745db96a56a On 12/18/17, Floyd Anderson wrote: > 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 =E2=80=98QCABLEFAGD=E2=80=99 nor an upper cased =E2=80=98H= W3.0=E2=80=99 directory in > [1][2][3][4]. > > Your log tells an other story now. As far as I can tell: > > =E2=80=9CDirect firmware load for [=E2=80=A6] failed with error -2=E2= =80=9D > > 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 =E2=80=98No such element=E2=80=99 or =E2=80=98No such file= or directory=E2=80=99. > > Even CONFIG_EXTRA_FIRMWARE_DIR defaults to =E2=80=98/lib/firmware=E2=80= =99, there should > be whether an entry =E2=80=98# CONFIG_EXTRA_FIRMWARE_DIR is not set=E2=80= =99 or > something like =E2=80=98CONFIG_EXTRA_FIRMWARE_DIR=3D"/lib/firmware"=E2=80= =99 in your > config. Its unclear to me why it is not there. > > If you want to build into the kernel again, check > =E2=80=98/lib/firmware/ath10k/QCA6174/hw2.1/firmware-6.bin=E2=80=99 exist= s and set: > > CONFIG_FIRMWARE_IN_KERNEL=3Dy > CONFIG_EXTRA_FIRMWARE=3D"ath10k/QCA6174/hw2.1/firmware-6.bin" > CONFIG_EXTRA_FIRMWARE_DIR=3D"/lib/firmware" > > Hope that helps. > > > [1] > > [2] > > [3] > [4] > [5] > > > > > -- > Regards, > floyd > > > That particular firmware does not exist. I am trying to figure how far back I need to rollback the kernel. Sabayon's live ISO is using 4.13.0, but that is no longer in the tree. Not sure if I need to go back to the 4.12 ebuilds, or if 4.13.5 will suit my needs; perhaps there is a bit of source code that I can look at to see what is being used for the firmware?