Help please to configure a Realtek USB Wifi (SOLVED, thanks)

[BJF]

Homework done, dongle is alive and well, with an indicated signal strength of 100% at the 10m test distance. Survives Hibernation (1 of) and reboot, (2 of), but dropped out and became invisible after about 10 minutes of up-time. Rebooted with the old kernel and it was there as a realtek wifi on wlan0 at 50% signal. Rebooted to the current late kernel with it shown as AMD etc on wlan1. I don't entirely trust it yet. It takes a while to come up and faff's about showing and hiding the red circle with the cross, then hiding it, then going to the green circle for a while before starting. Almost as if it is having an argument in the install somewhere. Where might I look for conflict like this, and what could I remove/uninstall to help this? Suggestions? Oh, and WOO-HOO!

[muungwana]

when things have settled down,as root,run "tail -n 60 /var/log/syslog" and paste its output

There could be something in the logs reflecting what you are seeing.

[BJF]

[mdm@localhost ~]$ su root
Password:
[root@localhost mdm]# tail -n 60 /var/log/syslog
Aug  8 17:24:51 localhost avahi-daemon[4300]: New relevant interface wlan1.IPv4 for mDNS.
Aug  8 17:24:51 localhost avahi-daemon[4300]: Registering new address record for 192.168.2.8 on wlan1.IPv4.
Aug  8 17:24:54 localhost ifplugd(wlan1)[2573]: client: PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
Aug  8 17:24:54 localhost ifplugd(wlan1)[2573]: client: --- 192.168.2.1 ping statistics ---
Aug  8 17:24:54 localhost ifplugd(wlan1)[2573]: client: 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
Aug  8 17:24:54 localhost avahi-daemon[4300]: Withdrawing address record for 192.168.2.8 on wlan1.
Aug  8 17:24:54 localhost avahi-daemon[4300]: Leaving mDNS multicast group on interface wlan1.IPv4 with address 192.168.2.8.
Aug  8 17:24:54 localhost avahi-daemon[4300]: Interface wlan1.IPv4 no longer relevant for mDNS.
Aug  8 17:24:54 localhost dhclient: Trying recorded lease 192.168.2.3
Aug  8 17:24:54 localhost avahi-daemon[4300]: Joining mDNS multicast group on interface wlan1.IPv4 with address 192.168.2.3.
Aug  8 17:24:54 localhost avahi-daemon[4300]: New relevant interface wlan1.IPv4 for mDNS.
Aug  8 17:24:54 localhost avahi-daemon[4300]: Registering new address record for 192.168.2.3 on wlan1.IPv4.
Aug  8 17:24:54 localhost ifplugd(wlan1)[2573]: client: PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
Aug  8 17:24:54 localhost ifplugd(wlan1)[2573]: client: --- 192.168.2.1 ping statistics ---
Aug  8 17:24:54 localhost ifplugd(wlan1)[2573]: client: 1 packets transmitted, 1 received, 0% packet loss, time 0ms
Aug  8 17:24:54 localhost ifplugd(wlan1)[2573]: client: rtt min/avg/max/mdev = 10.317/10.317/10.317/0.000 ms
Aug  8 17:24:55 localhost NET[5077]: /sbin/dhclient-script : updated /etc/resolv.conf
Aug  8 17:24:55 localhost dhclient: bound: immediate renewal.
Aug  8 17:24:55 localhost dhclient: DHCPREQUEST on wlan1 to 192.168.2.1 port 67
Aug  8 17:24:55 localhost ifplugd(wlan1)[2573]: client:  done.
Aug  8 17:24:55 localhost dhclient: DHCPNAK from 192.168.2.1
Aug  8 17:24:55 localhost avahi-daemon[4300]: Withdrawing address record for 192.168.2.3 on wlan1.
Aug  8 17:24:55 localhost avahi-daemon[4300]: Leaving mDNS multicast group on interface wlan1.IPv4 with address 192.168.2.3.
Aug  8 17:24:55 localhost avahi-daemon[4300]: Interface wlan1.IPv4 no longer relevant for mDNS.
Aug  8 17:24:56 localhost ifplugd(wlan1)[2573]: client: NETLINK: Packet too small or truncated! 56!=16!=1008
Aug  8 17:24:56 localhost ifplugd(wlan1)[2573]: Program executed successfully.
Aug  8 17:24:57 localhost dhclient: DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 3
Aug  8 17:24:57 localhost dhclient: DHCPOFFER from 192.168.2.1
Aug  8 17:24:57 localhost dhclient: DHCPREQUEST on wlan1 to 255.255.255.255 port 67
Aug  8 17:24:57 localhost dhclient: DHCPACK from 192.168.2.1
Aug  8 17:24:57 localhost avahi-daemon[4300]: Joining mDNS multicast group on interface wlan1.IPv4 with address 192.168.2.5.
Aug  8 17:24:57 localhost avahi-daemon[4300]: New relevant interface wlan1.IPv4 for mDNS.
Aug  8 17:24:57 localhost avahi-daemon[4300]: Registering new address record for 192.168.2.5 on wlan1.IPv4.
Aug  8 17:24:57 localhost NET[5210]: /sbin/dhclient-script : updated /etc/resolv.conf
Aug  8 17:24:57 localhost dhclient: bound to 192.168.2.5 -- renewal in 15198289 seconds.
Aug  8 17:25:26 localhost ntpd_initres[4579]: host name not found: 0.nz.pool.ntp.org
Aug  8 17:25:26 localhost ntpd_initres[4579]: host name not found: 1.nz.pool.ntp.org
Aug  8 17:25:26 localhost ntpd_initres[4579]: host name not found: 2.nz.pool.ntp.org
Aug  8 17:25:52 localhost laptop-mode: Laptop mode
Aug  8 17:25:52 localhost laptop-mode: enabled,
Aug  8 17:25:52 localhost laptop-mode: active [unchanged]
Aug  8 17:26:56 localhost laptop-mode: Laptop mode
Aug  8 17:26:56 localhost laptop-mode: enabled,
Aug  8 17:26:56 localhost laptop-mode: active [unchanged]
Aug  8 17:27:28 localhost ntpd_initres[4579]: host name not found: 0.nz.pool.ntp.org
Aug  8 17:27:28 localhost ntpd_initres[4579]: host name not found: 1.nz.pool.ntp.org
Aug  8 17:27:28 localhost ntpd_initres[4579]: host name not found: 2.nz.pool.ntp.org
Aug  8 17:27:38 localhost ntpd[4573]: synchronized to LOCAL(0), stratum 10
Aug  8 17:27:38 localhost ntpd[4573]: kernel time sync status change 0001
Aug  8 17:28:00 localhost laptop-mode: Laptop mode
Aug  8 17:28:00 localhost laptop-mode: enabled,
Aug  8 17:28:00 localhost laptop-mode: active [unchanged]
Aug  8 17:29:04 localhost laptop-mode: Laptop mode
Aug  8 17:29:04 localhost laptop-mode: enabled,
Aug  8 17:29:04 localhost laptop-mode: active [unchanged]
Aug  8 17:29:23 localhost ntpd[4573]: Listening on interface #6 wlan1, 192.168.2.5#123 Enabled
Aug  8 17:29:23 localhost ntpd[4573]: new interface(s) found: waking up resolver
Aug  8 17:29:25 localhost ntpd_initres[4579]: host name not found: 0.nz.pool.ntp.org
Aug  8 17:29:25 localhost ntpd_initres[4579]: host name not found: 1.nz.pool.ntp.org
Aug  8 17:29:25 localhost ntpd_initres[4579]: host name not found: 2.nz.pool.ntp.org
[root@localhost mdm]#

Things aren't settling down. Desktop reports Wlan0 trying to connect and dropping, even though I have deleted Wlan), the Realtek 802.11n device, twice in Configure>Wireless>>.
The AMD connection is up and posting now, but doesn't survive Hibernation and is REALLY slow to come up. It reports a 98% signal at 10m but is prone to drop out and reconnect, and if I move or pick the laptop up it comes back straight away. I'm sorry, but I don't believe that it really has 98% if it is sensitive to movement. I suspect too that there is a conflict of epic proportions going on with two devices which are really the same device trying to connect at the same time. But then you'd have read the runes by now and have figured it out!

  <Big Cheesy's

[sling-shot]

Umm... This discussion has progressed a lot and I do not understand most of it.

But if you are interested in trying it in another way....

If you go to the page http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=48&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true#RTL8188CUS
and scroll down to RTL8188CUS section, you will find this file under the Linux subsection from any of the mirrors :

RTL819xCU _USB_linux_v3.4.3_4369.20120622.zip

It contains an installer "install.sh".
I have done this for nVidia drivers before. I think you should extract the .zip file and navigate to the directory in Konsole and type

Code: [Select]

su
<root password>
sh install.sh

This is likely to install the correct driver.
-SS.

NOTE : NO WARRANTIES ;-)

[BJF]

Slingshot: I'm getting quite a list of drivers associated with this device installed on the laptop. That Realtek card driver you pointed me at, for instance, is still there. Bear in mind that I'm inexperienced in Linux but have a certain amount of native dot-connecting ability. I now see a machine which keeps reinstalling Wlan0, the Realtek 802:11n, if I remove it, ndiswrapper blacklisted but still potentially capable given the chance, of having a go at either form of the same device in the port, and the Realtek rtl8192cu driver which seems to unsuccessfully be competing and now failing to load. Couple this with the amount of P***ing about that is going on each wifi launch, and the unconnected signal when I plug an ethernet connection in to post successfully to the Forum, and I start to wonder...
Gentlemen, can we establish a base line again, and then discount what hasn't worked, and go to new pastures?

 

[Yankee]

Slingshot: I'm getting quite a list of drivers associated with this device installed on the laptop. That Realtek card driver you pointed me at, for instance, is still there. Bear in mind that I'm inexperienced in Linux but have a certain amount of native dot-connecting ability. I now see a machine which keeps reinstalling Wlan0, the Realtek 802:11n, if I remove it, ndiswrapper blacklisted but still potentially capable given the chance, of having a go at either form of the same device in the port, and the Realtek rtl8192cu driver which seems to unsuccessfully be competing and now failing to load. Couple this with the amount of P***ing about that is going on each wifi launch, and the unconnected signal when I plug an ethernet connection in to post successfully to the Forum, and I start to wonder...
Gentlemen, can we establish a base line again, and then discount what hasn't worked, and go to new pastures?

 

So you need to blacklist all the drivers that do not work,
disable connect at boot for now, and reboot.

Select a driver(s) from the Realtek site that appears
compatible for your kernel and "modprobe rtlxxxxxxx"
from the root terminal to load the driver to test it,
from the directory it's in.

Reconnect and see if it works.

Probably worth one more try.   Nothing else is there.

Defective wifi stick or general hardware/driver incompatibility
could be the story ?

[BJF]

Guys, I'm struggling with which way is up here.

 Got/already had the driver Slingshot pointed me at, so I installed it from instructions. The dongle woke up immediately as the AMD, strong and tireless. Survived Hibernate and a reboot, then went away. I blacklisted rtl8192cu, and it came back as Realtek 802:11n on Wlan1, which was the address showing for the AMD incarnation of the thing, when the Realtek was listing as Wlan0. That too survived a reboot, but I had to Connect it manually to the router. Then it too went. No sign of the router in Connect, and a long "little green circle" in the toolbar before it went red-no-connection.

This morning (my time) I booted it up again, and it paused at the bottom of the parade with some lines indicating Unable to resolve Wlan1, and a problem with line 27(?) of /etc/wlan/shared(?) and too many (somethings(drivers?)), sat here a moment too little for me to get notes, and booted to Desktop with no dongle. A reboot was missing those extra lines but still no wifi.

Conclusion: With ndiswrapper and rtl8192cu blacklisted and the rtl8188/rtl8192 driver installed, there is still something left over unspotted that is poisoning the install each time a new connection is achieved with a new driver. And I'm not smart enough to find it and am reliant on inspiration from you guys.

Is there a clue in this morning's boot parade? I've looked for an /etc/wlan/shared file, and not found one. Is there a file with such a wlan list we could look at? How do I wipe the slate completely clean as per Slingshot's advice? I don't accurately know what I'm blacklisting in order to get 'em all! It certainly appears as if the dongle is alive and willing but something is coming out of left field and corrupting the installed driver after the initial successes. Reading back shows several instances of this in the thread.

Thank you all for your input and patience so far too.
-John. 
 
 

[Yankee]

Got/already had the driver Slingshot pointed me at, so I installed it from instructions. The dongle woke up immediately as the AMD, strong and tireless. Survived Hibernate and a reboot, then went away. I blacklisted rtl8192cu, and it came back as Realtek 802:11n on Wlan1, which was the address showing for the AMD incarnation of the thing, when the Realtek was listing as Wlan0. That too survived a reboot, but I had to Connect it manually to the router. Then it too went. No sign of the router in Connect, and a long "little green circle" in the toolbar before it went red-no-connection.

You've done alot of things watching this, so I may duplicate something already done.
Search "dmesg" for wlan0 and wlan1, same for the system log, when the device fails.
Modprobe should only install one driver or give a FATAL ERROR message, and when it's
UP it's UP, if it goes DOWN then driver or hardware problem.

Computers do not control men, men control computers, but in this case I think the
computer is winning.   

[Yankee]

@BJF

If you're sure you've only got one driver successfully loaded,
try disabling the screensaver and all power-management features
of the screensaver, and set this command "iwconfig wlan0 rate 5M"
Adjust the m/bitrate to your connection speed to keep the speed
stable.  Both could help if the problem is a too old or too new of a kernel.

Out of ideas otherwise.

FF

[BJF]

FF: dmesg...

[mdm@localhost ~]$ su root

Password:

[root@localhost mdm]# dmesg | tail -n 50

ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 5

PCI: setting IRQ 5 as level-triggered

snd_ali5451 0000:00:06.0: PCI INT A -> Link[LNKH] -> GSI 5 (level, low) -> IRQ 5

pci 0000:01:05.0: power state changed by ACPI to D0

pci 0000:01:05.0: power state changed by ACPI to D0

pci 0000:01:05.0: PCI INT A -> Link[LNKC] -> GSI 10 (level, low) -> IRQ 10

AC'97 1 does not respond - RESET

AC'97 1 access is not valid [0xffffffff], removing mixer.

ali mixer 1 creating error.

eth0: DSPCFG accepted after 0 usec.

eth0: DSPCFG accepted after 0 usec.

NET: Registered protocol family 10

cfg80211: Calling CRDA for country: NZ

cfg80211: Regulatory domain changed to country: NZ

cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)

cfg80211:     (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 3000 mBm)

cfg80211:     (5170000 KHz - 5250000 KHz @ 20000 KHz), (300 mBi, 2300 mBm)

cfg80211:     (5250000 KHz - 5330000 KHz @ 20000 KHz), (300 mBi, 2300 mBm)

cfg80211:     (5735000 KHz - 5835000 KHz @ 20000 KHz), (300 mBi, 3000 mBm)

eth0: DSPCFG accepted after 0 usec.

ADDRCONF(NETDEV_UP): eth0: link is not ready

rtl8192cu: MAC auto ON okay!

rtl8192cu: Tx queue select: 0x05

rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin

ADDRCONF(NETDEV_UP): wlan1: link is not ready

rtl8192cu: MAC auto ON okay!

rtl8192cu: Tx queue select: 0x05

rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin

ADDRCONF(NETDEV_UP): wlan1: link is not ready

ata1.00: configured for UDMA/100

ata1: EH complete

sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

EXT4-fs (sda1): re-mounted. Opts: commit=600

eth0: DSPCFG accepted after 0 usec.

eth0: DSPCFG accepted after 0 usec.

ip_tables: (C) 2000-2006 Netfilter Core Team

EXT4-fs (sda1): re-mounted. Opts: commit=600

Netfilter messages via NETLINK v0.30.

nf_conntrack version 0.5.0 (6999 buckets, 27996 max)

ip6_tables: (C) 2000-2006 Netfilter Core Team

NF_TPROXY: Transparent proxy support initialized, version 4.1.0

NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.

ctnetlink v0.93: registering with nfnetlink.

ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully

xt_time: kernel timezone is +1200

u32 classifier

    Actions configured

usbcore: registered new interface driver snd-usb-audio

ndiswrapper version 1.58rc1 loaded (smp=yes, preempt=yes)

usbcore: registered new interface driver ndiswrapper

[root@localhost mdm]#

-Now that's peculiar!

[BJF]

...and syslog:

[mdm@localhost ~]$ su root

Password:

[root@localhost mdm]# tail -n 60 /var/log/syslog

Aug 10 14:42:10 localhost klogd: NF_TPROXY: Transparent proxy support initialized, version 4.1.0

Aug 10 14:42:10 localhost klogd: NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.

Aug 10 14:42:10 localhost klogd: ctnetlink v0.93: registering with nfnetlink.

Aug 10 14:42:10 localhost klogd: ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully

Aug 10 14:42:11 localhost ntpdate[3671]: can't find host 0.nz.pool.ntp.org

Aug 10 14:42:11 localhost ntpdate[3671]: can't find host 1.nz.pool.ntp.org

Aug 10 14:42:11 localhost ntpdate[3671]: can't find host 2.nz.pool.ntp.org

Aug 10 14:42:11 localhost ntpdate[3671]: no servers can be used, exiting

Aug 10 14:42:12 localhost ntpd[3769]: ntpd 4.2.4p7@1.1607 Fri Jun 26 06:39:16 UTC 2009 (1)

Aug 10 14:42:12 localhost ntpd[3774]: precision = 1.000 usec

Aug 10 14:42:12 localhost ntpd[3774]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16

Aug 10 14:42:12 localhost ntpd[3774]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled

Aug 10 14:42:12 localhost ntpd[3774]: Listening on interface #1 wildcard, ::#123 Disabled

Aug 10 14:42:12 localhost ntpd[3774]: Listening on interface #2 lo, ::1#123 Enabled

Aug 10 14:42:12 localhost ntpd[3774]: Listening on interface #3 lo, 127.0.0.1#123 Enabled

Aug 10 14:42:12 localhost ntpd[3774]: kernel time sync status 0040

Aug 10 14:42:12 localhost ntpd[3774]: frequency initialized 15.573 PPM from /var/lib/ntp/drift

Aug 10 14:42:12 localhost klogd: xt_time: kernel timezone is +1200

Aug 10 14:42:14 localhost ntpd_initres[3784]: host name not found: 0.nz.pool.ntp.org

Aug 10 14:42:14 localhost ntpd_initres[3784]: host name not found: 1.nz.pool.ntp.org

Aug 10 14:42:14 localhost ntpd_initres[3784]: host name not found: 2.nz.pool.ntp.org

Aug 10 14:42:15 localhost klogd: u32 classifier

Aug 10 14:42:15 localhost klogd:     Actions configured

Aug 10 14:42:17 localhost logger: Shorewall started

Aug 10 14:42:17 localhost klogd: usbcore: registered new interface driver snd-usb-audio

Aug 10 14:42:17 localhost klogd: ndiswrapper version 1.58rc1 loaded (smp=yes, preempt=yes)

Aug 10 14:42:18 localhost klogd: usbcore: registered new interface driver ndiswrapper

Aug 10 14:42:28 localhost blueman-mechanism: Exiting 

Aug 10 14:43:00 localhost laptop-mode: Laptop mode

Aug 10 14:43:00 localhost laptop-mode: enabled,

Aug 10 14:43:00 localhost laptop-mode: active [unchanged]

Aug 10 14:43:16 localhost ntpd_initres[3784]: host name not found: 0.nz.pool.ntp.org

Aug 10 14:43:16 localhost ntpd_initres[3784]: host name not found: 1.nz.pool.ntp.org

Aug 10 14:43:16 localhost ntpd_initres[3784]: host name not found: 2.nz.pool.ntp.org

Aug 10 14:44:02 localhost laptop-mode: Laptop mode

Aug 10 14:44:02 localhost laptop-mode: enabled,

Aug 10 14:44:02 localhost laptop-mode: active [unchanged]

Aug 10 14:45:04 localhost laptop-mode: Laptop mode

Aug 10 14:45:04 localhost laptop-mode: enabled,

Aug 10 14:45:04 localhost laptop-mode: active [unchanged]

Aug 10 14:45:18 localhost ntpd_initres[3784]: host name not found: 0.nz.pool.ntp.org

Aug 10 14:45:18 localhost ntpd_initres[3784]: host name not found: 1.nz.pool.ntp.org

Aug 10 14:45:18 localhost ntpd_initres[3784]: host name not found: 2.nz.pool.ntp.org

Aug 10 14:45:27 localhost ntpd[3774]: synchronized to LOCAL(0), stratum 10

Aug 10 14:45:27 localhost ntpd[3774]: kernel time sync status change 0001

Aug 10 14:46:06 localhost laptop-mode: Laptop mode

Aug 10 14:46:06 localhost laptop-mode: enabled,

Aug 10 14:46:06 localhost laptop-mode: active [unchanged]

Aug 10 14:47:08 localhost laptop-mode: Laptop mode

Aug 10 14:47:08 localhost laptop-mode: enabled,

Aug 10 14:47:08 localhost laptop-mode: active [unchanged]

Aug 10 14:48:13 localhost laptop-mode: Laptop mode

Aug 10 14:48:13 localhost laptop-mode: enabled,

Aug 10 14:48:13 localhost laptop-mode: active [unchanged]

Aug 10 14:49:16 localhost laptop-mode: Laptop mode

Aug 10 14:49:16 localhost laptop-mode: enabled,

Aug 10 14:49:16 localhost laptop-mode: active [unchanged]

Aug 10 14:49:20 localhost ntpd_initres[3784]: host name not found: 0.nz.pool.ntp.org

Aug 10 14:49:20 localhost ntpd_initres[3784]: host name not found: 1.nz.pool.ntp.org

Aug 10 14:49:20 localhost ntpd_initres[3784]: host name not found: 2.nz.pool.ntp.org

[root@localhost mdm]#

...and /etc/modprobe.d/blacklist

blacklist ssb

blacklist ssb
blacklist ndiswrapper

[BJF]

Gentlepeople: a note of cautious optimism here. I got brave. It's easy when one has clever friends. My day job involves noise and earmuffs and time alone with thoughts. Dangerous thoughts. When I got home, after posting the dmesg and syslog, I removed ndiswrapper completely. Then I blacklisted the native rtl8192cu driver because the laptop ran hot and got disobedient if I plugged the dongle in to check progress. Made an assumption that a couple of left-overs might still be competing. (Assumptions=dangerous). But in this case, which-ever of the pantheon of installed things tried out from the beginning of this thread remains active, it is now, so far, providing a solid 99% indicated signal on the test range (the dining room). You clever people will no doubt have a way of discovering which it is. But no matter. The Realtek thingy appears as its AMD alter-ego, and as Wlan1. It survives multiple boot-up's and comes up quite quickly after the Desktop is all in. The laptop chokes on shut-the-lid Hibernation but let's see what happens after the old beast settles down. Things that access the router via the connection are fast too. And finally, the computer runs cooler than in recent memory.

Watch this space! 

[sling-shot]

I suppose you could boot into a LiveCD or LiveUSB, fully update, and then try installing the Realtek website driver and check. if things work well, then OK. If not just stick with the current setup which is working for you now.
-SS.

[Yankee]

FF: dmesg...

[mdm@localhost ~]$ su root

Password:

[root@localhost mdm]# dmesg | tail -n 50

ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 5

PCI: setting IRQ 5 as level-triggered

snd_ali5451 0000:00:06.0: PCI INT A -> Link[LNKH] -> GSI 5 (level, low) -> IRQ 5

pci 0000:01:05.0: power state changed by ACPI to D0

pci 0000:01:05.0: power state changed by ACPI to D0

pci 0000:01:05.0: PCI INT A -> Link[LNKC] -> GSI 10 (level, low) -> IRQ 10

AC'97 1 does not respond - RESET

AC'97 1 access is not valid [0xffffffff], removing mixer.

ali mixer 1 creating error.

eth0: DSPCFG accepted after 0 usec.

eth0: DSPCFG accepted after 0 usec.

NET: Registered protocol family 10

cfg80211: Calling CRDA for country: NZ

cfg80211: Regulatory domain changed to country: NZ

cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)

cfg80211:     (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 3000 mBm)

cfg80211:     (5170000 KHz - 5250000 KHz @ 20000 KHz), (300 mBi, 2300 mBm)

cfg80211:     (5250000 KHz - 5330000 KHz @ 20000 KHz), (300 mBi, 2300 mBm)

cfg80211:     (5735000 KHz - 5835000 KHz @ 20000 KHz), (300 mBi, 3000 mBm)

eth0: DSPCFG accepted after 0 usec.

ADDRCONF(NETDEV_UP): eth0: link is not ready

rtl8192cu: MAC auto ON okay!

rtl8192cu: Tx queue select: 0x05

rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin

ADDRCONF(NETDEV_UP): wlan1: link is not ready

rtl8192cu: MAC auto ON okay!

rtl8192cu: Tx queue select: 0x05

rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin

ADDRCONF(NETDEV_UP): wlan1: link is not ready

ata1.00: configured for UDMA/100

ata1: EH complete

sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

EXT4-fs (sda1): re-mounted. Opts: commit=600

eth0: DSPCFG accepted after 0 usec.

eth0: DSPCFG accepted after 0 usec.

ip_tables: (C) 2000-2006 Netfilter Core Team

EXT4-fs (sda1): re-mounted. Opts: commit=600

Netfilter messages via NETLINK v0.30.

nf_conntrack version 0.5.0 (6999 buckets, 27996 max)

ip6_tables: (C) 2000-2006 Netfilter Core Team

NF_TPROXY: Transparent proxy support initialized, version 4.1.0

NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.

ctnetlink v0.93: registering with nfnetlink.

ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully

xt_time: kernel timezone is +1200

u32 classifier

    Actions configured

usbcore: registered new interface driver snd-usb-audio

ndiswrapper version 1.58rc1 loaded (smp=yes, preempt=yes)

usbcore: registered new interface driver ndiswrapper

[root@localhost mdm]#

-Now that's peculiar!

Hi,

The 2.6.38.8 kernel is probably the most reliable for this,
but, when you get the wlan0 working again whatever kernel
try running in terminal:

iwlist wlan0 (or wlan1) bitrate

take the highest bitrate you see and post it in

iwconfig wlan0 rate 50M (or what rate shows)

Have to run after every boot after wlan0 connects to see if it
solves the problem.   Will usually solidify the connection stopping
disconnections if any further problem.   Post back results sometime
and to make the setting permanent if not so.

FF

[BJF]

FF: This wasn't what I expected...

[mdm@localhost ~]$ su root
Password:
[root@localhost mdm]# iwlist wlan1 bitrate
wlan1     4 available bit-rates :
     1 Mb/s
     2 Mb/s
     5.5 Mb/s
     11 Mb/s
          Current Bit Rate:54 Mb/s

[root@localhost mdm]#

(Edit) Something new, thumb drives and extension HDD's won't unmount. "An application" is using the port. Can we check and see what it is somehow? Might be the Realtek card reader install that has taken over, and is also running the wifi!