|
Bugzilla – Full Text Bug Listing |
| Summary: | Network doesn't work after suspend2disk on SuSE-10.2 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Jan Doo <jan_doo> |
| Component: | Network | Assignee: | E-mail List <gnome-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
No, there is already a hook that is kicking NM before / after suspend. If this does not work, it is probably a NM bug (or a driver bug, but i doubt it). Looks similar to my experience in bug 216558 oops. Sorry, screening team, i "reassigned to default owner" of component network. This looks like a network bug, not a pm-utils bug (we only include workarounds for problems we cannot fix, this problem should, however, be fixed properly). *** This bug has been marked as a duplicate of bug 216495 *** |
After a wake up from suspend2disk with the new pm-utils, the network doesn't work. I use a 02:05.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02) After resume i have to reload the "network"-service (/etc/init.d/network) I've checked this behavior on several laptops with the same network card. As a fix, a script like "/etc/pm/hooks/00network" should be added: #!/bin/bash case $1 in thaw|resume) echo "restarting network service after suspend ..." /etc/init.d/network restart ;; esac