| 1 |
> Is the filesystem mounted when it tries to find the firmware? |
| 2 |
|
| 3 |
I thought it was, but having another look at dmesg, it looks like |
| 4 |
that's not the case. |
| 5 |
|
| 6 |
proxy linux # dmesg | grep eth0 |
| 7 |
[ 0.897559] r8169 0000:02:00.0: eth0: RTL8168d/8111d at |
| 8 |
0xffffc90000360000, 1c:6f:65:20:3f:c6, XID 083000c0 IRQ 41 |
| 9 |
[ 70.453673] r8169 0000:02:00.0: eth0: unable to load firmware patch |
| 10 |
rtl_nic/rtl8168d-2.fw (-2) |
| 11 |
[ 70.461027] r8169 0000:02:00.0: eth0: link down |
| 12 |
[ 70.461050] r8169 0000:02:00.0: eth0: link down |
| 13 |
[ 70.461444] ADDRCONF(NETDEV_UP): eth0: link is not ready |
| 14 |
[ 72.851287] r8169 0000:02:00.0: eth0: link up |
| 15 |
[ 72.851846] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready |
| 16 |
|
| 17 |
proxy linux # dmesg | grep btrfs |
| 18 |
[ 1.647953] btrfs: use lzo compression |
| 19 |
[ 2.129807] VFS: Mounted root (btrfs filesystem) on device 0:13. |
| 20 |
|
| 21 |
> In other words, are you perhaps using a ramdisk? |
| 22 |
> |
| 23 |
> If you have this drives as a module, can you try removing it (rmmod |
| 24 |
> <driver> and then reloading it (modprobe <driver>)? |
| 25 |
> |
| 26 |
> If it isn't a module, can you rebuild your kernel to have the relevant |
| 27 |
> driver as a module? |
| 28 |
|
| 29 |
Its not a module - i'll make it one and see how that goes. |
Archives