Jump to content
WarDoc

WhatEverGreen Support Topic

976 posts in this topic

Recommended Posts

What could be that i need to do make this new "platform" i should move as developers moved here.. to get intel hd4600 working with this? I have fakeID on and DSDT injection of IGPU and Inject Intel ON and IntelGFX = 0x04128086.

 

 

What basic working setup could be? :):hammer:

Share this post


Link to post
Share on other sites
Advertisement

@vit9696 Was looking over your sample SSDT and not seeing anything that I could use to make a SSDT for my Vega 64 card, now WEG does name the device (GFX1) correctly in the IOReg but I was wanting to add properties using the example you have. Here is what my IOReg looks like using WEG for Vega 64. Any suggestion for making a SSDT to match its devices?

xS9wEOh.png

This is what I have came ups with, but most of it is not getting injected.

DefinitionBlock ("", "SSDT", 2, "Pavo", "GFX", 0x00000000)
{
    External (_SB_.PCI1.NPX3, DeviceObj)    // (from opcode)
    External (_SB_.PCI1.NPX3.BRG0, DeviceObj)    // (from opcode)

    Scope (\_SB.PCI1.NPX3)
    {
        Scope (BRG0)
        {
            Device (BRG1)
            {
                Name (_ADR, Zero)  // _ADR: Address
                Device (GFX1)
                {
                    Name (_ADR, Zero)  // _ADR: Address
                    Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                    {
                        Return (Package (0x18)
                        {
                            "built-in", 
                            Buffer (One)
                            {
                                 0x00                                           
                            }, 

                            "AAPL,slot-name", 
                            Buffer (0x07)
                            {
                                "Slot-1"
                            }, 

                            "model", 
                            Buffer (0x12)
                            {
                                "Radeon RX Vega 64"
                            }, 

                            "name", 
                            Buffer (0x08)
                            {
                                "ATY_GPU"
                            }, 

                            "@0,connector-type", 
                            Buffer (0x04)
                            {
                                 0x00, 0x04, 0x00, 0x00                         
                            }, 

                            "@1,connector-type", 
                            Buffer (0x04)
                            {
                                 0x00, 0x04, 0x00, 0x00                         
                            }, 

                            "@2,connector-type", 
                            Buffer (0x04)
                            {
                                 0x00, 0x04, 0x00, 0x00                         
                            }, 

                            "@3,connector-type", 
                            Buffer (0x04)
                            {
                                 0x00, 0x08, 0x00, 0x00                         
                            }, 

                            "PP_PhmSoftPowerPlayTable", 
                            Buffer (One)
                            {
                                /* 0000 */  0xB6, 0x02, 0x08, 0x01, 0x00, 0x5C, 0x00, 0xE1,
                                /* 0008 */  0x06, 0x00, 0x00, 0xEE, 0x2B, 0x00, 0x00, 0x1B,
                                /* 0010 */  0x00, 0x48, 0x00, 0x00, 0x00, 0x80, 0xA9, 0x03,
                                /* 0018 */  0x00, 0xF0, 0x49, 0x02, 0x00, 0x32, 0x00, 0x08,
                                /* 0020 */  0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                                /* 0028 */  0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02, 0x01,
                                /* 0030 */  0x5C, 0x00, 0x4F, 0x02, 0x46, 0x02, 0x94, 0x00,
                                /* 0038 */  0x9E, 0x01, 0xBE, 0x00, 0x28, 0x01, 0x7A, 0x00,
                                /* 0040 */  0x8C, 0x00, 0xBC, 0x01, 0x00, 0x00, 0x00, 0x00,
                                /* 0048 */  0x72, 0x02, 0x00, 0x00, 0x90, 0x00, 0xA8, 0x02,
                                /* 0050 */  0x6D, 0x01, 0x43, 0x01, 0x97, 0x01, 0xF0, 0x49,
                                /* 0058 */  0x02, 0x00, 0x71, 0x02, 0x02, 0x02, 0x00, 0x00,
                                /* 0060 */  0x00, 0x00, 0x00, 0x00, 0x08, 0x00, 0x00, 0x00,
                                /* 0068 */  0x00, 0x00, 0x00, 0x00, 0x05, 0x00, 0x07, 0x00,
                                /* 0070 */  0x03, 0x00, 0x05, 0x00, 0x00, 0x00, 0x00, 0x00,
                                /* 0078 */  0x00, 0x00, 0x01, 0x08, 0x20, 0x03, 0x84, 0x03,
                                /* 0080 */  0xB6, 0x03, 0xE8, 0x03, 0x1A, 0x04, 0x4C, 0x04,
                                /* 0088 */  0x7E, 0x04, 0xB0, 0x04, 0x01, 0x01, 0x46, 0x05,
                                /* 0090 */  0x01, 0x01, 0x84, 0x03, 0x00, 0x08, 0x60, 0xEA,
                                /* 0098 */  0x00, 0x00, 0x00, 0x40, 0x19, 0x01, 0x00, 0x01,
                                /* 00A0 */  0x80, 0x38, 0x01, 0x00, 0x02, 0xDC, 0x4A, 0x01,
                                /* 00A8 */  0x00, 0x03, 0x90, 0x5F, 0x01, 0x00, 0x04, 0x00,
                                /* 00B0 */  0x77, 0x01, 0x00, 0x05, 0x90, 0x91, 0x01, 0x00,
                                /* 00B8 */  0x06, 0x6C, 0xB0, 0x01, 0x00, 0x07, 0x01, 0x08,
                                /* 00C0 */  0xD0, 0x4C, 0x01, 0x00, 0x00, 0x00, 0x80, 0x00,
                                /* 00C8 */  0x00, 0x00, 0x00, 0x00, 0x00, 0x1C, 0x83, 0x01,
                                /* 00D0 */  0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                                /* 00D8 */  0x00, 0x00, 0x70, 0xA7, 0x01, 0x00, 0x02, 0x00,
                                /* 00E0 */  0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x88,
                                /* 00E8 */  0xBC, 0x01, 0x00, 0x03, 0x00, 0x00, 0x00, 0x00,
                                /* 00F0 */  0x00, 0x00, 0x00, 0x00, 0xC0, 0xD4, 0x01, 0x00,
                                /* 00F8 */  0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                                /* 0100 */  0x00, 0x44, 0x23, 0x02, 0x00, 0x05, 0x00, 0x00,
                                /* 0108 */  0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x58,
                                /* 0110 */  0x02, 0x00, 0x06, 0x00, 0x00, 0x00, 0x00, 0x01,
                                /* 0118 */  0x00, 0x00, 0x00, 0x18, 0x6D, 0x02, 0x00, 0x07,
                                /* 0120 */  0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00,
                                /* 0128 */  0x00, 0x05, 0x60, 0xEA, 0x00, 0x00, 0x00, 0x40,
                                /* 0130 */  0x19, 0x01, 0x00, 0x00, 0x80, 0x38, 0x01, 0x00,
                                /* 0138 */  0x00, 0xDC, 0x4A, 0x01, 0x00, 0x00, 0x90, 0x5F,
                                /* 0140 */  0x01, 0x00, 0x00, 0x00, 0x08, 0x28, 0x6E, 0x00,
                                /* 0148 */  0x00, 0x00, 0x2C, 0xC9, 0x00, 0x00, 0x01, 0xF8,
                                /* 0150 */  0x0B, 0x01, 0x00, 0x02, 0x80, 0x38, 0x01, 0x00,
                                /* 0158 */  0x03, 0x90, 0x5F, 0x01, 0x00, 0x04, 0xF4, 0x91,
                                /* 0160 */  0x01, 0x00, 0x05, 0xD0, 0xB0, 0x01, 0x00, 0x06,
                                /* 0168 */  0xC0, 0xD4, 0x01, 0x00, 0x07, 0x00, 0x08, 0x6C,
                                /* 0170 */  0x39, 0x00, 0x00, 0x00, 0x24, 0x5E, 0x00, 0x00,
                                /* 0178 */  0x01, 0xFC, 0x85, 0x00, 0x00, 0x02, 0xAC, 0xBC,
                                /* 0180 */  0x00, 0x00, 0x03, 0x34, 0xD0, 0x00, 0x00, 0x04,
                                /* 0188 */  0x68, 0x6E, 0x01, 0x00, 0x05, 0x08, 0x97, 0x01,
                                /* 0190 */  0x00, 0x06, 0xEC, 0xA3, 0x01, 0x00, 0x07, 0x00,
                                /* 0198 */  0x01, 0x68, 0x3C, 0x01, 0x00, 0x00, 0x01, 0x04,
                                /* 01A0 */  0x3C, 0x41, 0x00, 0x00, 0x00, 0x00, 0x00, 0x50,
                                /* 01A8 */  0xC3, 0x00, 0x00, 0x00, 0x00, 0x00, 0x80, 0x38,
                                /* 01B0 */  0x01, 0x00, 0x02, 0x00, 0x00, 0x24, 0x71, 0x01,
                                /* 01B8 */  0x00, 0x04, 0x00, 0x00, 0x01, 0x08, 0x00, 0x98,
                                /* 01C0 */  0x85, 0x00, 0x00, 0x40, 0xB5, 0x00, 0x00, 0x60,
                                /* 01C8 */  0xEA, 0x00, 0x00, 0x50, 0xC3, 0x00, 0x00, 0x01,
                                /* 01D0 */  0x80, 0xBB, 0x00, 0x00, 0x60, 0xEA, 0x00, 0x00,
                                /* 01D8 */  0x94, 0x0B, 0x01, 0x00, 0x50, 0xC3, 0x00, 0x00,
                                /* 01E0 */  0x02, 0x00, 0xE1, 0x00, 0x00, 0x94, 0x0B, 0x01,
                                /* 01E8 */  0x00, 0x40, 0x19, 0x01, 0x00, 0x50, 0xC3, 0x00,
                                /* 01F0 */  0x00, 0x03, 0x78, 0xFF, 0x00, 0x00, 0x40, 0x19,
                                /* 01F8 */  0x01, 0x00, 0x88, 0x26, 0x01, 0x00, 0x50, 0xC3,
                                /* 0200 */  0x00, 0x00, 0x04, 0x40, 0x19, 0x01, 0x00, 0x80,
                                /* 0208 */  0x38, 0x01, 0x00, 0x80, 0x38, 0x01, 0x00, 0x50,
                                /* 0210 */  0xC3, 0x00, 0x00, 0x05, 0x80, 0x38, 0x01, 0x00,
                                /* 0218 */  0xDC, 0x4A, 0x01, 0x00, 0xDC, 0x4A, 0x01, 0x00,
                                /* 0220 */  0x50, 0xC3, 0x00, 0x00, 0x06, 0x00, 0x77, 0x01,
                                /* 0228 */  0x00, 0x00, 0x77, 0x01, 0x00, 0x90, 0x5F, 0x01,
                                /* 0230 */  0x00, 0x50, 0xC3, 0x00, 0x00, 0x07, 0x90, 0x91,
                                /* 0238 */  0x01, 0x00, 0x90, 0x91, 0x01, 0x00, 0x00, 0x77,
                                /* 0240 */  0x01, 0x00, 0x50, 0xC3, 0x00, 0x00, 0x01, 0x18,
                                /* 0248 */  0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0B,
                                /* 0250 */  0xE4, 0x12, 0xE8, 0x03, 0x60, 0x09, 0x3C, 0x00,
                                /* 0258 */  0x0A, 0x00, 0x54, 0x03, 0x90, 0x01, 0x90, 0x01,
                                /* 0260 */  0x90, 0x01, 0x90, 0x01, 0x90, 0x01, 0x90, 0x01,
                                /* 0268 */  0x90, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02,
                                /* 0270 */  0x08, 0x31, 0x07, 0xDC, 0x00, 0xDC, 0x00, 0xDC,
                                /* 0278 */  0x00, 0x2C, 0x01, 0x00, 0x00, 0x59, 0x00, 0x69,
                                /* 0280 */  0x00, 0x4A, 0x00, 0x4A, 0x00, 0x5F, 0x00, 0x73,
                                /* 0288 */  0x00, 0x73, 0x00, 0x64, 0x00, 0x40, 0x00, 0x90,
                                /* 0290 */  0x92, 0x97, 0x60, 0x96, 0x00, 0x90, 0x55, 0x00,
                                /* 0298 */  0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                                /* 02A0 */  0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                                /* 02A8 */  0x02, 0x02, 0xD4, 0x30, 0x00, 0x00, 0x02, 0x10,
                                /* 02B0 */  0x60, 0xEA, 0x00, 0x00, 0x02, 0x10             
                            }, 

                            "hda-gfx", 
                            Buffer (0x0A)
                            {
                                "onboard-2"
                            }, 

                            "PP_DisablePowerContainment", 
                            Buffer (One)
                            {
                                 0x01                                           
                            }, 

                            "PP_FuzzyFanControl", 
                            Buffer (One)
                            {
                                 0x00                                           
                            }
                        })
                    }
                }

                Device (HDAU)
                {
                    Name (_ADR, One)  // _ADR: Address
                    Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                    {
                        Return (Package (0x0A)
                        {
                            "built-in", 
                            Buffer (One)
                            {
                                 0x00                                           
                            }, 

                            "AAPL,slot-name", 
                            Buffer (0x07)
                            {
                                "Slot-1"
                            }, 

                            "name", 
                            Buffer (0x1B)
                            {
                                "Radeon RX Vega 64 HD-Audio"
                            }, 

                            "model", 
                            Buffer (0x1B)
                            {
                                "Radeon RX Vega 64 HD-Audio"
                            }, 

                            "hda-gfx", 
                            Buffer (0x0A)
                            {
                                "onboard-2"
                            }
                        })
                    }
                }
            }
        }
    }
}

 

Edited by Pavo

Share this post


Link to post
Share on other sites

The SSDT example is quite outdated. Now that Clover finally supports injecting device properties in a simple form via Properties in config.plist, you are supposed to stop using ACPI and use device properties similarly to Apple.

 

Yet, if you still want to inject device properties via ACPI, you should use the original name of your GPU, as WhateverGreen only renames the macOS internal device name, preserving ACPI intact and avoiding many issues people cause by attempting to edit or patch their ACPI tables.

 

Also, what you try to inject is utter nonsense, good for you it failed. PP overrides should be named as PP,PP_… and I do not think the connector fields even work like this. And slots/models for HDAU is logically insane.

Edited by vit9696

Share this post


Link to post
Share on other sites
6 hours ago, vit9696 said:

The SSDT example is quite outdated. Now that Clover finally supports injecting device properties in a simple form via Properties in config.plist, you are supposed to stop using ACPI and use device properties similarly to Apple.

 

Yet, if you still want to inject device properties via ACPI, you should use the original name of your GPU, as WhateverGreen only renames the macOS internal device name, preserving ACPI intact and avoiding many issues people cause by attempting to edit or patch their ACPI tables.

 

Also, what you try to inject is utter nonsense, good for you it failed. PP overrides should be named as PP,PP_… and I do not think the connector fields even work like this. And slots/models for HDAU is logically insane.

Appreciate your feedback and will try out Properties in config.plist

Share this post


Link to post
Share on other sites
On 8/1/2018 at 9:20 AM, xelanaiznac said:

 

thank you Pavo. I found out that if I use vega64, my hardware acceleration is fully supported.

as soon as I put my Nvidia gtx 1080, I have the error as picture

this happens on my x99 and on my x299 config (tried in both systems).

 

no issue with my z370 with both amd or nvidia

1127714983_Schermata2018-08-01alle09_10_27.png.f8319c051e63cf93433d3a6c56582a61.png

 

 

hi guys, any idea? @vit9696 @Pavo

Share this post


Link to post
Share on other sites

Hello,

 

Could somebody help me ?

I'm on High Sierra 10.13.6

I have a Vapor-X Radeon HD 5770 (Vervet framebuffer).

I can only boot with kext/other -->lilu+whatervergreen+fakesmc, and with the boot arg -radvesa

 

Could someone kindly tell me what clover config should I put ? (or boot args or additionnal kext in SLE or other?)

 

Thanks and have a good day,

 

Share this post


Link to post
Share on other sites

Is there any way to let WEG automatically set everything correctly as well in high Sierra and not just by default if you use Mojave ? For example if we use the new MacBook pro special macos version, we also have the newly implemented coffee lake stuff in there... @vit9696

Edited by DSM2

Share this post


Link to post
Share on other sites

Hello,

 

I recently updated to 10.13.6, and with it I updated all my Kext to the last version, however, I'm getting a pink/magenta tint on my second display. I have been playing around both multiple configurations and I haven't been able to remove it.

 

So far:

  • Older versions of Kexts: Gave black screen
  • Newer WhateverGreen with latest Shiki, and Lilu: kernel panic, and reboot (even when setting the no reboot option on clover)
  • Newer versions, disable Whatevergreen: Pink/Magenta tint
  • Newer versions, disable IntelFixup, and Shiki: Pink/Magenta tint.

Mac seems to recognize correctly my Graphic Card: MSI RX 560 AERO ITX 4G OC

 

Any help would be great!

image.png

Share this post


Link to post
Share on other sites

Is there a solution to get the internal display working with a kaby lake HD 620 and an eDP connector on mojave? Currently only backlight works. i found a workaround is to use SKL intelgfx and ig-platform-id but that's only a workaround because i get rare glitches that i don't have with KBL framebuffer.

 

I tried turning off CNConnectorAlwaysConnected but then the screen was all black, not even brightness works.

Edited by JHeartyP

Share this post


Link to post
Share on other sites

with last version of this amazing plugin is it possible to run both discrete gpu (intel + nvidia) on kabylake cpu? Or at least turn off intel and use nvidia instead?

Thanx

Share this post


Link to post
Share on other sites

i9 7980XE, Geforce 1080ti + 1080ti + 1080

Web Driver 378.10.10.10.25.106

10.13.5

HDMI output

 

Whatevergreen 1.2 + Lilu 1.2.5 always result in random kernel panic (TIMED-OUT WAITING FOR NMI-ACK, PROCEEDING).

Have to remove Whatevergreen to ensure stability.

 

What's the possible solution? My system will run without problems in the absence of Whatevergreen but I'm just curious about this.

(Also with 387 drivers OpenGL won't work at all on my system, have to stay at 378)

 

Edited by N01r

Share this post


Link to post
Share on other sites
1 hour ago, norton287 said:

What is the exact syntax in Clover to use the enableHDMI20 setting to have working HDMI audio on my card.

HDMI20 setting isn't for audio, it too support HDMI 2.0 protocol in order to allow 60+Hz frequency for monitors that support 60+Hz frequency. macOS has only supported 30Hz frequency for HDMI until Mojave (10.14).  So in order to be able to use HDMI above 30Hz frequency on your monitor in say High Sierra you would need a GPU that supports HDMI 2.0 and that bootflag enabled for WhateverGreen in order to allow HDMI for 60+Hz frequency.

Edited by Pavo

Share this post


Link to post
Share on other sites

hi guys. very strange issue here.

I put here the link with a short video. https://mega.nz/#!1AA1nQRA!HEOtRSXE-p9ZPnpCN8AC_NsvBzM0614iKdrzV26JDg4

 

so the issue is this:

I am on 10.13.6.

with my Vega 64 liquid (and even with air version) I can't turn on my projector (linked to Onkyo receiver) because it gives me intermittent signal.

no issue with same setup and gtx 1080/1080 ti

if I remember well, I have no issue in the past with older version of lily and whatever green + shiki.

any idea? any help?

 

edit: just tried with weg 1.7, same situation

edit 2: tried without weg, same situation

Edited by xelanaiznac

Share this post


Link to post
Share on other sites
6 hours ago, bronxteck said:

try shorter cables to the projector or shielded type cables.

thank you, but this is not the solution.

with my cables, everything is working if I plug it into my MacBook Pro or if I plug it into hack with Nvidia.

 

now I have just tried to connect the projector directly into vega (so monitor + projector) and everything is working.

i have the issue when I connect the projector to av receiver and and then connecting av receiver to Vega (av receiver mandatory for the 7.1 audio)

so it's not the hdmi cable between projector and hack the issue.

tried using hdmi to display port from av receiver to vega, nothing changed

I tried replacing hdmi short cable between av receiver and Vega, nothing changes. now I'm going to try with rx 580 8gb to see what happen

 

 

edit: further data.

no issue with rx 580 8gb (as with 1080ti)

so the issue is related to Vega 64

 

just tried with Vega 64 and windows, everything is working. 

so no cable related, no av receiver related.

 

my conclusion is that it is related to Vega 64 osx driver of 10.13.6 because with or without weg nothing changes

 

@Pavo @vit9696 any idea?

 

nb just to be sure, I just updated the av firmware receiver...nothing changed

 

further data:

Just tried to put my Vega 64 into my x299(iMac pro 1,1) hack (yes, I have a lot of hardware here). no smbios related or platform related

hope you have all the informations needed

 

Edited by xelanaiznac

Share this post


Link to post
Share on other sites
On 8/5/2018 at 11:30 PM, kennyeni said:

Hello,

 

I recently updated to 10.13.6, and with it I updated all my Kext to the last version, however, I'm getting a pink/magenta tint on my second display. I have been playing around both multiple configurations and I haven't been able to remove it.

 

So far:

  • Older versions of Kexts: Gave black screen
  • Newer WhateverGreen with latest Shiki, and Lilu: kernel panic, and reboot (even when setting the no reboot option on clover)
  • Newer versions, disable Whatevergreen: Pink/Magenta tint
  • Newer versions, disable IntelFixup, and Shiki: Pink/Magenta tint.

Mac seems to recognize correctly my Graphic Card: MSI RX 560 AERO ITX 4G OC

 

Any help would be great!

 

 

As detailed in this official post  Coredisplayfixup, Shiki and IntelFixup are now all depreciated as those functions are now merged with Whatevergren.

If you read the latest realise notes for Whatevergreen it specifically states that use of those kexts in-conjunction with Whatevergreen will result in KP's and display issues.

 

Delete them and just use the latest builds of Lilu + Whatevergreen.

 

Cheers

Jay

Share this post


Link to post
Share on other sites

Both Whatevergreen v1.2.0 and 1.2.1 caused my system to restart towards the end of the OS boot sequence (kernel panic?), just before the log in screen should appear. I noted what the release notes said about merging Shiki with Whatevergreen, and Jay's post above, so I tried removing the Shiki and IntelGraphicsFixUp kexts and using the latest Whatevergreen kext and it worked. Cheers.

Share this post


Link to post
Share on other sites

Hey guys

 

I finally got around to replacing NvidiaGraphicsFixup with WEG on my desktop hackingtosh system:

 

Specs:

 

ASRock Z97 Extreme 6 Motherboard

i7-4790K CPU / 16 GB RAM

Gigabyte's GT 980 Ti Extreme WaterForce GPU

LG 21:9 Monitor connected via DP

MacOS 10.13.6 with Nvidia WebDrivers Installed ( 287.10.10.10.40.105) Which is the current release according to the Nvidia Driver Manager

Using iMac 13,2 System Definition

 

All 3rd party kext's installed in /L/E

 

Unfortunately the system KP's (bootloop) with Whatevergreen installed (ver 1.2.1) + Lilu 1.2.6 and yes i removed  NvidiaGraphicsFixup, i do not have Shiki installed.

 

I tried the previous versions lilu V 1.2.5 + WEG 1.2.0 but same result (KP)

 

After removing the Whatevergreen kext the system boots fine,

Reinstalled NvidiaGraphicsFixup (V 1.2.7) with Lilu 1.2.6 and system still boots ok.

 

I read that a few other users also had issues with WEG + Nvidia GPU, but was not clear on what the solution was.

 

Whilst the system is running fine with Lilu + NvidiaGraphicsFixup i would like to get to the bottom of the issue as NvidiaGraphicsFixup is no longer being maintained and at some point would like to update to Mojave which will require the use of Whatevergreen. I'm using Whatevergreen with no problems on my laptop and other mini hacks without any issues but they all have Intel IGPU only.

 

Any advice or possible way forward much appreciated

 

Cheers

Jay

 

Update: Found the issue .... rouge copy of NvidiaGraphicsFixup found in Clovers Kexts Folder .. my bad

 

 

 

Edited by jaymonkey

Share this post


Link to post
Share on other sites
18 minutes ago, jaymonkey said:

Hey guys

 

I finally got around to replacing NvidiaGraphicsFixup with WEG on my desktop hackingtosh system:

 

Specs:

 

ASRock Z97 Extreme 6 Motherboard

i7-4790K CPU / 16 GB RAM

Gigabyte's GT 980 Ti Extreme WaterForce GPU

LG 21:9 Monitor connected via DP

MacOS 10.13.6 with Nvidia WebDrivers Installed ( 287.10.10.10.40.105) Which is the current release according to the Nvidia Driver Manager

 

All 3rd party kext's installed in /L/E

 

Unfortunately the system KP's (bootloop) with Whatevergreen installed (ver 1.2.1) + Lilu 1.2.6 and yes i removed  NvidiaGraphicsFixup, i do not have Shiki installed.

 

I tried the previous versions lilu V 1.2.5 + WEG 1.2.0 but same result (KP)

 

After removing the Whatevergreen kext the system boots fine,

Reinstalled NvidiaGraphicsFixup (V 1.2.7) with Lilu 1.2.6 and system still boots ok.

 

I read that a few other users also had issues with WEG + Nvidia GPU, but was not clear on what the solution was.

 

Whilst the system is running fine with Lilu + NvidiaGraphicsFixup i would like to get to the bottom of the issue as NvidiaGraphicsFixup is no longer being maintained and at some point would like to update to Mojave which will require the use of Whatevergreen. I'm using Whatevergreen with no problems on my laptop and other mini hacks without any issues but they all have Intel IGPU only.

 

Any advice or possible way forward much appreciated

 

Cheers

Jay

 

 

 

Have you tried compiling the latest comments yourself? There are quite alot of fixes from the release to latest comments.

Share this post


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

Have you tried compiling the latest comments yourself? There are quite alot of fixes from the release to latest comments.

 

Whatevergreen 1.2.1 + Lilu 1.2.6 was just released today ... includes all recent commits

Edited by jaymonkey

Share this post


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

 

Whatever green 1.2.6 was just released today ... includes all recent commits

Where are you seeing this release? I am looking at the github page right now and the latest release shown there is still 1.2.1. I am assuming you meant Lilu 1.2.6.

Edited by Pavo

Share this post


Link to post
Share on other sites

Hi Support Team (WhatEverGreen or Shiki)

I can't play DRM-protected video on iTunes. iTunes shows black screen and stops position of playing marker at '0'.

Here is my spec:

NVIDIA Geforce 1060 GTX

Intel i5 8400 + UHD 630

 

I have turned on iGPU + Discrete GPU setting on BIOS and seems to work on playing video using iina with hw-decoder perfectly (Imgur)
I also checked VDA Decoder if working using VDADecoderChecker and, it shows 'Intel plugin detected. HW Decoder is fully working' (Imgur)

I try to make it work with the following: I installed the kext WhateverGreen.kext and set boot args with shikigva=12.
Force AppleGVA to use Intel or Nvidia decoder and reset DRM But none of them makes it to work.

It still doesn't work. How do I work on it? Thanks!

Edited by awert_65

Share this post


Link to post
Share on other sites

With Intel HD 630, it works perfectly for the stock resolutions. But while I could get 1920x1080 at 60Hz in HiDPI with Shiki, IntelGraphicsFixUp; I can't get more than 30Hz in HiDPI with Whatevergreen. Wonder if I am missing a setting.

 

EDIT
nvm - should've read more carefully. Sheesh 12 years of Hackintosh'ing and I still don't RTFM.

Edited by laatmaarzien
Figured it out.

Share this post


Link to post
Share on other sites

With the latest WhateverGreen1.2.1 there is no use in CoreDisplay Fix with high resolution support.

 

I downgrade the WhateverGreen to 1.2.0 and get the CDF Patched support again.

 

Or i tried to add CDF + WhateverGreen1.2.1 together and it works well.

 

So i confim the WhateverGreen1.2.1 have problem in CDF patches.

 

Thanks for your and i hope the new release.

 

Thnaks more.

 

 

Update:

Now i tried to add bootarg with [-cdfon] and the cdf patch come back and works well.

But it was juest said this was a HDMI2.0 Patches.

Or it was disabled the whole CDF patched include high resolution cdf patch by default now?

 

HDMI2.0 disabled by default and i think the cdf for high resolution patch may enable by default and this two function with no confict.

 

Hope the normal cdf patch enable by default.

Edited by gujiangjiang

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
×