From: Quilro Ordonez <quiliro@riseup.net>
To: 23409@debbugs.gnu.org
Cc: lxo@fsfla.org
Subject: bug#23409: unable to load free firmware
Date: Tue, 03 May 2016 16:17:46 -0500 [thread overview]
Message-ID: <609d0dda92cead243d99546befa113ca@riseup.net> (raw)
In-Reply-To: <87eg9ij2fz.fsf@gnu.org>
El 2016-05-03 15:45, ludo@gnu.org escribió:
> Quilro Ordonez <quiliro@riseup.net> skribis:
>
>> El 2016-05-03 03:01, ludo@gnu.org escribió:
>
> [...]
>
>>> Could you try, as root, something like (use the right package and
>>> module
>>> name below):
>>>
>>> echo -n $(guix build b43-firmware-whatever)/lib/firmware \
>>> > /sys/module/firmware_class/parameters/path
>>> insmod b43-module-whatever-its-called
>>> dmesg | tail
>>>
>>> … and report back?
>>
>> These are the three options I tested:
>>
>> echo -n $(guix build b43-firmware-whatever)/lib/firmware >
>> /sys/module/firmware_class/parameters/path
>> echo -n $(guix build b43-open)/lib/firmware >
>> /sys/module/firmware_class/parameters/path
>> echo -n $(guix build b43-tools)/lib/firmware >
>> /sys/module/firmware_class/parameters/path
>> echo -n $(guix build openfwwf)/lib/firmware >
>> /sys/module/firmware_class/parameters/path
>> echo -n $(guix build openfwwf-firmware)/lib/firmware >
>> /sys/module/firmware_class/parameters/path
>>
>> The results for all those in the order of:
>>
>> guix build: error: openfwwf-firmware: unknown package
>
> That’s because “openfwwf-firmware” is not the right package name, or is
> not found. Perhaps you need to adjust GUIX_PACKAGE_PATH so that the
> recipe for “openfwwf-firmware” is found?
I suppose the path can be found with:
ls /gnu/store/*/ucode5.fw
/gnu/store/l7k3psmq08ad40swi1kf9as4bjizlz7i-openfwwf-firmware-5.2/ucode5.fw
/gnu/store/yjycspnbxyafys84hn4f1phjy37fai20-openfwwf-firmware-5.2/ucode5.fw
> sudo bash
> export GUIX_PACKAGE_PATH=/path/to/recipes
> echo -n $(guix build openfwwf-firmware)/lib/firmware > \
> /sys/module/firmware_class/parameters/path
So the path would be:
export GUIX_PACKAGE_PATH=/openfwwf-firmware-5.2
Is that correct?
next prev parent reply other threads:[~2016-05-03 21:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 21:06 bug#23409: unable to load free firmware Quilro Ordonez
2016-04-30 22:43 ` Leo Famulari
2016-05-01 13:19 ` Ludovic Courtès
2016-05-02 13:55 ` Eric Bavier
2016-05-03 8:01 ` Ludovic Courtès
2016-05-03 20:10 ` Quilro Ordonez
2016-05-03 20:45 ` Ludovic Courtès
2016-05-03 21:17 ` Quilro Ordonez [this message]
2016-05-03 21:21 ` Quilro Ordonez
2016-05-04 9:10 ` Alex Kost
2016-05-04 18:30 ` Quilro Ordonez
2016-05-04 21:33 ` Alex Kost
2016-05-04 23:08 ` Quilro Ordonez
2016-05-04 23:13 ` Quilro Ordonez
2016-05-05 8:42 ` Alex Kost
2016-05-11 19:01 ` Quilro Ordonez
[not found] ` <87oa8bzjqg.fsf@gmail.com>
2016-05-12 16:11 ` Quilro Ordonez
2016-05-13 13:25 ` Ludovic Courtès
2016-05-13 21:15 ` Quilro Ordonez
2016-05-14 16:17 ` Alex Kost
2016-11-02 22:19 ` Ludovic Courtès
2017-01-11 22:29 ` Ludovic Courtès
2016-11-04 0:43 ` Quiliro Ordonez
2016-11-04 0:46 ` Quiliro Ordonez
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=609d0dda92cead243d99546befa113ca@riseup.net \
--to=quiliro@riseup.net \
--cc=23409@debbugs.gnu.org \
--cc=lxo@fsfla.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).