morphbzh' | Voilà j'ai eu quelques nouvelles concernant le mode de fonctionnement de la machine, avec l'ACPI, et le WakeOnLAN.
J'ai fait un petit tour sur le newsgroup : comp.sys.ibm.pc.hardware.networking
J'avoue que c'est un peu dans le désordre, désolé.
Code :
- My motherboard ( supermicro x5dal-g) has wake on lan which normally
- works fine.
- However if power is removed ( ie I shutdown normally, unplug
- it, then plug it back in ), the machine does not wake up.
- Has anybody had a problem with this ( or got it to work)?
- I suspect that it is not a problem with other adaptors.
- My first guess would be to check the BIOS for an option that sounds like
- "After power loss..." Alot of boards have an option in the BIOS that keeps
- them from powering on automatically after power loss, i.e. power surge,
- power plug removed then plugged back in.
- Nobody with a properly designed motherboard will get the above scenario to
- work - because:
- - WOL "wakes" only from the "Standby" state,
- - and the "Standby" state depends on memory data being kept alive.
- - When you lose the mains power to the system, the memory data is lost
- - and the system power controller recognizes it is no longer in the "Standby"
- state
- - hence there will be no WOL function available...
- WOL and "boot on power restore" are two different things. What you say is
- true for WOL, but with power removed, the real time clock in the BIOS is still
- active. All that is needed, is a circuit to turn on the power supply when
- mains power is restored. Some BIOSs do have this circuit. The BIOS can
- then respond to a WOL request.
- No, that won't give you WOL. The bios switch you're referring to cannot return
- the system to the *Standby* state, so there's no way WOL will function.
- In addition to the requirement I provided, I left out at least one other
- critical need for WOL to function. Think about how WOL works and you should
- quickly arrive at the correct conclusion...
- It doesn't need WOL--the system is fully up. You can set the power management
- to go to "Standby" if you wish to wait for a WOL. Of course the NIC, or
- whatever is connected to the LAN must be active.
- And that's *not* WOL, which was the whole point of the thread, eh?
- That's simply "Power Up after AC loss", already noted...
- You left out this part of my answer:
- "You can set the power management
- to go to "Standby" if you wish to wait for a WOL."
- >- When you enable WakeOnLAN in the Windows driver. Where is saved this
- >parameter ? In ACPI Tables ? In Windows Registry ? In a Network Card Memory
- >?
- The important thing is the driver then configures the nic adapter and
- typically a supporting logic element (usually the SIO as most designs utilize
- generic SIO GPIO pins to support WOL) that will recognize the "wake me now"
- signal from the NIC and in turn signal the system power control logic to tell
- the main power supply to fully turn on.
- >- At shutdown, the NIC puts into a WakeOnLAN mode ? or just in a certain
- >electrical state which allows WakeOnLAN ?
- Careful, if you're using "shutdown" to indicate "standby". These are
- significant, contrary terms. There is no return to "awake" from "shutdown",
- only from "standby".
- If you meant "standby", the important bits are noted above.
- >- If I understand what you say first, after a powerfailure, when electricty
- >comes again, the PC isn't in Standby state. But is the WakeOnLAN enabled at
- >this moment ?
- If the PC wasn't steadily maintained in the Standby state, WOL is not
- possible. You cannot transition from the "shutdown" state to the "standby"
- state. You can only WOL from "standby".
- The same NIC and SIO settings that I listed earlier depend on maintaining the
- "standby" aka "housekeeping" power to these elements to retain the settings.
- When the system is put into the "standby" state, "standby" power is always
- available as long as mains (AC) power is connected to the supply.
- But if the AC disappears, the "standby" power disappears, and these dynamic
- settings are lost, so WOL is not possible.
- Sorry - the generic use of "power management" so close to a bios discussion
- left me at the bios level, not the os.
- Ok, so to review, if the OP sets the bios to enable "Power Up after AC loss",
- has it automatically boot the OS, has the nic driver configured to enable WOL,
- and has the OS power management configured to always go to Standby after N
- minutes, then yeah, that'd work, because you're NOT trying to do the
- impossible of getting from a full power down state to "WOL-ready".
- You'd sure want N to be fairly large though...which might reduce the
- practicality of such a work-around...
- There are some BIOS power management schemes. I think an OS scheme would
- be better for the reasons you mention.
- You'd need to see when the power management was loaded. If it were after
- all the other drivers were set up, N could be very small. You'd have to
- be sure the NIC driver and the program to accept the WOL "magic packet"
- were up and running.
- Even with a BIOS without "boot on power return", a handful of Radio Shack
- parts will "push the button" on a return of power. All sorts of schemes
- could be implemented, based on the fact that power return will provide
- +5V SB from the PS, and that the BIOS boot routine is in ROM or CMOS.
- Perhaps with embedded nics, bios could be aware enough, but not for much
- longer. What "bios" is left after the Next Big Thing is foisted upon the world
- will be even less capable post code and then a quick jump to the boot block.
- Leave everything else up to Redmund....
- I was thinking if N was small the poor bastard who has to actually use that
- machine on prime shift would have to hover over the keyboard to keep the
- damned thing awake.
- Context is everything, and unless the OP expresses the desire and the ability
- to cobble his/her hardware such notions are going to remain unsaid ;-)
- Even so, the utility of having a system in some weird "warm but dumb" state
- where a full OS load is required upon fully awakening to do anything useful
- kinda escapes me...
- For servers, by the way, we solve this with much more sophistication (read:
- more hardware and firmware) as we in addition to such mundanities as WOL, we
- have to allow a remote controlled full power-down, full power-up, reset, and
- so on, and be able to remotely see what you would see on a local monitor
- during post.
- This capability is sold as an option specifically for lights-out sites. The
- option cost is more than an entry level pc ;-)
- >When electricty comes again, and you put the machine in standby mode again
- >(without loading OS, just from BIOS loading), "The same NIC and SIO
- >settings" are so lost by Power Failure, nevertheless why we can use
- >WakeOnLAN ?
- >This shows that these parameters are saved somewhere, no ?
- >
- >It's the last question ;)
- >
- Possibly it's a regiser set in the NIC, that is loaded by BIOS or OS
- driver initialization, and once loaded, is preserved by 5VSB, but due
- to complete power failure 5VSB is of course gone too, so NIC reverts
- to defaults again, the process repeats.
- But as I mentioned there's more than just the NIC, there is the on-board WOL
- support that has to be set and only remains set while the SB voltages are
- present. This support has traditionally been implemented using SIO ("Super IO"
- chip) GPIO pins within a special section of the SIO that is kept "alive" with
- the same SB power.
- Lose the SB power = lose these settings = no WOL is possible...
- You cannot "put the machine in standby mode again without loading the OS".
- Period.
- After a mains power failure, you *can* reapply "standby power" to the system,
- but it isn't in WOL mode any longer. Yes, because the "parameters are saved
- somewhere" in the nic and motherboard WOL logic and are only preserved while
- "standby power" is constantly maintained, as I explained...
- >After a power failure, i start the machine and stop it 2 secondes after (no
- >Windows loading), the WakeOnLAN is active.
- How do you "stop" the system?
- How do you know WOL is active? And what did it wake up to?
- 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.
- 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?
- Not, just before the BIOS loading page : CPU, memory, HDD...
- 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.
- 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.
- 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]).
- 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.
|
After a mains power failure, you *can* reapply "standby power" to the system, but it isn't in WOL mode any longer.
Par contre là, ça contredit tous mes tests, j'active le WakeOnLAN, j'éteins la machine (StandBy mode), je la débranche électriquement, je la remet, le WakeOnLAN est inactif, ça OK. Mais si je relance la machine et que je l'éteins 2s après (on est encore au stade du BIOS, Windows ne charge pas), le WakeOnLAN est actif. Quoi penser, je ne sais pas, encore beaucoup de questions en fait  Je repose la question sur le newsgroup.
Après une coupure de courant, l'ACPI n'est plus activé.
Après plusieurs tests. J'ai conclu que le paramètre WakeOnLAN "enabled/disabled" reste bien sauvegardé sur la carte réseau même après une coupure de courant. Pour que la carte réseau se remette en veille et que le WakeOnLAN soit actif, il faut relancer la machine, l'ACPI s'active, et relit les paramètres dans la carte réseau et dans les tables ACPI.
Message édité par morphbzh' le 12-01-2004 à 09:00:37
|
FORUM HardWare.fr
Faudra que je teste tout ça dès que j'aurai un moment 
Faut pas que le serveur de Hardware.fr crash sinon...
(avec les paramètre bios avec allumage sur pci et wol )
![[:fear]](https://forum-images.hardware.fr/images/perso/fear.gif "[:fear]")
