Hello all,
i have three usb sticks with the the id:
0bda:8176
I am running ubuntu maverick with the compat tree from 2011-08-08
(downloaded this morning) and i also tried several others (dates from 15
juli 2011).
The main problem is that sometimes i get a connection and it works like
a charm and then all of the sudden i don't get any connection at all and
running wpa_supplicant says time out.
i really have no idea whats wrong so if someone could help me out.
is there a way to get debugging from the rtlwifi drivers?
i got the firmware from:
http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git
With kind regards
William
On 08/11/2011 09:42 AM, [email protected] wrote:
>
>
> On Thu, 11 Aug 2011 09:37:04 -0500, Larry Finger wrote:
>> On 08/11/2011 09:23 AM, [email protected] 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.
>
> Sorry for that. The kernel is 2.6.35 but your answer makes it clear it should
> work with no extra userland tools.
>>
>> 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.
>
> Ok but did the driver work before with wpa and or wpa2?
> If so do you have an idea which date the compat file should be?
>
> If not then i will have to wait for a fix but i can tell people whats wrong.
It works with wireless-testing kernel 3.0, but not with 3.1-rc1. There were no
changes in rtl8192cu in the interum - this problem has me baffled for the
moment. According to the NetworkManager log, the device authenticates correctly,
but it never manages to get an IP.
Larry
On 08/09/2011 10:12 AM, [email protected] 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
Hello Larry,
any updates on this one?
With kind regards
William
On 08/11/2011 05:59 PM, Larry Finger wrote:
>>
>>
>> If not then i will have to wait for a fix but i can tell people whats
>> wrong.
>
> It works with wireless-testing kernel 3.0, but not with 3.1-rc1. There
> were no changes in rtl8192cu in the interum - this problem has me
> baffled for the moment. According to the NetworkManager log, the
> device authenticates correctly, but it never manages to get an IP.
Hi all,
Have installed natty and also installed the snapshot.
After compile and installed the rtlwifi driver the wpa_supplicant works
like a charm every time with all three sticks.
So i think it is something in the compat layer or userland utilities?
Anyone an idea?
I would like this to work with the maverick kernel 2.6.35 because we
cannot upgrade right now.
With kind regards
William
On Tue, 09 Aug 2011 09:16:12 +0000, [email protected] wrote:
> Hello all,
>
> i have three usb sticks with the the id:
> 0bda:8176
>
> I am running ubuntu maverick with the compat tree from 2011-08-08
> (downloaded this morning) and i also tried several others (dates from
> 15
> juli 2011).
> The main problem is that sometimes i get a connection and it works
> like
> a charm and then all of the sudden i don't get any connection at all
> and
> running wpa_supplicant says time out.
>
> i really have no idea whats wrong so if someone could help me out.
> is there a way to get debugging from the rtlwifi drivers?
>
> i got the firmware from:
> http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git
> [1]
>
> With kind regards
>
> William
Links:
------
[1] http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git
On Wed, 10 Aug 2011 09:57:27 -0500, Larry Finger wrote:
> On 08/10/2011 08:32 AM, [email protected] wrote:
>> Hello Larry,
>>
>> did you receive my last email with the log files?
>> i'm not sure if that the right information so if you need more the
>> please let me
>> know.
>
> Yes, I got them.
>
> So far, the only conclusion from them is that you should install the
> CRDA package. That is not the cause of your problem, but it needs to
> be done.
>
> I can duplicate the problem here and find that it occurs between 3.0
> and 3.1-rc1. I first tried to bisect testing only
> drivers/net/wireless/rtlwifi, net/mac80211 and net/wireless
> directories. That led to an impossible "bad" commit, thus I'm having
> to bisect the whole tree.
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'll let you know what I find.
>
> Larry
On 08/11/2011 09:23 AM, [email protected] 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
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?
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.
With kind regards
William
On Tue, 09 Aug 2011 11:07:56 +0000, [email protected] wrote:
> Hi all,
>
> Have installed natty and also installed the snapshot.
>
> After compile and installed the rtlwifi driver the wpa_supplicant
> works
> like a charm every time with all three sticks.
> So i think it is something in the compat layer or userland utilities?
>
> Anyone an idea?
> I would like this to work with the maverick kernel 2.6.35 because we
> cannot upgrade right now.
>
> With kind regards
>
> William
>
> On Tue, 09 Aug 2011 09:16:12 +0000, [email protected] [2]wrote:
>
>> Hello all, i have three usb sticks with the the id: 0bda:8176 I am
>> running ubuntu maverick with the compat tree from 2011-08-08
>> (downloaded this morning) and i also tried several others (dates
>> from
>> 15 juli 2011). The main problem is that sometimes i get a connection
>> and it works like a charm and then all of the sudden i don't get any
>> connection at all and running wpa_supplicant says time out. i really
>> have no idea whats wrong so if someone could help me out. is there a
>> way to get debugging from the rtlwifi drivers? i got the firmware
>> from:
>> http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git
>> [1]
>> [1] With kind regards William
>
> Links:
> ------
> [1]
> http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git
> [3]
Links:
------
[1] http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git
[2] mailto:[email protected]
[3] http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git
On Thu, 11 Aug 2011 09:37:04 -0500, Larry Finger wrote:
> On 08/11/2011 09:23 AM, [email protected] 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.
Sorry for that. The kernel is 2.6.35 but your answer makes it clear it
should work with no extra userland tools.
>
> 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.
Ok but did the driver work before with wpa and or wpa2?
If so do you have an idea which date the compat file should be?
If not then i will have to wait for a fix but i can tell people whats
wrong.
Larry, thank you very much for your responses.
With kind regards
William van de Velde
>
> Larry
On 08/10/2011 08:32 AM, [email protected] wrote:
> Hello Larry,
>
> did you receive my last email with the log files?
> i'm not sure if that the right information so if you need more the please let me
> know.
Yes, I got them.
So far, the only conclusion from them is that you should install the CRDA
package. That is not the cause of your problem, but it needs to be done.
I can duplicate the problem here and find that it occurs between 3.0 and
3.1-rc1. I first tried to bisect testing only drivers/net/wireless/rtlwifi,
net/mac80211 and net/wireless directories. That led to an impossible "bad"
commit, thus I'm having to bisect the whole tree.
I'll let you know what I find.
Larry
Ok attached log files and below my test at home
Test scenario:
@home
I have a netgear wireless router which does wpa2 aes
i cannot get it to work anymore as at work so forgive me for these mixed
results.
What i do is compile todays compat wireless on ubuntu maverick and on natty
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
###################################################################
ubuntu maverick
###################################################################
ubuntu maverick 2.6.35-30.54:
dmesg -c after cold boot:
plugging in adapter:
dmesg:
[ 387.400102] usb 2-5: new high speed USB device using ehci_hcd and
address 3
[ 387.682348] rtl8192cu: MAC address: 00:a1:b0:89:82:1c
[ 387.682361] rtl8192cu: Board Type 0
[ 387.713558] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 387.713565] cfg80211: Updating information on frequency 2412 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713568] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713571] cfg80211: Updating information on frequency 2417 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713573] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713576] cfg80211: Updating information on frequency 2422 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713578] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713580] cfg80211: Updating information on frequency 2427 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713583] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713585] cfg80211: Updating information on frequency 2432 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713588] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713590] cfg80211: Updating information on frequency 2437 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713593] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713595] cfg80211: Updating information on frequency 2442 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713598] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713600] cfg80211: Updating information on frequency 2447 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713603] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713605] cfg80211: Updating information on frequency 2452 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713607] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713610] cfg80211: Updating information on frequency 2457 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713612] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713615] cfg80211: Updating information on frequency 2462 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713617] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713620] cfg80211: Disabling freq 2467 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 387.713622] cfg80211: Disabling freq 2472 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 387.713624] cfg80211: Disabling freq 2484 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 387.713886] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[ 387.718805] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[ 387.719469] usbcore: registered new interface driver rtl8192cu
[ 387.740881] udev[987]: renamed network interface wlan0 to wlan1
wpa_supplicant -Dnl80211 -dd -c /etc/wpa_supplicant_thuis.conf -f
wpa_supplicant.log -iwlan1
wpa_supplicant-ubuntu-maverick_cold_boot.log
dmesg:
[ 387.400102] usb 2-5: new high speed USB device using ehci_hcd and
address 3
[ 387.682348] rtl8192cu: MAC address: 00:a1:b0:89:82:1c
[ 387.682361] rtl8192cu: Board Type 0
[ 387.713558] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 387.713565] cfg80211: Updating information on frequency 2412 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713568] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713571] cfg80211: Updating information on frequency 2417 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713573] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713576] cfg80211: Updating information on frequency 2422 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713578] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713580] cfg80211: Updating information on frequency 2427 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713583] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713585] cfg80211: Updating information on frequency 2432 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713588] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713590] cfg80211: Updating information on frequency 2437 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713593] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713595] cfg80211: Updating information on frequency 2442 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713598] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713600] cfg80211: Updating information on frequency 2447 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713603] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713605] cfg80211: Updating information on frequency 2452 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713607] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713610] cfg80211: Updating information on frequency 2457 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713612] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713615] cfg80211: Updating information on frequency 2462 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713617] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713620] cfg80211: Disabling freq 2467 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 387.713622] cfg80211: Disabling freq 2472 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 387.713624] cfg80211: Disabling freq 2484 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 387.713886] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[ 387.718805] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[ 387.719469] usbcore: registered new interface driver rtl8192cu
[ 387.740881] udev[987]: renamed network interface wlan0 to wlan1
[ 462.336237] rtl8192cu: MAC auto ON okay!
[ 462.370400] rtl8192cu: Tx queue select: 0x05
[ 462.371173] rtl8192c_common: Loading firmware file
rtlwifi/rtl8192cufw.bin
[ 462.774420] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 463.673151] wlan1: direct probe to e0:91:f5:7a:ae:d6 (try 1/3)
[ 463.677499] wlan1: direct probe responded
[ 463.690120] wlan1: authenticate with e0:91:f5:7a:ae:d6 (try 1)
[ 463.708429] wlan1: authenticated
[ 463.708461] wlan1: associate with e0:91:f5:7a:ae:d6 (try 1)
[ 463.715801] wlan1: RX AssocResp from e0:91:f5:7a:ae:d6 (capab=0x411
status=0 aid=3)
[ 463.715808] wlan1: associated
[ 463.729553] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[ 473.761143] wlan1: deauthenticating from e0:91:f5:7a:ae:d6 by local
choice (reason=3)
[ 473.811154] cfg80211: All devices are disconnected, going to restore
regulatory settings
[ 473.811167] cfg80211: Restoring regulatory settings
[ 473.811176] cfg80211: Calling CRDA to update world regulatory domain
[ 473.824224] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[ 473.824232] cfg80211: World regulatory domain updated:
[ 473.824237] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 473.824246] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[ 473.824254] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz),
(300 mBi, 2000 mBm)
[ 473.824261] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz),
(300 mBi, 2000 mBm)
[ 473.824268] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[ 473.824275] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[ 474.240071] wlan1: no IPv6 routers present
[ 474.613195] wlan1: authenticate with e0:91:f5:7a:ae:d6 (try 1)
[ 474.810080] wlan1: authenticate with e0:91:f5:7a:ae:d6 (try 2)
[ 475.010123] wlan1: authenticate with e0:91:f5:7a:ae:d6 (try 3)
[ 475.014905] wlan1: authenticated
[ 475.014939] wlan1: associate with e0:91:f5:7a:ae:d6 (try 1)
[ 475.018642] wlan1: RX AssocResp from e0:91:f5:7a:ae:d6 (capab=0x411
status=0 aid=3)
[ 475.018650] wlan1: associated
[ 485.048496] wlan1: deauthenticating from e0:91:f5:7a:ae:d6 by local
choice (reason=3)
[ 485.083634] cfg80211: All devices are disconnected, going to restore
regulatory settings
[ 485.083644] cfg80211: Restoring regulatory settings
[ 485.083653] cfg80211: Calling CRDA to update world regulatory domain
[ 485.096588] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[ 485.096597] cfg80211: World regulatory domain updated:
[ 485.096601] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 485.096610] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[ 485.096617] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz),
(300 mBi, 2000 mBm)
[ 485.096625] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz),
(300 mBi, 2000 mBm)
[ 485.096632] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[ 485.096640] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[ 485.893367] wlan1: authenticate with e0:91:f5:7a:ae:d6 (try 1)
[ 486.092557] wlan1: authenticate with e0:91:f5:7a:ae:d6 (try 2)
[ 486.290075] wlan1: authenticate with e0:91:f5:7a:ae:d6 (try 3)
[ 486.490071] wlan1: authentication with e0:91:f5:7a:ae:d6 timed out
ctrl+c wpa_supplicant and starting again:
dmesg:
[ 387.400102] usb 2-5: new high speed USB device using ehci_hcd and
address 3
[ 387.682348] rtl8192cu: MAC address: 00:a1:b0:89:82:1c
[ 387.682361] rtl8192cu: Board Type 0
[ 387.713558] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 387.713565] cfg80211: Updating information on frequency 2412 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713568] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713571] cfg80211: Updating information on frequency 2417 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713573] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713576] cfg80211: Updating information on frequency 2422 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713578] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713580] cfg80211: Updating information on frequency 2427 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713583] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713585] cfg80211: Updating information on frequency 2432 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713588] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713590] cfg80211: Updating information on frequency 2437 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713593] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713595] cfg80211: Updating information on frequency 2442 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713598] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713600] cfg80211: Updating information on frequency 2447 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713603] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713605] cfg80211: Updating information on frequency 2452 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713607] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713610] cfg80211: Updating information on frequency 2457 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713612] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713615] cfg80211: Updating information on frequency 2462 MHz for
a 20 MHz width channel with regulatory rule:
[ 387.713617] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 387.713620] cfg80211: Disabling freq 2467 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 387.713622] cfg80211: Disabling freq 2472 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 387.713624] cfg80211: Disabling freq 2484 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 387.713886] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[ 387.718805] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[ 387.719469] usbcore: registered new interface driver rtl8192cu
[ 387.740881] udev[987]: renamed network interface wlan0 to wlan1
[ 462.336237] rtl8192cu: MAC auto ON okay!
[ 462.370400] rtl8192cu: Tx queue select: 0x05
[ 462.371173] rtl8192c_common: Loading firmware file
rtlwifi/rtl8192cufw.bin
[ 462.774420] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 463.673151] wlan1: direct probe to e0:91:f5:7a:ae:d6 (try 1/3)
[ 463.677499] wlan1: direct probe responded
[ 463.690120] wlan1: authenticate with e0:91:f5:7a:ae:d6 (try 1)
[ 463.708429] wlan1: authenticated
[ 463.708461] wlan1: associate with e0:91:f5:7a:ae:d6 (try 1)
[ 463.715801] wlan1: RX AssocResp from e0:91:f5:7a:ae:d6 (capab=0x411
status=0 aid=3)
[ 463.715808] wlan1: associated
[ 463.729553] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[ 473.761143] wlan1: deauthenticating from e0:91:f5:7a:ae:d6 by local
choice (reason=3)
[ 473.811154] cfg80211: All devices are disconnected, going to restore
regulatory settings
[ 473.811167] cfg80211: Restoring regulatory settings
[ 473.811176] cfg80211: Calling CRDA to update world regulatory domain
[ 473.824224] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[ 473.824232] cfg80211: World regulatory domain updated:
[ 473.824237] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 473.824246] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[ 473.824254] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz),
(300 mBi, 2000 mBm)
[ 473.824261] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz),
(300 mBi, 2000 mBm)
[ 473.824268] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[ 473.824275] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[ 474.240071] wlan1: no IPv6 routers present
[ 474.613195] wlan1: authenticate with e0:91:f5:7a:ae:d6 (try 1)
[ 474.810080] wlan1: authenticate with e0:91:f5:7a:ae:d6 (try 2)
[ 475.010123] wlan1: authenticate with e0:91:f5:7a:ae:d6 (try 3)
[ 475.014905] wlan1: authenticated
[ 475.014939] wlan1: associate with e0:91:f5:7a:ae:d6 (try 1)
[ 475.018642] wlan1: RX AssocResp from e0:91:f5:7a:ae:d6 (capab=0x411
status=0 aid=3)
[ 475.018650] wlan1: associated
[ 485.048496] wlan1: deauthenticating from e0:91:f5:7a:ae:d6 by local
choice (reason=3)
[ 485.083634] cfg80211: All devices are disconnected, going to restore
regulatory settings
[ 485.083644] cfg80211: Restoring regulatory settings
[ 485.083653] cfg80211: Calling CRDA to update world regulatory domain
[ 485.096588] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[ 485.096597] cfg80211: World regulatory domain updated:
[ 485.096601] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 485.096610] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[ 485.096617] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz),
(300 mBi, 2000 mBm)
[ 485.096625] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz),
(300 mBi, 2000 mBm)
[ 485.096632] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[ 485.096640] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[ 485.893367] wlan1: authenticate with e0:91:f5:7a:ae:d6 (try 1)
[ 486.092557] wlan1: authenticate with e0:91:f5:7a:ae:d6 (try 2)
[ 486.290075] wlan1: authenticate with e0:91:f5:7a:ae:d6 (try 3)
[ 486.490071] wlan1: authentication with e0:91:f5:7a:ae:d6 timed out
[ 612.790282] rtl8192cu: MAC auto ON okay!
[ 612.828665] rtl8192cu: Tx queue select: 0x05
[ 612.829415] rtl8192c_common: Loading firmware file
rtlwifi/rtl8192cufw.bin
[ 613.232099] ADDRCONF(NETDEV_UP): wlan1: link is not ready
attached wpa_supplicant-ubuntu-maverick_ctrlc.log
###################################################################
ubuntu natty
###################################################################
ubuntu natty 2.6.38-10.46:
dmesg -c after cold boot:
plugging in adapter:
dmesg:
[ 541.820017] usb 1-4: new high speed USB device using ehci_hcd and
address 3
[ 541.981323] cfg80211: Calling CRDA to update world regulatory domain
[ 542.094477] rtl8192cu: MAC address: 00:a1:b0:89:82:1c
[ 542.094484] rtl8192cu: Board Type 0
[ 542.102603] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 542.102610] cfg80211: Updating information on frequency 2412 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102615] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102618] cfg80211: Updating information on frequency 2417 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102622] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102625] cfg80211: Updating information on frequency 2422 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102629] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102632] cfg80211: Updating information on frequency 2427 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102636] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102639] cfg80211: Updating information on frequency 2432 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102642] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102646] cfg80211: Updating information on frequency 2437 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102649] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102652] cfg80211: Updating information on frequency 2442 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102656] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102659] cfg80211: Updating information on frequency 2447 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102663] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102666] cfg80211: Updating information on frequency 2452 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102670] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102673] cfg80211: Updating information on frequency 2457 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102677] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102680] cfg80211: Updating information on frequency 2462 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102683] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102687] cfg80211: Disabling freq 2467 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 542.102690] cfg80211: Disabling freq 2472 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 542.102693] cfg80211: Disabling freq 2484 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 542.102703] cfg80211: Pending regulatory request, waiting for it to
be processed...
[ 542.102760] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[ 542.105689] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[ 542.106369] usbcore: registered new interface driver rtl8192cu
wpa_supplicant -Dnl80211 -dd -c /etc/wpa_supplicant_thuis.conf -f
wpa_supplicant.log -iwlan0
wpa_supplicant-ubuntu-natty_cold_boot.log
dmesg:
[ 541.981323] cfg80211: Calling CRDA to update world regulatory domain
[ 542.094477] rtl8192cu: MAC address: 00:a1:b0:89:82:1c
[ 542.094484] rtl8192cu: Board Type 0
[ 542.102603] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 542.102610] cfg80211: Updating information on frequency 2412 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102615] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102618] cfg80211: Updating information on frequency 2417 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102622] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102625] cfg80211: Updating information on frequency 2422 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102629] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102632] cfg80211: Updating information on frequency 2427 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102636] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102639] cfg80211: Updating information on frequency 2432 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102642] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102646] cfg80211: Updating information on frequency 2437 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102649] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102652] cfg80211: Updating information on frequency 2442 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102656] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102659] cfg80211: Updating information on frequency 2447 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102663] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102666] cfg80211: Updating information on frequency 2452 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102670] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102673] cfg80211: Updating information on frequency 2457 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102677] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102680] cfg80211: Updating information on frequency 2462 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102683] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102687] cfg80211: Disabling freq 2467 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 542.102690] cfg80211: Disabling freq 2472 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 542.102693] cfg80211: Disabling freq 2484 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 542.102703] cfg80211: Pending regulatory request, waiting for it to
be processed...
[ 542.102760] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[ 542.105689] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[ 542.106369] usbcore: registered new interface driver rtl8192cu
[ 676.832020] [drm] nouveau 0000:01:00.0: Setting dpms mode 1 on vga
encoder (output 0)
[ 837.368145] rtl8192cu: MAC auto ON okay!
[ 837.400782] rtl8192cu: Tx queue select: 0x05
[ 837.401540] rtl8192c_common: Loading firmware file
rtlwifi/rtl8192cufw.bin
[ 837.794521] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 838.635952] wlan0: authenticate with e0:91:f5:7a:ae:d6 (try 1)
[ 838.640035] wlan0: authenticated
[ 838.640211] wlan0: associate with e0:91:f5:7a:ae:d6 (try 1)
[ 838.644032] wlan0: RX AssocResp from e0:91:f5:7a:ae:d6 (capab=0x411
status=0 aid=4)
[ 838.644036] wlan0: associated
[ 838.656495] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 838.681561] Intel AES-NI instructions are not detected.
[ 838.701438] padlock_aes: VIA PadLock not detected.
[ 848.816007] wlan0: no IPv6 routers present
ctrl+c wpa_supplicant and starting again:
dmesg:
[ 541.820017] usb 1-4: new high speed USB device using ehci_hcd and
address 3
[ 541.981323] cfg80211: Calling CRDA to update world regulatory domain
[ 542.094477] rtl8192cu: MAC address: 00:a1:b0:89:82:1c
[ 542.094484] rtl8192cu: Board Type 0
[ 542.102603] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 542.102610] cfg80211: Updating information on frequency 2412 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102615] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102618] cfg80211: Updating information on frequency 2417 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102622] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102625] cfg80211: Updating information on frequency 2422 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102629] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102632] cfg80211: Updating information on frequency 2427 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102636] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102639] cfg80211: Updating information on frequency 2432 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102642] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102646] cfg80211: Updating information on frequency 2437 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102649] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102652] cfg80211: Updating information on frequency 2442 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102656] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102659] cfg80211: Updating information on frequency 2447 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102663] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102666] cfg80211: Updating information on frequency 2452 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102670] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102673] cfg80211: Updating information on frequency 2457 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102677] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102680] cfg80211: Updating information on frequency 2462 MHz for
a 20 MHz width channel with regulatory rule:
[ 542.102683] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 542.102687] cfg80211: Disabling freq 2467 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 542.102690] cfg80211: Disabling freq 2472 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 542.102693] cfg80211: Disabling freq 2484 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 542.102703] cfg80211: Pending regulatory request, waiting for it to
be processed...
[ 542.102760] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[ 542.105689] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[ 542.106369] usbcore: registered new interface driver rtl8192cu
[ 676.832020] [drm] nouveau 0000:01:00.0: Setting dpms mode 1 on vga
encoder (output 0)
[ 837.368145] rtl8192cu: MAC auto ON okay!
[ 837.400782] rtl8192cu: Tx queue select: 0x05
[ 837.401540] rtl8192c_common: Loading firmware file
rtlwifi/rtl8192cufw.bin
[ 837.794521] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 838.635952] wlan0: authenticate with e0:91:f5:7a:ae:d6 (try 1)
[ 838.640035] wlan0: authenticated
[ 838.640211] wlan0: associate with e0:91:f5:7a:ae:d6 (try 1)
[ 838.644032] wlan0: RX AssocResp from e0:91:f5:7a:ae:d6 (capab=0x411
status=0 aid=4)
[ 838.644036] wlan0: associated
[ 838.656495] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 838.681561] Intel AES-NI instructions are not detected.
[ 838.701438] padlock_aes: VIA PadLock not detected.
[ 848.816007] wlan0: no IPv6 routers present
[ 952.783925] wlan0: deauthenticating from e0:91:f5:7a:ae:d6 by local
choice (reason=3)
[ 952.808221] cfg80211: All devices are disconnected, going to restore
regulatory settings
[ 952.808225] cfg80211: Restoring regulatory settings
[ 952.808231] cfg80211: Calling CRDA for country: US
[ 975.889157] rtl8192cu: MAC auto ON okay!
[ 975.921798] rtl8192cu: Tx queue select: 0x05
[ 975.922442] rtl8192c_common: Loading firmware file
rtlwifi/rtl8192cufw.bin
[ 976.313109] ADDRCONF(NETDEV_UP): wlan0: link is not ready
attached wpa_supplicant-ubuntu-maverick_ctrlc.log
@@@@@@@@@@@@@@@@@@@@
on 2.6.35 i cannot do a dhcp request but i can on 2.6.38
after ctrl+c both systems are rendered useless
On 08/09/2011 06:37 PM, Larry Finger wrote:
> On 08/09/2011 10:12 AM, [email protected] 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.
>
sorry for not being clear about this but i also compiled the compat tree
on this kernel
>> 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