wifi don't work after suspend

[paolo gagini]

When i take my laptop, fujitsu-siemens AMILO-Li3710, from a suspend state wifi don't work.
I need to restart it to function properly.

This is my laptop and i have ubuntu 14.04..
http://wiki.ubuntu-it.org/Hardware/Notebook/FujitsuSiemensAMILOLi3710

thx

[Yu Ning (yuningdodo)]

@paolo, could you check the output of command "nmcli nm"?

[paolo gagini (pax2you)]

sure! :)

IN ESECUZIONE STATO HARDWARE-WIFI WIFI HARDWARE-WWAN WWAN
in esecuzione collegato abilitato abilitato abilitato abilitato

[Yu Ning (yuningdodo)]

Sorry, I can't read it... Could you run the command instead?

LANG=C nmcli nm

[paolo gagini (pax2you)]

Sorry i can't change language in chinese.
This is output in english language:
RUNNING:running
STATE:asleep
WIFI-HARDWARE:enabled
WIFI:enabled
WWAN-HARDWARE:enabled
WWAN:disabled

I hope help you.
Thank you.

[Yu Ning (yuningdodo)]

paolo, thanks a lot for the translation. Then we have the same issue, on my box network manager is put into sleep during suspend, but not awaken during resuming. Although the root cause is not clear yet, you can manually execute below command as a workaround:

sudo nmcli nm sleep false

This command will manually awake network manager, so at least we don't have to restart the computer.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[paolo gagini (pax2you)]

Your command is very useful.
Thank you! :)

I have also a problem in boot sequence.
Do you have same situation?
When i boot pc i receive those messages:

waiting for network configuration

waiting up to 60 more seconds for network configuration.

After login wifi network is ready after more 60 seconds and before nmcli nm command display:
RUNNING:not running
STATE:unknown
WIFI-HARDWARE:unknown
WIFI:unknown
WWAN-HARDWARE:unknown
WWAN:unknown

[Bin Li (binli)]

I find a way to easy reproduce it.

gdbus call --system --dest org.freedesktop.login1 --object-path /org/freedesktop/login1 --method org.freedesktop.login1.Manager.HybridSleep true

[Yu Ning (yuningdodo)]

paolo, I did have encountered the issue you mentioned in comment #7, however that was on ubuntu precise (12.04), and it wasn't reproduced on 12.10 and later. Could you please report a separate LP bug for it.

For the NM asleep issue, we can put the workaround in a PM hook, so we don't have to manually invoke the command every time.

Please create a file /etc/pm/sleep.d/90_awake-network-manager with below content:
```
#!/bin/sh

case "$1" in
    resume|thaw)
        nmcli nm sleep false
        ;;
esac
```

Please also make sure it's executable:

chmod a+x /etc/pm/sleep.d/90_awake-network-manager

[paolo gagini (pax2you)]

1-Ok i reported a new bug for boot problem here:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1388097

2-I followed instruction in comment #9 but the situation now is worst.
I also deleted 90_awake-network-manager file but command:
sudo nmcli nm sleep false
dont' work and output:
Error in sleep: Already awake
command:
nmcli nm
output:
RUNNING:running
STATE:asleep
WIFI-HARDWARE:enabled
WIFI:enabled
WWAN-HARDWARE:enabled
WWAN:disabled

I cant' go online.

[Yu Ning (yuningdodo)]

thanks for the tests. how about manually sleep & awake again?

sudo nmcli nm sleep true
sudo nmcli nm sleep false

[paolo gagini (pax2you)]

I installed 14.10 os. Sorry.
Same problem.

i followed #11 comment.
Nothing change.
After suspend mode wifi don't work.

If i launch twice:
sudo nmcli nm sleep false
it respond:
Error in sleep: Already awake
but wifi don't work.

[Yu Ning (yuningdodo)]

I didn't mean to awake twice, but sleep -> awake

sudo nmcli nm sleep true
sudo nmcli nm sleep false

would you like to give it a try?

[paolo gagini (pax2you)]

Yes i did.
Nothing happened and wifi dont' work.

[Yu Ning (yuningdodo)]

hmm, I have no idea now, it looks like a race condition issue to me, however the root cause is not clear yet.

[paolo gagini (pax2you)]

Thank you very much Yu Ning.
I hope someone can solve but is not mandatory. :)

[Ara Pulido (ara)]

Marking as Invalid, as we don't have clear reproduceable steps