From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 30 18:52:28 2013 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 94A73FB4 for ; Mon, 30 Dec 2013 18:52:28 +0000 (UTC) Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 523511520 for ; Mon, 30 Dec 2013 18:52:28 +0000 (UTC) Received: by mail-qc0-f171.google.com with SMTP id c9so11116353qcz.2 for ; Mon, 30 Dec 2013 10:52:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=VB5k3vGMQUDSxUERlvqtX+tIfeBDbFu/abH7kB/ofnY=; b=BEI8CnerAedW48MkgMDeRisZv2kHaB5FBOtReHo0XhVHKe3bcTtzTFZ12XBUQlJkAA OHgUviQTT/MgBPVE/61C27V/UafuMYMcNDcf+QGgPKx2Ivz5J7q0umc85fsihRxI7U5B NLkKlkdvkq42+Vcft4+++1Ib/4FytauiQ9V8eycQMiuRTmjS7Iiyt5iIaOdPFZDIBNxZ 6OP75xVTvz3ULPtjBZLs7sQ8/6kbvnYYqodm9brA5urGFy5cXdtFBNtESPBNesHWSsFX MKZ4wPJ29TnroSzI+Bgfo24eKcHf9pXsMPrIEBF0fILk6Jr+PYv6fONWSMyeHdUia7D4 bQOQ== MIME-Version: 1.0 X-Received: by 10.49.76.66 with SMTP id i2mr114444857qew.35.1388429546759; Mon, 30 Dec 2013 10:52:26 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.52.8 with HTTP; Mon, 30 Dec 2013 10:52:26 -0800 (PST) In-Reply-To: <20131230203659.957651ynumecyn40@webmail.raad.tartu.ee> References: <20131230203659.957651ynumecyn40@webmail.raad.tartu.ee> Date: Mon, 30 Dec 2013 10:52:26 -0800 X-Google-Sender-Auth: VMHsSCrKMQyAoaMWi8dqsMOJtVQ Message-ID: Subject: Re: TP-Link TL-WN727N V3 - cannot scan or connect to anything From: Adrian Chadd To: Toomas Aas Content-Type: text/plain; charset=ISO-8859-1 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, 30 Dec 2013 18:52:28 -0000 Don't do up scan. Just do ifconfig wlan0 up ifconfig wlan0 list scan There may be some stupid race conditions there. -a On 30 December 2013 10:36, Toomas Aas wrote: > Hello! > > I posted a request on the FreeBSD forums on this topic, but got no > responses: > http://forums.freebsd.org/viewtopic.php?f=46&t=43895 > > So, I'll repeat it here hoping that it may catch the attention of some > experts who are maybe not following the forums. > > I'm trying to get TP-Link TL-WN727N V3 USB wifi adapter working with my > FreeBSD 9.2-STABLE amd64 system (r259472). It seems to me that this adapter > uses Ralink RT5370 chipset, and support for this was merged to 9-STABLE in > r259457. > > I plug in the adapter and it seems to be recognized: > > Dec 18 18:13:15 kernel: ugen2.2: at usbus2 > Dec 18 18:13:15 kernel: run0: <1.0> on usbus2 > Dec 18 18:13:15 kernel: run0: MAC/BBP RT5390 (rev 0x0502), RF RT5370 (MIMO > 1T1R), address f8:1a:67:19:40:24 > > I create the wlan device: > > # ifconfig wlan0 create wlandev run0 > > Then I try to scan, but both of the below commands return immediately > without any result: > > # ifconfig wlan0 up scan > # ifconfig wlan0 list scan > > I tried running wlandebug -i wlan0 +scan, and an endless supply of following > is recorded in /var/log/messages: > > Dec 18 21:47:26 kernel: wlan0: ieee80211_check_scan: active scan, append > Dec 18 21:47:26 kernel: wlan0: ieee80211_scanreq: flags 0x1b duration > 0x7fffffff mindwell 0 maxdwell 0 nssid 0 > Dec 18 21:47:26 kernel: wlan0: scan_update_locked: current scanner is > , switch to > Dec 18 21:47:26 kernel: wlan0: start_scan_locked: active scan, duration > 2147483647 mindwell 0 maxdwell 0, desired mode auto, flush > Dec 18 21:47:26 kernel: wlan0: scan set 1g, 6g, 11g, 7g, 2g, 3g, 4g, 5g, 8g, > 9g, 10g dwell min 20ms max 200ms > Dec 18 21:47:26 kernel: wlan0: start_scan_locked: active scan already in > progress > Dec 18 21:47:26 kernel: wlan0: scan_task: chan 1b -> 1g [active, dwell > min 20ms max 200ms] > Dec 18 21:47:26 kernel: wlan0: scan_task: chan 1g -> 6g [active, dwell > min 20ms max 200ms] > Dec 18 21:47:27 kernel: wlan0: scan_task: chan 6g -> 11g [active, dwell > min 20ms max 200ms] > Dec 18 21:47:27 kernel: wlan0: scan_task: chan 11g -> 7g [active, dwell > min 20ms max 200ms] > Dec 18 21:47:27 kernel: wlan0: scan_task: chan 7g -> 2g [active, dwell > min 20ms max 200ms] > Dec 18 21:47:27 kernel: wlan0: scan_task: chan 2g -> 3g [active, dwell > min 20ms max 200ms] > Dec 18 21:47:27 kernel: wlan0: scan_task: chan 3g -> 4g [active, dwell > min 20ms max 200ms] > Dec 18 21:47:28 kernel: wlan0: scan_task: chan 4g -> 5g [active, dwell > min 20ms max 200ms] > Dec 18 21:47:28 kernel: wlan0: scan_task: chan 5g -> 8g [active, dwell > min 20ms max 200ms] > Dec 18 21:47:28 kernel: wlan0: scan_task: chan 8g -> 9g [active, dwell > min 20ms max 200ms] > Dec 18 21:47:28 kernel: wlan0: scan_task: chan 9g -> 10g [active, dwell > min 20ms max 200ms] > Dec 18 21:47:29 kernel: wlan0: sta_pick_bss: no scan candidate > Dec 18 21:47:29 kernel: wlan0: scan_task: done, restart [ticks 1706420, > dwell min 20 scanend 2149187524] > Dec 18 21:47:29 kernel: wlan0: scan_task: chan 10g -> 1g [active, dwell > min 20ms max 200ms] > Dec 18 21:47:29 kernel: wlan0: scan_task: chan 1g -> 6g [active, dwell > min 20ms max 200ms] > Dec 18 21:47:29 kernel: wlan0: scan_task: chan 6g -> 11g [active, dwell > min 20ms max 200ms] > Dec 18 21:47:29 kernel: wlan0: scan_task: chan 11g -> 7g [active, dwell > min 20ms max 200ms] > > I've watched this output for 10 minutes and it just seems to go on > indefinitely. I'm not sure what to think of this. There are several access > points near me that the scan should find, but it doesn't. When I plug in the > same adapter to a laptop with Windows 7, it successfully shows the nearby > access points and allows me to connect to one, so the adapter is not broken. > Any ideas for further troubleshooting are welcome. > > -- > Toomas Aas > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org"