| 1 |
On 02/12/2013 09:43 PM, Duncan wrote: |
| 2 |
> Christopher Head posted on Tue, 12 Feb 2013 11:39:57 -0800 as excerpted: |
| 3 |
> |
| 4 |
>> On Sun, 10 Feb 2013 14:49:03 -0800 Alec Warner <antarus@g.o> |
| 5 |
>> wrote: |
| 6 |
>> |
| 7 |
>>> Most external firmware is not needed to boot. If you need it to boot, |
| 8 |
>>> you will have to stow it in the initramfs. |
| 9 |
or the kernel itself ... |
| 10 |
>> |
| 11 |
>> For those of us who prefer monolithic kernels, virtually all firmware is |
| 12 |
>> needed to boot. Even if a network interface doesn't need to be |
| 13 |
>> operational for boot, the kernel insists that the firmware be available |
| 14 |
>> right at boot or else it will fail and the interface will never appear. |
| 15 |
> |
| 16 |
> I'm a monolithic kernel guy myself, and I simply build-in the firmware I |
| 17 |
> need (three radeon firmware files, IIRC, used to be tg3 as well until |
| 18 |
> that mobo died). |
| 19 |
dito. |
| 20 |
|
| 21 |
> And FWIW, I didn't really know about linux-firmware either, but google |
| 22 |
> knew when I asked it about the files the kernel errors spit out. =:^) |
| 23 |
> And I didn't actually install it, either. I simply grabbed the tarball |
| 24 |
> and extracted the files I needed, placing them where the kernel could |
| 25 |
> find them. |
| 26 |
from cross distro source etc. |
| 27 |
I wonder how that linux-firmware serves it all will handle different |
| 28 |
versions of one firmware-filename with disjunct sets of supported |
| 29 |
hardware revisions. |
| 30 |
Random files in /lib/firmware out of packet manager space it is (form me). |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Michael Weber |
| 35 |
Gentoo Developer |
| 36 |
web: https://xmw.de/ |
| 37 |
mailto: Michael Weber <xmw@g.o> |
Archives