It seems the driver is loaded and the device can scan networks
so that part looks good. But "Access Point: Not-Associated" is not good.

One interesting question is if you use wicked or NetworkManager
to configure the wireless network.

I just tested with a Factory system updated yesterday. One I installed the kernel-firmware, my TP-Link TL-WN725N connected immediately using NetworkManager.

The new KDE applet is definitely inferior to the plasmoid-networkmanagement applet in 13.1.

Hallo Bernhard, Larry,

My initial report was with wicked (via Yast)

This evening I gave it a try with NetworkManager and now the Wireless connection works correctly. It started up however .slowly

Regards,    Frans

Please attach the following logs:
‒ set DEBUG=all in /etc/sysconfig/network/config
‒ systemctl restart wickedd
‒ wicked --debug all ifup all # systemctl restart wicked
‒ wicked ifstatus all > status.log
‒ wicked show-config > configs.log
‒ journalctl -b -o short-iso > wicked.log
‒ ip addr show > ip_addr.log
‒ ip route show > routes.log
‒ ip -6 route show >> routes.log

Yes, the results differs from HW to HW. While intel HW we have here in
our notebooks does not cause trouble, other HW is not always reliable.

I've the following stick here:

# hwinfo --netcard
28: USB 00.0: 0282 WLAN controller
  [Created at usb.122]
  Unique ID: 33sj.x9IMWGGtcg8
  Parent ID: ADDn.4Nx_qoDfSd7
  SysFS ID: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0
  SysFS BusID: 1-1.4:1.0
  Hardware Class: network
  Model: "Realtek 802.11n WLAN Adapter"
  Hotplug: USB
  Vendor: usb 0x0bda "Realtek Semiconductor Corp."
  Device: usb 0x8176 "802.11n WLAN Adapter"
  Revision: "2.00"
  Serial ID: "00e04c000001"
  Driver: "rtl8192cu"
  Driver Modules: "rtl8192cu"
  Device File: wlan0
  Features: WLAN
  Speed: 480 Mbps
  HW Address: 80:1f:02:bd:34:5c
  Link detected: no
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Module Alias: "usb:v0BDAp8176d0200dc00dsc00dp00icFFiscFFipFFin00"
  Driver Info #0:
    Driver Status: rtl8192cu is active
    Driver Activation Cmd: "modprobe rtl8192cu"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #34 (Hub)

and it basically works (with kernel-firmware-20140903git-2.1.noarch), but
I'm only able to connect one of the two networks I have. I've never seen
the second one in the scan results -- the signal is just perhaps 5% worser
but my mobile phone and notebook (intel HW) does not have any problem to
see and connect to both...

Hm... I've changed the settings to "everything auto" (enabling wireless-b
and all that stuff...) -- but now it simply worked:

A "iwlist wlan0 scan" reports them with:
  network 1 [not working before, AP FritzBox 6369]
                    Quality=50/70  Signal level=-60 dBm  
  network 2 [working before, D-Link DIR-850L]
                    Quality=54/70  Signal level=-56 dBm

Ahm... I've just overlooked before, that the card does not list channel 13
which the AP were using before (CRDA were DE, but it seems to add ch12+13).
So basically the above HW / firmware works too.

Question is now what this error from kernel driver means:
   [ 8584.856011] R8188EU: ERROR indicate disassoc
AFAIS, it is a staging driver == unknown quality ...

Please provide the logs requested in comment 4 and additionally also the
/var/log/wpa_supplicant.log and /var/log/NetworkManager.

Hello Pawel,

I am just back from vacation, so sorry for late reaction.

Just a few questions to clarify what you need and how to get the logs.

1  Should I do these steps with "Wicked" reconfigured, since I currently run
   networkmanager successfully?

2  How should I get the logs? Should I run on the command line just the various
   commands in the given sequence. Should I run the commands as user or as root? 

Regards,    Frans

(In reply to Frans Leerink from comment #8)
> Hello Pawel,

Hi Frank,

> 
> I am just back from vacation, so sorry for late reaction.
> 

No worries :-).

> Just a few questions to clarify what you need and how to get the logs.
> 
> 1  Should I do these steps with "Wicked" reconfigured, since I currently run
>    networkmanager successfully?
> 

First of all disable and kill NetworkManager properly. Description how to do that can be found here: 
https://bugzilla.suse.com/show_bug.cgi?id=893678#c17

> 2  How should I get the logs? Should I run on the command line just the
> various
>    commands in the given sequence. Should I run the commands as user or as
> root? 
> 

Here's more detailed description:

‒ set DEBUG=all in /etc/sysconfig/network/config

edit /etc/sysconfig/network/config file and tweak the requested DEBUG variable.

- enable wpa_supplicant in the debugging mode

Easiest is to edit the wpa_supplicant.service file and restart it by:
 * Apply the following diff (note it is just an additional -d option on the wpa_supplicant parm list)

diff --git a/usr/lib/systemd/system/wpa_supplicant.service b/usr/lib/systemd/system/wpa_supplicant.service.old
index c764a53..7f475cf 100644
--- a/usr/lib/systemd/system/wpa_supplicant.service
+++ b/usr/lib/systemd/system/wpa_supplicant.service.old
@@ -5,7 +5,7 @@ Before=network.target
 [Service]
 Type=dbus
 BusName=fi.w1.wpa_supplicant1
-ExecStart=/usr/sbin/wpa_supplicant -d -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log
+ExecStart=/usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log
 
 [Install]
 WantedBy=multi-user.target

 * execute as root on terminal: systemctl daemon-reload
 * execute as root on terminal: systemctl restart wpa_supplicant

All the following commands should be manually executed as root on the terminal:
‒ systemctl restart wickedd
‒ wicked --debug all ifup all # systemctl restart wicked
‒ wicked ifstatus all > status.log
‒ wicked show-config > configs.log
‒ journalctl -b -o short-iso > wicked.log
‒ ip addr show > ip_addr.log
‒ ip route show > routes.log
‒ ip -6 route show >> routes.log

Provide also log file from wpa_supplicant: /var/log/wpa_supplicant.log

> Regards,    Frans

If you are worried about that "ERROR" in the disassociate message, you can ignore it. All it is saying is that the interface is not associated. That is not necessarily an error.

This is an autogenerated message for OBS integration:
This bug (893665) was mentioned in
https://build.opensuse.org/request/show/254980 Factory / wicked

SUSE-RU-2014:1461-1: An update that has four recommended fixes can now be installed.

Category: recommended (important)
Bug References: 887910,893665,900112,900401
CVE References: 
Sources used:
SUSE Linux Enterprise Server 12 (src):    wicked-0.6.12-4.1
SUSE Linux Enterprise Desktop 12 (src):    wicked-0.6.12-4.1
SUSE Linux Enterprise Build System Kit 12 (src):    wicked-0.6.12-4.1