I was lately required to move to a newer kernel (3.12.10-rt15) on an Intel Atom
setup. All is working fine, including the wireless module (ath5k) acting as an
access point on my bridge, using hostapd:
:~$ lspci
...
03:00.0 Ethernet controller: Qualcomm Atheros AR5212/AR5213 Wireless Network
Adapter (rev 01)
Subsystem: D-Link System Inc AirPlus DWL-G520 Wireless PCI Adapter (rev. B)
Flags: bus master, fast Back2Back, medium devsel, latency 168, IRQ 20
Memory at d0000000 (32-bit, non-prefetchable) [size=64K]
Kernel driver in use: ath5k
Kernel modules: ath5k
...
:~$ iwconfig ath0
ath0 IEEE 802.11bg Mode:Master Tx-Power=27 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:on
:~$ iwlist ath0 f
ath0 11 channels in total; available frequencies :
Channel 01 : 2.412 GHz
Channel 02 : 2.417 GHz
Channel 03 : 2.422 GHz
Channel 04 : 2.427 GHz
Channel 05 : 2.432 GHz
Channel 06 : 2.437 GHz
Channel 07 : 2.442 GHz
Channel 08 : 2.447 GHz
Channel 09 : 2.452 GHz
Channel 10 : 2.457 GHz
Channel 11 : 2.462 GHz
However, as can be seen above I am now unable to read the current
channel/frequency info within iwlist, iwconfig or any other tool; ioctl on
SIOCGIWFREQ seems to fail with EINVAL (Invalid argument):
:~$ strace iwconfig ath0
...
ioctl(3, SIOCGIWFREQ, 0xbfc8f41c) = -1 EINVAL (Invalid argument)
...
I also have a a USB wireless stick (based on AR9271, using module ath9k_htc) at
hand, also working fine in same setup, but no chance to read SIOCGIWFREQ.
Why could this be? Has anything changed in the atheros wireless section
regarding this?
Thanks in advance,
Rolf Anderegg
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
