unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Bavier <ericbavier@openmailbox.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Quilro Ordonez <quiliro@riseup.net>,
	quiliro@fsfla.org, 23409@debbugs.gnu.org
Subject: bug#23409: unable to load free firmware
Date: Mon, 2 May 2016 08:55:07 -0500	[thread overview]
Message-ID: <20160502085507.31da4d6f@openmailbox.org> (raw)
In-Reply-To: <87shy1apax.fsf@gnu.org>

On Sun, 01 May 2016 15:19:34 +0200
ludo@gnu.org (Ludovic Courtès) wrote:

> Quilro Ordonez <quiliro@riseup.net> skribis:
> 
> > I am trying to lo use Broadcom wireless device on GuixSD. It is
> > confirmed to work with free drivers and free firmware. It works
> > correctly in Trisquel too.
> >
> > dmesg gives the following messages. I have included only the relevant
> > parts:  
> 
> [...]
> 
> > [   20.591158] b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not
> > found
> > [   21.313688] b43-phy0 ERROR: /*(DEBLOBBED)*/  
> 
> “DEBLOBBED” would suggest that Linux-libre’s deblobbing script viewed it
> as an opaque binary blob and thus patched it, which may be an issue
> here, no?

Does deblobbing happen at runtime too?  I thought it was only during
build time.

> 
> I assume you used the firmware packages that Leo copied.  Could you get
> its author to submit it?  :-)

That would be me :)  But I don't have the hardware to test it out on,
and qemu doesn't offer emulation of the broadcomm cards.

`~Eric

  reply	other threads:[~2016-05-02 16:17 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 [this message]
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
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=20160502085507.31da4d6f@openmailbox.org \
    --to=ericbavier@openmailbox.org \
    --cc=23409@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=quiliro@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).