https://bugzilla.novell.com/show_bug.cgi?id=396174 User mglenn@cco.state.oh.us added comment https://bugzilla.novell.com/show_bug.cgi?id=396174#c6 Michael Glenn <mglenn@cco.state.oh.us> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|mglenn@cco.state.oh.us | --- Comment #6 from Michael Glenn <mglenn@cco.state.oh.us> 2008-06-03 20:06:48 MDT --- Okay; one thing I came across was that NetControl and NetworkManager were both trying to manage the same NICs. Easy to do; just assume you already know how SuSE networking works and don't bother to RTFM. Perhaps we need some sort of contention checking here? Anyway, after cleaning things up and letting NetworkManager run the whole show, the suspend problem persisted, drat it. :( (In reply to comment #4 from Stefan Seyfried) . . .
1) after resuming, try connecting manually via the nm-applet menu. Does this help?
Tried it w/both NICs. On the wired NIC, the little applet icon swirled for awhile (both dots green); a mouse-over pops "Requesting a network address from the wired network....". It finally timed out w/no connection. An interesting thing: when I elect to edit the Network Connections list, the wired list contains "Auto eth1" with "never" next to it. The wireless link on the other hand, has a time next to it. With the WLAN NIC, The connection menu shows a measurable power level. On selection, the icon goes round and round as well (lower dot green, upper dot gray). A mouse-over pops "Attempting to join the wireless network 'bla-bla'". After a while, a dialog called "Secrets required by the wireless network" pops up. All the settings and the key are correct, but hitting connect just repeats the above.
2) after suspending, do "rcnetwork restart". Does this already help to bring network back?
Nope; same results as above, after NetworkManager came back up, except for a very strange Wireless Network Secrets dialog popped up instead of the normal wireless dialog. I'll attach a screenshot. The drop-down menu, btw, is null.
3) before suspend, do "rmmod e100", then suspend / resume, then do "modprobe e100". If network is not back, try "rcnetwork restart" after that.
No-go. Same symptoms. Something I then tried: I brought up the nm-applet's Network Connections list and deleted EVERYTHING, then rebooted. When I got the desktop back, I checked the Network Connections list: "Auto eth1 . . . . never" was back in it, though the wireless stayed gone. Selecting Edit on Auto eth1 shows a MAC address in the address field (it didn't have one before), and MTU now says "automatic" instead of being blank. Selecting Auto eth1 from the connection menu re-does the LAN connection, but that "never" never goes away(???). Doing a Suspend to RAM test results in a SUCCESSFUL reconnection, and ifconfig shows a valid DHCP-generated IP address. Pinging the router succeeds. Next, I opened the nm-applet and selected the local WLAN. The icon swirled for a bit (both balls green) then went back to normal; no status message. Network Connections - Wireless now shows a "Auto bla-bla . . . . now" entry, and ifconfig shows an IP address for eth0, which is interesting: where the heck did it get the WEP key? Doing a Suspend to RAM test results in BOTH NICS FAILING in the exact same way as described for #1. Just to see what would happen, with the NICs still down I then did rmmod airo: The command line *hung*. A warm reboot also hung, just after the Random Seed generation message, so I had to power-cycle the test machine to get it back. After the cold boot both NICs were back. I re-tried #3, this time testing the airo driver (the command line didn't hang on rmmod this time). Before doing the modprobe I did an ifconfig: eth1 (wired) is up. modprobe airo ran successfully, and about twenty seconds later I received a network-up message. ifconfig confirms both NICs up, ping is good. Something tells me that poor little airo is violently allergic to Suspend. :\ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.