Regression AR2413 from 9.1 to 10
All, I am in the process of upgrading my NanoBSD-ALIX kit from 802.11g to 802.11n. First step is to move from 9.1-PRERELEASE (100% stable) to 10-CURRENT with current hardware (AR2413). And alas, I am experiencing stalling wifi on all my clients: after about 30-60 seconds of being online, the client loses all connectivity (my Mac thinks it's still connected but nothing gets through anymore). *sigh*. I did not change my kernel config. MALLOC_PRODUCTION=Y etc. Where shall I start to debug this? All the ath* tools are already on my image so let's hack :-) Sven ___ 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: Regression AR2413 from 9.1 to 10
Hi Adrian, I am unable to build any svn sources from around March and April due to some yacc/parse.y failure that I cannot fix within the time I have. Can I simply restore an older version of sys/modules/ath and sys/dev/ath into an up-to-date /usr/src? Thanks Sven On Sun, Sep 23, 2012 at 10:14 AM, Adrian Chadd wrote: > Are you able to try 10.0 from say, 6 months back and see if it works? ___ 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: Regression AR2413 from 9.1 to 10
So far, so good! FreeBSD 10.0-CURRENT #0 r240893 running since this morning without glitches on my trusty AR2413. Great work! On Tue, Sep 25, 2012 at 5:37 AM, Adrian Chadd wrote: > Please try the latest -HEAD and report back. ___ 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"
AR9160 3x3 but only getting 2x2?
Hi there, I'm running FreeBSD 10-CURRENT r240893 on ALIX, just replaced my old 802.11g by a DNMA-83 3x3 802.11 card, works great, but ath only finds 2x2 instead of 3x3? dmesg with 1 antenna (which is what I'm testing now, I already really like MCS 7 over 11g): ath0: mem 0xe008-0xe008 irq 9 at device 12.0 on pci0 ath0: Setting RX chainmask to 0x1 ath0: Setting TX chainmask to 0x1 ath0: [HT] enabling HT modes ath0: [HT] 1 RX streams; 1 TX streams ath0: AR9160 mac 64.1 RF5133 phy 11.0 ath0: 2GHz radio: 0x; 5GHz radio: 0x00c0 Without any hints, I get this: ath0: [HT] enabling HT modes ath0: [HT] 2 RX streams; 2 TX streams But I would have expected 3x3, given the specs (http://unex.com.tw/product/dnma-83) and the 3 antenna connectors :-) Thanks, Sven ___ 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"
Ath 40MHz on 2.4GHz?
Does ath on CURRENT support 40Mhz channels on 2.4GHz for 802.11n? If yes, how do I enable it? I now have in rc.conf: wlans_ath0="wlan0" create_args_wlan0="wlanmode hostap" ifconfig_wlan0="inet 192.168.2.1 netmask 255.255.255.0 country NL mode 11ng channel 6:ht/40-" ifconfig -v wlan0 shows (amongst other things): status: running ssid KL5 channel 6 (2437 MHz 11g ht/40+) bssid 00:0b:6b:b1:3a:e7 I would like to use channel 1 as the secondary channel... Thanks Sven ___ 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"
Spectrum analysis?
Is there a way to do a spectrum analysis for the wifi band with ath on CURRENT? I would like to understand which channels give me the best signal/noise ratio (my baby monitor completely blows our wifi away) above and beyond other 802.11 activities. Does not need to be fast. Mikrotik has something like this; they use standard Wifi equipment to analyze 20MHz at a time with 10MHz increments, creating a nice heat map of the available spectrum... Thanks! ___ 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: Spectrum analysis?
On Wed, Oct 10, 2012 at 4:52 AM, Adrian Chadd wrote: > The AR9280 and later chips have the ability to access spectral FFT > information; but it's not yet in the open source driver. Bummer, I'm on an AR9160. Is there a simple way to show noise levels for each channel? That should give me the information I need... Thanks! ___ 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: 11n channel width
On Mon, Oct 22, 2012 at 4:09 PM, Adrian Chadd wrote: >> What difference in throuput can one expect between ht/20 and a ht/40 ? > > If you're hitting best possible circumstances? Almost 2x. I think I checked earlier: what about ht/40 on 2.4GHz? How do I enable it and select the secondary channel? 6+1 would be ideal in my situation. ___ 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: freebsd-head and spectral scan
On Wed, Jan 9, 2013 at 1:07 AM, Adrian Chadd wrote: > I hereby give you, AR9280 doing spectral + channel scanning: Much appreciated, Adrian. That is great functionality, and exactly what I was looking for. Is there a HOWTO to get this to work? I'm cranking up my buildworld cycle as we speak. Sven ___ 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"
ath performance degradation between Oct-12 and now?
I have just upgraded my ALIX router (with an Atheros 9160) from FreeBSD-HEAD r241243 (Oct 6, 2012) to r247155 (today) and I am noticing slightly lower throughput rates. With iperf, sitting 1 meter from the router, I consistently get 79-81 Mbits/sec TCP with r241243. This "drops" to 74-76 in r247155 (never higher than 75.5 actually). The rates also seem to vary a bit more (but that's hard to quantify). Anything I should be looking for? I'm more than happy to share debug output etc. if instructed how to capture. Thanks! Sven ___ 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"
From AR9160 to AR9340/AR9582
Does anyone know enough about the various Atheros devices to tell me the differences between various radios, output power, sensitivity and expected range? For various reasons, I am thinking of replacing my present FreeBSD ALIX router by a COTS OpenWRT router such as the TP-Link WDR3600. Current hardware is a WNC DNMA-83 AR9160 chipset and I'm only using 2.4GHz. The TP-Link has a AR9340 for 2.4GHz and a AR9582 for 5GHz. I read somewhere that it seems to be capped at 63 mW / 18 dBm (for 5GHz at least)... I wonder if this is better or worse than my current setup. Thanks for any insights! Sven ___ 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"
AR9160 on HEAD - unstable?
Ever since I upgraded my NanoBSD from May to October HEAD, I seem to be getting disconnects on my WLAN. It is most visible when I'm on a Skype video call on my MacBook Air, signal strength fine (MCS 15), but the MBA just loses the connection and I need to switch its wireless off and on again. Somehow it feels that these problems have gotten worse over the past few days (uptime of the box is now 12 days). This is what I see on dmesg on the NanoBSD box. What's that FRDS output...? ath0: ath_tx_default_comp: bf 0xc293e090: seqno 211: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc29438c0: seqno 212: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2942160: seqno 213: bf_next not NULL! FRDS 02:27:a7:10:7b:00->14:10:9f:f3:fb:64(00:0b:6b:b1:3a:e7) data QoS [TID 0] WEP [IV 7e 90 00 03 00 00 KID 0] 0M 8842 1410 9ff3 fb64 000b 6bb1 3ae7 0227 a710 7b00 700d 7e90 0020 0300 0300 0800 FRDS 02:27:a7:10:7b:00->14:10:9f:f3:fb:64(00:0b:6b:b1:3a:e7) data QoS [TID 0] WEP [IV 73 01 00 00 00 00 KID 1] 0M 8842 1410 9ff3 fb64 000b 6bb1 3ae7 0227 a710 7b00 40c9 0300 7301 0060 0300 0800 FRDS 02:27:a7:10:7b:00->14:10:9f:f3:fb:64(00:0b:6b:b1:3a:e7) data QoS [TID 0] WEP [IV 6e 7a 00 00 00 00 KID 0] 0M 8842 1410 9ff3 fb64 000b 6bb1 3ae7 0227 a710 7b00 303d 6e7a 0020 0300 0800 FRDS 02:27:a7:10:7b:00->14:10:9f:f3:fb:64(00:0b:6b:b1:3a:e7) data QoS [TID 0] WEP [IV 7d 0a 00 00 00 00 KID 0] 0M 8842 1410 9ff3 fb64 000b 6bb1 3ae7 0227 a710 7b00 c0a7 7d0a 0020 0300 0800 FRDS 02:27:a7:10:7b:00->14:10:9f:f3:fb:64(00:0b:6b:b1:3a:e7) data QoS [TID 0] WEP [IV 99 11 00 00 00 00 KID 0] 0M 8842 1410 9ff3 fb64 000b 6bb1 3ae7 0227 a710 7b00 7019 9911 0020 0300 0800 ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 4) ath0: device timeout FRDS 00:11:32:1a:e1:54->14:10:9f:f3:fb:64(00:0b:6b:b1:3a:e7) data QoS [TID 0] WEP [IV 37 00 00 00 00 00 KID 1] 0M 8842 1410 9ff3 fb64 000b 6bb1 3ae7 0011 321a e154 7024 3700 0060 0300 0800 FRDS 02:27:a7:10:7b:00->14:10:9f:f3:fb:64(00:0b:6b:b1:3a:e7) data QoS [TID 0] WEP [IV 33 02 00 00 00 00 KID 0] 0M 8842 2c00 1410 9ff3 fb64 000b 6bb1 3ae7 0227 a710 7b00 3023 15fc 3302 0020 0300 0800 ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 4) ath0: ath_tx_default_comp: bf 0xc29538d0: seqno 128: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc294d600: seqno 129: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc29490f0: seqno 130: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2953270: seqno 131: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc29458a0: seqno 132: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc294f1a0: seqno 133: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2944250: seqno 134: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2946340: seqno 135: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc293b500: seqno 136: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc294bd90: seqno 137: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2954d00: seqno 138: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2949ca0: seqno 139: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc293f900: seqno 140: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2943ae0: seqno 141: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2945460: seqno 142: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc294b620: seqno 143: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2936330: seqno 144: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc29425a0: seqno 145: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc293d1b0: seqno 146: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2946de0: seqno 147: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc294cfa0: seqno 148: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2945f00: seqno 149: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2948870: seqno 150: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc294d710: seqno 151: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc293da30: seqno 152: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2938420: seqno 153: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2955030: seqno 154: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2937210: seqno 155: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc293d5f0: seqno 156: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc2943e10: seqno 157: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc293f3b0: seqno 158: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc294e5f0: seqno 160: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc29414a0: seqno 161: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xc294de8
Re: AR9160 on HEAD - unstable?
Well, my original hypothesis was wrong: HEAD r250200 (around 3 May 2013) fully lost its wifi on me this morning. My iPhone was on during the night, which generated a long list of "stuck beacon" messages. The iPhone could not get a connection and neither could any other stations. A warm reboot did not help! I had to physically power down the ALIX box. So I guess I won't be testing on r250200 anymore, as my previous problems were all resolvable by resetting the station, not the AP. Below is the complete /var/log/messages. Any suggestions? Nov 7 21:54:23 algol newsyslog[1056]: logfile first created Nov 7 21:54:23 algol syslogd: kernel boot file is /boot/kernel/kernel Nov 7 21:54:23 algol kernel: Copyright (c) 1992-2013 The FreeBSD Project. Nov 7 21:54:23 algol kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Nov 7 21:54:23 algol kernel: The Regents of the University of California. All rights reserved. Nov 7 21:54:23 algol kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Nov 7 21:54:23 algol kernel: FreeBSD 10.0-CURRENT #0: Thu Nov 7 15:30:54 CET 2013 Nov 7 21:54:23 algol kernel: root@vmbsd10:/usr/obj/nanobsd.alix/usr/src/sys/ALIX i386 Nov 7 21:54:23 algol kernel: FreeBSD clang version 3.3 (trunk 178860) 20130405 Nov 7 21:54:23 algol kernel: CPU: Geode(TM) Integrated Processor by AMD PCS (498.06-MHz 586-class CPU) Nov 7 21:54:23 algol kernel: Origin = "AuthenticAMD" Id = 0x5a2 Family = 0x5 Model = 0xa Stepping = 2 Nov 7 21:54:23 algol kernel: Features=0x88a93d Nov 7 21:54:23 algol kernel: AMD Features=0xc040 Nov 7 21:54:23 algol kernel: real memory = 268435456 (256 MB) Nov 7 21:54:23 algol kernel: avail memory = 250781696 (239 MB) Nov 7 21:54:23 algol kernel: pnpbios: Bad PnP BIOS data checksum Nov 7 21:54:23 algol kernel: K6-family MTRR support enabled (2 registers) Nov 7 21:54:23 algol kernel: cryptosoft0: on motherboard Nov 7 21:54:23 algol kernel: pcib0 pcibus 0 on motherboard Nov 7 21:54:23 algol kernel: pci0: on pcib0 Nov 7 21:54:23 algol kernel: Geode LX: PC Engines ALIX.2 v0.99h tinyBIOS V1.4a (C)1997-2007 Nov 7 21:54:23 algol kernel: glxsb0: mem 0xefff4000-0xefff7fff irq 9 at device 1.2 on pci0 Nov 7 21:54:23 algol kernel: vr0: port 0x1000-0x10ff mem 0xe000-0xe0ff irq 10 at device 9.0 on pci0 Nov 7 21:54:23 algol kernel: vr0: Quirks: 0x2 Nov 7 21:54:23 algol kernel: vr0: Revision: 0x96 Nov 7 21:54:23 algol kernel: miibus0: on vr0 Nov 7 21:54:23 algol kernel: ukphy0: PHY 1 on miibus0 Nov 7 21:54:23 algol kernel: ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow Nov 7 21:54:23 algol kernel: vr0: Ethernet address: 00:0d:b9:19:aa:94 Nov 7 21:54:23 algol kernel: vr1: port 0x1400-0x14ff mem 0xe004-0xe00400ff irq 15 at device 11.0 on pci0 Nov 7 21:54:23 algol kernel: vr1: Quirks: 0x2 Nov 7 21:54:23 algol kernel: vr1: Revision: 0x96 Nov 7 21:54:23 algol kernel: miibus1: on vr1 Nov 7 21:54:23 algol kernel: ukphy1: PHY 1 on miibus1 Nov 7 21:54:23 algol kernel: ukphy1: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow Nov 7 21:54:23 algol kernel: vr1: Ethernet address: 00:0d:b9:19:aa:95 Nov 7 21:54:23 algol kernel: ath0: mem 0xe008-0xe008 irq 9 at device 12.0 on pci0 Nov 7 21:54:23 algol kernel: ath0: [HT] enabling HT modes Nov 7 21:54:23 algol kernel: ath0: [HT] 2 RX streams; 2 TX streams Nov 7 21:54:23 algol kernel: ath0: AR9160 mac 64.1 RF5133 phy 11.0 Nov 7 21:54:23 algol kernel: ath0: 2GHz radio: 0x; 5GHz radio: 0x00c0 Nov 7 21:54:23 algol kernel: isab0: port 0x6000-0x6007,0x6100-0x61ff,0x6200-0x623f,0x9d00-0x9d7f,0x9c00-0x9c3f at device 15.0 on pci0 Nov 7 21:54:23 algol kernel: isa0: on isab0 Nov 7 21:54:23 algol kernel: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 15.2 on pci0 Nov 7 21:54:23 algol kernel: ata0: at channel 0 on atapci0 Nov 7 21:54:23 algol kernel: ata1: at channel 1 on atapci0 Nov 7 21:54:23 algol kernel: ohci0: mem 0xefffe000-0xefffefff irq 12 at device 15.4 on pci0 Nov 7 21:54:23 algol kernel: usbus0 on ohci0 Nov 7 21:54:23 algol kernel: ehci0: mem 0xefffd000-0xefffdfff irq 12 at device 15.5 on pci0 Nov 7 21:54:23 algol kernel: usbus1: EHCI version 1.0 Nov 7 21:54:23 algol kernel: usbus1 on ehci0 Nov 7 21:54:23 algol kernel: cpu0 on motherboard Nov 7 21:54:23 algol kernel: orm0: at iomem 0xe-0xea7ff pnpid ORM on isa0 Nov 7 21:54:23 algol kernel: atrtc0: at port 0x70 irq 8 on isa0 Nov 7 21:54:23 algol kernel: Event timer "RTC" frequency 32768 Hz quality 0 Nov 7 21:54:23 algol kernel: attimer0: at port 0x40 on isa0 Nov 7 21:54:23 algol kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Nov 7 21:54:23 algol kernel: Event timer "i8254" frequency 1193182 Hz quality 100 Nov 7 21:54:23 algol kernel: uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Nov 7 21:54:23 algol kernel: uart0: console (57600,n,8,1) Nov 7
Re: AR9160 on HEAD - unstable?
OK will ignore the stuck beacon stuff :-). Warm reboot is indeed typing "reboot". That did not resolve this morning's matter. Actually, after I unplugged the ALIX for a couple of seconds, it came back up... same problem! Second time, I unplugged it for 30 seconds... problem solved...! Hardware issue with my AR9160? I've never had it this bad before. I did compile in your debug stuff + ath tools: what should I do next time this happens to get more information? On 9 November 2013 08:49, Adrian Chadd wrote: > the stuck beacon stuff is likely just the MAC getting angry at the > power save aggressiveness that the iphone/ipad does. But it itself > shouldn't lock things up. > > When you say you did a warm reboot, is that a 'reboot' where you typed > reboot? is there a physical reset button on the ALIX you can short? > ___ 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: Should I choose 10 or 11 of best WiFi AP expirience? :)
Hi Adrian, Thanks for all your hard work. To add to Lev's: what is the state of wifi in 10-RELEASE? Have significant improvements been made to CURRENT since then, or would 10-RELEASE be a good upgrade from an "oldish" CURRENT? It would be great to help people make their own decision based on some facts ;-) Sven On 23 January 2014 17:10, Adrian Chadd wrote: > I'm only developing on -current. If people wish to backport things > from -11 to -10 (or even -9) then I'll fully support them owning that > and fixing whatever bugs show up. But no, I won't be doing it. > ___ 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"
