Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 23 Aug 2006 22:33:16 -0400
From:      Jared Mauch <jared@puck.nether.net>
To:        freebsd-hackers@freebsd.org
Subject:   6.1-current 20060823 ath0 stuck beacon; resetting (bmiss count 4)
Message-ID:  <20060824023316.GB80963@puck.nether.net>

next in thread | raw e-mail | index | archive | help

	I have a Soekris 4501 (and 4521) i'm attempting to get
set up with the Atheros mini-pci cards 168c:0012 (rev 01), ie:

ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ath0: <Atheros 5211> mem 0xa0000000-0xa000ffff irq 10 at device 16.0 on pci0
ath0: Ethernet address: 00:01:24:70:42:3e
ath0: mac 4.2 phy 3.0 5ghz radio 1.7 2ghz radio 2.3

	I have more than one of the cards, so i've swapped them out
and it does not appear to be hardware related.

	Here's my basic setup (and i'm looking for help from
the ath or similar driver gurus).

	ath0 interface when configured for 802.11a + hostap and
set for hostap mode does not appear to trigger any
"stuck beacon" messages.  If I switch it over to just
802.11b media i get no beacons and it is not a viable wireless AP.

ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::201:24ff:fe70:423e%ath0 prefixlen 64 scopeid 0x1
        ether 00:01:24:70:42:3e
        media: IEEE 802.11 Wireless Ethernet autoselect mode 11a <hostap>
        status: associated
        ssid PublicAP channel 36 bssid 00:01:24:70:42:3e
        authmode OPEN privacy OFF txpowmax 28 dtimperiod 1 bintval 100

net45xx# ifconfig ath0 mode 11b
net45xx#
net45xx# ath0: stuck beacon; resetting (bmiss count 4)

net45xx# ifconfig ath0 mode 11aath0: stuck beacon; resetting (bmiss count 4)
net45xx#
<messages stop>

	i've also noticed some other problems with the driver
that appear to be triggered by twiddling the settings.  The antenna
selection when set to use antenna 0 for tx+rx

sysctls:
dev.ath.0.txantenna: 0
dev.ath.0.rxantenna: 1

	simply changing the mode w/ ifconfig to 11b from 11a will
trigger this driver/sysctl/antenna related bug.

	any tips for tracking down what is going on?  i'm going to
rebuild with ATH_DEBUG shortly and load that kernel in place.  If
there is additional data people would like to see or if i'm in the
wrong place, please help me find the right audience.

	thanks,

	- jared

-- 
Jared Mauch  | pgp key available via finger from jared@puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060824023316.GB80963>