From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 24 16:58:10 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F05B174C; Mon, 24 Feb 2014 16:58:09 +0000 (UTC) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 588071C72; Mon, 24 Feb 2014 16:58:09 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id f8so3339992wiw.7 for ; Mon, 24 Feb 2014 08:58:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Vvcu/n24ddQfSuG8RJIifmGyzmaEtmQEeCank9+0ufo=; b=AJhwWOh1HCf0DAamrX9ZJoIV4Daf818wvauhhRiZz8RKrSwwucBj7G0kLqhU/1/5ZP LWC1XR+cnet5X7S2U40VdguVtYt7rBu77bfh3ZL0UaYLJ5CmBZHctRCOiBfBykjWrmUy X1aMJNn8UDBOkaJHcQpedye8NAx+zPOp8DDhn+RiJiNIBE3qObmmCTvyk4HVcTSiO5tc UaDTCVMCElrriTwfuCzmGb5ntz2VnFiutiZv2ybeVevxmzTyglAW+9Hul8MhOuuiE4IR Gb40k0/SgLyoB35ayz9Gz5Vx7vnPedIr1f8N5fiDa61O66HUWq7CZ1A3C1Tfd2u/NO1Y usjw== MIME-Version: 1.0 X-Received: by 10.180.96.102 with SMTP id dr6mr15406902wib.19.1393261087585; Mon, 24 Feb 2014 08:58:07 -0800 (PST) Received: by 10.217.119.132 with HTTP; Mon, 24 Feb 2014 08:58:07 -0800 (PST) In-Reply-To: <530B060F.8030204@FreeBSD.org> References: <63a130f264cbfb29dc3fd34ab3170447.squirrel@mx.waitman.net> <53041318.6090303@FreeBSD.org> <530B060F.8030204@FreeBSD.org> Date: Mon, 24 Feb 2014 20:58:07 +0400 Message-ID: Subject: Re: Ralink RT3573 / ASUS USB-N66: run0: could not load 8051 microcode From: Alex Deiter To: Kevin Lo Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Feb 2014 16:58:10 -0000 Hello Kevin, Thank you very much! Successfully tested! 2014-02-24 12:42 GMT+04:00 Kevin Lo : > 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: 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@test:~ # ifconfig wlan0 list scan >>> root@test:~ # >>> >>> root@test:~ # wlandebug -i wlan0 scan >>> net.wlan.0.debug: 0x0 => 0x200000 >>> >>> 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 > -- Alex Deiter