Jump to content

Stuck at IOConsoleUsers: gIOScreenLockState 3 Big Sur


markosgiassA
 Share

20 posts in this topic

Recommended Posts

Hey guys, I’m stuck at  IOConsoleUsers: gIOScreenLockState 3
I know it’s a graphic problem because if I use VESA I can boot, login and do stuff. 
I use the platform Id 19160000 which in High Sierra was the correct id for my laptop. 
my laptop is Clevo p650rg
CPU: intel Core i7-6700hq with Intel HD 530 graphics 
Graphics: Nvidia GeForce Gtx 970m 6gb 
16ram gb.
Any ideas how to make the graphics work?

Link to comment
Share on other sites

Hello,

Your graphics Intel HD530 should work.

Nvidia must be switched off by BIOS or by special SSDT. Anyway intel graphics will work regardless Nvidia.

There are different ways to do this: Clover or OpenCore, WhateverGreen or Hackintool etc.

Link to comment
Share on other sites

I used -wegnoegpu. 
I know it should work but I honestly see that it doesn’t. 
with high Sierra I had a usb problem but I had full acceleration without any problems of the graphics. 
here I get stuck with verbose.

 

I don’t have the ability to switch graphics cards only the choice between IGFX AND SG which means switchable graphics. 

Hello mr Slice 

 

I’ll try to disable other devices in bios. Maybe it interferes with opencore and can’t load. 
I want an answer maybe it’s not supported. 

Link to comment
Share on other sites

You can only use your iGPU in Big Sur and rest assured that Skylake HD530 is fully supported.

Why don't you post your bootloader config or, better, a zipped copy of your bootloader EFI folder?

Link to comment
Share on other sites

Ad in verbose -wegnoegpu and test this :

<key>PciRoot(0x0)/Pci(0x2,0x0)</key>

<dict>

<key>AAPL,GfxYTile</key>

<data>AQAAAA==</data>

<key>AAPL,ig-platform-id</key>

<data>AAAWGQ==</data>

<key>AAPL,slot-name</key>

<string>Internal@0,2,0</string>

<key>complete-modeset</key>

<data>AQAAAA==</data>

<key>device-id</key>

<data>FhkAAA==</data>

<key>device_type</key>

<string>VGA compatible controller</string>

<key>disable-agdc</key>

<data>AQAAAA==</data>

<key>enable-hdmi-dividers-fix</key>

<data>AQAAAA==</data>

<key>force-online</key>

<data>AQAAAA==</data>

<key>framebuffer-con0-enable</key>

<data>AQAAAA==</data>

<key>framebuffer-con1-enable</key>

<data>AQAAAA==</data>

<key>framebuffer-con1-type</key>

<data>AAgAAA==</data>

<key>framebuffer-con2-enable</key>

<data>AQAAAA==</data>

<key>framebuffer-fbmem</key>

<data>AACQAA==</data>

<key>framebuffer-patch-enable</key>

<data>AQAAAA==</data>

<key>framebuffer-stolenmem</key>

<data>AAAwAQ==</data>

<key>hda-gfx</key>

<string>onboard-1</string>

<key>model</key>

<string>Intel HD Graphics 520</string>

</dict>

 

Link to comment
Share on other sites

Still doesn’t work. 
It gets stuck after it finishes verbose and fixing its brightness. 

 

I have dvmt 256mb

cfg unlock 

disabled bios some settings like they say in guides. 
tried various patches. 
the problem is the same. 
if no fake Id there is no boot to screen. 

Link to comment
Share on other sites

Your laptop is fitted with Skylake i7-6800HQ CPU which integrates Intel HD 530 iGPU with id 0x191B. Getting stuck with the message you posted usually means graphics are not initialising, something confirmed by the fact that you can boot in VESA mode.

 

Looking at your OC config (1st link):

1) iGPU properties injection

iGPU_properties.jpg

  • You inject the expect SKL framebuffer 0x19160000.
  • It's not necessary to inject/fake device-id 0x191B, it's your iGPU's own native id; of course, injecting one's own device id is totally harmless.
  • you change connector con1 to HDMI and that's pretty good if HDMI is indeed attached to con1. This ensures you'll get HDMI audio.
  • I'm failing to understand your index patch for connector con2; what were you trying to achieve by this?
  • similar comment and question regarding your connector type patch for connector con2; what change it from DP to HDMI?
  • I can't see why you limit your SKL framebuffer to 2 x ports when it defines 3 x ports by default. I certainly would remove that.
  • hda-gfx should probably be set to "onboard-1" rather than "onboard-2".

For reference, here is the manner in which SKL framebuffer 0x19160000 is defined:

19160000, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000090F
TOTAL STOLEN: 56 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes)
Model name: Intel HD Graphics SKL CRB
Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP
00000800 02000000 98000000
01050900 00040000 87010000
02040A00 00040000 87010000

 

I would suggest you remove your con2 and port count patches to limit your properties injection to the strict minimum:

AAPL,ig-platform-id        00001619             DATA
framebuffer-patch-enable   1                    NUMBER
framebuffer-fbmem          00009000             DATA
framebuffer-stolenmem      00003001             DATA
framebuffer-unifiedmem     00000080             DATA
framebuffer-con1-enable    1                    NUMBER
framebuffer-con1-type      00080000             DATA
AAPL,slot-name             Internal@0,2,0       STRING
device_type                Graphics controller  STRING
name                       Intel HD 530         STRING

 

2) SMBIOS:

SMBIOS_MBP13,3.jpg

MacBookPro13,3 is fine; You may try and experiment with MBP13,1 or MBP13,2 if still no success with MBP13,3.

 

3) boot-args:

boot-args.jpg

You use -wegnoegpu and nv_disable=1 but your dGPU is a Maxwell card, i.e. a model totally unsupported under Big Sur. The bootflags are harmless of course but not required. -cdfon is linked to HDMI 2.0 capabilities so you may keep that. On the other hand, why do you use -disablegfxfirmware boot arg? I would suggest you remove that one.

 

nVidia Optimus technology being unsupported on Hackintosh, make sure your Optimus settings are properly setup in BIOS. Usually, if Optimus is disabled, only the nVidia dGPU is active, whereas if Optimus is enabled in BIOS, the iGPU and the dGPU are active. You would then need to disable the dGPU through DSDT/SSDT patching. This to prevent the dGPU from draining the battery unnecessarily. But this can be done in a later phase.

 

There are also a few odd things on the kexts front but nothing that would prevent graphics initialising.

 

I also looked at the EFI posted in your 2nd link but in the OC config it contains, you only injected the AAPL,ig-platform-id property and that's not enough.

 

Question: what is the resolution of your built-in LCD screen?

Link to comment
Share on other sites

3840 × 2160!

 

I updated the same injection commands you posted. 

AAPL,ig-platform-id        00001619             DATA
framebuffer-patch-enable   1                    NUMBER
framebuffer-fbmem          00009000             DATA
framebuffer-stolenmem      00003001             DATA
framebuffer-unifiedmem     00000080             DATA
framebuffer-con1-enable    1                    NUMBER
framebuffer-con1-type      00080000             DATA
AAPL,slot-name             Internal@0,2,0       STRING
device_type                Graphics controller  STRING
name                       Intel HD 530         STRING
Edited by markosgiassA
Link to comment
Share on other sites

Lilu & Whatevergreen fail to load? That would explain a few things... Are you using the latest versions?

 

Try and add the csr-active-config NVRAM parameter to disable SIP. Set it to 0x867 or 0xFEF.

 

Double check that you've followed the Dortania documentation for Skylake laptops; I saw a few other oddities in your OC config.

https://dortania.github.io/OpenCore-Install-Guide/config-laptop.plist/skylake.html

Link to comment
Share on other sites

Head a dead end. 
Stuck again as the tittle of this thread 

 

So I found an error in my audio PCIROOT it should be onboard 1 not 2.

so I managed to get graphics working. 
so it is a success now. 
I have a problem with connecting HDMI to another screen. 
should I start this matter here? Or open a new thread ? 

Link to comment
Share on other sites

7 hours ago, markosgiassA said:

So I found an error in my audio PCIROOT it should be onboard 1 not 2.

so I managed to get graphics working. 
so it is a success now. 
I have a problem with connecting HDMI to another screen. 
should I start this matter here? Or open a new thread ? 

I think you'd better to open new thread in appropriate section.

Here is the section for the first question, for introduction into hackintosh world.

Link to comment
Share on other sites

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.

 Share

×
×
  • Create New...