Public bug reported:

In Jaunty, up to and including 2.6.28-7, if the Wireless network
regulatory domain needed setting manually for non USA regions such as
the European Union (EU) or Japan, an option was added for the cfg80211
module in /etc/modprobe.d/options.conf:

 options cfg80211 ieee80211_regdom=EU

The kernel build config used:

 CONFIG_WIRELESS_OLD_REGULATORY=y

In Ubuntu-2.6.28-8.21 the wireless-crda package was introduced to work
with udev to set the regulatory domain automatically. Therefore the
manual override was no longer used and the kernel build config changed
to:

 # CONFIG_WIRELESS_OLD_REGULATORY is not set

However, if the manually added module option was left in place it causes
cfg80211 to fail to load, which in turn causes the wireless drivers to
fail to load too:

kernel: [  379.889060] cfg80211: Unknown parameter `ieee80211_regdom'

sudo modprobe iwl3945
WARNING: Error inserting led_class 
(/lib/modules/2.6.28-9-generic/kernel/drivers/leds/led-class.ko): Unknown 
symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting mac80211 
(/lib/modules/2.6.28-9-generic/kernel/net/mac80211/mac80211.ko): Unknown symbol 
in module, or unknown parameter (see dmesg)
FATAL: Error inserting iwl3945 
(/lib/modules/2.6.28-9-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko): 
Unknown symbol in module, or unknown parameter (see dmesg)

The solution is to remove the module option, e.g:

sudo sed -i '/options cfg80211/ s/^.*$//' /etc/modprobe.d/options.conf

** Affects: linux (Ubuntu)
     Importance: Low
         Status: Confirmed

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low
       Status: New => Confirmed

** Description changed:

  In Jaunty, up to and including 2.6.28-7, if the Wireless network
- regulatory domain needed setting manual (for non USA regions such as the
- European Union (EU) or Japan, an option was added for the cfg80211
- module:
+ regulatory domain needed setting manually for non USA regions such as
+ the European Union (EU) or Japan, an option was added for the cfg80211
+ module in /etc/modprobe.d/options.conf:
  
- /etc/modprobe.d/options.conf:
- 
- options cfg80211 ieee80211_regdom=EU
+  options cfg80211 ieee80211_regdom=EU
  
  The kernel build config used:
  
- CONFIG_WIRELESS_OLD_REGULATORY=y
+  CONFIG_WIRELESS_OLD_REGULATORY=y
  
  In Ubuntu-2.6.28-8.21 the wireless-crda package was introduced to work
  with udev to set the regulatory domain automatically. Therefore the
  manual override was no longer used and the kernel build config changed
  to:
  
- # CONFIG_WIRELESS_OLD_REGULATORY is not set
+  # CONFIG_WIRELESS_OLD_REGULATORY is not set
  
- However, if the manually added module option was left in place it caused
- cfg80211 to fail to load, which in turn caused the wireless drivers to
+ However, if the manually added module option was left in place it causes
+ cfg80211 to fail to load, which in turn causes the wireless drivers to
  fail to load too:
  
  kernel: [  379.889060] cfg80211: Unknown parameter `ieee80211_regdom'
  
  sudo modprobe iwl3945
  WARNING: Error inserting led_class 
(/lib/modules/2.6.28-9-generic/kernel/drivers/leds/led-class.ko): Unknown 
symbol in module, or unknown parameter (see dmesg)
  WARNING: Error inserting mac80211 
(/lib/modules/2.6.28-9-generic/kernel/net/mac80211/mac80211.ko): Unknown symbol 
in module, or unknown parameter (see dmesg)
  FATAL: Error inserting iwl3945 
(/lib/modules/2.6.28-9-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko): 
Unknown symbol in module, or unknown parameter (see dmesg)
  
- The solution is to remove the manual module option, e.g:
+ The solution is to remove the module option, e.g:
  
  sudo sed -i '/options cfg80211/ s/^.*$//' /etc/modprobe.d/options.conf

-- 
Wifi driver will fail to load if regulatory domain set in module options
https://bugs.launchpad.net/bugs/343026
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to