unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: 23409@debbugs.gnu.org
Cc: Quilro Ordonez <quiliro@riseup.net>, lxo@fsfla.org
Subject: bug#23409: unable to load free firmware
Date: Thu, 05 May 2016 11:42:22 +0300	[thread overview]
Message-ID: <8737pwuc9d.fsf@gmail.com> (raw)
In-Reply-To: <0f0377ea297e219eab214635838e6838@riseup.net> (Quilro Ordonez's message of "Wed, 04 May 2016 18:13:00 -0500")

Quilro Ordonez (2016-05-05 02:13 +0300) wrote:

> Same errors in dmesg.

If you mean after system reconfiguring, then it is expected, because
nothing has changed, you just moved package definitions from you system
config to another file, so that "guix build" and other commands could
see these packages.

Or do you mean after modifying
"/sys/module/firmware_class/parameters/path" and "insmod"-ing that
firmware?

Here is an excerpt of Ludo's message.  Please report after doing these
steps.

Ludovic Courtès (2016-05-03 11:01 +0300) wrote:

> Quilíro: firmware files are searched for in the directory specified in
> the /sys/module/firmware_class/parameters/path pseudo-file (see the (gnu
> build activation) module.)
>
> 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?
>
> Also, can you show the output of:
>
>   find $(guix build b43-firmware-whatever)/lib/firmware
>
> ?
>
> It should contain “b43-open/ucode5.fw”.

-- 
Alex

  reply	other threads:[~2016-05-05  8:43 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
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 [this message]
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=8737pwuc9d.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=23409@debbugs.gnu.org \
    --cc=lxo@fsfla.org \
    --cc=quiliro@riseup.net \
    /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).