Wlan doesn't reenable itself after hibernate. Drive seems to be loaded
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I have a weird problem with the wlan on my laptop.
When i put the laptop into hibernate and later start it again,
the wlan is disabled. However the driver is loaded.
It seems that only a setting is changed somewhehre and i can't seem to find the origin.
Also the wlan can easily be reenabled by going to the network manager in the taskbar and it connets flawlessly.
I get this output when i use nmcli general (after resuming from hibernate):
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN
connected (local only) full enabled disabled enabled enabled
Hardware:
Dell Inspiron 5559
Intel Wireless 3160
Kernel and driver:
4.5.2-040502-generic
iwlwifi
OS:
- Linux Mint 18 Sarah 64-bit
linux-mint hibernate wlan iwlwifi
asked Oct 9 '17 at 11:14
PurifyPioneer
83
add a comment |Â
up vote
0
down vote
favorite
I have a weird problem with the wlan on my laptop.
When i put the laptop into hibernate and later start it again,
the wlan is disabled. However the driver is loaded.
It seems that only a setting is changed somewhehre and i can't seem to find the origin.
Also the wlan can easily be reenabled by going to the network manager in the taskbar and it connets flawlessly.
I get this output when i use nmcli general (after resuming from hibernate):
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN
connected (local only) full enabled disabled enabled enabled
Hardware:
Dell Inspiron 5559
Intel Wireless 3160
Kernel and driver:
4.5.2-040502-generic
iwlwifi
OS:
- Linux Mint 18 Sarah 64-bit
linux-mint hibernate wlan iwlwifi
asked Oct 9 '17 at 11:14
PurifyPioneer
83
Has the interface got an "auto" next to the interface name in /etc/network/inferfaces?
– Raman Sailopal
Oct 9 '17 at 11:32
Can you check the state of the rfkill locks? (Runrfkill listas root.) (Perhaps that's the enabled/disabled in the output ofnmcli, I don't know networkmanager.) In my experience, linux (the kernel), at least with some laptops, will reset the wireless "software lock" state back to "locked" (that is, no connectivity allowed) after resuming from hibernation.
– njsg
Oct 9 '17 at 11:34
@RamanSailopal The output of 'cat /etc/network/interfaces' is '# interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback' So it doesn't look like it's related to the wifi driver ? The output of 'sudo rfkill list' is 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no
– PurifyPioneer
Oct 9 '17 at 17:58
@njsg Output of rfkil llist is above. I just used the term "networkmanager" to describe the icon in the taskbar where you can visually manage your connections. 'nmcli' is the installed network manager as far as i know. How would i go about changing this kernel behaviour ?
– PurifyPioneer
Oct 9 '17 at 18:07
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a weird problem with the wlan on my laptop.
When i put the laptop into hibernate and later start it again,
the wlan is disabled. However the driver is loaded.
It seems that only a setting is changed somewhehre and i can't seem to find the origin.
Also the wlan can easily be reenabled by going to the network manager in the taskbar and it connets flawlessly.
I get this output when i use nmcli general (after resuming from hibernate):
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN
connected (local only) full enabled disabled enabled enabled
Hardware:
Dell Inspiron 5559
Intel Wireless 3160
Kernel and driver:
4.5.2-040502-generic
iwlwifi
OS:
- Linux Mint 18 Sarah 64-bit
linux-mint hibernate wlan iwlwifi
asked Oct 9 '17 at 11:14
PurifyPioneer
83
I have a weird problem with the wlan on my laptop.
When i put the laptop into hibernate and later start it again,
the wlan is disabled. However the driver is loaded.
It seems that only a setting is changed somewhehre and i can't seem to find the origin.
Also the wlan can easily be reenabled by going to the network manager in the taskbar and it connets flawlessly.
I get this output when i use nmcli general (after resuming from hibernate):
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN
connected (local only) full enabled disabled enabled enabled
Hardware:
Dell Inspiron 5559
Intel Wireless 3160
Kernel and driver:
4.5.2-040502-generic
iwlwifi
OS:
- Linux Mint 18 Sarah 64-bit
linux-mint hibernate wlan iwlwifi
linux-mint hibernate wlan iwlwifi
asked Oct 9 '17 at 11:14
PurifyPioneer
83
asked Oct 9 '17 at 11:14
PurifyPioneer
83
asked Oct 9 '17 at 11:14
PurifyPioneer
83
asked Oct 9 '17 at 11:14
PurifyPioneer
83
asked Oct 9 '17 at 11:14
PurifyPioneer
83
83
Has the interface got an "auto" next to the interface name in /etc/network/inferfaces?
– Raman Sailopal
Oct 9 '17 at 11:32
Can you check the state of the rfkill locks? (Runrfkill listas root.) (Perhaps that's the enabled/disabled in the output ofnmcli, I don't know networkmanager.) In my experience, linux (the kernel), at least with some laptops, will reset the wireless "software lock" state back to "locked" (that is, no connectivity allowed) after resuming from hibernation.
– njsg
Oct 9 '17 at 11:34
@RamanSailopal The output of 'cat /etc/network/interfaces' is '# interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback' So it doesn't look like it's related to the wifi driver ? The output of 'sudo rfkill list' is 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no
– PurifyPioneer
Oct 9 '17 at 17:58
@njsg Output of rfkil llist is above. I just used the term "networkmanager" to describe the icon in the taskbar where you can visually manage your connections. 'nmcli' is the installed network manager as far as i know. How would i go about changing this kernel behaviour ?
– PurifyPioneer
Oct 9 '17 at 18:07
add a comment |Â
Has the interface got an "auto" next to the interface name in /etc/network/inferfaces?
– Raman Sailopal
Oct 9 '17 at 11:32
Can you check the state of the rfkill locks? (Runrfkill listas root.) (Perhaps that's the enabled/disabled in the output ofnmcli, I don't know networkmanager.) In my experience, linux (the kernel), at least with some laptops, will reset the wireless "software lock" state back to "locked" (that is, no connectivity allowed) after resuming from hibernation.
– njsg
Oct 9 '17 at 11:34
@RamanSailopal The output of 'cat /etc/network/interfaces' is '# interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback' So it doesn't look like it's related to the wifi driver ? The output of 'sudo rfkill list' is 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no
– PurifyPioneer
Oct 9 '17 at 17:58
@njsg Output of rfkil llist is above. I just used the term "networkmanager" to describe the icon in the taskbar where you can visually manage your connections. 'nmcli' is the installed network manager as far as i know. How would i go about changing this kernel behaviour ?
– PurifyPioneer
Oct 9 '17 at 18:07
Has the interface got an "auto" next to the interface name in /etc/network/inferfaces?
– Raman Sailopal
Oct 9 '17 at 11:32
Has the interface got an "auto" next to the interface name in /etc/network/inferfaces?
– Raman Sailopal
Oct 9 '17 at 11:32
Can you check the state of the rfkill locks? (Run
rfkill list as root.) (Perhaps that's the enabled/disabled in the output of nmcli, I don't know networkmanager.) In my experience, linux (the kernel), at least with some laptops, will reset the wireless "software lock" state back to "locked" (that is, no connectivity allowed) after resuming from hibernation.– njsg
Oct 9 '17 at 11:34
Can you check the state of the rfkill locks? (Run
rfkill list as root.) (Perhaps that's the enabled/disabled in the output of nmcli, I don't know networkmanager.) In my experience, linux (the kernel), at least with some laptops, will reset the wireless "software lock" state back to "locked" (that is, no connectivity allowed) after resuming from hibernation.– njsg
Oct 9 '17 at 11:34
@RamanSailopal The output of 'cat /etc/network/interfaces' is '# interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback' So it doesn't look like it's related to the wifi driver ? The output of 'sudo rfkill list' is 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no
– PurifyPioneer
Oct 9 '17 at 17:58
@RamanSailopal The output of 'cat /etc/network/interfaces' is '# interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback' So it doesn't look like it's related to the wifi driver ? The output of 'sudo rfkill list' is 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no
– PurifyPioneer
Oct 9 '17 at 17:58
@njsg Output of rfkil llist is above. I just used the term "networkmanager" to describe the icon in the taskbar where you can visually manage your connections. 'nmcli' is the installed network manager as far as i know. How would i go about changing this kernel behaviour ?
– PurifyPioneer
Oct 9 '17 at 18:07
@njsg Output of rfkil llist is above. I just used the term "networkmanager" to describe the icon in the taskbar where you can visually manage your connections. 'nmcli' is the installed network manager as far as i know. How would i go about changing this kernel behaviour ?
– PurifyPioneer
Oct 9 '17 at 18:07
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f396988%2fwlan-doesnt-reenable-itself-after-hibernate-drive-seems-to-be-loaded%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Has the interface got an "auto" next to the interface name in /etc/network/inferfaces?
– Raman Sailopal
Oct 9 '17 at 11:32
Can you check the state of the rfkill locks? (Run
rfkill listas root.) (Perhaps that's the enabled/disabled in the output ofnmcli, I don't know networkmanager.) In my experience, linux (the kernel), at least with some laptops, will reset the wireless "software lock" state back to "locked" (that is, no connectivity allowed) after resuming from hibernation.– njsg
Oct 9 '17 at 11:34
@RamanSailopal The output of 'cat /etc/network/interfaces' is '# interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback' So it doesn't look like it's related to the wifi driver ? The output of 'sudo rfkill list' is 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no
– PurifyPioneer
Oct 9 '17 at 17:58
@njsg Output of rfkil llist is above. I just used the term "networkmanager" to describe the icon in the taskbar where you can visually manage your connections. 'nmcli' is the installed network manager as far as i know. How would i go about changing this kernel behaviour ?
– PurifyPioneer
Oct 9 '17 at 18:07