Jump to content

R9 Fury X Black screen Issue


paladinfan
 Share

15 posts in this topic

Recommended Posts

I have just installed the High Sierra 10.13.4 beta3 on my PC, which is B85 platform.


 I found I can't boot normally with the R9 Fury X.

I boot the macOS through Clover 4411 with lilu.kext 1.2.2, whatevergreen.kext 1.1.5, AppleALC.kext and AppleIntelE1000.kext. Add the frag -radbeta -lilubeta, with and without Inject ATI and RadeonDeinit

After the boot screen of Clover it turn to black, if I plug the cable to Intel Graphics HD4600, I can see the loggin screen only on the screen of IGPU.

Even if I start system through IGPU and plug cable to Fury X it still get a black screen.

Besides, in the system I found that AMD9000Controller and AMDRadeonX4000 are all loaded and Fury X's GPU may be working , but it is just black on screen, I take some screenshot below to show why I said GPU may be working:

post-2395804-0-12729200-1519784197_thumb.png

post-2395804-0-26676400-1519784208_thumb.png

post-2395804-0-93681400-1519784262_thumb.png

I can even change the display resolution of the screen on Fury X through RDM but I can't see anything except black on the screen.

Could sb. help me pls?

Link to comment
Share on other sites

Framebuffer?

 

You are correct, no more 9300cintrollerkext in 13.4.

I‘m trying the Framebuffer but... the IORegistryExplorer didn't show a FB name after ATY both in 10.13 and 10.12.6(In 10.12 the card works prety well).

So I may have to try FB names in 9000controller one by one...

Link to comment
Share on other sites

  • 2 weeks later...
On 2018/3/2 at 10:53 PM, Gigamaxx said:

If you have Xcode the 9000controller info plist may have them listed.

 

post-1753549-0-55174700-1520035295_thumb.png

Hi Bro.

There are some questions about the framebuffer.

I found there are some framebuffer in the AMD9000Controller.kext.

But the data of them shows they support several types of ports.

Some Framebuffer supports 6x DPs while some others supports only 1 HDMI.

No framebuffer gives the data equal to the port of FuryX (3x DPs+1x HDMI) whatever in 10.13.4 beta or 10.12.6.

But in 10.12.6 I can get the screen output normally through every port of my card.

I feel a liitle strange about it...

Link to comment
Share on other sites

3 hours ago, paladinfan said:

Hi Bro.

There are some questions about the framebuffer.

I found there are some framebuffer in the AMD9000Controller.kext.

But the data of them shows they support several types of ports.

Some Framebuffer supports 6x DPs while some others supports only 1 HDMI.

No framebuffer gives the data equal to the port of FuryX (3x DPs+1x HDMI) whatever in 10.13.4 beta or 10.12.6.

But in 10.12.6 I can get the screen output normally through every port of my card.

I feel a liitle strange about it...

The latest beta 13.4 version 4 was reported to work better.   Have you tried that yet?     

For frame buffers you can also try others not listed in the 9000kext like Baladi or FlueveSWIP (listed in 9300kext)?   Check out Clover Configurator frame buffer choices.

Link to comment
Share on other sites

  • 2 weeks later...
On 2018/3/12 at 12:45 AM, Gigamaxx said:

The latest beta 13.4 version 4 was reported to work better.   Have you tried that yet?     

For frame buffers you can also try others not listed in the 9000kext like Baladi or FlueveSWIP (listed in 9300kext)?   Check out Clover Configurator frame buffer choices.

Hi Bro

I think I resolved this issue. It was a long time that I was busy and got no time to work on the macOS

And yesterday I found the answer.

If I choose 'inject intel' in the Clover I'll get a black screen. (I need to enable the IGFX in bios for some application's feature in windows)

It seems like if I make the macOS recognize both the graphics (FuryX and HD4600), it required me to boot with a cable plug on HD4600.

Or I'll get a black screen.

Link to comment
Share on other sites

On 2018/3/26 at 12:18 AM, cdrhoek said:

It took Beta version 4 to get my FuryX working.  I don't need Lilu, Whatevergreen, or Shiki.  I only have to enable RadeonDeInit.  

Could you tell me how is your config.plist like?

And are you booting with UEFI only?

I can't boot with the 'Inject Intel' potion because if I chose it I'll get a black screen on FuryX even if I set up the PCIE solt1 as primary output.

And if I block the 'Inject Intel' I will start normally, but I can't make the machine sleep.

Disable the IGPU in bios seems make the 10.13.4 works perfect but I need the IGPU when I using Windows...

Link to comment
Share on other sites

  • 3 weeks later...
 Share

×
×
  • Create New...