Quote:
Originally Posted by cynwulf
I have the same chipset (out of use now since I switched to powerline adapters). It worked well enough for me In FreeBSD 9.x/10.0/10.1 and 10.2 (ath driver). It also worked flawlessly with OpenBSD's athn driver and with DragonFly's ath driver. NetBSD only supports it in 7.0 and -current
|
Glorious news! I first installed OpenBSD but the kernel panicked moments after installing the ath firmware. I had planned on trying both {Open,Free}BSD on this machine so I just moved on without any further exploration of the issue. So, there is a light at the end of this tunnel. I'll finish my assessment of FreeBSD and plan on returning to OpenBSD when 5.8 is released next month. Thanks for confirming this chipset/driver on OpenBSD!
Quote:
|
However I set my access point to 802.11g only.
|
I am using a community access point that probably supports 11g so maybe it's possible to coerce this card into operating in the 11g mode. Tried this:
# ifconfig wlan0 destroy
# ifconfig wlan0 create wlandev ath0 mode 11g
# wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf
# dhclient wlan0
# ifconfig | grep -B3 -i wireless
Code:
ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 2290
ether c4:e9:84:91:9c:20
media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng
--
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether c4:e9:84:91:9c:20
inet 192.168.49.179 netmask 0xfffffc00 broadcast 192.168.51.255
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
But it reports the mode as 11ng and the console still gets spamed with
Code:
ath0: bad series0 hwrate 0x81, tries 2 ts_status 0x0
ath0: bad series0 hwrate 0x81, tries 2 ts_status 0x0
ath0: bad series0 hwrate 0x82, tries 4 ts_status 0x0
ath0: bad series0 hwrate 0x81, tries 2 ts_status 0x0
ath0: bad series0 hwrate 0x81, tries 2 ts_status 0x0
Quote:
|
I'm not up to date with the state of FreeBSD's wireless networking stack, wpa_supplicant, etc, but last time I checked the ath driver supported the 'n' hardware like the AR9227, but not the 'n' data rates. I'm sure I tested it on an 'n' only access point and there were problems. I suggest doing some more research in that direction.
|
I guess it's time to start digging through the source code.
Muchas gracias, amigo!