Jump to content
WarDoc

WhatEverGreen Support Topic

976 posts in this topic

Recommended Posts

Advertisement
2 minutes ago, zhengshiqi said:

Hi, I really appreciate this work. 

One question: in readme file of https://github.com/acidanthera/WhateverGreen, I see

  • -cdfon (and enable-hdmi20 property) to enable HDMI 2.0 patches

Does that mean I should have both -cdfon boot argument and inject enable-hdmi20 in IGPU properties?

 

No. Choose one of them. 

Share this post


Link to post
Share on other sites

Hi guys,

Is there a flag to set a display which is connected to the GPU using the DisplayPort to be detected as the main display?

I have two monitors and one of them have only one HDMI port and the other one has a one DisplayPort and two HDMIs. When I use HDMI cables I can change the priority of the display by swapping the cables but when I use both DP and HDMI cables the display which is connected to the HDMI is always being detected as the main display no matter what.

 

Is there a way to fix it?

 

Thanks in advance.

Share this post


Link to post
Share on other sites
2 hours ago, Cyberdevs said:

Hi guys,

Is there a flag to set a display which is connected to the GPU using the DisplayPort to be detected as the main display?

I have two monitors and one of them have only one HDMI port and the other one has a one DisplayPort and two HDMIs. When I use HDMI cables I can change the priority of the display by swapping the cables but when I use both DP and HDMI cables the display which is connected to the HDMI is always being detected as the main display no matter what.

 

Is there a way to fix it?

 

Thanks in advance.

Are you looking for the boot-display property as detailed here?

Share this post


Link to post
Share on other sites
8 minutes ago, scj312 said:

Are you looking for the boot-display property as detailed here?

No not the boot-display properties, I'm looking for the display detection after macOS is loaded.

 

P.S.

Thanks for the link though I might find my answer there.

Edited by Cyberdevs

Share this post


Link to post
Share on other sites
3 hours ago, Cyberdevs said:

Hi guys,

Is there a flag to set a display which is connected to the GPU using the DisplayPort to be detected as the main display?

I have two monitors and one of them have only one HDMI port and the other one has a one DisplayPort and two HDMIs. When I use HDMI cables I can change the priority of the display by swapping the cables but when I use both DP and HDMI cables the display which is connected to the HDMI is always being detected as the main display no matter what.

 

Is there a way to fix it?

 

Thanks in advance.

Is this what you are looking for ?

Seems too simple.

Share this post


Link to post
Share on other sites
2 hours ago, Cyberdevs said:

Nope that's not what I'm looking for. :D

That doesn't work either anyways.

 

Clearly I do not understand what you are trying to do. Sorry.:)

 

But linked article worked for me.

In Display preferences arrangement window, I can drag & drop the menu bar from the DP screen to the HDMI screen and it changes the main display to the HDMI screen. On reboot, the login screen is now always HDMI.

 

Share this post


Link to post
Share on other sites
17 hours ago, MacNB said:

Clearly I do not understand what you are trying to do. Sorry.:)

 

But linked article worked for me.

In Display preferences arrangement window, I can drag & drop the menu bar from the DP screen to the HDMI screen and it changes the main display to the HDMI screen. On reboot, the login screen is now always HDMI.

 

Yeah actually at first I thought the guide is for arranging displays which didn't work for me and after reading the whole article I realized that it's different than I though and it easily fixed the issue, thanks for the help :)

Share this post


Link to post
Share on other sites
3 minutes ago, Cyberdevs said:

Yeah actually at first I thought the guide is for arranging displays which didn't work for me and after reading the whole article I realized that it's different than I though and it easily fixed the issue, thanks for the help :)

Great. So I did understand what you were trying to do :D

Glad you fixed it.

Share this post


Link to post
Share on other sites

hey again,

 

any chance the kernelversion check of new AppleBacklightFixup- Feature in WG could get removed?!

 

if (kextBacklight.loadIndex == index) {
		const uint8_t find[]    = {"F%uT%04x"};
		const uint8_t replace[] = {"F%uTxxxx"};
		KernelPatcher::LookupPatch patch = {&kextBacklight, find, replace, sizeof(find), 1};
		if (getKernelVersion() >= KernelVersion::Sierra) {
			DBGLOG("weg", "applying backlight patch");
			patcher.applyLookupPatch(&patch);
		}
	}

This breaks the function in Yosemite and so on...

 

thx :D

 

Share this post


Link to post
Share on other sites

@vit9696 I was wondering if there is away to make WEG name the discrete GPU from GFX0 to GFX2 if using MacPro6,1 SMBIOS.  Nevermind I figured it out

Edited by Pavo

Share this post


Link to post
Share on other sites

@vit9696 Anyway to fix screen recording in Mojave when using MacPro6,1 SMBIOS? Console log shows:

GVA encoder error: Branch_Encoder1_AMD2, input format not supported

I noticed you have some patches for /System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/AppleGVA built into WEG. 

 

LOL, once again I figured it out, all I needed was shiki-id=Mac-7BA5B2D9E42DDD94 shikigva=33

Edited by Pavo

Share this post


Link to post
Share on other sites
13 hours ago, Pavo said:

@vit9696 I was wondering if there is away to make WEG name the discrete GPU from GFX0 to GFX2 if using MacPro6,1 SMBIOS.  Nevermind I figured it out

..and the solution was ?

10 hours ago, Pavo said:

@vit9696 Anyway to fix screen recording in Mojave when using MacPro6,1 SMBIOS? Console log shows:


GVA encoder error: Branch_Encoder1_AMD2, input format not supported

I noticed you have some patches for /System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/AppleGVA built into WEG. 

 

LOL, once again I figured it out, all I needed was shiki-id=Mac-7BA5B2D9E42DDD94 shikigva=33

Is that fix for your Vega or RX580 system ?

Share this post


Link to post
Share on other sites
4 hours ago, MacNB said:

..and the solution was ?

I didn't have to rename the device from GFX0 to GFX1 or GFX2. All I had to do was use an injector kext to add my vendor device to AGPM. If you look at the AGPM info.plist, the iMacPro1,1 board-id section has the AGPM settings for both Vega 56 and Vega 64. I copied those settings and just changed the device-id and it worked. I also used the same injector kext to make AGDP use the same policy that iMacPro1,1 uses for the AGPM.

<key>AGPM</key>
		<dict>
			<key>CFBundleIdentifier</key>
			<string>com.apple.driver.AGPM</string>
			<key>IOClass</key>
			<string>AGPMController</string>
			<key>IONameMatch</key>
			<string>AGPMEnabler</string>
			<key>IOProviderClass</key>
			<string>IOPlatformPluginDevice</string>
			<key>Machines</key>
			<dict>
				<key>Mac-F60DEB81FF30ACF6</key>
				<dict>
					<key>Vendor1002Device687f</key>
					<dict>
						<key>AGDCEnabled</key>
						<integer>1</integer>
						<key>Heuristic</key>
						<dict>
							<key>ID</key>
							<integer>-1</integer>
						</dict>
						<key>control-id</key>
						<integer>17</integer>
						<key>max-power-state</key>
						<integer>15</integer>
						<key>min-power-state</key>
						<integer>0</integer>
					</dict>
					<key>GFX1</key>
					<dict>
						<key>AGDCEnabled</key>
						<integer>1</integer>
						<key>Heuristic</key>
						<dict>
							<key>ID</key>
							<integer>-1</integer>
						</dict>
						<key>control-id</key>
						<integer>16</integer>
						<key>max-power-state</key>
						<integer>15</integer>
						<key>min-power-state</key>
						<integer>0</integer>
					</dict>
					<key>GFX2</key>
					<dict>
						<key>AGDCEnabled</key>
						<integer>1</integer>
						<key>Heuristic</key>
						<dict>
							<key>ID</key>
							<integer>-1</integer>
						</dict>
						<key>control-id</key>
						<integer>17</integer>
						<key>max-power-state</key>
						<integer>15</integer>
						<key>min-power-state</key>
						<integer>0</integer>
					</dict>
				</dict>
         </dict>
<dict>
		<key>AppleGraphicsDevicePolicy</key>
		<dict>
			<key>CFBundleIdentifier</key>
			<string>com.apple.driver.AppleGraphicsDevicePolicy</string>
			<key>Config4</key>
			<dict>
				<key>GFX0</key>
				<dict>
					<key>EDID</key>
					<dict>
						<key>index</key>
						<integer>0</integer>
					</dict>
					<key>FeatureControl</key>
					<integer>12</integer>
					<key>unload</key>
					<false/>
				</dict>
				<key>IGPU</key>
				<dict>
					<key>unload</key>
					<true/>
				</dict>
				<key>display</key>
				<dict>
					<key>EDID</key>
					<dict>
						<key>index</key>
						<integer>0</integer>
					</dict>
					<key>FeatureControl</key>
					<integer>12</integer>
					<key>unload</key>
					<false/>
				</dict>
			</dict>
			<key>ConfigMap</key>
			<dict>
				<key>Mac-F60DEB81FF30ACF6</key>
				<string>Config4</string>
			</dict>
			<key>IOClass</key>
			<string>AppleGraphicsDevicePolicy</string>
			<key>IOMatchCategory</key>
			<string>AppleGraphicsDevicePolicy</string>
			<key>IOProviderClass</key>
			<string>AppleGraphicsDeviceControl</string>
			<key>IOResourceMatch</key>
			<string>IOKit</string>
		</dict>
4 hours ago, MacNB said:

Is that fix for your Vega or RX580 system ?

This is for my Asus STRIX OC Radeon RX Vega 64. Looking at WEG source code under the Shiki section it explains how to enable hardware encoding/decoding for systems that don't have iGPU or have it disabled. Using these settings I was able to get hardware encoding/decoding working for my Vega 64. For me I am only enabling ForceOnlineRenderer, and ReplaceBoardID. So that would mean ForceOnlineRenderer = 1 and ReplaceBoardID = 32, 1+32=33, so.... shikigva=33 bootarg. Since I am also changing the board-id that Shiki will be using I also have to have shiki-id=Mac-7BA5B2D9E42DDD94 as bootarg.

private:
	// Aside generic DRM unlock patches, which are always on, Shiki also provides a set of patches
	// to workaround various issues with hardware video acceleration support.
	// These are set as a shikigva boot-arg bitmask.
	// For example, to enable ForceOnlineRenderer, ExecutableWhitelist, and ReplaceBoardID
	// you sum 1 + 8 + 32 = 41 -> and pass shikigva=41.
	enum ShikiGVAPatches {
		// Remove forceOfflineRenderer from AppleGVA Info.plist.
		// This is required to allow hardware acceleration on several mac models with discrete GPUs
		// when only IGPU is available.
		// See /System/Library/PrivateFrameworks/AppleGVA.framework/Resources/Info.plist for more details.
		ForceOnlineRenderer        = 1,
		// Remve hweBGRA from AppleGVA Info.plist.
		// hweBGRA is not supported by NVIDIA GPUs, so the patch is sometimes required when using NVIDIA
		// in a mac model meant to be used with AMD or Intel.
		// See /System/Library/PrivateFrameworks/AppleGVA.framework/Resources/Info.plist for more details.
		AllowNonBGRA               = 2,
		// Prior to 10.13.4 certain GPU+CPU combinations were not meant to provide hardware acceleration and had to be patched.
		// The overall problematic configuration list is: NVIDIA+BDW, NVIDIA+SKL, NVIDIA+KBL, AMD+IVB, NVIDIA+SNB.
		// Enabled automatically if shikigva is *NOT* passed on 10.13.3 and earlier. All are fixed in 10.13.4.
		ForceCompatibleRenderer    = 4,
		// Unlike 10.12.6 without security updates and earlier, on 10.13 and latest 10.12.6 AppleGVA patches
		// do not apply to all processes, and each process needs to be patched explicitly. This is a bug
		// in Lilu, which needs to be explored and fixed. For now this bit ensures that the processes present
		// in WHITELIST section of Patches.plist will definitely get the fixes even on 10.13 and 10.12.6.
		// On 10.12.6 and 10.13 this must be used if any of the following bits are used:
		// - ForceOnlineRenderer
		// - AllowNonBGRA
		// - ForceCompatibleRenderer
		// - ReplaceBoardID
		// - FixSandyBridgeClassName
		// It is enabled automatically on 10.12 and 10.13 if shikigva is *NOT* passed and ForceCompatibleRenderer or
		// FixSandyBridgeClassName are automatically enabled.
		AddExecutableWhitelist     = 8,
		DisabledUnused16           = 16,
		// Replace board-id used by AppleGVA by a different board-id.
		// Sometimes it is feasible to use different GPU acceleration settings from the main mac model.
		// By default Mac-27ADBB7B4CEE8E61 (iMac14,2) will be used, but you can override this via shiki-id boot-arg.
		// See /System/Library/PrivateFrameworks/AppleGVA.framework/Resources/Info.plist for more details.
		ReplaceBoardID             = 32,
		// Attempt to support fps.1_0 (FairPlay 1.0) in Safari.
		// This should technically fix some very old streaming services in Safari, which rely on FairPlay DRM
		// similar to the one found in iTunes. Newer streaming services require FairPlay 2.0, which is hardware-only,
		// so nothing could be done about them.
		// Another way to enable this is to pass -shikifps boot argument.
		UnlockFP10Streaming        = 64,
		DeprecatedUnused128        = 128
	};

 

Edited by Pavo

Share this post


Link to post
Share on other sites
2 hours ago, Pavo said:

I didn't have to rename the device from GFX0 to GFX1 or GFX2. All I had to do was use an injector kext to add my vendor device to AGPM. If you look at the AGPM info.plist, the iMacPro1,1 board-id section has the AGPM settings for both Vega 56 and Vega 64. I copied those settings and just changed the device-id and it worked. I also used the same injector kext to make AGDP use the same policy that iMacPro1,1 uses for the AGPM.


<key>AGPM</key>
		<dict>
			<key>CFBundleIdentifier</key>
			<string>com.apple.driver.AGPM</string>
			<key>IOClass</key>
			<string>AGPMController</string>
			<key>IONameMatch</key>
			<string>AGPMEnabler</string>
			<key>IOProviderClass</key>
			<string>IOPlatformPluginDevice</string>
			<key>Machines</key>
			<dict>
				<key>Mac-F60DEB81FF30ACF6</key>
				<dict>
					<key>Vendor1002Device687f</key>
					<dict>
						<key>AGDCEnabled</key>
						<integer>1</integer>
						<key>Heuristic</key>
						<dict>
							<key>ID</key>
							<integer>-1</integer>
						</dict>
						<key>control-id</key>
						<integer>17</integer>
						<key>max-power-state</key>
						<integer>15</integer>
						<key>min-power-state</key>
						<integer>0</integer>
					</dict>
					<key>GFX1</key>
					<dict>
						<key>AGDCEnabled</key>
						<integer>1</integer>
						<key>Heuristic</key>
						<dict>
							<key>ID</key>
							<integer>-1</integer>
						</dict>
						<key>control-id</key>
						<integer>16</integer>
						<key>max-power-state</key>
						<integer>15</integer>
						<key>min-power-state</key>
						<integer>0</integer>
					</dict>
					<key>GFX2</key>
					<dict>
						<key>AGDCEnabled</key>
						<integer>1</integer>
						<key>Heuristic</key>
						<dict>
							<key>ID</key>
							<integer>-1</integer>
						</dict>
						<key>control-id</key>
						<integer>17</integer>
						<key>max-power-state</key>
						<integer>15</integer>
						<key>min-power-state</key>
						<integer>0</integer>
					</dict>
				</dict>
         </dict>

<dict>
		<key>AppleGraphicsDevicePolicy</key>
		<dict>
			<key>CFBundleIdentifier</key>
			<string>com.apple.driver.AppleGraphicsDevicePolicy</string>
			<key>Config4</key>
			<dict>
				<key>GFX0</key>
				<dict>
					<key>EDID</key>
					<dict>
						<key>index</key>
						<integer>0</integer>
					</dict>
					<key>FeatureControl</key>
					<integer>12</integer>
					<key>unload</key>
					<false/>
				</dict>
				<key>IGPU</key>
				<dict>
					<key>unload</key>
					<true/>
				</dict>
				<key>display</key>
				<dict>
					<key>EDID</key>
					<dict>
						<key>index</key>
						<integer>0</integer>
					</dict>
					<key>FeatureControl</key>
					<integer>12</integer>
					<key>unload</key>
					<false/>
				</dict>
			</dict>
			<key>ConfigMap</key>
			<dict>
				<key>Mac-F60DEB81FF30ACF6</key>
				<string>Config4</string>
			</dict>
			<key>IOClass</key>
			<string>AppleGraphicsDevicePolicy</string>
			<key>IOMatchCategory</key>
			<string>AppleGraphicsDevicePolicy</string>
			<key>IOProviderClass</key>
			<string>AppleGraphicsDeviceControl</string>
			<key>IOResourceMatch</key>
			<string>IOKit</string>
		</dict>

This is for my Asus STRIX OC Radeon RX Vega 64. Looking at WEG source code under the Shiki section it explains how to enable hardware encoding/decoding for systems that don't have iGPU or have it disabled. Using these settings I was able to get hardware encoding/decoding working for my Vega 64.


private:
	// Aside generic DRM unlock patches, which are always on, Shiki also provides a set of patches
	// to workaround various issues with hardware video acceleration support.
	// These are set as a shikigva boot-arg bitmask.
	// For example, to enable ForceOnlineRenderer, ExecutableWhitelist, and ReplaceBoardID
	// you sum 1 + 8 + 32 = 41 -> and pass shikigva=41.
	enum ShikiGVAPatches {
		// Remove forceOfflineRenderer from AppleGVA Info.plist.
		// This is required to allow hardware acceleration on several mac models with discrete GPUs
		// when only IGPU is available.
		// See /System/Library/PrivateFrameworks/AppleGVA.framework/Resources/Info.plist for more details.
		ForceOnlineRenderer        = 1,
		// Remve hweBGRA from AppleGVA Info.plist.
		// hweBGRA is not supported by NVIDIA GPUs, so the patch is sometimes required when using NVIDIA
		// in a mac model meant to be used with AMD or Intel.
		// See /System/Library/PrivateFrameworks/AppleGVA.framework/Resources/Info.plist for more details.
		AllowNonBGRA               = 2,
		// Prior to 10.13.4 certain GPU+CPU combinations were not meant to provide hardware acceleration and had to be patched.
		// The overall problematic configuration list is: NVIDIA+BDW, NVIDIA+SKL, NVIDIA+KBL, AMD+IVB, NVIDIA+SNB.
		// Enabled automatically if shikigva is *NOT* passed on 10.13.3 and earlier. All are fixed in 10.13.4.
		ForceCompatibleRenderer    = 4,
		// Unlike 10.12.6 without security updates and earlier, on 10.13 and latest 10.12.6 AppleGVA patches
		// do not apply to all processes, and each process needs to be patched explicitly. This is a bug
		// in Lilu, which needs to be explored and fixed. For now this bit ensures that the processes present
		// in WHITELIST section of Patches.plist will definitely get the fixes even on 10.13 and 10.12.6.
		// On 10.12.6 and 10.13 this must be used if any of the following bits are used:
		// - ForceOnlineRenderer
		// - AllowNonBGRA
		// - ForceCompatibleRenderer
		// - ReplaceBoardID
		// - FixSandyBridgeClassName
		// It is enabled automatically on 10.12 and 10.13 if shikigva is *NOT* passed and ForceCompatibleRenderer or
		// FixSandyBridgeClassName are automatically enabled.
		AddExecutableWhitelist     = 8,
		DisabledUnused16           = 16,
		// Replace board-id used by AppleGVA by a different board-id.
		// Sometimes it is feasible to use different GPU acceleration settings from the main mac model.
		// By default Mac-27ADBB7B4CEE8E61 (iMac14,2) will be used, but you can override this via shiki-id boot-arg.
		// See /System/Library/PrivateFrameworks/AppleGVA.framework/Resources/Info.plist for more details.
		ReplaceBoardID             = 32,
		// Attempt to support fps.1_0 (FairPlay 1.0) in Safari.
		// This should technically fix some very old streaming services in Safari, which rely on FairPlay DRM
		// similar to the one found in iTunes. Newer streaming services require FairPlay 2.0, which is hardware-only,
		// so nothing could be done about them.
		// Another way to enable this is to pass -shikifps boot argument.
		UnlockFP10Streaming        = 64,
		DeprecatedUnused128        = 128
	};

 

 

Thanks.

On the encode issue on my i7-3770K + RX580, I've not had any joy (iMac13,2).

H.264 is fine playback and encode (but uses the CPU+IGPU).

HEVC hangs the system (very slugish forcing a reboot). I tried the changing just the Board-ID to different values in the SMBIOS but no joy.

I don't use Whatevergreen as it made no difference.

But I had not used the shiki-id= trick.

 

That board ID you used is for which system ?

 

 

Share this post


Link to post
Share on other sites
2 minutes ago, MacNB said:

 

Thanks.

On the encode issue on my i7-3770K + RX580, I've not had any joy (iMac13,2).

H.264 is fine playback and encode (but uses the CPU+IGPU).

HEVC hangs the system (very slugish forcing a reboot). I tried the changing just the Board-ID to different values in the SMBIOS but no joy.

I don't use Whatevergreen as it made no difference.

But I had not used the shiki-id= trick.

You should be able to disable iGPU and use RX 580 for encoding/decoding just fine. WhateverGreen is required for using shiki-id but you also have to use shikigva bootarg in order to pass the shiki-id bootarg.

 

5 minutes ago, MacNB said:

That board ID you used is for which system ?

 Mac-7BA5B2D9E42DDD94 is iMacPro1,1 board-id. The reason I chose it was because they come with Vega GPUs and do not have iGPUs. Now I could be wrong but I think you have to have working AGPM to get encoding/decoding working for the GPU. To check if you have working AGPM look at your IOReg. Check to see if you have this on your GPU:

Screenshot-2018-12-15-13-02-37.png

If you don't then you need to get AGPM working for the GPU prior to getting encoding/decoding working.

 

Share this post


Link to post
Share on other sites
12 minutes ago, Pavo said:

You should be able to disable iGPU and use RX 580 for encoding/decoding just fine. WhateverGreen is required for using shiki-id but you also have to use shikigva bootarg in order to pass the shiki-id bootarg.

 

 Mac-7BA5B2D9E42DDD94 is iMacPro1,1 board-id. The reason I chose it was because they come with Vega GPUs and do not have iGPUs. Now I could be wrong but I think you have to have working AGPM to get encoding/decoding working for the GPU. To check if you have working AGPM look at your IOReg. Check to see if you have this on your GPU:

Screenshot-2018-12-15-13-02-37.png

If you don't then you need to get AGPM working for the GPU prior to getting encoding/decoding working.

 

 

OK thx. Yes I have AGPM working:

 

1698476146_Screenshot2018-12-15at18_16_15.thumb.png.4d9553e37cc9cecbe0ad5b02969e3d0d.png

 

1523403980_Screenshot2018-12-15at18_15_16.thumb.png.6f3d7a1fde00d197c08d30e394171ea4.png

 

I'll try WEG and disabling IGPU then use board-id from iMac18,3 (Mac-BE088AF8C5EB4FA2) as it has a Radeon Pro 580 similar to RX580.

Share this post


Link to post
Share on other sites
7 minutes ago, MacNB said:

 

OK thx. Yes I have AGPM working:

 

1698476146_Screenshot2018-12-15at18_16_15.thumb.png.4d9553e37cc9cecbe0ad5b02969e3d0d.png

 

1523403980_Screenshot2018-12-15at18_15_16.thumb.png.6f3d7a1fde00d197c08d30e394171ea4.png

 

I'll try WEG and disabling IGPU then use board-id from iMac18,3 (Mac-BE088AF8C5EB4FA2) as it has a Radeon Pro 580 similar to RX580.

Make sure you use the same info from iMac18,3 AGPM settings because it looks like your GFX0 settings are not the same as iMac18,3 settings:

<key>Mac-BE088AF8C5EB4FA2</key>
	<dict>
		<key>Vendor1002Device67df</key>
			<dict>
				<key>AGDCEnabled</key>
				<integer>1</integer>
				<key>Heuristic</key>
			<dict>
				<key>ID</key>
				<integer>-1</integer>
			</dict>
				<key>control-id</key>
				<integer>17</integer>
				<key>max-power-state</key>
				<integer>15</integer>
				<key>min-power-state</key>
				<integer>0</integer>
			</dict>

 

Share this post


Link to post
Share on other sites
3 minutes ago, Pavo said:

Make sure you use the same info from iMac18,3 AGPM settings because it looks like your GFX0 settings are not the same as iMac18,3 settings:


<key>Mac-BE088AF8C5EB4FA2</key>
	<dict>
		<key>Vendor1002Device67df</key>
			<dict>
				<key>AGDCEnabled</key>
				<integer>1</integer>
				<key>Heuristic</key>
			<dict>
				<key>ID</key>
				<integer>-1</integer>
			</dict>
				<key>control-id</key>
				<integer>17</integer>
				<key>max-power-state</key>
				<integer>15</integer>
				<key>min-power-state</key>
				<integer>0</integer>
			</dict>

 

 

Good point. Will change that. Thx.

Share this post


Link to post
Share on other sites
On 12/10/2018 at 8:52 AM, Andres ZeroCross said:

I get black screen after wake from Sleep in Mojave 10.14.2

eGPU : Radeon RX580
macOS Version : Mojave 10.14.2

It wake from sleep with normal condition in previous mojave 10.14 and 10.14.1 include beta 10.14.2. But after update to public release 10.14.2 i get black screen after wake from sleep if i sleep for long time. If for short time, it wake normally from sleep.
I used Lilu.kext version 1.2.8 and WhateverGreen version 1.2.4 

 

Same issue here. Using a Vanilla install, on an Asus Z370-A II / i7-8700K, dGPU (not external, it's on motherboard) Sapphire RX580 Nitro+. Wake after short sleep ok, long sleep (don't know how long exactly to trigger issue) does not work (blank screen).

 

Also notice that sometimes after wake from sleep, that dGPU memory clock speed gets stock at 2000 MHz even though dGPU core clock speed throttles up and down ok. It's fixed if I change display resolution to something else and back again. Anyone seen that issue?

 

The RX580 in my setup is idling at around 47 degrees (it's fans are off, which I do like a lot), while CPU is at around 37 degrees C. The heat pipes are rather hot on the RX580, and so is the whole metal side of the card. I would love if it idled at lower temps. Much warmer than CPU tower heatsink (nh-d15s). What are you experience here? 

Edited by gimtudil

Share this post


Link to post
Share on other sites
33 minutes ago, gimtudil said:

 

Same issue here. Using a Vanilla install, on an Asus Z370-A II / i7-8700K, dGPU (not external, it's on motherboard) Sapphire RX580 Nitro+. Wake after short sleep ok, long sleep (don't know how long exactly to trigger issue) does not work (blank screen).

 

Also notice that sometimes after wake from sleep, that dGPU memory clock speed gets stock at 2000 MHz even though dGPU core clock speed throttles up and down ok. It's fixed if I change display resolution to something else and back again. Anyone seen that issue?

 

The RX580 in my setup is idling at around 47 degrees (it's fans are off, which I do like a lot), while CPU is at around 37 degrees C. The heat pipes are rather hot on the RX580, and so is the whole metal side of the card. I would love if it idled at lower temps. Much warmer than CPU tower heatsink (nh-d15s). What are you experience here? 

Would love to see a pic of (not external, it's on motherboard) Sapphire RX580 Nitro+.

Share this post


Link to post
Share on other sites
On 12/15/2018 at 3:04 PM, Pavo said:

I didn't have to rename the device from GFX0 to GFX1 or GFX2. All I had to do was use an injector kext to add my vendor device to AGPM. If you look at the AGPM info.plist, the iMacPro1,1 board-id section has the AGPM settings for both Vega 56 and Vega 64. I copied those settings and just changed the device-id and it worked. I also used the same injector kext to make AGDP use the same policy that iMacPro1,1 uses for the AGPM.


<key>AGPM</key>
		<dict>
			<key>CFBundleIdentifier</key>
			<string>com.apple.driver.AGPM</string>
			<key>IOClass</key>
			<string>AGPMController</string>
			<key>IONameMatch</key>
			<string>AGPMEnabler</string>
			<key>IOProviderClass</key>
			<string>IOPlatformPluginDevice</string>
			<key>Machines</key>
			<dict>
				<key>Mac-F60DEB81FF30ACF6</key>
				<dict>
					<key>Vendor1002Device687f</key>
					<dict>
						<key>AGDCEnabled</key>
						<integer>1</integer>
						<key>Heuristic</key>
						<dict>
							<key>ID</key>
							<integer>-1</integer>
						</dict>
						<key>control-id</key>
						<integer>17</integer>
						<key>max-power-state</key>
						<integer>15</integer>
						<key>min-power-state</key>
						<integer>0</integer>
					</dict>
					<key>GFX1</key>
					<dict>
						<key>AGDCEnabled</key>
						<integer>1</integer>
						<key>Heuristic</key>
						<dict>
							<key>ID</key>
							<integer>-1</integer>
						</dict>
						<key>control-id</key>
						<integer>16</integer>
						<key>max-power-state</key>
						<integer>15</integer>
						<key>min-power-state</key>
						<integer>0</integer>
					</dict>
					<key>GFX2</key>
					<dict>
						<key>AGDCEnabled</key>
						<integer>1</integer>
						<key>Heuristic</key>
						<dict>
							<key>ID</key>
							<integer>-1</integer>
						</dict>
						<key>control-id</key>
						<integer>17</integer>
						<key>max-power-state</key>
						<integer>15</integer>
						<key>min-power-state</key>
						<integer>0</integer>
					</dict>
				</dict>
         </dict>

<dict>
		<key>AppleGraphicsDevicePolicy</key>
		<dict>
			<key>CFBundleIdentifier</key>
			<string>com.apple.driver.AppleGraphicsDevicePolicy</string>
			<key>Config4</key>
			<dict>
				<key>GFX0</key>
				<dict>
					<key>EDID</key>
					<dict>
						<key>index</key>
						<integer>0</integer>
					</dict>
					<key>FeatureControl</key>
					<integer>12</integer>
					<key>unload</key>
					<false/>
				</dict>
				<key>IGPU</key>
				<dict>
					<key>unload</key>
					<true/>
				</dict>
				<key>display</key>
				<dict>
					<key>EDID</key>
					<dict>
						<key>index</key>
						<integer>0</integer>
					</dict>
					<key>FeatureControl</key>
					<integer>12</integer>
					<key>unload</key>
					<false/>
				</dict>
			</dict>
			<key>ConfigMap</key>
			<dict>
				<key>Mac-F60DEB81FF30ACF6</key>
				<string>Config4</string>
			</dict>
			<key>IOClass</key>
			<string>AppleGraphicsDevicePolicy</string>
			<key>IOMatchCategory</key>
			<string>AppleGraphicsDevicePolicy</string>
			<key>IOProviderClass</key>
			<string>AppleGraphicsDeviceControl</string>
			<key>IOResourceMatch</key>
			<string>IOKit</string>
		</dict>

This is for my Asus STRIX OC Radeon RX Vega 64. Looking at WEG source code under the Shiki section it explains how to enable hardware encoding/decoding for systems that don't have iGPU or have it disabled. Using these settings I was able to get hardware encoding/decoding working for my Vega 64. For me I am only enabling ForceOnlineRenderer, and ReplaceBoardID. So that would mean ForceOnlineRenderer = 1 and ReplaceBoardID = 32, 1+32=33, so.... shikigva=33 bootarg. Since I am also changing the board-id that Shiki will be using I also have to have shiki-id=Mac-7BA5B2D9E42DDD94 as bootarg.


private:
	// Aside generic DRM unlock patches, which are always on, Shiki also provides a set of patches
	// to workaround various issues with hardware video acceleration support.
	// These are set as a shikigva boot-arg bitmask.
	// For example, to enable ForceOnlineRenderer, ExecutableWhitelist, and ReplaceBoardID
	// you sum 1 + 8 + 32 = 41 -> and pass shikigva=41.
	enum ShikiGVAPatches {
		// Remove forceOfflineRenderer from AppleGVA Info.plist.
		// This is required to allow hardware acceleration on several mac models with discrete GPUs
		// when only IGPU is available.
		// See /System/Library/PrivateFrameworks/AppleGVA.framework/Resources/Info.plist for more details.
		ForceOnlineRenderer        = 1,
		// Remve hweBGRA from AppleGVA Info.plist.
		// hweBGRA is not supported by NVIDIA GPUs, so the patch is sometimes required when using NVIDIA
		// in a mac model meant to be used with AMD or Intel.
		// See /System/Library/PrivateFrameworks/AppleGVA.framework/Resources/Info.plist for more details.
		AllowNonBGRA               = 2,
		// Prior to 10.13.4 certain GPU+CPU combinations were not meant to provide hardware acceleration and had to be patched.
		// The overall problematic configuration list is: NVIDIA+BDW, NVIDIA+SKL, NVIDIA+KBL, AMD+IVB, NVIDIA+SNB.
		// Enabled automatically if shikigva is *NOT* passed on 10.13.3 and earlier. All are fixed in 10.13.4.
		ForceCompatibleRenderer    = 4,
		// Unlike 10.12.6 without security updates and earlier, on 10.13 and latest 10.12.6 AppleGVA patches
		// do not apply to all processes, and each process needs to be patched explicitly. This is a bug
		// in Lilu, which needs to be explored and fixed. For now this bit ensures that the processes present
		// in WHITELIST section of Patches.plist will definitely get the fixes even on 10.13 and 10.12.6.
		// On 10.12.6 and 10.13 this must be used if any of the following bits are used:
		// - ForceOnlineRenderer
		// - AllowNonBGRA
		// - ForceCompatibleRenderer
		// - ReplaceBoardID
		// - FixSandyBridgeClassName
		// It is enabled automatically on 10.12 and 10.13 if shikigva is *NOT* passed and ForceCompatibleRenderer or
		// FixSandyBridgeClassName are automatically enabled.
		AddExecutableWhitelist     = 8,
		DisabledUnused16           = 16,
		// Replace board-id used by AppleGVA by a different board-id.
		// Sometimes it is feasible to use different GPU acceleration settings from the main mac model.
		// By default Mac-27ADBB7B4CEE8E61 (iMac14,2) will be used, but you can override this via shiki-id boot-arg.
		// See /System/Library/PrivateFrameworks/AppleGVA.framework/Resources/Info.plist for more details.
		ReplaceBoardID             = 32,
		// Attempt to support fps.1_0 (FairPlay 1.0) in Safari.
		// This should technically fix some very old streaming services in Safari, which rely on FairPlay DRM
		// similar to the one found in iTunes. Newer streaming services require FairPlay 2.0, which is hardware-only,
		// so nothing could be done about them.
		// Another way to enable this is to pass -shikifps boot argument.
		UnlockFP10Streaming        = 64,
		DeprecatedUnused128        = 128
	};

 

 

So..let me get this right.

On your VEGA system, you have your SMBIOS model id set for MacPro6,1 but using iMacPro1,1 Board-ID bootarg shiki-id=Mac-7BA5B2D9E42DDD94; and injecting AGPM & AGDP kext for MacPro6,1 ?

Share this post


Link to post
Share on other sites
58 minutes ago, MacNB said:

 

So..let me get this right.

On your VEGA system, you have your SMBIOS model id set for MacPro6,1 but using iMacPro1,1 Board-ID bootarg shiki-id=Mac-7BA5B2D9E42DDD94; and injecting AGPM & AGDP kext for MacPro6,1 ?

I am using MacPro6,1 SMBIOS, injecting iMacPro1,1 as a Shiki board-Id and using a injector kext to make AGPM and AGDP use the iMacPro1,1 AGPM and AGDP settings instead of using MacPro6,1 AGPM and AGDP settings.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By headkaze
      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 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:
      - 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:
      $ ./gfxutil -f IGPU DevicePath = 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. More info can be found here.
       
      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:
      4    SandyBridge 5    IvyBridge 6    Haswell 7    Broadwell 8    Skylake 9    KabyLake 10   CoffeeLake 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 (desktop): 0x19120000 (default)
      - 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 (desktop): 0x59160000 (default)
      - 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)
      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
      framebuffer-conX-enable (required to enable below) framebuffer-conX-alldata 3. Find / Replace
      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
       
      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):
      log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot >weglog.txt 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 on applelife.ru
      - RehabMan for all data patching method, ioreg framebuffer dump and other contributions
       


    • By fantomas1
      Hi InsanelyMacaholics   

      Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS Sierra.
       
      10.12.6
      Nvidia Web Driver - 378.05.05.25f16 --> build 16G2016 (thanks to Cyberdevs) New!
      Nvidia Web Driver - 378.05.05.25f15 --> build 16G1918 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f14 --> build 16G1917 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f13 --> build 16G1815 (thanks to flowrider)
      Nvidia Web Driver - 378.05.05.25f12 --> build 16G1710 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f11 --> build 16G1618 (thanks to Frank Nitty)
      Nvidia Web Driver - 378.05.05.25f10 --> build 16G1510 (thanks to BreBo) 
      Nvidia Web Driver - 378.05.05.25f09 --> build 16G1408 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f08 --> build 16G1314 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f07 --> build 16G1314 (thanks to haring)
      Nvidia Web Driver - 378.05.05.25f06 --> build 16G1212 (thanks to WeBeRiO)
      Nvidia Web Driver - 378.05.05.25f04 --> build 16G1114 (thanks to lukazm)
      Nvidia Web Driver - 378.05.05.25f03 --> build 16G1036 (thanks to Gradou)
      Nvidia Web Driver - 378.05.05.25f01 --> build 16G29 (thanks to Badruzeus)
       
       
      10.12.5
      Nvidia Web Driver - 378.05.05.15f01 --> build 16F73 (see this post)
       
       
      10.12.4
      Nvidia Web Driver - 378.05.05.05f02 --> build 16E195(thanks to crachmaster4999)
      Nvidia Web Driver - 378.05.05.05f01 --> build 16E195 (thanks to Moviemakergr)  Pascal support!!!
      Nvidia Web Driver - 367.15.10.45f01 --> build 16E195 (thanks to Lanc)
       
       
      10.12.3

      Nvidia Web Driver - 367.15.10.35f01 --> build 16D32 (thanks to shatterhenner)
       
       
      10.12.2
      Nvidia Web Driver - 367.15.10.25f02 --> build 16C68 (see this post)
      Nvidia Web Driver - 367.15.10.25f01 --> build 16C67 (see this post)
      Nvidia Web Driver - 367.15.10.25b06 --> build 16C60b/16C63a (see this post)
       
       
      10.12.1
      Nvidia Web Driver - 367.15.10.15f03 --> build 16B2657/16B2659 (thanks to Moviemakergr).
      Nvidia Web Driver - 367.15.10.15f01 --> build 16B2555 (thanks to Moviemakergr)
       
       
      10.12.0
      Nvidia Web Driver - 367.15.10.05f01 --> build 16A323 (thanks to phi777)
       
       
      GM
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A323 (same driver since DP4/PB3)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A322 (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A320 (see this post)
       
       
      DP/PB
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A313a (DP8 & PB7) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A304a (DP7 & PB6) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A294a (DP6 & PB5) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A286a (DP5 & PB4) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A270f (DP4 & PB3) (thanks to TheRacerMaster)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A254g (DP3 & PB2) (see this post)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A238m (PB1) (thanks to Faun) 
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A239j (DP2) (thanks to Faun)
      Nvidia Web Driver - 367.05.10.05b03 --> build 16A201w (DP1) (thanks to Xmedik)
       
    • By fantomas1
      macOS Mojave 10.14.6 beta (18G29g)
    • By fantomas1
      This update:
      • Adds AirPlay 2 support for sharing videos, photos, music and more from your Mac directly to your AirPlay 2-enabled smart TV
      • Adds the ability to follow a magazine from the Apple News+ catalog browsing view
      • Includes support for the Reiwa (令和) era of the Japanese calendar
      • Improves audio latency on MacBook Pro models introduced in 2018
      • Fixes an issue that prevented certain very large OmniOutliner and OmniPlan documents from rendering properly
       
      Update
      Combo

      View full article
×