Re: TP-Link TL-WN727N V3 - cannot scan or connect to anything
Toomas Aas wrote: Hello Kevin! I hate debugging problems on the last day of the year :-) Look at the bright side - one more problem fixed in 2013 :) It seems like the firmware forgot to MFC. I just MFC'ed r256717. Tested on the 9.2-STABLE (r260119) with the TL-WN727N wlan device. Confirmed, now it also works for me. Cool! BTW, for some reason I cannot build a kernel with "device runfw". I added the following to my kernel config: options IEEE80211_DEBUG device run device runfw device wlan device wlan_amrr device wlan_wep device wlan_ccmp device wlan_tkip and buildkernel failed: clang -c -O -pipe -march=athlon64 -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/dev/usb/wlan/if_run.c clang -O -pipe -march=athlon64 -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -c runfw.c uudecode -o runfw /usr/src/sys/contrib/dev/run/rt2870.fw.uu ld -b binary --no-warn-mismatch -d -warn-common -r -o runfw.fwo ld: no input files *** [runfw.fwo] Error code 1 I removed "device runfw" from kernel config, leaving everything else as is. Kernel built successfully and runfw seems to work as loadable module. Problem fixed by gonzo in r252064. It's just MFC'ed to stable/9 as r260134. :-) Happy end_of_the_year! Happy New Year! Kevin ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: TP-Link TL-WN727N V3 - cannot scan or connect to anything
Hello Kevin! I hate debugging problems on the last day of the year :-) Look at the bright side - one more problem fixed in 2013 :) It seems like the firmware forgot to MFC. I just MFC'ed r256717. Tested on the 9.2-STABLE (r260119) with the TL-WN727N wlan device. Confirmed, now it also works for me. BTW, for some reason I cannot build a kernel with "device runfw". I added the following to my kernel config: options IEEE80211_DEBUG device run device runfw device wlan device wlan_amrr device wlan_wep device wlan_ccmp device wlan_tkip and buildkernel failed: clang -c -O -pipe -march=athlon64 -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/dev/usb/wlan/if_run.c clang -O -pipe -march=athlon64 -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -c runfw.c uudecode -o runfw /usr/src/sys/contrib/dev/run/rt2870.fw.uu ld -b binary --no-warn-mismatch -d -warn-common -r -o runfw.fwo ld: no input files *** [runfw.fwo] Error code 1 I removed "device runfw" from kernel config, leaving everything else as is. Kernel built successfully and runfw seems to work as loadable module. Happy end_of_the_year! -- Toomas Aas ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: TP-Link TL-WN727N V3 - cannot scan or connect to anything
On 2013/12/31 02:36, Toomas Aas wrote: Hello! Hi Toomas, 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 0x7fff 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. I hate debugging problems on the last day of the year :-) It seems like the firmware forgot to MFC. I just MFC'ed r256717. Tested on the 9.2-STABLE (r260119) with the TL-WN727N wlan device. Please give it a try, thanks. Kevin ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: TP-Link TL-WN727N V3 - cannot scan or connect to anything
You have to do an 'up' with that ifconfig create line, or run the supplicant. The supplicant does the 'up' itself. -a On 30 December 2013 15:09, Thomas Mueller wrote: > from Toomas AAS: > >> Hello Adrian! > >> Thanks for the idea. > >> I tried with just "ifconfig wlan0 up". Indeed it seems that the "scan" >> is redundant, as wlandebug output shows that a scan is started >> immediately after I issue the "ifconfig wlan0 up" command. Alas, the >> scan result is still the same as in my original message, and "ifconfig >> wlan0 list scan" shows no results. > > Surprise that scan would occur gratuitously. When I type > > ifconfig wlan0 create wlandev rsu0 wlanmode sta > > I don't get any scan. But I can follow with > wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf > and this connects or associates. I still need > > dhclient wlan0 > or > ifconfig wlan0 inet 192.168.0.101 netmask 255.255.255.0 > route add default 192.168.0.1 > > This is for Hiro H50191 USB-stick wireless adapter. > Chipset is RTL8191SU, FreeBSD >= 10 device rsu. > > With re(4) bug, this is my only way for Internet access from FreeBSD on > MSI Z77 MPOWER motherboard. > > Tom > > ___ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org" ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: TP-Link TL-WN727N V3 - cannot scan or connect to anything
from Toomas AAS: > Hello Adrian! > Thanks for the idea. > I tried with just "ifconfig wlan0 up". Indeed it seems that the "scan" > is redundant, as wlandebug output shows that a scan is started > immediately after I issue the "ifconfig wlan0 up" command. Alas, the > scan result is still the same as in my original message, and "ifconfig > wlan0 list scan" shows no results. Surprise that scan would occur gratuitously. When I type ifconfig wlan0 create wlandev rsu0 wlanmode sta I don't get any scan. But I can follow with wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf and this connects or associates. I still need dhclient wlan0 or ifconfig wlan0 inet 192.168.0.101 netmask 255.255.255.0 route add default 192.168.0.1 This is for Hiro H50191 USB-stick wireless adapter. Chipset is RTL8191SU, FreeBSD >= 10 device rsu. With re(4) bug, this is my only way for Internet access from FreeBSD on MSI Z77 MPOWER motherboard. Tom ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: TP-Link TL-WN727N V3 - cannot scan or connect to anything
Ok. Kevin? -a On 30 December 2013 11:53, Toomas Aas wrote: > Hello Adrian! > > Thanks for the idea. > > I tried with just "ifconfig wlan0 up". Indeed it seems that the "scan" is > redundant, as wlandebug output shows that a scan is started immediately > after I issue the "ifconfig wlan0 up" command. Alas, the scan result is > still the same as in my original message, and "ifconfig wlan0 list scan" > shows no results. > > > On Mon, 30 Dec 2013 Adrian Chadd wrote: > >> 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 >>> 0x7fff 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
Re: TP-Link TL-WN727N V3 - cannot scan or connect to anything
Hello Adrian! Thanks for the idea. I tried with just "ifconfig wlan0 up". Indeed it seems that the "scan" is redundant, as wlandebug output shows that a scan is started immediately after I issue the "ifconfig wlan0 up" command. Alas, the scan result is still the same as in my original message, and "ifconfig wlan0 list scan" shows no results. On Mon, 30 Dec 2013 Adrian Chadd wrote: 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 0x7fff 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-unsubscr...@freebsd.org" -- Toomas Aas Tartu linnakantselei arvutivõrgu peaspetsialist tel 736 1274 mob 513 6493 ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: TP-Link TL-WN727N V3 - cannot scan or connect to anything
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 > 0x7fff 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-unsubscr...@freebsd.org" ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
TP-Link TL-WN727N V3 - cannot scan or connect to anything
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 0x7fff 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-unsubscr...@freebsd.org"