macOS 10.14.6 Update

[DrTom]

No issues at all here in Central Ohio. This Haswell computer will be six years old in October and is still going strong. One of these days I'll have to edit my config.plist so that my Xeon is shown properly in the processor section.

 

[jaymonkey]

This is fixed with whatevergreen 1.3.1, not actually sure if it fixes it or just blacks out the screen slightly longer whilst loading the graphics....

@Blindedbythelights and all,

The pink/purple lines are caused when the Apple AMD driver initialises and tests the dGPU's VRAM. However, it seems that the VRAM test overruns the VRAM memory and spills into the display framebuffer memory causing the pink/purple artefacts.

For the most part t.he issue is purely cosmetic, however if booting in Clover verbose mode then the pink/purple lines will scroll which means that the test will fail (as the test read back will return an invalid value) which may cause some driver issues although this has yet to be confirmed.

The latest master builds of Lilu (1.3.8) and WhatEverGreen (1.3.1) work together to disable the AMD VRAM memory test which resolves the issue of the pink/purple artefacts. There is no public binary release of these two kext's yet so you either have to compile both yourself using Xcode or wait for the next public release.

The developers are aiming for the first week of August for the next set of public releases.

The issue and codes changes are detailed here :-

Disable VRAM testing on AMD GPUs on 10.14.4+ (based on vladie's patch) · acidanthera/WhateverGreen@bcd3f2e

Various patches necessary for certain ATI/AMD/Intel/Nvidia GPUs - Disable VRAM testing on AMD GPUs on 10.14.4+ (based on vladie's patch) · acidanthera/WhateverGreen@bcd3f2e

github.com

Cheers
Jay

 

[Stork]

...
The pink/purple lines are caused when the Apple AMD driver initialises and tests the dGPU's VRAM. However, it seems that the VRAM test overruns the VRAM memory and spills into the display framebuffer memory causing the pink/purple artefacts.

The latest master builds of Lilu (1.3.8) and WhatEverGreen (1.3.1) work together to disable the AMD VRAM memory test which resolves the issue of the pink/purple artefacts. There is no public binary release of these two kext's yet so you either have to compile both yourself using Xcode or wait for the next public release.
...

Thanks @jaymonkey! I updated Post #2 with your explanation which reinforces the instructions to update the kexts before updating.

 

[Henties]

@Blindedbythelights and all,

The pink/purple lines are caused when the Apple AMD driver initialises and tests the dGPU's VRAM. However, it seems that the VRAM test overruns the VRAM memory and spills into the display framebuffer memory causing the pink/purple artefacts.

The latest master builds of Lilu (1.3.8) and WhatEverGreen (1.3.1) work together to disable the AMD VRAM memory test which resolves the issue of the pink/purple artefacts. There is no public binary release of these two kext's yet so you either have to compile both yourself using Xcode or wait for the next public release.

Cheers
Jay

I still get those lines, on both of my builds, even with the kexts you recommend. The screenshot refers.

 

[jaymonkey]

Quick and easy update on my MonkeyMedia Mac.

I did not update Clover, Lilu or any of the Plug-In's, took around 10 mins with the usual 3 reboots.

Cheers
Jay

 

[Stork]

...The latest master builds of Lilu (1.3.8) and WhatEverGreen (1.3.1)...

Did you build these versions? I asked because they one version behind on their download links.

Releases · acidanthera/Lilu

Arbitrary kext and process patching on macOS. Contribute to acidanthera/Lilu development by creating an account on GitHub.

github.com

Releases · acidanthera/WhateverGreen

Various patches necessary for certain ATI/AMD/Intel/Nvidia GPUs - acidanthera/WhateverGreen

github.com

 

[jaymonkey]

I still get those lines, on both of my builds, even with the kexts you recommend. The screenshot refers.

@Henties,

I downloaded the master builds and compiled those two kexts on my Video Edit System which has a Vega 64 (see White Knight build in my sig) and I don't get the pink/purple lines anymore. Having said that those two kexts are still a work in progress so i would report your issue to the developers on the official BugTracker :-

Display flashes during second stage of booting [AMD GPU] · Issue #438 · acidanthera/bugtracker

Hi As you may already know these 2 problems on AMD GPU, during the second stage of booting, there is one second display flash, some times the whole display, some times part of the display, and it s...

github.com

Cheers
Jay

 

[NorthAmTransAm]

Clicked update, left to buy beer, forgot about it, was updated effortlessly.

 

[Henties]

@Henties,

I downloaded the master builds and compiled those two kexts on my Video Edit System which has a Vega 64 (see White Knight build in my sig) and I don't get the pink/purple lines anymore. Having said that those two kexts are still a work in progress so i would report your issue to the developers on the official BugTracker :-

Display flashes during second stage of booting [AMD GPU] · Issue #438 · acidanthera/bugtracker

Hi As you may already know these 2 problems on AMD GPU, during the second stage of booting, there is one second display flash, some times the whole display, some times part of the display, and it s...

github.com

Cheers
Jay

Yes I have been building and compiling all my Lilu and it's siblings kexts from downloaded masters for longer than I can remember. Those purple lines, during the boot process, do not bother me, therefore I see no reason "to raise an alarm" with the developers. From time to time I download new/updated "masters" and let myself be surprised by the outcome, after applying them. Both my builds are working very well indeed with the dev. state of the kexts I currently deploy as per #68.

Cheers
Henties

 

[jaymonkey]

Those purple lines, during the boot process, do not bother me, therefore I see no reason "to raise an alarm" with the developers

@Henties,

I would still go ahead and let the devs know that it's not working for you .... It's possible that in its current from the fix only works on the AMD Vega drivers rather than all AMD drivers (RX-580 in your case).

If they don't know then they cant fix it ....

Cheers
Jay