https://bugzilla.novell.com/show_bug.cgi?id=387736 User skunze@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387736#c2 --- Comment #2 from Stefan Kunze 2008-05-07 07:38:24 MST --- ETHTOOL_Options is set to yes. -- 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=387736 User hvogel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387736#c5 Hendrik Vogelsang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #5 from Hendrik Vogelsang 2008-05-08 06:19:37 MST --- The ethtool wol setting is just good for the next wakeup. This is by design. -- 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=387736 User fmarmond@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387736#c7 --- Comment #7 from Frederic Marmond 2008-07-15 16:18:43 MDT --- maybe this bug report is too specific and one should fill a new bug 'feature request'? The aim of ethtool is NOT to be persistent (like ifconfig), so that's NOT a bug that the config is lost on the next reboot. Should we ask for feature in Yast-Network for that option? I still think it will be a valuable one. As I'm not (yet) used to suse bugzilla, it's just an opened question for now... :) -- 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=387736 User fmarmond@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387736#c9 Frederic Marmond changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|fmarmond@gmail.com | --- Comment #9 from Frederic Marmond 2008-07-21 09:30:31 MDT --- I think something in yast would be a good thing, as power management is widely used now, even by people that don't know how to modify their config files by hand. We already provide easy ways of suspending system, we must do the same for waking them :) Yast may enable the network to wake up the system at the same time (echo MAC>/proc/acpi/wakeup if MAC was disabled, the same, it's not persistent). We may have the choice between all ways of waking up the system with WOL: (man ethtool): wol p|u|m|b|a|g|s|d... Sets Wake-on-LAN options. Not all devices support this. The argument to this option is a string of characters specifying which options to enable. p Wake on phy activity u Wake on unicast messages m Wake on multicast messages b Wake on broadcast messages a Wake on ARP g Wake on MagicPacket(tm) s Enable SecureOn(tm) password for MagicPacket(tm) d Disable (wake on nothing). This option clears all previous options. Yast may show all those options, disabling those that are not available from the driver. If at less one is activated (but 'd'), we must as well play with /proc/acpi/wakeup to enable network in 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=387736 User fmarmond@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387736#c11 --- Comment #11 from Frederic Marmond 2008-07-22 02:25:31 MDT --- maybe we could add a section in yast, about powermanagement, to set disk idle time-out, cpu freq policies, swap usage, ... as well as ways of waking up the system (this discussion on WOL, but also timer, keyboard/mouse, like /proc/acpi/wakeup things) -- 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=387736 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387736#c13 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #13 from Thomas Renninger 2008-07-22 07:16:30 MDT --- I haven't read the whole bug in detail, only the description...:

I tried to set the wake on LAN Parametyers in 11.0 Beta 2 with ethtool. This is a feature which should work and come in through 2.6.27 kernel. This one will come in into SUSE through 11.1 soon. I cannot promise in which Alpha release this will happen (as soon as 2.6.27-rcX appears there). Early testing is very much appreciated as this is very young code and there is a lot HW specific things which might need HW specific fixups. There the ACPI parts and pci parts are glued together and ethtool should be the only tool which is needed to get things working.

I would close this one as Won't fix for 11.0 (->doing so). You may want to reopen or better open new bugs if ethtool does not arm your: - network card - pci parts - ACPI parts alltogether and WoL does not work then in 11.1 with 2.6.27-rcX kernel. About having WoL option be set persistent: This sounds like a kernel bug. Once set, the option should survive a suspend (IMO). But retrying 2.6.27 is worth it. Things changed there, maybe this bit is persistent then. ETHTOOL_OPTIONS='wol bg' sounds like a workaround. -- 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.