>> it does not actually matter how you configured the driver -- built-in kernel
>> or
>> as module: everytime when driver operates the device, it checks whether
>> firmware
>> is loaded.
> Are you sure about that? AFAIK firmware loading is only attempted once,
> when the driver is first initiali
> it does not actually matter how you configured the driver -- built-in kernel
> or
> as module: everytime when driver operates the device, it checks whether
> firmware
> is loaded.
Are you sure about that? AFAIK firmware loading is only attempted once,
when the driver is first initialized.
> f
On Mon, Aug 15, 2011 at 4:13 AM, Adam Carter wrote:
> # dmesg | grep firm
> [ 70.453673] r8169 :02:00.0: eth0: unable to load firmware patch
> rtl_nic/rtl8168d-2.fw (-2)
> # ls -l /lib/firmware/rtl_nic/rtl8168d-2.fw
> -rw-r--r-- 1 root root 1324 Aug 12 13:09 /lib/firmware/rtl_nic/rtl8168d-2.
> Is the filesystem mounted when it tries to find the firmware?
I thought it was, but having another look at dmesg, it looks like
that's not the case.
proxy linux # dmesg | grep eth0
[0.897559] r8169 :02:00.0: eth0: RTL8168d/8111d at
0xc936, 1c:6f:65:20:3f:c6, XID 083000c0 IRQ
On Mon, August 15, 2011 11:13 am, Adam Carter wrote:
> # dmesg | grep firm
> [ 70.453673] r8169 :02:00.0: eth0: unable to load firmware patch
> rtl_nic/rtl8168d-2.fw (-2)
> # ls -l /lib/firmware/rtl_nic/rtl8168d-2.fw
> -rw-r--r-- 1 root root 1324 Aug 12 13:09
> /lib/firmware/rtl_nic/rtl8168d-
# dmesg | grep firm
[ 70.453673] r8169 :02:00.0: eth0: unable to load firmware patch
rtl_nic/rtl8168d-2.fw (-2)
# ls -l /lib/firmware/rtl_nic/rtl8168d-2.fw
-rw-r--r-- 1 root root 1324 Aug 12 13:09 /lib/firmware/rtl_nic/rtl8168d-2.fw
Any ideas why this fails? Filesystem is mounted, file is re
6 matches
Mail list logo