Contribute
Register

macOS 10.13.6 Update

Add me to the list of people who got washed out colours/jaggy fonts/rainbow text with these new AMD graphics drivers sending YCbCr to my RGB monitor. Thanks to the info in post #249 I added the manual RGB override for my display (no need to disable SIP because we are already hacked) after only a few hours of eye strain LOL! Why don't we add that to the first post if many are encountering it, could be quite bad for the eyes of people who don't notice it.

To the person who saw a pink screen I think that happens when YCbCr is sent to a display that does not know how to handle it, I've seen it on some older Sony TVs.

Very odd we are back to having to do manual overrides, I remember this when the first Dell 4K displays came out and thought those days were long gone.
I don't think that this has anything to do with AMD drivers. From what I have read, this problem is created by Apple. Previous MacOs updates have not created the "pink" problem (with my monitor, dating back to 10.8). I think that you may have a point that the display may be a weak link but since this only cropped up with 10.13.6 (and the fix addressed the monitor profile, not the AMD driver), I will continue to blame Apple for the SANFU.:crazy:
 
You are right, the only reason I suggested it’s in the new Apple/AMD drivers because the first post said we have new ones but could be anywhere in the system.

In a way your pink screen is actually quite useful to alert you to the issue if it happens again, especially when we rely on people saying their upgrade went fine and it depends on their eyesight for the jaggy font thing.
 
You are right, the only reason I suggested it’s in the new Apple/AMD drivers because the first post said we have new ones but could be anywhere in the system.

In a way your pink screen is actually quite useful to alert you to the issue if it happens again, especially when we rely on people saying their upgrade went fine and it depends on their eyesight for the jaggy font thing.
Well, no. The reference to new drivers in the first post has to do with Nvidia drivers that need to be updated with every MacOs update since Nvidia is not natively recognized by Apple. Apple is using Radeon graphics cards so that means that they are natively recognized, hence no need to install and update drivers.
 
The first post does say there is a new AMD driver in this update. I’d guess it is defaulting to YCbCr instead of RGB for unknown displays probably a bug.
 
The first post does say there is a new AMD driver in this update. I’d guess it is defaulting to YCbCr instead of RGB for unknown displays probably a bug.
Yes, Apple updates the Intel and AMD drivers, since they are natively supported. They do not update the Nvidia drivers. This native support is why many on this site have migrated to Radeon cards. Hopefully, we will not have a repeat of the problem with Mojave.
 
Update done with the App Store. All went well, except USB 3.
I updated my Lilu.kext with the following value to fix the issue.

Code:
        <key>KextsToPatch</key>
        <array>
            <dict>
                <key>Comment</key>
                <string>USB 10.13.6+ by PMHeart&FredWst</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                g32IDw+DpwQAAA==
                </data>
                <key>InfoPlistPatch</key>
                <false/>
                <key>MatchOS</key>
                <string>10.13.x</string>
                <key>Name</key>
                <string>com.apple.driver.usb.AppleUSBXHCI</string>
                <key>Replace</key>
                <data>
                g32ID5CQkJCQkA==
                </data>
            </dict>
            <dict>
 
Very Strange, I don't know why I am having these issues. I did recently update to 10.13.6. After the update I had no problems other than trying to get my thunderbolt card to work (thanks again! @kgp )
Now anytime I boot the computer it hangs at the apple logo. Just loads halfway and then hangs. I added the USB patch for 10.13.6+ still nothing. Any suggestions? My system is bricked. I tried booting in safe mode -x no luck. Here attached is some verbose screenshots.
 

Attachments

  • 20180727_164945.jpg
    20180727_164945.jpg
    2.6 MB · Views: 187
  • 20180727_155758.jpg
    20180727_155758.jpg
    3.9 MB · Views: 194
  • 20180727_155805.jpg
    20180727_155805.jpg
    3.3 MB · Views: 183
Update done with the App Store. All went well, except USB 3.
I updated my Lilu.kext with the following value to fix the issue.

Code:
        <key>KextsToPatch</key>
        <array>
            <dict>
                <key>Comment</key>
                <string>USB 10.13.6+ by PMHeart&FredWst</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                g32IDw+DpwQAAA==
                </data>
                <key>InfoPlistPatch</key>
                <false/>
                <key>MatchOS</key>
                <string>10.13.x</string>
                <key>Name</key>
                <string>com.apple.driver.usb.AppleUSBXHCI</string>
                <key>Replace</key>
                <data>
                g32ID5CQkJCQkA==
                </data>
            </dict>
            <dict>

You should not use MatchOS entries..

What has the USB port limit patch to do with Lilu.kext?

Why 10.13.6+?
 
I opened my config.plist in Clover Configurator and added patch directly in «Text Mode» tab to «KextsToPatch» block. Then pressed «Synchronize» button.

After this, you should see this patch in «Kernel and Kext Patches» tab.

Code:
<dict>
   <key>Comment</key>
   <string>USB 10.13.6+ by PMHeart</string>
   <key>Disabled</key>
   <false/>
   <key>Find</key>
   <data>
   g32IDw+DpwQAAA==
   </data>
   <key>InfoPlistPatch</key>
   <false/>
   <key>MatchOS</key>
   <string>10.13.x</string>
   <key>Name</key>
   <string>com.apple.driver.usb.AppleUSBXHCI</string>
   <key>Replace</key>
   <data>
   g32ID5CQkJCQkA==
   </data>
</dict>

ABmZdR+

mkvDS4+


I tried Everything but my usb 3 still not working. Help me to fix this.
 
Back
Top