wireless usb lan won't connect reliably on 12.3!

English Network/Internet
1

Hello list, moderators! Nice job on the sticky posts.

I have two 12.3 towers, both with a wired connection. One tower is 64-bit, one is 32. Both are up to date with Online Update.

My problem is to get a wlan working so I can get a cat5 cable off my floor. My wireless usb lan works occasionally, but seldom reconnects on a reboot. It may be I have a cheap imatation of a RealTek. It did come with a Windows mini disk.

One thing from the “stickies” is that I don’t have wpa_ installed, but there is no match for wpa_ in any of the generic, community repositories plus packman.

This is the result of hwinfo --wlan:

root[512] hwinfo --wlan
20: USB 00.0: 0282 WLAN controller                              
  [Created at usb.122]
  Unique ID: KRJj.x9IMWGGtcg8
  Parent ID: uIhY.2DFUsyrieMD
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0
  SysFS BusID: 3-1: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: 48:02:2a:e3:7d:34
  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=no, avail=yes, need=no, active=unknown
  Attached to: #19 (Hub)
root[512]

Firmware looks like this:

root[512] dmesg | grep -i firmware
 8461.461732] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin
root[513]

The bottom of dmesg looks like this:

 8484.327099] wlan0: associated
 8484.327116] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
 8486.240209] SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:4a02:2aff:fee3:7d34 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=428 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=388 
 8486.302378] SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:4a02:2aff:fee3:7d34 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=258 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=218 
 8486.490788] SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:4a02:2aff:fee3:7d34 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=428 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=388 
 8486.741224] SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:4a02:2aff:fee3:7d34 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=428 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=388 
 8486.941748] SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:4a02:2aff:fee3:7d34 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=398 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=358 
 8530.073876] wlan0: deauthenticating from 00:17:3f:e4:da:5f by local choice (reason=3)
root[514]

AFAIK, I don’t have an access point set. Maybe I need to set one! I just want the wireless from my Belkin router to connect to the wlan less than 20’ away. If I have a mismatch between my usb wireless adapter and the router, I have other routers to try.

This usb wireless adapter worked better with 12.1 and 12.2. Sometimes with those and almost always with 12.3 the network manager keeps trying to connect, but gives up.

Another thing is that I’m new to centurylink.net as an ISP. I don’t expect they are involved in this “local” area problem.

I’ve tried WEP, WPA, and no security at all. What is wrong with this picture? Heboland.

2

Does this by any chance happen when rebooting in from another OS?

If you do start with a working connection, is it OK from then on?

On one of my machines that has multiple OS’s. I have to shutdown between switching OS. Different wireless hardware, but just thought I would mention.

3

Thank for your response, caf4926!

Let me ask a couple of questions up front, then answer your questions with the rambling that follows!

Is it easiest to get a connection without enabling security? Is there a log dedicated to wireless connections? Is there an advantage to matching routers with usb wireless lan, say both Belkin? Is there a preferred brand of hardware for a usb wireless lan with Linux?

My 32-bit tower is a multiple boot, but only the 12.3 has been used for the week or more. The 64 bit tower is only 12.3. I have moved the usb wireless lan between the towers.

For this thread the usb wireless lan can stay plugged into the 64-bit tower. The modem and router are within a foot of the wireless router which also provides the wired connections.

I don’t expect this problem is related to multiple operating systems.

It seems to me that turning security off in the router takes the encryption out of the mix. The usb wireless lan finds the broadcast ssid, the mac address, and knows there’s no security. In the system tray, the network manager just spins and spins, the connect icon stays orange. The “repair” menu that results from clicking the icon seems to do nothing.

Once I got a connection by entering in the BSSID, but on the next reboot of the same OS the connection failed. I don’t know if the BSSID is just a usb wireless lan property or if it involves the router.

If there was a log or a debug mode to trace the problem it would help. The frustration level is high when shooting in the dark! I’m glad I have my wired connections while I struggle with this! Heboland.

4

Some people find it easier to solve issues by taking encryption out of the mix, but it’s not advised to run that way except for testing. It’s possible for anyone to use your network.

32 or 64 bit I never found any difference with regard to wireless.

It seems clear that your device works. It’s just a configuration issue. And I’m not clear what could have changed between 12.1 and 12.2 > now with 12.3
And I’m not a wireless expert

5

Thanks for the reply caf4926!

I’m out in the sticks, so there’s little risk of anyone eavesdropping on an open wireless connection. If I ever get this to work, I’ll tighten up the security.

Lets follow up on your observation of a configuration problem. When using the 12.3 network manager, the only config file I’ve heard about is wpa_supplicant.conf. These are its contents:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel

/etc/wpa_supplicant/wpa_supplicant.conf lines 1-3/3 (END)

Is this saying I need to be a member of group wheel?

I have two wireless routers, both Belkin. To test each of these, I fired up the XP-32 boot. With the wireless security turned off in each router, either connects automatically on XP boot-up. This is a pre-SP1 XP. The RealTek driver wouldn’t install.

I used different SSIDs for each router. Each router is recognized by the 12.3-64. Network manager takes a shot at each, but won’t connect.

Where does the network manager connection information get stored? Heboland.

6

Where does the network manager connection information get stored? Heboland.

kde ? gnome?

But just delete all existing connections and start again, you shouldn’t need to edit the config file

7

Thanks caf4926!

I haven’t had a 12.3 wireless connection working for a few days now. My desktop is LXDE. It’s using the 12.3 network manager. I use some kde apps like okular and gwenview, so I have some of the kde environment installed.

Many times I have deleted the wireless connections and started over. I did try putting myself into wheel, but that didn’t change anything so I took myself out of wheel again.

I have four wireless modems that can send a wireless signal to test. The two Belkins, a Twowire, and a NetGear. All are detected. a connection will be attempted on any of these, but the result is the same. After a minute or so of spinning - no connection!

There must be some way to debug these wireless connections! Can you help me with that? Heboland.

8

You will have to excuse me being confused:

*You have 2 wireless routers? - Really…why?
but later you say
*I have four wireless modems

If nothing has changed in your setup, whatever that is, since having 12.1 / 12.2 (except the OS is now 12.3) then there should be no problem.

Just so we are clear

A router/modem is:
https://www.live-technician.com/images/stories/support_new/Wi-fiHomeNetwork/netgear_router_support.jpg

A wireless dongle is:
http://vinnyscomputerwarehouse.com/images/dongle.jpg

What were you using with the previous release?

Can you test a Live CD of 12.1 or 12.2 or other distro like Ubuntu, see what works…

9

Sorry for the confusion caf4926!

I recognize your router and dongle picture. My Belkin routeers look like yours. They are the two I counted the first time. The other two are modem/routers that have internal antennas. For more variety, I dug out the twowire and the netgear to move the router total to four. I only have one b-n dongle.

With the 12.1-32, I was using the netgear modem/router. Even then it took a lot of coaxing, restarting, replugging, etc to get a connection.

Only one of these routers has been active at a time. The bottom line for trying all these routers is that they have different security settings that offer different matches to the 12.3 wireless options.

In lieu of being able to debug the wireless problem, one other alternative is trial and error.

There are lots of setup choices in the modems and in the 12.3 wireless options. Some are mutually exclusive. One would hope the default settings would match up, but that hasn’t happened so far.

There aren’t any errors, just silent failures after a minute or so of trying to connect. What I see in the dmesg means nothing to me. One other thing that has showed up in 12.3 is the password keyring. I keep canceling it so I don’t have to deal with it too!

Today I found something on the internet that said to configure a wlan on 12.3 required shutting off the network manager and configuring the wlan in ifup mode. Have you heard of that?

Last time I shut off NM, my wired connection went away. As I recall the wired connection comes back with NM, but does wlan setup remain or would it be ignored?

I appreciate your patience dealing with me on this. Without any debug output, a tutorial, set of instructions, or even a man page would be of help. Are you familiar with either of these for wireless? Heboland.

10

I think your problem is not the router / modem, but more likely the wireless device (dongle) whatever it is you have?
Did you - Can you give details of this device?

Ideally you should use Network Manager
There was a bug in the 12.3 release to do with the network, but a simple reboot solved this. I’m sure you already rebooted plenty…

11

Thanks for sticking with me, caf4926!

Yes, the dongle could be suspect. A friend ordered it for me online. Not much documentation came with it. Like I wrote previously, the mini CD that came with it would not install on my old XP-32 dual boot. It does work with that XP without the proprietary CD software.

On the dongle there are some performance numbers stamped on it. The back shows a fine pitch barcode with long number preceeded by BL.

My first post showed the hwinfo for this dongle. AFAIK the yast > Hardware > hardware information doesn’t show any more.

What I have does connect some times, but usually only once. With WPA security set in the router, the password (ascii key) dialog box pops up every minute until I cancel it. If I edit the connection or create a new new connection where I can save the password it makes no difference. I don’t think I’ve ever got connected to a connection I created manually.

No security set in the router causes several minute-long network manager connection attempts, then quits.

One connection I got late yesterday with no security didn’t have internet access. When I disconnected it, it wouldn’t reconnect.

I see the Broadcom drivers shown in the yast > Software Manager. If I have to buy another dongle, that is probably the brand to get, right?

On the web I see an ad for the BCM4323. Do you which Broadcom usb dongles the 12.3 drivers will work with? Heboland.

12

Hello again list, caf4926!

I just discovered this in another post: tail -f /var/log/NetworkManager.

FWIW, this is the var/log/NetworkManager entry for a no-security connection to Belkin0 which is a 12.3 automatically created connection:

2013-04-18T09:15:39.430736-07:00 linux-uso4 NetworkManager[682]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
2013-04-18T09:15:41.203859-07:00 linux-uso4 NetworkManager[682]: <info> (wlan0): supplicant interface state: scanning -> inactive
2013-04-18T09:15:42.428235-07:00 linux-uso4 NetworkManager[682]: <info> Auto-activating connection 'Belkin0'.
2013-04-18T09:15:42.429030-07:00 linux-uso4 NetworkManager[682]: <info> Activation (wlan0) starting connection 'Belkin0'
2013-04-18T09:15:42.429685-07:00 linux-uso4 NetworkManager[682]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
2013-04-18T09:15:42.430415-07:00 linux-uso4 NetworkManager[682]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
2013-04-18T09:15:42.431079-07:00 linux-uso4 NetworkManager[682]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
2013-04-18T09:15:42.431714-07:00 linux-uso4 NetworkManager[682]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
2013-04-18T09:15:42.432287-07:00 linux-uso4 NetworkManager[682]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
2013-04-18T09:15:42.433082-07:00 linux-uso4 NetworkManager[682]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
2013-04-18T09:15:42.433342-07:00 linux-uso4 NetworkManager[682]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
2013-04-18T09:15:42.433734-07:00 linux-uso4 NetworkManager[682]: <info> Activation (wlan0/wireless): connection 'Belkin0' requires no security.  No secrets needed.
2013-04-18T09:15:42.434396-07:00 linux-uso4 NetworkManager[682]: <info> Config: added 'ssid' value 'Belkin0'
2013-04-18T09:15:42.434522-07:00 linux-uso4 NetworkManager[682]: <info> Config: added 'scan_ssid' value '1'
2013-04-18T09:15:42.434971-07:00 linux-uso4 NetworkManager[682]: <info> Config: added 'key_mgmt' value 'NONE'
2013-04-18T09:15:42.435376-07:00 linux-uso4 NetworkManager[682]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
2013-04-18T09:15:42.435742-07:00 linux-uso4 NetworkManager[682]: <info> Config: set interface ap_scan to 1
2013-04-18T09:15:44.182673-07:00 linux-uso4 NetworkManager[682]: <info> (wlan0): supplicant interface state: inactive -> scanning
2013-04-18T09:16:07.427044-07:00 linux-uso4 NetworkManager[682]: <warn> Activation (wlan0/wireless): association took too long, failing activation.
2013-04-18T09:16:07.427355-07:00 linux-uso4 NetworkManager[682]: <info> (wlan0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
2013-04-18T09:16:07.427581-07:00 linux-uso4 NetworkManager[682]: <info> Marking connection 'Belkin0' invalid.
2013-04-18T09:16:07.428244-07:00 linux-uso4 NetworkManager[682]: <warn> Activation (wlan0) failed for connection 'Belkin0'
2013-04-18T09:16:07.428470-07:00 linux-uso4 NetworkManager[682]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
2013-04-18T09:16:07.428957-07:00 linux-uso4 NetworkManager[682]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
2013-04-18T09:16:07.429388-07:00 linux-uso4 NetworkManager[682]: <info> (wlan0): deactivating device (reason 'none') [0]
2013-04-18T09:16:07.429823-07:00 linux-uso4 NetworkManager[682]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
2013-04-18T09:16:08.051800-07:00 linux-uso4 NetworkManager[682]: <info> (wlan0): supplicant interface state: scanning -> inactive
C^C
root[506] tail -f /var/log/NetworkManager
2013-04-18T09:15:44.182673-07:00 linux-uso4 NetworkManager[682]: <info> (wlan0): supplicant interface state: inactive -> scanning
2013-04-18T09:16:07.427044-07:00 linux-uso4 NetworkManager[682]: <warn> Activation (wlan0/wireless): association took too long, failing activation.
2013-04-18T09:16:07.427355-07:00 linux-uso4 NetworkManager[682]: <info> (wlan0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
2013-04-18T09:16:07.427581-07:00 linux-uso4 NetworkManager[682]: <info> Marking connection 'Belkin0' invalid.
2013-04-18T09:16:07.428244-07:00 linux-uso4 NetworkManager[682]: <warn> Activation (wlan0) failed for connection 'Belkin0'
2013-04-18T09:16:07.428470-07:00 linux-uso4 NetworkManager[682]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
2013-04-18T09:16:07.428957-07:00 linux-uso4 NetworkManager[682]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
2013-04-18T09:16:07.429388-07:00 linux-uso4 NetworkManager[682]: <info> (wlan0): deactivating device (reason 'none') [0]
2013-04-18T09:16:07.429823-07:00 linux-uso4 NetworkManager[682]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
2013-04-18T09:16:08.051800-07:00 linux-uso4 NetworkManager[682]: <info> (wlan0): supplicant interface state: scanning -> inactive

Does this log shed any more light on what’s going wrong? Heboland.

13

It’s me again!

Maybe this thread has run it’s course, or maybe I’m pressing my luck!

On the topic of my usb wireless lan being the problem, I found myself a new erector set! With a couple magnifying glasses I decyphered a contact point embedded in the slip of documentation that came with my usb wireless lan. On one of the tiny screens shown was the logo Shenzhen Bilian Electronic Co LTD. They have a website with drivers.

I think it’s OK to post this link here: Realtek. From my hwinfo --wlan it detects RTL8192CU as my device.

So if anyone is brave enough to follow this link there are both linux (unix) and windows drivers. I downloaded both and so far installed the windows driver on my old XP. Except for overreacting to the no security connection it seems to work fine.

The linux download is quite interesting to me. If any of the moderators here have the time to look at it, I would like to get their reaction. I’m tempted to try building this stuff. The download is only for kernel 3.0.8, so it may not build. Also the 12.3 seems to have a driver for the RTL8192CU, so I may be creating problems for myself.

Now I’m thinking before I buy another usb wlan adapter, I’m going to pursue making what I have works. Any comments before I step off the deep end? Heboland.

14

That is listed here
https://en.opensuse.org/HCL:Network_(Wireless)#Realtek

so please try this, you need a wired connection

su -
zypper ar -f [Index of /repositories/home:/Lord_LT:/drivers/openSUSE_12.3_Update](http://download.opensuse.org/repositories/home:/Lord_LT:/drivers/openSUSE_12.3_Update/) drivers

zypper ref

(a) to accept

zypper up
15

Please use your mouse to copy and paste the code from here in to your terminal

16

On 04/18/2013 09:46 PM, heboland wrote:
>
> It’s me again!
>
> Maybe this thread has run it’s course, or maybe I’m pressing my luck!
>
> On the topic of my usb wireless lan being the problem, I found myself a
> new erector set! With a couple magnifying glasses I decyphered a contact
> point embedded in the slip of documentation that came with my usb
> wireless lan. On one of the tiny screens shown was the logo Shenzhen
> Bilian Electronic Co LTD. They have a website with drivers.
>
> I think it’s OK to post this link here: ‘Realtek’
> (http://tinyurl.com/bsn5rrm). From my hwinfo --wlan it detects RTL8192CU
> as my device.
>
> So if anyone is brave enough to follow this link there are both linux
> (unix) and windows drivers. I downloaded both and so far installed the
> windows driver on my old XP. Except for overreacting to the no security
> connection it seems to work fine.
>
> The linux download is quite interesting to me. If any of the moderators
> here have the time to look at it, I would like to get their reaction.
> I’m tempted to try building this stuff. The download is only for kernel
> 3.0.8, so it may not build. Also the 12.3 seems to have a driver for the
> RTL8192CU, so I may be creating problems for myself.

The driver for the RTL8192CU has been in the kernel since 2.6.38; therefore, it
is available for all supported versions of openSUSE.

You are welcome to download a vendor driver; however, you would be responsible
for making ALL the changes needed to build it with a newer kernel. I have done
that for the official kernel version, and I have no interest in doing it again.
Note: there are substantial differences between kernel 3.0 and 3.7!

There is a bug that may affect kernel 3.7.10; however, you can get a fix for
that by downloading
https://www.kernel.org/pub/linux/kernel/projects/backports/stable/v3.9-rc4/compat-drivers-3.9-rc4-2.tar.bz2
and building the drivers from that.

BTW, if you had mentioned earlier in the thread that you had an RTL8192CU, I
would have answered earlier.

17

Thanks again lwfinger, caf4926!

lwfinger, I have no interest in reinventing the wheel if I don’t need to. On my original post, I included most of the system information recommended by the sticky posts. On of these was the hwinfo --wlan. That “code” does show my wlan to be the rtl8192cu.

Until I started backtracking this into the Chinese site that shows rtl819xcu, I didn’t realize that hwinto had filled in the “x” for me.

caf4926 there is a syntax problem with your code. I can probably figure it out, but if you are close, this is what I’m getting:

frank[5004] su -
Password: 
/etc/zshrc:57: compinit: function definition file not found
root[501] zypper ar -f Index of /repositories/home:/Lord_LT:/drivers/openSUSE_12.3_Update drivers
Too many arguments.


root[502] zypper ar -f Index of /repositories/home:/Lord_LT:/drivers/openSUSE_12.3_Update        
Too many arguments.


root[503] zypper ar -f /repositories/home:/Lord_LT:/drivers/openSUSE_12.3_Update      
If only one argument is used, it must be a URI pointing to a .repo file.
addrepo (ar) [options] <URI> <alias>
addrepo (ar) [options] <file.repo>

Add a repository to the sytem. The repository can be specified by its URI or can be read from specified .repo file (even remote).

For the record I use zsh for both me an root, but this shouldn’t be a factor here. I’m anxious to try this. BTW, after getting this repository added and enabled, I think I should disable it again after the update. Do you agree? Heboland.

18

I don’t know what happened to that code
Let me try again

You need to be su -

zypper ar -f http://download.opensuse.org/repositories/home:/Lord_LT:/drivers/openSUSE_12.3_Update/ drivers
19

Thanks caf4926!

Your new code executed fine, but there’s no cigar. There’s no connection! Prior to the update, I deleted all the wireless entries the Network Manager had. Then I changed to router SSID and the protocol to WPA & WPA2 and set a password.

Next I turned on the XP box and plugged the wlan into it. The XP driver I downloaded from China still had the old no-security SSID. I removed that and let it search for the new WPA SSID. I added the new entry an it asked for the password. I gave the password and the connection was made.

Now with the wlan on the 12.3-64, it finds the new SSID. I click “Connect” and up pops the menu for the authentication password. I give that, NM spins for a minute and pops the password menu back up. From there its an endless cycle that never connects.

This is the zypper update response from the shell:

frank[5002] su -
Password: 
/etc/zshrc:57: compinit: function definition file not found
root[501] zypper ar -f http://download.opensuse.org/repositories/home:/Lord_LT:/drivers/openSUSE_12.3_Update/ drivers
Adding repository 'drivers' ..............................................[done]
Repository 'drivers' successfully added
Enabled: Yes
Autorefresh: Yes
GPG check: Yes
URI: http://download.opensuse.org/repositories/home:/Lord_LT:/drivers/openSUSE_12.3_Update/

root[502] zypper ref
Retrieving repository 'drivers' metadata ------------------------------------\]

New repository or package signing key received:
Key ID: AD5DFED7532AF3A3
Key Name: home:Lord_LT OBS Project <home:Lord_LT@build.opensuse.org>
Key Fingerprint: 73BB17C93071C0E2F85FFB52AD5DFED7532AF3A3
Key Created: Tue Apr 24 09:59:24 2012
Key Expires: Thu Jul  3 09:59:24 2014
Repository: drivers

Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): t
Retrieving repository 'drivers' metadata .................................[done]
Building repository 'drivers' cache ......................................[done]
Retrieving repository 'Packman Repository' metadata ......................[done]
Building repository 'Packman Repository' cache ...........................[done]
Repository 'openSUSE-12.3-Non-Oss' is up to date.
Repository 'openSUSE-12.3-Oss' is up to date.
Repository 'openSUSE-12.3-Update' is up to date.
Repository 'openSUSE-12.3-Update-Non-Oss' is up to date.
All repositories have been refreshed.
root[503] zypper up
Loading repository data...
Reading installed packages...

The following package updates will NOT be installed:
  gstreamer gstreamer-0_10 gstreamer-0_10-plugin-gnomevfs 
  gstreamer-0_10-plugins-base gstreamer-plugins-bad gstreamer-plugins-base 
  gstreamer-plugins-good libgstapp-0_10-0 libgstapp-1_0-0 libgstaudio-1_0-0 
  libgstbasecamerabinsrc-1_0-0 libgstcodecparsers-1_0-0 libgstfft-1_0-0 
  libgstinterfaces-0_10-0 libgstpbutils-1_0-0 libgstphotography-1_0-0 
  libgstreamer-0_10-0 libgstreamer-1_0-0 libgstriff-1_0-0 libgstrtp-1_0-0 
  libgstrtsp-1_0-0 libgstsdp-1_0-0 libgsttag-1_0-0 libgstvideo-1_0-0 
  libmjpegutils-2_0-0 libquicktime0 libquvi-scripts libsox2 libstrigi0 
  libxmmsclient-glib1 libxmmsclient6 mjpegtools python-gstreamer-0_10 sox 
  strigi typelib-1_0-Gst-1_0 typelib-1_0-GstAudio-1_0 
  typelib-1_0-GstPbutils-1_0 typelib-1_0-GstTag-1_0 typelib-1_0-GstVideo-1_0 
  xmms2 xmms2-plugin-base 

The following packages are going to be upgraded:
  MPlayer gmplayer libmpg123-0 smplayer wine-mp3 

5 packages to upgrade.
Overall download size: 20.5 MiB. After the operation, additional 28.0 KiB will 
be used.
Continue? [y/n/?] (y): y
Retrieving package libmpg123-0-1.15.3-1.1.i586
                                           (1/5),  91.3 KiB (202.6 KiB unpacked)
Retrieving: libmpg123-0-1.15.3-1.1.i586.rpm .................[done (18.3 KiB/s)]
Retrieving package MPlayer-1.1+35127-2.25.i586
                                           (2/5),  18.9 MiB ( 52.4 MiB unpacked)
Retrieving: MPlayer-1.1+35127-2.25.i586.rpm .................[done (73.1 KiB/s)]
Retrieving package wine-mp3-1.1.39-12.22.i586
                                           (3/5),  16.7 KiB ( 83.1 KiB unpacked)
Retrieving: wine-mp3-1.1.39-12.22.i586.rpm ...............................[done]
Retrieving package gmplayer-1.1+35127-2.25.i586
                                           (4/5), 301.7 KiB (295.8 KiB unpacked)
Retrieving: gmplayer-1.1+35127-2.25.i586.rpm ................[done (49.0 KiB/s)]
Retrieving package smplayer-0.8.4-1.8.i586 (5/5),   1.3 MiB (  3.2 MiB unpacked)
Retrieving: smplayer-0.8.4-1.8.i586.rpm .....................[done (53.4 KiB/s)]
(1/5) Installing: libmpg123-0-1.15.3-1.1 .................................[done]
(2/5) Installing: MPlayer-1.1+35127-2.25 .................................[done]
(3/5) Installing: wine-mp3-1.1.39-12.22 ..................................[done]
(4/5) Installing: gmplayer-1.1+35127-2.25 ................................[done]
(5/5) Installing: smplayer-0.8.4-1.8 .....................................[done]
root[504] lo

Now from the bottom of NM log:

root[501] tail -f /var/log/NetworkManager
2013-04-19T21:51:39.443841-07:00 linux-uso4 NetworkManager[664]: <warn> No agents were available for this request.
2013-04-19T21:51:39.444402-07:00 linux-uso4 NetworkManager[664]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
2013-04-19T21:51:39.444707-07:00 linux-uso4 NetworkManager[664]: <info> Marking connection '3rivers' invalid.
2013-04-19T21:51:39.445103-07:00 linux-uso4 NetworkManager[664]: <warn> Activation (wlan0) failed for connection '3rivers'
2013-04-19T21:51:39.445516-07:00 linux-uso4 NetworkManager[664]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
2013-04-19T21:51:39.445862-07:00 linux-uso4 NetworkManager[664]: <info> (wlan0): deactivating device (reason 'none') [0]
2013-04-19T22:00:01.742174-07:00 linux-uso4 /usr/sbin/cron[5781]: pam_unix(crond:session): session opened for user root by (uid=0)
2013-04-19T22:00:01.788616-07:00 linux-uso4 /USR/SBIN/CRON[5781]: pam_unix(crond:session): session closed for user root
2013-04-19T22:15:01.793634-07:00 linux-uso4 /usr/sbin/cron[5828]: pam_unix(crond:session): session opened for user root by (uid=0)
2013-04-19T22:15:01.833490-07:00 linux-uso4 /USR/SBIN/CRON[5828]: pam_unix(crond:session): session closed for user root

Now hwinfo --wlan:

 root[502] hwinfo --wlan
20: USB 00.0: 0282 WLAN controller                              
  [Created at usb.122]
  Unique ID: KRJj.x9IMWGGtcg8
  Parent ID: uIhY.2DFUsyrieMD
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0
  SysFS BusID: 3-1: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: 48:02:2a:e3:7d:34
  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=no, avail=yes, need=no, active=unknown
  Attached to: #19 (Hub)
root[503]

So where do I do from here? Are there anymore logs to check?

Am I up to buying another wlan or attempting to build a custom driver from the Chinese tarball?

If the recommendation is to buy another wlan, what would you guys get if you were me? Heboland.

20

Hi heboland

You reported earlier that you’re using LXDE, so I assume using the gnome network manager and keyring?

  1. How are you storing the connection secrets?
  2. Did you create the connection as a user or system connection?

25.7.2. Storing Passwords and Credentials¶](http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.nm.html#sec.nm.sec.store) If you do not want to re-enter your credentials each time you want to connect to an encrypted network, you can use the desktop-specific tools GNOME Keyring Manager or KWalletManager to store your credentials encrypted on the disk, secured by a master password.

openSUSE 12.3: Chapter 25. Using NetworkManager