From: Larry Finger <Larry.Finger@lwfinger.net>
To: kc@cobradevil.org
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: rtl8192cu sometimes it can authenticate to ap
Date: Thu, 11 Aug 2011 09:37:04 -0500 [thread overview]
Message-ID: <4E43E910.7090001@lwfinger.net> (raw)
In-Reply-To: <30cc9c22bb40fb1e2bd2b9ef4692d167@cobradevil.org>
On 08/11/2011 09:23 AM, kc@cobradevil.org wrote:
> I have now tried several compat files til may 28 but none of them seems to work
> with maverick at all. Do i need some updated files on the client to be able to
> use the new compat tree?
>
> I thought that the compat tree would work without changes on kernel from >
> 2.6.30 is that right?
I have no idea what maverick is. I suppose it to be some release of Ubuntu, but
you really need to specify a kernel version, not a release name. Many of us do
not use any Debian-based systems for very good reasons.
The compat tree will work without changes on any kernel on which it will
compile, AS LONG AS THE REST OF THE KERNEL DOES NOT BREAK THE WIRELESS.
My full bisection ended up in am impossible result.
The only other thing I can add at the moment, is that rtl8192cu works with WEP
encryption, thus the part that broke is WPA and WPA2.
Larry
next prev parent reply other threads:[~2011-08-11 14:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 9:16 rtl8192cu sometimes it can authenticate to ap kc
2011-08-09 11:07 ` kc
2011-08-09 15:12 ` kc
2011-08-09 16:37 ` Larry Finger
2011-08-09 19:27 ` william
[not found] ` <d3faeaf2e881a324b0ad3102c10e6131@cobradevil.org>
2011-08-10 14:57 ` Larry Finger
2011-08-11 14:23 ` kc
2011-08-11 14:37 ` Larry Finger [this message]
2011-08-11 14:42 ` kc
2011-08-11 15:59 ` Larry Finger
2011-08-24 18:35 ` william
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=4E43E910.7090001@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=kc@cobradevil.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).