Hate to do a me too. But yep.Hi,
I also have the same exact issue as well. Sleep is broken. I don't remember it being like this in 10.3.1 and in Sierra since I have had the RX460 for a while.
I wonder if they did it on purpose to inconvenience us RX 460 owners since these cards aren't officially, official?
Just to confirm that the above steps fixed the sleep issue on my Mac Pro running 10.13.2 with an RX 580.
A bit annoying to have to reboot thrice and disable/enable SIP in the recovery console, but still much faster/safer than flashing the graphic card in a Windows box.
If you do a sudo kextload <driver path.kext> for whatever the driver is, it would show up on the General Security and Privacy panel, if it needed approval.Well... the supplemental update totally broke my RX 580 driver it seems (see dedicated thread), I am left with unaccelerated 2D, unbearably slow. Could it be a SIP/kext issue?
If you do a sudo kextload <driver path.kext> for whatever the driver is, it would show up on the General Security and Privacy panel, if it needed approval.
My story on this problem:
I have Mac Pro tower 5.1 2012 Nehalem and Sapphire RX 580 8 GB Nitro (ID 0x67df, revision 0x00e7) — this RX model has native macOS support, but with 10.13.2 got sleep issue as well.
I edited AMD9500Controller.kext (CFG_FB_LIMIT is 5 for my card) and it works well, even with SIP enabled and without recovering permissions with KextUtility.
But after 10.13.2.2 update (which patches Meltdown stuff) edited AMD9500Controller.kext is recognised only with disabled SIP. If you turned SIP on, RX 580 is not recognised, and graphic acceleration is turned off completely (as in safe mode).
Now i have only choice of keeping SIP disable (or maybe try csrutil enable --without kext ?)
[doublepost=1515717002][/doublepost]Ooook, and now somebody please explains to me how it can be — i managed again to boot with enabled SIP, edited AMD9500Controller.kext, recognised RX580 on 10.13.2.2. I cannot find any logic in all this. Proof is in attached image.
The result for me is that now awaking from sleep doesn't work even with edited CFG_FB_LIMIT in AMD9500Controller.kext — i don't know why. I disabled SIP, RX580 is recognised, kext is loaded.The logic should be very straight forward. If SIP is fully enabled, no unsigned kext can be loaded. TBH, I very doubt if your SIP really enabled last time. If yes, your modded kext should not be loaded.
A few reports of it breaking their RX 580 completely.Anyone try the supplemental MacOS 10.13.2 update, does it break the temporary AMD9500Controller.kext workaround?
Man, Apple is really not doing good with their software updates these days.A few reports of it breaking their RX 580 completely.
But it wasn't on 10.13.2? If that is the case, then this is good news.10.13.3 beta 5 is sleeping on my system!
My system at first seemed fix as it slept without error/restart last night. Today though I just went to use my iMac to find out that the error still exists for me and had an error/restart while waking from sleep. I have the public beta 5 installed of 10.13.3 and running an 27" iMac Late 2012.10.13.3 beta 5 is sleeping on my system!
We were talking about the Mac Pro and using RX 580 which causes sleep issues.My system at first seemed fix as it slept without error/restart last night. Today though I just went to use my iMac to find out that the error still exists for me and had an error/restart while waking from sleep. I have the public beta 5 installed of 10.13.3 and running an 27" iMac Late 2012.
Seems like they are making progress then, which is a good sign! Hopefully in the upcoming beta builds I'll also notice mine being resolved as well.We were talking about the Mac Pro and using RX 580 which causes sleep issues.
10.13.3 beta 5 is sleeping on my system!
That's conflicting with the above posts where the supplemental updated broke the sleep again.Hopefully the fix is in place for 10.13.3 public release…have to say though I installed the supplemental update to 10.13.2 this morning, and the kext workaround was unaffected (the update didn't switch off SIP either)- just woke my MP from sleep to shut it down, no issues.
It worked fine for me. Experiences clearly vary.That's conflicting with the above posts where the supplemental updated broke the sleep again.