On Fri, Apr 27, 2007 at 03:06:37PM +0200, Michael Biebl wrote: >> I'm not sure how you can think that when it works if NM doesn't know about >> the wakeup... > Because NM works perfectly with other drivers and it does not anything > special for ipw3945. Googling for ipw3945 reveils many hits with people > having problems with ipw3945 for suspend/resume.
Well, once again, why does network-manager work fine if I _don't_ tell it (via dbus) that a resume has happened? Also, why does it work fine if I don't use network-manager, just regular iwconfig? There is some sort of resetting that goes on at resume time in n-m that messes up the state -- it might be triggered by something in the driver, but in that case I'd appreciate if you could be more specific than just blaming it on ipw3945 :-) In any case, I get exactly the same problems with wired Ethernet (tg3); suspend/resume while connected, and n-m goes into vegetative state. Suspend too short (so the dbus signal doesn't arrive) and the problem never surfaces; restart n-m and it comes up again just fine. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
