0Sleep and WOL with Intel 82567LM‑3

I have a couple of old USFF Dell Opti­plex 760 PCs that have a built-in Intel 82567LM‑3 gig­abit eth­er­net con­nec­tion. Get­ting this adapter to work with both Sleep (S3 Sus­pend to RAM) and WOL (Wake on LAN) has proven very tricky. The PC ori­gin­ally came with Win­dows Vista and as a busi­ness class PC you’d expect these 2 fea­tures to work but it has always been a battle to get them work­ing.

Windows 7

Back in the days of Win­dows 7 I did even­tu­ally get both PCs work­ing with Sleep and WOL. Doing so required a lot of fid­dling about with drivers and set­tings so I will detail all the set­tings that worked for Win­dows 7 below.

  • Device: Intel 82567LM‑3
  • Intel ProSet 22.9.6.0
  • Driver 12.10.12.0
  • Driver Pro­vider: Intel
  • Driver Date: 18/07/2013
  • Power Save Options: All 3 unticked
  • Wake on LAN Options: both ‘Wake on Magic Pack­et’ ticked and ‘Wake on Pat­tern Match’ unticked

This driver can be down­loaded from soft­pe­dia. The driver files are found in the PRO1000\Winx64\NDIS62 sub­folder

Some sites also sug­gest that Intel ME needs to have the cor­rect set­tings in firm­ware. This is accessed by Press Ctrl‑P at bootup. I checked my set­tings and they are as fol­lows…

  • Intel ME Con­fig­ur­a­tion: State Con­trol: Enabled
  • Intel ME Con­fig­ur­a­tion: Man­age­ab­il­ity Fea­ture Selec­tion: Intel Stand­ard Man­age­ab­il­ity
  • Intel ME Con­fig­ur­a­tion: Intel ME Power Con­trol: Intel ME ON in Host Sleep States: Desktop ON
  • Intel Stand­ard Man­age­ab­il­ity Con­fig­ur­a­tion: SOL/IDE‑r: Enabled
  • Intel Stand­ard Man­age­ab­il­ity Con­fig­ur­a­tion: Cur­rent Pro­vi­sion­ing Mode: PKI
  • Intel Stand­ard Man­age­ab­il­ity Con­fig­ur­a­tion: Host Name: YOUR-PC-NAME-HERE
  • Intel Stand­ard Man­age­ab­il­ity Con­fig­ur­a­tion: TCP/IP: DHCP Enabled: Y

Once your ME set­tings are cor­rect, you have the driver above installed, and you have your win­dows set­tings cor­rect you should be able to use WOL from sleep when run­ning Win­dows 7.

Windows 10

Unfor­tu­nately the driver used for Win­dows 7 does­n’t want to be com­pat­ible with Win­dows 10 and so far I haven’t found an altern­at­ive that is offi­cially com­pat­ible. There is a good thread on the Intel for­ums that cov­ers the same issue and the poster there has been pretty thor­ough.

Like the poster on the Intel for­ums I tried for­cing a dif­fer­ent driver onto Win­dows 10 and suc­ceeded in for­cing a driver for the i218-LM card which does at least work. How­ever this still did­n’t get WOL work­ing.

Hacking the driver

To see if there is any way to get the Win­dows 7 driver work­ing with Win­dows 10 I set about hack­ing the inf file. I did man­age to hack it and get it to install although annoy­ingly this did mean I had to turn off driver sign­ing tem­por­ar­ily. I have detailed the pro­cess I used below.

Turn off driver sign­ing (see Win­dows 10 Tricks for more meth­ods)

  • Click start, expand the arrow next to shut­down, hold the shift key and click restart
  • Select troubleshoot­ing
  • Select advanced
  • Select reboot
  • At the menu that appears after reboot­ing press the 7 key to dis­able driver sign­ing

Edit the file e1k62x64.inf

  • Delete line 98
  • Change

    to

Use device man­ager to do a “have disk” forced driver install­a­tion. Then change the same set­tings as spe­cified for win­dows 7 above. This worked to install the driver that matches the one installed on Win­dows 7, but WOL still did­n’t work!

Next I need to check each of the ME set­tings and the Intel driver set­tings against each oth­er 1 by 1 in the hope that the dis­crep­ancy is some­where in the set­tings. I do remem­ber hav­ing an issue with Win­dows 7 where I had to find some obscure set­ting to get it work­ing. I am for­tu­nate to have 2 identic­al PCs, one with Win 7 and one with Win 10. I will con­tin­ue to see if I can find a solu­tion and will update this post with any­thing I find.

I also noticed that a small num­ber of set­tings seemed to show on the win 10 machine that wer­en’t present on the win 7 machine. I need to check my driver hack and also remote any pre­vi­ous Intel ProSet that has been installed to try to clear this. I plan to remove proset via pro­grams and fea­tures, and also remove and delete the drivers. I will then rein­stall the drivers and then run the proset installer (i will check to see how the driver was installed in win 7 — was it driver only or full proset)

What do you think? Drop us a comment below! If you would like to subscribe please use the subscribe link on the menu at the top right. You can also share this with your friends by using the social links below. Cheers.

Leave a Reply