Zyxel NWD210N not accepted at boot time but after plugging it in again

[PseudoCylon]

On Sat, Dec 17, 2011 at 6:11 AM, Bernhard Schmidt <bschmidt at freebsd.org> wrote:
> On Saturday 17 December 2011 06:58:56 Erich Dollansky wrote:
>> Hi,
>>
>> I have a simple problem with this Zyxel wireless adaptor. I am not able to use it directly after a reboot. The interface becomes only available after I unplug it and plug it in again.
>>
>> I believe that this is the crucial message:
>>
>> run0: could not load 8051 microcode
>>
>> As I have said, it all works as expected after I plugged it in again.
>>
>> Here is my dmesg with the messages regarding the device. The first part is from the boot and the remaining is from the replugging.
>>
>> run0: <1.0> on usbus1
>> run0: MAC/BBP RT2860 (rev 0x0102), RF RT2820 (MIMO 2T2R), address 00:19:cb:85:aa:76
>> runfw: root not mounted yet, no way to load image
>> run0: failed loadfirmware of file runfw
>> run0: could not load 8051 microcode
>> device_attach: run0 attach returned 6
>> run0: <1.0> on usbus1
>> run0: MAC/BBP RT2860 (rev 0x0102), RF RT2820 (MIMO 2T2R), address 00:19:cb:85:aa:76
>> run0: firmware RT2870 loaded
>>
>> I think that the explanation is so simple but I do not see it.
>
> run(4) tries to load the firmware on attach at which point the root
> filesystem isn't yet mounted. Actually I think the prefered behaviour
> is to load it during init, not sure this is possible for run(4)
> though. Someone should check this. :)
>
mmm... It seems "someone" is me.

At the quick look, the firmware could be loaded during the init. Give
me a few days, I will try to change.

> As a workaround you can add runfw_load="YES" to /boot/loader.conf
>
Yep. This should load the firmware during the boot.


AK