HP EliteDesk 800 G2 / HP ProDesk 600 G2 - SUCCESS

[maxsurf]

Thanks, I will try that soon, my windows keyboard does not want to cooperate.
I will keep you updated.

 

[asleb]

---------------------------
Don't add anything for your device-id - let it default to 0x1912 (a valid device-id for Skylake as listed here). Then (also according to this document), try AAPL,ig-platform-id=0x19120000. If that doesn't work, try AAPL,ig-platform-id values listed in this document (in the list labeled SKL framebuffer list) that have 3 connectors if you're trying to use IGPU for display or that have 0 connectors if you're trying to use your IGPU for computing with your RX580. If I were working on your rig and I wanted to use your IGPU for my displays, I would first try the following device properties for PciRoot(0x0)/Pci(0x2,0x0) (with the latest Lilu and Whatevergreen installed) with no other properties defined:

• AAPL,ig-platform-id=0x19120000 (which, interestingly enough is a mobile type according to this document)
• framebuffer-patch-enable: 0x00000001

I don't know OC, so you'll need to make sure these values are properly formatted in your config.plist.

--------------------------------------------

More advanced: This is why I suggested reading @RehabMan's DSDT patching guide. If you want to be good at this stuff, it's not sufficient to put values in a config.plist. Lot's of people can copy and paste stuff and get lucky and then brag about their "success." You need to understand why you're doing stuff. The IGPU device properties that you are injecting in your OC config.plist are equivalent to what would have been "old school" for patching the IGPU._DSM in your DSDT. If you're trying to get your rig working without understanding, it's like learning to play an instrument without learning how to read music. This is my philosophy, so take it for what it's worth. Be patient with yourself and take the time to read and learn.

I tested with all these values from the SKL framebuffer list

All these values shows on 2 monitors, 1024 res. (can not change), registers as 1 monitor:
0x191E0000 (mobile, 3 connectors, 56 MB)
0x19160000 (mobile, 3 connectors, 56 MB)
0x19260000 (mobile, 3 connectors, 56 MB)
0x19270000 (mobile, 3 connectors, 56 MB)
0x191B0000 (mobile, 3 connectors, 56 MB)
0x193B0000 (mobile, 3 connectors, 56 MB)

Shows correct res. but 2nd monitor disconnects after graphics is loaded
0x19120000 (mobile, 3 connectors, 56 MB)

On the value above I have to use framebuffer-patch-enable: 01000000 as the value you suggested-> framebuffer-patch-enable: 0x00000001 gives wrong resolution.

Using framebuffer-patch-enable: 01000000 with any ig-platform-id values gives no picture.

 

[deeveedee]

I tested with all these values from the SKL framebuffer list

All these values shows on 2 monitors, 1024 res. (can not change), registers as 1 monitor:
0x191E0000 (mobile, 3 connectors, 56 MB)
0x19160000 (mobile, 3 connectors, 56 MB)
0x19260000 (mobile, 3 connectors, 56 MB)
0x19270000 (mobile, 3 connectors, 56 MB)
0x191B0000 (mobile, 3 connectors, 56 MB)
0x193B0000 (mobile, 3 connectors, 56 MB)

Shows correct res. but 2nd monitor disconnects after graphics is loaded
0x19120000 (mobile, 3 connectors, 56 MB)

On the value above I have to use framebuffer-patch-enable: 01000000 as the value you suggested-> framebuffer-patch-enable: 0x00000001 gives wrong resolution.

Using framebuffer-patch-enable: 01000000 with any ig-platform-id values gives no picture.

You just learned a valuable lesson about device properties in the config.plist (the best way to learn and now a lesson you won't forget)! The difference between 0x00000001 (the actual 64-bit hexadecimal value of "one") and 0x01000000 is the byte ordering. We need to specify the "reverse byte order" 0x01000000 in the config.pllist and NOT the actual value 0x00000001 (using the actual value in the config.plist is WRONG). See this table for byte ordering examples of framebuffer AAPL,ig-platform-id values. The column labeled "reverse byte order" is what you need to use in the config.plist. See my config.plist attached to this post (in the EliteDesk.zip archive) for the reverse byte order values that I used.

If you enter 0x00000001 in your config.plist for framebuffer-patch-enable, you're NOT entering the correct value. I learned this the hard way, too! . The same applies for ALL data device properties in your config.plist.

Note that Hackintool does the byte ordering for you automatically.

 

[deeveedee]

Also note that this guide specifies the actual 64-bit hexadecimal framebuffer values. You need to reverse the byte order before entering these values in your config.plist.

Examples
If you are using a value of AAPL,ig-platform-id = 0x191E0000 in your config.plist, this is WRONG. You need to use the reverse byte order value 0x00001E19 in your config.plist. 0x191E0000 is the actual value, but the reverse byte order value 0x00001E19 MUST be used in the config.plist.

Another example: For AAPL,ig-platform-id = 0x19160002 (another valid framebuffer value for Skylake as listed here), the framebuffer value is 0x19160002, but you must enter the reverse byte order value 0x02001619 in your config.plist. If you enter 0x19160002 in your config.plist, this value is WRONG.

Again, Hackintool does the byte-ordering for you automatically.

 

[asleb]

Also note that this guide specifies the actual 64-bit hexadecimal framebuffer values. You need to reverse the byte order before entering these values in your config.plist.

Examples
If you are using a value of AAPL,ig-platform-id = 0x191E0000 in your config.plist, this is WRONG. You need to use the reverse byte order value 0x00001E19 in your config.plist. 0x191E0000 is the actual value, but the reverse byte order value 0x00001E19 MUST be used in the config.plist.

Another example: For AAPL,ig-platform-id = 0x19160002 (another valid framebuffer value for Skylake as listed here), the framebuffer value is 0x19160002, but you must enter the reverse byte order value 0x02001619 in your config.plist. If you enter 0x19160002 in your config.plist, this value is WRONG.

Again, Hackintool does the byte-ordering for you automatically.

Thanks. You are very patient No wonder it does not work! So This is the correct way to enter the SKL buffer values?

0x191E0000 (mobile, 3 connectors, 56 MB) -> 00001E19
0x19160000 (mobile, 3 connectors, 56 MB) -> 00001619
0x19260000 (mobile, 3 connectors, 56 MB) -> 00002619
0x19270000 (mobile, 3 connectors, 56 MB) -> 00002719
0x191B0000 (mobile, 3 connectors, 56 MB) -> 00001B19
0x193B0000 (mobile, 3 connectors, 56 MB) -> 00003B19

framebuffer-patch-enable: 01000000

 

[deeveedee]

Thanks. You are very patient No wonder it does not work! So This is the correct way to enter the SKL buffer values?

0x191E0000 (mobile, 3 connectors, 56 MB) -> 00001E19
0x19160000 (mobile, 3 connectors, 56 MB) -> 00001619
0x19260000 (mobile, 3 connectors, 56 MB) -> 00002619
0x19270000 (mobile, 3 connectors, 56 MB) -> 00002719
0x191B0000 (mobile, 3 connectors, 56 MB) -> 00001B19
0x193B0000 (mobile, 3 connectors, 56 MB) -> 00003B19

framebuffer-patch-enable: 01000000

You got it!

 

[asleb]

You got it!

Tested all these combinations and every time the second monitor turns off after graphics is loaded

0x191E0000 (mobile, 3 connectors, 56 MB) -> 00001E19 - no
0x19160000 (mobile, 3 connectors, 56 MB) -> 00001619 - no
0x19260000 (mobile, 3 connectors, 56 MB) -> 00002619 - no
0x19270000 (mobile, 3 connectors, 56 MB) -> 00002719 - no
0x191B0000 (mobile, 3 connectors, 56 MB) -> 00001B19 - no
0x193B0000 (mobile, 3 connectors, 56 MB) -> 00003B19 - no
0x19120000 (mobile, 3 connectors, 56 MB) -> 00001219 - no
0x19160002 (mobile, 3 connectors, no fbmem, 58 MB) -> 02001619 - no
0x19260002 (mobile, 3 connectors, no fbmem, 58 MB) -> 02002619 - no
0x191E0003 (mobile, 3 connectors, no fbmem, 41 MB) -> 03001E19 - no
0x19260004 (mobile, 3 connectors, no fbmem, 35 MB) -> 04002619 - no
0x19270004 (mobile, 3 connectors, no fbmem, 58 MB) -> 04002719 - no
0x19260007 (mobile, 3 connectors, no fbmem, 35 MB) -> 07002619 - no

framebuffer-patch-enable: 01000000

Now this is not a major problem. My major problem is sleep!

 

[deeveedee]

Tested all these combinations and every time the second monitor turns off after graphics is loaded

Now this is not a major problem. My major problem is sleep!

What is your "native" device-id of your IGPU (the default device-id when you don't override it with the device-id property)?

 

[asleb]

What is your "native" device-id of your IGPU (the default device-id when you don't override it with the device-id property)?

0x1912

 

[deeveedee]

0x1912

Have you tried with device-id = 0x00001912 (Reverse byte order: 0x12190000) and AAPL,ig-platform-id 0x19120000 (reverse byte order 0x00001219)?