GUIDE How to Enable Intel Skylake Graphics (Intel HD Graphics 515, 520, 530, 540, 550 and 580) on macOS Sonoma and Later

[aekennison]

I'm grateful for your replies to my questions, as always, thank you again. As for DVMT, I checked my bios and don't see any options. I will check again but I haven't seen anything. Since it's an AIO they may have decided to bake in those values and not expose them in BIOS. It certainly not obvious.

You mentioned checking whether the display is connected to IGPU or Nvidia; could you please point me to information that would allow me to confirm that? I've been on a search for motherboard schematics and other diagrams, hoping to figure out something like that.

The SKL CPU I have is a 6700T; it seems less common, and perhaps there is some additional configuration necessary.

I have another idea or two. First I was thinking of using VNC viewer after enabling share screen, so that even with the so-called correct ID and no native display I could blindly enter my password, and land on the desktop, at which point I could connect via VNC and perhaps look around. Doing that might allow OCLP to decide that it needs to do something with root patching.

The second idea relates to OCLP. When I build the EFI using the tool I see additional kext files, resources, etc, that I do not have in my EFI. So I was thinking about merging the so-called missing files and folders into my EFI, and updating my plist for the kext files. Essentially I am trying to get OCLP to acknowledge its existence on the system and similarly acknowledge that root patching has not occurred, and that it should do something. When I check the library folder there are simply the three EFI files like soft raid present. Even with that OCLP doesn't think it needs to do anything. I'm currently not running any device ID at all, only the AAPL value.

I'll read up on EDID, thank you for the tip. One additional thing, is that this is a dual boot setup, where I have Windows 10 running on a different partition. I have full access there for to anything in Windows, including device manager information. I've dug around in there looking for things, but I think it's a less common approach.

 

[EliteMacx86]

I'm grateful for your replies to my questions, as always, thank you again. As for DVMT, I checked my bios and don't see any options. I will check again but I haven't seen anything. Since it's an AIO they may have decided to bake in those values and not expose them in BIOS. It certainly not obvious.

It could be possible.

You mentioned checking whether the display is connected to IGPU or Nvidia; could you please point me to information that would allow me to confirm that? I've been on a search for motherboard schematics and other diagrams, hoping to figure out something like that.

Already linked it but will do that again.

GUIDE Thread 'How to check Laptop HDMI and other Display Output Ports connection'

Jun 20, 2020

How to check Laptop HDMI and other Display Output Ports connection​

An EliteMacx86 Exclusive Guide - This guide describes how to check Laptop's HDMI and other display output ports connection. By following this guide, you'll be able to find which GPU your external display output are tied to.

Overview

---

Normally, on Laptops, the internal screen is connected to the IGPU, and the other ports such as HDMI, mDP, DP, or VGA are also connected to IGPU. However, this is not the case with the Laptops with a dGPU. These Laptops usually have the internal screen connected...

• EliteMacx86
• amd apu connection dgpu display output display port hdmi igpu intel nvidia ports type type-c
• Replies: 0
• Forum: Graphics and Displays

The SKL CPU I have is a 6700T; it seems less common, and perhaps there is some additional configuration necessary.

Yes, the T CPUs are low TDP and no, there is not much to configure as the CPU is supported.

I have another idea or two. First I was thinking of using VNC viewer after enabling share screen, so that even with the so-called correct ID and no native display I could blindly enter my password, and land on the desktop, at which point I could connect via VNC and perhaps look around. Doing that might allow OCLP to decide that it needs to do something with root patching.

Yes, this is good idea!

The second idea relates to OCLP. When I build the EFI using the tool I see additional kext files, resources, etc, that I do not have in my EFI. So I was thinking about merging the so-called missing files and folders into my EFI, and updating my plist for the kext files. Essentially I am trying to get OCLP to acknowledge its existence on the system and similarly acknowledge that root patching has not occurred, and that it should do something. When I check the library folder there are simply the three EFI files like soft raid present. Even with that OCLP doesn't think it needs to do anything. I'm currently not running any device ID at all, only the AAPL value.

The steps are quite simple. Let's say for a SKL Desktop or Mobile CPU, one needs to have a correct EFI with the SKL device properties (framebuffer) and should be able to boot without any problems. As there are no SKL kexts present on macOS Sonoma and later, it will boot without any problems if the EFI is build correctly. Once the system is booted, make the necessary changes like disabling SIP, disabling Secure Boot to allow root patching. Reboot, and then just connect the system to interent, download and install OCLP and then run the root patching. Reboot when prompted and you should have the Graphics acceleration now. Of course, if you see a black/blank screen, the problem lies with the framebuffer patching. Also, not to forget some system may have a different panel which could be problematic and further adjustments might be necessary such as patching EDID or tuning the framebuffer patching.

I'll read up on EDID, thank you for the tip. One additional thing, is that this is a dual boot setup, where I have Windows 10 running on a different partition. I have full access there for to anything in Windows, including device manager information. I've dug around in there looking for things, but I think it's a less common approach.

Sounds great

 

[aekennison]

Thank you, I hadn't seen the port checking link; my display is connected to the IGPU. I've been thinking about this relative to the computer being an AIO and decided to track down the monitor part. It's information is here. It's been bothering me that eDP hasn't been considered (in my case), as it would be (in my view) the most direct way to connect to the IGPU. All the framebuffers / AAPL ID's I've tried were all using DP or HDMI connectors. I want to go back to WEG's info and see if there are any SKL AAPL ID's using eDP.... it might mean something in my system.

I have presumed that an invalid ID would have the OS fallback to VESA mode... thus my display "works" with the invalid ID. I will confirm this as I can with the vesa boot arg as you suggest.

This may be another rabbit hole for me to explore.

As for OCLP, I'm running Monterey, so I've assumed that SKL kexts should be available. I think SIP and secure boot are disabled, but will check again.

 

[aekennison]

I'm in the GUI thanks to your boot arg with the SKL AAPL ID 00001219. This feels like huge progress . I want to follow up with the other things you've mentioned and will report back later.

 

[aekennison]

I've managed to disable SIP and secure boot, and OCLP won't apply any patches. I was hopeful. Maybe the boot arg way of having ID 00001219 'work' disables patching; I don't know.

Hackintool shows this information for the peripherals (attached).

 

[EliteMacx86]

Thank you, I hadn't seen the port checking link; my display is connected to the IGPU. I've been thinking about this relative to the computer being an AIO and decided to track down the monitor part. It's information is here. It's been bothering me that eDP hasn't been considered (in my case), as it would be (in my view) the most direct way to connect to the IGPU. All the framebuffers / AAPL ID's I've tried were all using DP or HDMI connectors. I want to go back to WEG's info and see if there are any SKL AAPL ID's using eDP.... it might mean something in my system.

eDP has some problems and may need to address the issue. Had a few cases like Samsung where the eDP would just not output display despite of patching framebuffer correctly. It was Ivy Bridge/Haswell Laptop.

I have presumed that an invalid ID would have the OS fallback to VESA mode... thus my display "works" with the invalid ID. I will confirm this as I can with the vesa boot arg as you suggest.

That's right!

As for OCLP, I'm running Monterey, so I've assumed that SKL kexts should be available. I think SIP and secure boot are disabled, but will check again.

Oh, well. So, that's the reason why OCLP does not detect any patches. As the kexts are already present if you're sure you've installed Monterey, then there should be no need of the root patching.

 

[EliteMacx86]

I'm in the GUI thanks to your boot arg with the SKL AAPL ID 00001219. This feels like huge progress . I want to follow up with the other things you've mentioned and will report back later.

In VESA mode?

 

[EliteMacx86]

I've managed to disable SIP and secure boot, and OCLP won't apply any patches. I was hopeful. Maybe the boot arg way of having ID 00001219 'work' disables patching; I don't know.

It won't apply because the Monterey already has SKL Graphics kexts.

 

[aekennison]

In VESA mode?

Yes, 1024x768 resolution (ouch!)

 

[aekennison]

eDP has some problems and may need to address the issue. Had a few cases like Samsung where the eDP would just not output display despite of patching framebuffer correctly. It was Ivy Bridge/Haswell Laptop.


That's right!


Oh, well. So, that's the reason why OCLP does not detect any patches. As the kexts are already present if you're sure you've installed Monterey, then there should be no need of the root patching.

Great, just need to connect the IGPU kexts to the device, I suppose.