Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I'm running Ubuntu 12.04 LTS on my Asus U56E. This problem appeared after an update about 2 weeks ago. After a random amount of time, sometimes 5 minutes and sometimes a few hours, my wireless connection drops. The network-manager will show networks, but I'm not able to connect to them anymore.

After running sudo service network-manager restart, I see no networks in the network-manager, and it tells me: "device not ready."

If I put my computer to sleep and resume, it brings back my desktop, but everything is locked (keyboard and trackpad).

The only way I've found to reconnect is through a restart.

(Tentative idea: This may be caused in close proximity to plugging in and/or removing the power cord. That seems ridiculous, and it hasn't happened enough times to confirm it.)

This Asus U56E has some weird, well-documented quirks, but I've already added the following lines to /etc/modprobe.d/iwl.conf:

options iwlagn bt_coex_active=0
options iwlagn 11n_disable=1

Below, I will give some interesting data. I'll provide my printouts before AND after the crash. I'll also paste the printouts of an identical computer that has not been updated and works great.

Problem computer when working

$ lspci | grep -i wireless
02:00.0 Network controller: Intel Corporation Centrino Wireless-N + WiMAX 6150 (rev 67)

$ sudo ifconfig
eth0      Link encap:Ethernet  HWaddr c8:60:00:38:b3:25  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:54 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:282 errors:0 dropped:0 overruns:0 frame:0
          TX packets:282 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:24038 (24.0 KB)  TX bytes:24038 (24.0 KB)

wlan2     Link encap:Ethernet  HWaddr 40:25:c2:c0:11:34  
          inet addr:192.168.0.100  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::4225:c2ff:fec0:1134/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:672 errors:0 dropped:0 overruns:0 frame:0
          TX packets:704 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:421616 (421.6 KB)  TX bytes:181599 (181.5 KB)

wmx0      Link encap:Ethernet  HWaddr 64:d4:da:6c:0d:84  
          UP NOARP  MTU:1400  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:20 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Alternate working computer (same model) without update

$ lspci | grep -i wireless
02:00.0 Network controller: Intel Corporation Centrino Wireless-N + WiMAX 6150 (rev 67)

$ sudo ifconfig
lo        no wireless extensions.

wlan1     IEEE 802.11bgn  ESSID:"HampNet2"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: 14:35:8B:07:38:F8   
          Bit Rate=150 Mb/s   Tx-Power=15 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=44/70  Signal level=-66 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:12979  Invalid misc:82   Missed beacon:0

wmx0      no wireless extensions.

eth0      no wireless extensions.

Problem computer after wireless crashes

$ sudo ifconfig
eth0      Link encap:Ethernet  HWaddr c8:60:00:38:b3:25  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:54 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1488 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1488 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:119803 (119.8 KB)  TX bytes:119803 (119.8 KB)

wmx0      Link encap:Ethernet  HWaddr 64:d4:da:6c:0d:84  
          UP NOARP  MTU:1400  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:20 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

$ sudo ifconfig wlan2 up
SIOCSIFFLAGS: Connection timed out

$ rfkill list
0: i2400m-usb:1-1.1:1.0: WiMAX
    Soft blocked: yes
    Hard blocked: no
1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
2: asus-wlan: Wireless LAN
    Soft blocked: no
    Hard blocked: no
3: asus-wimax: WiMAX
    Soft blocked: yes
    Hard blocked: no

$ rfkill unblock all
$ rfkill list
0: i2400m-usb:1-1.1:1.0: WiMAX
    Soft blocked: yes
    Hard blocked: no
1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
2: asus-wlan: Wireless LAN
    Soft blocked: no
    Hard blocked: no
3: asus-wimax: WiMAX
    Soft blocked: no
    Hard blocked: no

Still nothing. Even after restarting network-manager again.

share|improve this question
    
I'm not sure if this will help, but does running "sudo rfkill unblock all" help matters any? –  UncleNerdicus Jun 20 '13 at 4:47
    
I did confirm that it happens when I change my power state. Strangely, when I restarted just now, empathy crashed on me and my wireless had a tough time connecting. So I removed empathy and toggled my wireless on and off a few times and now everything is fine. I don't know what the "real issue" is, but I'm happy to be able to move about my house again after 2 weeks... –  algebralives Jun 20 '13 at 22:56
    
That's an odd one.. But hey, whatever works :) –  UncleNerdicus Jun 21 '13 at 4:10
    
Nope. It's back again. I don't believe in random crashes. I'm trying everything to narrow it down, but it really appears random. Sometimes it's 1 minute. Sometimes it's 1 hour. But it always crashes. –  algebralives Jun 21 '13 at 20:52
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.