wake-on-lan after power loss ( doesn't work).

  • Thread starter Thread starter H Brett Bolen
  • Start date Start date
I thank you for all these answers

Without you, I would be still posed many questions in my head ;)
 
After a power failure, i start the machine and stop it 2 secondes after (no
Windows loading), the WakeOnLAN is active.
 
After a power failure, i start the machine and stop it 2 secondes after (no
Windows loading), the WakeOnLAN is active.
Click to expand...

How do you "stop" the system?
How do you know WOL is active? And what did it wake up to?

/daytripper
 
I stop the system with the power switch button.
I know WOL is active because I can wake the system from a sended Magic
Packet on this machine.
 
I stop the system with the power switch button.
I know WOL is active because I can wake the system from a sended Magic
Packet on this machine.
Click to expand...

Did you press the power button absolutely *before* the system started loading
the OS? Or had it already started loading but just hadn't gotten to the
log-in screen?

/daytripper
 
Not, just before the BIOS loading page : CPU, memory, HDD...
Click to expand...

That's certainly a curiosity. Including laptops I have seven systems here,
comprised of five different designs and none of them are able to do the same,
even with bios loaded and looking for a boot block.

Do you know who made the motherboard for your system, and roughly when it was
manufactured?
 
I think it was an ABIT VH6.
I have two systems with the same motherboard and it results the same thing.

Next monday, I will test on a Dell GX270 machine, but I don't know what is
the installed motherboard.
I will tell you.
 
daytripper said:
That's certainly a curiosity. Including laptops I have seven systems here,
comprised of five different designs and none of them are able to do the same,
even with bios loaded and looking for a boot block.

Do you know who made the motherboard for your system, and roughly when it was
manufactured?
Click to expand...

Could it be that the NIC and/or whatever holds the "macic packet" has memory
retained as long as +5V SB is supplied. Holding the power button in is not
the same as removing AC line power. This just allows the PS-ON line, (pin14),
to go low, turning off the main PS.

Just a thought.

Virg Wall
 
V said:
Could it be that the NIC and/or whatever holds the "macic packet" has memory
retained as long as +5V SB is supplied. Holding the power button in is not
the same as removing AC line power. This just allows the PS-ON line, (pin14),
to go low, turning off the main PS.
Click to expand...

As long as the magic packet is received afer power is re-applied,
I'd be happy. This is not the case for my hardware.

I am the origional poster, and my hardware is supermicro X5DAL-G,
with motherboard intel e1000 ethernet.

Tech support worked with me and in the end, they determined that
it is not supported (wakeup after power loss) on this motherboard.
They kept pushing the 'resume after power loss' which as been
pointed out, is quite different.

I believe it is possible if the hardware were designed this way, and
I would be interested in knowing what mobo/ethernet card will
support this. all that would be needed ( in my mind), is a
default state of '+5v SB' to be on, and an ethernet card
that default power on state to be 'WOL on Magic Packet'. Or
maybe there is such a thing as line powered ethernet.

BTW, WOL WakeUp doesn't 'Resume' for me, it does a complete 'Power
On Self Test' ( So memory, usb, kbd, other peripherals don't need
power -- the power supply only needs to look for changes to
the WOL_Detect jumper [ or equivalent with mobo ethernet]).

b²
 
As long as the magic packet is received afer power is re-applied,
I'd be happy. This is not the case for my hardware.

I am the origional poster, and my hardware is supermicro X5DAL-G,
with motherboard intel e1000 ethernet.

Tech support worked with me and in the end, they determined that
it is not supported (wakeup after power loss) on this motherboard.
They kept pushing the 'resume after power loss' which as been
pointed out, is quite different.

I believe it is possible if the hardware were designed this way, and
I would be interested in knowing what mobo/ethernet card will
support this. all that would be needed ( in my mind), is a
default state of '+5v SB' to be on, and an ethernet card
that default power on state to be 'WOL on Magic Packet'. Or
maybe there is such a thing as line powered ethernet.

BTW, WOL WakeUp doesn't 'Resume' for me, it does a complete 'Power
On Self Test' ( So memory, usb, kbd, other peripherals don't need
power -- the power supply only needs to look for changes to
the WOL_Detect jumper [ or equivalent with mobo ethernet]).

b²
Click to expand...

I'm wondering if a different type of solution might work for you,
simply using an UPS. If power is off for too long to make a larger
UPS cost-effective, perhaps using software bundled with some to
logically power-off (for example the shut-down common in Windows) so
the power supply is still getting the AC input voltage to preserve
5VSB output to motherboard, just draining the UPS very slowly since
it's only powering a dozen or less watts for 5VSB (or 3VSB if the
power supply supports both).

However I'm not certain that all UPS will remain "on", after they shut
down the system... if one that stays on cannot be found perhaps
dedicating the UPS to a separate, dedicated 5V ~2A power supply
substituting for the original power supply's 5VSB rail.
 
On the Dell GX270 Machine.
After a Power Failure, when the electricity comes again, I can see the Power
light is On during one second. So, I test the WakeOnLAN is active ? Yes, i
can wake up the machine without rebooting the machine after a power failure.
So with all this tests, i don't know how to think.

I've read the www.acpi.info PDF document and I must know how it really
works...
 
Another test

I have two machines.

1st Machine :
NIC - WakeOnLAN ON (1)

2nd Machine :
NIC - WakeOnLAN OFF (2)

I put the NIC (1) in the 2nd Machine : I can wake up this machine.
I put the NIC (2) in the 1st Machine : I can't wake up this machine.

So, I conclude that the parameter is only saved in the NIC. But I'm not
sure...
 
| Another test
|
| I have two machines.
|
| 1st Machine :
| NIC - WakeOnLAN ON (1)
|
| 2nd Machine :
| NIC - WakeOnLAN OFF (2)
|
| I put the NIC (1) in the 2nd Machine : I can wake up this machine.
| I put the NIC (2) in the 1st Machine : I can't wake up this machine.
|
| So, I conclude that the parameter is only saved in the NIC. But I'm
| not sure...

Nope, not exactly.

For an NIC to do wake-on-LAN it has on-board hardware support to:
a) Recognise a 'magic packet' - its MAC address repeated so many times,
and;
b) Activate the WOL signal via the flying lead which plugs between it and
a m/board connactor.
Nothing gets 'stored' in the NIC from boot to boot,or by the BIOS, it is a
hardware function triggered by the content of the hardware buffer.

For an m/board to do wake-on-LAN, it must:
a) Provide the +5v 'standby' current to the NIC - part of the ATX spec;
b) Have the WOL connector on-board and the associated logic to suppot
it - also ATX;
c) Have 'WOL enable' set in the BIOS;

From my experience with Gigabyte m/boards - and a whole bunch of tests
done recently - if all of the above are 'present and correct' then sending
the rght magic packet to powered-nut-mot-booted machine will result in it
performing the same function as it the power button has been pressed:
a) From the 'standby' or 'hibernate' or 'suspend-to-RAM' states, it will
'resume';
b) From a powered-down state it will perform a full boot-up.

What happens if the machine completely loses power, so the +5v standby
current is interrupted, is a whole different issue.

Kevin.
 
test said:
Another test

I have two machines.

1st Machine :
NIC - WakeOnLAN ON (1)

2nd Machine :
NIC - WakeOnLAN OFF (2)

I put the NIC (1) in the 2nd Machine : I can wake up this machine.
I put the NIC (2) in the 1st Machine : I can't wake up this machine.

So, I conclude that the parameter is only saved in the NIC. But I'm not
sure...
Click to expand...

how did you set 'NIC - WakeOnLan " On and Off? What make/model
is the NIC?

Thanks.

b
 
"I put the NIC (1) - WakeOnLAN ON in the 2nd Machine : I can wake up this
machine."

But why can i wake up this machine ? It was WakeOnLAN OFF only in Windows...

I don't understand :(

Too many questions :)
 
| "I put the NIC (1) - WakeOnLAN ON in the 2nd Machine : I can wake up
| this machine."
|
| But why can i wake up this machine ? It was WakeOnLAN OFF only in
| Windows...
|
| I don't understand :(
|
| Too many questions :)

Okay - one step at a time.
The WOL function occurs before Windoze has even started to load - it
powers the machine back on.
WOL is enabled/disablled in the BIOS. If it is enabled, then it should
work - given the correct hardware.
Would be interested in knowing whereabouts in which version of Windoze you
found the option to turn OFF WOL ?
Kevin.
 
| "I put the NIC (1) - WakeOnLAN ON in the 2nd Machine : I can wake up
| this machine."
|
| But why can i wake up this machine ? It was WakeOnLAN OFF only in
| Windows...
|
| I don't understand :(
|
| Too many questions :)

Okay - one step at a time.
The WOL function occurs before Windoze has even started to load - it
powers the machine back on.
WOL is enabled/disablled in the BIOS. If it is enabled, then it should
work - given the correct hardware.
Would be interested in knowing whereabouts in which version of Windoze you
found the option to turn OFF WOL ?
Kevin.
Click to expand...

The WOL function does indeed occur before Windows loads, which is the
whole issue of the thread, that "something" is discriminating between
different settings, not the BIOS, as that m'board BIOS isn't executed
yet. It's not a certain version of Windows that allows changing the
WOL feature, it's all(?) versions, an option given by the NIC driver,
often accessible in the networking properties or perhaps Device
Manager props for the NIC. As an example:

http://69.36.189.159/usr_1034/nic_wake.gif

My memory of it is a bit vague, but I believe this feature is
implemented even if the NIC doesn't have a WOL header on it, then by
PCI bus feature.
 
Back
Top