On Tue, Apr 22, 2014 at 11:04:55AM -0700, Adrian Chadd wrote: > Try setting it up without 11n enabled: > > ifconfig wlan0 create wlandev ath0 wlanmode hostap channel 6:g > > .. and if that doesn't help, try with 11n enabled but without ampdutx: > > ifconfig wlan0 -ampdutx > > I'm not using the AR5416 as an AP at the moment but it should be ok. > I'm definitely using it as a station though. > > Can your try -HEAD instead? I don't plan on MFCing things myself back > to stable/10; i rely on others who are actively using stable/10 to do > it. I did try it to 11g (as I know that 11n wasn't supported before), but it didn't help.
I did -not- try without ampdutx. I can try that, and I can also try HEAD --- but that will take a little bit of time, as I will need to do some reconfiguring of other things to ensure that my systems are up and available while I'm testing. I'll let you know when I have a chance to test. -greg > On 21 April 2014 17:59, Greg Byshenk <free...@byshenk.net> wrote: > > On Mon, Apr 21, 2014 at 09:30:47AM -0700, Adrian Chadd wrote: > > > >> Which NIC? > > > > It is a TP-Link TL-WN951N "Wireless N PCI Adapter". > > > > dmesg: > > ath0: <Atheros 5416> mem 0xfe6f0000-0xfe6fffff irq 16 at device 0.0 on pci4 > > ath0: AR5416 mac 13.10 RF2133 phy 8.1 > > > > pciconf: > > ath0@pci0:4:0:0: class=0x028000 card=0x3071168c chip=0x0023168c > > rev=0x01 hdr=0x00 > > vendor = 'Atheros Communications Inc.' > > device = 'AR5008 Wireless Network Adapter' > > class = network > > > > On 9-STABLE, I see an occasional "stuck beacon" error, but all > > carries on more or less happily after. On 10-STABLE, the errors > > as mentioned. (It is 10-STABLE, revision 264683). > > -- greg byshenk - gbysh...@byshenk.net - Portland, OR USA _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"