I am out of luck on this one...
It's been the 3rd consecutive Kubuntu release I am unable to re-establish network connectivity after a resume. It loses the IP address assigned to eth0 and I cannot re-establish it. Of course I don't understand why it loses it.
It seems to be the only thing blocking me from upgrading from 11.10 (to 13.04). I must say I suspend to RAM 6 days out of 7 so rebooting each time is a show stopper for me.
Logging out and back in does not help in any way.
When I resume, I get this
Code:
~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:21:91:21:d5:0d
inet6 addr: fe80::221:91ff:fe21:d50d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4438 errors:0 dropped:0 overruns:0 frame:0
TX packets:4273 errors:4 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4355203 (4.3 MB) TX bytes:612818 (612.8 KB)
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:65536 Metric:1
RX packets:606 errors:0 dropped:0 overruns:0 frame:0
TX packets:606 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:59902 (59.9 KB) TX bytes:59902 (59.9 KB)
But in eth0 it should show like this
Code:
eth0 Link encap:Ethernet HWaddr 00:21:91:21:d5:0d
inet addr:1.2.3.4 Bcast:1.225.255.255 Mask:255.255.0.0 (the IP address has been changed for posting)
inet6 addr: fe80::221:91ff:fe21:d50d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:235 errors:0 dropped:0 overruns:0 frame:0
TX packets:279 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:36696 (36.6 KB) TX bytes:27691 (27.6 KB)
Yes I did check pm-suspend.log, here it is!
Code:
pm-suspend.log
Mon Jun 3 16:34:17 EDT 2013: Awake.
Mon Jun 3 16:34:17 EDT 2013: Running hooks for resume
Running hook /etc/pm/sleep.d/novatel_3g_suspend resume suspend:
/etc/pm/sleep.d/novatel_3g_suspend resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend:
/usr/lib/pm-utils/sleep.d/99video: 22: /usr/lib/pm-utils/sleep.d/99video: shopt: not found
/usr/lib/pm-utils/sleep.d/99video resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend:
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led resume suspend:
/usr/lib/pm-utils/sleep.d/95led resume suspend: not applicable.
Running hook /usr/lib/pm-utils/sleep.d/95hdparm-apm resume suspend:
/usr/lib/pm-utils/sleep.d/95hdparm-apm resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95anacron resume suspend:
/usr/lib/pm-utils/sleep.d/95anacron resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock resume suspend:
/usr/lib/pm-utils/sleep.d/90clock resume suspend: not applicable.
Running hook /usr/lib/pm-utils/sleep.d/75modules resume suspend:
Reloaded unloaded modules.
/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/60_wpa_supplicant resume suspend:
/usr/lib/pm-utils/sleep.d/60_wpa_supplicant resume suspend: not executable.
Running hook /etc/pm/sleep.d/11custom resume suspend:
* Stopping fan speed regulator fancontrol
...done.
network-manager stop/waiting
network-manager start/running, process 3824
* Starting fan speed regulator fancontrol
...done.
I couldn't find the command line actions to completely stop networking and completely resume it. I could simply add it in my sleep.d script and it should do the job, but all I could find was that network-manager restart and it doesn't help.
I tried deleting
Code:
rm /var/lib/NetworkManager/NetworkManager.state
before restarting network manager but it doesn't help.
I tried deleting the 'ifstate' file and it doesn't help.
I tried deleting '/var/lib/NetworkManager/NetworkManager.state' but it doesn't help.
I tried
Code:
sudo ifconfig eth0 down
and
Code:
sudo ifconfig eth0 up
does not help at all.
It brings back eth0 at the exact point it is, which is without an IP assigned.
I am unable to get the IP assigned to the interface.
I feel this is a real show-stopper, who could accept to hibernate and resume and need to reboot all the time to get the IP assigned?
I am clueless here... any thoughts?
tnx a lot!