Mac Pro Late 2013 and Samsung 4k monitor problem

I have the new Samsung 28" 4k screen (U28D590D) and it has tearing along the right edge when used with displayport. Any way to fix that? I tried different cables (all DisplayPort 1.2 complient) to be sure and have narrowed the issue to the Mac Pro. The HDMI works fine tho only @30hz so is a bit laggy in normal interaction. There is no way to turn on Multi-stream as indicated and I hope it isnt that this screen will never work.

Mac Pro, OS X Mavericks (10.9.2), Dual Fire Pro D700

Posted on Apr 11, 2014 2:12 PM

Reply
Question marked as Top-ranking reply

Posted on Oct 1, 2014 10:44 PM

Good news! I have this same issue running 10.9.5. But I installed the golden master (build 14A379b) of Yosemite tonight and my Samsung displays perfectly @60hz at all resolutions! FINALLY! Yosemite should be out in just a few more days so rest easy Samsung U28D590D owners! Relief is on the way!

330 replies

Jul 3, 2014 7:21 AM in response to orrbain

I was able to get it working at the native resolution at 50hz using the resolution switching utility. However, as others have noted working at a native 4K resolution makes things a bit too small for comfort, and there doesn't appear to be any way to create a scaled resolution using a custom "base" resolution. So at this point while it's nice to know that we can get it working at 50hz, until Apple enables that functionality themselves or fixes it to work at 60hz, we're pretty much stuck operating at 30hz for all "practical" purposes...

Jul 3, 2014 10:11 AM in response to Kremmel

Kremmel, the name of the file should be DisplayProductID-28a2, not DisplayProductID-32a2. (Note: 32a3 is the ASUS PQ321 which is an older 4K MST monitor; I don't know what a 32a2 is).


I don't think the <data> contents needs to be on one line. It uses base64 encoding to encode the binary data. I think base64 will skip spaces, tabs, and newlines. If you want it on one line, then you can open the file in a text editor.


Orrbain, It's possible the PB287/28a2 and PB287Q/28a3 products might be the same monitor with different EDIDs. They have different preferred timings as I mentioned before, where the PB287 does not use a CVT-RB timing but the PB287Q does. If the PB287 does not like the 50 Hz CVT-RB timing but the PB287Q does, then it means their hardware (not just the EDID) is also different and we need a new EDID for the PB287.


As stated before, the reason why we're editing the EDID is to make a custom "base" resolution for scaled resolutions by editing the preferred timing. You can use SwitchResX to find a timing that makes your monitor work, but you have to use an override file to override the EDID to set the new timing as the "base" resolution.


So post your working timing and I'll post an EDID. If you can get a better timing in Windows, then post that too.

Jul 15, 2014 1:51 AM in response to chriskuta

chriskuta wrote:


I'm hoping someone can confirm that using a DisplayPort 1.2 compliant cable fixes this tearing on the right hand side of the screen on the Samsung U28D590 on Late 2013 Mac Pro (AMD FirePro D500)? I'm stumped why my existing cable works fine with my Late 2013 MBP on this very display.


You need a good Mini DisplayPort to DisplayPort 1.2 cable AND you need to use the custom EDID / timings that have been discussed from page 6 onwards in this thread.

Jul 16, 2014 1:19 PM in response to Terscion

pacioccone wrote:



I spoke with Apple Care who had a response from engineering regarding this thread and the bugs referenced in the thread. Engineering is putting this back on Samsung and stating this has nothing to do with Apple. Why would this be Samsung's issue? 😐


It's not a Samsung issue if it works in Windows. Has Engineering or anyone in this thread tried one of these 4K 60 Hz SST monitors in Boot Camp on the same Mac? If it works in Windows but not in Mac OS X, then it's a Mac OS X driver problem.


Terscion wrote:


Most people on this forum seem to be using the Samsung U28D590D or the Asus PB287Q, but since their release, a few other 4K monitors are on the market. Was wondering if anyone here has any experience with using the following monitors with the new Mac Pro?


Viewsonic VX2880ml

Philips Brilliance 288P6LJEB

AOC U2868PQU

Lenovo Thinkvision Pro 2840m


I can't tell if those monitors are SST or MST. The Samsung U28D590D or the Asus PB287Q are SST. Any SST monitor should just work (except for this AMD issue) since they are like normal monitors except with higher bandwidth. I don't know how MST monitors work in Mac OS X - whether or not Apple has to add support for each MST monitor, or if the driver can detect that the monitor requires MST and work with that. If Apple needs to add support for each MST monitor, then maybe we can figure out how that's done and add support ourselves, or maybe the EDID can be edited to make it appear as a supported MST monitor.

Jul 21, 2014 9:19 PM in response to joevt

Hi joevt,


I messed with SwitchResX for a while and discovered that this setup (nMP, OSX and SST 4k) is just not ready to go past 54 hz. at full resolution without the picture overlap. I expect that we will see some improvements in SST 4k drivers and support in the near future. For now I will work with 54 hz. using the override file that you supplied.


The problem appears to be limited to the D500 and D700 which are based on the Tahiti AMD GPU engine where the D300 (appears to be working fine) is based on the Pitcairn AMD GPU engine, maybe this is a coincidence or a helpful hint to a solution. Also, the monitor suppliers need to work closely with Apple and AMD to get this fixed to better support SST technology as it appears to be here to stay.


I may be putting Windows on the Mac Pro but I was holding off, trying to migrate all my work under OSX. At least for now, a 90% solution is here thanks to you.

Aug 11, 2014 6:06 PM in response to joevt

joevt,


Sorry I didn't get back to you sooner. I have one of those jobs that drags me away from technology every now and then. Thanks for your assistance, it has been a great learning experience.


I eventually got it working at 50Hz on the PB287Q without any problems and then a friend advised that the latest Yosemite build had "fixed" the problem so I deleted all my override files, installed the update and now I can run at either 50Hz or 60Hz on the PB287Q without any problems.


I can confirm that owners of the D300 builds have not had any problems (as we have two at work).


Thanks everyone for your help!

Aug 12, 2014 3:54 PM in response to trace101

60Hz seems to be the problem with the 500 and 700's. Try the method mentioned in this thread. My Samsung is working great at 30Hz on HDMI or 50Hz on DP.


Hopefully there will be an Apple provided plist or driver.


This is what I ended up doing.



—————



1 - Go to Launchpad and start Terminal.


2 - type "sudo -s" and input your password.


3 - type "cd /System/Library/Displays/Overrides/DisplayVendorID-4c2d/".


4 - type "pico DisplayProductID-b80"


5 - copy and paste this inside:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>DisplayProductID</key>

<integer>2944</integer>

<key>DisplayVendorID</key>

<integer>19501</integer>

<key>IODisplayEDID</key>

<data>AP///////wBMLYALAAAAADQXAQS1PSN4Ol+xoldPoigPUFS/74BxT4EAgcCBgKnAswCVANEAq KwAoPBwM4AwIDUAX1khAAAaVl4AoKCgKVAwIDUAX1khAAAaAAAA/QAySx6GNgAKICAgICAgAAAA/ABV M jhENTkwCiAgICAgAXkCAwzwIwkHB4MBAAACOoAYcTgtQFgsRQBfWSEAAB4AAAAAAAAAAAAAAAAAAAAA A AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA A AAAAAAAAAAAAAAAAAAAAAAAAAAAlw==</data>

</dict>

</plist>

Press Control + X, then y


6 - Reboot, or turn off and change the cable if you're using HDMI, and you're all set.


-------



I hope it helps.


-Chris

Oct 3, 2014 9:35 AM in response to seminolefans

I don't know abut others but my experience has been a good one. As soon as I installed Beta 2 the problem went away. and now that we are at Beta 4, it is still working great.


I worked on making Mavericks work by editing the display files and got 54hz without tearing. but I found a little choppy when I moved windows around.


I hope that others have the same positive experience with Yosemite.

Apr 11, 2014 4:57 PM in response to digitalcoleman

An additional confirmation of it likely being a driver issue - I used the same cable and the same 4k monitor with my MBP (late 2012) and it runs the full native resolution perfectly, no artifacts or errors at all. Because I recieved these a full week before their release date, im not that surprised or worried, but for those considering the screen, it does not seem to be fully supported yet.

May 18, 2014 12:11 PM in response to jimfromarlington

Apple completely lost the ball on this one.. That the new Mac Pro does not support SST 4k/60Hz after 10.9.3 is not acceptable. It´s also not acceptable that they have not updated the HDMI 1.4 to 2.0 for HDMI 4K/60Hz support. As 1.4 and 2.0 are identical hardware wise, this should be as simple as update the firmware.


I know several users from reduser.net who have bought *several* 4k monitors, only to learn one by one that they are left out cold for 4k/60Hz. Apple appears to only support a very limited range of 4K displays with MST, which by itself is buggy and a "hack" to make 4K show up. SST should have been implemented from the get-go.


There are a lot of people who are incredibly frustrated about this, and feel the investment in nMP has been a waste as we are stuck on 4k/30hz with most monitors/tvs.


Apple has to fix this now. 10.9.3 was suppose to be the 4K update to settle things. It has done very little to add more support.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Mac Pro Late 2013 and Samsung 4k monitor problem

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.