Hi there,
i just bought an Alfa AWUS036NHR for testing.
It runs with the rtl8192cu driver.
I have a question because sometimes the wireless adapter dont shows any
networks no longer.
I have to reload the module an then its showing some networks.
In dmesg it shows:
[ 262.219575] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 269.770133] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 270.947047] ADDRCONF(NETDEV_UP): wlan1: link is not ready
For any further output please let me know.
On 09/21/2011 02:02 AM, Larry Finger wrote:
> On 09/20/2011 04:38 PM, Chiefdome wrote:
>> I tried at least wireless-next but the adapter isn't showing up.
>> Where to get more log files and stuff?
>> Isnt this adapter good supported by the rtl8192cu driver or where is
>> the problem?
>
> For the mainline kernel to work with 802.11n-only APs and to reconnect
> after an initial try, your kernel needs the following patches:
>
> commit bac2555c6d86387132930af4d14cb47c4dd3f4f7
> Author: George <[email protected]>
> Date: Sat Sep 3 10:58:48 2011 -0500
>
> rtlwifi: Fix problem when switching connections
>
> The driver fails to clear encryption keys making it impossible
> to switch connections.
>
> Signed-off-by: George <[email protected]>
> Signed-off-by: Larry Finger <[email protected]>
> Cc: Stable <[email protected]> [2.6.39+]
> Signed-off-by: John W. Linville <[email protected]>
>
> commit 3401dc6eba788ebc7c14ce51018d775b1c263399
> Author: George <[email protected]>
> Date: Sat Sep 3 10:58:47 2011 -0500
>
> rtlwifi: rtl8192su: Fix problem connecting to HT-enabled AP
>
> The driver fails to connect to 802.11n-enabled APs. The patch fixes
> Bug #42262.
>
> Signed-off-by: George <[email protected]>
> Signed-off-by: Larry Finger <[email protected]>
> Cc: Stable <[email protected]> [2.6.39+]
> Signed-off-by: John W. Linville <[email protected]>
>
> Both of these are in wireless-testing, and were just merged into the
> mainline kernel. In addition, they were merged with the 3.0 stable
> tree today.
>
> Both should be in wireless-next, but as I recall, you were not able to
> test with that tree.
>
> With the updated mainline kernel, the link is stable and performance
> is acceptible with netperf TCP_STREAM (TX) at 20.5 +/- 4.8 Mbps and
> TCP_MAERTS (RX) of 21.7 +/- 3.8 Mbps. These numbers are not
> spectacular, but they will do.
>
> Larry
>
I tried the latest git repo from
git://git.infradead.org/users/linville/wireless-next.
Same story here.
After disconnecting to the network, I have to reload the module only
then networks are seen.
Chiefdome
On 09/20/2011 04:38 PM, Chiefdome wrote:
> I tried at least wireless-next but the adapter isn't showing up.
> Where to get more log files and stuff?
> Isnt this adapter good supported by the rtl8192cu driver or where is the problem?
I have no idea as the only AWUS036 I have is the old one with an RTL8187 chip.
I have been running a wireless-testing 3.1-rc6 kernel with an RTL8188CUS chip
(USB IDs are 7392:7811) with no problems. George will know more about supporting
that chip than I do.
I will boot my mainline kernel, but I think it is OK.
If the adapter isn't showing up in wireless-next, you need to check the USB IDs
using lsusb, and compare them with the USB_DEVICE tables in
drivers/net/wireless/rtl8192cu/sw.c. The only place that logs will occur is
dmesg, /var/log/messages, or /var/log/syslog.
Larry
On 09/20/2011 11:32 AM, Chiefdome wrote:
> On 09/20/2011 05:05 AM, Larry Finger wrote:
>> On 09/19/2011 09:27 PM, Chiefdome wrote:
>>> On 09/20/2011 04:10 AM, Chiefdome wrote:
>>>> Hi there,
>>>>
>>>> i just bought an Alfa AWUS036NHR for testing.
>>>> It runs with the rtl8192cu driver.
>>>> I have a question because sometimes the wireless adapter dont shows
>>>> any
>>>> networks no longer.
>>>> I have to reload the module an then its showing some networks.
>>>>
>>>> In dmesg it shows:
>>>>
>>>> [ 262.219575] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>>> [ 269.770133] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>>> [ 270.947047] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>>>
>>>>
>>>> For any further output please let me know.
>>> A complete dmesg output can be seen here, because theres also a
>>> problem when
>>> associating to a network:
>>>
>>> [ 1455.353142] cfg80211: All devices are disconnected, going to restore
>>> regulatory settings
>>> [ 1455.353155] cfg80211: Restoring regulatory settings
>>> [ 1455.353165] cfg80211: Calling CRDA to update world regulatory domain
>>> [ 1455.361425] cfg80211: Ignoring regulatory request Set by core
>>> since the
>>> driver uses its own custom regulatory domain
>>> [ 1455.361436] cfg80211: Ignoring regulatory request Set by core
>>> since the
>>> driver uses its own custom regulatory domain
>>> [ 1455.361442] cfg80211: World regulatory domain updated:
>>> [ 1455.361447] cfg80211: (start_freq - end_freq @ bandwidth),
>>> (max_antenna_gain,
>>> max_eirp)
>>> [ 1455.361454] cfg80211: (2400000 KHz - 2494000 KHz @ 40000 KHz),
>>> (N/A, 3301 mBm)
>>> [ 1455.361460] cfg80211: (4910000 KHz - 5895000 KHz @ 40000 KHz),
>>> (N/A, 3301 mBm)
>>> [ 1455.403456] iwlagn 0000:03:00.0: L1 Disabled; Enabling L0S
>>> [ 1455.403856] iwlagn 0000:03:00.0: Radio type=0x0-0x2-0x0
>>> [ 1455.459585] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>>> [ 1455.950477] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
>>> [ 1456.010220] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
>>> [ 1456.011668] ADDRCONF(NETDEV_UP): eth0: link is not ready
>>> [ 1495.264204] rtl8192cu: MAC auto ON okay!
>>> [ 1495.299099] rtl8192cu: Tx queue select: 0x05
>>> [ 1495.299880] rtl8192c_common: Loading firmware file
>>> rtlwifi/rtl8192cufw.bin
>>> [ 1495.709590] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>> [ 1500.741392] usbcore: deregistering interface driver rtl8192cu
>>> [ 1505.097104] rtl8192cu: MAC address: 00:c0:ca:52:cb:4c
>>> [ 1505.097116] rtl8192cu: Board Type 1
>>> [ 1505.102441] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
>>> [ 1505.102454] cfg80211: Updating information on frequency 2412 MHz
>>> for a 20 MHz
>>> width channel with regulatory rule:
>>> [ 1505.102462] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>>> 2000 mBm)
>>> [ 1505.102468] cfg80211: Updating information on frequency 2417 MHz
>>> for a 20 MHz
>>> width channel with regulatory rule:
>>> [ 1505.102475] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>>> 2000 mBm)
>>> [ 1505.102480] cfg80211: Updating information on frequency 2422 MHz
>>> for a 20 MHz
>>> width channel with regulatory rule:
>>> [ 1505.102487] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>>> 2000 mBm)
>>> [ 1505.102493] cfg80211: Updating information on frequency 2427 MHz
>>> for a 20 MHz
>>> width channel with regulatory rule:
>>> [ 1505.102499] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>>> 2000 mBm)
>>> [ 1505.102505] cfg80211: Updating information on frequency 2432 MHz
>>> for a 20 MHz
>>> width channel with regulatory rule:
>>> [ 1505.102511] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>>> 2000 mBm)
>>> [ 1505.102517] cfg80211: Updating information on frequency 2437 MHz
>>> for a 20 MHz
>>> width channel with regulatory rule:
>>> [ 1505.102523] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>>> 2000 mBm)
>>> [ 1505.102529] cfg80211: Updating information on frequency 2442 MHz
>>> for a 20 MHz
>>> width channel with regulatory rule:
>>> [ 1505.102536] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>>> 2000 mBm)
>>> [ 1505.102541] cfg80211: Updating information on frequency 2447 MHz
>>> for a 20 MHz
>>> width channel with regulatory rule:
>>> [ 1505.102548] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>>> 2000 mBm)
>>> [ 1505.102553] cfg80211: Updating information on frequency 2452 MHz
>>> for a 20 MHz
>>> width channel with regulatory rule:
>>> [ 1505.102560] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>>> 2000 mBm)
>>> [ 1505.102565] cfg80211: Updating information on frequency 2457 MHz
>>> for a 20 MHz
>>> width channel with regulatory rule:
>>> [ 1505.102572] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>>> 2000 mBm)
>>> [ 1505.102578] cfg80211: Updating information on frequency 2462 MHz
>>> for a 20 MHz
>>> width channel with regulatory rule:
>>> [ 1505.102584] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>>> 2000 mBm)
>>> [ 1505.102590] cfg80211: Disabling freq 2467 MHz as custom regd has
>>> no rule that
>>> fits a 20 MHz wide channel
>>> [ 1505.102595] cfg80211: Disabling freq 2472 MHz as custom regd has
>>> no rule that
>>> fits a 20 MHz wide channel
>>> [ 1505.102601] cfg80211: Disabling freq 2484 MHz as custom regd has
>>> no rule that
>>> fits a 20 MHz wide channel
>>> [ 1505.103549] cfg80211: Ignoring regulatory request Set by core
>>> since the
>>> driver uses its own custom regulatory domain
>>> [ 1505.103803] ieee80211 phy2: Selected rate control algorithm 'rtl_rc'
>>> [ 1505.105949] usbcore: registered new interface driver rtl8192cu
>>> [ 1513.004969] rtl8192cu: MAC auto ON okay!
>>> [ 1513.038127] rtl8192cu: Tx queue select: 0x05
>>> [ 1513.038878] rtl8192c_common: Loading firmware file
>>> rtlwifi/rtl8192cufw.bin
>>> [ 1513.443284] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>> [ 1519.568596] rtl8192cu: MAC auto ON okay!
>>> [ 1519.601476] rtl8192cu: Tx queue select: 0x05
>>> [ 1519.602253] rtl8192c_common: Loading firmware file
>>> rtlwifi/rtl8192cufw.bin
>>> [ 1520.008221] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>> [ 1520.350447] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
>>> [ 1520.410244] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
>>> [ 1520.411607] ADDRCONF(NETDEV_UP): eth0: link is not ready
>>> [ 1520.619096] rtl8192cu: MAC auto ON okay!
>>> [ 1520.651975] rtl8192cu: Tx queue select: 0x05
>>> [ 1520.652755] rtl8192c_common: Loading firmware file
>>> rtlwifi/rtl8192cufw.bin
>>> [ 1521.060567] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>> [ 1524.272807] wlan1: authenticate with [MAC-ADDRESS] (try 1)
>>> [ 1524.299985] wlan1: authenticated
>>> [ 1524.300029] wlan1: associate with [MAC-ADDRESS] (try 1)
>>> [ 1524.309323] wlan1: RX AssocResp from [MAC-ADDRESS] (capab=0x431
>>> status=0 aid=1)
>>> [ 1524.309331] wlan1: associated
>>> [ 1524.311767] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
>>> [ 1525.172880] type=1400 audit(1316485102.702:35): apparmor="DENIED"
>>> operation="open" parent=5409 profile="/sbin/dhclient"
>>> name="/var/lib/wicd/dhclient.conf" pid=5445 comm="dhclient"
>>> requested_mask="r"
>>> denied_mask="r" fsuid=0 ouid=0
>>> [ 1534.590028] wlan1: no IPv6 routers present
>>
>> What kernel? There are some problems with kernels prior to 3.1 in
>> connecting to 802.11n networks, and also a problem in clearing the
>> keys. Both of these problems are fixed in the latest compat-wireless.
>>
>> Larry
>>
> Kernel is Linux C1 3.1.0-rc6linux-next1.01-next-20110919 #1 SMP Mon
> Sep 19 14:23:56 CEST 2011 x86_64 x86_64 x86_64 GNU/Linux
> I tried to apply the latest compat-wireless but errors are the same.
>
> Chiefdome
I tried at least wireless-next but the adapter isn't showing up.
Where to get more log files and stuff?
Isnt this adapter good supported by the rtl8192cu driver or where is the
problem?
Kind Regards
Chiefdome
On 09/19/2011 09:27 PM, Chiefdome wrote:
> On 09/20/2011 04:10 AM, Chiefdome wrote:
>> Hi there,
>>
>> i just bought an Alfa AWUS036NHR for testing.
>> It runs with the rtl8192cu driver.
>> I have a question because sometimes the wireless adapter dont shows any
>> networks no longer.
>> I have to reload the module an then its showing some networks.
>>
>> In dmesg it shows:
>>
>> [ 262.219575] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> [ 269.770133] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> [ 270.947047] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>
>>
>> For any further output please let me know.
> A complete dmesg output can be seen here, because theres also a problem when
> associating to a network:
>
> [ 1455.353142] cfg80211: All devices are disconnected, going to restore
> regulatory settings
> [ 1455.353155] cfg80211: Restoring regulatory settings
> [ 1455.353165] cfg80211: Calling CRDA to update world regulatory domain
> [ 1455.361425] cfg80211: Ignoring regulatory request Set by core since the
> driver uses its own custom regulatory domain
> [ 1455.361436] cfg80211: Ignoring regulatory request Set by core since the
> driver uses its own custom regulatory domain
> [ 1455.361442] cfg80211: World regulatory domain updated:
> [ 1455.361447] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain,
> max_eirp)
> [ 1455.361454] cfg80211: (2400000 KHz - 2494000 KHz @ 40000 KHz), (N/A, 3301 mBm)
> [ 1455.361460] cfg80211: (4910000 KHz - 5895000 KHz @ 40000 KHz), (N/A, 3301 mBm)
> [ 1455.403456] iwlagn 0000:03:00.0: L1 Disabled; Enabling L0S
> [ 1455.403856] iwlagn 0000:03:00.0: Radio type=0x0-0x2-0x0
> [ 1455.459585] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 1455.950477] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
> [ 1456.010220] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
> [ 1456.011668] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 1495.264204] rtl8192cu: MAC auto ON okay!
> [ 1495.299099] rtl8192cu: Tx queue select: 0x05
> [ 1495.299880] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin
> [ 1495.709590] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 1500.741392] usbcore: deregistering interface driver rtl8192cu
> [ 1505.097104] rtl8192cu: MAC address: 00:c0:ca:52:cb:4c
> [ 1505.097116] rtl8192cu: Board Type 1
> [ 1505.102441] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
> [ 1505.102454] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 1505.102462] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
> [ 1505.102468] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 1505.102475] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
> [ 1505.102480] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 1505.102487] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
> [ 1505.102493] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 1505.102499] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
> [ 1505.102505] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 1505.102511] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
> [ 1505.102517] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 1505.102523] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
> [ 1505.102529] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 1505.102536] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
> [ 1505.102541] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 1505.102548] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
> [ 1505.102553] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 1505.102560] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
> [ 1505.102565] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 1505.102572] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
> [ 1505.102578] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 1505.102584] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi, 2000 mBm)
> [ 1505.102590] cfg80211: Disabling freq 2467 MHz as custom regd has no rule that
> fits a 20 MHz wide channel
> [ 1505.102595] cfg80211: Disabling freq 2472 MHz as custom regd has no rule that
> fits a 20 MHz wide channel
> [ 1505.102601] cfg80211: Disabling freq 2484 MHz as custom regd has no rule that
> fits a 20 MHz wide channel
> [ 1505.103549] cfg80211: Ignoring regulatory request Set by core since the
> driver uses its own custom regulatory domain
> [ 1505.103803] ieee80211 phy2: Selected rate control algorithm 'rtl_rc'
> [ 1505.105949] usbcore: registered new interface driver rtl8192cu
> [ 1513.004969] rtl8192cu: MAC auto ON okay!
> [ 1513.038127] rtl8192cu: Tx queue select: 0x05
> [ 1513.038878] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin
> [ 1513.443284] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 1519.568596] rtl8192cu: MAC auto ON okay!
> [ 1519.601476] rtl8192cu: Tx queue select: 0x05
> [ 1519.602253] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin
> [ 1520.008221] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 1520.350447] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
> [ 1520.410244] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
> [ 1520.411607] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 1520.619096] rtl8192cu: MAC auto ON okay!
> [ 1520.651975] rtl8192cu: Tx queue select: 0x05
> [ 1520.652755] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin
> [ 1521.060567] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 1524.272807] wlan1: authenticate with [MAC-ADDRESS] (try 1)
> [ 1524.299985] wlan1: authenticated
> [ 1524.300029] wlan1: associate with [MAC-ADDRESS] (try 1)
> [ 1524.309323] wlan1: RX AssocResp from [MAC-ADDRESS] (capab=0x431 status=0 aid=1)
> [ 1524.309331] wlan1: associated
> [ 1524.311767] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
> [ 1525.172880] type=1400 audit(1316485102.702:35): apparmor="DENIED"
> operation="open" parent=5409 profile="/sbin/dhclient"
> name="/var/lib/wicd/dhclient.conf" pid=5445 comm="dhclient" requested_mask="r"
> denied_mask="r" fsuid=0 ouid=0
> [ 1534.590028] wlan1: no IPv6 routers present
What kernel? There are some problems with kernels prior to 3.1 in connecting to
802.11n networks, and also a problem in clearing the keys. Both of these
problems are fixed in the latest compat-wireless.
Larry
On 09/21/2011 10:39 PM, Chiefdome wrote:
> On 09/21/2011 10:37 PM, Larry Finger wrote:
>> On 09/21/2011 03:28 PM, Chiefdome wrote:
>>> The AP showen above is configured as you say as an 802.11bgn device.
>>> The
>>> wireless connection is controlled by wicd.
>>
>> I just reviewed our entire correspondence on this issue. I could not
>> find where you specified the make and model of the AP.
>>
>> I have never used wicd, but several people on the openSUSE forums
>> abandoned it because it was buggy. Are you sure it is not the problem?
>>
>> Larry
>>
> I also have a built-in iwlagn-wireless-card wicd is seriously not the
> problem.
> What would you suggest to use to make a wireless connection from the gui?
> With network-manager I have the same problems.
>
> Chiefdome
Sorry I forgot to say what the AP is, it is a FritzBox 7270 v2.
On 09/21/2011 03:41 PM, Chiefdome wrote:
> On 09/21/2011 10:39 PM, Chiefdome wrote:
>> On 09/21/2011 10:37 PM, Larry Finger wrote:
>>> On 09/21/2011 03:28 PM, Chiefdome wrote:
>>>> The AP showen above is configured as you say as an 802.11bgn device. The
>>>> wireless connection is controlled by wicd.
>>>
>>> I just reviewed our entire correspondence on this issue. I could not find
>>> where you specified the make and model of the AP.
>>>
>>> I have never used wicd, but several people on the openSUSE forums abandoned
>>> it because it was buggy. Are you sure it is not the problem?
>>>
>>> Larry
>>>
>> I also have a built-in iwlagn-wireless-card wicd is seriously not the problem.
>> What would you suggest to use to make a wireless connection from the gui?
>> With network-manager I have the same problems.
>>
>> Chiefdome
>
> Sorry I forgot to say what the AP is, it is a FritzBox 7270 v2.
It seems that we are converging on an incompatibility between that FritzBox 7270
and rtl8192cu as a problem.
*George* Do you have one in your Lab? As the price on EBay is $275 US, I'm not
very interested in getting one.
*Chiefdome* Would it be possible for you to run Wireshark on some other machine
and send us the capture file for the attempt to connect? When you use WPA-TKIP
encryption, does it work? I would also appreciate your using 'git log' and
verify that commits bac2555c6d863871329 and 3401dc6eba788ebc7c is present in
your source.
Larry
hello larry,
i've an ALFA AWUS036NHR and i tried latest compat-wireless-2011-09-27 on ubuntu
natty 3.0.4-030004-generic,
the adapter is recognized as rtl8192cu but is not
responding, no network is detected.
Then if i try to "modprobe -r rtl8192cu" results
FATAL: Error removing rtl8192cu
(/lib/modules/3.0.4-030004-generic/updates/drivers/net/wireless/rtlwifi
/rtl8192cu/rtl8192cu.ko):
Device or resource busy
seems that remains blocked..i can't do anything
tried dmesg and it says
.....
.....
[ 2610.093638] rtlwifi: reg 0xc1c, usbctrl_vendorreq TimeOut! status:0xfffffff4
value=0xed827478
[ 2610.093645] xhci_hcd 0000:05:00.0: ERROR no room on ep ring
[ 2610.093650] rtlwifi: reg 0xc4c, usbctrl_vendorreq TimeOut! status:0xfffffff4
value=0xed827478
[ 2610.093656] xhci_hcd 0000:05:00.0: ERROR no room on ep ring
[ 2610.093662] rtlwifi: reg 0xc78, usbctrl_vendorreq TimeOut! status:0xfffffff4
value=0xed827478
[ 2610.093668] xhci_hcd 0000:05:00.0: ERROR no room on ep ring
[ 2610.093683] rtlwifi: reg 0xc80, usbctrl_vendorreq TimeOut! status:0xfffffff4
value=0xed827478
[ 2610.234960] xhci_hcd 0000:05:00.0: ERROR no room on ep ring
[ 2610.255767] ADDRCONF(NETDEV_UP): wlan1: link is not ready
don't know what to do, waiting for an help :)
ok thx for reply, i just like to say to you that i have tryed beini tiny core
1.2.3 that was patched to support this type of usb device with the latest
update, and it works with rtl8192cu (and the blue led is working)
i've extracted a .tce module from the beini that seems to be rtl8192cu modded
driver,
this is the link i've uploaded on fileserve
http://www.fileserve.com/file/9mZxX5T/x_rtl8188ru_20110812.tce
maybe it could be useful, thx :)
On 09/21/2011 04:43 AM, Chiefdome wrote:
> I tried the latest git repo from
> git://git.infradead.org/users/linville/wireless-next.
> Same story here.
> After disconnecting to the network, I have to reload the module only then
> networks are seen.
I just cloned the wireless-next tree. The two patches mentioned in my previous
Email are included.
Please run the following command sequence and send us the dmesg output after
your failure occurs:
modprobe -rv rtl8192cu
modprobe -v rtlwifi debug=3
modprobe -v rtl8192cu
Larry
On 09/20/2011 05:05 AM, Larry Finger wrote:
> On 09/19/2011 09:27 PM, Chiefdome wrote:
>> On 09/20/2011 04:10 AM, Chiefdome wrote:
>>> Hi there,
>>>
>>> i just bought an Alfa AWUS036NHR for testing.
>>> It runs with the rtl8192cu driver.
>>> I have a question because sometimes the wireless adapter dont shows any
>>> networks no longer.
>>> I have to reload the module an then its showing some networks.
>>>
>>> In dmesg it shows:
>>>
>>> [ 262.219575] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>> [ 269.770133] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>> [ 270.947047] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>>
>>>
>>> For any further output please let me know.
>> A complete dmesg output can be seen here, because theres also a
>> problem when
>> associating to a network:
>>
>> [ 1455.353142] cfg80211: All devices are disconnected, going to restore
>> regulatory settings
>> [ 1455.353155] cfg80211: Restoring regulatory settings
>> [ 1455.353165] cfg80211: Calling CRDA to update world regulatory domain
>> [ 1455.361425] cfg80211: Ignoring regulatory request Set by core
>> since the
>> driver uses its own custom regulatory domain
>> [ 1455.361436] cfg80211: Ignoring regulatory request Set by core
>> since the
>> driver uses its own custom regulatory domain
>> [ 1455.361442] cfg80211: World regulatory domain updated:
>> [ 1455.361447] cfg80211: (start_freq - end_freq @ bandwidth),
>> (max_antenna_gain,
>> max_eirp)
>> [ 1455.361454] cfg80211: (2400000 KHz - 2494000 KHz @ 40000 KHz),
>> (N/A, 3301 mBm)
>> [ 1455.361460] cfg80211: (4910000 KHz - 5895000 KHz @ 40000 KHz),
>> (N/A, 3301 mBm)
>> [ 1455.403456] iwlagn 0000:03:00.0: L1 Disabled; Enabling L0S
>> [ 1455.403856] iwlagn 0000:03:00.0: Radio type=0x0-0x2-0x0
>> [ 1455.459585] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>> [ 1455.950477] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
>> [ 1456.010220] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
>> [ 1456.011668] ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [ 1495.264204] rtl8192cu: MAC auto ON okay!
>> [ 1495.299099] rtl8192cu: Tx queue select: 0x05
>> [ 1495.299880] rtl8192c_common: Loading firmware file
>> rtlwifi/rtl8192cufw.bin
>> [ 1495.709590] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> [ 1500.741392] usbcore: deregistering interface driver rtl8192cu
>> [ 1505.097104] rtl8192cu: MAC address: 00:c0:ca:52:cb:4c
>> [ 1505.097116] rtl8192cu: Board Type 1
>> [ 1505.102441] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
>> [ 1505.102454] cfg80211: Updating information on frequency 2412 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 1505.102462] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>> 2000 mBm)
>> [ 1505.102468] cfg80211: Updating information on frequency 2417 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 1505.102475] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>> 2000 mBm)
>> [ 1505.102480] cfg80211: Updating information on frequency 2422 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 1505.102487] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>> 2000 mBm)
>> [ 1505.102493] cfg80211: Updating information on frequency 2427 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 1505.102499] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>> 2000 mBm)
>> [ 1505.102505] cfg80211: Updating information on frequency 2432 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 1505.102511] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>> 2000 mBm)
>> [ 1505.102517] cfg80211: Updating information on frequency 2437 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 1505.102523] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>> 2000 mBm)
>> [ 1505.102529] cfg80211: Updating information on frequency 2442 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 1505.102536] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>> 2000 mBm)
>> [ 1505.102541] cfg80211: Updating information on frequency 2447 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 1505.102548] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>> 2000 mBm)
>> [ 1505.102553] cfg80211: Updating information on frequency 2452 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 1505.102560] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>> 2000 mBm)
>> [ 1505.102565] cfg80211: Updating information on frequency 2457 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 1505.102572] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>> 2000 mBm)
>> [ 1505.102578] cfg80211: Updating information on frequency 2462 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 1505.102584] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
>> 2000 mBm)
>> [ 1505.102590] cfg80211: Disabling freq 2467 MHz as custom regd has
>> no rule that
>> fits a 20 MHz wide channel
>> [ 1505.102595] cfg80211: Disabling freq 2472 MHz as custom regd has
>> no rule that
>> fits a 20 MHz wide channel
>> [ 1505.102601] cfg80211: Disabling freq 2484 MHz as custom regd has
>> no rule that
>> fits a 20 MHz wide channel
>> [ 1505.103549] cfg80211: Ignoring regulatory request Set by core
>> since the
>> driver uses its own custom regulatory domain
>> [ 1505.103803] ieee80211 phy2: Selected rate control algorithm 'rtl_rc'
>> [ 1505.105949] usbcore: registered new interface driver rtl8192cu
>> [ 1513.004969] rtl8192cu: MAC auto ON okay!
>> [ 1513.038127] rtl8192cu: Tx queue select: 0x05
>> [ 1513.038878] rtl8192c_common: Loading firmware file
>> rtlwifi/rtl8192cufw.bin
>> [ 1513.443284] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> [ 1519.568596] rtl8192cu: MAC auto ON okay!
>> [ 1519.601476] rtl8192cu: Tx queue select: 0x05
>> [ 1519.602253] rtl8192c_common: Loading firmware file
>> rtlwifi/rtl8192cufw.bin
>> [ 1520.008221] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> [ 1520.350447] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
>> [ 1520.410244] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
>> [ 1520.411607] ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [ 1520.619096] rtl8192cu: MAC auto ON okay!
>> [ 1520.651975] rtl8192cu: Tx queue select: 0x05
>> [ 1520.652755] rtl8192c_common: Loading firmware file
>> rtlwifi/rtl8192cufw.bin
>> [ 1521.060567] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> [ 1524.272807] wlan1: authenticate with [MAC-ADDRESS] (try 1)
>> [ 1524.299985] wlan1: authenticated
>> [ 1524.300029] wlan1: associate with [MAC-ADDRESS] (try 1)
>> [ 1524.309323] wlan1: RX AssocResp from [MAC-ADDRESS] (capab=0x431
>> status=0 aid=1)
>> [ 1524.309331] wlan1: associated
>> [ 1524.311767] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
>> [ 1525.172880] type=1400 audit(1316485102.702:35): apparmor="DENIED"
>> operation="open" parent=5409 profile="/sbin/dhclient"
>> name="/var/lib/wicd/dhclient.conf" pid=5445 comm="dhclient"
>> requested_mask="r"
>> denied_mask="r" fsuid=0 ouid=0
>> [ 1534.590028] wlan1: no IPv6 routers present
>
> What kernel? There are some problems with kernels prior to 3.1 in
> connecting to 802.11n networks, and also a problem in clearing the
> keys. Both of these problems are fixed in the latest compat-wireless.
>
> Larry
>
Kernel is Linux C1 3.1.0-rc6linux-next1.01-next-20110919 #1 SMP Mon Sep
19 14:23:56 CEST 2011 x86_64 x86_64 x86_64 GNU/Linux
I tried to apply the latest compat-wireless but errors are the same.
Chiefdome
On 09/20/2011 04:10 AM, Chiefdome wrote:
> Hi there,
>
> i just bought an Alfa AWUS036NHR for testing.
> It runs with the rtl8192cu driver.
> I have a question because sometimes the wireless adapter dont shows
> any networks no longer.
> I have to reload the module an then its showing some networks.
>
> In dmesg it shows:
>
> [ 262.219575] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 269.770133] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 270.947047] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>
>
> For any further output please let me know.
A complete dmesg output can be seen here, because theres also a problem
when associating to a network:
[ 1455.353142] cfg80211: All devices are disconnected, going to restore
regulatory settings
[ 1455.353155] cfg80211: Restoring regulatory settings
[ 1455.353165] cfg80211: Calling CRDA to update world regulatory domain
[ 1455.361425] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[ 1455.361436] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[ 1455.361442] cfg80211: World regulatory domain updated:
[ 1455.361447] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 1455.361454] cfg80211: (2400000 KHz - 2494000 KHz @ 40000 KHz),
(N/A, 3301 mBm)
[ 1455.361460] cfg80211: (4910000 KHz - 5895000 KHz @ 40000 KHz),
(N/A, 3301 mBm)
[ 1455.403456] iwlagn 0000:03:00.0: L1 Disabled; Enabling L0S
[ 1455.403856] iwlagn 0000:03:00.0: Radio type=0x0-0x2-0x0
[ 1455.459585] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1455.950477] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
[ 1456.010220] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
[ 1456.011668] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1495.264204] rtl8192cu: MAC auto ON okay!
[ 1495.299099] rtl8192cu: Tx queue select: 0x05
[ 1495.299880] rtl8192c_common: Loading firmware file
rtlwifi/rtl8192cufw.bin
[ 1495.709590] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 1500.741392] usbcore: deregistering interface driver rtl8192cu
[ 1505.097104] rtl8192cu: MAC address: 00:c0:ca:52:cb:4c
[ 1505.097116] rtl8192cu: Board Type 1
[ 1505.102441] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 1505.102454] cfg80211: Updating information on frequency 2412 MHz for
a 20 MHz width channel with regulatory rule:
[ 1505.102462] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 1505.102468] cfg80211: Updating information on frequency 2417 MHz for
a 20 MHz width channel with regulatory rule:
[ 1505.102475] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 1505.102480] cfg80211: Updating information on frequency 2422 MHz for
a 20 MHz width channel with regulatory rule:
[ 1505.102487] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 1505.102493] cfg80211: Updating information on frequency 2427 MHz for
a 20 MHz width channel with regulatory rule:
[ 1505.102499] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 1505.102505] cfg80211: Updating information on frequency 2432 MHz for
a 20 MHz width channel with regulatory rule:
[ 1505.102511] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 1505.102517] cfg80211: Updating information on frequency 2437 MHz for
a 20 MHz width channel with regulatory rule:
[ 1505.102523] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 1505.102529] cfg80211: Updating information on frequency 2442 MHz for
a 20 MHz width channel with regulatory rule:
[ 1505.102536] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 1505.102541] cfg80211: Updating information on frequency 2447 MHz for
a 20 MHz width channel with regulatory rule:
[ 1505.102548] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 1505.102553] cfg80211: Updating information on frequency 2452 MHz for
a 20 MHz width channel with regulatory rule:
[ 1505.102560] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 1505.102565] cfg80211: Updating information on frequency 2457 MHz for
a 20 MHz width channel with regulatory rule:
[ 1505.102572] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 1505.102578] cfg80211: Updating information on frequency 2462 MHz for
a 20 MHz width channel with regulatory rule:
[ 1505.102584] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (N/A mBi,
2000 mBm)
[ 1505.102590] cfg80211: Disabling freq 2467 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 1505.102595] cfg80211: Disabling freq 2472 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 1505.102601] cfg80211: Disabling freq 2484 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 1505.103549] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[ 1505.103803] ieee80211 phy2: Selected rate control algorithm 'rtl_rc'
[ 1505.105949] usbcore: registered new interface driver rtl8192cu
[ 1513.004969] rtl8192cu: MAC auto ON okay!
[ 1513.038127] rtl8192cu: Tx queue select: 0x05
[ 1513.038878] rtl8192c_common: Loading firmware file
rtlwifi/rtl8192cufw.bin
[ 1513.443284] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 1519.568596] rtl8192cu: MAC auto ON okay!
[ 1519.601476] rtl8192cu: Tx queue select: 0x05
[ 1519.602253] rtl8192c_common: Loading firmware file
rtlwifi/rtl8192cufw.bin
[ 1520.008221] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 1520.350447] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
[ 1520.410244] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
[ 1520.411607] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1520.619096] rtl8192cu: MAC auto ON okay!
[ 1520.651975] rtl8192cu: Tx queue select: 0x05
[ 1520.652755] rtl8192c_common: Loading firmware file
rtlwifi/rtl8192cufw.bin
[ 1521.060567] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 1524.272807] wlan1: authenticate with [MAC-ADDRESS] (try 1)
[ 1524.299985] wlan1: authenticated
[ 1524.300029] wlan1: associate with [MAC-ADDRESS] (try 1)
[ 1524.309323] wlan1: RX AssocResp from [MAC-ADDRESS] (capab=0x431
status=0 aid=1)
[ 1524.309331] wlan1: associated
[ 1524.311767] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[ 1525.172880] type=1400 audit(1316485102.702:35): apparmor="DENIED"
operation="open" parent=5409 profile="/sbin/dhclient"
name="/var/lib/wicd/dhclient.conf" pid=5445 comm="dhclient"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 1534.590028] wlan1: no IPv6 routers present
On 09/21/2011 10:03 PM, Larry Finger wrote:
> On 09/21/2011 02:19 PM, Chiefdome wrote:
>> I have found another bug - it is impossible to me to connect a
>> WPA2-network -
>> here is the dmesg output for that - will send you the output for a
>> WEP-network
>> later then:
>>
>> [ 194.011573] ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [ 194.230135] rtl8192cu: MAC auto ON okay!
>> [ 194.263015] rtl8192cu: Tx queue select: 0x05
>> [ 194.263820] rtl8192c_common: Loading firmware file
>> rtlwifi/rtl8192cufw.bin
>> [ 194.670927] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> [ 237.379814] rtl8192cu: MAC auto ON okay!
>> [ 237.413488] rtl8192cu: Tx queue select: 0x05
>> [ 237.414243] rtl8192c_common: Loading firmware file
>> rtlwifi/rtl8192cufw.bin
>> [ 237.821229] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> [ 238.160462] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
>> [ 238.220187] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
>> [ 238.221641] ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [ 278.340442] usbcore: deregistering interface driver rtl8192cu
>> [ 326.145824] rtl8192cu:rtl92cu_read_eeprom_info():<0-0> Boot from EFUSE
>> [ 326.223617] rtl8192cu: MAC address: [MAC-ADDRESS]
>> [ 326.223629] rtl8192cu:_rtl92cu_read_adapter_info():<0-0> VID =
>> 0xbda PID = 0x817f
>> [ 326.223636] rtl8192cu: Board Type 1
>> [ 326.223641] rtl8192cu:_rtl92cu_hal_customized_behavior():<0-0> RT
>> Customized
>> ID: 0x00
>> [ 326.227751] rtlwifi:_rtl_usb_init():<0-0> USB EP(0x81),
>> MaxPacketSize=512
>> ,Interval=0.
>> [ 326.227762] rtlwifi:_rtl_usb_init():<0-0> USB EP(0x02),
>> MaxPacketSize=512
>> ,Interval=0.
>> [ 326.227770] rtlwifi:_rtl_usb_init():<0-0> USB EP(0x03),
>> MaxPacketSize=512
>> ,Interval=0.
>> [ 326.227777] rtlwifi:_rtl_usb_init():<0-0> USB EP(0x84),
>> MaxPacketSize=64
>> ,Interval=1.
>> [ 326.228202] rtl8192cu:_TwoOutEpMapping():<0-0> USB typical
>> Setting.....
>> [ 326.228209] rtlwifi:_rtl_usb_init_tx():<0-0> USB Max Bulk-out Size=512
>> [ 326.228217] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
>> [ 326.228223] rtlwifi:_rtl_init_hw_ht_capab():<0-0> 1T1R
>> [ 326.228234] cfg80211: Updating information on frequency 2412 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 326.228241] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
>> mBi, 2000 mBm)
>> [ 326.228247] cfg80211: Updating information on frequency 2417 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 326.228253] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
>> mBi, 2000 mBm)
>> [ 326.228259] cfg80211: Updating information on frequency 2422
>> MH00:1c:4a:03:b9:64z for a 20 MHz width channel with regulatory rule:
>> [ 326.228266] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
>> mBi, 2000 mBm)
>> [ 326.228271] cfg80211: Updating information on frequency 2427 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 326.228278] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
>> mBi, 2000 mBm)
>> [ 326.228284] cfg80211: Updating information on frequency 2432 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 326.228290] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
>> mBi, 2000 mBm)
>> [ 326.228296] cfg80211: Updating information on frequency 2437 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 326.228302] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
>> mBi, 2000 mBm)
>> [ 326.228308] cfg80211: Updating information on frequency 2442 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 326.228314] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
>> mBi, 2000 mBm)
>> [ 326.228320] cfg80211: Updating information on frequency 2447 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 326.228327] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
>> mBi, 2000 mBm)
>> [ 326.228332] cfg80211: Updating information on frequency 2452 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 326.228339] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
>> mBi, 2000 mBm)
>> [ 326.228344] cfg80211: Updating information on frequency 2457 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 326.228351] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
>> mBi, 2000 mBm)
>> [ 326.228356] cfg80211: Updating information on frequency 2462 MHz
>> for a 20 MHz
>> width channel with regulatory rule:
>> [ 326.228363] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
>> mBi, 2000 mBm)
>> [ 326.228369] cfg80211: Disabling freq 2467 MHz as custom regd has no
>> rule that
>> fits a 20 MHz wide channel
>> [ 326.228374] cfg80211: Disabling freq 2472 MHz as custom regd has no
>> rule that
>> fits a 20 MHz wide channel
>> [ 326.228380] cfg80211: Disabling freq 2484 MHz as custom regd has no
>> rule that
>> fits a 20 MHz wide channel
>> [ 326.228554] cfg80211: Ignoring regulatory request Set by core since
>> the driver
>> uses its own custom regulatory domain
>> [ 326.228881] ieee80211 phy2: Selected rate control algorithm 'rtl_rc'
>> [ 326.234614] usbcore: registered new interface driver rtl8192cu
>> [ 330.227015] rtl8192cu:_rtl92cu_init_power_on():<0-0> Autoload Done!
>> [ 330.228731] rtl8192cu: MAC auto ON okay!
>> [ 330.264497] rtl8192cu: Tx queue select: 0x05
>> [ 330.264507] rtl8192cu:rtl92c_set_network_type():<0-0> Set Network
>> type to NO
>> LINK!
>> [ 330.265249] rtl8192c_common:rtl92c_phy_set_bw_mode():<0-0> FALSE
>> driver sleep
>> or unload
>> [ 330.265265] rtl8192c_common: Loading firmware file
>> rtlwifi/rtl8192cufw.bin
>> [ 330.265269] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware
>> Version(63),
>> Signature(0x88c1),Size(32)
>> [ 330.658702] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set
>> RCR(0xf0002a0e) ###
>> [ 330.658734] rtl8192cu:rtl92cu_set_hw_reg():<0-0> Set
>> HW_VAR_RETRY_LIMIT(0x00000004)
>> [ 330.670568] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> [ 340.000671] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set
>> RCR(0xf0002a0e) ###
>> [ 340.016768] rtl8192cu:_rtl92cu_init_power_on():<0-0> Autoload Done!
>> [ 340.018500] rtl8192cu: MAC auto ON okay!
>> [ 340.051808] rtl8192cu: Tx queue select: 0x05
>> [ 340.051828] rtl8192cu:rtl92c_set_network_type():<0-0> Set Network
>> type to NO
>> LINK!
>> [ 340.052543] rtl8192c_common:rtl92c_phy_set_bw_mode():<0-0> FALSE
>> driver sleep
>> or unload
>> [ 340.052583] rtl8192c_common: Loading firmware file
>> rtlwifi/rtl8192cufw.bin
>> [ 340.052590] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware
>> Version(63),
>> Signature(0x88c1),Size(32)
>> [ 340.450345] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set
>> RCR(0xf0002ace) ###
>> [ 340.450367] rtl8192cu:rtl92cu_set_hw_reg():<0-0> Set
>> HW_VAR_RETRY_LIMIT(0x00000004)
>> [ 340.462324] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> [ 340.810935] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
>> [ 340.870239] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
>> [ 340.871685] ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [ 340.960624] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set
>> RCR(0xf0002a0e) ###
>> [ 341.088320] rtl8192cu:_rtl92cu_init_power_on():<0-0> Autoload Done!
>> [ 341.091812] rtl8192cu: MAC auto ON okay!
>> [ 341.128338] rtl8192cu: Tx queue select: 0x05
>> [ 341.128356] rtl8192cu:rtl92c_set_network_type():<0-0> Set Network
>> type to NO
>> LINK!
>> [ 341.129072] rtl8192c_common:rtl92c_phy_set_bw_mode():<0-0> FALSE
>> driver sleep
>> or unload
>> [ 341.129112] rtl8192c_common: Loading firmware file
>> rtlwifi/rtl8192cufw.bin
>> [ 341.129119] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware
>> Version(63),
>> Signature(0x88c1),Size(32)
>> [ 341.523259] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set
>> RCR(0xf0002ace) ###
>> [ 341.523296] rtl8192cu:rtl92cu_set_hw_reg():<0-0> Set
>> HW_VAR_RETRY_LIMIT(0x00000004)
>> [ 341.535132] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> [ 344.553546] wlan1: direct probe to [MAC-ADDRESS] (try 1/3)
>> [ 344.750275] wlan1: direct probe to [MAC-ADDRESS] (try 2/3)
>> [ 344.950061] wlan1: direct probe to [MAC-ADDRESS] (try 3/3)
>> [ 345.150150] wlan1: direct probe to [MAC-ADDRESS] timed out
>
> The first thing I notice is that you apparently do not have CRDA
> installed. A second thing is that the interface never comes up. As
> long as it remains down, it can never connect. How are you connecting?
> I'm using NetworkManager.
>
> The following is an excerpt from my dmesg log with debug=3 set when
> rtlwifi is loaded:
>
> [17268.232826] usbcore: registered new interface driver rtl8192cu
> [17268.352125] rtl8192cu:_rtl92cu_init_power_on():<0-0> Autoload Done!
> [17268.364205] rtl8192cu: MAC auto ON okay!
> [17269.148482] rtl8192cu: Tx queue select: 0x05
> [17269.149472] rtl8192cu:rtl92c_set_network_type():<0-0> Set Network
> type to NO LINK!
> [17269.159549] rtl8192c_common:rtl92c_phy_set_bw_mode():<0-0> FALSE
> driver sleep or unload
> [17269.161148] rtl8192c_common: Loading firmware file
> rtlwifi/rtl8192cufw.bin
> [17269.161177] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware
> Version(63), Signature(0x88c1),Size(32)
> [17270.343392] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set
> RCR(0xf0002a0e) ###
> [17270.345208] rtl8192cu:rtl92cu_set_hw_reg():<0-0> Set
> HW_VAR_RETRY_LIMIT(0x00000004)
> [17270.388005] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [17274.168628] wlan0: authenticate with c0:3f:0e:be:2b:44 (try 1)
> [17274.168756] rtlwifi:_rtl_usb_tx_preprocess():<200-1> MAC80211_LINKING
> [17274.173393] wlan0: authenticated
> [17274.259600] wlan0: associate with c0:3f:0e:be:2b:44 (try 1)
> [17274.267367] wlan0: RX AssocResp from c0:3f:0e:be:2b:44 (capab=0x411
> status=0 aid=1)
> [17274.267400] wlan0: associated
> [17274.267428] rtlwifi:rtl_op_sta_add():<0-0> Add sta addr is
> c0:3f:0e:be:2b:44
> [17274.267614] rtl8192cu:rtl92cu_update_hal_rate_table():<0-0> 0
> [17274.274103] rtlwifi:rtl_action_proc():<10000-1> Rx ACT_ADDBAREQ
> From :c0:3f:0e:be:2b:44
> [17274.322888] rtlwifi:rtl_op_bss_info_changed():<0-0> BSS_CHANGED_ASSOC
> [17274.325839] rtlwifi:rtl_op_bss_info_changed():<0-0> c0:3f:0e:be:2b:44
> [17274.336522] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set
> RCR(0xf0002ace) ###
> [17274.340812] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> [17274.340968] rtlwifi:rtl_action_proc():<200-1> Tx ACT_ADDBARSP From
> :00:1f:1f:c8:8e:cb
> [17274.358740] rtlwifi:rtl_op_set_key():<0-0> Using hardware based
> encryption for keyidx: 0, mac: c0:3f:0e:be:2b:44
> [17274.358799] rtlwifi:rtl_op_set_key():<0-0> alg:CCMP
> [17274.358818] rtlwifi:rtl_op_set_key():<0-0> set enable_hw_sec,
> key_type:4(OPEN:0 WEP40:1 TKIP:2 AES:4 WEP104:5)
> [17274.359178] rtlwifi:rtl_op_set_key():<0-0> set pairwise key
> [17274.359202] rtl8192cu:rtl92c_set_key():<0-0> add one entry
> [17274.359222] rtl8192cu:rtl92c_set_key():<0-0> set Pairwiase key
> [17274.359244] rtlwifi:rtl_cam_add_one_entry():<0-0> EntryNo:4,
> ulKeyId=0, ulEncAlg=4, ulUseDK=0 MacAddr c0:3f:0e:be:2b:44
> [17274.364992] rtlwifi:rtl_cam_add_one_entry():<0-0> <===
> [17274.367387] rtlwifi:rtl_op_set_key():<0-0> Using hardware based
> encryption for keyidx: 1, mac: ff:ff:ff:ff:ff:ff
> [17274.367434] rtlwifi:rtl_op_set_key():<0-0> alg:CCMP
> [17274.367457] rtlwifi:rtl_op_set_key():<0-0> set group key
> [17274.367483] rtl8192cu:rtl92c_set_key():<0-0> add one entry
> [17274.367506] rtl8192cu:rtl92c_set_key():<0-0> set group key
> [17274.367529] rtlwifi:rtl_cam_add_one_entry():<0-0> EntryNo:1,
> ulKeyId=1, ulEncAlg=4, ulUseDK=0 MacAddr ff:ff:ff:ff:ff:ff
> [17274.372787] rtlwifi:rtl_cam_add_one_entry():<0-0> <===
> [17274.416690] rtl8192cu:rtl92cu_update_hal_rate_table():<0-0> 15
> [17276.428211] rtl8192cu:rtl92cu_update_hal_rate_table():<0-0> 15
> [17280.412251] rtl8192cu:rtl92cu_update_hal_rate_table():<0-0> 15
> [17293.203904] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set
> RCR(0xf0002a0e) ###
> [17295.692077] rtlwifi:rtl_tx_agg_start():<0-0> on ra =
> c0:3f:0e:be:2b:44 tid = 0 seq:0
> [17295.692345] rtlwifi:rtl_action_proc():<200-1> Tx ACT_ADDBAREQ From
> :00:1f:1f:c8:8e:cb
> [17295.695093] rtlwifi:rtl_action_proc():<10000-1> Rx ACT_ADDBARSP
> From :c0:3f:0e:be:2b:44
> [17295.695400] rtlwifi:rtl_tx_agg_oper():<0-0> on ra =
> c0:3f:0e:be:2b:44 tid = 0
>
> As you notice, this connection uses the CCMP algorithm, i.e. it is
> with WPA2-AES. It is also an 802.11n. Just to test, I switched the AP
> to run only at 802.11g rates. That also worked.
>
> I need to know more about your setup. What AP and how is it
> configured? How do you control the wireless connection?
>
> Larry
The AP showen above is configured as you say as an 802.11bgn device. The
wireless connection is controlled by wicd.
Chiefdome
On 09/21/2011 02:19 PM, Chiefdome wrote:
> I have found another bug - it is impossible to me to connect a WPA2-network -
> here is the dmesg output for that - will send you the output for a WEP-network
> later then:
>
> [ 194.011573] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 194.230135] rtl8192cu: MAC auto ON okay!
> [ 194.263015] rtl8192cu: Tx queue select: 0x05
> [ 194.263820] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin
> [ 194.670927] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 237.379814] rtl8192cu: MAC auto ON okay!
> [ 237.413488] rtl8192cu: Tx queue select: 0x05
> [ 237.414243] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin
> [ 237.821229] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 238.160462] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
> [ 238.220187] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
> [ 238.221641] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 278.340442] usbcore: deregistering interface driver rtl8192cu
> [ 326.145824] rtl8192cu:rtl92cu_read_eeprom_info():<0-0> Boot from EFUSE
> [ 326.223617] rtl8192cu: MAC address: [MAC-ADDRESS]
> [ 326.223629] rtl8192cu:_rtl92cu_read_adapter_info():<0-0> VID = 0xbda PID = 0x817f
> [ 326.223636] rtl8192cu: Board Type 1
> [ 326.223641] rtl8192cu:_rtl92cu_hal_customized_behavior():<0-0> RT Customized
> ID: 0x00
> [ 326.227751] rtlwifi:_rtl_usb_init():<0-0> USB EP(0x81), MaxPacketSize=512
> ,Interval=0.
> [ 326.227762] rtlwifi:_rtl_usb_init():<0-0> USB EP(0x02), MaxPacketSize=512
> ,Interval=0.
> [ 326.227770] rtlwifi:_rtl_usb_init():<0-0> USB EP(0x03), MaxPacketSize=512
> ,Interval=0.
> [ 326.227777] rtlwifi:_rtl_usb_init():<0-0> USB EP(0x84), MaxPacketSize=64
> ,Interval=1.
> [ 326.228202] rtl8192cu:_TwoOutEpMapping():<0-0> USB typical Setting.....
> [ 326.228209] rtlwifi:_rtl_usb_init_tx():<0-0> USB Max Bulk-out Size=512
> [ 326.228217] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
> [ 326.228223] rtlwifi:_rtl_init_hw_ht_capab():<0-0> 1T1R
> [ 326.228234] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 326.228241] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
> [ 326.228247] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 326.228253] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
> [ 326.228259] cfg80211: Updating information on frequency 2422
> MH00:1c:4a:03:b9:64z for a 20 MHz width channel with regulatory rule:
> [ 326.228266] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
> [ 326.228271] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 326.228278] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
> [ 326.228284] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 326.228290] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
> [ 326.228296] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 326.228302] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
> [ 326.228308] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 326.228314] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
> [ 326.228320] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 326.228327] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
> [ 326.228332] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 326.228339] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
> [ 326.228344] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 326.228351] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
> [ 326.228356] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz
> width channel with regulatory rule:
> [ 326.228363] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
> [ 326.228369] cfg80211: Disabling freq 2467 MHz as custom regd has no rule that
> fits a 20 MHz wide channel
> [ 326.228374] cfg80211: Disabling freq 2472 MHz as custom regd has no rule that
> fits a 20 MHz wide channel
> [ 326.228380] cfg80211: Disabling freq 2484 MHz as custom regd has no rule that
> fits a 20 MHz wide channel
> [ 326.228554] cfg80211: Ignoring regulatory request Set by core since the driver
> uses its own custom regulatory domain
> [ 326.228881] ieee80211 phy2: Selected rate control algorithm 'rtl_rc'
> [ 326.234614] usbcore: registered new interface driver rtl8192cu
> [ 330.227015] rtl8192cu:_rtl92cu_init_power_on():<0-0> Autoload Done!
> [ 330.228731] rtl8192cu: MAC auto ON okay!
> [ 330.264497] rtl8192cu: Tx queue select: 0x05
> [ 330.264507] rtl8192cu:rtl92c_set_network_type():<0-0> Set Network type to NO
> LINK!
> [ 330.265249] rtl8192c_common:rtl92c_phy_set_bw_mode():<0-0> FALSE driver sleep
> or unload
> [ 330.265265] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin
> [ 330.265269] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware Version(63),
> Signature(0x88c1),Size(32)
> [ 330.658702] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set RCR(0xf0002a0e) ###
> [ 330.658734] rtl8192cu:rtl92cu_set_hw_reg():<0-0> Set
> HW_VAR_RETRY_LIMIT(0x00000004)
> [ 330.670568] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 340.000671] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set RCR(0xf0002a0e) ###
> [ 340.016768] rtl8192cu:_rtl92cu_init_power_on():<0-0> Autoload Done!
> [ 340.018500] rtl8192cu: MAC auto ON okay!
> [ 340.051808] rtl8192cu: Tx queue select: 0x05
> [ 340.051828] rtl8192cu:rtl92c_set_network_type():<0-0> Set Network type to NO
> LINK!
> [ 340.052543] rtl8192c_common:rtl92c_phy_set_bw_mode():<0-0> FALSE driver sleep
> or unload
> [ 340.052583] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin
> [ 340.052590] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware Version(63),
> Signature(0x88c1),Size(32)
> [ 340.450345] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set RCR(0xf0002ace) ###
> [ 340.450367] rtl8192cu:rtl92cu_set_hw_reg():<0-0> Set
> HW_VAR_RETRY_LIMIT(0x00000004)
> [ 340.462324] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 340.810935] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
> [ 340.870239] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
> [ 340.871685] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 340.960624] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set RCR(0xf0002a0e) ###
> [ 341.088320] rtl8192cu:_rtl92cu_init_power_on():<0-0> Autoload Done!
> [ 341.091812] rtl8192cu: MAC auto ON okay!
> [ 341.128338] rtl8192cu: Tx queue select: 0x05
> [ 341.128356] rtl8192cu:rtl92c_set_network_type():<0-0> Set Network type to NO
> LINK!
> [ 341.129072] rtl8192c_common:rtl92c_phy_set_bw_mode():<0-0> FALSE driver sleep
> or unload
> [ 341.129112] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin
> [ 341.129119] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware Version(63),
> Signature(0x88c1),Size(32)
> [ 341.523259] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set RCR(0xf0002ace) ###
> [ 341.523296] rtl8192cu:rtl92cu_set_hw_reg():<0-0> Set
> HW_VAR_RETRY_LIMIT(0x00000004)
> [ 341.535132] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 344.553546] wlan1: direct probe to [MAC-ADDRESS] (try 1/3)
> [ 344.750275] wlan1: direct probe to [MAC-ADDRESS] (try 2/3)
> [ 344.950061] wlan1: direct probe to [MAC-ADDRESS] (try 3/3)
> [ 345.150150] wlan1: direct probe to [MAC-ADDRESS] timed out
The first thing I notice is that you apparently do not have CRDA installed. A
second thing is that the interface never comes up. As long as it remains down,
it can never connect. How are you connecting? I'm using NetworkManager.
The following is an excerpt from my dmesg log with debug=3 set when rtlwifi is
loaded:
[17268.232826] usbcore: registered new interface driver rtl8192cu
[17268.352125] rtl8192cu:_rtl92cu_init_power_on():<0-0> Autoload Done!
[17268.364205] rtl8192cu: MAC auto ON okay!
[17269.148482] rtl8192cu: Tx queue select: 0x05
[17269.149472] rtl8192cu:rtl92c_set_network_type():<0-0> Set Network type to NO
LINK!
[17269.159549] rtl8192c_common:rtl92c_phy_set_bw_mode():<0-0> FALSE driver sleep
or unload
[17269.161148] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin
[17269.161177] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware Version(63),
Signature(0x88c1),Size(32)
[17270.343392] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set RCR(0xf0002a0e) ###
[17270.345208] rtl8192cu:rtl92cu_set_hw_reg():<0-0> Set
HW_VAR_RETRY_LIMIT(0x00000004)
[17270.388005] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[17274.168628] wlan0: authenticate with c0:3f:0e:be:2b:44 (try 1)
[17274.168756] rtlwifi:_rtl_usb_tx_preprocess():<200-1> MAC80211_LINKING
[17274.173393] wlan0: authenticated
[17274.259600] wlan0: associate with c0:3f:0e:be:2b:44 (try 1)
[17274.267367] wlan0: RX AssocResp from c0:3f:0e:be:2b:44 (capab=0x411 status=0
aid=1)
[17274.267400] wlan0: associated
[17274.267428] rtlwifi:rtl_op_sta_add():<0-0> Add sta addr is c0:3f:0e:be:2b:44
[17274.267614] rtl8192cu:rtl92cu_update_hal_rate_table():<0-0> 0
[17274.274103] rtlwifi:rtl_action_proc():<10000-1> Rx ACT_ADDBAREQ From
:c0:3f:0e:be:2b:44
[17274.322888] rtlwifi:rtl_op_bss_info_changed():<0-0> BSS_CHANGED_ASSOC
[17274.325839] rtlwifi:rtl_op_bss_info_changed():<0-0> c0:3f:0e:be:2b:44
[17274.336522] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set RCR(0xf0002ace) ###
[17274.340812] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[17274.340968] rtlwifi:rtl_action_proc():<200-1> Tx ACT_ADDBARSP From
:00:1f:1f:c8:8e:cb
[17274.358740] rtlwifi:rtl_op_set_key():<0-0> Using hardware based encryption
for keyidx: 0, mac: c0:3f:0e:be:2b:44
[17274.358799] rtlwifi:rtl_op_set_key():<0-0> alg:CCMP
[17274.358818] rtlwifi:rtl_op_set_key():<0-0> set enable_hw_sec,
key_type:4(OPEN:0 WEP40:1 TKIP:2 AES:4 WEP104:5)
[17274.359178] rtlwifi:rtl_op_set_key():<0-0> set pairwise key
[17274.359202] rtl8192cu:rtl92c_set_key():<0-0> add one entry
[17274.359222] rtl8192cu:rtl92c_set_key():<0-0> set Pairwiase key
[17274.359244] rtlwifi:rtl_cam_add_one_entry():<0-0> EntryNo:4, ulKeyId=0,
ulEncAlg=4, ulUseDK=0 MacAddr c0:3f:0e:be:2b:44
[17274.364992] rtlwifi:rtl_cam_add_one_entry():<0-0> <===
[17274.367387] rtlwifi:rtl_op_set_key():<0-0> Using hardware based encryption
for keyidx: 1, mac: ff:ff:ff:ff:ff:ff
[17274.367434] rtlwifi:rtl_op_set_key():<0-0> alg:CCMP
[17274.367457] rtlwifi:rtl_op_set_key():<0-0> set group key
[17274.367483] rtl8192cu:rtl92c_set_key():<0-0> add one entry
[17274.367506] rtl8192cu:rtl92c_set_key():<0-0> set group key
[17274.367529] rtlwifi:rtl_cam_add_one_entry():<0-0> EntryNo:1, ulKeyId=1,
ulEncAlg=4, ulUseDK=0 MacAddr ff:ff:ff:ff:ff:ff
[17274.372787] rtlwifi:rtl_cam_add_one_entry():<0-0> <===
[17274.416690] rtl8192cu:rtl92cu_update_hal_rate_table():<0-0> 15
[17276.428211] rtl8192cu:rtl92cu_update_hal_rate_table():<0-0> 15
[17280.412251] rtl8192cu:rtl92cu_update_hal_rate_table():<0-0> 15
[17293.203904] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set RCR(0xf0002a0e) ###
[17295.692077] rtlwifi:rtl_tx_agg_start():<0-0> on ra = c0:3f:0e:be:2b:44 tid =
0 seq:0
[17295.692345] rtlwifi:rtl_action_proc():<200-1> Tx ACT_ADDBAREQ From
:00:1f:1f:c8:8e:cb
[17295.695093] rtlwifi:rtl_action_proc():<10000-1> Rx ACT_ADDBARSP From
:c0:3f:0e:be:2b:44
[17295.695400] rtlwifi:rtl_tx_agg_oper():<0-0> on ra = c0:3f:0e:be:2b:44 tid = 0
As you notice, this connection uses the CCMP algorithm, i.e. it is with
WPA2-AES. It is also an 802.11n. Just to test, I switched the AP to run only at
802.11g rates. That also worked.
I need to know more about your setup. What AP and how is it configured? How do
you control the wireless connection?
Larry
On 09/20/2011 04:38 PM, Chiefdome wrote:
> I tried at least wireless-next but the adapter isn't showing up.
> Where to get more log files and stuff?
> Isnt this adapter good supported by the rtl8192cu driver or where is the problem?
For the mainline kernel to work with 802.11n-only APs and to reconnect after an
initial try, your kernel needs the following patches:
commit bac2555c6d86387132930af4d14cb47c4dd3f4f7
Author: George <[email protected]>
Date: Sat Sep 3 10:58:48 2011 -0500
rtlwifi: Fix problem when switching connections
The driver fails to clear encryption keys making it impossible
to switch connections.
Signed-off-by: George <[email protected]>
Signed-off-by: Larry Finger <[email protected]>
Cc: Stable <[email protected]> [2.6.39+]
Signed-off-by: John W. Linville <[email protected]>
commit 3401dc6eba788ebc7c14ce51018d775b1c263399
Author: George <[email protected]>
Date: Sat Sep 3 10:58:47 2011 -0500
rtlwifi: rtl8192su: Fix problem connecting to HT-enabled AP
The driver fails to connect to 802.11n-enabled APs. The patch fixes
Bug #42262.
Signed-off-by: George <[email protected]>
Signed-off-by: Larry Finger <[email protected]>
Cc: Stable <[email protected]> [2.6.39+]
Signed-off-by: John W. Linville <[email protected]>
Both of these are in wireless-testing, and were just merged into the mainline
kernel. In addition, they were merged with the 3.0 stable tree today.
Both should be in wireless-next, but as I recall, you were not able to test with
that tree.
With the updated mainline kernel, the link is stable and performance is
acceptible with netperf TCP_STREAM (TX) at 20.5 +/- 4.8 Mbps and TCP_MAERTS (RX)
of 21.7 +/- 3.8 Mbps. These numbers are not spectacular, but they will do.
Larry
On 09/21/2011 10:37 PM, Larry Finger wrote:
> On 09/21/2011 03:28 PM, Chiefdome wrote:
>> The AP showen above is configured as you say as an 802.11bgn device. The
>> wireless connection is controlled by wicd.
>
> I just reviewed our entire correspondence on this issue. I could not
> find where you specified the make and model of the AP.
>
> I have never used wicd, but several people on the openSUSE forums
> abandoned it because it was buggy. Are you sure it is not the problem?
>
> Larry
>
I also have a built-in iwlagn-wireless-card wicd is seriously not the
problem.
What would you suggest to use to make a wireless connection from the gui?
With network-manager I have the same problems.
Chiefdome
On 09/30/2011 09:20 AM, v4mp wrote:
> hello larry,
>
> i've an ALFA AWUS036NHR and i tried latest compat-wireless-2011-09-27 on ubuntu
> natty 3.0.4-030004-generic,
> the adapter is recognized as rtl8192cu but is not
> responding, no network is detected.
>
> Then if i try to "modprobe -r rtl8192cu" results
> FATAL: Error removing rtl8192cu
> (/lib/modules/3.0.4-030004-generic/updates/drivers/net/wireless/rtlwifi
> /rtl8192cu/rtl8192cu.ko):
> Device or resource busy
>
> seems that remains blocked..i can't do anything
You are the second person that has reported a problem with this device.
Unfortunately, I do not have a sample of the device, but I have just ordered one
that will be delivered in about one week. I would guess that there is some
difference between the RTL8192CU and the RTL8188RU chips.
I Cc'd the Realtek group that works on USB devices. Perhaps they have some info
that will be useful. Given the difference in time between the US and Taiwan, I
would not expect any answer until Monday.
There are some changes that affect connection with an 802.11n network that are
found in the latest kernels. I'm not sure they are in the one you are using. You
can get the very latest by downloading and building the "bleeding edge" version
of compat-wireless.
Larry
On 09/21/2011 04:45 PM, Larry Finger wrote:
> On 09/21/2011 04:43 AM, Chiefdome wrote:
>> I tried the latest git repo from
>> git://git.infradead.org/users/linville/wireless-next.
>> Same story here.
>> After disconnecting to the network, I have to reload the module only
>> then
>> networks are seen.
>
> I just cloned the wireless-next tree. The two patches mentioned in my
> previous Email are included.
>
> Please run the following command sequence and send us the dmesg output
> after your failure occurs:
>
> modprobe -rv rtl8192cu
> modprobe -v rtlwifi debug=3
> modprobe -v rtl8192cu
>
> Larry
I have found another bug - it is impossible to me to connect a
WPA2-network - here is the dmesg output for that - will send you the
output for a WEP-network later then:
[ 194.011573] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 194.230135] rtl8192cu: MAC auto ON okay!
[ 194.263015] rtl8192cu: Tx queue select: 0x05
[ 194.263820] rtl8192c_common: Loading firmware file
rtlwifi/rtl8192cufw.bin
[ 194.670927] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 237.379814] rtl8192cu: MAC auto ON okay!
[ 237.413488] rtl8192cu: Tx queue select: 0x05
[ 237.414243] rtl8192c_common: Loading firmware file
rtlwifi/rtl8192cufw.bin
[ 237.821229] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 238.160462] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
[ 238.220187] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
[ 238.221641] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 278.340442] usbcore: deregistering interface driver rtl8192cu
[ 326.145824] rtl8192cu:rtl92cu_read_eeprom_info():<0-0> Boot from EFUSE
[ 326.223617] rtl8192cu: MAC address: [MAC-ADDRESS]
[ 326.223629] rtl8192cu:_rtl92cu_read_adapter_info():<0-0> VID = 0xbda
PID = 0x817f
[ 326.223636] rtl8192cu: Board Type 1
[ 326.223641] rtl8192cu:_rtl92cu_hal_customized_behavior():<0-0> RT
Customized ID: 0x00
[ 326.227751] rtlwifi:_rtl_usb_init():<0-0> USB EP(0x81),
MaxPacketSize=512 ,Interval=0.
[ 326.227762] rtlwifi:_rtl_usb_init():<0-0> USB EP(0x02),
MaxPacketSize=512 ,Interval=0.
[ 326.227770] rtlwifi:_rtl_usb_init():<0-0> USB EP(0x03),
MaxPacketSize=512 ,Interval=0.
[ 326.227777] rtlwifi:_rtl_usb_init():<0-0> USB EP(0x84),
MaxPacketSize=64 ,Interval=1.
[ 326.228202] rtl8192cu:_TwoOutEpMapping():<0-0> USB typical Setting.....
[ 326.228209] rtlwifi:_rtl_usb_init_tx():<0-0> USB Max Bulk-out Size=512
[ 326.228217] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 326.228223] rtlwifi:_rtl_init_hw_ht_capab():<0-0> 1T1R
[ 326.228234] cfg80211: Updating information on frequency 2412 MHz for
a 20 MHz width channel with regulatory rule:
[ 326.228241] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
mBi, 2000 mBm)
[ 326.228247] cfg80211: Updating information on frequency 2417 MHz for
a 20 MHz width channel with regulatory rule:
[ 326.228253] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
mBi, 2000 mBm)
[ 326.228259] cfg80211: Updating information on frequency 2422
MH00:1c:4a:03:b9:64z for a 20 MHz width channel with regulatory rule:
[ 326.228266] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
mBi, 2000 mBm)
[ 326.228271] cfg80211: Updating information on frequency 2427 MHz for
a 20 MHz width channel with regulatory rule:
[ 326.228278] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
mBi, 2000 mBm)
[ 326.228284] cfg80211: Updating information on frequency 2432 MHz for
a 20 MHz width channel with regulatory rule:
[ 326.228290] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
mBi, 2000 mBm)
[ 326.228296] cfg80211: Updating information on frequency 2437 MHz for
a 20 MHz width channel with regulatory rule:
[ 326.228302] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
mBi, 2000 mBm)
[ 326.228308] cfg80211: Updating information on frequency 2442 MHz for
a 20 MHz width channel with regulatory rule:
[ 326.228314] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
mBi, 2000 mBm)
[ 326.228320] cfg80211: Updating information on frequency 2447 MHz for
a 20 MHz width channel with regulatory rule:
[ 326.228327] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
mBi, 2000 mBm)
[ 326.228332] cfg80211: Updating information on frequency 2452 MHz for
a 20 MHz width channel with regulatory rule:
[ 326.228339] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
mBi, 2000 mBm)
[ 326.228344] cfg80211: Updating information on frequency 2457 MHz for
a 20 MHz width channel with regulatory rule:
[ 326.228351] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
mBi, 2000 mBm)
[ 326.228356] cfg80211: Updating information on frequency 2462 MHz for
a 20 MHz width channel with regulatory rule:
[ 326.228363] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A
mBi, 2000 mBm)
[ 326.228369] cfg80211: Disabling freq 2467 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 326.228374] cfg80211: Disabling freq 2472 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 326.228380] cfg80211: Disabling freq 2484 MHz as custom regd has no
rule that fits a 20 MHz wide channel
[ 326.228554] cfg80211: Ignoring regulatory request Set by core since
the driver uses its own custom regulatory domain
[ 326.228881] ieee80211 phy2: Selected rate control algorithm 'rtl_rc'
[ 326.234614] usbcore: registered new interface driver rtl8192cu
[ 330.227015] rtl8192cu:_rtl92cu_init_power_on():<0-0> Autoload Done!
[ 330.228731] rtl8192cu: MAC auto ON okay!
[ 330.264497] rtl8192cu: Tx queue select: 0x05
[ 330.264507] rtl8192cu:rtl92c_set_network_type():<0-0> Set Network
type to NO LINK!
[ 330.265249] rtl8192c_common:rtl92c_phy_set_bw_mode():<0-0> FALSE
driver sleep or unload
[ 330.265265] rtl8192c_common: Loading firmware file
rtlwifi/rtl8192cufw.bin
[ 330.265269] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware
Version(63), Signature(0x88c1),Size(32)
[ 330.658702] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set
RCR(0xf0002a0e) ###
[ 330.658734] rtl8192cu:rtl92cu_set_hw_reg():<0-0> Set
HW_VAR_RETRY_LIMIT(0x00000004)
[ 330.670568] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 340.000671] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set
RCR(0xf0002a0e) ###
[ 340.016768] rtl8192cu:_rtl92cu_init_power_on():<0-0> Autoload Done!
[ 340.018500] rtl8192cu: MAC auto ON okay!
[ 340.051808] rtl8192cu: Tx queue select: 0x05
[ 340.051828] rtl8192cu:rtl92c_set_network_type():<0-0> Set Network
type to NO LINK!
[ 340.052543] rtl8192c_common:rtl92c_phy_set_bw_mode():<0-0> FALSE
driver sleep or unload
[ 340.052583] rtl8192c_common: Loading firmware file
rtlwifi/rtl8192cufw.bin
[ 340.052590] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware
Version(63), Signature(0x88c1),Size(32)
[ 340.450345] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set
RCR(0xf0002ace) ###
[ 340.450367] rtl8192cu:rtl92cu_set_hw_reg():<0-0> Set
HW_VAR_RETRY_LIMIT(0x00000004)
[ 340.462324] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 340.810935] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
[ 340.870239] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
[ 340.871685] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 340.960624] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set
RCR(0xf0002a0e) ###
[ 341.088320] rtl8192cu:_rtl92cu_init_power_on():<0-0> Autoload Done!
[ 341.091812] rtl8192cu: MAC auto ON okay!
[ 341.128338] rtl8192cu: Tx queue select: 0x05
[ 341.128356] rtl8192cu:rtl92c_set_network_type():<0-0> Set Network
type to NO LINK!
[ 341.129072] rtl8192c_common:rtl92c_phy_set_bw_mode():<0-0> FALSE
driver sleep or unload
[ 341.129112] rtl8192c_common: Loading firmware file
rtlwifi/rtl8192cufw.bin
[ 341.129119] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware
Version(63), Signature(0x88c1),Size(32)
[ 341.523259] rtl8192cu:rtl92cu_set_hw_reg():<0-0> ### Set
RCR(0xf0002ace) ###
[ 341.523296] rtl8192cu:rtl92cu_set_hw_reg():<0-0> Set
HW_VAR_RETRY_LIMIT(0x00000004)
[ 341.535132] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 344.553546] wlan1: direct probe to [MAC-ADDRESS] (try 1/3)
[ 344.750275] wlan1: direct probe to [MAC-ADDRESS] (try 2/3)
[ 344.950061] wlan1: direct probe to [MAC-ADDRESS] (try 3/3)
[ 345.150150] wlan1: direct probe to [MAC-ADDRESS] timed out
On 09/21/2011 03:28 PM, Chiefdome wrote:
> The AP showen above is configured as you say as an 802.11bgn device. The
> wireless connection is controlled by wicd.
I just reviewed our entire correspondence on this issue. I could not find where
you specified the make and model of the AP.
I have never used wicd, but several people on the openSUSE forums abandoned it
because it was buggy. Are you sure it is not the problem?
Larry
Hello,
I also have the AWUS036NHR device and I got it working on Ubuntu 11.04
2.6.38-11-generic x64. The only thing I did is to compile&install
compat-wireless-2.6.39-1 (same as beini!) which can be found here:
http://www.orbit-lab.org/kernel/compat-wireless-2.6-stable/v2.6.39/
There was only one strange thing: In drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
there is no entry for the AWUS036NHR so that no driver is loaded when I plugged
the USB in, but in older versions of compat-wireless (e.g. 2.6.38) there IS one
entry for this device. The entry looks like this:
/* 8188RU in Alfa AWUS036NHR */
{RTL_USB_DEVICE(USB_VENDER_ID_REALTEK, 0x817f, rtl92cu_hal_cfg)}
So I patched the file, compiled&installed it and everything worked! Could
someone patch the sources and add this device? Thanks!
Toddy
On 10/15/2011 09:22 AM, v4mp wrote:
>
>
> i've tried also kernel 3.1-rc9 with latest compat wireless 14-10-2011 and still
> don't work...it was recognized but no APs can be detected..the led of the alfa
> is off..seems that it is power off..
>
> i don't know about firmware, i see that there are .bin on lib/firmware/rtlwifi..
> how can i update them?
That depends on your distro, but please look at the output of the dmesg command
to see if there is an error loading the firmware.
You also need to install rfkill and look at the output of 'rfkill list'. If you
have another wireless device that is being hard blocked, or if there is a soft
block active, then rtl8192cu cannot work.
Note that the device works on my system. There should not be a problem with the
driver on your device once we clean up these questions. Once the device gets the
proper firmware and the RF is unblocked, the LED will light.
Larry
ok, i've checked the md5 checksum of the firmware and is ok,
i give you dmesg at pastebin.com
it has 2 parts: in the second part i can't see what is in previous of the error
the link is: http://pastebin.com/7tfcBfbD
yes, i know that the awus036h uses a different driver,
i just wanna say that it
has no conflicts with xhci_hcd as happen when loading
the rtl8192cu driver for the 036nhr
the driver i downloaded from realtek is what you can find here
http://www.alfa.com.tw /in/front/bin/ ptlist.phtml?Category=105397
for the awus036nhr, and it works fine without any kind of errors,
detection of APs and connections
every compat wireless i download does not with rtl8192cu and my alfa,
i tested all the specific kernel version of compat-wireless and the latest
bleeding edge compat wireless, i'm hating this fuckin errors :)
On 10/17/2011 12:09 PM, v4mp wrote:
>
>
> ok, i've checked the md5 checksum of the firmware and is ok,
> i give you dmesg at pastebin.com
>
> it has 2 parts: in the second part i can't see what is in previous of the error
>
> the link is: http://pastebin.com/7tfcBfbD
There are a number of USB errors, all occurring on the xhci controller. Do you
have any USB ports on different controllers? What is the output of lsusb?
Larry
On 10/08/2011 11:24 AM, Toddy wrote:
> Hello Larry,
>
> thanks for the quick reply! Yes I know this version is a bit older, but when I
> use the newest compat-wireless (eg.
> http://www.orbit-lab.org/kernel/compat-wireless-2.6/compat-wireless-2011-10-07.tar.bz2)
> the driver loads but some features like monitor-mode and packet injection
> doesn't work. The listing of available networks (with airodump) doesn't work
> too. Usually I have 13 channels because I live in Germany but if I use the
> newest driver I have only 11 channels. But if I use the older compat-wireless
> package all works fine.
The difference between 11 and 13 channels depends on your CRDA settings. Do you
have that package installed? Check the output of dmesg to see what domain is
being set. If you have CRDA installed, then you can force the use of Germany in
the domain by creating a file named /etc/modprobe.d/50-cfg80211.conf containing
a single line with "options cfg80211 ieee80211_regdom=DE" (without the quote marks).
You can get a list of available networks using iwconfig or iw. I know those work.
As I do not test, support, nor condone packet injection, I cannot speak to it
working on any driver.
Larry
i'm sorry but i don't know how to recompile kernel to apply this patch,
i'm using the 3.1.oneric.rc9 for ubuntu precompiled
can u recompile it with this patch,
and then send me the compiled kernel to install?
On 10/26/2011 10:49 AM, Chiefdome wrote:
> Is there a way to set the tx-power over 20dbm on the adapter?
> I thought it is able to do 2w. There is no way for me to get it over 20 dbm.
> When trying to to set the adapter with "iwconfig wlan1 set txpower 30" it answers
>
> Error for wireless request "Set Tx Power" (8B26) :
> SET failed on device wlan1 ; Invalid argument.
>
> I think there has to be done some work in the code but where do I start?
>
> Thanks for all replys.
The WEXT interface is deprecated. It is there as a convenience, but it will not
be extended. To change the power setting, you need to use the iw utility. The
specific commands are:
iw dev <devname> set txpower <auto|fixed|limit> [<tx power in mBm>]
or
iw phy <phyname> set txpower <auto|fixed|limit> [<tx power in mBm>]
The maximum power will be dependent on your regulatory domain setting.
Larry
i don't know why you are saying this, i was just kidding....
you take me too seriously...
i think i'm doing a favour to you too debugging this..
however with the rtl8192cu the hardware doesn't work with
the ep error related to xhci_hcd..
it is the point that we are now
there is something more can i do now?
i don't have any other usb port that works with other controller like ehci..
hello,
i've tried blacklisting xhci_hcd driver but when i disable it can't read nothing
from usb, also the usb mouse doesn't work
the problem should be here, i think they are usb 3.0 ports
the lsusb listes correctly that a realtek is connected
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0bda:817f Realtek Semiconductor Corp.
Bus 003 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0489:e00f Foxconn / Hon Hai
Bus 001 Device 003: ID 064e:2100 Suyin Corp.
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
thx
On 10/17/2011 05:07 AM, v4mp wrote:
>
> ok, i've attached the alfa and run rfkill list but it shows that there are no
> blocked devices, then i run modprobe rtl8192cu and strangely the alfa has
> lighted, but it doesn't work..
> i've done dmesg and seen this:
>
> [ 1218.079638] rtlwifi: reg 0xc80, usbctrl_vendorreq TimeOut! status:0xfffffff4
> value=0xed545b78
> [ 1218.079645] xhci_hcd 0000:05:00.0: ERROR no room on ep ring
> [ 1218.079650] rtlwifi: reg 0xc80, usbctrl_vendorreq TimeOut! status:0xfffffff4
> value=0xed545b78
> [ 1218.079657] xhci_hcd 0000:05:00.0: ERROR no room on ep ring
> [ 1218.079664] xhci_hcd 0000:05:00.0: ERROR no room on ep ring
> [ 1218.079669] rtlwifi: reg 0xc4c, usbctrl_vendorreq TimeOut! status:0xfffffff4
> value=0xed545b78
> [ 1218.079676] xhci_hcd 0000:05:00.0: ERROR no room on ep ring
> [ 1218.079682] xhci_hcd 0000:05:00.0: ERROR no room on ep ring
> [ 1218.079687] rtlwifi: reg 0xc94, usbctrl_vendorreq TimeOut! status:0xfffffff4
> value=0xed545b78
> [ 1218.241190] ADDRCONF(NETDEV_UP): wlan1: link is not ready
Those errors look as if the device was removed before unloading the driver. That
is a known problem with the driver.
> for the firmware i don't know how to update it, i'm using ubuntu 11.04 natty
> with 3.1.0-0301rc9-generic
> where can i download updated firmware to test it for this card?
> thx
The firmware is available in the linux-firmware git repo, and should be in your
distro's firmware package.
Only one version of the firmware has been published. The md5sum output is
943e9b714a926e630b8152d7aad91d2e /lib/firmware/rtlwifi/rtl8192cufw.bin.
Please reboot your system, try to connect, and then post your entire dmesg
output at pastebin.com. Report the link here.
Larry
On 10/19/2011 03:17 AM, v4mp wrote:
>
> i don't know why you are saying this, i was just kidding....
> you take me too seriously...
> i think i'm doing a favour to you too debugging this..
>
> however with the rtl8192cu the hardware doesn't work with
> the ep error related to xhci_hcd..
> it is the point that we are now
>
> there is something more can i do now?
> i don't have any other usb port that works with other controller like ehci..
You can set up usbmon and dump the starting USB traffic for rtl8192cu and for
the Alfa driver, but please do not let it run for a long time. Those dumps get
very long. Load the driver you want with the device unplugged, then plug in the
device, and dump the buffer 3-4 seconds later. The instructions for using usbmon
are at http://www.mjmwired.net/kernel/Documentation/usb/usbmon.txt or in
Documentation/usb/usbmon.txt in the source tree.
The other thing you could do is to plug in the device with rtl8192cu as the
driver and after 1 second dump the dmesg log with 'dmesg > dmesg.out'. In your
previous attempt, you let the buffer wrap around and important info was lost.
These logs should be posted at Pastebin.
I sent a request for info regarding this to the Chinese group that wrote the
driver, but I have not heard back.
Larry
ok, i've attached the alfa and run rfkill list but it shows that there are no
blocked devices, then i run modprobe rtl8192cu and strangely the alfa has
lighted, but it doesn't work..
i've done dmesg and seen this:
[ 1218.079638] rtlwifi: reg 0xc80, usbctrl_vendorreq TimeOut! status:0xfffffff4
value=0xed545b78
[ 1218.079645] xhci_hcd 0000:05:00.0: ERROR no room on ep ring
[ 1218.079650] rtlwifi: reg 0xc80, usbctrl_vendorreq TimeOut! status:0xfffffff4
value=0xed545b78
[ 1218.079657] xhci_hcd 0000:05:00.0: ERROR no room on ep ring
[ 1218.079664] xhci_hcd 0000:05:00.0: ERROR no room on ep ring
[ 1218.079669] rtlwifi: reg 0xc4c, usbctrl_vendorreq TimeOut! status:0xfffffff4
value=0xed545b78
[ 1218.079676] xhci_hcd 0000:05:00.0: ERROR no room on ep ring
[ 1218.079682] xhci_hcd 0000:05:00.0: ERROR no room on ep ring
[ 1218.079687] rtlwifi: reg 0xc94, usbctrl_vendorreq TimeOut! status:0xfffffff4
value=0xed545b78
[ 1218.241190] ADDRCONF(NETDEV_UP): wlan1: link is not ready
for the firmware i don't know how to update it, i'm using ubuntu 11.04 natty
with 3.1.0-0301rc9-generic
where can i download updated firmware to test it for this card?
thx
i've tried also kernel 3.1-rc9 with latest compat wireless 14-10-2011 and still
don't work...it was recognized but no APs can be detected..the led of the alfa
is off..seems that it is power off..
i don't know about firmware, i see that there are .bin on lib/firmware/rtlwifi..
how can i update them?
thx
On 10/09/2011 09:21 AM, v4mp wrote:
>
> Sorry, but i can't get this Alfa product to work with the latest bleeding edge
> compat-wireless-2011-10-08 on ubuntu 11.04, tryed with kernels 2.6.38-11,
> 2.6.39 rc4 and 3.0
>
> i tryed also the 2.6.39-1 version of compat-wireless
>
> Don't show anything in managed and monitor mode..
I do not know about monitor mode, but the Alfa device works in managed mode with
kernel 3.1-rc9 from both wireless-testing and mainline. I use NetworkManager.
All of this current code should be in the latest bleeding edge compat-wireless
version.
Have you installed the firmware?
Larry
ok, i've done what you asked me with usbmon,
but i'm not sure that is what you want
i've redone dumping dmesg trying to grab the information you are lookin for
i can't upload it on pastebin cause it's too large, i uploaded logs on megaupload
http://www.megaupload.com/?d=3D0QS1MX
Hello Larry,
thanks for the quick reply! Yes I know this version is a bit older, but when I
use the newest compat-wireless (eg.
http://www.orbit-lab.org/kernel/compat-wireless-2.6/compat-wireless-2011-10-07.tar.bz2)
the driver loads but some features like monitor-mode and packet injection
doesn't work. The listing of available networks (with airodump) doesn't work
too. Usually I have 13 channels because I live in Germany but if I use the
newest driver I have only 11 channels. But if I use the older compat-wireless
package all works fine.
Toddy
Is there a way to set the tx-power over 20dbm on the adapter?
I thought it is able to do 2w. There is no way for me to get it over 20 dbm.
When trying to to set the adapter with "iwconfig wlan1 set txpower 30"
it answers
Error for wireless request "Set Tx Power" (8B26) :
SET failed on device wlan1 ; Invalid argument.
I think there has to be done some work in the code but where do I start?
Thanks for all replys.
On 10/18/2011 08:07 AM, v4mp wrote:
> i tested the compat wireless drivers with another alfa awus036h and it works
> well, i tested also the realtek linux drivers 8192cu and the alfa awus036nhr
> works with them in the same distro and same kernel
> with rtl8192cu and xhci_hcd there are these no room on ep ring errors :(
I'm confused about what you did.
The Alfa AWUS036H uses a completely different driver (rtl8187) than does the
AWUS036NHR (rtl8192cu). It has been in the kernel for several years, thus using
compat-wireless would not be necessary.
Are you saying that driver 8192cu from Realtek's web site works with your
system, but that the kernel version from compat-wireless does not? If that is
true, what is the exact file name of the driver you downloaded?
Larry
On 10/18/2011 04:50 PM, v4mp wrote:
>
>
> yes, i know that the awus036h uses a different driver,
> i just wanna say that it
> has no conflicts with xhci_hcd as happen when loading
> the rtl8192cu driver for the 036nhr
>
> the driver i downloaded from realtek is what you can find here
> http://www.alfa.com.tw /in/front/bin/ ptlist.phtml?Category=105397
> for the awus036nhr, and it works fine without any kind of errors,
> detection of APs and connections
>
> every compat wireless i download does not with rtl8192cu and my alfa,
> i tested all the specific kernel version of compat-wireless and the latest
> bleeding edge compat wireless, i'm hating this fuckin errors :)
And I get really pissed off at people that have bleeding-edge hardware and get
mad because a driver doesn't work. Do you want to debug this issue by yourself?
If not, then you had better control your temper and your language. I am just a
volunteer. From what I see on my computer, the device, which I bought with my
own money, works fine. Thus - no problem.
Larry
On 10/06/2011 11:25 AM, Toddy wrote:
> Hello,
>
> I also have the AWUS036NHR device and I got it working on Ubuntu 11.04
> 2.6.38-11-generic x64. The only thing I did is to compile&install
> compat-wireless-2.6.39-1 (same as beini!) which can be found here:
> http://www.orbit-lab.org/kernel/compat-wireless-2.6-stable/v2.6.39/
>
> There was only one strange thing: In drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
> there is no entry for the AWUS036NHR so that no driver is loaded when I plugged
> the USB in, but in older versions of compat-wireless (e.g. 2.6.38) there IS one
> entry for this device. The entry looks like this:
>
> /* 8188RU in Alfa AWUS036NHR */
> {RTL_USB_DEVICE(USB_VENDER_ID_REALTEK, 0x817f, rtl92cu_hal_cfg)}
>
> So I patched the file, compiled&installed it and everything worked! Could
> someone patch the sources and add this device? Thanks!
The device is already in the kernel source.
Your choice of a compat-wireless version is what caused the problem. That device
was added to wireless-testing code on Aug. 5, 2011. By choosing an older version
of compat-wireless, you did not get that patch. For best results, you should
always choose the bleeding-edge version of compat-wireless.
Larry
On Sat, Oct 8, 2011 at 6:52 PM, Larry Finger <[email protected]> wrote:
> On 10/08/2011 11:24 AM, Toddy wrote:
>>
>> Hello Larry,
>>
>> thanks for the quick reply! Yes I know this version is a bit older, but
>> when I
>> use the newest compat-wireless (eg.
>>
>> http://www.orbit-lab.org/kernel/compat-wireless-2.6/compat-wireless-2011-10-07.tar.bz2)
>> the driver loads but some features like monitor-mode and packet injection
>> doesn't work. The listing of available networks (with airodump) doesn't
>> work
>> too. Usually I have 13 channels because I live in Germany but if I use the
>> newest driver I have only 11 channels. But if I use the older
>> compat-wireless
>> package all works fine.
>
> The difference between 11 and 13 channels depends on your CRDA settings. Do
> you have that package installed? Check the output of dmesg to see what
> domain is being set. If you have CRDA installed, then you can force the use
> of Germany in the domain by creating a file named
> /etc/modprobe.d/50-cfg80211.conf containing a single line with "options
> cfg80211 ieee80211_regdom=DE" (without the quote marks).
>
> You can get a list of available networks using iwconfig or iw. I know those
> work.
>
> As I do not test, support, nor condone packet injection, I cannot speak to
> it working on any driver.
Well, packet injection is required for Hostapd to work.
>
> Larry
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
On 10/17/2011 12:09 PM, v4mp wrote:
>
>
> ok, i've checked the md5 checksum of the firmware and is ok,
> i give you dmesg at pastebin.com
>
> it has 2 parts: in the second part i can't see what is in previous of the error
>
> the link is: http://pastebin.com/7tfcBfbD
Please try blacklisting xhci-hcd by adding a line containing
"blacklist xhci-hcd" to the end of /etc/modprobe.d/50-blacklist.conf.
Thanks,
Larry
On 10/26/2011 02:39 PM, Chiefdome wrote:
> Did you tested the commands you posted to me? Anyway here they do nothing. I
> cant see any changes in iwconfig nor in in iw.
>
> iw reg get
> country 00:
> (2400 - 2494 @ 40), (N/A, 33)
> (4910 - 5895 @ 40), (N/A, 33)
>
> so after my regulatory domain I should be able to change the adapter settings.
No, I did not test them. If they don't work, then you need to debug cfg80211.
These things are not a part of the driver. It only does what it is told.
You need to set a proper regulatory domain. Yours says "country 00", which is
not right. Mine says
finger@larrylap:~> iw reg get
country US:
(2402 - 2472 @ 40), (3, 27)
(5170 - 5250 @ 40), (3, 17)
(5250 - 5330 @ 40), (3, 20), DFS
(5490 - 5600 @ 40), (3, 20), DFS
(5650 - 5710 @ 40), (3, 20), DFS
(5735 - 5835 @ 40), (3, 30)
and that 27 dBm exactly matches what iwconfig says.
Larry
On 10/26/2011 02:39 PM, Chiefdome wrote:
>
> Did you tested the commands you posted to me? Anyway here they do nothing. I
> cant see any changes in iwconfig nor in in iw.
>
> iw reg get
> country 00:
> (2400 - 2494 @ 40), (N/A, 33)
> (4910 - 5895 @ 40), (N/A, 33)
>
> so after my regulatory domain I should be able to change the adapter settings.
I now have tested. My device is limited to 27 dBm, thus the limit in the txpower
command is 2700, but one can reduce the power.
finger@larrylap:~/linux-2.6> iwconfig wlan25
wlan25 IEEE 802.11bg ESSID:"lwfdjf-n"
Mode:Managed Frequency:2.422 GHz Access Point: C0:3F:0E:BE:2B:44
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=66/70 Signal level=-44 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:93 Invalid misc:270 Missed beacon:0
finger@larrylap:~/linux-2.6> sudo iw dev wlan25 set txpower limit 2200
finger@larrylap:~/linux-2.6> iwconfig wlan25
wlan25 IEEE 802.11bg ESSID:"lwfdjf-n"
Mode:Managed Frequency:2.422 GHz Access Point: C0:3F:0E:BE:2B:44
Bit Rate=54 Mb/s Tx-Power=22 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=68/70 Signal level=-42 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:93 Invalid misc:270 Missed beacon:0
With your regulatory info, you should be able to get 3300, unless the rtl8192cu
firmware has a limit to keep you from destroying the chip.
Perhaps you should ask Alfa about this issue.
Larry
On 10/26/2011 06:12 PM, Larry Finger wrote:
> On 10/26/2011 10:49 AM, Chiefdome wrote:
>> Is there a way to set the tx-power over 20dbm on the adapter?
>> I thought it is able to do 2w. There is no way for me to get it over
>> 20 dbm.
>> When trying to to set the adapter with "iwconfig wlan1 set txpower
>> 30" it answers
>>
>> Error for wireless request "Set Tx Power" (8B26) :
>> SET failed on device wlan1 ; Invalid argument.
>>
>> I think there has to be done some work in the code but where do I start?
>>
>> Thanks for all replys.
>
> The WEXT interface is deprecated. It is there as a convenience, but it
> will not be extended. To change the power setting, you need to use the
> iw utility. The specific commands are:
>
> iw dev <devname> set txpower <auto|fixed|limit> [<tx power in mBm>]
>
> or
>
> iw phy <phyname> set txpower <auto|fixed|limit> [<tx power in mBm>]
>
> The maximum power will be dependent on your regulatory domain setting.
>
> Larry
Did you tested the commands you posted to me? Anyway here they do
nothing. I cant see any changes in iwconfig nor in in iw.
iw reg get
country 00:
(2400 - 2494 @ 40), (N/A, 33)
(4910 - 5895 @ 40), (N/A, 33)
so after my regulatory domain I should be able to change the adapter
settings.
Chiefdome
Sorry, but i can't get this Alfa product to work with the latest bleeding edge
compat-wireless-2011-10-08 on ubuntu 11.04, tryed with kernels 2.6.38-11,
2.6.39 rc4 and 3.0
i tryed also the 2.6.39-1 version of compat-wireless
Don't show anything in managed and monitor mode..
i tested the compat wireless drivers with another alfa awus036h and it works
well, i tested also the realtek linux drivers 8192cu and the alfa awus036nhr
works with them in the same distro and same kernel
with rtl8192cu and xhci_hcd there are these no room on ep ring errors :(
On 10/20/2011 04:47 AM, v4mp wrote:
>
>
> i'm sorry but i don't know how to recompile kernel to apply this patch,
> i'm using the 3.1.oneric.rc9 for ubuntu precompiled
> can u recompile it with this patch,
> and then send me the compiled kernel to install?
I do not use Ubuntu, thus I cannot compile the kernel for you.
Larry
On 10/19/2011 09:37 AM, v4mp wrote:
>
>
> ok, i've done what you asked me with usbmon,
> but i'm not sure that is what you want
>
> i've redone dumping dmesg trying to grab the information you are lookin for
>
> i can't upload it on pastebin cause it's too large, i uploaded logs on megaupload
>
> http://www.megaupload.com/?d=3D0QS1MX
I got the data. Thanks. It will take a while to analyze the usbmon data, but
there is something I would like you to try. It will involve getting the kernel
source for some recent kernel, and applying the attached patch. With it,
xhci-hcd will dump the stack whenever the "short transfer on control ep" or "no
room on ep ring" errors occur. Send me those parts of the dmesg output, but
again do the dump early before the buffer wrap around happens.
Larry