Jump to content

Booting Opencore ends with "Unsupported PCH" and "gIOScreenlockstate"


48 posts in this topic

Recommended Posts

Hello fellows!

 

I have a problem booting from the USB installer.

 

My setup:

  • Opencore latest version
  • MacOS Catalina
  • Lenovo Thinkpad p15v (2021)
  • Intel i7-10750h (Comet lake)
  • Intel UHD 630
  • Nvidia Quadro P620
  • 16 GB RAM DDR4

 

Now I know that Nvidia dGPU's cause problems, but I disabled it in the config.plist (at least I think I did...).

I followed Dortania's Opencore guide for Comet Lake Laptops carefully, cannot find any errors.

If somebody wants to help me, I'd be glad to at least know the problem.

 

Maybe it is not the GPU. I honestly don't know what "unsupported PCH" means...

 

I attached my EFI folder and the screenshot which I get when trying to boot from the USB....:

EFI: https://drive.google.com/file/d/1lnzaEQ6O8kBvBzrnLE0oZ6lLDZeSHBlD/view?usp=sharing

Error Screenshot: https://ibb.co/pbR2wGk

 

Thank you!!

 

IMG-20210413-231648.jpg

 

 

Edited by Philipp_Dahobo

Don't worry about the "Unsupported PCH" warning, that's without impact.

As stated by Slice, the last message you see on screen with "gIOScreenLockState" is indicative of graphics not initialising. Boot therefore gets stuck at that point. You're gonna need to revise the properties you inject for the iGPU of your Hackintosh.

https://dortania.github.io/GPU-Buyers-Guide/modern-gpus/intel-gpu.html#kabylake-refresh-coffee-lake-cometlake-8xxx-9xxx

https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md

 

It'd be better if you could directly attach a zipped copy of your EFI folder (you may remove the resources subfolder) rather than a link to a non-public Google Drive that requires authorisation to access. I gave up at that point...

 

  • Like 2
Posted (edited)
17 hours ago, Hervé said:

Don't worry about the "Unsupported PCH" warning, that's without impact.

As stated by Slice, the last message you see on screen with "gIOScreenLockState" is indicative of graphics not initialising. Boot therefore gets stuck at that point. You're gonna need to revise the properties you inject for the iGPU of your Hackintosh.

https://dortania.github.io/GPU-Buyers-Guide/modern-gpus/intel-gpu.html#kabylake-refresh-coffee-lake-cometlake-8xxx-9xxx

https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md

 

It'd be better if you could directly attach a zipped copy of your EFI folder (you may remove the resources subfolder) rather than a link to a non-public Google Drive that requires authorisation to access. I gave up at that point...

Thank you for replying and sorry for that, I couldn't get the zip smaller than 10 MB. I changed the Google Drive file to public.

EDIT: I see that I have to modify some entries in the config.plist. What I at least did right: I only put in the Lilu and WhateerGreen Kexts, none of the other. I will try this and report back if something changed, thank you!

Edited by Philipp_Dahobo

Just checked the EFI in the now-public Google Drive: no WhateverGreen kext and no reference to it in your OC config file. That's the 1st mistake. 2nd mistake is that there are absolutely no (zero) injected properties for your UHD 630 iGPU. This explains why you're getting stuck at graphics initialisation.

 

Make sure you add WEG kext to your OC setup (I understand you've done it now) and inject the necessary properties for your iGPU as per the info available through the links I provided earlier.

Posted (edited)
On 4/16/2021 at 2:33 PM, Hervé said:

Just checked the EFI in the now-public Google Drive: no WhateverGreen kext and no reference to it in your OC config file. That's the 1st mistake. 2nd mistake is that there are absolutely no (zero) injected properties for your UHD 630 iGPU. This explains why you're getting stuck at graphics initialisation.

 

Make sure you add WEG kext to your OC setup (I understand you've done it now) and inject the necessary properties for your iGPU as per the info available through the links I provided earlier.

I made the changes and it goes on now but I get a Kernel Panic... Not sure if I injected everything right. This is, what I got:

IMG_20210418_150230.jpg

This is my new EFI folder:

https://drive.google.com/file/d/1HwPWA-UZz5ge5KJgXlpQNIMFOgIIaLaA/view?usp=sharing

 

 

PS: I just went through the guide again for the config.plist and saw that they have three entries with "framebuffer" in that section which I don't have. On the other side I have an entry "layout-id" which they don't have. Anyway - I added those three frambuffer entries. But I cannot find information about what values I have to put in. Maybe this is the reason for my Kernel Panic now? 

DeviceProperties

Edited by Philipp_Dahobo
Posted (edited)
On 4/18/2021 at 3:48 PM, Philipp_Dahobo said:

I made the changes and it goes on now but I get a Kernel Panic... Not sure if I injected everything right. This is, what I got:

IMG_20210418_150230.jpg

This is my new EFI folder:

https://drive.google.com/file/d/1HwPWA-UZz5ge5KJgXlpQNIMFOgIIaLaA/view?usp=sharing

 

 

PS: I just went through the guide again for the config.plist and saw that they have three entries with "framebuffer" in that section which I don't have. On the other side I have an entry "layout-id" which they don't have. Anyway - I added those three frambuffer entries. But I cannot find information about what values I have to put in. Maybe this is the reason for my Kernel Panic now? 

DeviceProperties

I made it into the Installer! Had to fix some minor things in DeviceProperties. Now everything works fine as I notice.

Only exceptions:

- Drag and drop gestures with the trackpad are a bit buggy. (Scrolling and all other gestures work fine)

- My old USB Logitech mouse doesn't work. 

- graphic Acceleration doesn't seem to work (I notice that the interface doesn't behave 100% smooth)

 

 

Edited by Philipp_Dahobo

I've not checked myself but Slice did advise in his previous post to you that Comet Lake was not supported (despite what Dortania's documentation states) so, assuming that's indeed the case for laptops, you would never gain graphics acceleration. The only Mac computers ever built on Comet Lake platform are 2020 iMac desktop models (iMac20,x) and all use dedicated AMD graphics cards, not Intel UHD Graphics. But desktop UHD graphics is indeed supported in macOS Catalina and Big Sur, that's fully established. On the laptop front, things are a little different because last (2019/2020) Intel-based MacBook Air (MBA9,1)/MacBookPro (MBP16,x) are fitted with either 10th gen. Ice Lake and Iris Plus graphics or 9th gen. Coffee Lake R CPUs and UHD 630 graphics. There are no Comet Lake/Intel UHD graphics-based MBA or MBP.

 

You're gonna have to go through existing material posted for Comet Lake-based Hackintosh laptops and see if there's any success story with details of the iGPU settings used to obtain graphics acceleration.

 

I don't know if you've looked at (or properly read) the info provided in the WEG user manual (one of the links I posted in one of my previous answers) or Dortania documentation because you do not appear to be using the recommended settings posted in either place:

  • i7-10750H does carry Intel UHD Graphics iGPU (=UHD 630) with id 9BC4. It's understood to be supported natively (since it is listed in the CFL framebuffer kext) but, should it not be the case, fake CFL iGPU id 3E9B.
  • The iGPU framebuffer layout recommended by WEG and Dortania documentation for CFL/CML laptops is 3EA50009 (but you may try all of the listed mobile layouts of course).
  • At Dortania, mobile layout 3E9B0000 is clearly indicated as being for UHD 620.

The CFL framebuffer natively supports the following iGPU ids:

  • Coffee Lake-S UHD630 (GT2): 0x3E91, 0x3E92, 0x3E98
  • Coffee Lake-H UHD630 (GT2): 0x3E9B
  • Coffee Lake-U Iris Plus 655 (GT3e): 0x3EA5
  • Coffee Lake-U Iris Plus 645 (GT3e): 0x3EA6
  • Comet Lake-H UHD graphics (GT2): 0x9BC4
  • Comet Lake-S UHD630 (GT2): 0x9BC5, 0x9BC8

 

NB:

Discontinued 2019 15" MacBookPro 15,1 with 9th gen. Coffee Lake R CPU and UHD630 graphics (dev id 3E9B) used CFL framebuffer layout 3E9B0006. It'd be fair to say that the subsequent 16" model still in current production uses the same iGPU settings given that it's based on the exact same Coffee Lake R platforms as its predecessor.

 

  • Like 1

Hello, I'm a hackintosh noob running similar hardware (Lenovo Thinkpad, 10th gen Comet Lake CPU with Intel UHD 630 graphics) and using Opencore I've found myself in a similar situation (no graphics acceleration after a graphics-related pre-install issue) so I was hoping to compare notes.

I'm running Big Sur on my Lenovo as opposed to Catalina, which may be the cause of some of the issues I've encountered but here goes:
For me, I needed the -igfxvesa boot argument to get to the installer. (Thank you Slice and 1Revenger1!) You haven't posted your EFI after the success so I assume that's what worked for you as well.
I've been running 0x3E9B0007 as my framebuffer for most of my attempts because it has the most favorable outcome out of all the framebuffers when I boot without -igfxvesa (black screen as opposed to a forced reboot) and haven't specified a device-id to spoof as my iGPU's device-id, 0x9BC4,  is natively supported according to the Whatevergreen docs.
I've also been putting the framebuffer info underneath PciRoot(0x0)/Pci(0x2, 0x0) as opposed to PciRoot(0x0)/Pci(0x1b, 0x0) because that's where my iGPU is, and where I assume yours would be as well.

There are multiple ways to disable your dGPU, and I don't see any of them in the latest EFI you posted but the simplest way is using the -wegnoegpu boot argument.

Lastly, here's a post on reddit about a success with a working iGPU on a Comet Lake P15, even if it's a Xeon instead of a Core:


You'll be able to find my own post asking for help on this site as well if you wish to read it. If you have any more information about enabling GPU acceleration with a Comet Lake CPU and Intel UHD Graphic I'd be happy to hear it, and if you have any questions please go ahead and ask. Good luck!

EDIT: I got graphics acceleration and all the graphics drivers working on my iGPU a while ago but forgot to share the info here for anyone who might be interested in it.
I wound up using framebuffer 0x3EA60005 with the enable-max-link-rate-fix iGPU property and a device-id of 0x3EA6. The framebuffer would give me a black screen after the boot process if I didn't include the enable-max-link-rate-fix, and without the device-id graphics acceleration would "work" at first but Photos and other graphics-heavy apps would crash on launch, and certain webpages such as Amazon.com would work for a second then fail with a non-descriptive error message.
Hope this helps someone.

Edited by xefyr0
Update with more information
  • Like 1

If this guy states to have full graphics acceleration on the P630 iGPU (=UHD630) of his Comet Lake Xeon W-10885M, you should ask him what CFL framebuffer layout he's using and what iGPU id he's faking.

 

Edit: Arf! He does not appear to know! :thumbsup_anim:

8 hours ago, Philipp_Dahobo said:

I made it into the Installer! Had to fix some minor things in DeviceProperties. Now everything works fine as I notice.

Only exceptions:

- Drag and drop gestures with the trackpad are a bit buggy. (Scrolling and all other gestures work fine)

- My old USB Logitech mouse doesn't work. 

- graphic Acceleration doesn't seem to work (I notice that the interface doesn't behave 100% smooth)

 

 

 

Try here for a match or close match:

https://github.com/topics/hackintosh?o=desc&s=updated

  • Like 1
Posted (edited)
3 hours ago, xefyr0 said:

Hello, I'm a hackintosh noob running similar hardware (Lenovo Thinkpad, 10th gen Comet Lake CPU with Intel UHD 630 graphics) and using Opencore I've found myself in a similar situation (no graphics acceleration after a graphics-related pre-install issue) so I was hoping to compare notes.

I'm running Big Sur on my Lenovo as opposed to Catalina, which may be the cause of some of the issues I've encountered but here goes:
For me, I needed the -igfxvesa boot argument to get to the installer. (Thank you Slice and 1Revenger1!) You haven't posted your EFI after the success so I assume that's what worked for you as well.
I've been running 0x3E9B0007 as my framebuffer for most of my attempts because it has the most favorable outcome out of all the framebuffers when I boot without -igfxvesa (black screen as opposed to a forced reboot) and haven't specified a device-id to spoof as my iGPU's device-id, 0x9BC4,  is natively supported according to the Whatevergreen docs.
I've also been putting the framebuffer info underneath PciRoot(0x0)/Pci(0x2, 0x0) as opposed to PciRoot(0x0)/Pci(0x1b, 0x0) because that's where my iGPU is, and where I assume yours would be as well.

There are multiple ways to disable your dGPU, and I don't see any of them in the latest EFI you posted but the simplest way is using the -wegnoegpu boot argument.

Lastly, here's a post on reddit about a success with a working iGPU on a Comet Lake P15, even if it's a Xeon instead of a Core:


You'll be able to find my own post asking for help on this site as well if you wish to read it. If you have any more information about enabling GPU acceleration with a Comet Lake CPU and Intel UHD Graphic I'd be happy to hear it, and if you have any questions please go ahead and ask. Good luck!

Hello!

 

I also used -wegnoegpu. But on the same try I also changed some other entries so I cannot determine whether the -wegnoegpu entry or one of the other changes brought me to this little success. I did not post my EFI folder yet because I do not count it as a real success. I want to try some kexts first to get my USB mouse and mousepad working properly (drag and drop especially). But here you have it: https://drive.google.com/file/d/1nXx3q45Yp4g6JCRqu46QlDt4WGZzgtul/view?usp=sharing

 

I will post every update here. 

By the way, Thinkpads sometimes have that Intel SST Audio. As by Dortania stated, this is never going to work on MacOS. Wonder if anybody has a solution for that...

I tried to play music in Safari on the installation screen, but it would not even play so I could not test audio. However, I have an USB audio interface, so I could compensate this.

Good luck for you!

 

 

Edited by Philipp_Dahobo

@Philipp_Dahobo What success are you referring to here? You got the installer to boot but did you actually manage to complete the installation and then boot macOS?

 

Looking at the OC config available in your OC pack, I guess you could not possibly obtain graphics acceleration with the incorrect property injection you entered for iGPU id faking:

device-id        3E9B        DATA        // invalid iGPU device id 9B3E

when it should be (to fake CFL UHD630 iGPU id 3E9B):

device-id        9B3E0000        DATA

but, as previously stated, should not be required since CML 9BC4 is natively supported.

On 4/21/2021 at 3:50 PM, Philipp_Dahobo said:

By the way, Thinkpads sometimes have that Intel SST Audio. As by Dortania stated, this is never going to work on MacOS. Wonder if anybody has a solution for that...

This might not be true.
I have Intel SST Audio as well, and looking at the product spec for the P15 vs. the X1 Extreme, we share the same audio chip & codec. (ALC 3286, which is actually ALC 285 under the hood)
I managed to get sound coming out of my speakers & headphone jack with comparatively little effort, even if the microphone array doesn't work and the headphone jack's input remains untested.

In my case, the PCI address for the sound card was PciRoot(0x0)/Pci(0x1F,0x3) and layout-id 11 works perfectly fine. That said, I can't guarantee that these will be the same for your system so I recommend you double check the PCI address with gfxutil and test the other layout-ids to see if any of them work better than mine does for me.

You can just follow the Dortania guide using that info and it should work out. One think you should take note of is the alcid=XXX boot argument. (In the EFI you just shared, it's alcid=1) It overrides whatever you set in DeviceProperties so it's easier to use for debugging purposes, but it can interfere with your attempts to configure audio.

Good luck!


EDIT: I later discovered that the headphone jack input on my machine works, but only under layout-id 61. 

Edited by xefyr0
Update
  • Like 1

I successfully installed and have a quite fully working Hackintosh - except I cant geht HDMI to work. Neither via fallback to HDMI 1.4 nor via LSPCON (but maybe I made a mistake there). At least all dispalys are connected wo iGPU (verified in Windows).

 

 

  • Like 1

It is not UHD630. According to Intel specification it is 
Intel® UHD Graphics for 10th Gen Intel® Processors

It's the same thing slice. Basically, Intel recycled UHD6x0 graphics of Kaby Lake R/Coffee Lake in Comet Lake.

  • Comet Lake "H" mobile CPUs -> UHD630 graphics
  • Comet Lake "U" mobile CPUs -> UHD620 graphics
  • Like 1
5 hours ago, Hervé said:

It's the same thing slice. Basically, Intel recycled UHD6x0 graphics of Kaby Lake R/Coffee Lake in Comet Lake.

  • Comet Lake "H" mobile CPUs -> UHD630 graphics
  • Comet Lakje "U" mobile CPUs -> UHD620 graphics

Compare two CometLake processors

https://ark.intel.com/content/www/us/en/ark/compare.html?productIds=203899,201905

One has UHD630, other "graphics for 10th...".

Absolutely. And Comet Lake desktop CPUs generally show UHD630 graphics too in ARK Intel data.

 

But there is widespread literature on the Web stating that "Intel UHD graphics for 10th gen processors" is basically just a name for what is effectively recycling of Coffee Lake UHD6x0 graphics (itself a refresh of Kaby Lake R graphics). This is applied to mobile CML "H" and "U" CPUs. It gets a little more confusing when you realise that, in rare cases, some of those CPUs even have a GT1 iGPU version:

  • "U" CPUs have 23 to 24xEUs -> UHD620 (GT2)
  • "H" CPUs have 23 to 24xEUs -> UHD630 (GT2)
  • some rare "U" or "H" CPUs (eg: i5-10200H) have 12xEUs -> UHD610 (GT1)

As a general rule (but there are rare exceptions of course!), Pentium&Celeron have a 12xEUs iGPU, i3 CPUs have a 23xEUs iGPU and i5/i7/i9 have a 24xEUs IGPU. See attached Intel UHD Graphics Programmers Reference Manual for Comet Lake CPUs:

Intel UHD Graphics Open Source. Programmer's Reference Manual.pdf

  • Like 1

The integrated laptop display works out of the box. 

 

One thing that confuses me about Intel GPU patching: According to Intel ARK my iGPU is 0x9BC4. But WEG IntelHD (Comet Lake) lists the closest framebuffer 0x9BC40003 as desktop graphics. So I sticked with the recommended 0x3EA50009 for laptops, for UHD 630 - which is according to Wikipedia the GPU of i7 10750H.

But I am completely stuck at GPU patching. Framebuffer@1 is my HDMI port - but either the Laptop panics/freezes/stays black or the HDMI port does not work. I would be happy to have at least HDMI 1.4 working :/

 

Big thanks for the help!!! I attached my latest (working, but no HDMI) config

config.plist

Edited by vadammt
8 hours ago, Hervé said:

Absolutely. And Comet Lake desktop CPUs generally show UHD630 graphics too in ARK Intel data.

 

But there is widespread literature on the Web stating that "Intel UHD graphics for 10th gen processors" is basically just a name for what is effectively recycling of Coffee Lake UHD6x0 graphics (itself a recycling of Kaby Kale R graphics). This is applied to mobile CML "H" and "U" CPUs. It gets a little more confusing when you realise that, in rare cases, some of those CPUs even have a GT1 iGPU version:

  • "U" CPUs have 23 to 24xEUs -> UHD620 (GT2)
  • "H" CPUs have 23 to 24xEUs -> UHD630 (GT2)
  • some rare "U" or "H" CPUs (eg: i5-10200H) have 12xEUs -> UHD610 (GT1)

As a general rule (but there are rare exceptions of course!), Pentium&Celeron have a 12xEUs iGPU, i3 CPUs have a 23xEUs iGPU and i5/i7/i9 have a 24xEUs IGPU. See attached Intel UHD Graphics Programmers Reference Manual for Comet Lake CPUs:

Intel UHD Graphics Open Source. Programmer's Reference Manual.pdf 475.21 kB · 2 downloads

If you say that KabyLake and CoffeeLake graphics are the same then why there are two different set of graphics kexts, KBL and CFL?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...