[Voyage-linux] hostapd & ath9k

[Frank Parker]

I would prefer to use madwifi (I think) if possible.  My concern is
that the wifi card wont even go into Master mode with the ath9k
driver:

# iwconfig wlan0 mode Master
Error for wireless request "Set Mode" (8B06) :
    SET failed on device wlan0 ; Invalid argument.


Madwifi seems to be installed in voyage-0.6.5.  I didnt install it,
but it's there.

# apt-cache search madwifi
madwifi-tools - tools for the Multiband Atheros Driver for WiFi
madwifi-modules-2.6.30-voyage - modules for the Multiband Atheros
Driver for WiFi (kernel 2.6.30-voyage)
hostapd - user space IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator

# apt-get install madwifi-modules-2.6.30-voyage
Reading package lists... Done
Building dependency tree
Reading state information... Done
madwifi-modules-2.6.30-voyage is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.


How do I know if it supports my specific wireless card?  This wireless
card doesn't have the usual model number that I see in other examples.
 It just says "Atheros Communications Inc. Device 002b (rev 01)" :

voyage:/lib/modules/2.6.30-voyage/kernel# lspci -vv -s 0:6:0.0
06:00.0 Network controller: Atheros Communications Inc. Device 002b (rev 01)
	Subsystem: Foxconn International, Inc. Device e023
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 18
	Region 0: Memory at febf0000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
		Address: 00000000  Data: 0000
	Capabilities: [60] Express (v2) Legacy Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0
<512ns, L1 <64us
			ClockPM- Suprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive-
BWMgmt- ABWMgmt-
	Capabilities: [100] Advanced Error Reporting <?>
	Capabilities: [140] Virtual Channel <?>
	Capabilities: [160] Device Serial Number 12-14-24-ff-ff-17-15-00
	Capabilities: [170] Power Budgeting <?>
	Kernel driver in use: ath9k
	Kernel modules: ath9k


Assuming it's supported, can you tell me how you configured this?




On Mon, Feb 22, 2010 at 3:43 PM, Gustin Johnson <gustin at echostar.ca> wrote:
> The ath0 interface is what one would expect when using the madwifi
> drivers.  You are using the ath9k driver.  I have no experience with it
> so I cannot really provide guidance here.  I have set up APs and routers
> using the madwifi drivers and hostapd, I have not tried with the ath9k
> drivers.