Jump to content

R9 290X Help for mavericks


TechGuru
 Share

473 posts in this topic

Recommended Posts

Absolutely.

 

Okay then, there you go! :)

 

Attachment added with the following included in the package:

 

- Clover configuration (s/n etc. are masked).

- IOReg dump from IORegistryExplorer v2.1.

- Clover ACPI folder (original and patched DSDT, as well as the DSL file).

 

Check my signature for hardware / software specs (it's the desktop one of course  :)).

 

 

I hope that this information may help you. If you still need more information, don't hesitate to ask.

files.zip

  • Like 1
Link to comment
Share on other sites

Okay then, there you go! :)

 

Attachment added with the following included in the package:

 

- Clover configuration (s/n etc. are masked).

- IOReg dump from IORegistryExplorer v2.1.

- Clover ACPI folder (original and patched DSDT, as well as the DSL file).

 

Check my signature for hardware / software specs (it's the desktop one of course  :)).

 

 

I hope that this information may help you. If you still need more information, don't hesitate to ask.

I see no drivers attached to HDMI device.

Link to comment
Share on other sites

weird...  ^_^  What did you do to load Audio driver?

What about VoodooHDA?

 

If you mean HDMI audio. I do not use that. I only use HDMI video. I use ALC898 patch from toleda for working audio :) My screen is on HDMI, but does not have speakers.

I am currently not in the need to get HDMI audio working as I cannot test it, but if there is anything you need from me, please do tell.

 

I also finally came 'round to test the DP and that one (at least on my card) still needs to be re-plugged. DVI I cannot test, yet. HDMI works though on this card with the patch.

 

Sorry for the confusion  :blush:

Link to comment
Share on other sites

After using bits and pieces from MacFaultys config file I was able to get 2 displays running on my card (so, that's an improvement), still no luck getting the 3rd to light up. Wierd thing is - it doesn't matter what ports I plug them into, so the connectors work but it only activates 2 screens at max for some reason. What do you guys think, is it still a problem with the framebuffer or maybe the driver itself is {censored}ed?

Link to comment
Share on other sites

After using bits and pieces from MacFaultys config file I was able to get 2 displays running on my card (so, that's an improvement), still no luck getting the 3rd to light up. Wierd thing is - it doesn't matter what ports I plug them into, so the connectors work but it only activates 2 screens at max for some reason. What do you guys think, is it still a problem with the framebuffer or maybe the driver itself is {censored}ed?

 

I think I have gotten 3 up and going by connecting the 3rd after the system is booted. I just don't think I was successful getting it to boot that way.

 

Anyway, I have also noticed that any monitors connected to the secondary card seem to have strange artifact issues with flash animations. Its like its getting bitmaps mixed up or something. 

 

On the machine with 1440p monitor and HDMI I moved both monitors to the same card and now that machine works really well. 

Link to comment
Share on other sites

Hey Guys, I wanna say thanks for the config.plist (@MacFaulty) which worked for my R9 290 (Non-X). And I also ordered the active display port converter from dell and that's why I am posting here. I found the adapter very very cheap. 

 

http://www.notebook-traum.de/shop/multimedia/bizlink-displayport-zu-dvi-dual-link-adapter-kabel-dell-pn-0xt625-xt625-neu/

 

You get it for about 10 Euros. They are from Germany. International Delivery is 15 Euro, which makes 25 Euro, so still very cheap. (But i am not exactly sure where they deliver to, but i think International Delivery means Europe) 

 

Thought that might be useful.

Link to comment
Share on other sites

i repeat this card does not need active adapters that's why we can run 3 or more at once without them i run a dp to dvi non active it works i run a hdmi to dvi-dl non active so i suggest you learn a little more about the 290x before talking people into to buying {censored} they do not need

Link to comment
Share on other sites

Hello. Can someone help me? Days and days I`m trying to solve problem. I have MSI R9 290X (4gb). With  all patches in this topic i get only hdmi+dvi working. Or just black screen. I also tried to patch by myself. No luck. I need HDMI+DVI+DP working. Here`s my bios and config. I would be appreciate for your help.

You can try this, also I have attached the AMD8000Controller.kext from 10.10.3 which has the Exmoor FB, the Baladi FB makes the gfx card over heat badly.

Connector at index 0
	Type [@offset 43554]: DisplayPort (10)
	Encoder [@offset 43558]: INTERNAL_UNIPHY2 (0x21)
	i2cid [@offset 43646]: 0x90, OSX senseid: 0x1
Connector at index 1
	Type [@offset 43564]: HDMI-A (11)
	Encoder [@offset 43568]: INTERNAL_UNIPHY2 (0x21)
	i2cid [@offset 43673]: 0x92, OSX senseid: 0x3
Connector at index 2
	Type [@offset 43574]: DVI-D (3)
	Encoder [@offset 43578]: INTERNAL_UNIPHY1 (0x20)
	i2cid [@offset 43700]: 0x93, OSX senseid: 0x4
Connector at index 3
	Type [@offset 43584]: DVI-D (3)
	Encoder [@offset 43588]: INTERNAL_UNIPHY (0x1e)
	i2cid [@offset 43727]: 0x95, OSX senseid: 0x6


Connector Object Id [19] which is [DISPLAY_PORT]
	encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false
Connector Object Id [12] which is [HDMI_TYPE_A]
	encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x22 [duallink 0x2] enc 0x5)] linkb: true
Connector Object Id [4] which is [DVI_D]
	encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false
Connector Object Id [4] which is [DVI_D]
	encoder obj id [0x1e] which is [INTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false

01 [DISPLAY_PORT] 
redsock_bios_decoder :
enc obj 0x21 transmitter 0x12 dual link 0x2 enc 0x4
radeon_bios_decode:
Connector at index 0
Type [@offset 43522]: DisplayPort (10)
Encoder [@offset 43526]: INTERNAL_UNIPHY2 (0x21) 
i2cid [@offset 43632]: 0x90, OSX senseid: 0x1

12 04 01 01

02 [HDMI_TYPE_A]
redsock_bios_decoder:
encoder obj 0x21 txmit 0x22 duallink 0x2 enc 0x5
radeon_bios_decoder:
Connector at index 1
Type [@offset 42512]: HDMI-A (11)
Encoder [@offset 42516]: INTERNAL_UNIPHY2 (0x21)
i2cid [@offset 42621]: 0x92, OSX senseid: 0x3

22 05 02 03

03 [DVI_D]
redsock_bios_decoder:
encoder obj id 0x20 txmit 0x11 duallink 0x1 enc 0x2
radeon_bios_decoder:
Connector at index 2
Type [@offset 42522]: DVI-D (3)
Encoder [@offset 42526]: INTERNAL_UNIPHY1 (0x20)
i2cid [@offset 42648]: 0x93, OSX senseid: 0x4

11  02  03  04

04 [DVI_D]
redsock_bios_decoder:
encoder obj id 0x1e txmit 0x10 duallink 0x0 enc 0x0
radeon_bios_decoder:
Connector at index 3
Type [@offset 42532]: DVI-D (3)
Encoder [@offset 42536]: INTERNAL_UNIPHY (0x1e)
i2cid [@offset 42675]: 0x95, OSX senseid: 0x6

10  00  04  06

Personality: Exmoor
Original Output:
02  00  00  00  00  01  00  00  00  01  01  03  22  05  02  02
02  00  00  00  00  01  00  00  00  01  02  03  12  04  01  01
00  04  00  00  04  03  00  00  00  01  03  07  11  02  03  03
00  04  00  00  04  03  00  00  00  01  04  07  21  03  04  04

Patched Output:
Patched Output:
04  00  00  00  14  02  00  00  00  01  04  00  10  00  04  06 <—DVI2
00  04  00  00  04  03  00  00  00  01  01  00  12  04  01  01 <—Displayport
00  08  00  00  04  02  00  00  00  01  02  00  22  05  02  03 <—HDMI
04  00  00  00  14  02  00  00  00  01  03  00  11  02  03  04 <—DVI-D

Find:
02000000000100000001010322050202020000000001000000010203120401010004000004030000000103071102030300040000040300000001040721030404

Replace:
04000000140200000001040010000406000400000403000000010100120401010008000004020000000102002205020304000000140200000001030011020304

AMD8000Controller.kext.zip

  • Like 2
Link to comment
Share on other sites

 

You can try this, also I have attached the AMD8000Controller.kext from 10.10.3 which has the Exmoor FB, the Baladi FB makes the gfx card over heat badly.

Connector at index 0
	Type [@offset 43554]: DisplayPort (10)
	Encoder [@offset 43558]: INTERNAL_UNIPHY2 (0x21)
	i2cid [@offset 43646]: 0x90, OSX senseid: 0x1
Connector at index 1
	Type [@offset 43564]: HDMI-A (11)
	Encoder [@offset 43568]: INTERNAL_UNIPHY2 (0x21)
	i2cid [@offset 43673]: 0x92, OSX senseid: 0x3
Connector at index 2
	Type [@offset 43574]: DVI-D (3)
	Encoder [@offset 43578]: INTERNAL_UNIPHY1 (0x20)
	i2cid [@offset 43700]: 0x93, OSX senseid: 0x4
Connector at index 3
	Type [@offset 43584]: DVI-D (3)
	Encoder [@offset 43588]: INTERNAL_UNIPHY (0x1e)
	i2cid [@offset 43727]: 0x95, OSX senseid: 0x6


Connector Object Id [19] which is [DISPLAY_PORT]
	encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false
Connector Object Id [12] which is [HDMI_TYPE_A]
	encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x22 [duallink 0x2] enc 0x5)] linkb: true
Connector Object Id [4] which is [DVI_D]
	encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false
Connector Object Id [4] which is [DVI_D]
	encoder obj id [0x1e] which is [INTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false

01 [DISPLAY_PORT] 
redsock_bios_decoder :
enc obj 0x21 transmitter 0x12 dual link 0x2 enc 0x4
radeon_bios_decode:
Connector at index 0
Type [@offset 43522]: DisplayPort (10)
Encoder [@offset 43526]: INTERNAL_UNIPHY2 (0x21) 
i2cid [@offset 43632]: 0x90, OSX senseid: 0x1

12 04 01 01

02 [HDMI_TYPE_A]
redsock_bios_decoder:
encoder obj 0x21 txmit 0x22 duallink 0x2 enc 0x5
radeon_bios_decoder:
Connector at index 1
Type [@offset 42512]: HDMI-A (11)
Encoder [@offset 42516]: INTERNAL_UNIPHY2 (0x21)
i2cid [@offset 42621]: 0x92, OSX senseid: 0x3

22 05 02 03

03 [DVI_D]
redsock_bios_decoder:
encoder obj id 0x20 txmit 0x11 duallink 0x1 enc 0x2
radeon_bios_decoder:
Connector at index 2
Type [@offset 42522]: DVI-D (3)
Encoder [@offset 42526]: INTERNAL_UNIPHY1 (0x20)
i2cid [@offset 42648]: 0x93, OSX senseid: 0x4

11  02  03  04

04 [DVI_D]
redsock_bios_decoder:
encoder obj id 0x1e txmit 0x10 duallink 0x0 enc 0x0
radeon_bios_decoder:
Connector at index 3
Type [@offset 42532]: DVI-D (3)
Encoder [@offset 42536]: INTERNAL_UNIPHY (0x1e)
i2cid [@offset 42675]: 0x95, OSX senseid: 0x6

10  00  04  06

Personality: Exmoor
Original Output:
02  00  00  00  00  01  00  00  00  01  01  03  22  05  02  02
02  00  00  00  00  01  00  00  00  01  02  03  12  04  01  01
00  04  00  00  04  03  00  00  00  01  03  07  11  02  03  03
00  04  00  00  04  03  00  00  00  01  04  07  21  03  04  04

Patched Output:
Patched Output:
04  00  00  00  14  02  00  00  00  01  04  00  10  00  04  06 <—DVI2
00  04  00  00  04  03  00  00  00  01  01  00  12  04  01  01 <—Displayport
00  08  00  00  04  02  00  00  00  01  02  00  22  05  02  03 <—HDMI
04  00  00  00  14  02  00  00  00  01  03  00  11  02  03  04 <—DVI-D

Find:
02000000000100000001010322050202020000000001000000010203120401010004000004030000000103071102030300040000040300000001040721030404

Replace:
04000000140200000001040010000406000400000403000000010100120401010008000004020000000102002205020304000000140200000001030011020304

Unfortunately, same situation. I have DVI HDMI working. It doesn't recognize DP. Maybe I have syntax mistakes in config.plist? Or wrong bios settings.. I have vd-t - enable, intel graphics - disable, CSM - as I understood enable. (I have yosemite 10.10.3 beta 2 already).

config.plist.zip

Link to comment
Share on other sites

Unfortunately, same situation. I have DVI HDMI working. It doesn't recognize DP. Maybe I have syntax mistakes in config.plist? Or wrong bios settings.. I have vd-t - enable, intel graphics - disable, CSM - as I understood enable. (I have yosemite 10.10.3 beta 2 already).

 

I had to enable CSM to get DP to work. I bought a cheap HDMI --> VGA adapter so I could turn CSM off. Previously I only had a DP --> VGA adapter.

Link to comment
Share on other sites

I had to enable CSM to get DP to work. I bought a cheap HDMI --> VGA adapter so I could turn CSM off. Previously I only had a DP --> VGA adapter.

Same as me. I also use VGA-DP adaptor. And CSM as default (enable). I think, i have mistakes in config.plist. I`ll try to find a problem..

Link to comment
Share on other sites

I have different idea. I`ve got my monitors connected: primary(HDMI) with DVI-HDMI cable,  second(DVI) with DVI-DVI, and third (DP which not work) with VGA-VGA+vga-dp adapter. Maybe os x/mac cannot recognize DP because of adapter? What do you think guys?

 

HAVE ANYONE working monitors with adapters as mine?

Link to comment
Share on other sites

I have different idea. I`ve got my monitors connected: primary(HDMI) with DVI-HDMI cable,  second(DVI) with DVI-DVI, and third (DP which not work) with VGA-VGA+vga-dp adapter. Maybe os x/mac cannot recognize DP because of adapter? What do you think guys?

 

HAVE ANYONE working monitors with adapters as mine?

 

VGA is not supported by OS X but may work and i think there are no via dp adapters cause VGA is analogue signal and dp digital. Thats like to convert SKART to HDMI

 

happy hacking

 

OSBeast

Link to comment
Share on other sites

VGA is not supported by OS X but may work and i think there are no via dp adapters cause VGA is analogue signal and dp digital. Thats like to convert SKART to HDMI

 

happy hacking

 

OSBeast

Yes, digital and analogue. You`re right. I mean this device.

BUT Firstly, Windows runs great with this adapter.

Secondly, without frame buffer patch my Hackintosh can start with working DP. But as he like, can start with working or can start with black screen at same config.

 

I`m not sure that is something as a bug, or theoretically it can work with this adapter with right config?

post-1307523-0-14978700-1425557520_thumb.jpg

Link to comment
Share on other sites

i was using this one:

 

http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=9127780

 

it supports DVI and HDMI out and works really well. 

 

now I'm using this one

 

http://www.amazon.com/gp/product/B00LIHRFPW/

 

sometimes after wake with this one the monitor takes an long time to sync or reverts to a weird resolution. probably something to do with this cheap 19" monitor. 

Link to comment
Share on other sites

  • 2 weeks later...

Quick question. If you are patching a framebuffer, will this patch need to be adjusted when a new version of the kext is included in an update?

I'm using Clover and put the connectorsData in there. So, do you only need to patch the framebuffer once (only if the framebuffer stays in the driver and you keep the same graphics card, obviously)? :)

 

Thanks

Link to comment
Share on other sites

  • 1 month later...
  • 2 weeks later...
 Share

×
×
  • Create New...