From: "Leo L. Schwab" <ewhac@ewhac.org>
To: linux-wireless@vger.kernel.org
Subject: compat-wireless-2.6-old: Can't Load Modules
Date: Tue, 7 Oct 2008 14:30:21 -0700 [thread overview]
Message-ID: <20081007213021.GA13525@best.com> (raw)
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
reply other threads:[~2008-10-07 21:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081007213021.GA13525@best.com \
--to=ewhac@ewhac.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).