I have an on-Board intel 82579LM Gigabit Network Connection on my HPz420 PC which runs Win 10 Pro x64bit. In the Networkadapter settings there isn't the "Active Magic Packets" option, in order to be able to activate Wake on Lan. Even though I could activate WOL in BIOS, if the network adapter itself hadn't the option to activate wol, it would not work. Does anyone know, if this network adapter support wol or not ?
Intel 82579LM Gigabit Network Connection – Wake on LAN Support
wake-on-lanwindows 10
Related Topic
- Linux – Does wake-on LAN/WOL depend on hardware or the operating system
- Linux – ethtool, WOL: What does “wake on physical activity” actually mean and (how) can I use it
- Intel 82579LM Gbit Ethernet Controller – magic packet (WOL) right after ping is not working
- WOL and WOW does not work after a certain time
Best Answer
Yes, 82579LM has WOL, I have not seen any NIC that does not have it since NE2000 nics.
When I think about WOL I think about power on from power off mode. (not really wake from sleep)
Not all features that a NIC has can be changed in all versions of the Windows driver, and some features can not be changed at all.
Sure, NICs have registers that can be modified to change features, but few (if any) store these, so the only time any options in a windows driver would have any effect is after windows boots, so potentially when a machine goes to sleep. but on system reset, and power off, they would be irrelevant.
Consider for a moment that you turn of the machine by pulling the plug, this resets the NIC entirely, now plug in the power, and use WOL to start the machine, note that no Windows driver would have had the chance to modify the registers on the NIC to modify WOL settings.
When you enable WOL in BIOS:
Now let's look on the drivers in Wired_driver_26.4_x64.exe
\PRO1000\Winx64\NDIS63\
there ise1c63x64.inf
here we can find82579LM
and in turnPowermgmt.reg
- Note that these settings are in regards to "wake from sleep" (this is driver ver 03/29/2016,12.15.31.4) So if you want' these settings, make sure to install a driver that has them.A quick search found this that especially mentions the NIC in question.