Intel UHD 620 QE/CI problems..

[tikizondo94]

12 minutes ago, mnfesq said:

 

I compared my video code in my DSDT and SSDTs with yours.  What I have in an SSDT is in your DSDT.  All except one thing.  My SSDT for _SB.PCI0.IGPU has a _DSM method.  Your DSDT for _SB.PCI0.IGPU does not.  It is not elsewhere in your DSDT or SSDTs.  I added mine from my SSDT to the same location in your DSDT and removed some of the code for devices which your DSDT does not have.  Try it out to see if it does anything.  Just select the DSDT-VID_DSM in Clover options when you boot.  Don't make it your default DSDT.

 

DSDT-VID_DSM.aml.zip

This is what i get when i boot with the attached DSDT-VID.aml. Then i get the famous stop sign lol. This thing is really being a pain...

[mnfesq]

40 minutes ago, tikizondo94 said:

This is what i get when i boot with the attached DSDT-VID.aml. Then i get the famous stop sign lol. This thing is really being a pain...

 

Yeah, that's a step in the wrong direction.  ACPI error.  Never got to the video drivers.

[tikizondo94]

Well I've got some info regarding my laptops monitor connection may be the issue. My internal monitor uses an "eDP" connection. And I've been informed such connections are not well supported with macos. I'm wondering if anyone here with a kabylake-r/uhd 620 has successfully got QE/CI working with an eDP connection. And if so what magic did you need to work..

Sent from my ONEPLUS A5010 using Tapatalk

[mnfesq]

On 7/17/2018 at 9:12 AM, tikizondo94 said:

Well I've got some info regarding my laptops monitor connection may be the issue. My internal monitor uses an "eDP" connection. And I've been informed such connections are not well supported with macos. I'm wondering if anyone here with a kabylake-r/uhd 620 has successfully got QE/CI working with an eDP connection. And if so what magic did you need to work..

Sent from my ONEPLUS A5010 using Tapatalk
 

 

See if this will help you.

 

https://github.com/ZombieTheBest/XPS9350-10.13-HighSierra

 

2016-11-20

• Correct SKL laptops' internal display connector type from LVDS to eDP credit syscl

Edited July 20, 2018 by mnfesq

[tikizondo94]

 
See if this will help you.
 
https://github.com/ZombieTheBest/XPS9350-10.13-HighSierra

I'll give it a shot! Thank you. I'm still fight my graphics. I've recently been told that my monitor connection eDP may be the issue. But I'm still looking for a way. Seems other people with dells and eDP have got it working somehow. So I still have some hope left lol.

Sent from my ONEPLUS A5010 using Tapatalk

[mnfesq]

19 minutes ago, tikizondo94 said:

I'll give it a shot! Thank you. I'm still fight my graphics. I've recently been told that my monitor connection eDP may be the issue. But I'm still looking for a way. Seems other people with dells and eDP have got it working somehow. So I still have some hope left lol.

Sent from my ONEPLUS A5010 using Tapatalk
 

 

I think I found the patch in config.plist that you may need, but it might need to be changed from Skylake to Kabylake and may therefore need new/different code.  But you can try to ask Syscl what to look for and what to change it to for your set up.  For testing purposes, you can try to use FakeID for Skylake and Skylake's ig-platform-id.

 

<dict>
	<key>Comment</key>
	<string>eDP, port 0000, 0x19260004 credit syscl</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>AAAAAAAAAAAAAAgAAgAAAJgEAAA=</data>
	<key>Name</key>
	<string>AppleIntelSKLGraphicsFramebuffer</string>
	<key>Replace</key>
	<data>AAAAAAAAAAAAAAgAAAQAAJgEAAA=</data>
</dict>

Also, check this out:

 

 

Edited July 20, 2018 by mnfesq

[tikizondo94]

Good find. Yeah ive been trying to patch KBLframebuffer kext and have made "slight" headways. Ive found the code based on 0x59160000 "0 0 0 0 1 6 5 9 in Hex. And have tried to modify the LVDS connector to use eDP. The problem im having is im not exactly sure the data im using for eDP is correct. DisplayPort data is "0 0 0 4 0 0 0 0" and eDP "supposedly" is "0 4 0 0 0 0 0 0". But using clover to patch the kext would be a much simpler fix. 

[tikizondo94]

On 7/20/2018 at 1:58 PM, mnfesq said:

 

I think I found the patch in config.plist that you may need, but it might need to be changed from Skylake to Kabylake and may therefore need new/different code.  But you can try to ask Syscl what to look for and what to change it to for your set up.  For testing purposes, you can try to use FakeID for Skylake and Skylake's ig-platform-id.

 

<dict>
	<key>Comment</key>
	<string>eDP, port 0000, 0x19260004 credit syscl</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>AAAAAAAAAAAAAAgAAgAAAJgEAAA=</data>
	<key>Name</key>
	<string>AppleIntelSKLGraphicsFramebuffer</string>
	<key>Replace</key>
	<data>AAAAAAAAAAAAAAgAAAQAAJgEAAA=</data>
</dict>

Also, check this out:

 

 

I gave this a try. The only problem was he was using a haswell based cpu. Im using a kabylake-r. The Imac 14.2 had haswells in them. I dont know if i can spoof my machine into thinking its a haswell. I tried just a straight Smbios change to 14.2 iMac. It booted to a black screen. I guess its better than locking at IOScreenLockState lol. 

[123456789323]

any news on this?

[tikizondo94]

any news on this?

Nothing new. I'm kinda at a halt for now. Everything works flawless but QE/CI. Which it's pretty hard to use the machine without it. Hopefully with the finally release of Mojave, maybe some things will change.

Sent from my ONEPLUS A5010 using Tapatalk

[123456789323]

Try this and replace your whole EFI folder: 

 

 

FIX.zip

[tikizondo94]

3 hours ago, DSM2 said:

Try this and replace your whole EFI folder: 

 

 

FIX.zip

Thanks man. I appreciate the help. But, its still locking at the same spot. Replaced EFI. Cleared all caches and prelinked kernel. Attached is where it locks at.. 

[123456789323]

Did you try to remove the ntfs drive?

[tikizondo94]

12 minutes ago, DSM2 said:

Did you try to remove the ntfs drive?

Yes in previous attempts. Its a single 512GB NVMe drive. It dual partitioned currently with Windows 10 and Mojave DP5. But in other attempts ive wiped the entire drive and formatted for only mac. And installed only mac. I still always get locked at the same place. IOScreenLockState. I was using the new WhateverGreen and Lilu Kext and Modifications to Clover/Devices/Properties process. It allowed for a "smoother" experience WITHOUT QE/CI when booted. But i have never been able to get Acceleration with my internal monitor. Only with an external monitor hooked up via the hdmi port using 0x59120000 PlatfromID.. Laptop monitor goes black. 

[123456789323]

Ok, really interesting...

[tikizondo94]

1 hour ago, DSM2 said:

Ok, really interesting...

Its been a real fight for me. Ive pretty much just given up and went back to my macbook pro lol. This little dell is blazing fast and id love to use the i7 8550u in macos and see how it runs. But this IGPU 620 just will not accept kbl drivers for some reason. Ive had alot of help here on the forum and from various other forum sites. But we have not been able to get QE/CI working. Everything else seems to work flawless, Wifi, sounds, USB, etc. Anyways, I really appreciate your help. If you have any other ideas, im all ears and willing to try anything at this point

[123456789323]

Will tell you as soon as the "problem device" arrives today and I will get my hands on at night...

[tikizondo94]

8 hours ago, DSM2 said:

Will tell you as soon as the "problem device" arrives today and I will get my hands on at night...

You got one? Inspiron 13 7370?

[123456789323]

try following EFI 

 

 

EFI.zip

[tikizondo94]

3 hours ago, DSM2 said:

try following EFI 

 

 

EFI.zip

Tried attached EFI. Just getting the stop sign when trying to boot. Loads for about 20 seconds then stop sign. 

Attached are my current debug files if it would help at all. 

Send me Pauls-MacBook-Pro.zip

Edited August 10, 2018 by tikizondo94

[mnfesq]

I'm still following this topic and have some observations.  

 

The gIOScreenLockState message is what I got when I had dual GPUs.  Whenever you try to change your PCI ID, you get that error and I'm thinking it's because it is adding a "virtual GPU" rather than replacing the ID on your physical GPU.  In other words, ID injection via DSDT or Clover is not working and the only true ID you have and can use is 5917, not 5916.  If that means that your display will never be compatible with macOS, then that's what that means.  However, it may be that your solution will have to involve a change in the driver rather than a change in your DSDT.  If you can patch the driver to work with PID 5917, you may get it to recognize your display without "adding a new GPU." 

 

I looked at the info.plist for AppleIntelKBLGraphicsFramebuffer.kext.  The IOPCIPrimaryMatch includes the following ID's:

0x59128086 0x59168086 0x591B8086 0x591C8086 0x591E8086 0x59268086 0x59278086 0x59238086 0x87C08086

I'm thinking, if you haven't tried it already, to add the ID 0x59178086 and see if it will install/run.  It may be a more complicated matter than to just change the PCI ID in the kext since you indicated that the connector to your display is not supported for macOS.  But I do believe that it is supported for new iMacs so you may want to make sure that you are using that SMBIOS.  Given that you have a pretty trick laptop, I wouldn't give up on getting the internal display to use hardware acceleration. 

 

EDIT 1:  I just looked at RehabMan's FakePCIID_Intel_HD_Graphics.kext.  He added 0x59178086 to the IOPCIPrimaryMatch in that kext, which is used with FakePCIID.kext.  I don't recall if you ever just used these two kexts without others, such as Lilu and Whatevergreen.  If you have, then you don't need to patch the FB kext.  It won't work.  

 

EDIT 2:  There is another possibility that you have not tried.  I'm thinking that you might want to do a search for IGPU in your DSDT and SSDT's and remove all code related to your IGPU device (and GFX0 device.)  Then, you can add the IGPU device back using exclusively Clover patches.  It's possible that there is some code for your graphics device(s) that is conflicting with your attempt to inject a different PCI ID.  Only by removing all code from your DSDT/SSDT entirely and completely controlling what code gets added to create your IGPU device can you, perhaps, change its PCI ID.

Edited August 10, 2018 by mnfesq

[tikizondo94]

59 minutes ago, mnfesq said:

I'm still following this topic and have some observations.  

 

The gIOScreenLockState message is what I got when I had dual GPUs.  Whenever you try to change your PCI ID, you get that error and I'm thinking it's because it is adding a "virtual GPU" rather than replacing the ID on your physical GPU.  In other words, ID injection via DSDT or Clover is not working and the only true ID you have and can use is 5917, not 5916.  If that means that your display will never be compatible with macOS, then that's what that means.  However, it may be that your solution will have to involve a change in the driver rather than a change in your DSDT.  If you can patch the driver to work with PID 5917, you may get it to recognize your display without "adding a new GPU." 

 

I looked at the info.plist for AppleIntelKBLGraphicsFramebuffer.kext.  The IOPCIPrimaryMatch includes the following ID's:

0x59128086 0x59168086 0x591B8086 0x591C8086 0x591E8086 0x59268086 0x59278086 0x59238086 0x87C08086

I'm thinking, if you haven't tried it already, to add the ID 0x59178086 and see if it will install/run.  It may be a more complicated matter than to just change the PCI ID in the kext since you indicated that the connector to your display is not supported for macOS.  But I do believe that it is supported for new iMacs so you may want to make sure that you are using that SMBIOS.  Given that you have a pretty trick laptop, I wouldn't give up on getting the internal display to use hardware acceleration. 

 

EDIT 1:  I just looked at RehabMan's FakePCIID_Intel_HD_Graphics.kext.  He added 0x59178086 to the IOPCIPrimaryMatch in that kext, which is used with FakePCIID.kext.  I don't recall if you ever just used these two kexts without others, such as Lilu and Whatevergreen.  If you have, then you don't need to patch the FB kext.  It won't work.  

 

EDIT 2:  There is another possibility that you have not tried.  I'm thinking that you might want to do a search for IGPU in your DSDT and SSDT's and remove all code related to your IGPU device (and GFX0 device.)  Then, you can add the IGPU device back using exclusively Clover patches.  It's possible that there is some code for your graphics device(s) that is conflicting with your attempt to inject a different PCI ID.  Only by removing all code from your DSDT/SSDT entirely and completely controlling what code gets added to create your IGPU device can you, perhaps, change its PCI ID.

Ive not looked into modifying the KBL info.plist to add 59178086 but i have used the latest fakepciid and fakepciidintelgraphics.kexts with the modifications for 59178086. It has not seemed to make a difference. Ive tried all MinStolenPatches and DVMT modifications, even using the setup_var process in cloveruefi shell to modify my DVMT values in BIOS. Still same result. Now with this latest update with WhateverGreen And Lilu process, I can get my system to run somewhat "smoother". But still no QE/CI. Always 7mb in Intel HD620. Now when it comes to removing IGPU in my DSDT. Should i remove EACH instance of IGPU? I show 42 instances when searching for IGPU?

DSDT.aml.zip

[mnfesq]

20 hours ago, tikizondo94 said:

Now when it comes to removing IGPU in my DSDT. Should i remove EACH instance of IGPU? I show 42 instances when searching for IGPU?

DSDT.aml.zip

 

You need to remove the IGPU/GFX0 devices (and maybe PEGP devices) from your DSDT.  However, once you do that, your DSDT/SSDT won't compile if there is an entry that points to that device and it's not there.  I realize, however, that there is not a Clover patch that creates the IGPU device.  That could be created in a custom SSDT and MacIASL should be able to locate it and modify your SSDT references to it.  Please post your current DSDT/SSDT's and I can give it a try, although there are people out there who are better than me at customizing DSDT's.  I also noticed in Clover Configurator that there is an option to remove OEM DSM methods and it gives you the option of removing the DSM for Intel HD Graphics.  That should allow you to add a custom SSDT with a custom DSM for your IGPU device.  You might want to try that option and save the DSDT it creates (without the IGPU OEM_DSM) and post that.  (I could try that on my laptop since I have the same GPU but I can't guarantee that it would work on your laptop.)

[tikizondo94]

20 hours ago, mnfesq said:

 

You need to remove the IGPU/GFX0 devices (and maybe PEGP devices) from your DSDT.  However, once you do that, your DSDT/SSDT won't compile if there is an entry that points to that device and it's not there.  I realize, however, that there is not a Clover patch that creates the IGPU device.  That could be created in a custom SSDT and MacIASL should be able to locate it and modify your SSDT references to it.  Please post your current DSDT/SSDT's and I can give it a try, although there are people out there who are better than me at customizing DSDT's.  I also noticed in Clover Configurator that there is an option to remove OEM DSM methods and it gives you the option of removing the DSM for Intel HD Graphics.  That should allow you to add a custom SSDT with a custom DSM for your IGPU device.  You might want to try that option and save the DSDT it creates (without the IGPU OEM_DSM) and post that.  (I could try that on my laptop since I have the same GPU but I can't guarantee that it would work on your laptop.)

Sure bro. Attached is my current debug dump. All should be in there. 

debug_6316.zip

[bronxteck]

have you tried playing with FB-Patcher app