[12.04] ASUS USB-N13 WiFi Adapter doesn't connect to the network

[gower]

I unplugged all my internet connections and rebooted.

"sudo cat /var/log/syslog | grep ndis" from last hour:

Nov  3 17:22:41 janek-desktop kernel: [12223.208847] ndiswrapper version 1.57 loaded (smp=yes, preempt=no)
Nov  3 17:22:41 janek-desktop kernel: [12223.257495] usbcore: registered new interface driver ndiswrapper
Nov  3 17:26:41 janek-desktop kernel: [   22.012531] rndis_host 2-1:1.0: usb0: register 'rndis_host' at usb-0000:00:1d.7-1, RNDIS device, de:52:c2:d6:a6:5c
Nov  3 17:26:41 janek-desktop kernel: [   22.012701] usbcore: registered new interface driver rndis_host
Nov  3 17:26:41 janek-desktop NetworkManager[766]: <info> (usb0): new Ethernet device (driver: 'rndis_host' ifindex: 3)
Nov  3 17:26:41 janek-desktop kernel: [   22.179275] usbcore: registered new interface driver rndis_wlan
Nov  3 17:40:05 janek-desktop kernel: [  825.849882] rndis_host 2-1:1.0: usb0: unregister 'rndis_host' usb-0000:00:1d.7-1, RNDIS device

"lsmod | grep -e rtl -e 80211" gives nothing - empty output.

EDIT: Thank you very much for helping me, I hope we'll figure it out. I have to leave now, but I'll be back in a few hours.

[chili555]

Nov 3 17:26:41 janek-desktop kernel: [ 22.012531] rndis_host 2-1:1.0: usb0: register 'rndis_host' at usb-0000:00:1d.7-1, RNDIS device, de:52:c2:d6:a6:5c
Nov 3 17:26:41 janek-desktop kernel: [ 22.012701] usbcore: registered new interface driver rndis_host
Nov 3 17:26:41 janek-desktop NetworkManager[766]: <info> (usb0): new Ethernet device (driver: 'rndis_host' ifindex: 3)
Nov 3 17:26:41 janek-desktop kernel: [ 22.179275] usbcore: registered new interface driver rndis_wlan
Nov 3 17:40:05 janek-desktop kernel: [ 825.849882] rndis_host 2-1:1.0: usb0: unregister 'rndis_host' usb-0000:00:1d.7-1, RNDIS device

I assume all this is your cellphone, tethered??

"lsmod | grep -e rtl -e 80211" gives nothing - empty output.

Perfect!

I'll check in later.

[gower]

During last reboot (17:40) both my cellphone and N13 were removed. In previous one, yes I suppose it's my phone.

[gower]

Any clues what else can I do?

[chili555]

Any clues what else can I do?

Your log entries for ndiswrapper show nothing remarkable. Check syslog or syslog.1 again and let's see the freeze. If you still can't see anything, I'm afraid you'll need to freeze it so we can see the reasons why in syslog.

[gower]

So I went through syslog once again after kernel panic but there is no sign of this reboot. System crash has no entry in syslog.

I don't know how to get panic's logs so I've simply taken pictures of panic screen. Maybe you can find something on them.

[chili555]

It's very hard to troubleshoot from what we see here. Essentially, the freeze has already started and we see the wreckage flying. We don't see the specific ndiswrapper error(s) that led to the freeze. As I see it, we have a few options available. First, we can try to troubleshoot your current ndiswrapper installation. Let's see if there are any remnants of the old 32-bit files.

ls /etc/ndiswrapper

We can see if there are any errors or warnings. With the device NOT inserted:

sudo modprobe ndiswrapper
dmesg |grep ndiswrapper

The second thing we can try is to capture a more complete log. Insert the device and let it freeze. After a reboot, run:

sudo cat /var/log/syslog.1 > gower.txt
sudo cat /var/log/syslog >> gower.txt
zip gower.zip gower.txt

Find the file gower.zip in your user directory, transfer it on a USB or similar and attach it to your reply.

Next, depending on the syslog results, we can compile a newer version of ndiswrapper or remove it altogether and try again to get rtl8192cu to work correctly.

[gower]

ls /etc/ndiswrapper/

netrtwlanu

ls /etc/ndiswrapper/netrtwlanu/

04BB:094C.F.conf  050D:1004.F.conf  07B8:8178.F.conf  0BDA:8176.F.conf  0BDA:817F.F.conf  0DF6:005C.F.conf  13D3:3358.F.conf  2019:1201.F.conf  20F4:648B.F.conf  netrtwlanu.inf
04F2:AFF7.F.conf  050D:1102.F.conf  07B8:8189.F.conf  0BDA:8177.F.conf  0BDA:8186.F.conf  0DF6:0061.F.conf  13D3:3359.F.conf  2019:4902.F.conf  4855:0090.F.conf  rtwlanu.sys
04F2:AFF8.F.conf  050D:2102.F.conf  0B05:17AB.F.conf  0BDA:8178.F.conf  0BDA:818A.F.conf  0E66:0019.F.conf  2001:3307.F.conf  2019:AB2A.F.conf  4855:0091.F.conf
04F2:AFF9.F.conf  050D:2103.F.conf  0B05:17BA.F.conf  0BDA:817A.F.conf  0BDA:8192.F.conf  0E66:0020.F.conf  2001:3308.F.conf  2019:AB2B.F.conf  4856:0091.F.conf
04F2:AFFA.F.conf  0586:341F.F.conf  0BDA:018A.F.conf  0BDA:817B.F.conf  0BDA:819A.F.conf  0EB0:9071.F.conf  2001:3309.F.conf  2019:AB2E.F.conf  7392:7811.F.conf
04F2:AFFB.F.conf  06F8:E033.F.conf  0BDA:317F.F.conf  0BDA:817C.F.conf  0BFF:8160.F.conf  103C:1629.F.conf  2001:330A.F.conf  2019:ED17.F.conf  7392:7822.F.conf
04F2:AFFC.F.conf  07AA:0056.F.conf  0BDA:8170.F.conf  0BDA:817E.F.conf  0DF6:0052.F.conf  13D3:3357.F.conf  2001:330B.F.conf  20F4:624D.F.conf  CDAB:8010.F.conf

sudo modprobe ndiswrapper
dmesg |grep ndiswrapper

[ 2190.634577] ndiswrapper version 1.57 loaded (smp=yes, preempt=no)
[ 2190.651555] usbcore: registered new interface driver ndiswrapper

I've changed the

*.*;auth,authpriv.none     -/var/log/syslog

line in /etc/rsyslog.d/50-default.conf to

*.*;auth,authpriv.none     /var/log/syslog

I had read that this may help saving kernel panic's logs.

I inserted the devide shortly after 20:30.

[chili555]

Everything here looks entirely normal. In your syslogs, there is no sign of a freeze, crash, oops, smoke, sparks, etc. There is also no mention of ndiswrapper!

I suggest we remove ndiswrapper altogether:

sudo ndiswrapper -e netrtwlanu
sudo rm -rf /etc/niswrapper/*

Now remove the blacklist:

sudo gedit /etc/modprobe.d/blacklist.conf

Remove the line 'blacklist rtl8192cu', proofread, save and close gedit. Check for any other ndiswrapper files:

ls /etc/modprobe.d

If you find any, sudo rm them.

Reboot and let's try troubleshooting again:

dmesg | grep -e rtl -e wlan

[gower]

Everything here looks entirely normal. Check for any other ndiswrapper files:

ls /etc/modprobe.d

If you find any, sudo rm them.

I found ndiswrapper.conf and removed it.

Reboot and let's try troubleshooting again:

dmesg | grep -e rtl -e wlan

With no device plugged in I've got empty output.

After plugging in N13 there was no crash, but I still can't connect to the network. Output of dmesg was:

[  122.951165] rtl8192cu: MAC address: c8:60:00:d3:b0:f8
[  122.951170] rtl8192cu: Board Type 0
[  122.976165] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[  122.996838] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[  122.997630] usbcore: registered new interface driver rtl8192cu
[  123.052468] udevd[600]: renamed network interface wlan0 to wlan1
[  123.056786] rtl8192cu: MAC auto ON okay!
[  123.093923] rtl8192cu: Tx queue select: 0x05
[  123.094563] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin
[  123.490563] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[  123.491313] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[  146.260547] wlan1: direct probe to 00:1e:37:10:1b:60 (try 1/3)
[  146.260561] wlan1: direct probe responded
[  146.272059] wlan1: authenticate with 00:1e:37:10:1b:60 (try 1)
[  146.279058] wlan1: authenticated
[  146.301297] wlan1: associate with 00:1e:37:10:1b:60 (try 1)
[  146.309435] wlan1: RX AssocResp from 00:1e:37:10:1b:60 (capab=0x411 status=0 aid=4)
[  146.309438] wlan1: associated
[  146.310676] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[  156.856014] wlan1: no IPv6 routers present
[  192.204687] wlan1: deauthenticating from 00:1e:37:10:1b:60 by local choice (reason=3)