SOLVED UHD 620 (KBL-R) not working after framebuffer patches

[takoriin]

Hi, I've been following the frame patching guide here and I've been setting the values here accordingly. I'm confused because the values for pavp and device-id were reflecting correctly, but the values for AAPL,ig-platform-id isn't. What am I missing here? Please help, thank you.

In addition to that, my About this Mac shows 7MB memory for the UHD620 which also solidifies the idea that the patch didn't work. My SoC is an Intel 8250U (Kabylake-R) if that also helps.

 

[EliteMacx86]

Hi, I've been following the frame patching guide here and I've been setting the values here accordingly. I'm confused because the values for pavp and device-id were reflecting correctly, but the values for AAPL,ig-platform-id isn't. What am I missing here? Please help, thank you.

In addition to that, my About this Mac shows 7MB memory for the UHD620 which also solidifies the idea that the patch didn't work. My SoC is an Intel 8250U (Kabylake-R) if that also helps.

Remove the pavp flag and also remove -igfxvesa boot arg.

 

[takoriin]

Remove the pavp flag and also remove -igfxvesa boot arg.

Did that just now and this is what I got, oddly enough.

Not sure if it’s the lack of the -igfxvesa which causes this, or maybe my igpu requires a different combination. I’m not really sure.

Update: can confirm that removing igfxvesa causes the kernel panic, but putting it back lets me boot again.

Update2: I tried checking my video outputs by booting the laptop to Windows and I can confirm that I have HDMI and USBC Video. I’ll read up WhateverGreen’s whitepaper on how to get the right platform-id.

 

[EliteMacx86]

Not sure if it’s the lack of the -igfxvesa which causes this, or maybe my igpu requires a different combination. I’m not really sure.

-igfxvesa disables the graphics completely.

Update: can confirm that removing igfxvesa causes the kernel panic, but putting it back lets me boot again.

Probably because of less DVMT. The DVMT must be at least 64MB. If you have 1080p screen, 32MB will work but you'll have to patch!

 

[takoriin]

Alright, I spent the whole day figuring out how to make this UHD 620 work and this is what I’ve done so far

1. Tried crosschecking in WhateverGreen’s documentation on what combinations will be feasible and I’m only stuck to 1659 and 1B59 due to my laptop’s port configuration.
2. Changed SMBIOS to MacBookPro15,2.
3. Applied the 32MB patch by following RehabMan’s config.plist for UHD620, kept 16590000 as the device-id and 1B590000 as the ig-platform-id, and I always get a kernel panic even when trying the -igfxdvmt boot-arg included.
4. Tried spoofing the GPU using the Skylake to Kabylake instructions in hopes to do the trick but it didn’t do anything. It booted with the args and 32MB patch but it didn’t have any effect at all. The system still shows 7MB.
5. Tried lilucpu=9 with the Skylake to Kabylake spoof and no dice.
6. Reverted everything to 16590000 as the device-id and 00001b59 as the ig-platform-id without the 32MB patch and adding -igpudvmt on and it boots with no issues. Still shows 7MB.
7. Didn’t change anything in my config outside the PciRoot(0x0)/Pci(0x2,0X0) section and boot-args.

Another thing: I don’t see the same thing in the tutorials for figuring out the device in IORegistry. I only see .Display_boot which makes connector patching almost impossible to do. Please advise. Attaching the config here.

 

[EliteMacx86]

Changed SMBIOS to MacBookPro15,2.

Not appropriate SMBIOS

Applied the 32MB patch by following RehabMan’s config.plist for UHD620, kept 16590000 as the device-id and 1B590000 as the ig-platform-id, and I always get a kernel panic even when trying the -igfxdvmt boot-arg included.

Outdated

Tried spoofing the GPU using the Skylake to Kabylake instructions in hopes to do the trick but it didn’t do anything. It booted with the args and 32MB patch but it didn’t have any effect at all. The system still shows 7MB.

If you have the KBL-R then what makes you think you have Skylake?

Tried lilucpu=9 with the Skylake to Kabylake spoof and no dice.

Same thing as above

Reverted everything to 16590000 as the device-id and 00001b59 as the ig-platform-id without the 32MB patch and adding -igpudvmt on and it boots with no issues. Still shows 7MB.

Outdated

Another thing: I don’t see the same thing in the tutorials for figuring out the device in IORegistry. I only see .Display_boot which makes connector patching almost impossible to do. Please advise. Attaching the config here.

That's because, the frambuffer info will only load when the Graphics drivers load. Graphics drivers contains framebuffers and all that info. If the driver is not loaded, it will never show the connector info as the framebuffer isn't either loaded nor being used. To patch the connector, either use a common formula or define every connector upto 3 or 4. Once you define one connector and have a display, you can start debugging and can patch the connectors easily.

 

[takoriin]

Not appropriate SMBIOS


Outdated


If you have the KBL-R then what makes you think you have Skylake?


Same thing as above


Outdated


That's because, the frambuffer info will only load when the Graphics drivers load. Graphics drivers contains framebuffers and all that info. If the driver is not loaded, it will never show the connector info as the framebuffer isn't either loaded nor being used. To patch the connector, either use a common formula or define every connector upto 3 or 4. Once you define one connector and have a display, you can start debugging and can patch the connectors easily.

I’m honestly lost with this. Sorry about this.

I have no issues switching back to 15,1 as that’s what the guides out there advise for Sonoma support. I did 15,1 per your suggestion in my first thread after all and that’s what made things work.

I just followed this guide for patching DVMT and under the Framebuffer section it mentioned referring to RehabMan. I have no idea that that part’s outdated.

GUIDE - How to Unlock DVMT Pre-Allocated on Laptops

How to Unlock DVMT Pre-Allocated on Laptops An EliteMacx86 Exclusive Guide - This guide covers unlocking of DVMT Pre-alloc on Laptops Overview Setting DVMT to 64 is required and it can avoid several graphics issue. This requirement is not only for laptops but for desktops too. But a majority...

elitemacx86.com

Doing the Skylake to KBLR patch is a silly move, I know. But given that both 1659 and 1B59 ain’t working for me I had to try something. Even with igfxvesa the whole thing crawls whenever the slightest animation plays.

I also checked Dortania’s guide and it’s essentially the same. Please let me know of the latest way around patching this and making UHD620 work with my system and I’ll do my best to follow it diligently.

 

[takoriin]

I’ll give up on this for now. I already formatted the drive to Windows and I’m setting it up as I type. This is getting way too complicated than what I can take. I’ll go back to this once I’m not too swamped anymore, or just save up and buy a used Mac Mini or Macbook. Thanks for everything.

 

[takoriin]

Please delete this thread. Already solved the problem by just purchasing a Macbook. Should've done that firsthand.

 

[EliteMacx86]

I’ll give up on this for now. I already formatted the drive to Windows and I’m setting it up as I type. This is getting way too complicated than what I can take. I’ll go back to this once I’m not too swamped anymore, or just save up and buy a used Mac Mini or Macbook. Thanks for everything.

Giving up is your choice. Yes, real hardware will give you a seamless experience if you cannot invest the time.