high power usb dongle fails to connect (RTL8188SU)

mzzxx11 · 08-01-2013, 11:47 AM

Hi,

I'm using debian squeeze (debian 6) and trying to add a Planet WNL-U555HA high power wifi dongle:
http://www.planet.com.tw/en/product/...t.php?id=37435

The problem I have is that the adapter doesnt connect to wifi networks, except for my android mobile's hotspot.

lsusb gives:

Code:

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 044e:3017 Alps Electric Co., Ltd BCM2046 Bluetooth Device
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 0bda:8171 Realtek Semiconductor Corp. RTL8188SU 802.11n WLAN Adapter
Bus 001 Device 003: ID 05ca:18b6 Ricoh Co., Ltd 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

so the dongle uses the RTL8188SU cheapset.

Following the debian wiki, I've installed the realtek nonfree firmware. The module is r8192s_usb.
The dongle is detected and the LED goes on, but as mentioned it doesnt connect to any wifi network around, EXCEPT for my android mobile when set to be a hotspot.

Below is the relevant excerpt from /var/log/syslog when trying to connect to a wifi network "wifi1":

Code:

Aug  1 22:10:13 mylap NetworkManager[1298]: <info> Activation (wlan1) starting connection 'Auto wifi1'
Aug  1 22:10:13 mylap NetworkManager[1298]: <info> (wlan1): device state change: 3 -> 4 (reason 0)
Aug  1 22:10:13 mylap kernel: [  868.087803] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem()  Switch to 20MHz bandwidth
Aug  1 22:10:13 mylap kernel: [  868.087809] 
Aug  1 22:10:13 mylap NetworkManager[1298]: <info> Activation (wlan1) Stage 1 of 5 (Device Prepare) scheduled...
Aug  1 22:10:13 mylap NetworkManager[1298]: <info> Activation (wlan1) Stage 1 of 5 (Device Prepare) started...
Aug  1 22:10:13 mylap kernel: [  868.102471] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Aug  1 22:10:13 mylap kernel: [  868.102487] =================>ieee80211_authentication_req():auth->algorithm is 0
Aug  1 22:10:13 mylap NetworkManager[1298]: <info> Activation (wlan1) Stage 2 of 5 (Device Configure) scheduled...
Aug  1 22:10:13 mylap NetworkManager[1298]: <info> Activation (wlan1) Stage 1 of 5 (Device Prepare) complete.
Aug  1 22:10:13 mylap NetworkManager[1298]: <info> (wlan1): supplicant connection state:  completed -> disconnected
Aug  1 22:10:13 mylap NetworkManager[1298]: <info> Activation (wlan1) Stage 2 of 5 (Device Configure) starting...
Aug  1 22:10:13 mylap NetworkManager[1298]: <info> (wlan1): device state change: 4 -> 5 (reason 0)
Aug  1 22:10:13 mylap NetworkManager[1298]: <info> Activation (wlan1/wireless): connection 'Auto wifi1' requires no security.  No secrets needed.
Aug  1 22:10:13 mylap NetworkManager[1298]: <info> Config: added 'ssid' value 'wifi1'
Aug  1 22:10:13 mylap NetworkManager[1298]: <info> Config: added 'scan_ssid' value '1'
Aug  1 22:10:13 mylap NetworkManager[1298]: <info> Config: added 'key_mgmt' value 'NONE'
Aug  1 22:10:13 mylap NetworkManager[1298]: <info> Activation (wlan1) Stage 2 of 5 (Device Configure) complete.
Aug  1 22:10:13 mylap NetworkManager[1298]: <info> Config: set interface ap_scan to 1
Aug  1 22:10:13 mylap kernel: [  868.134759] Association response status code 0xc
Aug  1 22:10:13 mylap kernel: [  868.134790] ===>ieee80211_associate_procedure_wq(), chan:6
Aug  1 22:10:13 mylap NetworkManager[1298]: <info> (wlan1): supplicant connection state:  disconnected -> scanning
Aug  1 22:10:13 mylap kernel: [  868.184814] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem()  Switch to 20MHz bandwidth
Aug  1 22:10:13 mylap kernel: [  868.184819] 
Aug  1 22:10:13 mylap kernel: [  868.199364] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Aug  1 22:10:13 mylap kernel: [  868.199386] =================>ieee80211_authentication_req():auth->algorithm is 0
Aug  1 22:10:13 mylap kernel: [  868.254372] Association response status code 0xc
Aug  1 22:10:13 mylap kernel: [  868.259731] Association response status code 0xc
Aug  1 22:10:13 mylap kernel: [  868.259731] Association response status code 0xc
Aug  1 22:10:15 mylap kernel: [  869.674826] ===>ieee80211_associate_procedure_wq(), chan:6
Aug  1 22:10:15 mylap kernel: [  869.714851] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem()  Switch to 20MHz bandwidth
Aug  1 22:10:15 mylap kernel: [  869.714857] 
Aug  1 22:10:15 mylap kernel: [  869.729617] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Aug  1 22:10:15 mylap kernel: [  869.729640] =================>ieee80211_authentication_req():auth->algorithm is 0
Aug  1 22:10:15 mylap kernel: [  869.729670] ===>ieee80211_associate_procedure_wq(), chan:6
Aug  1 22:10:15 mylap kernel: [  869.751370] rtl819xU:rtl8192_qos_association_resp: network->flags = 2,0
Aug  1 22:10:15 mylap kernel: [  869.751378] 
Aug  1 22:10:15 mylap kernel: [  869.768596] rtl819xU:==>SetBWModeCallback8192SUsbWorkItem()  Switch to 20MHz bandwidth
Aug  1 22:10:15 mylap kernel: [  869.768605] 
Aug  1 22:10:15 mylap kernel: [  869.768623] rtl819xU:qos active process with associate response received
Aug  1 22:10:15 mylap kernel: [  869.768629] 
Aug  1 22:10:15 mylap kernel: [  869.783356] rtl819xU:<==SetBWModeCallback8192SUsbWorkItem()
Aug  1 22:10:15 mylap kernel: [  869.783377] =================>ieee80211_authentication_req():auth->algorithm is 0
Aug  1 22:10:15 mylap kernel: [  869.783402] Associated successfully
Aug  1 22:10:15 mylap kernel: [  869.783411] Using G rates:108
Aug  1 22:10:15 mylap kernel: [  869.783420] Successfully associated, ht not enabled(0, 1)
Aug  1 22:10:15 mylap kernel: [  869.783429] =====>rtl8192SU_link_change 1
Aug  1 22:10:15 mylap wpa_supplicant[1314]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Aug  1 22:10:15 mylap kernel: [  869.784618] <=====rtl8192SU_link_change 2
Aug  1 22:10:15 mylap kernel: [  869.784631] ============>normal associate
Aug  1 22:10:15 mylap NetworkManager[1298]: <info> (wlan1): supplicant connection state:  scanning -> disconnected
Aug  1 22:10:15 mylap kernel: [  869.852140] rtl819xU:rtl8192_qos_association_resp: network->flags = 2,0
Aug  1 22:10:15 mylap kernel: [  869.852148] 
Aug  1 22:10:15 mylap kernel: [  869.852194] rtl819xU:qos active process with associate response received
Aug  1 22:10:15 mylap kernel: [  869.852201] 
Aug  1 22:10:15 mylap kernel: [  869.852228] Associated successfully
Aug  1 22:10:15 mylap kernel: [  869.852237] Using G rates:108
Aug  1 22:10:15 mylap kernel: [  869.852246] Successfully associated, ht not enabled(0, 1)
Aug  1 22:10:15 mylap kernel: [  869.852255] =====>rtl8192SU_link_change 1
Aug  1 22:10:15 mylap kernel: [  869.855742] =============>ARFR0+rate_index*4:0x5
Aug  1 22:10:15 mylap wpa_supplicant[1314]: No network configuration found for the current AP
Aug  1 22:10:15 mylap wpa_supplicant[1314]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Aug  1 22:10:15 mylap kernel: [  869.865116] <=====rtl8192SU_link_change 2
Aug  1 22:10:15 mylap kernel: [  869.865129] ============>normal associate
Aug  1 22:10:15 mylap kernel: [  869.866197] Linking with wifi2,channel:6, qos:0, myHT:1, networkHT:1, mode:10

So after some events, the connection is dropped and the the adapter connects to the mobile hotspot wifi ("wifi2").

I am able to connect to "wifi1" with the laptop onboard adapter, so that network is functioning. It is an open network (no encryption).

Any suggestions how to get the adapter to connect?

TIA

PeterSullivan · 08-02-2013, 05:44 AM

please mention which device you are trying to connect with your wifi. some latest device like Playstation, windows 7 and other latest smart gadget,
please check the following this.

* A wireless network adapter switch that's not enabled
* WEP, WPA, or WPA2 security key or passphrase issues
*Cables that aren't connected properly
* Corrupted or incompatible drivers
* Missing updates
* Network connection settings
* Hardware or software problems

mzzxx11 · 08-02-2013, 09:21 AM

tnx.

I'm trying to connect to a public wifi network. I dont have access to the router/computer I'm to connect to.

As I've mentioned, the usb dongle fails to connect to network that the laptop onboard adapter succeeds. The dongle works fine under Windows 7 so its not a faulty HW issue.

evo2 · 08-06-2013, 04:09 AM

Hi,

Quote:

Originally Posted by mzzxx11

I'm using debian squeeze (debian 6) and trying to add a Planet WNL-U555HA high power wifi dongle:
http://www.planet.com.tw/en/product/...t.php?id=37435

the very first thing I would do here is upgrade to the current version of Debian. I'm not saying that this will definitely solve your problem, but newer kernels often do resolve driver/hardware issues.

Evo2.

mzzxx11 · 08-07-2013, 12:00 AM

I am planning to upgrade to wheezy once I return (I'm currently travelling, so an upgrade is too intensive to perform).

Not trying to turn this into a Linux vs. Windows debate, but having to upgrade an entire OS just to get a wifi dongle working is a big issue linux needs to solve.
Why can windows owner just install a driver irrespective of their OS version, while in linux if something isnt working one needs to perform a huge system upgrade?.

Kinda dissapointed with this linux "feature".

evo2 · 08-07-2013, 01:34 AM

Hi,

Quote:

Originally Posted by mzzxx11

Not trying to turn this into a Linux vs. Windows debate, but having to upgrade an entire OS just to get a wifi dongle working is a big issue linux needs to solve.

False premise. You do not _have_ to upgrade your whole OS to get a new driver.

Quote:

Why can windows owner just install a driver irrespective of their OS version, while in linux if something isnt working one needs to perform a huge system upgrade?.

The manufactures provide windows drivers but they do not provide Linux drivers. Nor to they provide information about how the devices operate. Instead people reverse engineer the devices and release drivers for free so all can benefit. Again, you don't have to "perform a huge system upgrade", but keeping the OS up to date is the simplest approach for most users.

Quote:

Kinda dissapointed with this linux "feature".

I don't think you have a very accurate picture of the situation.

Evo2.

PS. What I wrote in the 2nd paragraph is not true of all devices and all companies.

mzzxx11 · 08-07-2013, 01:47 AM

I disagree.

I've tried to backport the kernel to 3.2 or 3.4 (whatever is available on repo) and I ended up with a nonworking system, because other components too (maybe the entire gnome desktop) also need to be backported. not to mention the pulsbo specialized drivers for the graphics card and who knows what else.

so to get my wifi dongle working I may have to backport/upgrade tons of apps which are completely unrelated to networking. Luckily I still have the option of booting with the 2.6.32 kernel so the system works (but no dongle).

Reverse engineering drivers has nothing to do with linux being a tangled web of interconnected programs. There is no reason why a reverse engineered driver should require a full desktop update. This happens only because of the software architecture used in linux.

Linux is good but far from perfect and often a lot more hassle to operate than Windows or OSX. Its OK to critisize it.