Intel HD 530 Monterey

[Alan Sojan]

12 hours ago, miliuco said:

@Alan Sojan

 

Working over the last EFI uploaded by @eSaF, replacing only config.plist, here you have 2 files, config1.plist and config2.plist.

Try first config1.plist, replacing the current config.plist (don't forget to rename config1.plist >> config.plist). Comment if it's working well.

If config1.plist fails, try config2.plist in the same way (replacing current config.plist and renaming config1.plist to config.plist).

• config1.plist has framebuffer for mobile Intel 530.
• config2.plist has framebuffer for NUC Intel 530.

 

config1.plist 18.45 kB · 1 download config2.plist 18.45 kB · 1 download

I tried both but both arent working? Im not sure if I'm doing something wrong.  I have windows installed on this machine as well if that can maybe help with this problem.

[feartech]

8 minutes ago, Alan Sojan said:

I tried both but both arent working? Im not sure if I'm doing something wrong.  I have windows installed on this machine as well if that can maybe help with this problem.

probably because of this boot argument:

-igfxvesa

 

 

[Alan Sojan]

4 minutes ago, feartech said:

probably because of this boot argument:

-igfxvesa

 

 

I will remove it and try.

[miliuco]

@feartech

 

What a mistake! I hadn't noticed this boot arg. Of course @Alan Sojan has to remove it, as long as you have it on there will be no graphic acceleration regardless of the framebuffer.

 

@Alan Sojan

 

These are the 2 config.plist previously uploaded, with -igfxvesa removed.

 

 

config1.plist config2.plist

Edited April 14, 2023 by miliuco

[Alan Sojan]

11 minutes ago, miliuco said:

@feartech

 

What a mistake! I hadn't noticed this boot arg. Of course @Alan Sojan has to remove it, as long as you have it on there will be no graphic acceleration regardless of the framebuffer.

I have tried both and removed the boot argument on both of them it's still not working. 

[miliuco]

1 minute ago, Alan Sojan said:

I have tried both and removed the boot argument on both of them it's still not working. 

config1 and config2? Do you still have 6 MB in the iGPU vram?

[Alan Sojan]

2 minutes ago, miliuco said:

config1 and config2? Do you still have 6 MB in the iGPU vram?

Yes I tried both, and it has 6 MB in the Graphics 

[Alan Sojan]

32 minutes ago, eSaF said:

I know this maybe a bit of stretch but is the BIOS the latest version for the motherboard? With all the tips/fixes offered, at least one should have cured the problem in my opinion.

Yes, I am on the latest BIOS version. I'm not sure if this affects anything but, I am using a VGA monitor with a HDMI adaptor.

[deeveedee]

@Alan Sojan For properly working VGA with HD530, you may need boot-arg igfxagdc=0 (same as DeviceProperty disable-agdc).

 

Also, I did a quick scan of the various config.plists posted in this thread: config.plist is missing framebuffer-patch-enable (so video patches are not applied) and it specifies a frame buffer with zero connectors (see here), config1.plist and config2.plist have incorrect framebuffers (needs to be Little Endian).

Edited April 14, 2023 by deeveedee

[miliuco]

Thanks @deeveedee for your notes. I change the framebuffer of both config.plist to little endian (19160002 >> 02001619 and 19160000 >> 00001619, right?). Also adding igfxagdc=0 boot arg. About framebuffer-patch-enable, both files have it with data value of 01000000, must be 00000001?  Other config.plist files are missing framebuffer-patch-enable, as you say.

 

Edited April 14, 2023 by miliuco

[deeveedee]

<01000000> is correct.  It's Little Endian representation of 0x00000001.

Edited April 14, 2023 by deeveedee

[miliuco]

@Alan Sojan

 

With changes by @deeveedee.

I cross my fingers. 

config2.plist config1.plist

[Alan Sojan]

27 minutes ago, miliuco said:

@Alan Sojan

 

With changes by @deeveedee.

I cross my fingers. 

config2.plist 18.45 kB · 1 download config1.plist 18.45 kB · 1 download

Hey, I tried config1.plist it loads up the code and turns off my monitor 

[Alan Sojan]

Will try the config2.plist now..

[Alan Sojan]

1 hour ago, miliuco said:

@Alan Sojan

 

With changes by @deeveedee.

I cross my fingers. 

config2.plist 18.45 kB · 2 downloads config1.plist 18.45 kB · 1 download

Both of the config.plist's are making my monitor turn off 😓 Not sure what the problem is.

Edited April 14, 2023 by Alan Sojan

[deeveedee]

@Alan Sojan Let's take a look at your config.plist.  Whenever you ask for help or have a problem, post your config.plist.  Not that we don't trust you, but it's easy to make mistakes (trust me, I've made many).

 

EDIT: Also, according to this, Skylake graphics is only officially supported up to MacOS 12 (Monterey).  If you're trying to test with Ventura, I would recommend that you start testing with a version of MacOS that officially supports your graphics.  We can "spoof" another device-id after you confirm that graphics works with a macOS that officially supports it.  This is my suggestion. Others may suggest that you spoof the device-id with Ventura as your first test.

Edited April 14, 2023 by deeveedee

[Alan Sojan]

18 minutes ago, deeveedee said:

@Alan Sojan Let's take a look at your config.plist.  Whenever you ask for help or have a problem, post your config.plist.  Not that we don't trust you, but it's easy to make mistakes (trust me, I've made many).

Okay, I understand. This is my config.plist

config.plist

[deeveedee]

@Alan Sojan  What version of OpenCore are you using?  When debugging a new system, I'd recommend sticking with only RELEASE versions (not Beta / nightly build).  Just my preference.

[Alan Sojan]

8 minutes ago, deeveedee said:

@Alan Sojan  What version of OpenCore are you using?  When debugging a new system, I'd recommend sticking with only RELEASE versions (not Beta / nightly build).  Just my preference.

I will check now. 

[deeveedee]

@Alan Sojan If you're using OC 0.9.2 nightly build, that's ok.  It's just that I find that there are typically enough things to diagnose in a new system without worrying about the stability of a DEVELOPER build.  If you're using OC 0.9.2, keep it for now.

[Alan Sojan]

3 minutes ago, deeveedee said:

@Alan Sojan If you're using OC 0.9.2 nightly build, that's ok.  It's just that I find that there are typically enough things to diagnose in a new system without worrying about the stability of a DEVELOPER build.  If you're using OC 0.9.2, keep it for now.

Hi, how do I check the version of OC I'm using? When I open it with Opencore configurator it says I have an old version of OC.

[deeveedee]

@Alan Sojan I'm not an OCAT user - nothing against it, I just don't use it.  If you run ocvalidate in the Open Core Utilities folder (in the version of Open Core that you downloaded), it will report the version.  I asked your version, because you're using quirk DisableIoMapperMapping which I think is not yet released (will be in OC 0.9.2 when it is released I think).

 

I will be able to look at this again later today and expect that others will have things to add here, too.  What I'll be looking at is the connectors in the frame buffers that you are using.  Here's where graphics patching gets tricky: just because you're using a frame buffer for HD530 doesn't mean that your graphics ports (e.g., HDMI) are mapped properly.  I looked at the EFI that @Rocky12 posted here and see that the OP isn't using HD530 iGPU.  I haven't patched Skylake iGPU before, so I'll be learning with you.

[deeveedee]

@Alan Sojan I'm not an OCAT user - nothing against it, I just don't use it.  If you run ocvalidate in the Open Core Utilities folder (in the version of Open Core that you downloaded), it will report the version.  I asked your version, because you're using quirk DisableIoMapperMapping which I think is not yet released.

 

I will be able to look at this again later today and expect that others will have things to add here, too.  What I'll be looking at is the connectors in the frame buffers that you are using.  Here's where graphics patching gets tricky: just because you're using a frame buffer for HD530 doesn't mean that your graphics ports (e.g., HDMI) are mapped properly.  I looked at the EFI that @Rocky12 posted here and see that the OP isn't using HD530 iGPU.  I haven't patched Skylake iGPU before, so I'll be learning with you.

 

EDIT: @Alan Sojan If you look at this, you will see that it defines each framebuffer (the definition associated with each AAPL,ig-platform-id).  For the skylake framebuffer in the config.plist that you posted (<02001619>, 0x19160002), the definition is:

ID: 19160002, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00830B02
TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes)
Model name: Intel Iris Graphics 540
Camellia: CamelliaV3 (3), Freq: 1388 Hz, FreqMax: 1388 Hz
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000498 - ConnectorLVDS
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000003C7 - ConnectorDP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000003C7 - ConnectorDP
00000800 02000000 98040000
01050900 00040000 C7030000
02040A00 00040000 C7030000

Note that the framebuffer defines the type of each connector.  None of the connectors in the framebuffer that you have chosen are HDMI.  You have two options after you choose a framebuffer: 1) add patches that modify the connector type and 2) choose a different framebuffer that more closely matches that of your rig.  Slice provided you with some mobile framebuffers here.  I only see one framebuffer (AAPL,ig-platform-id) that includes an HDMI port:

• 0x193B0000      mobile  3       56 MB (Has 1 HDMI port):

ID: 193B0000, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x00001187
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
[2] busId: 0x04, pipe: 10, type: 0x00000800, flags: 0x00000187 - ConnectorHDMI
[3] busId: 0x06, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP
00000800 02000000 98000000
02040A00 00080000 87010000
03060A00 00040000 87010000

Please try AAPL,ig-platform-id = <00003B19> and report back.  If this framebuffer doesn't work for you, then we'll need to add more patches to define the connector type.  Note that <00003B19> is the framebuffer that worked for Slice as he reported here.

 

EDIT2: FYI: My laptop with Kabylake UHD620 has an HDMI port.  I use an HDMI -> VGA adapter without any problems.

Edited April 14, 2023 by deeveedee

[miliuco]

@deeveedee

 

When you try to help, you do it in depth. This is certainly great information for @Alan Sojan to try to fix the issue he is having with the Intel 530.

But I'll go back to the first post in the thread. @Alan Sojan if you can try again the original EFI, the one you used when you started the thread and macOS showed the Desktop fine but with 6 MB in iGPU, my idea is to try this same EFI with the only change to remove -igfxvesa from boot args. It is the only change in a first step.

If the bug is not resolved, the second step is to add igfxagdc=0 to boot args (without -igfxvesa, of course).

The third step is to test the one that @deeveedee has proposed, AAPL,ig-platform-id = 00003B19.

Always without -igfxvesa.

 

[deeveedee]

@miliuco Very good idea.  Note that the macOS desktop will show when graphics patching is broken.  One technique to getting macOS to boot on a new hack before graphics patches are known is to intentionally use an invalid framebuffer.  macOS Desktop will likely display, but without graphics acceleration.  Looking forward to the OP's test results.

 

EDIT: Note that the original EFI in Post #1 has no DeviceProperties.  I will be amazed if it works.

Edited April 15, 2023 by deeveedee