https://bugzilla.novell.com/show_bug.cgi?id=812592 https://bugzilla.novell.com/show_bug.cgi?id=812592#c26 --- Comment #26 from Robin Klitscher <robnk@xtra.co.nz> 2013-07-27 21:06:35 UTC --- (In reply to comment #25) Before we go any further, some new information. On the vague chance that the problem might have something to do with wake-on-LAN, I'd previously tried disabling WOL at the level of the onboard NIC (Intel I217V Gigabit ethernet controller). It made no difference - poweroff still resulted in reboot. But there is a second switch in the BIOS called "Wake on LAN from S4/S5". In light of the above implication that WOL was not the source of the problem, I hadn't tried disabling this item as well. When I did so it worked the magic - I get a clean shutdown to poweroff. To recap: enabling or disabling WOL at the level of the NIC makes no difference to the errant shutdown behaviour. But disabling "Wake on LAN from S4/S5" at the level of the BIOS does normalise that behaviour. All of which might suggest that the problem lies in the motherboard or its firmware. But that's not the whole story because the system powers off properly under some operating systems but not others. And so, very much in lay terms it seems that: 1. opensSUSE 12.3 generates some kind of WOL signal that is sensitive to a main BIOS setting but not to WOL settings in the NIC itself. This also applies to Clonezilla's Debian-based implementation. 2. Both Win 7 and Parted Magic's Slackware shut down properly irrespective of the WOL settings at either the mainboard level or the NIC. And so, under my preferred system oS 12.3 I can have WOL working or poweroff working, but not both. It's not a showstopper by any means, but if possible I'd really like to have both of these things working properly. Thank you for your consideration ...... -- 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.