October 23, 201312 yr Author I have the same board in mine & I've got it working from shutdown... haven't tried from sleep. Try ethtool -s eth0 wol g I added it to my go script also... I'm sure there's a better place to add it... but that's beyond me i really appreciate you chiming in to try and help us! it seems odd to me that the script above is fixing the problem, since i would have assumed that the script is only executed once unraid boots, therefore at the time the WOL packet is sent, the machine isn't booted, so how is that script being executed? for example, and i'm probably not saying this right, but it seems like you can't use a 'program' to help windows boot because the program can't run until after windows boots! or does the script create some kind of ready state for when the machine is off?
October 23, 201312 yr Here is the (edited) quote (from page above) I went from... You must switch the WoL support on in the destonation computer's_BIOS_. The field you need may be called Wake On Lan Enable or Power On By PCIE or any other like that; it may also happen that your BIOS does not allow setting this mode while the motherboard supports it by default. If you do not know whether your network card supports WoL, load the destination computer and enter in the console: ethtool eth0 It will return something like: Settings for eth0: Supported ports: [ MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 1 Transceiver: external Auto-negotiation: on Supports Wake-on: g Wake-on: d Link detected: yes You will need the lines Supports Wake-on and Wake-on. The first of them shows the available wakeup modes for the network adapter (actually, g stands for wakeup with Magic Pocket) and the second shows the current mode (d stands for WoL off). To switch your network card to WoL mode, execute: ethtool -s eth0 wol g To set WoL off, enter: ethtool -s eth0 wol d The adapter may save its final status, but it may also initialize it (usually setting it to d), that is why you need to set the required WoL mode at each booting. ... seems to work
October 23, 201312 yr Author thanks mike... its awesome that its working for you! does that mean that you didn't have to enable anything in the bios? a couple of us have been searching for a setting, but i assume you only followed the steps below, and didn't actually change a setting in the bios? we can't find what to change! i assume maybe our boards just have WOL permanently 'on' and that there isn't a setting for it in the bios? as soon as i'm home i'll run ethtool eth0 command to see if mine's on or off Here is the (edited) quote (from page above) I went from... You must switch the WoL support on in the destonation computer's_BIOS_. The field you need may be called Wake On Lan Enable or Power On By PCIE or any other like that; it may also happen that your BIOS does not allow setting this mode while the motherboard supports it by default. If you do not know whether your network card supports WoL, load the destination computer and enter in the console: ethtool eth0 It will return something like: Settings for eth0: Supported ports: [ MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 1 Transceiver: external Auto-negotiation: on Supports Wake-on: g Wake-on: d Link detected: yes You will need the lines Supports Wake-on and Wake-on. The first of them shows the available wakeup modes for the network adapter (actually, g stands for wakeup with Magic Pocket) and the second shows the current mode (d stands for WoL off). To switch your network card to WoL mode, execute: ethtool -s eth0 wol g To set WoL off, enter: ethtool -s eth0 wol d The adapter may save its final status, but it may also initialize it (usually setting it to d), that is why you need to set the required WoL mode at each booting. ... seems to work
October 23, 201312 yr I didn't change anything in the bios... I came across this thread, and seeing I had the same board, thought I'd check it out... I always use IPMI & had never tried the WOL.
October 23, 201312 yr Author I didn't change anything in the bios... I came across this thread, and seeing I had the same board, thought I'd check it out... I always use IPMI & had never tried the WOL. ok great thanks, will run the command you mentioned, i assume mine will report that WOL is off (hence why i can't boot with it) and then use the command you mention to enable WOL, and try again. assuming it works, will add command to my go file and we're good! why do i think i'll probably be posting back with further probs?
October 23, 201312 yr That may very well be the issue => you may have to change a setting in the LAN chip that isn't "brought out" to the BIOS (although clearly it SHOULD be !! ... and the manual implies it is with the comment about enabling WOL in the BIOS).
October 23, 201312 yr Author ok major progress, but with a snag ran the ethtool command..showed that 'supports Wake-on: g' but 'Wake-on: d'. so ran the command ethtool -s eth0 wol g also added this file to my go file. (i'll come back to this) then ran ethtool eth0 again and showed that 'Wake-on: g'. ok, good! shut down. ran wake up shortcut. seemed to take a long time, like a whole minute or so, then booted! amazing! wheee! BUT. then i wanted to try again! shut down. tried short cut, but nothing. waited a long time. booted up using power switch then when booted, ran ethtool again, and saw that 'Wake-up: D'!!! so for some reason the wake up reset back to D, but i want it set to G!!! i think maybe its how i added the script to my go file? i opened the go file in notepad, went to the end of all the text there, added one space and then pasted the command in. i'm not positive that's even the problem... ie does it even matter if its in the go file? if so, is there a better way to edit it?
October 23, 201312 yr What did you edit the go file with? I use Notepad++ in windows... Windows built-in Notepad doesn't work.
October 23, 201312 yr Notepad++ is a good choice for editing the GO file. I'm still surprised the BIOS doesn't allow this to be set correctly ... BUT if you put the command to reset it in the GO file, so it's set on every boot; then it SHOULD always work okay ... i.e. it will be set every time it boots; so WOL should work one time after that => and then when it boots again it will be reset again, etc. Not as good as a permanently set WOL option -- but should do the trick. The only problem is if you ever reload your flash drive you need to be sure you include that line in the GO file.
October 23, 201312 yr By the way, it probably won't help, but I'd send a note to SuperMicro and ask them if there's a way to correctly enable WOL so it's always available. Since there's apparently not a BIOS option, there MAY be a jumper on the motherboard that will do this.
October 23, 201312 yr Author well that sorted it! never used notepad ++ but will keep it handy, thanks for the suggestion! i have used windows notepad before and i guess i've gotten lucky. i think the problem was adding the space anyway... THANKS SO MUCH TO EVERYONE WHO HELPED ME WITH THIS!!! SUCH AN AWESOME COMMUNITY! actually got quite a few side benefits from this- got to know my bios better (warts and all), also got my pc setup with WOL (that worked MUCH easier lol) and have a great go file editor!!! thanks everyone, i really appreciate it!!! PS lastly just wanted to mention i'm using a very cool and free app for my ipad called Mocha WOL... i'm currently using it to wake my pc and (NOW) my server! works awesome for me since the pc and tower are in the basement but my ipad is always upstairs with me!!! anyway i'm not connected by to the app in anyway but works awesome!
October 23, 201312 yr check out this image. shows JWOL near the green slot. can only imagine JWOL stands for Jumper WOL.
October 24, 201312 yr From page 2-13 of the manual The Wake-On-LAN header is designated JWOL. See the table on the right for pin defi nitions. You must have a LAN card with a Wake-On-LAN connector and cable to use the WakeOn-LAN feature. (Note: Wake-On-LAN from S3, S4, S5 are supported by LAN1. LAN2 supports Wake-On-LAN from S1 only.)
October 24, 201312 yr I don't think the JWOL jumper has anything to do with the on-board LAN adapters. It's apparently to provide standby power to a LAN card with WOL support, so it can monitor the network for a WOL packet and send the appropriate signal to the motherboard.
October 24, 201312 yr What is the output of "ethtool eth0"? Not sure who you're asking... but here's mine Logopolis login: root Linux 3.9.6p-unRAID. root@Logopolis:~# ethtool eth0 Settings for eth0: Supported ports: [ MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 2 Transceiver: external Auto-negotiation: on Supports Wake-on: g Wake-on: g Link detected: yes root@Logopolis:~#
October 24, 201312 yr See here: http://lime-technology.com/wiki/index.php/Setup_Sleep_(S3)_and_Wake_on_Lan_(WOL)
October 25, 201312 yr See here: http://lime-technology.com/wiki/index.php/Setup_Sleep_(S3)_and_Wake_on_Lan_(WOL) Keep forgetting about the wiki I might try putting it to sleep... now that I found it wakes up!! Thanks...
Archived
This topic is now archived and is closed to further replies.