On the WaLL with WoL: Up & AT'em Cowboy (System reboots after shutdown, but only with onboard LAN)

[BiLUX]

First, I'm a layman with WoL problems outside of Windows.

I have a ASUS mini-ITX board with onboard LAN, and I threw in a netis PCIe gigabit card (its WoL doesn't work at all). My BiOS does NOT mentioned booting from PCIe explicitly (maybe because it doesn't have an PCIe 1x ?). If I put WoL to "Off" in NAS4Free's settings, the system does NOT reboot after a shutdown. The only settings that do anything are "ON" and WOL_MCAST. However, with those enabled on my onboard LAN adapter, the computer starts up/reboots on its own after a shutdown (reboots in about 30 seconds).

Moving on. I put in the netis PCIe card, put the cable in it, booted NAS4Free, and with the NAS4Free box hooked directly to a monitor, I shut it down (never used the web gui). Well, it stays shutdown now, but what about WoL? About 5 minutes later, I used mc-wol.exe XX:XX:XX:XX:XX:XX and what do you know, it BOOTS! But apparently I have to keep it this way, because once I change the interface setting in NAS4Free back to my on board LAN, it never shuts down! I guess it's just an overachiever...

So here I am presently thinking: How do I get keep this functionality and have NAS4Free connected to my LAN? I really don't know, so I'm asking here. Also I'm thinking: Why the hell does WoL "just work" without a fuss on Windows 7, why...

[BiLUX]

UPDATE: Well, disabling "ACPI 2.0 SUPPORT" in my bios lets me operate normally with the option WOL_MAGIC, no more immediate restarts. Still however, if the Wake on LAN options is set to "on", it still restarts in a few seconds. I'm going to try WOL_MCAST, being it might be more useful. WOL_UCAST is lost on me because I don't understand how you send something "directly" to the MAC, which by contrast makes me wonder how MAGIC works any differently?

I'm not sure if BSD just re-enables ACPI 2.0, but something changed. This leads me to believe that WoL support is a little "off" when in conjunction with ACPI 2.0. Windows 7 I believe requires ACPI 2.0 (I think Vista did anyhow), so maybe Windows has refined their support a little. I've ran this board in Windows 7 with WoL full on, not just enabled by Magic, and it never restarted like it does in BSD. I'm starting to think this might be an error on Windows behalf and not that BSD is doing something wrong. With the WoL setting to "on", maybe a computer would boot up immediately being that ANY activity could wake it. But who's on second, I don't know.

Also, news to me is that with my particular motherboard, I only have to POST to have WoL support with Magic. I *thought* the operating system had to put the NIC into a certain state for it to work, however just a clean POST works. So is that normal?

PROBLEM #2 !

Apparentely, I can no longer put the system down with -S3 . Not sure if this has anything to do with the ACPI 2.0 spec in BSD, but there's no love. If I can figure out how to log it and where the logs go, I guess I could debug something. Otherwise I can't, because as soon as it goes down thinking it's going into -S3, the video drops and all fans and disks are still spinning as if it -S3 never happened. However, something happened because the server is gone. -S3 worked before, but of course the system would just wake back up due to my WoL issue. I did enable -S3 strictly in my BIOS, instead of auto between -S3 and S1, so it should be the only available option that still works.

Atop of my mobo's bios reads (this is the latest and last bios version)...

M4A88T-I Deluxe BIOS Setup Version 1201
ACPI 2.0 SUPPORT [ DISABLED ]
ACPI APIC SUPPORT [ ENABLED ] (Apparentely you can't run without this enabled?)
Also, I only have wake enabled for [SPACE BAR] and PME# (no Ring or RTC)

[BiLUX]

UPDATE:

So I just finished installing NAS4FREE with "ACPI 2.0 SUPPORT" disabled from the start. Now -s3 works, and I can wake it up with WOL_MAGIC, but it only powers back up the hardware and the front power light starts to blink. Obviously this isn't good. I did read that ZFS doesn't like drives to spin down and this can cause the system to become inoperable, but I'm not sure if ZFS is solely to blame. So...

Can one use -s3 to suspend if they are using a ZFS pool? And assuming -s3 is working properly, is the system just supposed to come back to normal state like it was before issuing -s3, or is there something I'm missing?

BTW, I did try out WOL_MCAST and apparently that is part of or the entire part of why the system reboots after shutdown. Basically the settings of "On" and "WOL_MCAST" are identical as far as making the system reboot immediately after shutdown. I have still yet to find anything on how to use or why somebody would use WOL_UCAST.

[b0ssman]

wol and freebsd is a special thing.
either it works or it doesnt.
not much of the development of freebsd is spend on this.

normally since you need ecc for zfs (which you dont seem to have see https://forums.freenas.org/index.php?th ... zfs.15449/)
you get a board with ipmi which can be used instead of wol to achieve the same result.

[BiLUX]

If I had a computer with ECC memory and ipmi the odds are I wouldn't be booting from a USB drive.

Was looking at a SoC C2000 board (http://www.supermicro.com/products/moth ... -2758F.cfm), but then again I wouldn't be running NAS4Free from a USB drive if I had such hardware (amongst other things).

Of course, I didn't think NAS4Free was about spending hundreds of dollars on hardware, especially when not all options available work (i.e. WoL).

Anyways, thanks.

[b0ssman]

even if you had that board you should be running the embedded install from usb because its the recommended way of running nas4free.