You are not logged in.
Pages: 1
Greetings,
Network is unreachable after I resume the laptop from sleep (open the lid).
It used to work flawlessly for a lot of time. I *think* the issue started after upgrading to Gnome 3.20.
I tried "systemctl restart NetworkManager", "systemctl restart dhcpcd" and "netctl restart wlp2s0-tebeka" - all of them didn't work.
The only solution right now is a reboot.
Any ideas?
Thanks,
--
Miki
Offline
What type of net connection is the one that is failing? Ethernet/Wireless?
As you appear to use Network manager to handle your connection (though you too mention netctl which is a bit confusing), checking the status of the related service file would be a good idea instead of "blindly" restarting it.
A wild guess on my behalf would be that you simply do not have your network set up correctly in order to resume when waking up.
As an example, in my case I had to set up a resume service for both, suspend and hibernate. As I do mostly the latter, if I had not I have to restart the wireless network service (i use netctl-auto with two profiles - ethernet and wireless) manually each time as it would only "resume" after a reboot.
Anyway, a good starting point would be to explain how you have configured your network (f.e. which tool you actually use to handle it) and from that on it would be easier to troubleshoot your problem.
\(o_X)/
'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols
Offline
It's a wireless connection.
I really don't remember how I configured the network, it was a while back. IIRC I followed the beginners guide.
Is there a way for me to determine the current network configuration?
Thanks.
Offline
systemctl list-unit-files | grep enabled
EDIT: how do you remember your user-id?
Last edited by Docbroke (2016-04-15 05:33:51)
Arch is home!
https://github.com/Docbroke
Offline
org.cups.cupsd.path enabled
autovt@.service enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
display-manager.service enabled
docker.service enabled
gdm.service enabled
getty@.service enabled
NetworkManager-dispatcher.service enabled
NetworkManager.service enabled
ntpd.service enabled
org.cups.cupsd.service enabled
systemd-timesyncd.service enabled
org.cups.cupsd.socket enabled
remote-fs.target enabled
I don't remember my user-id, Chrome does
Offline
Does anyone have an idea?
Offline
Please don't bump providing new information https://wiki.archlinux.org/index.php/Fo … te#Bumping
Thanks.
Does the network even exist after it powers back up? What are the output of
ip link
ip addr
and
iwconfig
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Sorry for the bump, will try to follow the etiquette from now on.
I did play with removing and reloading iwlwifi but it didn't work.
Here's the output from the commands before and after sleep.
Before sleep (with network)
$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
link/ether 00:24:d7:57:3a:38 brd ff:ff:ff:ff:ff:ff
3: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 5c:26:0a:65:f1:a8 brd ff:ff:ff:ff:ff:ff
4: br-93a535cda897: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:42:83:d3:cc:b9 brd ff:ff:ff:ff:ff:ff
5: br-83bc1cb5c1fd: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:42:a9:62:fe:68 brd ff:ff:ff:ff:ff:ff
6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:42:da:18:f0:e2 brd ff:ff:ff:ff:ff:ff
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:24:d7:57:3a:38 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.9/24 brd 10.0.0.255 scope global dynamic wlp2s0
valid_lft 3510sec preferred_lft 3510sec
inet6 fe80::224:d7ff:fe57:3a38/64 scope link
valid_lft forever preferred_lft forever
3: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 5c:26:0a:65:f1:a8 brd ff:ff:ff:ff:ff:ff
4: br-93a535cda897: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:83:d3:cc:b9 brd ff:ff:ff:ff:ff:ff
inet 172.18.0.1/16 scope global br-93a535cda897
valid_lft forever preferred_lft forever
5: br-83bc1cb5c1fd: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:a9:62:fe:68 brd ff:ff:ff:ff:ff:ff
inet 172.19.0.1/16 scope global br-83bc1cb5c1fd
valid_lft forever preferred_lft forever
6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:da:18:f0:e2 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 scope global docker0
valid_lft forever preferred_lft forever
$ iwconfig
wlp2s0 IEEE 802.11abgn ESSID:"tebeka"
Mode:Managed Frequency:2.412 GHz Access Point: E8:FC:AF:98:F4:A1
Bit Rate=144.4 Mb/s Tx-Power=15 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=65/70 Signal level=-45 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:5 Invalid misc:389 Missed beacon:0
After sleep (no network)
ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
link/ether 00:24:d7:57:3a:38 brd ff:ff:ff:ff:ff:ff
3: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 5c:26:0a:65:f1:a8 brd ff:ff:ff:ff:ff:ff
4: br-93a535cda897: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:42:83:d3:cc:b9 brd ff:ff:ff:ff:ff:ff
5: br-83bc1cb5c1fd: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:42:a9:62:fe:68 brd ff:ff:ff:ff:ff:ff
6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:42:da:18:f0:e2 brd ff:ff:ff:ff:ff:ff
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:24:d7:57:3a:38 brd ff:ff:ff:ff:ff:ff
inet6 fe80::224:d7ff:fe57:3a38/64 scope link
valid_lft forever preferred_lft forever
3: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 5c:26:0a:65:f1:a8 brd ff:ff:ff:ff:ff:ff
4: br-93a535cda897: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:83:d3:cc:b9 brd ff:ff:ff:ff:ff:ff
inet 172.18.0.1/16 scope global br-93a535cda897
valid_lft forever preferred_lft forever
5: br-83bc1cb5c1fd: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:a9:62:fe:68 brd ff:ff:ff:ff:ff:ff
inet 172.19.0.1/16 scope global br-83bc1cb5c1fd
valid_lft forever preferred_lft forever
6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:da:18:f0:e2 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 scope global docker0
valid_lft forever preferred_lft forever
$ iwconfig
wlp2s0 IEEE 802.11abgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Offline
I tried "systemctl restart NetworkManager", "systemctl restart dhcpcd" and "netctl restart wlp2s0-tebeka" - all of them didn't work
https://bbs.archlinux.org/viewtopic.php?id=57855
It looks like NetworkManager has dropped the connection completely.
Is there anything in the logs?
https://wiki.archlinux.org/index.php/Systemd#Journal
Offline
I've pasted output of journal and dmesg in https://gist.github.com/tebeka/a83602d4 … da177201e5. This looks problematic, but I don't know how to solve it:
[ 1.997185] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-6000-6.ucode failed with error -2
[ 1.997224] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-6000-5.ucode failed with error -2
I'm pretty sure now that the problem is with NetworkManager. I've disabled it sudo systemctl stop NetworkManager and then started netctl sudo netctl start wlp2s0-tebeka and now I have network.
Offline
It's NetworkManager. Computer back from sleep with netcl and network works.
Offline
This looks problematic, but I don't know how to solve it:
[ 1.997185] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-6000-6.ucode failed with error -2 [ 1.997224] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-6000-5.ucode failed with error -2
Those are normal messages, if you look further down you will see that later attempts to load firmware to that device were successful.
Offline
This seems to be fixed for me with NetworkManager 1.2.0-3
Offline
Pages: 1