On Fri, Apr 27, 2007 at 05:42:42PM +0200, Michael Biebl wrote: > What happens if you leave out the hal-system-power-sleep-linux call and > simply put NM into sleep and wake it up again?
Then it works. > What happens if you unload/load the ipw3945 module in between? Still works. > I don't own a ipw3945, so unfortunately I can't really debug this any > further. My guess is that the ipw3954 driver is not immediately ready > after suspend/resume. That sounds like a reasonable guess. However, should that make n-m give up and die? > As a workaround, you can tell g-p-m to not notify NetworkManager. > Edit the gconf key (via gconf-editor) > /apps/gnome-power-manager/networkmanager_sleep and set it to false. OK, I could try that, but I guess that will give me other issues wrt. ESSID scanning? > As there is a working workaround and it seems to be a ipw3954 specific > problem, I'm setting the severity to minor. It's not ipw3945 specific. Like I wrote in my previous mail, it also affects my tg3 card. Also, a friend reports exactly the same issue on a ThinkPad X40, with ipw2200. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
