| 1 |
On Sun, 10 February 2013 Maxim Kammerer <mk@×××.su> wrote: |
| 2 |
> On Sun, Feb 10, 2013 at 5:05 PM, Pacho Ramos <pacho@g.o> wrote: |
| 3 |
> > I agree as I have also needed to google and search in forums to get |
| 4 |
> > proper firmware installed in the past in some machines :/ |
| 5 |
> |
| 6 |
> for fw in $(strings -a -n 10 $(find /lib/modules -name '*.ko') | sed |
| 7 |
> -n 's/^firmware=//p' | sort -u); do |
| 8 |
> if [ ! -e /lib/firmware/${fw} ]; then |
| 9 |
> echo ${fw} |
| 10 |
> fi |
| 11 |
> done |
| 12 |
> |
| 13 |
> I guess you can do something similar with vmlinux.bin if compiling |
| 14 |
> modules into kernel. |
| 15 |
|
| 16 |
Last I looked into that the list of firmwares needed by built-in drivers |
| 17 |
is not available as is the case for modules (and in addition those |
| 18 |
built-in drivers may need the firmware long before /lib/firmware/ is |
| 19 |
available) |
| 20 |
|
| 21 |
Bruno |
| 22 |
|
| 23 |
> Looking into kernel sources is more robust, but |
| 24 |
> gets annoying fast. Full script I am using is here: |
| 25 |
> https://github.com/mkdesu/liberte/blob/master/src/root/helpers/lst-firmwares |
| 26 |
> |
| 27 |
> You can encounter superfluous warnings with modules that support |
| 28 |
> multiple firmware subversions (e.g., iwlwifi). |
Archives