From: Larry Finger <Larry.Finger@lwfinger.net>
To: Colleen Josephson <cjoseph@mit.edu>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: issues with RTL8188CE device and rtl8192ce driver
Date: Mon, 12 Aug 2013 18:55:04 -0500 [thread overview]
Message-ID: <520975D8.8040908@lwfinger.net> (raw)
In-Reply-To: <CAN3-2D75TLTS-Fv3CgoBjA+RA3jv-QyLoSs+PZeKXLY_MUcSTQ@mail.gmail.com>
On 08/12/2013 06:44 PM, Colleen Josephson wrote:
>> If you install the baclports drivers, they will replace the standard ones.
>
> Even for drivers built into my kernel (not as modules?). Just making
> sure, as I seem to have encountered a problem:
>
> After installing the backports version of rtl8192ce and rebooting,
> wlan0 is not longer showing up when I run "ifconfig".
>
> lsmod shows compat and rtl8192c_common, but not rtl8192ce. If I try
> 'modprobe rtl8192ce' I get this error: "Unknown symbol in module, or
> unknown parameter (see dmesg)"
>
> dmesg shows "rtlwifi: Unknown symbol mac80211_ieee80211_rx (err 0)"
I'm not sure, but I would expect you need the standard ones to be modules. I
always build all wireless devices as modules. That way when one goes bad, you
have a chance to recover with an unload/load sequence with modprobe. If it
works, you save a reboot.
I am assuming that you built mac80211 from the backported source. That is required.
Larry
next prev parent reply other threads:[~2013-08-12 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 22:54 issues with RTL8188CE device and rtl8192ce driver Colleen Josephson
2013-08-12 22:58 ` Larry Finger
2013-08-12 23:27 ` Colleen Josephson
2013-08-12 23:37 ` Larry Finger
2013-08-12 23:44 ` Colleen Josephson
2013-08-12 23:55 ` Larry Finger [this message]
2013-08-13 0:08 ` Colleen Josephson
2013-08-14 3:04 ` Larry Finger
2013-08-14 21:39 ` Colleen Josephson
2013-08-27 23:09 ` Colleen Josephson
2013-08-27 23:17 ` Larry Finger
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=520975D8.8040908@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=cjoseph@mit.edu \
--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).