unable to load free firmware

DoneSubmitted by Quilro Ordonez.
Details
5 participants
  • Alex Kost
  • Eric Bavier
  • Leo Famulari
  • Ludovic Courtès
  • Quilro Ordonez
Owner
unassigned
Severity
normal
Q
Q
Quilro Ordonez wrote on 30 Apr 2016 23:06
(address . bug-guix@gnu.org)
8c7981c22c93720a9dbd5f63c279c44b@riseup.net
Hello mashi (Mashi is the kichwa word for friend, partner, associate, camerade. Kichwa is the language spoken in the Andes mountain region along all the West of South America).
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.400251] b43-phy0: Broadcom 4311 WLAN found (core revision 10)[ 20.432041] b43-phy0: Found PHY: Analog 4, Type 2 (G), Revision 8[ 20.432058] b43-phy0: Found Radio: Manuf 0x17F, ID 0x2050, Revision 2, Version 0[ 20.444116] Broadcom 43xx driver loaded [ Features: PNL ][ 20.444306] ssb0:0: Missing Free firmware (non-Free firmware loading is disabled)[ 20.444308] Unable to load firmware[ 20.591119] b43 ssb0:0: Direct firmware load for /*(DEBLOBBED)*/ failed with error -2[ 20.591135] b43 ssb0:0: Direct firmware load for b43-open/ucode5.fw failed with error -2[ 20.591154] b43 ssb0:0: Direct firmware load for b43-open/ucode5.fw failed with error -2[ 20.591158] b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found[ 21.313688] b43-phy0 ERROR: /*(DEBLOBBED)*/
'lspci -vmmnn -d 14e4:' shows:Slot: 03:00.0Class: Network controller [0280]Vendor: Broadcom Corporation [14e4]Device: BCM4311 802.11b/g WLAN [4311]SVendor: Hewlett-Packard Company [103c]SDevice: BCM4311 802.11b/g Wireless LAN Controller [1363]Rev: 01
'lspci -nn -d 14e4:' shows03:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g WLAN [14e4:4311] (rev 01)
h-node.com establishes rev 01 of this card works with free software inhttps://h-node.org/wifi/view/en/2/Broadcom-Corporation-BCM4311-802-11b-g-WLAN--rev-02-
Please suggest what I should try. Thank you very much.
Quiliro
L
L
Leo Famulari wrote on 1 May 2016 00:43
(address . quiliro@fsfla.org)(address . 23409@debbugs.gnu.org)
20160430224316.GA9483@jasmine
On Sat, Apr 30, 2016 at 04:06:58PM -0500, Quilro Ordonez wrote:
Toggle quote (4 lines)> 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.
I believe that these package definitions for b43-tools andopenfwwf-firmware, copied from http://termbin.com/i02e,are what arebeing used:
(define-public b43-tools (let ((commit "8dce53297966b31b6c70a7a03c2433978dd9f288")) (package (name "b43-tools") (version (string-append "20160406." (string-take commit 8))) (source (origin (method git-fetch) (uri (git-reference (url "http://git.bues.ch/git/b43-tools.git") (commit commit))) (sha256 (base32 "08k7sdr9jagm43r2zv4h03j86klhkblpk73p12444a3vzg1gy1lv")))) (build-system gnu-build-system) (native-inputs `(("flex" ,flex) ("bison" ,bison))) (arguments `(#:modules ((srfi srfi-1) (guix build gnu-build-system) (guix build utils)) #:tests? #f ;no tests #:phases (let ((subdirs '("assembler" "disassembler"))) ;TODO: fwcutter (modify-phases %standard-phases (delete 'configure) (add-before 'build 'patch-/bin/true (lambda _ (substitute* (find-files "." "Makefile") (("/bin/true") ":")) #t)) (replace 'build (lambda _ (every (lambda (dir) (zero? (system* "make" "-C" dir "CC=gcc"))) subdirs))) (replace 'install (lambda* (#:key outputs #:allow-other-keys) (let ((out (assoc-ref outputs "out"))) (mkdir-p (string-append out "/bin")) (every (lambda (dir) (zero? (system* "make" "-C" dir (string-append "PREFIX=" out) "install"))) subdirs)))))))) (home-page "") (synopsis "") (description "") (license gpl2))))
(define-public openfwwf-firmware (package (name "openfwwf-firmware") (version "5.2") (source (origin (method url-fetch) (uri (string-append "http://netweb.ing.unibs.it/~openfwwf/firmware/" "openfwwf-" version ".tar.gz")) (sha256 (base32 ;; /gnu/store/ag7rf0kmb1wrnhwjfi3fgr1jcv1vg021-openfwwf-5.2.tar.gz "1p60gdi7w88s7qw82d3g9v7mk887mhvidf4l5q5hh09j10h37q4x")))) (build-system gnu-build-system) (native-inputs `(("b43-tools" ,b43-tools))) (arguments `(#:make-flags (list (string-append "PREFIX=" (assoc-ref %outputs "out") "/b43-open")) #:tests? #f ;no tests #:phases (modify-phases %standard-phases (delete 'configure)))) (home-page "http://netweb.ing.unibs.it/~openfwwf/") (synopsis "") (description "") (license gpl2)))
L
L
Ludovic Courtès wrote on 1 May 2016 15:19
(name . Quilro Ordonez)(address . quiliro@riseup.net)
87shy1apax.fsf@gnu.org
Quilro Ordonez <quiliro@riseup.net> skribis:
Toggle quote (7 lines)> 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:
[...]
Toggle quote (4 lines)> [ 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 itas an opaque binary blob and thus patched it, which may be an issuehere, no?
I assume you used the firmware packages that Leo copied. Could you getits author to submit it? :-)
What’s your GuixSD OS config like? You must make sure to list thefirmware packages in the ‘firmware’ field, as noted at:
https://www.gnu.org/software/guix/manual/html_node/operating_002dsystem-Reference.html#index-firmware
Is this part OK?
Thanks,Ludo’.
E
E
Eric Bavier wrote on 2 May 2016 15:55
(name . Ludovic Courtès)(address . ludo@gnu.org)
20160502085507.31da4d6f@openmailbox.org
On Sun, 01 May 2016 15:19:34 +0200ludo@gnu.org (Ludovic Courtès) wrote:
Toggle quote (19 lines)> 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 duringbuild time.
Toggle quote (4 lines)> > 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
L
L
Ludovic Courtès wrote on 3 May 2016 10:01
(name . Eric Bavier)(address . ericbavier@openmailbox.org)
871t5jfu3d.fsf@gnu.org
Eric Bavier <ericbavier@openmailbox.org> skribis:
Toggle quote (25 lines)> 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.
Right, it’s at at build time, but the “deblobbing script” leaves those“DEBLOBBED” messages in places where it has removed firmware loadingcapabilities.
It may be worth checking with the Linux-libre team what happens in thisparticular case—i.e., whether this code is erroneously deblobbed, orsomething else.
Quilíro: firmware files are searched for in the directory specified inthe /sys/module/firmware_class/parameters/path pseudo-file (see the (gnubuild activation) module.)
Could you try, as root, something like (use the right package and modulename 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”.
Toggle quote (5 lines)>> I assume you used the firmware packages that Leo copied. Could you get>> its author to submit it? :-)>> That would be me :)
Ah ha! I suspected it but wasn’t sure. :-)
Toggle quote (3 lines)> But I don't have the hardware to test it out on, and qemu doesn't> offer emulation of the broadcomm cards.
Good point. Let’s test it with Quilíro.
Thanks!
Ludo’.
L
L
Ludovic Courtès wrote on 3 May 2016 22:06
control message for bug #23409
(address . control@debbugs.gnu.org)
878tzqlxd8.fsf@gnu.org
tags 23409 moreinfo
Q
Q
Quilro Ordonez wrote on 3 May 2016 22:10
Re: bug#23409: unable to load free firmware
(address . ludo@gnu.org)
ef92f4c5f05c03392bcc23dfae364c82@riseup.net
El 2016-05-03 03:01, ludo@gnu.org escribió:
Toggle quote (52 lines)> Eric Bavier <ericbavier@openmailbox.org> skribis:> >> 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.> > Right, it’s at at build time, but the “deblobbing script” leaves those> “DEBLOBBED” messages in places where it has removed firmware loading> capabilities.> > It may be worth checking with the Linux-libre team what happens in this> particular case—i.e., whether this code is erroneously deblobbed, or> something else.> > 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?
These are the three options I tested:
echo -n $(guix build b43-firmware-whatever)/lib/firmware > /sys/module/firmware_class/parameters/pathecho -n $(guix build b43-open)/lib/firmware > /sys/module/firmware_class/parameters/pathecho -n $(guix build b43-tools)/lib/firmware > /sys/module/firmware_class/parameters/pathecho -n $(guix build openfwwf)/lib/firmware > /sys/module/firmware_class/parameters/pathecho -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 packagebash: /sys/module/firmware_class/parameters/path: Permiso denegado
(This is the result of the last test.)
Toggle quote (9 lines)> Also, can you show the output of:> > find $(guix build b43-firmware-whatever)/lib/firmware> > ?> > It should contain “b43-open/ucode5.fw”.

quiliro@komputilo ~$ find $(guix build openfwwf-firmware)/lib/firmwareguix build: error: openfwwf-firmware: unknown packagefind: ‘/lib/firmware’: No existe el fichero o el directorio
Toggle quote (17 lines)>>> I assume you used the firmware packages that Leo copied. Could you >>> get>>> its author to submit it? :-)>> >> That would be me :)> > Ah ha! I suspected it but wasn’t sure. :-)> >> But I don't have the hardware to test it out on, and qemu doesn't>> offer emulation of the broadcomm cards.> > Good point. Let’s test it with Quilíro.> > Thanks!> > Ludo’.
This is my config.scmhttp://termbin.com/4qpx
And this is the output of the update with that config:
quiliro@komputilo ~$ sudo guix system reconfigure raw.scmPassword:substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%substitute: updating list of substitutes from 'https://hydra.gnu.org'... 100.0%The following derivation will be built: /gnu/store/2cj80qdh89vd5zjnwg3m6cx0bhf97lac-grub.cfg.drv/gnu/store/xv88rlnb9q1gk9vp7z5ih2dwf6rjd0kd-system/gnu/store/sb9g34hmckfnnjpr471llqmyg4hckflm-grub.cfg/gnu/store/myrc5cinlhpj2yilhzv5y0szz2ax2i6z-grub-2.00activating system...setting up setuid programs in '/run/setuid-programs'...populating /etc from /gnu/store/msm5mb78xdfc49jp1400jwz9wfnmydrs-etc...usermod: sin cambiosusermod: sin cambiosusermod: sin cambiosusermod: sin cambiosusermod: sin cambiosusermod: sin cambiosusermod: sin cambiosusermod: sin cambiosusermod: sin cambiosmaking '/gnu/store/xv88rlnb9q1gk9vp7z5ih2dwf6rjd0kd-system' the current system...Installation finished. No error reported.
L
L
Ludovic Courtès wrote on 3 May 2016 22:45
(name . Quilro Ordonez)(address . quiliro@riseup.net)
87eg9ij2fz.fsf@gnu.org
Quilro Ordonez <quiliro@riseup.net> skribis:
Toggle quote (2 lines)> El 2016-05-03 03:01, ludo@gnu.org escribió:
[...]
Toggle quote (28 lines)>> 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 isnot found. Perhaps you need to adjust GUIX_PACKAGE_PATH so that therecipe for “openfwwf-firmware” is found?
Toggle quote (2 lines)> bash: /sys/module/firmware_class/parameters/path: Permiso denegado
That’s because this is not performed as root. This needs to be done ina “root” shell, so:
sudo bash export GUIX_PACKAGE_PATH=/path/to/recipes echo -n $(guix build openfwwf-firmware)/lib/firmware > \ /sys/module/firmware_class/parameters/path
Could you try again?
(Please paste the exact commands and output in your reply.)
Thanks,Ludo’.
Q
Q
Quilro Ordonez wrote on 3 May 2016 23:17
(address . 23409@debbugs.gnu.org)(address . lxo@fsfla.org)
609d0dda92cead243d99546befa113ca@riseup.net
El 2016-05-03 15:45, ludo@gnu.org escribió:
Toggle quote (38 lines)> 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
Toggle quote (5 lines)> 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?
Q
Q
Quilro Ordonez wrote on 3 May 2016 23:21
(address . 23409@debbugs.gnu.org)(address . lxo@fsfla.org)
35d2e4a2bdc12bc75b84965e714beaa0@riseup.net
root@komputilo /home/quiliro# export GUIX_PACKAGE_PATH=/openfwwf-firmware-5.2root@komputilo /home/quiliro# echo -n $(guix build openfwwf-firmware)/lib/firmware > \
Toggle quote (1 lines)> /sys/module/firmware_class/parameters/path
guix build: warning: cannot access `/openfwwf-firmware-5.2': No existe el fichero o el directorioguix build: error: openfwwf-firmware: unknown packageroot@komputilo /home/quiliro# export GUIX_PACKAGE_PATH=/gnu/store/yjycspnbxyafys84hn4f1phjy37fai20-openfwwf-firmware-5.2root@komputilo /home/quiliro# echo -n $(guix build openfwwf-firmware)/lib/firmware > /sys/module/firmware_class/parameters/pathguix build: error: openfwwf-firmware: unknown package
A
A
Alex Kost wrote on 4 May 2016 11:10
(name . Quilro Ordonez)(address . quiliro@riseup.net)
877ffagpdy.fsf@gmail.com
Quilro Ordonez wrote:
Toggle quote (5 lines)> So the path would be:> export GUIX_PACKAGE_PATH=/openfwwf-firmware-5.2
> Is that correct?
No.
Toggle quote (15 lines)> root@komputilo /home/quiliro# export> GUIX_PACKAGE_PATH=/openfwwf-firmware-5.2> root@komputilo /home/quiliro# echo -n $(guix build> openfwwf-firmware)/lib/firmware > \>> /sys/module/firmware_class/parameters/path> guix build: warning: cannot access `/openfwwf-firmware-5.2': No existe> el fichero o el directorio> guix build: error: openfwwf-firmware: unknown package> root@komputilo /home/quiliro# export> GUIX_PACKAGE_PATH=/gnu/store/yjycspnbxyafys84hn4f1phjy37fai20-openfwwf-firmware-5.2> root@komputilo /home/quiliro# echo -n $(guix build> openfwwf-firmware)/lib/firmware >> /sys/module/firmware_class/parameters/path> guix build: error: openfwwf-firmware: unknown package
This happens because you put your packages in your system config file,so "guix build" command cannot find them. As Ludovic pointed, you needto move these packages into a separate file (or files) and setGUIX_PACKAGE_PATH accordingly. For example, you can create"/any/directory/you/want/my-guix-packages.scm" file with the followingcontents:
(define-module (my-guix-packages) #:use-module (guix packages) #:use-module (guix build-system gnu) #:use-module (guix download) #:use-module (guix git-download) #:use-module (guix licenses) #:use-module (gnu packages flex) #:use-module (gnu packages bison)) (define-public b43-tools (let ((commit "8dce53297966b31b6c70a7a03c2433978dd9f288")) (package (name "b43-tools") (version (string-append "20160406." (string-take commit 8))) (source (origin (method git-fetch) (uri (git-reference (url "http://git.bues.ch/git/b43-tools.git") (commit commit))) (sha256 (base32 "08k7sdr9jagm43r2zv4h03j86klhkblpk73p12444a3vzg1gy1lv")))) (build-system gnu-build-system) (native-inputs `(("flex" ,flex) ("bison" ,bison))) (arguments `(#:modules ((srfi srfi-1) (guix build gnu-build-system) (guix build utils)) #:tests? #f ;no tests #:phases (let ((subdirs '("assembler" "disassembler"))) ;TODO: fwcutter (modify-phases %standard-phases (delete 'configure) (add-before 'build 'patch-/bin/true (lambda _ (substitute* (find-files "." "Makefile") (("/bin/true") ":")) #t)) (replace 'build (lambda _ (every (lambda (dir) (zero? (system* "make" "-C" dir "CC=gcc"))) subdirs))) (replace 'install (lambda* (#:key outputs #:allow-other-keys) (let ((out (assoc-ref outputs "out"))) (mkdir-p (string-append out "/bin")) (every (lambda (dir) (zero? (system* "make" "-C" dir (string-append "PREFIX=" out) "install"))) subdirs)))))))) (home-page "") (synopsis "") (description "") (license gpl2)))) (define-public openfwwf-firmware (package (name "openfwwf-firmware") (version "5.2") (source (origin (method url-fetch) (uri (string-append "http://netweb.ing.unibs.it/~openfwwf/firmware/" "openfwwf-" version ".tar.gz")) (sha256 (base32 ;; /gnu/store/ag7rf0kmb1wrnhwjfi3fgr1jcv1vg021-openfwwf-5.2.tar.gz "1p60gdi7w88s7qw82d3g9v7mk887mhvidf4l5q5hh09j10h37q4x")))) (build-system gnu-build-system) (native-inputs `(("b43-tools" ,b43-tools))) (arguments `(#:make-flags (list (string-append "PREFIX=" (assoc-ref %outputs "out") "/b43-open")) #:tests? #f ;no tests #:phases (modify-phases %standard-phases (delete 'configure)))) (home-page "http://netweb.ing.unibs.it/~openfwwf/") (synopsis "") (description "") (license gpl2)))
After that the following command should build the package:
$ GUIX_PACKAGE_PATH=/any/directory/you/want guix build openfwwf-firmware
Also if you add this directory to GUILE_LOAD_PATH, you could use(my-guix-packages) module in any guile code, particularly in your systemconfig which may look like this:
;; This is an operating system configuration template ;; for a "desktop" setup with GNOME and Xfce. (use-modules (gnu) (gnu system nss) (my-guix-packages)) (use-service-modules desktop) (use-package-modules certs) (operating-system (host-name "komputilo") (timezone "America/Guayaquil") (locale "es_EC.utf8") ;; Assuming /dev/sdX is the target hard disk, and "my-root" ;; is the label of the target root file system. (bootloader (grub-configuration (device "/dev/sda"))) (initrd (lambda (fs . args) (apply base-initrd fs #:extra-modules '("pata_amd" "sata_nv") args))) (firmware (list openfwwf-firmware)) ;; (firmware (cons* b34-tools ;; openfwwf-firmware %base-firmware)) (file-systems (cons (file-system (device "raiz") (title 'label) (mount-point "/") (type "ext4")) %base-file-systems)) (users (cons (user-account (name "quiliro") (comment "Quiliro Ordonez") (group "users") (supplementary-groups '("wheel" "netdev" "audio" "video")) (home-directory "/home/quiliro")) %base-user-accounts)) ;; This is where we specify system-wide packages. (packages (cons* nss-certs ;for HTTPS access %base-packages)) ;; Add GNOME and/or Xfce---we can choose at the log-in ;; screen with F1. Use the "desktop" services, which ;; include the X11 log-in service, networking with Wicd, ;; and more. (services (cons* (gnome-desktop-service) (xfce-desktop-service) %desktop-services)) ;; Allow resolution of '.local' host names with mDNS. (name-service-switch %mdns-host-lookup-nss))
So add the following to your ~/.bash_profile:
export GUIX_PACKAGE_PATH=/any/directory/you/want export GUILE_LOAD_PATH=/any/directory/you/want
-- Alex
Q
Q
Quilro Ordonez wrote on 4 May 2016 20:30
(address . 23409@debbugs.gnu.org)(address . lxo@fsfla.org)
c1f9add0862382112ed11b91baa8a1ab@riseup.net
Thank you very much for your help Alex. Below is my report.
El 2016-05-04 04:10, Alex Kost escribió:
Toggle quote (3 lines)> you can create> "/any/directory/you/want/my-guix-packages.scm" file
Downloaded the file and saved it on directory /home/quiliro/guix/packages
Toggle quote (5 lines)> After that the following command should build the package:> > $ GUIX_PACKAGE_PATH=/any/directory/you/want guix build > openfwwf-firmware
This is the output:
$ GUIX_PACKAGE_PATH=/home/quiliro/guix/packages guix build openfwwf-firmware/gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2$
Toggle quote (5 lines)> Also if you add this directory to GUILE_LOAD_PATH, you could use> (my-guix-packages) module in any guile code, particularly in your > system> config
Downloaded quiliro-os.scm and placed it in /home/quiliro/guix
Toggle quote (5 lines)> So add the following to your ~/.bash_profile:> > export GUIX_PACKAGE_PATH=/any/directory/you/want> export GUILE_LOAD_PATH=/any/directory/you/want
Did that.
This is the output of reconfiguring the whole system:
# guix system reconfigure /home/quiliro/guix/quiliro-os.scmguix system: error: failed to load 'quilro-os.scm':ice-9/boot-9.scm:2867:6: In procedure resolve-interface:ice-9/boot-9.scm:2867:6: no code for module (my-guix-packages)#
A
A
Alex Kost wrote on 4 May 2016 23:33
(name . Quilro Ordonez)(address . quiliro@riseup.net)
87r3dhv78q.fsf@gmail.com
Quilro Ordonez (2016-05-04 21:30 +0300) wrote:
Toggle quote (21 lines)> Thank you very much for your help Alex. Below is my report.>> El 2016-05-04 04:10, Alex Kost escribió:>> you can create>> "/any/directory/you/want/my-guix-packages.scm" file>> Downloaded the file and saved it on directory> /home/quiliro/guix/packages>>> After that the following command should build the package:>>>> $ GUIX_PACKAGE_PATH=/any/directory/you/want guix build>> openfwwf-firmware>> This is the output:>> $ GUIX_PACKAGE_PATH=/home/quiliro/guix/packages guix build> openfwwf-firmware> /gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2> $
Great, so as "guix build openfwwf-firmware" succeeds now, you can returnto answering Ludovic's message about modifying"/sys/module/firmware_class/parameters/path".
Toggle quote (21 lines)>> Also if you add this directory to GUILE_LOAD_PATH, you could use>> (my-guix-packages) module in any guile code, particularly in your>> system>> config>> Downloaded quiliro-os.scm and placed it in /home/quiliro/guix>>> So add the following to your ~/.bash_profile:>>>> export GUIX_PACKAGE_PATH=/any/directory/you/want>> export GUILE_LOAD_PATH=/any/directory/you/want>> Did that.>> This is the output of reconfiguring the whole system:>> # guix system reconfigure /home/quiliro/guix/quiliro-os.scm> guix system: error: failed to load 'quilro-os.scm':> ice-9/boot-9.scm:2867:6: In procedure resolve-interface:> ice-9/boot-9.scm:2867:6: no code for module (my-guix-packages)
Ahem, did you try "echo $GUILE_LOAD_PATH" before this? I bet it will beempty, because you export this variable as user, but run "guix system"command as root.
-- Alex
Q
Q
Quilro Ordonez wrote on 5 May 2016 01:08
(name . Alex Kost)(address . alezost@gmail.com)
70fc6efde4ccf16e88fcdaa122c12c1d@riseup.net
El 2016-05-04 16:33, Alex Kost escribió:
Toggle quote (11 lines)> Quilro Ordonez (2016-05-04 21:30 +0300) wrote:>> $ GUIX_PACKAGE_PATH=/home/quiliro/guix/packages guix build>> openfwwf-firmware>> /gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2>> $> > Great, so as "guix build openfwwf-firmware" succeeds now, you can > return> to answering Ludovic's message about modifying> "/sys/module/firmware_class/parameters/path".
No error:
# export GUIX_PACKAGE_PATH=/home/quiliro/guix/packages# echo -n $(guix build openfwwf-firmware)/lib/firmware > \ /sys/module/firmware_class/parameters/path#
Toggle quote (12 lines)>> This is the output of reconfiguring the whole system:>> >> # guix system reconfigure /home/quiliro/guix/quiliro-os.scm>> guix system: error: failed to load 'quilro-os.scm':>> ice-9/boot-9.scm:2867:6: In procedure resolve-interface:>> ice-9/boot-9.scm:2867:6: no code for module (my-guix-packages)> > Ahem, did you try "echo $GUILE_LOAD_PATH" before this? I bet it will > be> empty, because you export this variable as user, but run "guix system"> command as root.
No errors:
# guix system reconfigure guix/quilro-os.scm;;; compiling /home/quiliro/guix/packages/my-guix-packages.scm;;; compiled /root/.cache/guile/ccache/2.0-LE-8-2.0/home/quiliro/guix/packages/my-guix-packages.scm.gosubstitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%substitute: updating list of substitutes from 'https://hydra.gnu.org'... 100.0%The following derivation will be built: /gnu/store/a40j8b6k3wlbxqbn7n9n3sfcmr92x8g7-grub.cfg.drv/gnu/store/xv88rlnb9q1gk9vp7z5ih2dwf6rjd0kd-system/gnu/store/vk1z6naajhbigs0965xqbx9h9mnw2n52-grub.cfg/gnu/store/myrc5cinlhpj2yilhzv5y0szz2ax2i6z-grub-2.00activating system...setting up setuid programs in '/run/setuid-programs'...populating /etc from /gnu/store/msm5mb78xdfc49jp1400jwz9wfnmydrs-etc...usermod: sin cambiosusermod: sin cambiosusermod: sin cambiosusermod: sin cambiosusermod: sin cambiosusermod: sin cambiosusermod: sin cambiosusermod: sin cambiosusermod: sin cambiosmaking '/gnu/store/xv88rlnb9q1gk9vp7z5ih2dwf6rjd0kd-system' the current system...Installation finished. No error reported.# echo $GUILE_LOAD_PATH/home/quiliro/guix/packages#
Q
Q
Quilro Ordonez wrote on 5 May 2016 01:13
(address . 23409@debbugs.gnu.org)(address . lxo@fsfla.org)
0f0377ea297e219eab214635838e6838@riseup.net
Same errors in dmesg.
A
A
Alex Kost wrote on 5 May 2016 10:42
(address . 23409@debbugs.gnu.org)
8737pwuc9d.fsf@gmail.com
Quilro Ordonez (2016-05-05 02:13 +0300) wrote:
Toggle quote (2 lines)> Same errors in dmesg.
If you mean after system reconfiguring, then it is expected, becausenothing has changed, you just moved package definitions from you systemconfig to another file, so that "guix build" and other commands couldsee these packages.
Or do you mean after modifying"/sys/module/firmware_class/parameters/path" and "insmod"-ing thatfirmware?
Here is an excerpt of Ludo's message. Please report after doing thesesteps.
Ludovic Courtès (2016-05-03 11:01 +0300) wrote:
Toggle quote (22 lines)> 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
Q
Q
Quilro Ordonez wrote on 11 May 2016 21:01
(address . 23409@debbugs.gnu.org)
b6cfb7807bd9fade92a8fde68dfe8ec3@riseup.net
Hello:
This is my first oportunity to use my laptop with telecomunications. Below I comment with my reports. Thank you for your patience.
El 2016-05-05 03:42, Alex Kost escribió:
Toggle quote (13 lines)> 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?
Sorry, I didn't test that yet. I did it now. The output is below the respective part of Ludo's message.
Toggle quote (21 lines)> 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?
Here it is:
$ sudo bash# export GUIX_PACKAGE_PATH=/home/quiliro/guix/packages# echo -n $(guix build openfwwf-firmware) > /sys/module/firmware_class/parameters/pathsubstitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%# cat /sys/module/firmware_class/parameters/path/gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2# insmod b43-openinsmod: ERROR: could not load module b43-open: No such file or directory# echo -n $(guix build openfwwf-firmware)/lib/firmware > /sys/module/firmware_class/parameters/path# cat /sys/module/firmware_class/parameters/path/gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2/lib/firmwareo# insmod b43-openinsmod: ERROR: could not load module b43-open: No such file or directory#
Toggle quote (8 lines)>> Also, can you show the output of:>> >> find $(guix build b43-firmware-whatever)/lib/firmware>> >> ?>> >> It should contain “b43-open/ucode5.fw”.
# find $(guix build b43-open)/lib/firmwareguix build: error: b43-open: unknown packagefind: ‘/lib/firmware’: No existe el fichero o el directorio# find $(guix build openfwwf-firmware)/lib/firmwarefind: ‘/gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2/lib/firmware’: No existe el fichero o el directorio# find $(guix build openfwwf-firmware)/gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2/gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2/b43-open/gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2/b43-open/b0g0initvals5.fw/gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2/b43-open/b0g0bsinitvals5.fw/gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2/b43-open/ucode5.fw#
Q
Q
Quilro Ordonez wrote on 12 May 2016 18:11
(address . 23409@debbugs.gnu.org)(address . lxo@fsfla.org)
439cb02466263acb8b2d19df2beb6ff1@riseup.net
Thank you for your help Alex. Below is my report.
El 2016-05-12 04:52, Alex Kost escribió:
Toggle quote (54 lines)> Quilro Ordonez (2016-05-11 22:01 +0300) wrote:> >> El 2016-05-05 03:42, Alex Kost escribió:>>> 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?>> >> Here it is:>> >> $ sudo bash>> # export GUIX_PACKAGE_PATH=/home/quiliro/guix/packages>> # echo -n $(guix build openfwwf-firmware) >>> /sys/module/firmware_class/parameters/path>> substitute: updating list of substitutes from>> 'https://mirror.hydra.gnu.org'... 100.0%>> substitute: updating list of substitutes from>> 'https://mirror.hydra.gnu.org'... 100.0%>> substitute: updating list of substitutes from>> 'https://mirror.hydra.gnu.org'... 100.0%>> substitute: updating list of substitutes from>> 'https://mirror.hydra.gnu.org'... 100.0%>> # cat /sys/module/firmware_class/parameters/path>> /gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2>> # insmod b43-open>> insmod: ERROR: could not load module b43-open: No such file or >> directory>> # echo -n $(guix build openfwwf-firmware)/lib/firmware >>> /sys/module/firmware_class/parameters/path>> # cat /sys/module/firmware_class/parameters/path>> /gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2/lib/firmware>> o# insmod b43-open>> insmod: ERROR: could not load module b43-open: No such file or >> directory> > I have no idea what I suggest but did you try:> > # insmod> /gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2/b43-open
# insmod /gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2/b43-openinsmod: ERROR: could not insert module /gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2/b43-open: Is a directory#
L
L
Ludovic Courtès wrote on 13 May 2016 15:25
(name . Quilro Ordonez)(address . quiliro@riseup.net)
87y47e2ips.fsf@gnu.org
Hi,
Quilro Ordonez <quiliro@riseup.net> skribis:
Toggle quote (2 lines)> El 2016-05-05 03:42, Alex Kost escribió:
[...]
Toggle quote (40 lines)>> 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?>> Here it is:>> $ sudo bash> # export GUIX_PACKAGE_PATH=/home/quiliro/guix/packages> # echo -n $(guix build openfwwf-firmware) >> /sys/module/firmware_class/parameters/path> substitute: updating list of substitutes from> 'https://mirror.hydra.gnu.org'... 100.0%> substitute: updating list of substitutes from> 'https://mirror.hydra.gnu.org'... 100.0%> substitute: updating list of substitutes from> 'https://mirror.hydra.gnu.org'... 100.0%> substitute: updating list of substitutes from> 'https://mirror.hydra.gnu.org'... 100.0%> # cat /sys/module/firmware_class/parameters/path> /gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2> # insmod b43-open> insmod: ERROR: could not load module b43-open: No such file or directory
I had to double-check the module name, and it’s in fact called “b43”:
Toggle snippet (5 lines)$ find $LINUX_MODULE_DIRECTORY -name b43\*ko/run/booted-system/kernel/lib/modules/4.5.2-gnu/kernel/drivers/net/wireless/broadcom/b43/b43.ko/run/booted-system/kernel/lib/modules/4.5.2-gnu/kernel/drivers/net/wireless/broadcom/b43legacy/b43legacy.ko
Furthermore, you’ll need to use ’modprobe’ rather than ‘insmod’ (sorryabout that!).
Toggle quote (7 lines)> # find $(guix build openfwwf-firmware)> /gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2> /gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2/b43-open> /gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2/b43-open/b0g0initvals5.fw> /gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2/b43-open/b0g0bsinitvals5.fw> /gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2/b43-open/ucode5.fw
Oh so this lacks “lib/firmware” (eventually we should fix thisopenfwwf-firmware package to have the .fw files under lib/firmware;Eric? :-)).
So, to recap, you should try (again as root):
echo -n $(guix build openfwwf-firmware)/b43-open \ > /sys/module/firmware_class/parameters/path modprobe b43 dmesg | tail
Could you try and report back?
Thanks for your patience!
Ludo’.
Q
Q
Quilro Ordonez wrote on 13 May 2016 23:15
(address . ludo@gnu.org)
635e88c088fe98b4fe895d6a95a84d08@riseup.net
Hi,
El 2016-05-13 08:25, ludo@gnu.org escribió:
Toggle quote (8 lines)> I had to double-check the module name, and it’s in fact called “b43”:> > --8<---------------cut here---------------start------------->8---> $ find $LINUX_MODULE_DIRECTORY -name b43\*ko> /run/booted-system/kernel/lib/modules/4.5.2-gnu/kernel/drivers/net/wireless/broadcom/b43/b43.ko> /run/booted-system/kernel/lib/modules/4.5.2-gnu/kernel/drivers/net/wireless/broadcom/b43legacy/b43legacy.ko> --8<---------------cut here---------------end--------------->8---
Yes. I get that same result.
Toggle quote (9 lines)> So, to recap, you should try (again as root):> > echo -n $(guix build openfwwf-firmware)/b43-open \> > /sys/module/firmware_class/parameters/path> modprobe b43> dmesg | tail> > Could you try and report back?
# echo -n $(guix build openfwwf-firmware)/b43-open /sys/module/firmware_class/parameters/pathguix build: error: openfwwf-firmware: unknown package/b43-open /sys/module/firmware_class/parameters/path# rmmod b43# modprobe b43# dmesg | tail[ 20.409663] Console: switching to colour frame buffer device 160x50[ 20.411395] nouveau 0000:00:05.0: fb0: nouveaufb frame buffer device[ 20.420052] [drm] Initialized nouveau 1.3.1 20120801 for 0000:00:05.0 on minor 0[ 24.935207] input: HDA NVidia Front Headphone as /devices/pci0000:00/0000:00:10.1/sound/card0/input10[ 40.788264] NET: Registered protocol family 4[ 40.994977] NET: Registered protocol family 3[ 41.137842] NET: Registered protocol family 5[ 974.864509] b43-wlan ERROR: Dual-core devices are not supported[ 974.864521] b43: probe of ssb0:0 failed with error -524[ 974.864536] Broadcom 43xx driver loaded [ Features: PNL ]#
Toggle quote (2 lines)> Thanks for your patience!
Thank YOU for the freedom....
I will be traveling to a far away community in the jungle this weekend. So I will be available with telecommunications for about 11 more hours. After that I will be able to answer only in about 66 hours.
Quiliro
A
A
Alex Kost wrote on 14 May 2016 18:17
(name . Quilro Ordonez)(address . quiliro@riseup.net)
87poso397n.fsf@gmail.com
Quilro Ordonez (2016-05-14 00:15 +0300) wrote:
[...]
Toggle quote (13 lines)>> So, to recap, you should try (again as root):>>>> echo -n $(guix build openfwwf-firmware)/b43-open \>> > /sys/module/firmware_class/parameters/path>> modprobe b43>> dmesg | tail>>>> Could you try and report back?>> # echo -n $(guix build openfwwf-firmware)/b43-open> /sys/module/firmware_class/parameters/path> guix build: error: openfwwf-firmware: unknown package
I thought we passed this stage. You reported that this package wasbuilt successfully [1]. Please don't forget that you need to adjustGUIX_PACKAGE_PATH, otherwise "guix build" wouldn't know where to findyour packages.
[1] http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23409#37
-- Alex
L
L
Ludovic Courtès wrote on 2 Nov 2016 23:19
(name . Eric Bavier)(address . ericbavier@openmailbox.org)
87d1idle2j.fsf@gnu.org
Eric Bavier <ericbavier@openmailbox.org> skribis:
Toggle quote (32 lines)> 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, do you know if the firmware package you wrote got more testing?It’s been mentioned several times on IRC over time.
TIA. :-)
Ludo’.
Q
Q
Quiliro Ordonez wrote on 4 Nov 2016 01:43
(address . 23409@debbugs.gnu.org)
b27aed9f4b54018aea8227bef7d37b55@riseup.net
El 2016-05-01 08:19, ludo@gnu.org escribió:
Toggle quote (31 lines)> 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?> > I assume you used the firmware packages that Leo copied. Could you get> its author to submit it? :-)> > What’s your GuixSD OS config like? You must make sure to list the> firmware packages in the ‘firmware’ field, as noted at:> > > https://www.gnu.org/software/guix/manual/html_node/operating_002dsystem-Reference.html#index-firmware> > Is this part OK?
I no longer Have that computer. I was not able to use GuixSD because I was not able to configure the system correctly.
Q
Q
Quiliro Ordonez wrote on 4 Nov 2016 01:46
(address . ludo@gnu.org)
20293c389d4c800b630d5cfded6da3e9@riseup.net
I wonder why this email is arriving today.
El 2016-05-01 08:19, ludo@gnu.org escribió:
Toggle quote (33 lines)> 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?> > I assume you used the firmware packages that Leo copied. Could you get> its author to submit it? :-)> > What’s your GuixSD OS config like? You must make sure to list the> firmware packages in the ‘firmware’ field, as noted at:> > > https://www.gnu.org/software/guix/manual/html_node/operating_002dsystem-Reference.html#index-firmware> > Is this part OK?> > Thanks,> Ludo’.
L
L
Ludovic Courtès wrote on 11 Jan 2017 23:29
(name . Eric Bavier)(address . ericbavier@openmailbox.org)
87eg09ut5y.fsf@gnu.org
ludo@gnu.org (Ludovic Courtès) skribis:
Toggle quote (37 lines)> Eric Bavier <ericbavier@openmailbox.org> skribis:>>> 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, do you know if the firmware package you wrote got more testing?> It’s been mentioned several times on IRC over time.
This was done in commit 52db41aff8771518f99eb1f9b63b814b568f7a4a back inNov. 2016. Closing!
Ludo’.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send email to 23409@debbugs.gnu.org