Jump to content

R9 290X Help for mavericks

TechGuru

By TechGuru,
in ATi

 Share
473 posts in this topic

Recommended Posts

Awesome Donkey
Awesome Donkey
Posted
Posted

I've tried multiple fixes (e.g. tried/modified various Clover connection patches, different DVI-D port, etc.) to get DVI-D output working with my ASUS Radeon R9 290X DirectCU II OC card without the glitches with no luck. I've also tried looking into how changing the disk offset without changing the framebuffer broke the patch from working without any luck either (can anyone please explain that one?). So, I'm beginning to wonder since it's expecting a DisplayPort connection that perhaps I should purchase that DisplayPort to DVI-D adapter from Apple and try using it from the DP port instead of DVI-D. Maybe that'd work OOTB without any glitches? Thoughts?

MattsCreative
MattsCreative
Posted
Posted

I've tried multiple fixes (e.g. tried/modified various Clover connection patches, different DVI-D port, etc.) to get DVI-D output working with my ASUS Radeon R9 290X DirectCU II OC card without the glitches with no luck. I've also tried looking into how changing the disk offset without changing the framebuffer broke the patch from working without any luck either (can anyone please explain that one?). So, I'm beginning to wonder since it's expecting a DisplayPort connection that perhaps I should purchase that DisplayPort to DVI-D adapter from Apple and try using it from the DP port instead of DVI-D. Maybe that'd work OOTB without any glitches? Thoughts?

if you have a uefi mobo switch to ozmosis and use igpu if you have one it will enable 3 screens 

MattsCreative
MattsCreative
Posted
Posted

I've thought about it, but Ozmosis seems too much hassle to deal with honestly. Plus, my monitor won't work with the iGPU since it's DVI-D only (Korean 1440p IPS monitor).

no hassle go into chat and ask pavo and give him all your kexts 

zm8
zm8
Posted
Posted (edited)

 

Not sure how useful my changes are to anyone else, but sure. I made my changes in the clover config.plist though, but here's what I did to get the single DVI working good on the ASUS DirectCU II OC 290X (note, not any other port):

 

This is my graphics section:

	<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<true/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<false/>
		</dict>
		<key>PatchVBios</key>
		<false/>
		<key>FBName</key>
		<string>Baladi</string>
		<key>VideoPorts</key>
		<string>1</string>
		<key>InjectEDID</key>
		<string>Yes</string>
	</dict>

And add this under KernelAndKextPatches:

		<key>ATIConnectorsController</key>
		<string>8000</string>
		<key>ATIConnectorsData</key>
		<string>00040000040300000001030012040303</string>
		<key>ATIConnectorsPatch</key>
		<string>04000000140000000001010011020303</string>

 

Thanks! I have a PowerColor PCS+ R9 290 (non-X), and the above was what got my monitor (1680x1050) detected. Interestingly the connector layout of the 290 is exactly the same as your 290X.

 

I recently upgraded the monitor to a 27-inch one (resolution 2560x1440), and couldn't get it properly recognized though. The monitor showed up as "30.5-inch, 1920 x 1080"!

 

So after 2 days of trial and error, here is what made Dual-Link DVI work on my system: (See Edit 2 further down for an improved patch)

 

 

<key>ATIConnectorsController</key>

<string>8000</string>

<key>ATIConnectorsData</key>

<string>000400000403000000010300120403030004000004030000000101001102010100040000040300000001020021030202000400000403000000010400220504040004000004030000000105001000050500040000040300000001060020010606</string>

<key>ATIConnectorsPatch</key>

<string>000400000403000000010300120403010400000014020000000101000000010600040000040300000001020021030202000800000402000000010400220504030400000014020000000105000102050400040000040300000001060020010605</string>

 

 

And it was very important to turn off InjectEDID, otherwise I would get a second phantom monitor (30.5-inch 1920 x 1080) in the system that caused all sorts of weird issues (black screen after login, for example).

 

Edit:

Additionally, I had:

AtiPorts = 5, or not set

Dual Link to 1, or not set

 

And,

Fake ATI ID: 0x67b01002 (because my card is non-X)

 

Edit 2:

I quickly realized that the patch above was not quite there, so after some further experiments I am now using the new patch below.

 

Things weren't working but are now:

  • Boot into the login screen on any of the ports; previously only the bottom DVI port could do it
  • Survive sleep and wake (a pretty good sign that this is close, I think  :) )
<key>ATIConnectorsController</key>
<string>8000</string>
<key>ATIConnectorsData</key>
<string>000400000403000000010300120403030004000004030000000101001102010100040000040300000001020021030202000400000403000000010400220504040004000004030000000105001000050500040000040300000001060020010606</string>
<key>ATIConnectorsPatch</key>
<string>000800000400000000010300220503030004000004000000000101002103010200040000040000000001020012040201040000000400000000010400010204040400000004000000000105000000050600040000040000000001060020010605</string> 

Still I have no clue as to why the HDMI and DP video would flicker often once the system is up and running. Oh well, one DVI Dual Link port was all I was after.

 

Edit 3:

 

Just software updated the system to 10.10.1, and to my great relief the display still works fine at its native resolution!

 

Good luck everyone!

Edited by zm8
Awesome Donkey
Awesome Donkey
Posted
Posted

That patch kinda works for me. Kinda, as in it'll show the screen with the patched framebuffer instead of going black on boot. However DVI-D (both ports) still glitch for me forcing me to do the sleep trick. Still, it's a step in the right direction, thanks! :)

 

EDIT: Okay, done some further testing. The patch works with the second DVI-DL port if you set Dual Link to 1 in Clover, and remove VideoPorts. The *only* problem with the patch is, it graphically messes with the second stage during boot - the progress bar gets stuck to the bottom left instead of the middle of the screen. VERY close now - the second stage may need a special patch, not sure.

zm8
zm8
Posted
Posted

The *only* problem with the patch is, it graphically messes with the second stage during boot - the progress bar gets stuck to the bottom left instead of the middle of the screen. VERY close now - the second stage may need a special patch, not sure.

 

That's right ... the progress bar for some reason would show up at bottom left, but on my system it quickly disappears with the transition to the Yosemite login screen.  All is fine then as far as the display is concerned! :-)

Awesome Donkey
Awesome Donkey
Posted
Posted

It even appears on the bottom left when using the two second stage Clover patches too (there's two progress bars that show). Maybe vusun123 or somebody else has some ideas on how to workaround that to get perfect output.

Nur710As
Nur710As
Posted
Posted

 

Anonymous UUID:       6D376380-E4C0-857C-DC46-FCD007F4D0A7

 
Sat Oct 12 22:39:14 2013
panic(cpu 1 caller 0xffffff80002dc19e): Kernel trap at 0xffffff7f810b1af5, type 0=divide error, registers:
CR0: 0x0000000080010033, CR2: 0xffffff80f3d9465c, CR3: 0x0000000061cd9051, CR4: 0x00000000000606e0
RAX: 0x0000000000000000, RBX: 0xffffff8102a6b3e0, RCX: 0x0000000000000000, RDX: 0x0000000000000000
RSP: 0xffffff8102a6aad0, RBP: 0xffffff8102a6b270, RSI: 0x000000000000001f, RDI: 0xffffff8102a6b3e0
R8:  0x0000000000000000, R9:  0x0000000030200203, R10: 0x0000000000ff0000, R11: 0xffffff8102a6b700
R12: 0x0000000000000001, R13: 0xffffff80f3d94854, R14: 0x0000000000003440, R15: 0xffffff8102a6b700
RFL: 0x0000000000010246, RIP: 0xffffff7f810b1af5, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0xffffff80f3d9465c, Error code: 0x0000000000000000, Fault CPU: 0x1
 
Backtrace (CPU 1), Frame : Return Address
0xffffff8102a6a760 : 0xffffff8000222f69 
0xffffff8102a6a7e0 : 0xffffff80002dc19e 
0xffffff8102a6a9b0 : 0xffffff80002f3606 
0xffffff8102a6a9d0 : 0xffffff7f810b1af5 
0xffffff8102a6b270 : 0xffffff7f810abe14 
0xffffff8102a6ba80 : 0xffffff7f81029571 
0xffffff8102a6bab0 : 0xffffff7f810296de 
0xffffff8102a6bae0 : 0xffffff7f81027d05 
0xffffff8102a6bb70 : 0xffffff80006cccda 
0xffffff8102a6bb90 : 0xffffff80006cd83e 
0xffffff8102a6bbf0 : 0xffffff80006cb28f 
0xffffff8102a6bd40 : 0xffffff80002b6008 
0xffffff8102a6be50 : 0xffffff8000226bb1 
0xffffff8102a6be80 : 0xffffff80002139b5 
0xffffff8102a6bef0 : 0xffffff800021e003 
0xffffff8102a6bf70 : 0xffffff80002c921d 
0xffffff8102a6bfb0 : 0xffffff80002f3e26 
      Kernel Extensions in backtrace:
         com.apple.iokit.IOAcceleratorFamily(98.7.1)[024BF8EC-2925-3C4B-ADBB-CFE36F7D41C5]@0xffffff7f8101e000->0xffffff7f81075fff
            dependency: com.apple.iokit.IOPCIFamily(2.8)[447B4896-16FF-3616-95A2-1C516B2A1498]@0xffffff7f807fe000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.6)[38E388A5-92D6-3388-B799-F2498E582287]@0xffffff7f80b97000
         com.apple.AMDRadeonX3000(1.1.4)[1D52EEFE-BB7C-388A-A323-42EFE8A119E1]@0xffffff7f81076000->0xffffff7f81416fff
            dependency: com.apple.iokit.IOAcceleratorFamily(98.7.1)[024BF8EC-2925-3C4B-ADBB-CFE36F7D41C5]@0xffffff7f8101e000
            dependency: com.apple.iokit.IOPCIFamily(2.8)[447B4896-16FF-3616-95A2-1C516B2A1498]@0xffffff7f807fe000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.6)[38E388A5-92D6-3388-B799-F2498E582287]@0xffffff7f80b97000
 
BSD process name corresponding to current thread: Final Cut Pro
Boot args: -v npci=0x2000  slide=0 
 
Mac OS version:
13A598
 
Kernel version:
Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64
Kernel UUID: 1D9369E3-D0A5-31B6-8D16-BFFBBB390393
System model name: iMac12,2 (Mac-942B59F58194171B)
 
System uptime in nanoseconds: 158253495566

It's after starting FX Factory. In addition second monitor don't working. Kexts and library (OpenCl, openGL) are bad.

tokugawamac
tokugawamac
Posted
Posted

Hi all,

 

I've read through this thread a couple of times, and I'm still not clear whether anyone has solved the problem of flickering/having to unplug and replug on startup with an R9 290x. I have an R9 290x mostly working in 10.9.5 thanks to netkas' package with the most salient problem being the flickering, jittering and sometimes lack of image on startup. Any help would be greatly appreciated. Apologies if I'm an idiot for missing it...

zm8
zm8
Posted
Posted

I've read through this thread a couple of times, and I'm still not clear whether anyone has solved the problem of flickering/having to unplug and replug on startup with an R9 290x.

 

See my post #307 above. Although mine is an R9 290 non-X, it suffered exactly the same problems (flickering/having to unplug and replug, etc.)

 

What initially fixed it for me was the patch kindly provided by stingray_454, quoted in my post. I was then driven to figure out the Dual Link part. So I'd say give either patches a try ... IMHO the display-related issues are in most cases signs that the frame buffer settings aren't right yet.

  • Like 1
tokugawamac
tokugawamac
Posted
Posted

See my post #307 above. Although mine is an R9 290 non-X, it suffered exactly the same problems (flickering/having to unplug and replug, etc.)

 

What initially fixed it for me was the patch kindly provided by stingray_454, quoted in my post. I was then driven to figure out the Dual Link part. So I'd say give either patches a try ... IMHO the display-related issues are in most cases signs that the frame buffer settings aren't right yet.

 

 

Thanks for pointing me in the right direction! So far, stingray's solution hasn't been working for me, but I'll try looking at it more in-depth over the weekend. Thanks again!

MattsCreative
MattsCreative
Posted
Posted

the only way i have got 3 monitors working is by using my hd4000 and that has one monitor it's the main boot gpu then have the other two monitors on the 290x now the only person i know that can fix our issues is rampage dev 

thrownaround
thrownaround
Posted
Posted

My 7790 gives me a grey flickering screen and nothing else when I boot it in Yosemite. I probably need to edit the framebuffer but the information I found regarding editing the framebuffer is seeming to lose me halfway through. I don't mind doing it myself but for the life of me I can't get HDMI or DVI to work. I've been attempting for awhile now getting it to work, and have read plenty of things but somehow I can't seem to get my head around framebuffer editing and it makes me feel dumb as hell.

francescophp
francescophp
Posted
Posted

My 7790 gives me a grey flickering screen and nothing else when I boot it in Yosemite. I probably need to edit the framebuffer but the information I found regarding editing the framebuffer is seeming to lose me halfway through. I don't mind doing it myself but for the life of me I can't get HDMI or DVI to work. I've been attempting for awhile now getting it to work, and have read plenty of things but somehow I can't seem to get my head around framebuffer editing and it makes me feel dumb as hell.

Same gpu same problem

 

Are you the one from Netkas xD?

MattsCreative
MattsCreative
Posted
Posted

The 7790 is different from a 290X and thus off-topic for this topic. Since updating to 10.10.1 the patch doesn't seem to work anymore. I'll do some further testing later.

ya graphics changed in 10.10.1 and again in 10.10.2 for the better

MattsCreative
MattsCreative
Posted
Posted

How are you all monitoring your temperatures? I've heard of someone having overheated his card due to the 290x's inablility to display temperatures or change fanspeeds in Mavericks and Yosemite.

i have a hybrid bios that has unlocked voltage and sapphire tri-x oc clocks and a custom fancurve built in so my gou never goes over 75c max load

  • Like 1
MattsCreative
MattsCreative
Posted
Posted

Hi guys. 

 

Is there progress on Dual Screen on the 290X over DVI/HDMI?

 

I have a 290X that's still in the box waiting to be installed ;)

 

Thx

if you have two gpu's just use both hook one screen up to the other gpu and hook 2 screens up to the 290x 

Neo.Luxembourg
Neo.Luxembourg
Posted
Posted

if you have two gpu's just use both hook one screen up to the other gpu and hook 2 screens up to the 290x 

 

My case is to small for two cards.
 
If the situation does not change in the coming weeks, I will sell the card and wait for an alternative. I jumped to fast on unsupported hardware, will not happen again ;)
 
 
Keeping an eye one the 980/970, but hey seem to have similar problems.
 Share
Go to topic listing
×
×
  • Create New...