> I realised that the madwifi-driver package is masked and that this > indicates that I may experience problems, but I suspect I'm more > problems than others - considering that loads of people appear to have > the madwifi drivers working with other distributions. I've hunted on the > web for definitive information about the madwifi-driver and while I can > find a fair bit of information I can't find a specific gentoo sample > configuration against which I can compare mine - nor can I find people > reporting the same fault. > > So far I've used emerge to merge the madwifi-driver > (madwifi-driver-0.1_pre20050224) which went without a glitch. I then > added a few lines (details below - which I assumed appropriate from a > weblog-style "howto") to my /etc/modules.autoload.d/kernel-2.6 (I am > using the 2.6 "development" kernel): > > -- > ath_hal > ath_rate_amrr > ath_rate_onoe > ath_pci > wlan > wlan_acl > wlan_ccmp > wlan_tkip > wlan_wep > wlan_xauth > -- > > When I reboot I get as far as probing modules then see a load of errors... > > -- > ath_hal: module license 'Proprietary' taints kernel. > ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) > wlan: Unknown symbol wireless_send_event > ath_rate_amrr: Unknown symbol ether_sprintf > ath_rate_amrr: Unknown symbol ieee80211_iterate_nodes > wlan: Unknown symbol wireless_send_event > ath_rate_onoe: Unknown symbol ether_sprintf > ath_rate_onoe: Unknown symbol ieee80211_iterate_nodes > wlan: Unknown symbol wireless_send_event > ath_rate_onoe: Unknown symbol ether_sprintf > ath_rate_onoe: Unknown symbol ieee80211_iterate_nodes > ath_pci: Unknown symbol ath_rate_tx_complete > ath_pci: Unknown symbol ieee80211_encap > ath_pci: Unknown symbol ieee80211_input > ath_pci: Unknown symbol ieee80211_ifattach > ath_pci: Unknown symbol ieee80211_sysctl_register > ath_pci: Unknown symbol ieee80211_beacon_update > ath_pci: Unknown symbol ath_rate_attach > ath_pci: Unknown symbol ether_sprintf > ath_pci: Unknown symbol ieee80211_ifdetach > ath_pci: Unknown symbol ieee80211_free_node > ath_pci: Unknown symbol ath_rate_newassoc > ath_pci: Unknown symbol ieee80211_notify_michael_failure > ath_pci: Unknown symbol ieee80211_dump_pkt > ath_pci: Unknown symbol ath_rate_node_copy > ath_pci: Unknown symbol ieee80211_media_change > ath_pci: Unknown symbol ieee80211_beacon_alloc > ath_pci: Unknown symbol ieee80211_find_node > ath_pci: Unknown symbol ieee80211_mhz2ieee > ath_pci: Unknown symbol ath_rate_node_cleanup > ath_pci: Unknown symbol ath_rate_detach > ath_pci: Unknown symbol ieee80211_next_scan > ath_pci: Unknown symbol ieee80211_media_init > ath_pci: Unknown symbol ieee80211_ioctl > ath_pci: Unknown symbol ieee80211_media_status > ath_pci: Unknown symbol ieee80211_announce > ath_pci: Unknown symbol ieee80211_chan2ieee > ath_pci: Unknown symbol ieee80211_state_name > ath_pci: Unknown symbol ath_rate_node_init > ath_pci: Unknown symbol ath_rate_findrate > ath_pci: Unknown symbol ieee80211_crypto_encap > ath_pci: Unknown symbol ieee80211_chan2mode > ath_pci: Unknown symbol ieee80211_getrssi > ath_pci: Unknown symbol ath_rate_newstate > ath_pci: Unknown symbol ath_rate_setupxtxdesc > wlan: Unknown symbol wireless_send_event > wlan: Unknown symbol wireless_send_event > wlan_acl: Unknown symbol ieee80211_aclator_unregister > ath_pci: Unknown symbol ath_rate_node_cleanup > ath_pci: Unknown symbol ath_rate_detach > ath_pci: Unknown symbol ieee80211_next_scan > ath_pci: Unknown symbol ieee80211_media_init > ath_pci: Unknown symbol ieee80211_ioctl > ath_pci: Unknown symbol ieee80211_media_status > ath_pci: Unknown symbol ieee80211_announce > ath_pci: Unknown symbol ieee80211_chan2ieee > ath_pci: Unknown symbol ieee80211_state_name > ath_pci: Unknown symbol ath_rate_node_init > ath_pci: Unknown symbol ath_rate_findrate > ath_pci: Unknown symbol ieee80211_crypto_encap > ath_pci: Unknown symbol ieee80211_chan2mode > ath_pci: Unknown symbol ieee80211_getrssi > ath_pci: Unknown symbol ath_rate_newstate > ath_pci: Unknown symbol ath_rate_setupxtxdesc > wlan: Unknown symbol wireless_send_event > wlan: Unknown symbol wireless_send_event > wlan_acl: Unknown symbol ieee80211_aclator_unregister > wlan_acl: Unknown symbol ether_sprintf > wlan_acl: Unknown symbol ieee80211_aclator_register > wlan: Unknown symbol wireless_send_event > wlan_ccmp: Unknown symbol ether_sprintf > wlan_ccmp: Unknown symbol ieee80211_crypto_unregister > wlan_ccmp: Unknown symbol ieee80211_notify_replay_failure > wlan_ccmp: Unknown symbol ieee80211_crypto_register > wlan: Unknown symbol wireless_send_event > wlan_tkip: Unknown symbol ether_sprintf > wlan_tkip: Unknown symbol ieee80211_notify_michael_failure > wlan_tkip: Unknown symbol ieee80211_crypto_unregister > wlan_tkip: Unknown symbol ieee80211_notify_replay_failure > wlan_tkip: Unknown symbol ieee80211_crypto_register > wlan: Unknown symbol wireless_send_event > wlan_wep: Unknown symbol ether_sprintf > wlan_wep: Unknown symbol rc4_init > wlan_wep: Unknown symbol ieee80211_crypto_unregister > wlan_wep: Unknown symbol rc4_crypt_skip > wlan_wep: Unknown symbol ieee80211_crypto_register > wlan: Unknown symbol wireless_send_event > wlan_xauth: Unknown symbol ieee80211_authenticator_unregister > wlan_xauth: Unknown symbol ieee80211_authenticator_register > -- > > Noting that the first error is generated by the wlan module, following a > session with Google I suspected that my kernel needed wireless network > support... I used menuconfig and made these selections: > > -- > │ [*] Wan interfaces support > │ < > Comtrol Hostess SV-11 support > │ < > COSA/SRP sync serial boards support > │ < > Etinc PCISYNC serial board support > │ < > LanMedia Corp. SSI/V.35, T1/E1, HSSI, T3 boards > │ < > Sealevel Systems 4021 support > │ < > SyncLink HDLC/SYNCPPP support > │ < > Generic HDLC layer > │ < > Frame Relay DLCI support > │ < > Granch SBNI12 Leased Line adapter support > -- > > Can anyone tell me if they've got the madwifi-drivers working under > Gentoo (with a 2.6 kernel)? If so - where do our approaches differ? What > kernel options are actually required? Do I really need all the modules > I've got in my autoloading (I don't care about security - the only > service I'll expose over this interface will be SSH - the same one as I > expose to the internet at large)?
I've been fighting with the madwifi-driver for so long but as of night before last it is working perfectly via WPA. I use wpa_supplicant and I've read conflicting information that it can and can not be used to connect to an unsecured AP. It can definitely connect via WEP or WPA though. The only module you need to autoload is ath_pci. The kernel option you must be missing is: Device Drivers -> Networking support -> Wireless LAN -> Wireless LAN drivers There is probably another one if your wireless card is PCMCIA. You don't need the WAN support. - Grant -- gentoo-user@gentoo.org mailing list
