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#c1 --- Comment #1 from Michael Glenn 2008-05-31 15:30:51 MDT --- Created an attachment (id=219351) --> (https://bugzilla.novell.com/attachment.cgi?id=219351) Result of hwinfo --netcard -- 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.

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#c3 --- Comment #3 from Michael Glenn 2008-05-31 22:00:34 MDT --- BTW: Let me take a second to tell everyone just how impressed w/how far the networking aspects of SuSE has come to date, especially wireless on laptops. Thanks. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=396174 Michael Glenn changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #219352|application/octet-stream |text/plain mime type| | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=396174 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=396174#c4 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mglenn@cco.state.oh.us --- Comment #4 from Stefan Seyfried 2008-06-03 10:24:02 MDT --- Ok. I'd like you to try a few things, one after the other. We'll concentrate on wired network first, if we get this working, we'll proceed to wireless (or split the bug into two bugs, depending on the results). All those commands need to be run as root. Do the following: 1) after resuming, try connecting manually via the nm-applet menu. Does this help? 2) after suspending, do "rcnetwork restart". Does this already help to bring network back? 3) before suspend, do "rmmod e100", then suspend / resume, then do "modprobe e100". If network is not back, try "rcnetwork restart" after that. Another question: are we talking about suspend to RAM (called "suspend" by gnome-power-manager) or suspend to disk (called "hibernate"), or does it happen on both? This is probably either an issue with the kernel drivers or with NetworkManager, but we need to find out where the problem is before finding the one who has to fix it :) -- 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.

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 changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|mglenn@cco.state.oh.us | --- Comment #6 from Michael Glenn 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.

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#c8 --- Comment #8 from Michael Glenn 2008-06-03 20:41:29 MDT --- I think I know why eth1 in Network Connections always showed "never": I brought up Wireshark, and it informed me that all traffic was using the wireless link rather than the wired. This is a curious behavior: Since both NICs connected to the same net and therefore had the same metric, shouldn't the 100 Mbps hardwired NIC been given automatic preference over the 11 Mbps WLAN link? :| -- 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.

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#c10 --- Comment #10 from Michael Glenn 2008-06-04 10:01:39 MDT --- (In reply to comment #9 from Stefan Seyfried)

Ok, so the executive summary, as i digested it, is: "If you unload airo before suspend and reload it after resume, then both interfaces work fine." Is this correct?

This is correct.

(Everything else, the strange UI issues, preferring the slower connection, etc., are NetworkManager bugs that are not really related to suspend and which should be filed in separate bugreports to not mix everything up here.)

Yes; I realized this late yesterday. See Bug 396175: For some reason NetworkManager and NetControl were both trying to manage the same interfaces. :P -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=396174 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=396174#c12 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fseidel@novell.com, pavel@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |kernel-maintainers@forge.provo.novell.com --- Comment #12 from Stefan Seyfried 2008-06-04 10:26:53 MDT --- the screening team will not fix this bug ;-) Reassigning again. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=396174 Pavel Machek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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.

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#c14 --- Comment #14 from Michael Glenn 2008-06-10 09:49:16 MDT --- . . . Anything I can help with? -- 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.

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#c16 --- Comment #16 from Michael Glenn 2008-06-13 08:01:24 MDT --- Okay; I'll burn a copy of the boot CD and install the latest Factory image, then test again. In the meantime, I found the following on the Cisco website, documents 12157 & 8127: "The Linux driver runs on most distributions, and kernels 2.2.x and 2.4.x are supported." "Version 1.5.000 of Cisco's Linux driver currently supports versions 2.2.x and 2.4.x of the Linux kernel." Could it be airo was never tested against 2.6.x? :( BTW: In case this remains a problem after release, could you recommend a work-around; say, inserting rmmod & modprobe commands somewhere in the Suspend scripts? Thanks. Ref: http://www.cisco.com/en/US/products/hw/wireless/ps458/products_qanda_item091... http://www.cisco.com/en/US/products/hw/wireless/ps4555/products_tech_note091... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=396174 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=396174#c18 --- Comment #18 from Pavel Machek 2008-06-16 01:42:30 MDT --- #16: I find it unlikely that airo would be "never tested" in 2.6.x. If that was the case, it would probably never even compile. If unload/reload works, it should be possible to get it working with suspend, too. Can you check that prev_state in airo_pci_resume is indeed != PCI_D1? Can you try contacting breed@users.sourceforge.net for help? He's listed as airo.c author... -- 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.

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#c19 --- Comment #19 from Michael Glenn 2008-06-17 06:59:32 MDT --- (In reply to comment #18 from Pavel Machek)

.... If unload/reload works, it should be possible to get it working with suspend, too.

Well, that's certainly good to hear.

.... Can you check that prev_state in airo_pci_resume is indeed != PCI_D1?

Ummmm, I think I'll pass that question on to airo's author. :\ -- 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.

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#c21 --- Comment #21 from Michael Glenn 2008-06-30 12:58:16 MDT --- I'm beginning to think we're not going to get a response. :( -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=396174 Pavel Machek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |mglenn@cco.state.oh.us -- 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.