Is anybody using the WL-500W with an AR5008 or AR9160 card and having a satisfactory experience?
Thanks
tanguy
The content of this topic has been archived between 23 Apr 2018 and 2 May 2018. Unfortunately there are posts – most likely complete pages – missing.
Is anybody using the WL-500W with an AR5008 or AR9160 card and having a satisfactory experience?
Thanks
tanguy
not for everyday use. not that stable. now is a test platform. nothing more. i'm talking about wireless
Chris
I'm using AR5008 (ar5416), runing the latest trunk, with ath9k...
dmesg |grep Atheros
phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81: mem=0xc0280000, irq=6
iwconfig wlan0
wlan0 IEEE 802.11bgn Mode:Master Frequency:2.442 GHz Tx-Power=20 dBm
I' have no problems with 11bg... just gona try 11n...
I will post the results ...
Any fresh news on this? Are Ar5008 cards working in n mode with latest 2.6 trunk and Wl 500w? If so, are there any additional pathces to apply at compilation time to make it work?
Thank you
I tested my wl-500gp v1 with a mikrotik r52n ar9220 and its not even detected on the router. used r18430 and ath9k.
Have it working on a ubnt rspro as ap, with ar5413 ath5k as sta.
(Last edited by Elphidium on 17 Nov 2009, 14:18)
I tested my wl-500gp v1 with a mikrotik r52n ar9220 and its not even detected on the router. used r18430 and ath9k.
Have it working on a ubnt rspro as ap, with ar5413 ath5k as sta.
Same here. Openwrt v17.01.4.
root@LEDE:~# lspci
00:00.0 Host bridge: Broadcom Limited BCM4704 PCI to SB Bridge (rev 09)
00:02.0 Network controller: Qualcomm Atheros AR922X Wireless Network Adapter (rev 01)
00:03.0 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev 61)
00:03.1 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev 61)
00:03.2 USB controller: VIA Technologies, Inc. USB 2.0 (rev 63)
root@LEDE:~# dmesg | grep ath
[ 11.917566] ath: phy0: address test failed addr: 0x00008000 - wr:0x55555555 != rd:0x45555555
[ 11.926283] ath: phy0: Unable to initialize hardware; initialization status: -19
[ 11.933896] ath9k 0000:00:02.0: Failed to initialize device
root@LEDE:~#
The discussion might have continued from here.