Ralink RT3573 / ASUS USB-N66: run0: could not load 8051 microcode

[Kevin Lo]

Cool!  I committed a fix in r262465, thanks.

     Kevin

On 2014/02/25 00:58, Alex Deiter wrote:
> Hello Kevin,
>
> Thank you very much!
> Successfully tested!
>
>
> 2014-02-24 12:42 GMT+04:00 Kevin Lo <kevlo at freebsd.org>:
>
>> On 2014/02/19 10:12, Kevin Lo wrote:
>>
>>> On 2014/02/18 14:17, Alex Deiter wrote:
>>>
>>>> Hello,
>>>>
>>> Hi Alex,
>>>
>>>
>>>> Thank you for your advice!
>>>> I found a workaround:
>>>>
>>>> # ifconfig wlan0 create wlandev run0
>>>>
>>>> then wait 5 minutes ;-)
>>>>
>>>> and only thereafter:
>>>>
>>>> # ifconfig wlan0 up
>>>>
>>>> run0: <1.0> on usbus1
>>>> run0: MAC/BBP RT3593 (rev 0x0402), RF RT3053 (MIMO 3T3R), address
>>>> 30:85:a9:f4:52:bd
>>>> uhid0: <vendor 0x04d9 USB Keyboard, class 0/0, rev 1.10/1.01, addr 4> on
>>>> usbus1
>>>> wlan0: Ethernet address: 30:85:a9:f4:52:bd
>>>> run0: firmware RT3071 ver. 0.33 loaded
>>>>
>>>> But found another issue: ifconfig wlan0 list scan command does not show
>>>> any
>>>> results:
>>>>
>>>> root at test:~ # ifconfig wlan0 list scan
>>>> root at test:~ #
>>>>
>>>> root at test:~ # wlandebug -i wlan0 scan
>>>> net.wlan.0.debug: 0x0 => 0x200000<scan>
>>>>
>>>> wlan0: sta_pick_bss: no scan candidate
>>>> wlan0: scan_task: done, restart [ticks 487917, dwell min 20 scanend
>>>> 2147963261]
>>>> wlan0: scan_task: chan 140a ->   1g [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan   1g ->   6g [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan   6g ->  11g [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan  11g ->   7g [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan   7g ->  52a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan  52a ->  56a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan  56a ->  60a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan  60a ->  64a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan  64a ->  36a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan  36a ->  40a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan  40a ->  44a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan  44a ->  48a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan  48a ->   2g [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan   2g ->   3g [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan   3g ->   4g [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan   4g ->   5g [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan   5g ->   8g [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan   8g ->   9g [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan   9g ->  10g [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan  10g -> 149a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan 149a -> 153a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan 153a -> 157a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan 157a -> 161a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan 161a -> 100a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan 100a -> 104a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan 104a -> 108a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan 108a -> 112a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan 112a -> 116a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan 116a -> 120a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan 120a -> 124a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan 124a -> 128a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan 128a -> 132a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan 132a -> 136a [active, dwell min 20ms max 200ms]
>>>> wlan0: scan_task: chan 136a -> 140a [active, dwell min 20ms max 200ms]
>>>> wlan0: sta_pick_bss: no scan candidate
>>>>
>>> I have an ZyxXEL NWD2705 working fine.  It has the exact same chipset as
>>> the ASUS USB-N66.  So far I haven't been able to come up with a good
>>> solution to your problem.  I purchased the ASUS USB-N66 and will arrive
>>> in the next couple of days.  Hope I could find a new interesting bug :-)
>>>
>> After r258363, I forgot to add a flag to run's device list which uses a
>> standard scsi eject.  The ASUS USB-N66 has been tested to work on my
>> laptop.
>> The attached patch should fix your problem :-)  Please test it, thanks.
>>
>>      Kevin
>>
>
>