Contribute
Register

macOS Sierra PB: Need testers for new AMD Radeon drivers!

Status
Not open for further replies.
How did you install? Did you follow a guide and add all the fixes? Some on another site were reverting back to earlier clover revisions due to bugs.

The first time I downloaded the installer, double clicked it and noticed something strange -- it did not use the RX card connected monitor for the install as is usual, it used the motherboard display for the whole process, the RX monitor stayed blank.

The second time I used the Recovery partition to use Disk Utilities to repair permissions and then reinstall the os. Again it ignored the RX card and used the motherboard display. But both times the graphics were excellent, so I think it was using the RX card as a helper because I have the memory allotment for the IGPU set to very low, around 64MB IIRC.

Clover is version 4097, general release. These are the Clover settings I used:
Code:
    <key>SMBIOS</key>
    <dict>
        <key>BiosReleaseDate</key>
        <string>06/26/2017/string>
        <key>BiosVendor</key>
        <string>Apple Inc.</string>
        <key>BiosVersion</key>
        <string>IM142.88Z.0119.B01.1706261827</string>
        <key>FirmwareFeatures</key>
        <string>0xe007e137</string>
        <key>FirmwareFeaturesMask</key>
        <string>0xff1fff3f</string>
 
But, I can report some good news, I had system sounds set to play though the default connection with the default connection being the AMD RX HDMI connector. I usually have a couple of seconds before the window server crashes and restarts and I was able to hear actual sound from the HDMI connector...

Now if only I can get the rest of it working.
 
Ive been having issue when injecting ATI in newer clover versions did you try letting the RX ride along natively as R9 xxx?

Ioreg. did it load?

At the moment I am using Inject-ATI set to false. Unfortunately the window server crashes too fast for me to do much more than move the cursor and click a few times before I am booted out to the log-in screen, which by the way is very stable, go figure. I am going to have to pull the card again and use the motherboard graphics to turn on ioreg as a startup item and remote login etc to try to debug it, but without any diagnostic crash reports that I can find this will be tough.

The kext does load because the fans spin up and the login screen comes on, it is just the window server is somehow losing the login credential -- guess -- and restarting. Note: window server is more of a Linux term than macOS term, but it is the same thing.
 
I have made some progress, the window server is being told to crash, but what is causing it is still up in the air ...
I am getting the following crash error:
Code:
...

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000008
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]

VM Regions Near 0x8:
--> 
    __TEXT                 000000010f716000-000000010f717000 [    4K] r-x/rwx SM=COW  /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.CoreDisplay             0x00007fffa9700b8c 0x7fffa966d000 + 605068
1   com.apple.CoreDisplay             0x00007fffa96a29da 0x7fffa966d000 + 219610
2   com.apple.CoreDisplay             0x00007fffa968940c 0x7fffa966d000 + 115724
3   com.apple.SkyLight               0x00007fffcaa740cc WS::DisplaySurface::Present(DisplaySurfaceSyncType) + 366
4   com.apple.SkyLight               0x00007fffcaabb0f3 CGXUpdateDisplay + 14291
5   com.apple.SkyLight               0x00007fffcaab76ed update_display_callback(void*, double) + 257
6   com.apple.SkyLight               0x00007fffcaafde8e run_timer_pass + 495
7   com.apple.SkyLight               0x00007fffcab2d2eb CGXRunOneServicesPass + 247
8   com.apple.SkyLight               0x00007fffcab2ebd3 SLXServer + 4205
9   WindowServer                     0x000000010f716dde 0x10f716000 + 3550
10  libdyld.dylib                     0x00007fffd0a4fff9 start + 1

...

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0xc2ba12ac3157001b  rbx: 0x0000000000000000  rcx: 0x00007fff504e8a10  rdx: 0x00007fff504e8a0c
  rdi: 0x0000000000000000  rsi: 0x00007fff504e8a08  rbp: 0x00007fff504e8a90  rsp: 0x00007fff504e8a20
   r8: 0x00007fff504e8a14   r9: 0x0000000000000000  r10: 0x000007fa43ed2dac  r11: 0x0000000000000004
  r12: 0x000000005b81c5c0  r13: 0x00007fff504e8ff0  r14: 0x00007fa43ed22078  r15: 0x0000000000000000
  rip: 0x00007fffa9700b8c  rfl: 0x0000000000010202  cr2: 0x00007faa8c0a5000
 
Logical CPU:     0
Error Code:      0x02000170
Trap Number:     133

This puppy runs fine if I pull the card, but some call is being made when the card is in the PCIe slot that is reaching beyond its allowed play space.
 
Have you tried a new config.plist without any AMD or Audio fixes?

I do not use any audio fixes and with Inject-ATI = false essentially no AMD fixes. This disk is as close to stock as possible, especially with wiping the disk and reinstalling the os a few times. I also tried the lilu and intelgraphicsfixup combination just to be sure, though I did not have much hope for it, it did not work. Just to be thorough, I also tried using the card as primary instead of the IGPU in the BIOS settings but no good.
 
Different Symbios?

I am kind of set with iMac 14.2, (Haswell setup i5 4690s) Z97n Gaming 5. iMac 14.1 is not speced for a discrete gpu. But the catch of it is it works just fine without the card.
 
I am kind of set with iMac 14.2, (Haswell setup i5 4690s) Z97n Gaming 5. iMac 14.1 is not speced for a discrete gpu. But the catch of it is it works just fine without the card.

I've used everything from Mac Mini to Mac Pro, even MacBook definitions, maybe a recent MacBook which has the RX installed?
 
Status
Not open for further replies.
Back
Top