Jump to content

Tracing back the AMD GPU wakeup issue to its origin

AMD GPU Sierra El Capitan sleep wakeup Radeon

  • Please log in to reply
201 replies to this topic

#141
Gigamaxx

Gigamaxx

    InsanelyMac Legend

  • Donators
  • 902 posts
  • Gender:Male

Not working Amd 390X Asus Strix, tried al combination possible in Bios and Ati Inject Yes and No. 
 
- Connectors problem?
- If someone wants to cooperate and need a compiled Darwin or sth like that just tell me and I will add the file.


Does it have the 9300controllerkext ID 0x73001002? They dedicated a whole controllerkext but there is no matching ID in the accelerator kexts. If Apple assigned a whole controllerkext to that card only hopefully they are going to add a 5150kext or something just for that card very soon. We tried adding the ID to the 5000kexts, the 4150, 4250, 4000 etc. nothing takes.

@mork nice explanation, I'm just wondering how to inject a custom SSDT for GPU? what I did so far is copy and replace the code in DSDT.aml generated by clover and saved it into /EFI/acpi/patched...
 
but what to do with the SSDT-AMD.aml. How would you inject just this file? Does clover automatically scan the ACPI/patched folder or?


Slice added it to clover 4296 so it’s automatic if selected in options, before we were adding the SSDZt to Clover ACPI/Pathced folder.

#142
Gigamaxx

Gigamaxx

    InsanelyMac Legend

  • Donators
  • 902 posts
  • Gender:Male

deleted



#143
Nightf4ll

Nightf4ll

    InsanelyMac Protégé

  • Members
  • PipPip
  • 79 posts

You asked about the injection method not how to compile it?

I thought there was an easier method without compiling it, my mistake I guess.. Anyways, deleted my above comments, since I dont want to spam this thread...



#144
Picasso

Picasso

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 383 posts
  • Gender:Male

@Gigamaxx

I don´t understand what are you saying.

If I have to force a kext, or you know the apple devs and you are waiting for an Id.

 

I think 390x is the same as 290x, and maybe is to add something into the ssdt.



#145
Gigamaxx

Gigamaxx

    InsanelyMac Legend

  • Donators
  • 902 posts
  • Gender:Male

@Gigamaxx

I don´t understand what are you saying.

If I have to force a kext, or you know the apple devs and you are waiting for an Id.

 

I think 390x is the same as 290x, and maybe is to add something into the ssdt.

I tried to help someone with their Fury card with ID 0x73001002.    Is this the same card you have with HBM memory?    There is a AMD9300Controllerkext with only 0x73001002 ID  and no other IDs in that kext.   However no matter which accelerator kext we used ie.. AMD5000kext, AMD4250kext, AMD4150kext, AMD4000kext by adding an ID 0x73001002 to info.plist the card never worked.    I noticed that the AMD5000kext has Vega IDs and also there is one more Kext with the IDs in the info.plist.    So the Vega branch of graphics drivers contain 3 kexts with the Vega device IDs.    Most OSX graphics supported cards (AMD) use only 2 kexts.     If the Fury card 0x73001002 is to work with the AMD5000kext then you have to add the 0x73001002 to 2 kexts in the 5000 bundle.   The AMDX5000HWServiceskext.    You could try to add that ID to both the AMD5000kext and the HWServiceskext to see if the AMD9300Controllerkext will link with it.   The user I tried to assist may not have added the info.plist edits correctly so it may work.   It may be worth trying, but if you have that card ID you cannot currently use the card because the ID is missing from the existing kexts.  I think they will add a AMD5150kext or something similar like the did with Polaris cards in Sierra.    In Sierra we were able to use Polaris cards by adding these IDs in the various kexts.

Attached Files



#146
Picasso

Picasso

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 383 posts
  • Gender:Male

@Gigamaxx

 

Amd 390X/290X

 

DeviceID 0x67B01002

AMD8000Controller and AMDX4000

Hawaii

Baladi framebuffer



#147
Gigamaxx

Gigamaxx

    InsanelyMac Legend

  • Donators
  • 902 posts
  • Gender:Male

@Gigamaxx

 

Amd 390X/290X

 

DeviceID 0x67B11002

AMD8000Controller and AMDX4000

Hawaii

Baladi framebuffer

 

Sorry, I thought it was fury card.    Did you check for IDs in the 4000kext?


@Gigamaxx

 

Amd 390X/290X

 

DeviceID 0x67B11002

AMD8000Controller and AMDX4000

Hawaii

Baladi framebuffer?    Here are edited kexts, save extra originals, install these and then use kext wizard before reboot.

 

Try these edited kexts for 0x67B11002 use kext wizard before reboot.

Attached Files



#148
Tusskan

Tusskan

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 152 posts
  • Gender:Male
  • Interests:Javascript.

Sorry, I thought it was fury card.    Did you check for IDs in the 4000kext?

 
Try these edited kexts for 0x67B11002 use kext wizard before reboot.

 

@Gigamaxx
 
Amd 390X/290X
 
DeviceID 0x67B11002

AMD8000Controller and AMDX4000
Hawaii
Baladi framebuffer
 
 

Sorry, I thought it was fury card.    Did you check for IDs in the 4000kext?

 
Try these edited kexts for 0x67B11002 use kext wizard before reboot.

 
DeviceID 0x67B11002
 
That's the Device ID for R9 290 non X

#149
Pavo

Pavo

    InsanelyMac Legend

  • Developers
  • 575 posts
  • Gender:Male
  • Location:Fort Gordon, GA

R9 290X/390X Device ID is 0x67B01002 and its in AMD8000Controller.kext, has been natively supported since Yosemite.



#150
WarDoc

WarDoc

    The oncoming Storm

  • Members
  • PipPipPipPipPipPipPip
  • 816 posts
  • Gender:Male
  • Location:usa
  • Interests:Causing Chaos just to watch the world burn

For the 290X proper naming patch it's 

AMD8000Controller

Find: 414d4420 52616465 6f6e2048 44203878 7878

replace: 41 4d 44 20 52 61 64 65 6f 6e 20 52 39 20 32 39 30 58

 

For 390x replace: 41 4d 44 20 52 61 64 65 6f 6e 20 52 39 20 33 39 30 58

 

if you want 490x for kicks well Replace : 41 4d 44 20 52 61 64 65 6f 6e 20 52 39 20 34 39 30 58

 

for newest 10.13.2 beta find:414d4420 52616465 6f6e2048 44203878 7878 

replace: 41 4d 44 20 52 61 64 65 6f 6e 20 52 39 20 32 39 30 58

Clover Patch Works Thanks 



#151
cyberdevs

cyberdevs

    InsanelyMacaholic

  • Donators
  • 2,501 posts
  • Gender:Male

For the 290X proper naming patch it's 

AMD8000Controller

Find: 414d4420 52616465 6f6e2048 44203878 7878

replace: 41 4d 44 20 52 61 64 65 6f 6e 20 52 39 20 32 39 30 58

 

Clover Patch Works Thanks 

Did you test the SSDT? Does it work?



#152
WarDoc

WarDoc

    The oncoming Storm

  • Members
  • PipPipPipPipPipPipPip
  • 816 posts
  • Gender:Male
  • Location:usa
  • Interests:Causing Chaos just to watch the world burn

Did you test the SSDT? Does it work?

it failed but thanks for trying



#153
cyberdevs

cyberdevs

    InsanelyMacaholic

  • Donators
  • 2,501 posts
  • Gender:Male

it failed but thanks for trying

You got the black screen or the naming wasn't right?



#154
Si Vis Pacem

Si Vis Pacem

    InsanelyMac Protégé

  • Members
  • PipPip
  • 65 posts

Not working Amd 390X Asus Strix, tried al combination possible in Bios and Ati Inject Yes and No. 

 

- Connectors problem?

- If someone wants to cooperate and need a compiled Darwin or sth like that just tell me and I will add the file.

 

Did you decode your gpu bios as per VLADs guide and check if your connectors are the same as the one in the Baldi frame buffer? Or just use AtiFramebufferUtility.

 

edit:

corrected an autocorrect change



#155
WarDoc

WarDoc

    The oncoming Storm

  • Members
  • PipPipPipPipPipPipPip
  • 816 posts
  • Gender:Male
  • Location:usa
  • Interests:Causing Chaos just to watch the world burn

You got the black screen or the naming wasn't right?

black screen 


F0VN0Fy.pnggreat work 



#156
cyberdevs

cyberdevs

    InsanelyMacaholic

  • Donators
  • 2,501 posts
  • Gender:Male

black screen 

Just out of curiosity can you tell me the device ID for your GPU? Is it 67B0? right?



#157
WarDoc

WarDoc

    The oncoming Storm

  • Members
  • PipPipPipPipPipPipPip
  • 816 posts
  • Gender:Male
  • Location:usa
  • Interests:Causing Chaos just to watch the world burn

Just out of curiosity can you tell me the device ID for your GPU? Is it 67B0? right?

yup all the info was in the bios I gave you and the 290x has only one device Id


Sent from my iPhone using Tapatalk

#158
Fl0r!an

Fl0r!an

    InsanelyMac Protégé

  • Members
  • Pip
  • 37 posts

Nice to see this issue finally being fully understood and solved! I've assumed that pre-OS initialization of the GPU was the culprit for quite a long time, but I never was able to prove/fix it (as documented in the other thread).

 

Great work Mieze!  :)



#159
cyberdevs

cyberdevs

    InsanelyMacaholic

  • Donators
  • 2,501 posts
  • Gender:Male

yup all the info was in the bios I gave you and the 290x has only one device Id


Sent from my iPhone using Tapatalk

When I tried to open the BIOS there was an error. So I couldn't say for sure, and I know that there's only one device ID for R9 290X but if it has a custom VBIOS or if it is a custom designed GPU things might change.

 

Anyways your problem is solved and that's what matters.

Attached Files



#160
Pavo

Pavo

    InsanelyMac Legend

  • Developers
  • 575 posts
  • Gender:Male
  • Location:Fort Gordon, GA

Added all the SSDTs in this thread to the repo https://ddi.hopto.or....brock/AMD_SSDT








0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2017 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy