From: Mick <michaelkintzios@gmail.com>
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 [thread overview]
Message-ID: <1651601.XtACczL8qe@dell_xps> (raw)
In-Reply-To: <CAJ1hvUESBMd7-qpvGZwfax5SLPzSn3eegjXdhtJ1+0_vOREZqA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1787 bytes --]
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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-17 9:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-17 5:34 [gentoo-user] Loading a Firmware Module By hand? Hunter Jozwiak
2017-12-17 9:18 ` Mick [this message]
2017-12-17 9:28 ` Andrey Utkin
2017-12-18 5:11 ` Hunter Jozwiak
2017-12-18 7:33 ` Floyd Anderson
2017-12-18 17:09 ` Mick
2017-12-18 19:15 ` Hunter Jozwiak
2017-12-18 21:51 ` Floyd Anderson
2017-12-18 21:59 ` Hunter Jozwiak
2017-12-18 23:33 ` Adam Carter
2017-12-18 22:22 ` Floyd Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1651601.XtACczL8qe@dell_xps \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox