[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ATH driver doesn't associate with turbo.



If I put my access point in turbo mode, the ath driver won't associate
with it.  Additionally, the documentation for my card says that it
should support upto 108Mbps in turbo mode, but the ath driver doesn't
detect this.

This is somewhat of a datapoint, since I don't know if this is
supposed to work.  My card probes as:

Preloaded elf module "/boot/kernel/if_ath.ko" at 0xc084836c.
Preloaded elf module "/boot/kernel/ath_hal.ko" at 0xc0848418.
ath0: <Atheros 5212> mem 0xfafd0000-0xfafdffff irq 11 at device 3.0 on pci2
ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3
ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath0: 802.11 address: 00:02:6f:20:5a:23

I've also noticed that the driver will stop receiving packets every
once in awhile (one or two dropped pings) ... but I nailed down what
causes that yet.

The access point is a Netgear HE 102 (a-only) that I got for $26.96
Cdn.  I also have a FreeBSD 802.11b access point in the area.  When I
put the Netgear into turbo "enabled" mode, the ath card associates
only with my 802.11b point.  If I force the ssid to the a-only ssid,
the ath card doesn't associate.

Dave.

-- 
============================================================================
|David Gilbert, Independent Contractor.       | Two things can only be     |
|Mail:       dave_(_at_)_daveg_(_dot_)_ca                    |  equal if and only if they |
|http://daveg.ca                              |   are precisely opposite.  |
=========================================================GLO================