The current (though masked) madwifi-driver fails to setup the device properly: > iwconfig lo no wireless extensions. eth0 no wireless extensions. wifi0 no wireless extensions. Using either of the previous versions (0.1_pre20050420-r1 or 0.1_pre20051111), however, works flawlessly. Funny thing is, that the new madwifi-driver package tries to init a wifi0 device, while previous - and working - version initialize device ath0. I'm using a NETGEAR WG511T card (PCMCIA), wich is reported as: > lscpi 05:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
emerge --info, please...
wlanconfig needs to be run, to create ath0, in madwifi-ng - see http://forums.gentoo.org/viewtopic-t-408550.html
Sorry that I forgot the emerge info. The link to the Gentoo forum is very informative, albeit it referes to the older madwifi driver versions that I got running just fine. I'll try to follow all steps mentioned there and see if it makes a difference...
Created attachment 78074 [details] emerge info output
Incorrect configuration is not an ebuild bug. Please, read and follow the ebuild post-install instructions next time.
I agree that misconfiguration is not an ebuild bug. But in order to read ebuild post-install instructions, the ebuild better has any of these. > grep einfo madwifi-driver-0.1401.20060117.ebuild > einfo "Removing old ath_rate modules Not very talkative, or is it?
grep wlanconfig /usr/portage/net-wireless/madwifi-tools/madwifi-tools-0.1401.20060117.ebuild wlanconfig is now needed. I use it, it works. The ebuild that installs wlanconfig draws attention to it. Where's the bug?
The bug is that, as is correctly stated in the forum, one needs to manually patch the ebuild to reenable madwifi support. Otherwise, as happened to me, a simple upgrade breaks all wireless functionality for users that use Atheros chipset based WLAN cards. There's not even a user notification about that. Please also keep in mind, that I cannot know out of the blue that I now have to install wlanconfig, just to see it telling me that I indeed need to install it.
As already said once, kinda read the ebuild instructions: madwifi-tools-0.1401.20060117.ebuild <snip> pkg_postinst() { einfo einfo "Interfaces (athX) needs to be added using wlanconfig(8) after" einfo "loading madwifi-driver." einfo if use udev; then einfo "Example udev rules for automatically taking care of this has been" einfo "installed to:" einfo einfo " /etc/udev/rules.d/65-madwifi.rules" einfo einfo "Modify these rules to match your configuration and either run 'udevstart'" einfo "or reboot for the rules to take effect." einfo fi } </snip> CLOSED.
My apologies, wlanconfig comes bundled with madwifi-tools. What needs to be patched is wpa_supplicant. Still, I'm sure other folks will stumble as well, since the notification is rather short, and not as informative as it was in the previous version. I won't reopen this "bug", though. :)
(In reply to comment #10) This will work almost out-of-the-box for anyone on 2.6 kernels with udev. Since you are using 2.4 kernel, you don't have udev and will have to set it up manually.
