after sleep networking doesn't work

To be more clear on a couple things:

Hibernate works perfectly, everything works fine.

Sleep works perfectly on everything, except neither wired nor wireless networking works on resume. This happened both using network-manager, and before that using basic gnome networking tools.

When I try a sudo ifup eth0 (wireless), or sudo ifup eth1 (wired) it simply reports "Ignoring unknown interface eth0=eth0"

This is all using a fully updated Dapper, with the 2.6.15-19 kernel.

Please save dmesg after the resume and attach (not paste) it to this bug report.

This sounds more like an acpi issue of not reloading drivers, but I want to be sure.

Here a dmesg after resuming, I think the sleep part only starts around line 418.

I can confirm this behavior on my HP Compaq NC6120 laptop with ipw2200 wifi.

After resume from sleep I must right-clcik on the network manager icon, uncheck enable networking, right click again and re-check the enable networking item. The NM comes back to life. Networking works afterwards.

It seems that either NM doesn't detect a wake from acpi sleep or IPW2000 driver is not getting reloaded.

I can confirm this on HP nc4200 with ipw2200. On awaken the same error. I cannot fix using the uncheck-enable check-enable trick and must manually find the pid for NetworkManager then kill it with a -9 to get it to start again.

The ocured ONLY after update to dap 2.6.15-23-386 on 19 May

To be clear: this is a NM bug and not a networking one, On awaken, all interfaces work fine and I can manually connect. The problem is rather with NM crashing, I personally suspect on suspend.

This problem has occurred for me since before I used NetworkManager. The problem is not with NM, although it does confirm the problem. If I perform an ifconfig, it only reports info for lo, it's as if the other interfaces don't exist.

I also see this on my thinkpad x41 with ipw2200. I always have to disable and enable networking from the network-manager tray icon to get the net up again after resuming from suspend.

Let me know if you need any more information from me that can help fix this.

Could this be a dup of https://launchpad.net/distros/ubuntu/+bug/45696 ?

No, my actual hardware doesn't work after resume, with or without NetworkManager. The basic Ubuntu networking tools don't work either.

I've read several versions of this same bug, and several different symptoms. I'm on an HP nc4200 and ipw2200.

1. Suspend/Resume works perfectly.
2.On resume, NetworkManager crashes. MOST of the time
3.On resume, selecting enable/disable from the nm-applet tray is INeffective for me. I must manually kill, with a -9, NetworkManager then restart.
4. It is NOT the interface: eth1 (my wireless card) operates and can manually associate with APs either through the GUI network config utility or at the CLI with iwconfig

Well a little update, my wired network now returns from sleep, after a little dist-upgrading.

As far as my wireless network goes, ifconfig reports info on lo and eth1, eth0 is just completely absent. sudo killall -9 /usr/sbin/NetworkManager, and then starting NetworkManager again helps nothing. iwconfig reports no wireless extensions, since it only sees eth1.

Then I tried modprobing ipw2100, ieee80211, and ieee80211_crypt (or something like that) and that also didn't help. So I had to restart again.

I repeat, this is NOT a NetworkManager bug report! This has to do with my hardware not coming back on, with or without NetworkManager.

My machine loses all networking after resume from hibernation as well. eMachines M5312 [https://wiki.ubuntu.com/LaptopTestingTeam/EmachinesM5312]

Same problem for my machine here : IBM Thinkpad T40p with Atheros Wireless card and Intel Gigabit adapter. After resuming NM says "No network devices have been found", but wired networking still works anyway.
It also seems to bug wireless networking even after restarting the machine : NM only shows my wired adapter and doesn't seem to know about my wireless any more.

The original bug is a kernel problem with suspend. Some people talk of a network-manager bug that's solved by disabling/enabling networking. I've filed that bug:

https://launchpad.net/distros/ubuntu/+source/network-manager/+bug/57689

I upgraded to Edgy, and the problem is fixed with the new kernel or acpi-support, whatever the problem was in...

Just thought I'd let you know for people having the same problem in Dapper.

My computer with Xubuntu feisty had a problem with getting an ip-adress after waking from hibernation. I´ve solved this problem by changing /etc/default/acpi-support

Editing this file, look for the line below, where to add [networking] after that no problems anymore:

# Add services to this list to stop them before suspend and restart them in
# the resume process.
STOP_SERVICES="networking"

Hope this will work for you to,
Thomas.

[Expired for linux-source-2.6.15 (Ubuntu) because there has been no activity for 60 days.]