290x + Clover + 10.10.2

[destrekor]

Update: 

Installed successfully. 

 

Added Note:

I am returning the MST Hub because while it works perfectly in Windows, it seems Mac support for MST is very very limited. Ultimately, it wasn't going to make things that much easier to justify continuing to fight with it when I could recoup that money and put it to better use. 

 

I currently have multi-monitor working with two on DVI and one on DP. However, the middle monitor (upper DVI-D port on the 290X Lightning) flickers and requires a sleep/wake cycle to restore functionality. I'm hoping to iron that out and have a functional 3-monitor system from the get-go, however, I COULD tolerate this so long as everything else is functional with the cards (full performance and power management). I've been working within Windows so I haven't gotten to doing any further work, I suspect I'll have to patch AGPM for proper power management as I had to with the 560 Ti.

 

 

---------------------- Original Post ----------------------

 

I had/have a previous OS X installation and after the update to 10.10.2 I ended up trashing the Clover bootloader. I won't go into how I managed that, but suffice it to say I would like to make a new installation anyhow. I hope to at least be able to access the data of the old installation so that I may backup user data before I wipe that drive in the installer and start over. That installation had a few edits related to two 560 Ti's and onboard audio, and now that has changed. I have a USB soundcard (Xonar U7) and a MSI R9 290X Lightning (4GB). 

 

I have used a few different Connectors Data and Patch strings. I'm using the Baladi FB. 

 

I've tried these strings:

Data:

00040000040300000001030012040303000400000403000000010100110201010004000004030000000102002103020200040000040300000001040022050404

Patch:

00040000040300000001000012040101000800000402000000010000220502030400000014020000000100001102030404000000140200000001000010010406

From here: http://www.hackintoshosx.com/topic/22779-radeon-r9-290x-recognised-as-hd-8xxx/

 

 

These strings:

Data:

000400000403000000010300120403030004000004030000000101001102010100040000040300000001020021030202000400000403000000010400220504040004000004030000000105001000050500040000040300000001060020010606

Patch:

000800000402000000010200220502030004000004030000000101011204010100040000040300000001020021030202040000001402000000010300110203040004000004030000000105001000050500020000040200000001040110000406

From here: http://www.insanelymac.com/forum/topic/304386-yosemite-10102-r9-290x-2/

 

 

I've even tried this set:

ATIConnectorsData 00040000040300000001030012040303
ATIConnectorsPatch 04000000140000000001010011020303

From here: 

 

In all cases, I tried using only one DP connection. I had also tried just one DVI connection on a few different tests. I bought a MST DisplayPort adapter to power a triple-monitor setup using the one DP port, and it works under Windows on that machine. I was testing two monitors connected that way for the hackintosh efforts but then decided it was best to only use a single monitor connected directly to the DP connector, no middleman involved.

 

Where I stand? The installer does boot up, as when I set there long enough I'll hear a voice prompt from the installer. But I have no video, I never have had any under any test config. 

Immediately prior to launching, I do see this when booting with verbose: "AGPM Controller: Unknown Platform" 

 

 

Relevant system info:

P8Z68 Deluxe - BIOS 3603

i7-2600K

MSI R9 290X Lightning (4GB) [2x DVI-D / 1x HDMI / 1x DP]

 

Thoughts?

[Pavo]

Don't use ATI injection for the installer and only have 1 monitor connected, it will use the default FB and it should give you a screen.

[destrekor]

Aha, that did it. I'm in the installer now.

 

Also, using the MST DP hub, I do have two monitors connected with the installer mirrored on both at the moment. This foves me hope that getting all 3 to work off the single DP connection will be possible.

[destrekor]

Well I'm in Yosemite right now, and there is partial success.

 

I'm using the Inject again and the second set of strings I posted in the OP, the set that SunmanBG created from his 290X Lightning. As I have the same model, I figure that should work best. I'll have to try other ones however, as we aren't fully functional just yet.

 

To test multiple ports, I have my third monitor on the bottom DVI port. The other two monitors are on the MST hub that is on the DP port.

 

Unfortunately there are two issues here:

1. the DVI flickers and does not display image until after a sleep/wake cycle. 

2. the two monitors sharing the DP port are automatically mirroring each other, even though mirroring is not explicitly enabled. 

 

I have confirmed the DP port is in fact an MST-capable port, because those two monitors function perfectly as individual displays in Windows on this machine. 

 

I'll be playing around with different strings and other graphics-related info in the meantime. I also now have my second 290X Lightning, I had to send one in for RMA. Later, I'll be testing that under Windows for Crossfire purposes and then I'll get back to messing around in Mac to ensure functionality and power management. 

 

FYI: About Mac does display AMD Radeon R9 290X 4096MB, so that part is at least correct. Under System Information, it does not list Mirror enabled for DisplayPort, so at least that part is reported correctly by software. It is actually mirroring, however. 

 

Is it possibility that Multi Stream Transport is simply not a possibility under Mac? I've heard of that as an issue before. I'm curious if it is simply a matter of reworking the frame buffer information or if Mac simply does not enable multiple displays under DP. Considering you can daisy-chain Thunderbolt, and that carries multiple DP streams in such instances, I'd find it odd if it is not supported.

[destrekor]

Thought I'd update that I DO have three working monitors with individual displays (no mirrors). However, to achieve this I had to use both DVI ports available and only use one DP port, without the hub. I did not try using only one on the hub itself, I don't think it would have mattered as the hub would only pass on to the display controller that a single stream would be needed, but I digress.

 

However, there is a bit of an issue. The middle monitor, on DVI, flickers until a Sleep/Wake cycle. If nothing else, if everything can work like this, I can be satisfied in a humbled way. I'll have to at least check out performance later to confirm that things are at least working well, and if that is true, then I can handle this, especially if I have no other choice. But damn, to have everything good from boot would be wonderful.

 

Right now I am using sunmanBG's FB patch data:

Connector Data

000400000403000000010300120403030004000004030000000101001102010100040000040300000001020021030202000400000403000000010400220504040004000004030000000105001000050500040000040300000001060020010606

 

Connector Patch

000400000403000000010300120401010008000004020000000101002205020304000000140200000001020011020304040000001402000000010400100004060004000004030000000105002001050500040000040300000001060020010605

 

Zeroing out the fifth and sixth port segments really doesn't matter it seems, and I've just been using this to test anyhow. I'd really like to have the DP MST hub working but as I bought it to hopefully make multi-monitor easier for OS X, I guess I wouldn't mind returning it to get back that $100 or whatever it was. I like the idea because DP is awesome in replacement of DVI, and when disconnecting the PC it's one display cable to disconnect (connected to the hub) as opposed to unscrewing multiple DVI cables. However, if it just seems impossible to get working, I would like to recoup that $100, most definitely. 

 

I am asking for help in NOT getting that money back, just so we're clear. I really want this hub to work.

[destrekor]

I changed my mind. I am returning the MST Hub because while it works perfectly in Windows, it seems Mac support for MST is very very limited. Ultimately, it wasn't going to make things that much easier to justify continuing to fight with it when I could recoup that money and put it to better use.