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 #1502 (new defect)

Opened 14 years ago

Last modified 14 years ago

Madwifi not working with kernels since 2.6.19 with Netgear WG511T (AR5212)

Reported by: richard.ketchersid@gmail.com Assigned to:
Priority: minor Milestone:
Component: madwifi: other Version: trunk
Keywords: Cc:
Patch is attached: 0 Pending:

Description

I have compiled kernels 2.6.19,20,21, and 22 and tried them with both the latest svn sources and 0.9.3. In all cases everything compiles, all the modules load, the card seems to connect to the router but there seems to be no communication between router and card.

There is nothing in the log file that gives a clue to what is going on. Everything works fine with 2.6.18 and madwifi-0.9.3 and the log files look essentially the same with that combination and with all the later ones. I have attached parts of the log file.

Attachments

wifi.log (20.1 kB) - added by anonymous on 08/10/07 06:12:59.

Change History

08/10/07 06:12:59 changed by anonymous

  • attachment wifi.log added.

08/10/07 07:43:37 changed by mrenzmann

Quoting from the attachment:

With kernel-2.6.18 and Madwifi 0.9.3 ... Jul 21 18:09:51 firewall kernel: ath_pci: 0.9.4.5 (svn r1691)

That's not 0.9.3, but rather something between 0.9.2 and 0.9.3.

Anyway, since you switched from an old to a new version of the driver along with changing the kernel revision, this opens a few other possibilities as cause for what you experience.

After configuring ath0 and before running dhclient, you should check that your card gets a valid association. Look at iwconfig ath0 (you might need to run that several times as the card needs a while to scan for APs) and see whether you get something in the Access-Point field. Also check that the card sees the Access Point and has it listed in the output of iwlist ath0 scan.

08/11/07 10:19:25 changed by richard.ketchersid@gmail.com

Here is the output of iwconfig with both combinations. There is no difference, but still in one case wireless works and in the other it does not (cant even ping the router - so it is not dns related).

Everything works with 2.6.18 + Madwifii-0.9.3 (ath_pci: 0.9.4.5 (svn r1691),ath_hal: 0.9.17.2):

Result of iwconfig:

ath0 IEEE 802.11g ESSID:"mdwong" Nickname:"firewall.localdomain"

Mode:Managed Frequency:2.462 GHz Access Point: 00:18:4D:57:54:AE Bit Rate:24 Mb/s Tx-Power:18 dBm Sensitivity=0/3 Retry:off RTS thr:off Fragment thr:off Encryption key:D567-6B6A-342E-2A83-A274-6BDE-E97E-F5AE Security mode:restricted Power Management:off Link Quality=26/94 Signal level=-69 dBm Noise level=-95 dBm Rx invalid nwid:93 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Everything looks like it works with Kernel-2.6.22 + Madwifi-0.9.4 (svn r2644), but it doesn't!:

ath0 IEEE 802.11g ESSID:"mdwong" Nickname:"firewall.localdomain"

Mode:Managed Frequency:2.462 GHz Access Point: 00:18:4D:57:54:AE Bit Rate:54 Mb/s Tx-Power:18 dBm Sensitivity=0/3 Retry:off RTS thr:off Fragment thr:off Encryption key:F98B-5067-7656-DE7F-F8E7-38DF-0570-7FCF Security mode:restricted Power Management:off Link Quality=56/94 Signal level=-33 dBm Noise level=-89 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0