Jump to content

AMD 390x on 10.10.4 Problems


tomh117
 Share

12 posts in this topic

Recommended Posts

I'm having trouble getting my new 390x to work on 10.10.4.
I have seen a ton of posts about the 290x but nothing about the 390x, which from my understanding is mostly the same thing.

The id of the card is 67b0 0080, I tried adding that to the AMD8000Controller.kext AMDRadeonX4000.kext like suggested in another post but that didn't do anything.
I'm booting in chameleon with kext-dev-mode=1 and tried both GrapicsEnabler=YES and NO (currently having issues with clover beachballing after login so I have to use chameleon for now).

I couldn't see any issues with the kexts in the bootlogs, and I checked kextstat and it does show AMD8000 as loaded.
But it just isn't using the card/driver. The system profiler tool only shows it with a few MB VRAM and everything is as clunky as before.

No framebuffer patch, the way I understood this from another thread is that I don't need a framebuffer patch if I only have 1 monitor connected, and It should work out of the gate? But that might have been about the 290x.

I also saw this post and understand that the 390x should be better supported on 10.11, but I'm on an AMD kernel so that's not an option.

Any help and guidance would be greatly appreciated.

Link to comment
Share on other sites

Okay I reset AMD8000 back to its original IDs and added mine to AMD9000, but still no luck.
Do I still need to add the ID to AMDRadeonX4000 as well, cause that other post said so for the 290x?

Also we are talking about editing the 10.10.4 kexts right? Not the 10.11 ones "backported" to 10.10.4? Cause currently I'm editing the 10.10.4 ones.

But its not working. And kextstat still shows AMD8000 and AMDSupport as loaded, despite me triple checking that my ID is in 9000 and not in 8000 anymore.
I have no clue why. I also installed them with KextWizrard and fixed permissions and rebuild cache to make sure it was okay.

I also tried both GraphicsEnabler YES and NO with chameleon as well as various combinations with Clover. With InjectATI on and off and the original ID as well as modified IDs just to get it working but no luck either.

Link to comment
Share on other sites

390X has the same device id as the 290X which AMD8000Controller already has no need to add it to any other kext.

 

Ohh I assumed that the IOPCIMatch string was the device and revision field but it is the device and vendor field. Sorry you're right that is in the AMD8000 file by default, I'm an idiot.

 

But if it's in the file by default why doesn't it work and how to I get it to work?

Link to comment
Share on other sites

Does the 390X not work by default without injecting a framebuffer?

 

Nope it doesn't, neither on 10.10.1 nor 10.10.4, tried every possible GraphicsEnalber,AtiConfig in chameleon and equivalent thing in clover as well without success. Always 3MB VRAM.

 

I also tried backporting the 10.11 ones but managed to completely screw up my OS somehow and had to reinstall. No idea what to do now.

Link to comment
Share on other sites

Ok I have a R9 390.. I edited AMD8000 and AMDX4000. In the 8000 I added 0x67B11002 to the end of 0x67B01002.   THEN in AMDX4000 I changed 1 of them. I changed the 0x67B01002 to 0x67B11002

 

Now for me only ONE port works DVI meaning if I boot with TWO monitors I just get black.. if only ONE DVI.. boots fine. .never tried booting just DP.hmm.. yet if I sleep then plug in other monitor I get two....

 

Also this is using Chameleon. Now with El Capitan (no editing files) that drive I use Clover and injecting Aticonfig blah blah blah it boots in fine ..its just like its in safe mode as if NO frambuffer is being used YET I have it set and tried different ones. It sees the card as R9 290 8096.. full res.. BUT.. man I am no expert haha but got 10.10.5 working.

 

For ME again its just not as fast as others with 290's..mine being 390. Yet I dont game on it so .. no lose there.

Link to comment
Share on other sites

Thanks for the help everyone.

 

Couldn't get it to work, just in case someone else with the same problem finds this thread:

 

I found this reddit post with someone in the comments having the same problem as me. He also installed with niresh 10.10.1 and updated and had the exact same issue I had. Some other people as well. It seems the niresh iso includes something that messes with the drivers or stops them from working. He said a clean install fixes it.

 

Now to find out how to do a clean install on AMD without any distro.

Link to comment
Share on other sites

  • 2 weeks later...

Thanks for the help everyone.

 

Couldn't get it to work, just in case someone else with the same problem finds this thread:

 

I found this reddit post with someone in the comments having the same problem as me. He also installed with niresh 10.10.1 and updated and had the exact same issue I had. Some other people as well. It seems the niresh iso includes something that messes with the drivers or stops them from working. He said a clean install fixes it.

 

Now to find out how to do a clean install on AMD without any distro.

hey i also have a 390x use clover it has support on its own by default i have problems cuz i am using dvi lines and flickers. but yeah ! just trying to get ur hope back ! 

hey i also have a 390x use clover it has support on its own by default i have problems cuz i am using dvi lines and flickers. but yeah ! just trying to get ur hope back ! 

10.10.5 may be a bit better ? 

Link to comment
Share on other sites

  • 4 weeks later...
 Share

×
×
  • Create New...