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 72AF7139083 for ; Sun, 17 Dec 2017 09:18:23 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BDDE2E0DD0; Sun, 17 Dec 2017 09:18:17 +0000 (UTC) Received: from mail-wr0-x243.google.com (mail-wr0-x243.google.com [IPv6:2a00:1450:400c:c0c::243]) (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 43D3EE0CAE for ; Sun, 17 Dec 2017 09:18:17 +0000 (UTC) Received: by mail-wr0-x243.google.com with SMTP id q9so11499228wre.7 for ; Sun, 17 Dec 2017 01:18:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:reply-to:subject:date:message-id:in-reply-to:references :mime-version; bh=1cYyZBsptveWZ621Du8baQCjlLDEvW7cH/uPF7nRi0k=; b=VhKLaqTO+RxAInmMTwh4MsXkTShN0q+Yfp5Kb5dp1efzRYLSWVvSmas9DPkiqbOWNQ ZT0Mps8zcilYflb/JgR2VigFwNxoW1biNhtdFm4LnbjIejuZTXH1cr0piPaRGM76j0SQ CFeHNiS8xud8gc/5XlbKdNn4HuvYggzngUuac92p5960yXMyjLlQFzHkXNVJ1Uby8KiR V5BxUDPhYvGng0yH03y5RZOMeQXwgehGHFPhcxcGHJQzMHOU+PB9ZjQp61nSZP5ndZ2w nJnn9DFtrhI6Zte4V89Y5/JwKY3nX2ZYBJjaX8VH0miWGsBQMBnMecZqR72jO4LyPurD MhTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:reply-to:subject:date:message-id :in-reply-to:references:mime-version; bh=1cYyZBsptveWZ621Du8baQCjlLDEvW7cH/uPF7nRi0k=; b=jNxiSj4F0Kgrn0R2TbVyVoXY3c5qnC2LopE6F+t6C7d6PpxmuyW5X7kOngD5U4cwEh e1lj2AbKvjf3rEoZd5PVJ7e9qfLG5IAzaMtnipCMItdReU3ZUAn+Re3lyY8WM1KCnkw+ vBottogl7CoMlF5t3kvllrApOxqZY9YTeqDraleaL1/9/sL6yoKDZ8RfA2e2D8yxT6FL YJ7yyhkj04f2mHf/1fW73BT9pPl+JK7L5EqIkup7lAdkI0r1IonCPGxxx7Y49K8sYJhS HkUmY48yYCOZpAsthxg6UI9b+HmKR7bB8W0n+Uf4COMa+0i9qUMqakV8b9RbTHvNEavy 9r/w== X-Gm-Message-State: AKGB3mKCa0CD4xFXNzlLJwfoB6y4NzohytHVcXdneQKzGBuEhPeXjZXP z/BHUWhE/6bVJCGj6dng3cnTHA== X-Google-Smtp-Source: ACJfBoua1hzWLJMBcg6qn/BS5SCgRpRfwjo8QFeEiWD2YVfs6//9nmyAwElRR8s0q3js0X/dx6+A9g== X-Received: by 10.223.171.79 with SMTP id r15mr3451942wrc.219.1513502295769; Sun, 17 Dec 2017 01:18:15 -0800 (PST) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by smtp.gmail.com with ESMTPSA id f18sm6539021wrg.66.2017.12.17.01.18.14 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 17 Dec 2017 01:18:15 -0800 (PST) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Loading a Firmware Module By hand? Date: Sun, 17 Dec 2017 09:18:18 +0000 Message-ID: <1651601.XtACczL8qe@dell_xps> In-Reply-To: References: 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: multipart/signed; boundary="nextPart1630373.1OKpnjzO5n"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-Archives-Salt: 9f5317e2-1435-4deb-a158-0893d0c7a13a X-Archives-Hash: 1c2ecd159a9b02c0dd919120ef9aeff9 --nextPart1630373.1OKpnjzO5n Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" On Sunday, 17 December 2017 05:34:14 GMT Hunter Jozwiak wrote: > Hi, > > I have an ath10k_pci device that I'm trying to get hooked to the > Internet, but I'm having some strange issues. It is trying to load the > 2.1 firmware, but I don't think that is the proper firmware for the > interface to have; I think it ought to be loading the 3.0 module, but > am not quite sure on that either, or how I could go about injecting > that into the modprobe; Usually the kernel will probe the device and load the appropriate firmware the device needs. The output of dmesg will show if loading the firmware was successful, or complain if different firmware was needed and not found in your "/lib/firmware/" or whatever you have set up in your kernel as the directory for firmware blobs. > I wasn't able to pinpoint the firmware blob > the ISO was using, so that wasn't much of a pointer in the right > direction either. I see that the 3.0 blob does exist in > /lib/firmware/ath10k/QCABLEFAGD/HW3.0, but there are many bin files, > so choosing the right one is a bit tricky by the looks of things. > Earlier today, I had read the Gentoo wiki on the topic, which > suggested that I compile the blob into the kernel itself, but the link > they gave only described the advantages and disadvantages of modular > kernels and how to drop kmod if you're using a moduleless kernel. Does > anybody have any insight on this matter? > > Thanks, > > Hunter Have a look in: # Generic Driver Options and then: CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="Put your firmware files in here, space separated" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/" I don't have your NIC to know the specifics, but the above ought to work. -- Regards, Mick --nextPart1630373.1OKpnjzO5n Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEt7MNaGaS6HvTUrEz6WnU8jC95dcFAlo2NloACgkQ6WnU8jC9 5deQ1Q//UnrO3p4y+5Hxf6Rfo6wanKUKBzFHuCNRJ/rNPoOGWpYsgKPv0N8v8pXC u8xPg68yMpgYZi+os2k+SRohqLXNHSQ0Oc030qQAjHt773P42RNMsSDfTNxwo8yg S6MR0p6ZUJfHuE79n37oFhGpM4941kKUFZxvxXT2V07zKztSBlDAYARLsNGmw2/w XP0SXSNjVxsQFND9D5pSHrBBiElKy0hEnApUYh1Zp1EFNETB+hI/w0lzMpsx3NFN 1Jyf33oPdR+AWCmOSkqvKhaK+43pnnYpXAMKFonf5DT/7e6b9Bi8n8NgJKdftXyr ayICD1ECMVhPYW4dvoEBFMFQToo7dZCRW0QTEye9D7GRjxh6oEy9uguKWdaDPUXQ HhKVhhRR1yJ4jWDNe6oLOzSdw5OgKjQeNtFjeO2MPDIrNfLmUfJC1z6K2LjPYjZO rmnNO1J1ePWucXCYlZrm9C23fm7vxnUKzzjjMZhbVhi4j0z5GnWKXRt4fS7EgsT8 WeQSivXTpTBrD0ScZaTxZ9eIuSXjy0doScU0QjEgg79ioDg6k6FqbKMDgatrIOw1 V30h40n8Z7ZPEkCy1DPo0NlMSPGXo0JMhizOyAn/VQ1sf1kZW7xr1lJNrXyaZl59 0mwu51SxJvQQ28HBNfGpU4lYr7/OD8wmdj2K+of4nyL815iSgtA= =T/IG -----END PGP SIGNATURE----- --nextPart1630373.1OKpnjzO5n--