Hi Daniel!
> I've set in the kernel config:
>
> CONFIG_FIRMWARE_IN_KERNEL=y
And what happened? Are you sure you recompiled and booted the new kernel with
CONFIG_FIRMWARE_IN_KERNEL=y?
> Although I don't see the asked file in initramfs. The file with full
> path is /lib/firmware/bnx2/bnx2-mips-06-4.6.16.fw:
>
> # zcat /boot/initrd.img-2.6.30.4-dgb | cpio -t | grep bnx2
> lib/modules/2.6.30.4-dgb/kernel/drivers/net/bnx2.ko
> 300859 blocks
>
> Whereupon this variable is set to 'y' would not have to be sufficient?
>
> <just_guessing>
> 1) Perhaps firmware must be in some other directory.
> 2) Perhaps there is no access to the FS in /lib at the moment that loads
> drivers.
> </just_guessing>
Obviously bnx2.ko is loaded from initramfs. At that time the root filesystem is
not accessible. I expected CONFIG_FIRMWARE_IN_KERNEL=y is sufficient to solve
the problem.
Here is what I would try:
- make sure the firmware is included in your kernel, or
- keep bnx2.ko from including in initramfs (unless you boot via network), or
- include /lib/firmware/bnx2/bnx2-mips-06-4.6.16.fw in initramfs
HTH
Bernhard
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
