From: Larry Finger <Larry.Finger@lwfinger.net>
To: Xavier de Almeida <xavierdealmeida@yahoo.fr>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Tr : Tr : Can't make RTL8188CE work with hostapd (rtl8192ce)
Date: Fri, 27 Jul 2012 06:51:27 -0500 [thread overview]
Message-ID: <501280BF.4070409@lwfinger.net> (raw)
In-Reply-To: <1343370892.97699.YahooMailNeo@web28904.mail.ir2.yahoo.com>
On 07/27/2012 01:34 AM, Xavier de Almeida wrote:
> Hi Larry,
>
> I am using hostapd v0.7.3 but I did not install the bleeding-edge compat-wireless drivers.
>
> What I noticed is that your script refers to module se while I have a ce. (I am not sure if this can impact or explain the differences between your setup and mine).
>
> When I download the drivers from http://wireless.kernel.org/en/users/Download#Where_to_download_bleeding_edge, I got this file "compat-wireless-2.6.tar.bz2" which contains maybe a too old version compat-wireless-2012-05-10.
>
> Should I install this version?
> If I install kernel 3.5.0, will I still need to install the compat-wireless drivers?
The SE was in the ESSID. Do you think that matters?? The chip I used was an
RTL8188CE, the same as yours.
You need to install the bleeding-edge compat wireless from
http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2.
That sounds like the version you got.
Installing kernel 3.5 0 will get older drivers than compat-wireless. That is the
way that kernel development works. The ones in 3.5.0 should be OK, but
installing compat would be easier than generating a 3.5 kernel.
Larry
next prev parent reply other threads:[~2012-07-27 11:51 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKjQTCesBzbjbv4T+RPRutrgTyJoXJciwsKqPAxZDDcvot=q5g@mail.gmail.com>
[not found] ` <CAKjQTCex5oXLkPOZeoccT5a0CxMDpdpmSqcJy4SV7h1eaeo=pA@mail.gmail.com>
[not found] ` <1343074978.66314.YahooMailNeo@web28904.mail.ir2.yahoo.com>
2012-07-23 20:31 ` Can't make RTL8188CE work with hostapd (rtl8192ce) Xavier de Almeida
2012-07-23 21:07 ` Larry Finger
[not found] ` <1343138030.94415.YahooMailNeo@web28906.mail.ir2.yahoo.com>
2012-07-24 13:56 ` Tr : " Xavier de Almeida
2012-07-24 15:06 ` Larry Finger
2012-07-24 15:25 ` Xavier de Almeida
2012-07-24 15:46 ` Larry Finger
2012-07-24 17:06 ` Tr : " Xavier de Almeida
2012-07-24 17:51 ` Larry Finger
2012-07-25 13:54 ` Xavier de Almeida
2012-07-25 17:19 ` Xavier de Almeida
2012-07-25 17:25 ` Xavier de Almeida
2012-07-25 17:43 ` Larry Finger
2012-07-26 9:58 ` Xavier de Almeida
2012-07-26 10:53 ` Larry Finger
2012-07-26 11:01 ` Xavier de Almeida
2012-07-26 11:28 ` Larry Finger
2012-07-26 12:44 ` Xavier de Almeida
2012-07-26 14:49 ` Xavier de Almeida
2012-07-26 21:52 ` Larry Finger
2012-07-27 6:34 ` Xavier de Almeida
2012-07-27 11:51 ` Larry Finger [this message]
2012-07-27 13:09 ` Xavier de Almeida
2012-07-27 14:12 ` Xavier de Almeida
2012-07-27 15:38 ` Xavier de Almeida
2012-07-27 15:59 ` Xavier de Almeida
2012-07-27 16:38 ` Xavier de Almeida
2012-07-28 15:25 ` Larry Finger
2012-07-29 19:57 ` Xavier de Almeida
2012-07-29 20:53 ` Larry Finger
2012-07-30 18:06 ` Xavier de Almeida
2012-07-30 19:51 ` Larry Finger
2012-07-30 20:03 ` Xavier de Almeida
2012-07-30 20:17 ` Xavier de Almeida
2012-07-30 21:27 ` Larry Finger
2012-07-30 21:31 ` Larry Finger
2012-07-27 8:14 ` Xavier de Almeida
2012-07-27 10:32 ` Xavier de Almeida
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=501280BF.4070409@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=xavierdealmeida@yahoo.fr \
/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).