linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: kc@cobradevil.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: rtl8192cu sometimes it can authenticate to ap
Date: Tue, 09 Aug 2011 11:37:34 -0500	[thread overview]
Message-ID: <4E41624E.3010904@lwfinger.net> (raw)
In-Reply-To: <532595cb4d5ef910de54a4736ba76185@cobradevil.org>

On 08/09/2011 10:12 AM, kc@cobradevil.org wrote:
> Hello all,
>
> not sure what is happening but so far i have the following results:
> i downloaded the latest bleeding edge wireless from
> http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2
> I installed kernel headers and build-essentials end run:
> ./scripts/driver-select rtlwifi
> make && make install
>
> i downloaded the firmware from
> http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git
>
> Running on Ubuntu maverick kernel 2.6.35-30 update 56 i get sometimes an
> authenticated message when running wpa_supplicant -Dnl80211 -c
> /etc/wpa_supplicant.conf -i wlan0 but most times it will timeout
> Running on Ubuntu natty kernel 2.6.38-10 update 46 i always get the
> authenticated message when running wpa_supplicant -Dnl80211 -c
> /etc/wpa_supplicant.conf -i wlan0
>
> only when using dhcp request on two accespoint i get different results on the
> natty driver but that has todo with:
> https://bugzilla.kernel.org/show_bug.cgi?id=38012 when applied i can connect two
> both accespoints.
>
> Any ideas why it does not work on the maverick kernel?

How does it work at all with a 2.6.38 kernel? Driver rtl8192cu was not added to 
the kernel until 2.6 39.

> Also when stopping the wpa_supplicant with ctrl+c and restart i first have to
> replug the device before it tries todo anything with the card.

What info is in the dmesg output in this case?

To debug the authentication case, run wpa_supplicant with the "-ddd" and "-f 
wpa_supplicant.log" switches. That way you will get a log of what is going wrong.

Larry

  reply	other threads:[~2011-08-09 16: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 [this message]
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
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=4E41624E.3010904@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).