rt73 driver makes madwifi (Atheros) drivers not work?

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=4571

pytheas22

17-01-2008 21:04:50

I'm having a strange problem where compiling the rt73 driver from serialmonkey and rebooting causes my madwifi driver (version 0.9.3.3), which I use for an Atheros PCI device that I have attached to my system in addition to my Ralink card, to do a weird thing the Atheros device will no longer work in 11g mode, only 11b, and consequently won't see or connect to my wlan.

I am not sure what the rt73 driver would have to do with the madwifi one. But I tried isolating other factors and it appears that the rt73 driver is what's triggering the problem with my Atheros card. Even on a clean system install, my Atheros card works fine in 11g mode until I compile, install and modprobe the CVS rt73 driver from serialmonkey, and then reboot (before rebooting, I also blacklist all of the mac80211 ralink drivers that ship with Ubuntu 7.10 Gusty, which don't work reliably). After reboot, my Atheros device can only be brought up in 11b mode. Removing the rt73 module or unplugging my Ralink device doesn't help, nor does reinserting the madwifi module or even recompiling it from source. And the command used to change the mode of Atheros cards--iwpriv ath0 mode 11g--doesn't do anything. This behavior has been reproduced twice with clean installs of Ubuntu.

I posted about this on the madwifi users' list and got no help, so I am hoping that someone here might have an idea of why the rt73 driver would be interfering with the function of my Atheros card. Is there some point at which they share configurations or something and the rt73 driver would be able to override settings needed by madwifi? Or anything else I could look for?

For what it's worth, I am using an Intel 64-bit architecture, and as I said, my OS is Ubuntu 7.10.

Thanks in advance for any help.

EDIT sorry for not checking this before, but maybe my problem is related to the one outlined here http//rt2x00.serialmonkey.com/phpBB2/v ... ht=atheros
That issue is more extreme--I can still bring up my Atheros interface without having a system freeze or anything, but I can't get it to work properly. And also, I just got my Atheros card, so I can't say whether rt73 and madwifi coexisted peacefully in the past or not.

impdonkey

19-01-2008 21:53:45



EDIT sorry for not checking this before, but maybe my problem is related to the one outlined here http//rt2x00.serialmonkey.com/phpBB2/v ... ht=atheros
That issue is more extreme--I can still bring up my Atheros interface without having a system freeze or anything, but I can't get it to work properly. And also, I just got my Atheros card, so I can't say whether rt73 and madwifi coexisted peacefully in the past or not.[/quote1p9f89js]

It seems reasonable to assume yours and my problems are related. I just wanted to add that, in my case, removing the rt73 module does not help either, as it doesn't help in your case. My madwifi freeze happens regardless... In both cases, madwifi initially works normally, and the skew happens only when the (legacy) rt73 driver is installed.

Also, please note that regarding the coexistence of my ath0 and rausb0, it depends which of the entirely different development threads of the drivers are loaded -- 1) the driver provided by ralinktech (http//www.ralinktech.com/ralink/Home/S ... Linux.html ), 2) the new rt2x00 driver, or 3) the legacy rt73 module.

The official ralinktech.com release did not seem to hamper my madwifi in anyway. The rt2x00 driver, may have actually hampered it somewhat -- now that I re-read my own earlier post and see that i reported problems with "ifconfig ath0 up" hanging at the command line -- but not to the point of freezing my entire system completely. Or that my have been due to having more than one ralink driver/module loaded simultaneously

Only the legacy rt73 CVS version, thus far, has produced my freezes.

(In terms of feature benefits, there are pros and cons for each version, and i found that, with the given tradeoffs, the rt73 legacy module is most ideal for my situation. Starcrasher and Spy84464 have spelled out the difference in this thread http//rt2x00.serialmonkey.com/phpBB2/v ... php?t=4530 )

I am hoping someone will inventory and identify everything that gets written and overwritten during the culprit installation. The fact that the effect persists without the rt73 being loaded is rather unusual.

impdonkey

23-01-2008 06:42:43

suggestion/offer to the developers

If you guys don't have any madwifi hardware for debugging, I can lend you a compatible card with an atheros chip (cardbus factor).

please send me a message with mailing directives.

the other option would be for you to log into a system remotely, except that the freezes might make it difficult.

thanks for your hard work

pytheas22

27-01-2008 18:42:20

ah, just checked back here for the first time in several days, to find your post. Thanks for the response, and glad to see that there is work being done on the issue in the thread you created.

I also thought it would be useful to add that the 2x00 drivers didn't seem to cause any problems for madwifi. I use Ubuntu 7.10, which ships with the 2x00 drivers by default, and it was only after blacklisting them and installing the legacy rt73 driver (and rebooting) that madwifi stopped working.

The 2x00 drivers do not work reliably for my DWL-G122 device--the interface crashes arbitrarily--so I really prefer the legacy drivers. I haven't tried the drivers from Ralink because I believe that they don't support 64-bit, which I use.