2008-10-07 21:37:09

by Leo L. Schwab

[permalink] [raw]
Subject: compat-wireless-2.6-old: Can't Load Modules

When I tried the latest (last night's) version of
compat-wireless-2.6-old on my 2.6.26 Debian laptop, I got the following
error messages when I tried to 'modprobe iwl3945":

Oct 7 02:20:14 walkies kernel: cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)

Once that happened, there were a series of cascading failures:

Oct 7 02:20:14 walkies kernel: mac80211: Unknown symbol wiphy_register
Oct 7 02:20:14 walkies kernel: mac80211: Unknown symbol wiphy_new
Oct 7 02:20:14 walkies kernel: mac80211: Unknown symbol wiphy_unregister
Oct 7 02:20:14 walkies kernel: mac80211: Unknown symbol ieee80211_radiotap_iterator_init
Oct 7 02:20:14 walkies kernel: mac80211: Unknown symbol __ieee80211_get_channel
Oct 7 02:20:14 walkies kernel: mac80211: Unknown symbol ieee80211_radiotap_iterator_next
Oct 7 02:20:14 walkies kernel: mac80211: Unknown symbol ieee80211_channel_to_frequency
Oct 7 02:20:14 walkies kernel: mac80211: Unknown symbol ieee80211_frequency_to_channel
Oct 7 02:20:14 walkies kernel: mac80211: Unknown symbol wiphy_free
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_free_hw
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_alloc_hw
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_notify_mac
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_register_hw
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_rate_control_unregister
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol __ieee80211_get_radio_led_name
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_wake_queue
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol __ieee80211_get_tx_led_name
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_tx_status_irqsafe
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol __ieee80211_get_rx_led_name
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_wake_queues
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_rate_control_register
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol sta_info_get
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_stop_queue
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_stop_queues
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol __ieee80211_get_assoc_led_name
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_scan_completed
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_channel_to_frequency
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_unregister_hw
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_hdrlen
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_beacon_get
Oct 7 02:20:14 walkies kernel: iwl3945: Unknown symbol ieee80211_rx_irqsafe

It seems this isn't a new problem, and was pointed out nearly two
months ago:

http://article.gmane.org/gmane.linux.kernel.wireless.general/19530/

I have CONFIG_RFKILL=m in my .config, and the module is loaded.
This potential conflict is not mentioned in the README. Should I alter my
kernel .config to avoid the collision, unload rfkill, or is there a magic
incantation in compat-wireless to avoid the problem?

Thanks,
Schwab