Steve ([EMAIL PROTECTED]) scribbled: > 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 > --
The relevant portion of my '/etc/modules.autoload.d/kernel-2.6': wlan ath_hal ath_pci everything else autoloads from these three. > > When I reboot I get as far as probing modules then see a load of errors... [snip error msgs] What are CONFIG_NET_WIRELESS and CONFIG_NET_RADIO set to in your kernel config? Cooper. -- gentoo-user@gentoo.org mailing list
