Contribute
Register

[Guide] Intel Framebuffer patching using WhateverGreen

Joined
Dec 18, 2013
Messages
482
Motherboard
Lenovo Yoga C740
CPU
i7-10510U
Graphics
Intel UHD Graphics
Mac
  1. MacBook Air
  2. MacBook Pro
Mobile Phone
  1. Android
I'm trying to find the best settings for my Yoga C740 I7-10510U with Intel UHD Graphics (no number) - any hints? It is a Comet Lake based graphics, and Whiskey Lake CPU? That confueses me...

Thanks!
 
Joined
Jun 4, 2020
Messages
4
Motherboard
Surface Pro 2 (Unknown)
CPU
i5-4200U
Graphics
Intel HD 4400
I can not for life of me sort out my igpu setup for my OC. I've tried using framebuffer-fbmem and framebuffer-stolenmem along side framebuffer-patch-enable and the two platform ID's I've found for my HD 5000. I'm super lost at this point.
 
Joined
Sep 13, 2020
Messages
9
Motherboard
Skylake
CPU
Skylake
Graphics
620
What does this IVB/AppleIntelFramebuffer/AppleIntelController.cpp:14147 Assertion failed: (0 == i) || ((pfbInfo->rangeStolen.physBase - pfbInfoPrev->rangeStolen.physBase) == fFramebufferMemorySize) mean? Hd4000

Debugger called: </Library/Caches/com.apple.xbs/Sources/GPUDriversIntel/GPUDriversIntel-16.0.31/IONDRV/IVB/AppleIntelFramebuffer/AppleIntelController.cpp:14147 Assertion failed: (0 == i) || ((pfbInfo->rangeStolen.physBase - pfbInfoPrev->rangeStolen.physBase) == fFramebufferMemorySize)
>
Backtrace (CPU 0), Frame : Return Address
0xffffffb07cd2ba40 : 0xffffff802f6be00d mach_kernel : _handle_debugger_trap + 0x3dd
0xffffffb07cd2ba90 : 0xffffff802f7fbf03 mach_kernel : _kdp_i386_trap + 0x143
0xffffffb07cd2bad0 : 0xffffff802f7ed2da mach_kernel : _kernel_trap + 0x55a
0xffffffb07cd2bb20 : 0xffffff80335969bd as.vit9696.VirtualSMC : __ZN18VirtualSMCProvider10kernelTrapI22x86_saved_state_1010_tEEvPT_Pm + 0x46d
0xffffffb07cd2bbc0 : 0xffffff802f663b2f mach_kernel : _return_from_trap + 0xff
0xffffffb07cd2bbe0 : 0xffffff802f6be3c3 mach_kernel : _DebuggerWithContext + 0x113
0xffffffb07cd2bd00 : 0xffffff7fcba6bbaf com.apple.driver.AppleIntelFramebufferCapri : __ZN25AppleIntelCapriController13FBMemMgr_InitEv + 0x22f
0xffffffb07cd2bd70 : 0xffffff7fcba6ace6 com.apple.driver.AppleIntelFramebufferCapri : __ZN25AppleIntelCapriController5startEP9IOService + 0x712
0xffffffb07cd2bdd0 : 0xffffff802fdecfca mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xea
0xffffffb07cd2be40 : 0xffffff802fdecb78 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xcd8
0xffffffb07cd2bef0 : 0xffffff802fdebd0f mach_kernel : __ZN9IOService14doServiceMatchEj + 0x30f
0xffffffb07cd2bf50 : 0xffffff802fdeeae6 mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x186
0xffffffb07cd2bfa0 : 0xffffff802f66323e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
as.vit9696.VirtualSMC(1.1.6)[6F755764-8E17-36B0-8685-1E7E665211BE]@0xffffff8033587000->0xffffff80335adfff
dependency: as.vit9696.Lilu(1.4.7)[151FFC0B-EC7E-3736-AFED-9CE86076EA92]@0xffffff8033501000->0xffffff8033584fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[593AE8E6-8DF6-3911-B2C3-6A30430ED6A7]@0xffffff8031c00000->0xffffff8031c03fff
com.apple.driver.AppleIntelFramebufferCapri(16.0)[4F388A84-0C97-37D5-A1CB-4A6C557A9E73]@0xffffff7fcba51000->0xffffff7fcba98fff
dependency: com.apple.AppleGraphicsDeviceControl(6.1.14)[A40DBA32-8D97-3E0F-B813-0631C55C4341]@0xffffff7fcb1e1000->0xffffff7fcb1e4fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[593AE8E6-8DF6-3911-B2C3-6A30430ED6A7]@0xffffff8031c00000->0xffffff8031c03fff
dependency: com.apple.iokit.IOAcceleratorFamily2(439.31.1)[7FAA5933-BE49-3284-89AE-9252D326DAF1]@0xffffff7fcc9bd000->0xffffff7fcca28fff
dependency: com.apple.iokit.IOGraphicsFamily(582)[E0308B18-9E90-39DC-9D64-E63763B357D0]@0xffffff7fccafd000->0xffffff7fccb2cfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[285D610A-74EC-3A72-9F73-154B63B25011]@0xffffff803218c000->0xffffff80321b3fff

Process name corresponding to current thread: kernel_task
Boot args: debug=0x100 -wegdbg amfi_get_out_of_my_way=0x1 -no_compat_check -v keepsyms=1

Mac OS version:
20A4299v

Kernel version:
Darwin Kernel Version 20.0.0: Sat Jun 13 17:58:16 PDT 2020; root:xnu-7090.0.0.111.5~1/RELEASE_X86_64
Kernel UUID: 8A20D5DC-6ED7-31BE-8E81-A5ADCBC358D7
KernelCache slide: 0x000000002f400000
KernelCache base: 0xffffff802f600000
Kernel slide: 0x000000002f40c000
Kernel text base: 0xffffff802f60c000
__HIB text base: 0xffffff802f500000
System model name: iMac13,2 (Mac-FC02E91DDD3FA6A4)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 26587116287
 
Joined
Oct 2, 2020
Messages
3
Motherboard
Dell 7285 laptop
CPU
Intel Core i5-7Y57 (1.2GHz, 3.3GHz boost) 2 cores, 4 threads
Graphics
Intel 615HD GPU; Display12.3-inch (2880 x 1920) 3K 281ppi IPS LCD
Mac
  1. iMac
  2. MacBook Pro
Mobile Phone
  1. iOS
Can anyone report on, or assist with, getting the internal display on the Dell Latitude 7285 to function with Graphics Acceleration in Mojave? The internal display (3K) will work without Graphics Acceleration in native resolution(2880x1920) [and 1440x960 HiDPI]. Once the framebuffer patch (thank you, @RehabMan) is applied to fix Graphics Acceleration, the system boots, but the internal display will only show backlight [the screen is black, but backlit---the system successfully boots, but no-show on the internal display, although it is shown in About this Mac/Displays, but with the incorrect resolution(s)], and on the external monitor everything will work (including Graphics Acceleration).
I have tried a variety of fixes on this, specifically using the Hackintool and Guide to Custom HiDPI resolutions to set the correct aspect ratio and resolutions to the internal display [3:2, 2880x1920]. It may be a hint to this problem that Hackintool doesn't consistently read the "Display" information (with Graphics Acceleration working)--Hackintool variously returns either incorrect aspect ratios (16:9, 8:5, 4:3), or non-sensical (3860:189) ones. With Graphics Acceleration working, Hackintool reads the display as VID-4D10;PID1482 (which appears to be correct), but either incorrectly reads (or imposes) aspect ratios of either 16:10 and/or 16:9 (there are a large number of Scaled Resolutions that are offered in SysPrefs/Display for the internal display----all of them based on 16:10 or 16:9---importantly, none based on 3:2, which is the correct aspect ratio for the internal display. If Graphics Acceleration in turned off, Hackintool "Display" reads the correct aspect ratio (3:2), but the VID and PID seem to be incorrect [VID-756e6b6e;PID717]. It is as if, Whatevergreen or Apple, imposes a 16:10 or 16:9 aspect ratio to internal displays----is this true? My working theory is that if I can figure out how to successfully inform the GPU that the internal display is 2880x1920 (and the various scaled resolutions that cascade from this 3:2 aspect ratio) that the internal display will correctly "light up", instead of its currrent weakly flashing backlight (which is easily induced by choosing among the incorrect scaled resolutions that are offered in SysPrefs/Displays for the internal display).

Thank you for any kind assistance on this---I've hit the wall. I attach Debug.zip (thanks, @black.dragon74).
 

Attachments

  • debug_32657.zip
    4.4 MB · Views: 12
Joined
Feb 16, 2011
Messages
51
Motherboard
Clevo N141CU
CPU
i5-10210U
Graphics
HD620
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. iOS
Hi - I've got my HDMI working, but it takes 4 attempts before it connects (that's the laptop connecting, not me!).

Is this common? I assume it's not normal.

The laptop has eDP for internal, a Mini DP socket and an HDMI socket. The DP can be routed to either the mDP or the TB port in the BIOS - it is currently set to the mDP since I have a USB drive connected to TB. mDP works perfectly, HDMI does this multiple connect thing. Also, if I connected mDP and HDMI at the same time, there is corruption at the top of the screen but I'm happy to just not do that - one external screen will do :D

Excerpt from log when the issue occurs (FB2 is the HDMI port):

Code:
[IGFB][INFO   ] [AGDC] Get port status
[IGFB][INFO   ] FB2, port = 2
[IGFB][INFO   ] FB2 Getting display status
[IGFB][INFO   ] FB2 Setting DP power state = 1
[IGFB][ERROR  ] FB2: WriteAUX Timeout for addr 600 with Status = 0xe00002d6
[IGFB][ERROR  ] FB2: ReadAUX Timeout for addr 600 with Status = 0xe00002d6
[IGFB][ERROR  ] FB2: WriteAUX Timeout for addr 600 with Status = 0xe00002d6
[IGFB][ERROR  ] FB2: ReadAUX Timeout for addr 600 with Status = 0xe00002d6
[IGFB][ERROR  ] FB2: WriteAUX Timeout for addr 600 with Status = 0xe00002d6
[IGFB][ERROR  ] FB2: ReadAUX Timeout for addr 600 with Status = 0xe00002d6
[IGFB][INFO   ] Set DP power state failed. Returned state 0
[IGFB][INFO   ] Setting DP power failed (0xe00002bc), ignoring empty dongle handling (likely HDMI/TMDS case)
[IGFB][INFO   ] FB2 Display status is = 0

CPU etc., is to the left. SMBIOS is MBP16,3 (not sure this is correct?) My OpenCore Device Properties for iGPU are attached...

Any tips greatly appreciated!
 

Attachments

  • igpu_props.txt
    761 bytes · Views: 19
Last edited:
Joined
May 20, 2020
Messages
1
Motherboard
asrock h170m ax it
CPU
i5-6600K
Graphics
GTX 1070
Hi guys, after a CPU upgrade i've changed the bootloader from clover to OC.
Everything is ok except for the iGPU (there was no acceleration) so i tried with the patch and now it works, but the monitor is flickering at the login and i have to disconnect and riconnect the HDMI cable.
Can you help me to fix this problem pls?
My HW is: asrock h170m itx/dl with intel i7 7700
 

Attachments

  • EFI.zip
    2.2 MB · Views: 18
Joined
Dec 11, 2020
Messages
4
Motherboard
Gigabyte H97M-D3H
CPU
i7-5775c
Graphics
Iris Pro 6200
I've recently upgraded my CPU from i3-4370 (HD4600) to i7-5775c (Iris6200Pro, Broadwell) running Mojave and while acceleration is working it looks like the GPU is stuck at 300Mhz. I've tried all sorts of options, different adapter ids, different PM settings, switching between Clover's Intel Inject and WEG, no luck. The card is properly recognised and works fine but it's pretty slow when acceleration is needed (games), maybe even slower than the HD4600 used to be. How do I fix this? (either force the high clock rate or enable proper igp PM)
 

Attachments

  • Screenshot 2020-12-11 at 14.07.52.png
    Screenshot 2020-12-11 at 14.07.52.png
    69.1 KB · Views: 18
  • Screenshot 2020-12-11 at 14.07.24.png
    Screenshot 2020-12-11 at 14.07.24.png
    61.6 KB · Views: 20
Joined
Oct 12, 2017
Messages
12
Motherboard
MSI X299M Gaming Carbon AC
CPU
i7-7800X
Graphics
RX 580
Mobile Phone
  1. Android
I've recently upgraded my CPU from i3-4370 (HD4600) to i7-5775c (Iris6200Pro, Broadwell) running Mojave and while acceleration is working it looks like the GPU is stuck at 300Mhz. I've tried all sorts of options, different adapter ids, different PM settings, switching between Clover's Intel Inject and WEG, no luck. The card is properly recognised and works fine but it's pretty slow when acceleration is needed (games), maybe even slower than the HD4600 used to be. How do I fix this? (either force the high clock rate or enable proper igp PM)

Try to use boot-arg igfxrpsc=1 with Whatevergreen.kext.
 

trs96

Moderator
Joined
Jul 31, 2012
Messages
19,676
Motherboard
GA-Z97X-UD3H-BK
CPU
i5-4690K
Graphics
HD4600 / RX 570
Mac
  1. MacBook Pro
  2. Mac mini
Mobile Phone
  1. Android
I've tried all sorts of options, different adapter ids, different PM settings, switching between Clover's Intel Inject and WEG, no luck.
Have you tried using iMac 14,4 SMBIOS ? That should increase the iGPU frequency. A lot.

If you change the SMBIOS permanently you will have to create a new USBPorts.kext as the kext is linked to product name. You could get away with editing just the plist file inside the kext, but if usb starts acting up it's best to create a new map. You will also have to generate a new pair of serials and system UUID if you change the model.
 
Joined
Dec 11, 2020
Messages
4
Motherboard
Gigabyte H97M-D3H
CPU
i7-5775c
Graphics
Iris Pro 6200
Have you tried using iMac 14,4 SMBIOS ? That should increase the iGPU frequency. A lot.

If you change the SMBIOS permanently you will have to create a new USBPorts.kext as the kext is linked to product name. You could get away with editing just the plist file inside the kext, but if usb starts acting up it's best to create a new map. You will also have to generate a new pair of serials and system UUID if you change the model.
Try to use boot-arg igfxrpsc=1 with Whatevergreen.kext.
Thank you both, I was running 14,1, currently it's running on 16,1 (yes I've re-generated SMBIOS and all). igfxrpsc=1 made no difference, unfortunately. Would it make sense to test 14,4 if 16,1 made no difference?
 
Top