Atheros driver under x86_64 not working.
Hi all, I'm having an issue with SuSE 9.3, 10beta1, 10beta2, and 10beta3. I'm running an AMD 64 3000 processor with the D-Link DWL-G520 PCI wireless G network card. SuSE9.3 sort of gets the card working every other installation with the native drivers, but I cannot shut down the interface without it freezing my computer. I believe this is a known issue that has been fixed, but in the 10 x86_64 betas, I cannot get the ath_pci module to load. The system says there are unknown symbols in the module. To fix this I've tried downloading the latest madwifi cvs and, using the SuSEbuild script from the madwifi help wiki, I've been able to compile the new driver. When I load this new module, dmesg tells me that WEP AES AES-CCMP and TKIP are enabled. WPA_Supplicant doesn't work with the module, but I can scan for Access Points and find them with the new driver. Am I missing something in getting WPA_Supplicant to work with the new driver? The errors from WPA_supplicant indicate that it is failing trying to implement an ioctrl operation on the ath_pci driver. I haven't recompiled wpa_supplicant from source yet. I'm using the rpm from the 10beta3 cd at the moment. So my question is, am I going in the right direction to try to recompile the wpa_supplicant from source? Or is there something missing when I'm compling the new madwifi driver? Thanks in advance for any responses. Richard Lemon LAN Administrator Maricopa County Attorney OFC: 602-506-0929 CEL: 602-763-9282 FAX: 602-594-7395
Hi, On Mon, 29 Aug 2005, Lemon Richard wrote:
I'm having an issue with SuSE 9.3, 10beta1, 10beta2, and 10beta3. I'm running an AMD 64 3000 processor with the D-Link DWL-G520 PCI wireless G network card. SuSE9.3 sort of gets the card working every other installation with the native drivers, but I cannot shut down the interface without it freezing my computer. I believe this is a known issue that has been fixed, but in the 10 x86_64 betas, I cannot get the ath_pci module to load. The system says there are unknown symbols in the module.
You need http://ftp4.gwdg.de/pub/suse/i386/10.0/SUSE-Linux10.0-Beta3-Extra/kernel-mod... against the unknown symbols. The ath_pci driver has "closed source" parts.
To fix this I've tried downloading the latest madwifi cvs and, using the SuSEbuild script from the madwifi help wiki, I've been able to compile the new driver. When I load this new module, dmesg tells me that WEP AES AES-CCMP and TKIP are enabled. WPA_Supplicant doesn't work with the module, but I can scan for Access Points and find them with the new driver.
Am I missing something in getting WPA_Supplicant to work with the new driver? The errors from WPA_supplicant indicate that it is failing trying to implement an ioctrl operation on the ath_pci driver. I haven't recompiled wpa_supplicant from source yet. I'm using the rpm from the 10beta3 cd at the moment.
So my question is, am I going in the right direction to try to recompile the wpa_supplicant from source? Or is there something missing when I'm compling the new madwifi driver?
My personal impression is: wpa_supplicant ist not very reliable. So I don't use it at the moment. Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
Eberhard Moenkeberg <emoenke@gwdg.de> writes:
My personal impression is: wpa_supplicant ist not very reliable. So I don't use it at the moment.
Please test beta4 again, it will contain an updated wpa_supplicant. If this is not reliable, please file a bugreport, Andreas - currently using the new wpa_supplicant to test it for beta4;-) -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Mon, 2005-08-29 at 21:44 +0200, Andreas Jaeger wrote:
Eberhard Moenkeberg <emoenke@gwdg.de> writes:
My personal impression is: wpa_supplicant ist not very reliable. So I don't use it at the moment.
Please test beta4 again, it will contain an updated wpa_supplicant. If this is not reliable, please file a bugreport,
Andreas - currently using the new wpa_supplicant to test it for beta4;-)
Excellent. I've tried both the RPM Eberhard suggested and compiling from CVS from the madwifi sourceforge site. Both get the card working fine except for WPA. I was starting to think it was the wpa_supplicant. I'll definitely try it when beta 4 is released and let you know the results.
Richard Lemon <lemonr@mcao.maricopa.gov> writes:
On Mon, 2005-08-29 at 21:44 +0200, Andreas Jaeger wrote:
Eberhard Moenkeberg <emoenke@gwdg.de> writes:
My personal impression is: wpa_supplicant ist not very reliable. So I don't use it at the moment.
Please test beta4 again, it will contain an updated wpa_supplicant. If this is not reliable, please file a bugreport,
Andreas - currently using the new wpa_supplicant to test it for beta4;-)
Excellent. I've tried both the RPM Eberhard suggested and compiling from CVS from the madwifi sourceforge site. Both get the card working fine except for WPA. I was starting to think it was the wpa_supplicant. I'll definitely try it when beta 4 is released and let you know the results.
please file a bug report in bugzilla if it does not work with beta4, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (4)
-
Andreas Jaeger -
Eberhard Moenkeberg -
Lemon Richard -
Richard Lemon