Jump to content
473 posts in this topic

Recommended Posts

  • 2 weeks later...

 

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.

 

My 980 works on all ports except HDMI. 4 display outputs is still quite enough for me though. Later this week I will be attempting to get HDMI working with NVCAP. Most 980s (and a lot of the 970s, including the Gigabyte one) it seems the only port that doesn't work is the HDMI.

My 980 works on all ports except HDMI. 4 display outputs is still quite enough for me though. Later this week I will be attempting to get HDMI working with NVCAP. Most 980s (and a lot of the 970s, including the Gigabyte one) it seems the only port that doesn't work is the HDMI.

keep on topic please this isnt about nvidia it's 290x only 

Apologies if this is a silly question, but does anyone know if the new Catalyst Omega drivers in Windows affect anything hardware/firmware-wise (i.e. could it affect compatibility on the OS X side)? I noticed on the release notes it says:

 

  • This driver is not intended for use on AMD products running in Apple Boot Camp platforms. Users of these platforms should contact their manufacturer for driver support

Maybe the new drivers are just not compatible with the GPUs that normally come with real macs? Anyway, thanks!

  • 4 weeks later...

Don't know, I will try to do some research this weekend

i have the framebuffer loaded with ozmosis but i still only have a single monitor unless i also use hd4000 

I've tried the different framebuffers Ultimatebadass posted in Clover and none of them work for DVI-DL even though the framebuffers *should* be correct after analyzing and comparing to my own results. I'm beginning to wonder if this just isn't a bug in 10.10.0/10.10.1. I'm waiting for 10.10.2.

I've tried the different framebuffers Ultimatebadass posted in Clover and none of them work for DVI-DL even though the framebuffers *should* be correct after analyzing and comparing to my own results. I'm beginning to wonder if this just isn't a bug in 10.10.0/10.10.1. I'm waiting for 10.10.2.

the 290x and 290 only have a single framebuffer in the 8000.kext 

https://drive.google.com/file/d/0B3y5hldpEFDYOXdQTDFlMWJtejA/view?usp=sharing i binary patched the 8000 kext all you need for clover is inject ati with the frambuffer name it works on 10.10.1 and 10.10.2

for people using oz after installing the kext go into term and type sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:AtiFramebuffer=Baladi then reboot you will have two monitors working with the framebuffer loaded to have a 3rd monitor use your igpu

The modified kext kinda works. But there's tons of graphical corruption and overall laggy performance, especially with boot and moving the mouse.

you have the 290? i made this for the 290x

https://drive.google.com/file/d/0B3y5hldpEFDYSmRXa2ZYVHg4eEU/view?usp=sharing another patch for our beloved 290x this will make the card faster and run right giving it a huge fps boost

Unfortunately (and not surprisingly) the patch doesn't do anything for me. Why oh why did I have to choose the 290X with the custom PCB?!? Maybe it's time I concede and just buy a damn Nvidia card.

it's for performance only 

https://drive.google.com/file/d/0B3y5hldpEFDYdUhXbVBMaVlmdkk/view?usp=sharing another patch for our beloved 290x this will make the card faster and run right giving it a huge fps boost

 

Hi, thank you for all your contributions! I had Netkas' package from back in June installed, and using you kext didn't change anything. That being said, I don't think my numbers have been particularly low.

 

Before/After:

LuxMark v2.1 Sala: 2902 / 2927

Cinebench R15: 76.70 / 76.49

×
×
  • Create New...