Ticket #238 (closed enhancement: fixed)

Opened 6 years ago

Last modified 6 years ago

(A) fix for ath0 No scan results

Reported by: sammelweis@gmail.com Assigned to: svens
Priority: major Milestone:
Component: madwifi: driver Version: trunk
Keywords: no scan results rfkill patch Cc:
Patch is attached: 1 Pending:

Description

My Atheros AR5004G (AR5213 chipset) wouldn't scan for networks successfully: 

iwlist ath0 scan:
ath0    No scan results

I searched the archives for this problem, it was mentioned quite often - sometimes with the AR5004G as well. I asked about my problem on the IRC channel, svens suggested me to try a patch he wrote (he used an AR5213 chipset as well) to disable rfkill in the module. So I tried this patch, and disabled rfkill, and now it works just fine. Since rfkill doesn't have to be disabled (it only is when you load the module with modprobe ath_pci rfkill=0) it might be a good idea to patch the module by default, it saves users a headache trying to find a fix.

Svens' patch:

http://svens.ath.cx/rfkill.diff

Sam

Change History

12/17/05 15:10:33 changed by svens

  • status changed from new to assigned.
  • owner set to svens.

I've ask madwifi-devel for comments: http://article.gmane.org/gmane.linux.drivers.madwifi.devel/1803. If nobody complains about side-effects in the next days, this feature will be added to madwifi-ng.

12/19/05 09:30:13 changed by mrenzmann

Since there was no other comment on your patch yet in madwifi-devel, feel free to commit your patch.

Side note: if we don't have yet, a wiki page detailing the meaning of the existing module parameters would be nice.

12/19/05 19:41:41 changed by svens

  • status changed from assigned to closed.
  • resolution set to fixed.

commited

02/01/06 11:41:47 changed by kelmo

  • patch_attached set to 1.