Re: Issues with urtwn

2014-12-21 Thread Matthias Apitz
El día Saturday, December 20, 2014 a las 11:41:43AM -0800, Adrian Chadd escribió: > It's a race condition in the scan handling. :( > > When scan is cancelled (eg because something cancels it, or the state > transitions to IDLE or something because the VAP resets) then it > should be setting a fl

Re: BUG: run0 wifi driver

2014-12-21 Thread Matthias Apitz
El día Saturday, December 20, 2014 a las 02:42:18PM -0800, solarflow99 escribió: > Since this seems to be a BSD problem, I just wanted to report this as a > possible bug and see if anyone else has a rt3072 driver working > successfully? It used to work as run0 interface , but recently it doesn't >

Re: Issues with urtwn

2014-12-21 Thread Adrian Chadd
Sweet, which version of -HEAD did you end up updating to? -adrian On 21 December 2014 at 02:17, Matthias Apitz wrote: > El día Saturday, December 20, 2014 a las 11:41:43AM -0800, Adrian Chadd > escribió: > >> It's a race condition in the scan handling. :( >> >> When scan is cancelled (eg bec

Re: Issues with urtwn

2014-12-21 Thread Matthias Apitz
El día Sunday, December 21, 2014 a las 08:07:28AM -0800, Adrian Chadd escribió: > Sweet, which version of -HEAD did you end up updating to? I'm running HEAD r269739 (from August this year) and updated only src/sys/net80211/ieee80211_scan.c yesterday night to: r275964 | adrian | 2014-12-20 20:41:

Re: Issues with urtwn

2014-12-21 Thread Adrian Chadd
Ok. You should also update iee80211_sta.c and ieee80211_power.c. I fixed some issues there too relating to this. -adrian On 21 December 2014 at 08:40, Matthias Apitz wrote: > El día Sunday, December 21, 2014 a las 08:07:28AM -0800, Adrian Chadd > escribió: > >> Sweet, which version of -HEAD

Re: Issues with urtwn

2014-12-21 Thread Matthias Apitz
El día Sunday, December 21, 2014 a las 08:46:35AM -0800, Adrian Chadd escribió: > Ok. You should also update iee80211_sta.c and ieee80211_power.c. I > fixed some issues there too relating to this. If I do so it gives: /usr/src/sys/net80211/ieee80211_sta.c:941:2: error: implicit declaration of

Re: BUG: run0 wifi driver

2014-12-21 Thread Matthias Apitz
El día Sunday, December 21, 2014 a las 10:18:11AM -0800, solarflow99 escribió: > I can't get any debug info because it just hangs at boot up, or endlessly > reboots (+Cc: freebsd-wireless, please keep it Cc'ed to get more/better help) Is this an USB Wifi dongle? If so, you plug it in later after

Problem reports for freebsd-wireless@FreeBSD.org that need special attention

2014-12-21 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 193826] iwn does not scan channels

2014-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193826 --- Comment #1 from Henry Hu --- I just discovered that when wlan0 is connected and working normally, the empty scan is also going on: Dec 21 15:59:54 pepsi kernel: wlan0: ieee80211_scanreq: flags 0x20052 duration 0x7fff mindwell 0 max

[Bug 193826] iwn does not scan channels

2014-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193826 Adrian Chadd changed: What|Removed |Added CC||adr...@freebsd.org --- Comment #2 f

Re: Atheros AR9565 detected, not working

2014-12-21 Thread Adrian Chadd
Hi! ok, how'd you build things? a module, or in the kernel? You need to (a) build it using 'make buildkernel / make installkernel' and (b) ensure ATH_ENABLE_11N is in your kernel configuration. The GPIO bits are a bit odd - let me check the other chipset drivers. Can you compile the tools in sr

Re: Atheros AR9565 detected, not working

2014-12-21 Thread Adrian Chadd
Oh, and ath_hal_enable_rfkill() maps to setting the capability bit: #define ath_hal_enable_rfkill(_ah, _v) \ ath_hal_setcapability(_ah, HAL_CAP_RFSILENT, 1, _v, AH_NULL) .. so, the AR9300 HAL code is enabling RFKILL in the HAL and then the call to ar9300_enable_rf_kill() is unconditionally tu