On Mon, Oct 13, 2008 at 4:24 PM, John W. Linville<linville@xxxxxxxxxxxxx> wrote:> On Tue, Oct 14, 2008 at 01:02:02AM +0200, J.A. Magallón wrote:>>> werewolf:~# modprobe ath5k>> WARNING: Error inserting cfg80211 (/lib/modules/2.6.27-jam03/kernel/net/wireless/cfg80211.ko): Unknown symbol in module, or unknown parameter (see dmesg)>> WARNING: Error inserting mac80211 (/lib/modules/2.6.27-jam03/kernel/net/mac80211/mac80211.ko): Unknown symbol in module, or unknown parameter (see dmesg)>> FATAL: Error inserting ath5k (/lib/modules/2.6.27-jam03/kernel/drivers/net/wireless/ath5k/ath5k.ko): Unknown symbol in module, or unknown parameter (see dmesg)>> werewolf:~# modprobe mac80211>> WARNING: Error inserting cfg80211 (/lib/modules/2.6.27-jam03/kernel/net/wireless/cfg80211.ko): Unknown symbol in module, or unknown parameter (see dmesg)>> FATAL: Error inserting mac80211 (/lib/modules/2.6.27-jam03/kernel/net/mac80211/mac80211.ko): Unknown symbol in module, or unknown parameter (see dmesg)>>>> Dmesg is below.>> cfg80211 isn't loading, so mac80211 can't find it's symbols, and> ath5k can't find mac80211's symbols. What symbols? sudo rmmod ath5ksudo dmesg -c > /dev/nullsudo modprobe ath5ksudo dmesg -c >> cfg80211: Unknown parameter `ieee80211_regdom' Ahh this one.. this is the 2 character module parameter you can passto cfg80211 upon load and this is available only whenCONFIG_WIRELESS_OLD_REGULATORY is enabled. I still don't see why you are seeing this, as your modprobe commanddid not pass any module parameter options.. do you have some optionsfor cfg8021 in your distribution place for them on /etc/ somewhere? > config WIRELESS_OLD_REGULATORY> bool "Old wireless static regulatory definitions"> default n> ---help---> This option enables the old static regulatory information> and uses it within the new framework. This is available> temporarily as an option to help prevent immediate issues> due to the switch to the new regulatory framework which> does require a new userspace application which has the> database of regulatory information (CRDA) and another for> setting regulatory domains (iw).>> For more information see:>> http://wireless.kernel.org/en/developers/Regulatory/CRDA> http://wireless.kernel.org/en/users/Documentation/iw>> It is important to note though that if you *do* have CRDA present> and if this option is enabled CRDA *will* be called to update the> regulatory domain (for US and JP only). Support for letting the user> set the regulatory domain through iw is also supported. This option> mainly exists to leave around for a kernel release some old static> regulatory domains that were defined and to keep around the old> ieee80211_regdom module parameter. This is being phased out and you> should stop using them ASAP.>> Say N unless you cannot install a new userspace application> or have one currently depending on the ieee80211_regdom module> parameter and cannot port it to use the new userspace interfaces.>> This is scheduled for removal for 2.6.29.>> Is this not clear enough? I am in hopes distributions can start packaging iw and crda soonerrather than later, if not we will have to consider pushing the removalof this option for until 2.6.30 and also set it to default in 2.6.28(?). I'd hate to see this but I guess this is reasonable since noteven NM is yet asking yet cfg80211 to set the regulatory domain to aspecific country. Luis��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
