1 |
>> Maybe you have an older firmware installed from a different package? |
2 |
>> Run emerge -p linux-firmware on that box to see if there's a blocker. |
3 |
> |
4 |
> linux-firmware is blocked by radeon-ucode and rt61-firmware, |
5 |
|
6 |
I'm guessing that radeon-ucode and rt61-firmware and all the others |
7 |
are being deprecated in favour of linux-firmware, but i don't recall |
8 |
seeing an elog on it. |
9 |
|
10 |
> but now |
11 |
> that I look closer I realize that ifconfig doesn't show an eth0 |
12 |
> interface at all even though lspci -v shows: |
13 |
> |
14 |
> Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI |
15 |
> Express Gigabit Ethernet controller |
16 |
> ... |
17 |
> Kernel driver in use: r8169 |
18 |
> |
19 |
> Shouldn't the eth0 interface appear in ifconfig once the r8169 driver |
20 |
> is loaded? dmesg has no mention of eth0 or r8169. |
21 |
|
22 |
That's odd. Does that box still have the failed loading firmware |
23 |
error? Perhaps missing firmware stops eth0 from being created. I'd try |
24 |
installing linux-fireware and trying again (assuming you havent |
25 |
already). |
26 |
|
27 |
>>> I guess linux-firmware is a package released by the kernel folks |
28 |
>>> containing certain firmware blobs? It looks like rt73 is in there but |
29 |
>>> not b43. |
30 |
>> |
31 |
>> Maybe these? |
32 |
>> /lib/firmware/brcm/bcm4329-fullmac-4.bin |
33 |
>> /lib/firmware/brcm/bcm4329-fullmac-4.txt |
34 |
>> /lib/firmware/brcm/bcm43xx-0.fw |
35 |
>> /lib/firmware/brcm/bcm43xx_hdr-0.fw |
36 |
>> /lib/firmware/LICENCE.broadcom_bcm43xx |
37 |
> |
38 |
> Right again. The contents of /lib/firmware/b43 and /lib/firmware/brcm |
39 |
> are completely different, but you think either one will work with a |
40 |
> b43 device? |
41 |
|
42 |
The driver will know which one it wants. You could grep the source for |
43 |
the firmware file names to see which it pulls in. |