As per the wpa_supplicant README, at some point you must copy the .config from your live /usr/src/linux folder into the source tree of wpa_supplicant, then make some changes so that wpa_supplicant will recognize and compile certain most support into the module. If you try to modify the one directly from /usr/src/linux then it won't compile the necessary modules because the instructions on the wpa_supplicant site says we have to copy then modify the .config inside the wpa_supplicant source folder -- modifications depend on which method of wireless driver a person is using. There is one method of configuring wpa_supplicant with ndiswrapper and a completely different method for madwifi. It should be specified how to do this. The method as it is written right now (see URL), does not work out-of-box. I have one of the most used chipsets with Linux support (Atheros), Mad-wifi-ng detects and starts my card, but its useless without WPA. wpa_supplicant simply does not know that I have madwifi without adding the following to the .config: CONFIG_DRIVER_MADWIFI=y CFLAGS += -I/usr/src/madwifi-ng CONFIG_CTRL_IFACE=y But you cannot modify the live /usr/src/linux.config file or emerge will break, so where do I copy the file so emerge will see it? Thanks. Jeff Singleton Atlanta, GA Reproducible: Always Steps to Reproduce: 1.see description 2. 3. Actual Results: wpa_supplicant emerges with NO support for any card. Expected Results: The wpa_supplicant emerge process should involve the steps provided by the developer's documentation and then compile the configured module support. It should be documented so that the noobs know what is going on.
If wpa_supplicant really requires such treating, then it's up to its maintainers to fix/document/ask us to document/... it. I use wpa_supplicant and never had to mess with kernel config for it, sorry.
If you have some problems, then post actual emerge errors, emerge --info output, wpa_supplicant version and reopen then. The above is simply not true at all.
Jan Kundrát That us just what I did. I e-mail Sven who was listed as the Author for the Gentoo handbook page that I put in the URL above. His reply was: "Can you please direct your questions or bugreports to http://bugs.gentoo.org? I'm no longer maintaining any gentoo documentation (I'm no longer a Gentoo developer); the Gentoo Documentation Project should be able to help you out on this issue." So I opened a bug.
Jakub Moc I guess you haven't read the README from the wpa_supplicant site. Because it is clear as day, saying that you have to modify the .config and add some CONFIG support for the method you are trying to use (ndiswrapper or madwifi). Out of box, simply emerging wpa_supplicant does not include the required module support for madwifi or ndiswrapper. From what I can tell, there are some USE flags that could be used, but there is no mention of this in the Handbook. This bug is not to report an error in the emerge ... its a bug to request a documentation update. It is definitely incomplete.
What doesn't work for you? Enable USE=madwifi if you want madwifi support, there's no need to copy kernel .config anywhere nor to mess with CFLAGS. ndiswrapper support is *always* enabled, no need to do anything.
(In reply to comment #4) > I guess you haven't read the README from the wpa_supplicant site. Because it is > clear as day, saying that you have to modify the .config and add some CONFIG > support for the method you are trying to use (ndiswrapper or madwifi). You don't compile wpa_suplicant by hand, so you don't read its README. You install it using Portage and wpa_supplicant's ebuild provided by Gentoo handles all dirty crap. If it doesn't, you're encouraged to file a bug against the wpa_supplicant's ebuild. There's nothing wrong with Gentoo documentation in this matter.
So point me to where the documentation explains how to enable or disable certain features that may be required for it to work. Nowhere in that documentation does it say anything about USE flags. Of which ARE required if one wants to add madwifi or ndiswrapper support into the wpa_supplicant module. It's not ok the way it is...if it was then it would have worked for me as well. Out-of-Box wpa_supplicant does not compile madwifi or ndiswrapper support, even if they are already installed. Sorry, but it does not work without enabling the madwifi or wext USE flags for wpa_supplicant. And for some, not knowing where to look for this information would end up lost because it isn't written where it should be. Some things should not be assumed. ---- I'm starting to understand why the Gentoo community has so many quarrels. Nobody wants to help anyone anymore, they are all in it for themselves.
(In reply to comment #7) > So point me to where the documentation explains how to enable or disable > certain features that may be required for it to work. > > Nowhere in that documentation does it say anything about USE flags. Of which > ARE required if one wants to add madwifi or ndiswrapper support into the > wpa_supplicant module. Please kindly read http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=2 . > Out-of-Box wpa_supplicant does not compile madwifi or ndiswrapper support, even > if they are already installed. Sorry, but it does not work without enabling the > madwifi or wext USE flags for wpa_supplicant. This is not a bug, but a feature. If you don't want to make use of USE flags, perhaps you should consider trying any other distribution. Seriously, complaining about USE flags is like complaining that "compilation of OpenOffice takes ages". > And for some, not knowing where to look for this information would end up lost > because it isn't written where it should be. Some things should not be assumed. We assume our users read the Handbook. This assumption is not going to change. > I'm starting to understand why the Gentoo community has so many quarrels. > Nobody wants to help anyone anymore, they are all in it for themselves. Two Gentoo developers has already lost at least 30 minutes of their precious time dealing with this report. This is half an hour that could have been spent working (=making money), studying (=getting qualification for earning more money) or just being with their family. You're really showing a great deal of grattitude to those people. Thanks :(.
