(Guide) Intel Framebuffer Patching Using WhateverGreen PDF

8/30/2019 [Guide] Intel Framebuffer patching using WhateverGreen | tonymacx86.
com
Contribute Log in Register 
 
Home  Post Installation  Graphics 
[Guide] Intel Framebuffer patching using WhateverGreen

 headkaze ·  Jul 17, 2018
1 of 96 Next  
headkaze
Jul 17, 2018  #1
Framebuffer patching in Mojave

Binary patching framebuffers using KextsToPatch in Clover is no longer a viable method in
Mojave for Skylake and above. Now you need to use Lilu + WhateverGreen.
Not just for Mojave

This method of framebuffer patching is not only required for Mojave we recommend it for all
previous and future releases of macOS.
Coffee Lake Users

Please note that the new WhateverGreen will not work with fake Kaby Lake platform-id's. You
will need to have either macOS 10.14 Beta 4 (18A336e) or newer or macOS High Sierra
10.13.6 (17G2112). The latter is a special build only available to MacBookPro15,1 or
MacBookPro15,2 board id's. You can create a macOS High Sierra 10.13.6 (17G2112) installer
by running installinstallmacos.py. (Update: vit9696 added back ability to fake Kaby Lake
platform-id's)
Lilu + WhateverGreen
WhateverGreen is going to replace all the other video patching plugins for Lilu (it currently has
merged WhateverGreen, IntelGraphicsFixup, NvidiaGraphicsFixup, Shiki and
CoreDisplayFixup). Others will likely follow (such as AppleALC, HibernationFixup and
IntelGraphicsDVMTFixup). This is aiming to be the all-in-one solution for video.
Preliminary
1. Remove:
https://www.tonymacx86.com/threads/guide-intel-framebuffer-patching-using-whatevergreen.256490/ 1/23
8/30/2019 [Guide] Intel Framebuffer patching using WhateverGreen | tonymacx86.com
- FakePCIID_Intel_HD_Graphics
- IntelGraphicsFixup
- NvidiaGraphicsFixup
- CoreDisplayFixup
- Shiki
2. Turn off all graphics injections in Clover:
- config.plist/Graphics/Inject/ATI=NO
- config.plist/Graphics/Inject/Intel=NO
- config.plist/Graphics/Inject/NVidia=NO
- config.plist/Graphics/ig-platform-id=
- config.plist/Devices/FakeID/IntelGFX=
3. Disable DSDT Clover fixes:

- AddHDMI
- FixDisplay
- FixIntelGfx
- AddIMEI
4. Disable UseIntelHDMI
5. Remove boot argument: -disablegfxfirmware
6. Remove any IGPU and HDMI entries from:
- config.plist/Devices/Arbitrary
- config.plist/Devices/Properties
- config.plist/Devices/AddProperties
7. Remove any IGPU and HDMI related SSDT and DSDT from:
- CLOVER/ACPI/patched
8. Renaming GFX0 -> IGPU
- WhateverGreen will do this automatically (see caveat below)
- Be aware that WhateverGreen does not rename all instances of GFX0 -> IGPU but should be
okay in most cases
- You may need to include Clover GFX0 -> IGPU rename for other kexts or ACPI patching that
require it
Compile Lilu + WhateverGreen

Download WhateverGreen. Make sure you place the debug version of Lilu into the root of
WhateverGreen before you compile. Install Lilu and WhateverGreen kext's into the usual
place. Compile WhateverGreen as debug if you want to view debug output.
Having trouble compiling?

If you're having trouble compiling you can download the official release binaries or download
my (unsupported) build_lilu.sh shell script and run it in a folder to download and build Lilu +
WhateverGreen using Xcode automatically. I recommend you try the debug versions first
(place them into Clover's EFI/Clover/kexts/Other folder).
Get the device path of your IGPU:

Download and use the gfxutil tool like so:
Code:
$ ./gfxutil
IGPU = PciRoot(0x0)/Pci(0x2,0x0)
ig-platform-id
For the AAPL,ig-platform-id (AAPL,snb-platform-id for Sandy Bridge) entry Clover requires
this value to be in Data format so you need to reverse the bytes. So if you want your
platform-id to be 0x3EA50009 first reverse the bytes (0900A53E) then use Xcode's plist editor
to add the values to Clover's config.plist.
What ig-platform-id should I use for my system?

You should choose one that is the closest match to your system. I recommend you do some
research on this before choosing one. See post #2 for available options.
You can determine the generation of your CPU by the first digit after the hyphen.
Examples:
- Intel(R) Core(TM) i5-2760QM (Gen 2)
- Intel(R) Core(TM) i7-5257U CPU @ 2.70GHz (Gen 5)
- Intel(R) Core(TM) m3-6Y30 (Gen 6)
- Intel(R) Core(TM) i5-8350U (Gen 8)
Spoofing Intel CPU Gen

If you need to spoof a different Intel CPU generation you can use the lilucpu=N boot flag.
The N refers to the following Intel generations:
Code:
4 Sandy Bridge
5 Ivy Bridge
6 Haswell
7 Broadwell
8 Skylake
9 Kaby Lake
10 Coffee Lake
To spoof a CPU you will need to set a valid device-id in your GPU entry in Devices/Properties
for the appropriate Intel generation.
Eg. Spoofing Skylake (lilucpu=8 boot flag with device-id=0x16190000), Kaby Lake (lilucpu=9
boot flag with device-id=0x12590000).
Here are some recommended frames:
Gen 2: Sandy Bridge (Intel HD Graphics 2000/3000)

- S/L/E/AppleIntelSNBGraphicsFB.kext
- Support started with OS X 10.7.x and ended with macOS 10.13.6
- Metal support is not available
- device-id: 0x0102 0x0106 0x010A 0x0112 0x0116 0x0122 0x0126
- AAPL,snb-platform-id (desktop): 0x00030010 (default)
- AAPL,snb-platform-id (laptop): 0x00010000 (default)
Gen 3: Ivy Bridge (Intel HD Graphics 2500/4000)

- S/L/E/AppleIntelFramebufferCapri.kext
- Support started with OS X 10.8.x
- device-id: 0x0152 0x0156 0x0162 0x0166
- AAPL,ig-platform-id (desktop): 0x0166000A (default), 0x01620005
- AAPL,ig-platform-id (laptop): 0x01660003 (default), 0x01660009, 0x01660004
Gen 4: Haswell (Intel HD Graphics 4200-5200)

- S/L/E/AppleIntelFramebufferAzul.kext
- Support started with OS X 10.9.x
- device-id: 0x0D26 0x0A26 0x0A2E 0x0D22 0x0412
- AAPL,ig-platform-id (desktop): 0x0D220003 (default)
- AAPL,ig-platform-id (laptop): 0x0A160000 (default), 0x0A260005 (recommended)
Gen 5: Broadwell (Intel HD Graphics 5300-6300)

- S/L/E/AppleIntelBDWGraphicsFramebuffer.kext
- Support started with OS X 10.10.2
- device-id: 0x0BD1 0x0BD2 0x0BD3 0x1606 0x160E 0x1616 0x161E 0x1626 0x1622 0x1612
0x162B
- AAPL,ig-platform-id (desktop): 0x16220007 (default)
- AAPL,ig-platform-id (laptop): 0x16260006 (default)
Gen 6: Skylake (Intel HD Graphics 510-580)

- S/L/E/AppleIntelSKLGraphicsFramebuffer.kext
- Support started with OS X 10.11.4
- device-id: 0x1916 0x191E 0x1926 0x1927 0x1912 0x1932 0x1902 0x1917 0x193B 0x191B
- AAPL,ig-platform-id (laptop): 0x19160000 (default)
Gen 7: Kaby Lake (Intel HD Graphics 610-650)

- S/L/E/AppleIntelKBLGraphicsFramebuffer.kext
- Support started with macOS 10.12.6
- device-id: 0x5912 0x5916 0x591B 0x591C 0x591E 0x5926 0x5927 0x5923 0x87C0
- AAPL,ig-platform-id (laptop): 0x591B0000 (default)
Gen 8: Coffee Lake (Intel UHD Graphics 630)

- S/L/E/AppleIntelCFLGraphicsFramebuffer.kext
- Support started with macOS 10.13.6 (17G2112) / 10.14 beta 4 (18A336e)
- device-id: 0x3E9B 0x3EA5 0x3EA6 0x3E92 0x3E91 0x3E98
- AAPL,ig-platform-id (desktop): 0x3EA50000 (default), 0x3E9B0007 (recommended)
- AAPL,ig-platform-id (laptop): 0x3EA50009 (default)
Framebuffer Patching
WhateverGreen does most of the work automatically for you and in most cases you do not
need any extra Framebuffer Patching. At the minimum though you should choose an ig-
platform-id suitable for your system and place it in config.plist/Devices/Properties like
this:
Here are some reasons why you might need extra Framebuffer Patching:
- Setting DVMT for those who can't set it above 32 MB in BIOS (framebuffer-stolenmem /
framebuffer-fbmem)
- Setting higher VRAM for 4K users who experience graphical glitches (framebuffer-
unifiedmem)
- Disabling eGPU (disable-external-gpu)
- Enable pixel clock patch for 4K support (enable-hdmi20)
- Disabling connectors to enable sleep (framebuffer-pipecount / framebuffer-portcount /
framebuffer-conX-type=-1)
- Removing CNConnectorAlwaysConnected flag for eDP laptop screens on < 10.13.6
(framebuffer-con0-flags=0x00000090)
- Changing connector types to match your systems ports (framebuffer-conX-type)
Framebuffer Patching Types

We have three different types of patches:
1. Arbitrary (Recommended)
Code:
framebuffer-patch-enable (required to enable below)

framebuffer-framebufferid (optional; defaults to current platform-id)
(all below are optional)
framebuffer-mobile
framebuffer-pipecount
framebuffer-portcount
framebuffer-memorycount
framebuffer-stolenmem
framebuffer-fbmem
framebuffer-unifiedmem
framebuffer-cursormem (Haswell only)
framebuffer-camellia
framebuffer-flags
framebuffer-conX-enable (required to enable below)

framebuffer-conX-index
framebuffer-conX-busid
framebuffer-conX-pipe
framebuffer-conX-type
framebuffer-conX-flags
2. All Data
Code:
framebuffer-conX-enable (required to enable below)

framebuffer-conX-alldata
3. Find / Replace
Code:
framebuffer-patchX-enable (required to enable below)

framebuffer-patchX-framebufferid (optional; defaults to current platform-id)
framebuffer-patchX-find
framebuffer-patchX-replace
framebuffer-patchX-count (optional; defaults to 1)
You should place your patches in config.plist/Devices/Properties in Clover config.plist.
Here are some example patches:

- 32MB BIOS, 19MB stolen (framebuffer) 9MB fbmem (cursor) 2048MB unifiedmem (vram)
- Pipe / Port Count 3 to 2

- Connector 1 DP to HDMI
- Connector 2 Disable
Here is an example of the All Data method:
Here is an example of the Find / Replace method:
Framebuffer Dumps
There are two ways to dump your framebuffer data (both require WhateverGreen + Lilu debug
versions):
1. Using -igfxdump boot flag to dump IGPU framebuffer kext to /AppleIntelFramebuffer_X_Y

(root of your boot drive)
There are several ways of reading this dump:

- Using 010 Editor along with the IntelFramebuffer.bt template
- Using Hackintool File->Open menu
2. Using -igfxfbdump boot flag to dump native and patched framebuffer table to ioreg at
IOService:/IOResources/WhateverGreen
There are several ways of reading this dump:

- Using dump_platformlist.sh shell script
- Using Hackintool File->Import->IOReg Dump menu
3. Using Hackintool Framebuffer->macOS 10.14 menu
Adjusting the brightness on a laptop

1. Method 1
Enable Clover DSDT fix AddPNLF. Enable SetIntelBacklight and SetIntelMaxBacklight. A
specific value is not necessary - it will be automatically injected according to the processor
installed.
2. Method 2
Use this ACPI table: SSDT-PNLF.dsl
Do not use both methods at the same time!
Digital Audio (HDMI / DVI / DP)

To enable digital audio it is necessary to set the necessary properties and, usually, patch the
connectors.
To enable audio in general and HDMI in particular use WEG along with AppleALC.kext.
On 10.10.5 and above, WEG automatically changes the connector-type of DP (00040000) to
HDMI (00080000) if no custom patches are used.
The actual connection may be of any type (HDMI / DVI / DP), but for the digital audio to
function the connector-type must explicitly be HDMI.
VGA support
In most cases with Intel Skylake and newer it works by default.
For Ivy Bridge and possibly other generations there are the options to patch your connectors
with the following:
06020000 02000000 30000000 // Option 1
06020000 01000000 30000000 // Option 2
On OS X 10.8.2 and newer it is impossible to have VGA on Ivy Bridge systems.
Hot-plugging VGA usually does not work.
In case this doesn't help - there are no other known solutions at this time.
EDID
EDID is usually correctly identified, so no actions are required. In rare cases, EDID needs to
be injected manually.
An EDID dump can be obtained, for example, with Linux. The correct EDID must be put into
*AAPL00,override-no-connect* property for IGPU, where the second 0 stands for the display
number.
In some cases the EDID dump may be incompatible with macOS and leads to distortions. For
some EDID in such cases you can use this script, which corrects a provided EDID and saves it
to your desktop.
HDMI in UHD resolution with 60 fps

Add the enable-hdmi20 property to IGPU, otherwise you will get a black screen. Or instead
of this property use the boot-arg -cdfon
Disablng a discrete graphics card

Add the disable-external-gpu property to IGPU. Or instead of this property, use the boot-
arg -wegnoegpu
Fix the invalid maximum link rate issue on some laptops (Dell XPS 15 9570, etc.)
Add the enable-dpcd-max-link-rate-fix property to IGPU, otherwise a kernel panic would
happen due to a division-by-zero. Or instead of this property, use the boot-arg -igfxmlr.
You could also manually specify a maximum link rate value via the dpcd-max-link-rate for
the builtin display.
Typically use 0x14 for 4K display and 0x0A for 1080p display.
All possible values are 0x06 (RBR), 0x0A (HBR), 0x14 (HBR2) and 0x1E (HBR3).
If an invalid value is specified, the default value 0x14 will be used instead.
If this property is not specified, same as above.
Fix the infinite loop on establishing Intel HDMI connections with a higher pixel clock
rate on Skylake, Kaby Lake and Coffee Lake platforms
Add the enable-hdmi-dividers-fix property to IGPU or use the -igfxhdmidivs boot
argument instead to fix the infinite loop when the graphics driver tries to establish a HDMI
connection with a higher pixel clock rate, for example connecting to a 2K/4K display with
HDMI 1.4, otherwise the system just hangs (and your builtin laptop display remains black)
when you plug in the HDMI cable.
1. General Notes
For those who want to have "limited" 2K/4K experience (i.e. 2K@59Hz or 4K@30Hz) with
their HDMI 1.4 port, you might find this fix helpful.
For those who have a laptop or PC with HDMI 2.0 routed to IGPU and have HDMI output
issues, please note that this fix is now succeeded by the LSPCON driver solution, and it is
still recommended to enable the LSPCON driver support to have full HDMI 2.0
experience.
(You might still need this fix temporarily to figure out the connector index of
your HDMI port. See the LSPCON section below.)
LSPCON driver support to enable DisplayPort to HDMI 2.0 output on IGPU
1. Brief Introduction
Recent laptops (Kaby Lake/Coffee Lake-based) are typically equipped with a HDMI 2.0 port.
This port could be either routed to IGPU or DGPU, and you can have a confirmation on
Windows 10. Intel (U)HD Graphics, however, does not provide native HDMI 2.0 output, so in
order to solve this issue OEMs add an additional hardware named LSPCON on the
motherboard to convert DisplayPort into HDMI 2.0.
LSPCON works in either Level Shifter (LS) or Protocol Converter (PCON) mode. When the
adapter works in LS mode, it is capable of producing HDMI 1.4 signals from DisplayPort, while
in PCON mode, it could provide HDMI 2.0 output. Some onboard LSPCON adapters (e.g. the
one on Dell XPS 15 9570) have been configured in the firmware to work in LS mode by
default, resulting a black screen on handling HDMI 2.0 connections.
Starting from version 1.3.0, WhateverGreen now provides driver support for the onboard
LSPCON by automatically configuring the adapter to run in PCON mode on new HDMI
connections, and hence solves the black screen issue on some platforms.
2. Before you start
LSPCON driver is only applicable for laptops and PCs with HDMI 2.0 routed to IGPU.
LSPCON driver is necessary for all newer platforms unless the new IGPU starts to provide
native HDMI 2.0 output.
Supported Intel Platform: Skylake, Kaby Lake, Coffee Lake and later.
Skylake Case: Intel NUC Skull Canyon; Iris Pro 580 + HDMI 2.0 with Parade PS175
LSPCON.
Coffee Lake Case: Some laptops, e.g. Dell XPS 15 9570, are equipped with HDMI 2.0 and
Parade PS175 LSPCON.
If you have confirmed that your HDMI 2.0 is routed to IGPU and is working properly right
now, you don't need to enable this driver, because your onboard LSPCON might already
be configured in the firmware to work in PCON mode.
3. Instructions
Add the enable-lspcon-support property to IGPU to enable the driver, or use the boot-
arg -igfxlspcon instead.
Next, you need to know the corresponding connector index (one of 0,1,2,3) of your
HDMI port. You could find it under IGPU in IORegistryExplorer. (i.e.
AppleIntelFramebuffer@0/1/2/3)
If you only have a 2K/4K HDMI monitor, you might need to enable the infinite
loop fix before connecting a HDMI monitor to your build, otherwise the system
just hangs, so you won't be able to run the IORegistryExplorer and find the
framebuffer index.
Add the framebuffer-conX-has-lspcon property to IGPU to inform the driver which

connector has an onboard LSPCON adapter.
Replace X with the index you have found in the previous step.
The value must be of type Data and should be one of 01000000 (True) and 00000000
(False).
(Optional) Add the framebuffer-conX-preferred-lspcon-mode property to IGPU to
specify a mode for your onboard LSPCON adapter.
The value must be of type Data and should be one of 01000000 (PCON, DP to HDMI
2.0) and 00000000 (LS, DP to HDMI 1.4).
Any other invalid values are treated as PCON mode.
If this property is not specified, the driver assumes that PCON mode is preferred.
4. Debugging
Once you have completed the steps above, rebuild the kext cache and reboot your computer.
After plugging into your HDMI 2.0 cable (and the HDMI 2.0 monitor), you should be able to
see the output on your monitor.
Dump your kernel log and you should also be able to see something simillar to lines below.
Code:
// When you insert the HDMI 2.0 cable

igfx @ (DBG) SC: GetDPCDInfo() DInfo: [FB0] called with controller at 0xffffff81a8680000 and fr
igfx @ (DBG) SC: GetDPCDInfo() DInfo: [FB0] No LSPCON chip associated with this framebuffer.
igfx @ (DBG) SC: GetDPCDInfo() DInfo: [FB0] Will call the original method.
igfx @ (DBG) SC: GetDPCDInfo() DInfo: [FB0] Returns 0x0.
igfx @ (DBG) SC: LSPCON::probe() DInfo: [FB2] Found the LSPCON adapter: Parade PS1750.
igfx @ (DBG) SC: LSPCON::probe() DInfo: [FB2] The current adapter mode is Level Shifter (DP++ to
igfx @ (DBG) SC: GetDPCDInfo() DInfo: [FB2] LSPCON driver has detected the onboard chip success
igfx @ (DBG) SC: GetDPCDInfo() DInfo: [FB2] LSPCON driver has been initialized successfully.
igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x00.
igfx @ (DBG) SC: LSPCON::setMode() DInfo: [FB2] The new mode is now effective.
igfx @ (DBG) SC: GetDPCDInfo() DInfo: [FB2] The adapter is running in preferred mode [Protocol
// When you remove the HDMI 2.0 cable

igfx @ (DBG) SC: GetDPCDInfo() DInfo: [FB0] No LSPCON chip associated with this framebuffer.
igfx @ (DBG) SC: GetDPCDInfo() DInfo: [FB2] LSPCON driver (at 0xffffff802ba3afe0) has already b
igfx @ (DBG) SC: LSPCON::setModeIfNecessary() DInfo: [FB2] The adapter is already running in Protoc
igfx @ (DBG) SC: LSPCON::wakeUpNativeAUX() DInfo: [FB2] The native AUX channel is up. DPCD Rev = 0x
Additionally, you can find these properties injected by the driver under the corresponding
framebuffer.
(Only available in DEBUG version)
fw-framebuffer-has-lspcon indicates whether the onboard LSPCON adapter exists or not.

fw-framebuffer-preferred-lspcon-mode indicates the preferred adapter mode. 1 is PCON,
and 0 is LS.
Debug Output
To get debug output from Lilu use the -liludbgall liludump=60 boot flags. You will need to
compile Lilu and WhateverGreen as debug for both of these flags to work. Log files should be
located at /var/log/Lilu_*.
To view debug paste the following into Terminal (weglog.txt will output to your
home directory):
Code:
log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessag
Getting Help
To help the users of this forum diagnose issues with your configuration please generate a Lilu
debug log and then run gen_debug.sh to generate a folder of debug files you can attach to a
forum post requesting help.
Credits
- vit9696 and lvs1974 for WhateverGreen (Full Credits) and Lilu (Full Credits)
- Andrey1970 for his guide
- RehabMan for all data patching method, ioreg framebuffer dump and other contributions
Attachments
FBPatch01.png FBPatch02.png
528.8 KB Views: 10,188 691.3 KB Views: 9,805
Last edited: Aug 20, 2019
BigTheta, SchmockLord, prana and 26 others
headkaze
Jul 18, 2018  #2
macOS High Sierra 10.13.6 (17G2112)

Sandy Bridge
Code:
0x00010000 (mobile, 4 connectors, no fbmem)

0x00030010 (desktop, 3 connectors, no fbmem)

ID: 00010000
TOTAL STOLEN: 0 bytes, TOTAL CURSOR: 1 MB, MAX STOLEN: 0 bytes, MAX OVERALL: 1 MB (1064960 bytes
GPU Name: Intel HD Graphics 3000
Model Name(s): MacBookPro8,1 MacBookPro8,2 MacBookPro8,3
Freq: 1808 Hz, FreqMax: 1808 Hz
Mobile: 1, PipeCount: 2, PortCount: 4, FBMemoryCount: 0
[5] busId: 0x03, pipe: 0, type: 0x00000002, flags: 0x00000030 - LVDS
[2] busId: 0x05, pipe: 0, type: 0x00000400, flags: 0x00000007 - DP
05030000 02000000 30000000
02050000 00040000 07000000
03040000 00040000 09000000
04060000 00040000 09000000
ID: 00020000
Model Name(s): MacBookPro8,3
05030000 02000000 30000000
ID: 00030010
Model Name(s): Macmini5,1 Macmini5,3
Freq: 0 Hz, FreqMax: -1 Hz

Ivy Bridge
Code:
0x01660000 (desktop, 4 connectors)

0x01660001 (mobile, 4 connectors)
0x0166000A (desktop, 3 connectors)
0x0166000B (desktop, 3 connectors)
ID: 01660000, STOLEN: 96 MB, FBMEM: 24 MB, VRAM: 1024 MB

TOTAL STOLEN: 24 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 72 MB, MAX OVERALL: 73 MB (7
Model Name(s):

01000000 02000000 30000000
02050000 00040000 07000000
03040000 00040000 07000000
04060000 00040000 07000000
ID: 01620006, STOLEN: 0 bytes, FBMEM: 0 bytes, VRAM: 256 MB

TOTAL STOLEN: 0 bytes, TOTAL CURSOR: 0 bytes, MAX STOLEN: 0 bytes, MAX OVERALL: 0 bytes
Model Name(s): Unknown
ID: 01620007, STOLEN: 0 bytes, FBMEM: 0 bytes, VRAM: 256 MB

TOTAL STOLEN: 0 bytes, TOTAL CURSOR: 0 bytes, MAX STOLEN: 0 bytes, MAX OVERALL: 0 bytes
F 1808 H F M 1808 H

Haswell
Code:
0x0C060000 (desktop, 3 connectors)

0x0D260000 (desktop, 3 connectors)
0x0A160000 (desktop, 3 connectors)
0x0A260000 (desktop, 3 connectors)
0x0A260005 (mobile, 3 connectors)
0x0A260006 (mobile, 3 connectors)
0x0A2E0008 (mobile, 3 connectors)
0x0A16000C (mobile, 3 connectors)
0x0D260007 (mobile, 4 connectors)
0x0D220003 (desktop, 3 connectors)
0x0A2E000A (desktop, 3 connectors)
0x0A26000A (desktop, 3 connectors)
0x0A2E000D (desktop, 2 connectors)
0x0A26000D (desktop, 2 connectors)
0x0412000B (desktop, 0 connectors, no fbmem)
0x0D260009 (mobile, 1 connectors)
0x0D26000E (mobile, 4 connectors)
0x0D26000F (mobile, 1 connectors)
ID: 0C060000, STOLEN: 64 MB, FBMEM: 16 MB, VRAM: 1024 MB, Flags: 0x00000004
TOTAL STOLEN: 209 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 209 MB, MAX OVERALL: 210 M
GPU Name: Intel Haswell GT1
Model Name(s):
Camelia: Disabled, Freq: 5273 Hz, FreqMax: 5273 Hz

[1] busId: 0x05, pipe: 9, type: 0x00000004, flags: 0x00000004 - DigitalDVI
[2] busId: 0x04, pipe: 9, type: 0x00000800, flags: 0x00000082 - HDMI
00000800 02000000 30000000
01050900 04000000 04000000
02040900 00080000 82000000
ID: 0C160000, STOLEN: 64 MB, FBMEM: 16 MB, VRAM: 1024 MB, Flags: 0x00000004

Broadwell
Code:

0x160E0000 (desktop, 3 connectors)
0x161E0000 (desktop, 3 connectors)
0x162B0000 (desktop, 3 connectors)
0x160E0001 (mobile, 3 connectors)
0x162B0002 (mobile, 3 connectors)
ID: 16060000, STOLEN: 16 MB, FBMEM: 15 MB, VRAM: 1024 MB, Flags: 0x00000B06
GPU Name: Intel Broadwell GT1
Model Name(s):
[1] busId: 0x05, pipe: 9, type: 0x00000004, flags: 0x00000004 - DigitalDVI
00000800 02000000 30020000
01050900 04000000 04000000
02040900 00080000 82000000
ID: 160E0000, STOLEN: 16 MB, FBMEM: 15 MB, VRAM: 1024 MB, Flags: 0x00000706
GPU Name: Intel Broadwell GT1

Skylake
Code:

0x191E0003 (mobile, 3 connectors, no fbmem)
0x193B0005 (mobile, 4 connectors, no fbmem)
ID: 191E0000, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000050F
TOTAL STOLEN: 56 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB
Model Name(s):
00000800 02000000 98000000
01050900 00040000 87010000
02040A00 00040000 87010000
ID: 19160000, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000090F
Model Name(s):
[0] busId: 0x00 pipe: 8 type: 0x00000002 flags: 0x00000098 LVDS

Kaby Lake
Code:


ID: 591E0000, STOLEN: 34 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000078B
Model Name(s): MacBook10,1
00000800 02000000 98000000
01050900 00040000 87010000
02040A00 00040000 87010000
ID: 59160000, STOLEN: 34 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00000B0B
Model Name(s): MacBookPro14,2
00000800 02000000 98000000
01050900 00040000 87010000

Coffee Lake
Code:
0x3EA50009 (mobile, 3 connectors, no fbmem)

0x3E9B0009 (mobile, 3 connectors, no fbmem)
0x3E9B0007 (desktop, 3 connectors, no fbmem)
ID: 3EA50009, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00830B0A
GPU Name: Intel Iris Plus Graphics 655
Model Name(s):
Camelia: V3
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000001C7 - DP
00000800 02000000 98000000
01050900 00040000 C7010000
02040A00 00040000 C7010000
ID: 3E920009, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0083130A
GPU Name: Intel UHD Graphics 630
Model Name(s):
Camelia: V3
[-1] busId: 0x00, pipe: 0, type: 0x00000001, flags: 0x00000020 - Dummy
[-1] busId: 0x00, pipe: 0, type: 0x00000001, flags: 0x00000020 - Dummy
00000800 02000000 98000000
FF000000 01000000 20000000
FF000000 01000000 20000000
ID: 3E9B0009, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0083130A

Cannon Lake
Code:
0x5A510009 (mobile, 3 connectors, no fbmem)

ID: 5A510009, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00A0070A
GPU Name: Intel Cannonlake GT2
Camelia: V3
00000800 02000000 98000000
01010900 00040000 C7090000
02020A00 00040000 C7090000
ID: 5A400009, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00A0070A
GPU Name: Unknown
Camelia: V3
00000800 02000000 98000000
01010900 00040000 C7090000

Ice Lake (LP)
Code:
0xFF050000 (mobile, 3 connectors, no fbmem)

0x8A5C0000 (mobile, 3 connectors, no fbmem)
0x8A5D0000 (mobile, 3 connectors, no fbmem)
0x8A5A0000 (mobile, 3 connectors, no fbmem)
0x8A5B0000 (mobile, 3 connectors, no fbmem)
ID: FF050000, STOLEN: 64 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00000602
GPU Name: Unknown
Camelia: Disabled
00000000 00000000 00000000 00000000 02000000 18000000
01000000 02000000 01000000 00000000 00040000 01020000
02000000 09000000 01000000 01000000 00040000 01020000
ID: 8A700000, STOLEN: 64 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0001000B
GPU Name: Unknown
Camelia: Disabled
00000000 00000000 00000000 00000000 02000000 18000000
01000000 02000000 01000000 00000000 00040000 01020000
02000000 09000000 01000000 01000000 00040000 01020000
GPU Name: Intel Ice Lake GT2
Camelia: Disabled

Ice Lake (HP)
Code:
0xFF050000 (mobile, 3 connectors, no fbmem)

ID: FF050000, STOLEN: 64 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00000602
GPU Name: Unknown

Camelia: Disabled
00000000 00000000 00000000 00000000 02000000 18000000
01000000 02000000 01000000 00000000 00040000 01020000
02000000 09000000 01000000 01000000 00040000 01020000
Camelia: Disabled
00000000 00000000 00000000 00000000 02000000 18000000
01000000 02000000 01000000 00000000 00040000 01020000
02000000 09000000 01000000 01000000 00040000 01020000
Camelia: Disabled
macOS 10.14 Beta 4 (18A336e)

Coffee Lake
Code:

0x3E9B0007 (desktop, 3 connectors, no fbmem)
0x3E920003 (desktop, 0 connectors, no fbmem)
ID: 3EA50009, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00830B0A
GPU Name: Intel Iris Plus Graphics 655 (0x3EA58086)
Model Name(s):
Camellia: V3
[0] busID: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - LVDS
[1] busID: 0x05, pipe: 9, type: 0x00000400, flags: 0x000001C7 - DP
[2] busID: 0x04, pipe: 10, type: 0x00000400, flags: 0x000001C7 - DP
00000800 02000000 98000000
01050900 00040000 C7010000
02040A00 00040000 C7010000
ID: 3E920009, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0083130A
GPU Name: Intel UHD Graphics 630 (0x3E928086)
Model Name(s):
Camellia: V3
[0] busID: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - LVDS
[-1] busID: 0x00, pipe: 0, type: 0x00000001, flags: 0x00000020 - Dummy
[-1] busID: 0x00, pipe: 0, type: 0x00000001, flags: 0x00000020 - Dummy
00000800 02000000 98000000
Last edited: May 17, 2019
prana, iwake, Outfield303 and 8 others
sherlocks
Jul 18, 2018  #3
EDIT.. thanks to vit9696

Last edited: Jul 18, 2018
anmool
Jul 18, 2018  #4
how can I get liludebug.kext I compiled succeeded lilu.kext but I cannot get liludebug.kext
into the lilu-master. only got release version shall I download debug version separately?
sherlocks
Jul 18, 2018  #5
EDIT1. thanks to vit9696. got it

Last edited: Jul 19, 2018
scottkendall
Jul 18, 2018  #6
headkaze said: 
Lilu + WhateverGreen
WhateverGreen is going to replace all the other video patching plugins for Lilu (it currently has merged
WhateverGreen, IntelGraphicsFixup, NvidiaGraphicsFixup, Shiki and CoreDisplayFixup). Others will likely
follow (such as AppleALC, HibernationFixup and IntelGraphicsDVMTFixup). This is aiming to be the all-in-
one solution for video.
This makes me sad because Watevergreen or another program causes hard freezes when
Whatevergreen is installed. I use Vegafixup on my main rig and I do not get the hard freezes,
maybe it has to do with the HDMI/DP Audio aspect of whatevergreen. Hopefully it does not
cause my Nvida/Kabby hack to start having hard freezes once they are all combined!
Build 1 : Z170A PC Mate | i5 6600K | Radeon RX Vega 56 Air Boost

Build 2 : ROG STRIX Z370-F GAMING | i5 8600K | RX 580 Pulse 8GB
Sniki
Moderator
Jul 19, 2018  #7
Should this apply for laptops as well ?
johnnync21
RehabMan
Moderator
Jul 19, 2018  #8
Sniki said: 
Should this apply for laptops as well ?
Yes, of course.
johnnync21 and Sniki
anmool
Jul 19, 2018  #9
Hi headkaze this patch didn't work my systdm

I installed mojave beta 1 installation fine but post installation i install latest whatevergreen
1.2.0+lilu 1.2.5 and other kext reboot didn't work kernel panic
I removed integraphicfix coredisplayfixup and shiki no luck
RehabMan
Moderator
Jul 19, 2018  #10
anmool said: 
Hi headkaze this patch didn't work my systdm

I installed mojave beta 1 installation fine but post installation i install latest whatevergreen 1.2.0+lilu
1.2.5 and other kext reboot didn't work kernel panic
I removed integraphicfix coredisplayfixup and shiki no luck
Keep in mind you must configure the kext patches correctly.

Contrary to post #1, I would use config.plist/Devices/AddProperties to set the required
properties that drive the patching.
1 of 96 Next   You must log in or register to reply here.
Share:        
Home  Post Installation  Graphics 
Forum Guides Downloads 

Search…
The Build Start Here! Downloads Albums
Search Installation 10.14 Index Shop
Post Installation DSDT CustoMac.com
Installation 10.13 Kexts MultiBeast.com
The Installation NVIDIA UniBeast.com
Workshop 10.12 Drivers
The Tools Installation Community
The 10.11 Software
Clubhouse Installation Archive
Infinite 10.10
Loop Installation
Laptops 10.9
Installation
10.8
Installation
10.7
Installation
10.6
Installation
Fix
iMessage
essage
Home Activity Rules Contact Us Contribute

    
Copyright © 2010 - 2019 tonymacx86 LLC
Privacy Policy Terms and Conditions Rules Top 

(Guide) Intel Framebuffer Patching Using WhateverGreen PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

(Guide) Intel Framebuffer Patching Using WhateverGreen PDF

Încărcat de

Drepturi de autor:

Formate disponibile

8/30/2019 [Guide] Intel Framebuffer patching using WhateverGreen | tonymacx86.

Contribute Log in Register 

Home  Post Installation  Graphics 

[Guide] Intel Framebuffer patching using WhateverGreen

Jul 17, 2018  #1

Framebuffer patching in Mojave

Not just for Mojave

Coffee Lake Users

3. Disable DSDT Clover fixes:

Compile Lilu + WhateverGreen

Having trouble compiling?

Get the device path of your IGPU:

What ig-platform-id should I use for my system?

Spoofing Intel CPU Gen

Here are some recommended frames:

Gen 2: Sandy Bridge (Intel HD Graphics 2000/3000)

- AAPL,snb-platform-id (laptop): 0x00010000 (default)

Gen 3: Ivy Bridge (Intel HD Graphics 2500/4000)

Gen 4: Haswell (Intel HD Graphics 4200-5200)

Gen 5: Broadwell (Intel HD Graphics 5300-6300)

Gen 6: Skylake (Intel HD Graphics 510-580)

Gen 7: Kaby Lake (Intel HD Graphics 610-650)

Gen 8: Coffee Lake (Intel UHD Graphics 630)

Framebuffer Patching Types

framebuffer-patch-enable (required to enable below)

framebuffer-conX-enable (required to enable below)

framebuffer-conX-enable (required to enable below)

framebuffer-patchX-enable (required to enable below)

You should place your patches in config.plist/Devices/Properties in Clover config.plist.

Here are some example patches:

- Pipe / Port Count 3 to 2

Here is an example of the All Data method:

Here is an example of the Find / Replace method:

1. Using -igfxdump boot flag to dump IGPU framebuffer kext to /AppleIntelFramebuffer_X_Y

There are several ways of reading this dump:

There are several ways of reading this dump:

3. Using Hackintool Framebuffer->macOS 10.14 menu

Adjusting the brightness on a laptop

Do not use both methods at the same time!

Digital Audio (HDMI / DVI / DP)

HDMI in UHD resolution with 60 fps

Disablng a discrete graphics card

LSPCON driver support to enable DisplayPort to HDMI 2.0 output on IGPU

2. Before you start

Add the framebuffer-conX-has-lspcon property to IGPU to inform the driver which

// When you insert the HDMI 2.0 cable

// When you remove the HDMI 2.0 cable

fw-framebuffer-has-lspcon indicates whether the onboard LSPCON adapter exists or not.

Last edited: Aug 20, 2019

BigTheta, SchmockLord, prana and 26 others

Jul 18, 2018  #2

macOS High Sierra 10.13.6 (17G2112)

0x00010000 (mobile, 4 connectors, no fbmem)

0x00030030 (desktop, 0 connectors, no fbmem)

macOS High Sierra 10.13.6 (17G2112)

0x01660000 (desktop, 4 connectors)

ID: 01660000, STOLEN: 96 MB, FBMEM: 24 MB, VRAM: 1024 MB

Freq: 1808 Hz, FreqMax: 1808 Hz

ID: 01620006, STOLEN: 0 bytes, FBMEM: 0 bytes, VRAM: 256 MB

ID: 01620007, STOLEN: 0 bytes, FBMEM: 0 bytes, VRAM: 256 MB

macOS High Sierra 10.13.6 (17G2112)

0x0C060000 (desktop, 3 connectors)

Mobile: 0, PipeCount: 3, PortCount: 3, FBMemoryCount: 3