@ elisw

Its interesting cuz the latest version on asus.com is 11.7.0.1040. I will try this later: Intel MEI Driver v11.7.0.1052 MEI-Only Installer.


@ plutomaniac

ok, good. i'll try it tommorow or on monday and let u know.


Thank you all.

Zitat von plutomaniac im Beitrag #3560

---

@ crown_nick:

I made a typo. It's neither DHCP (LAN IP) nor DCHP (nothing). Its HDCP as jockyw2001 correctly assumed. When I say driver I mean for you to actually run the Setup of the latest Drivers & Software pack. The other command is only for Re-Key purposes.

---

Zitat von plutomaniac im Beitrag #3563

---

What does the Cyberlink Advisor show exactly? Maybe a picture?

---

Zitat von crown_nick im Beitrag #3564

---

Zitat von plutomaniac im Beitrag #3563

---

What does the Cyberlink Advisor show exactly? Maybe a picture?

---

It simply says that HDCP 2.2 is "Not Available." It would do the same thing if, say, SGX wasn't enabled in the UEFI. There's a log file that can be sent to Cyberlink but it doesn't have anything interesting. No "HDCP 2.2 failed at during handshake step 2.d" or RAM dumps or anything. It's a lowest common denominator log, basically.

That said, Cyberlink does encourage people sometimes to pass along DxDiag.txt, which is a far more detailed log that (IIRC) is generated by Windows. I have that and could potentially post it. HDCP doesn't really come up much but maybe there's something I'm missing.

---

@crown_nick

I am happy to report that those instructions I found at that above mentioned link successfully enabled SGX capability on my Z270M MSI board where according to Cyberlink UHD advisor it had previously failed. Here is my (almost) passing marks.

All I need now is to enable HDR and buy a HDCP 2.2 Display. Should note I also upgraded the ME to the latest 1054 version. The steps I took was to pull sgx_PSW_100.msi from the PSW Intel SDK package and run "msiexec /i SGX_PSW_nnn.msi" and uninstall the SGX extensions. Then I installed the new 11.7.0.1054 ME driver package. Rebooted. Ran msiexec SGX again this time installing the SGX code. Rebooted. And Voila it worked! Cyberlink lighted up green almost everywhere!




Heres the relevant file needed and instructions: https://www.mediafire.com/file/j1f4rsy54txy6d2/sgx.zip

Credit and Props to Whirlpool.

Zitat von davidm71 im Beitrag #3565

---

Check out this thread post #505:

https://forum.redfox.bz/threads/new-in-p...7.72076/page-26

---

Zitat von crown_nick im Beitrag #3567

---

Zitat von davidm71 im Beitrag #3565

---

Check out this thread post #505:

https://forum.redfox.bz/threads/new-in-p...7.72076/page-26

---

That's not related. SGX works fine on my setup. The Cyberlink advisor sees it and is happy.

Also, your board will never support HDCP 2.2. AFAIK, the only boards right now that support HDCP 2.2 are the ones that have Megachips's MDCP2800 chip, which does DisplayPort 1.2 -> HDMI 2.0a conversion of the signal from Intel's CPU and has built-in HDCP 2.2 support. (Right now, Intel GPUs don't have native support for HDMI 2.0 or HDCP 2.2. I'm sure this will change eventually.) For now, nothing else will work.

---

(I'll stop here as this is going way off-topic.)

Zitat von davidm71 im Beitrag #3568

---

Oh bummer. Was hoping to use a DP 1.2 to hdmi 2.0 a active adapter. At least I got SGX turn on for what its worth.

---

This tools is correct for my system: Intel CSME System Tools v11 r6 ?

asus z170 pro, intel 6700k

@crown_nick: resetting the playready drm might help :
https://blogs.msdn.microsoft.com/andrew_...ardware-change/

PS: seems this forum has a problem with redirecting. Here is the https link you should copy/paste:
blogs.msdn.microsoft.com/andrew_richards/2016/01/21/windows-media-center-reset-playready-after-hardware-change/

- edited -

Once again thank you fernando and plutomaniac for your fantastic work here, makes my job a lot easier. Whenever there's something going on with ME or AHCI / RAID I know where to look first.

ninjaed

Hello. Before I continue, a hearty thanks to everybody who has been helping out. I really appreciate it. :)

Zitat von plutomaniac im Beitrag #3572

---

@ crown_nick:

I mainly asked for a picture to see if everything else is Passing. For example Protective Audio/Video Path (PAVP) is a component of CSME firmware so I wanted to see if it shows as working too. There are some configuration options for DRM in Flash Image Tool but both BIOS/SPI from ASRock have the same.

---

Zitat

---

So as far as Cyberlink Advisor is concerned, I assume that you get all Passes except for HDCP 2.2 (GPU/Display) only, correct? To understand where the problem is we would need to test a few things like the CleanUp Guide on latest BIOS/11.8 and/or flashing the old BIOS/11.7 to see if that fixes it. Meaning, right now we don't know if the problem is CSME firmware corruption/misconfiguration, BIOS-related, Cyberlink-related (needs an update?) and so on. To test the non-Cyberlink theories we need to have read/write access to the CSME region of the SPI chip though. Maybe, after trying what jockyw2001 suggested, you want to try the "pinmod" (short two pins in the audio chip while the system boots) to temporarily unlock the Flash Descriptor (read/write access) and do some testing.

---

Okay. I have a few thoughts.

- In the pic you posted, I believe I saw an entry regarding LSPCON Display Port 1. ("The setting determines which port for LSPCON will be connected to the HDCP 2.2 bridge adapter Display 1.") I seem to recall posting in my last MEInfo dump that no port was listed. ("Retrieving Variable 'LSPCON Port Configuration' -> LSPCON Ports None") I'm a bit unsure of how exactly this works, seeing as how my rough understanding is that the MDCP2800 chip operates as the LSPCON and the bridge adapter. I know the ASRock Z270 Gaming-ITX/ac board (basically the same as mine, only mine has the Z370 chipset) activated HDCP 2.2 after-the-fact by using a slight variation of the flashing tool for the MDCP2800 that I used to update my chip's firmware to 1.72. The HDCP flasher was the same but it also included an entry for a key file. (Mine worked right out of the box.) Anyway, if this value is supposed to be set, then yes, something went wrong somewhere.
- I can't flash 11.7 firmware. I tried. The SVN restriction blocks it. I don't think flashing the original 1.10 BIOS will help but I'll keep it in mind.
- I'll give @jockyw2001's idea a shot. I don't think it'll help but I don't think it can hurt.
- Shorting pins is a bit above my pay grade. As much as I love tinkering, I've put too much money into the system to risk doing something silly to it. Maybe when a long-lost uncle dies and leaves me his fortune.... :)