Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Ticket #2359 (new defect)

Opened 12 years ago

Last modified 12 years ago

madwifi trunk is not working on AR71xx

Reported by: nenad@panline.net Assigned to:
Priority: critical Milestone:
Component: madwifi: driver Version: trunk
Keywords: Cc:
Patch is attached: 0 Pending: 0

Description

I've been trying to use madwifi-trunk (r4099) on Ubiquiti routerstation board - Atheros AR7161 rev 2 CPU, but with no success. After creating ath0 interface, all I could get is

wifi0: ath_fatal_tasklet: Hardware error; resetting.
wifi0: ath_fatal_tasklet: Hardware error; resetting.
...
wifi0: ath_fatal_tasklet: Hardware error; resetting.

until interface is shutted down.

Change History

(in reply to: ↑ description ) 02/17/10 06:47:26 changed by vishal.sevani@gmail.com

Replying to nenad@panline.net:

I've been trying to use madwifi-trunk (r4099) on Ubiquiti routerstation board - Atheros AR7161 rev 2 CPU, but with no success. After creating ath0 interface, all I could get is {{{ wifi0: ath_fatal_tasklet: Hardware error; resetting. wifi0: ath_fatal_tasklet: Hardware error; resetting. ... wifi0: ath_fatal_tasklet: Hardware error; resetting. }}} until interface is shutted down.

Iam getting the same problem. The hardware and software configuration that Iam employing is miniPCI Ubiquiti SR2 cards based on AR5212 chipset on Mikrotik RB433AH boards. The OS that Iam using is Openwrt kamikaze v8.09 with linux kernel 2.6.26.5 and I have tried with madwifi_0.9.4r3980 till madwifi_0.9.4r4119. I have tested it in adhoc as well as monitor mode, but as soon as the modules load the following error keeps appearing

wifi0: ath_fatal_tasklet: Hardware error; resetting.

(follow-up: ↓ 3 ) 02/20/10 00:19:24 changed by proski

The same error message is reported in #2322.

(in reply to: ↑ 2 ) 02/20/10 00:36:53 changed by nenad@panline.net

Replying to proski:

The same error message is reported in #2322.

#2322 is dealing with some kind of AP related problem; problem described in this ticket arises on AR71xx CPU platform (probably caused by AR71xx chipset DMA transfer hardware bug when operating with 802.11a/b/g Atheros wireless), no matter what operating mode is selected (AP or STA). Same driver (r4099 in my case) works fine on x86.