upgrade to 13.10 after you suspend, network is disabled and cant be enabled

[sdowney717]

It requires a reboot.
This is an onboard e1000 network chip

[coffeecat]

13.10 is no longer in development and has been released now.

Thread moved to Installation & Upgrades.

[sdowney717]

It requires a reboot.
This is an onboard e1000 network chip
any ideas?

I have the x1300 AMD video card
After it wakes up, you see the empty network triangle and click on it says network disabled.
And the leds are off.
IF you tell it to enable, the LEDs light up but the empty triangle remains. And no network.

[sdowney717]

I solved following this advice
http://askubuntu.com/questions/26685...ter-suspension

Here is a technique that sometimes works:

gksudo gedit /etc/pm/config.d/config
Add a single line:

SUSPEND_MODULES="e100"
Proofread, save and close gedit. Reboot, suspend and let us have your report.

for me the driver is e100.
You find the driver by sudo lshw -C network

the line driver = 'the driver', the driver is what you use in that line

SUSPEND_MODULES="the driver"

[sdowney717]

Not solved.
This seems to work if you do a suspend and then within a couple minutes awake the PC.
I just left it sit suspended for an hour and when it awakens, the network is disabled.

[castor_fou]

Same issue here.

I can however resume network with : sudo nmcli nm sleep false

[sdowney717]

Thanks for this. That does work.
I ran it and I got a message that says network now offline.

Then you click the icon and you see all the network cards
Then tell it to enable networking, selecting 'Auto Ethernet'
And it comes back working.

SO, how can we make this work like it should?
Anyone submitted a bug yet?

I changed the line to read
SUSPEND_MODULES="e100 e1000" in that config file, but it has no effect.
This MB has 2 NICS onboard builtin.

[sdowney717]

I started a bug report so if you wish to join and contribute some input there.
https://bugs.launchpad.net/ubuntu/+s...r/+bug/1242679

[phaenze]

I have this bug as well. I found the work-around* here and here. The basic steps are:

sudo touch /etc/pm/sleep.d/wakenet.sh

sudo chmod +x /etc/pm/sleep.d/wakenet.sh

sudo gedit /etc/pm/sleep.d/wakenet.sh

Insert the following lines:

#!/bin/bash
case "$1" in
thaw|resume)
nmcli nm sleep false
;;
*)
;;
esac
exit $?

Save

Now the interface is started upon resume. It seems to suspend/resume slower, but it works.

Peace,
Paul

*This is not the solution (as I originally wrote) but a work-around. The solution is for the bug to be fixed. Visit this page and click if it's affecting you. Thanks.

[yefymenko]

I have this bug as well. I found the work-around* here and here. The basic steps are:


Now the interface is started upon resume. It seems to suspend/resume slower, but it works.

Peace,
Paul

*This is not the solution (as I originally wrote) but a work-around. The solution is for the bug to be fixed. Visit this page and click if it's affecting you. Thanks.

This worked perfectly for me. Ubuntu 13.10, driver=iwlwifi,

Hardware:
description: Wireless interface
product: PRO/Wireless 5100 AGN [Shiloh] Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: 00
serial: 00:21:5d:90:dd:44
width: 64 bits
clock: 33MHz


Thanks.