F16 Wake on lan not working

[carlmuck]

I'm beating my head against a small rack of computers that need to be started remotely (won't have front panel access generally) so WOL is the obvious solution. Originally the whole rack was set to be RHEL 6 (really should just have used Centos) but the workstations needed more current stuff, so Fedora was the right choice for them, servers are still RH. When all were RHEL 6.2 the entire rack could boot using WOL.

After loading F16 on the workstations they booted using WOL just fine (the first time...) but now WOL only works on them from a "suspended" state. Fully shutdown they don't respond.

The systems are Dell Precsions with Broadcom 10G ethernet cards (tg3). The driver is the same (3.119) between RH and F16 (3.1 kernel) so seems that its in the surrounding code. Problem

When up, ethtool reports Wake On Lan = g, as expected, so everything looks good. I've tried putting 'ETHTOOL_OPTS="wol g" ' in the ifcfg-em1 and wedged 'ethtool-set' into all the places in ifdown-eth where the interfaces are cleared. Even commented out the line in ifdown-eth where the device is set "down" ('ip link set dev ${DEVICE} down'). No joy all around.

The new systemd setup does a very good job of hiding the whole halt process. there's no "/etc/init.d/halt" to play around with.

Any ideas? Any one?

TIA,

carl.

[carlmuck]

more on my situation.

looking directly into the /sys/class/net/em1/device/power/wakeup it is "enabled" setting ethtool -s wol d does set it to "disabled." So the system, when up, seems to be properly configured, but WOL does not work.

Looking at the device the link light is on on the card, so power is being applied, it just won't respond to the WOL. (And again WOL works for a system in "suspend" but not in "poweroff").

pointers?

carl.

---------- Post added at 10:40 PM ---------- Previous post was at 04:38 PM ----------

Curiouser and curiouser.

If I reboot and then when I get to grub, issue a halt from the grub command line, then WOL works. So there's something in the Fedora shutdown routines that is leaning heavily on the ethernet card.

Does anyone have a good approach for tracing what the heck is happening during the shutdown? I can't get any log information.

I've tried the recommendation from DBelton here for a script in /lib/systemd/system-shutdown, but it doesn't seem to run for me (I don't get any information in /dmesg.shutdown.

[carlmuck]

for those watching, a bit more info.

If I issue shutdown -H (instead of shutdown -h) telling the system to "HALT" not "POWEROFF" the system will not actually shutdown. Fedora gets to the end (apparently, the log file shows rsyslogd closing, which is usually last) but then just sits, in a powered state. If at that point I push the power button it shuts down, and then can be woken with WOL.

[Dutchy]

Most likely a driver problem even though the version hasn't changed.
What Broadcom model do you have?

[carlmuck]

I've got a Broadcom NetXtreme BCM5761. Its built-in to the Dell boxes I'm working with.

ACPITOOL reports that the cards are "disabled" for waking the PCI, I can't seem to get "enabled" to stick, so yes, it may be the card. I saw a couple of month old conversation about this but the mentioned patches are already in the driver. (I've pulled the source for it as well as systemd).

So right now my work-around is to reboot the box, intercept it in grub and halt from there. Very inelegant, but gets me what I need....

[coyrls]

I had the same problem as you and a simmilar level of frustration. I found the solution here: http://www.techanswerguy.com/2010/02...lan-redux.html

I can't get to grips with the way halt works with systmctl and so I added the following script with chkconfig:

#!/bin/sh
# chkconfig: 123456 55 95

case "$1" in
start)
        ;;
stop)
        rmmod tg3
        ;;
status)
        echo "fix for wol on shutdown"
        ;;
*)
        echo $"Usage: $0 {start|stop|status}"
        exit 1
esac

exit 0