Jump to content
6 posts in this topic

Recommended Posts

Hi everyone!

This is my first post on this forum.

 

Yesterday I switched from MacBookPro14,1 to MacBookPro15,1 because this fall I want to upgrade to Sonoma and MacBookPro14,1 is no longer support. But after doing that HDMI stopped working.

 

I have an ASUS UX510U with Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (Kaby Lake) and Intel HD Graphics 620. For this reason I added to my config.plist:

<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
<dict>
	<key>AAPL,ig-platform-id</key>
	<data>AAAbWQ==</data>
	<key>device-id</key>
	<data>FlkAAA==</data>
</dict>

As first attempt I tried to patch connectors without success. Then using 010 Editor and the IntelFramebuffer.bt script I found the following information about framebuffers and connectors:

ID: 591B0000, STOLEN: 38 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000130B
TOTAL STOLEN: 39 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 136 MB, MAX OVERALL: 137 MB (144191488 bytes)
Model name: Intel HD Graphics KBL 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

like reported on WhateverGreen FAQ.

 

I suppose that here everything is right. So maybe are other patches required?

36 minutes ago, miticollo said:

Hi everyone!

This is my first post on this forum.

 

Yesterday I switched from MacBookPro14,1 to MacBookPro15,1 because this fall I want to upgrade to Sonoma and MacBookPro14,1 is no longer support. But after doing that HDMI stopped working.

 

I have an ASUS UX510U with Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (Kaby Lake) and Intel HD Graphics 620. For this reason I added to my config.plist:

<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
<dict>
	<key>AAPL,ig-platform-id</key>
	<data>AAAbWQ==</data>
	<key>device-id</key>
	<data>FlkAAA==</data>
</dict>

As first attempt I tried to patch connectors without success. Then using 010 Editor and the IntelFramebuffer.bt script I found the following information about framebuffers and connectors:

ID: 591B0000, STOLEN: 38 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000130B
TOTAL STOLEN: 39 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 136 MB, MAX OVERALL: 137 MB (144191488 bytes)
Model name: Intel HD Graphics KBL 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

like reported on WhateverGreen FAQ.

 

I suppose that here everything is right. So maybe are other patches required?

The MacBook Pro 15,1 uses an entirely different Thunderbolt standard as it introduced the T2 chip for the first time. The system (GPIO) bus and SMC were designed to pass through the T2 chip. It causes a lot of repair shops issues to this day... So basically, unless you can emulate a T2 chip (which is yet to be done) I'm afraid 2017 backwards are your only options. 

36 minutes ago, miticollo said:

Hi everyone!

This is my first post on this forum.

 

Yesterday I switched from MacBookPro14,1 to MacBookPro15,1 because this fall I want to upgrade to Sonoma and MacBookPro14,1 is no longer support. But after doing that HDMI stopped working.

 

I have an ASUS UX510U with Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (Kaby Lake) and Intel HD Graphics 620. For this reason I added to my config.plist:

<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
<dict>
	<key>AAPL,ig-platform-id</key>
	<data>AAAbWQ==</data>
	<key>device-id</key>
	<data>FlkAAA==</data>
</dict>

As first attempt I tried to patch connectors without success. Then using 010 Editor and the IntelFramebuffer.bt script I found the following information about framebuffers and connectors:

ID: 591B0000, STOLEN: 38 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000130B
TOTAL STOLEN: 39 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 136 MB, MAX OVERALL: 137 MB (144191488 bytes)
Model name: Intel HD Graphics KBL 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

like reported on WhateverGreen FAQ.

 

I suppose that here everything is right. So maybe are other patches required?

If you want to upgrade to Sonoma, take a look at this: https://github.com/5T33Z0/OC-Little-Translated/blob/main/14_OCLP_Wintel/Ivy_Bridge-Ventura.md#installing-macos-ventura-on-ivy-bridge-systems - It allows you to upgrade to Ventura / Sonoma while using an older / unsupported SMBIOS. Should fix what you're looking for while maintaining HDMI support. Who knows, I hear rumours about newer versions of OpenCore supporting minimal T2 features so that could possibly include property HDMI support. 

Edited by Draykanos

Solved! This Reddit commet was very useful. Basically it seems that my HDMI connector works if the model identifier is a MacBookPro with an Iris Plus iGPU.
I tested MacBookPro14,1, MacBookPro14,2 and MacBookPro15,2.

On 7/22/2023 at 2:26 PM, miticollo said:

Solved! This Reddit commet was very useful. Basically it seems that my HDMI connector works if the model identifier is a MacBookPro with an Iris Plus iGPU.
I tested MacBookPro14,1, MacBookPro14,2 and MacBookPro15,2.

Ahh, fair enough. Spoofing IRIS graphics that doesn't go through the T2 SOC seems to work. 

  • Like 1

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
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...