El 2016-05-03 15:45, l...@gnu.org escribió:
Quilro Ordonez <quil...@riseup.net> skribis:
El 2016-05-03 03:01, l...@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?
