DisplayPort Signal Issue with Samsung Monitor.

Danish297

Member
AMD OS X Member
Oct 26, 2021
89
2
13
8
CPU:
AMD 3950X
Hi All,

I recently purchased a new monitor (Samsung LS24A600UCMXUE), which comes with three ports: HDMI, DisplayPort (DP), and USB-C. While HDMI works perfectly, I encounter the message "No Signal - DisplayPort" when using the DP connection.

Here are the observations:
1. The signal is frequently lost for 30–40 seconds before stabilizing.
2. My GPU (Asus Radeon RX 6800XT) does not have a USB-C output option.
3. I need to use the DP connection to get sound output from the monitor.
4. The HDMI cable works without any issues.
5. Signal loss with DP occurs multiple times, causing disruptions for 30–40 seconds.

Any suggestions or help to resolve this issue would be greatly appreciated.
 
Hi All,

I recently purchased a new monitor (Samsung LS24A600UCMXUE), which comes with three ports: HDMI, DisplayPort (DP), and USB-C. While HDMI works perfectly, I encounter the message "No Signal - DisplayPort" when using the DP connection.

Here are the observations:
1. The signal is frequently lost for 30–40 seconds before stabilizing.
2. My GPU (Asus Radeon RX 6800XT) does not have a USB-C output option.
3. I need to use the DP connection to get sound output from the monitor.
4. The HDMI cable works without any issues.
5. Signal loss with DP occurs multiple times, causing disruptions for 30–40 seconds.

Any suggestions or help to resolve this issue would be greatly appreciated.
@CaseySJ @Edhawk @Shaneee @leesurone can you please help me to fix it.
 
  1. Which type of connection and cable were you using before you obtained the new Samsung display?
  2. Are you using a good quality, fully functional DP to DP cable, i.e. no kinks or bends affecting either end?
  3. Have you unplugged and plugged both ends of the DP cable in to their respective connectors on the Hack and display? Ensuring they are fully seated in their connectors.
  4. Have you tried using a different DP cable?
  5. Have you tried using a different DP out connector from the RX 6800 XT?
 
What version of DP is the monitor? Does the cable match? I've seen it before when the DP cable is an older spec version and won't work on a newer DP revision.
 
  1. Which type of connection and cable were you using before you obtained the new Samsung display?
  2. Are you using a good quality, fully functional DP to DP cable, i.e. no kinks or bends affecting either end?
  3. Have you unplugged and plugged both ends of the DP cable in to their respective connectors on the Hack and display? Ensuring they are fully seated in their connectors.
  4. Have you tried using a different DP cable?
  5. Have you tried using a different DP out connector from the RX 6800 XT?
  1. Which type of connection and cable were you using before you obtained the new Samsung display? HDMI which was working fine.
  2. Are you using a good quality, fully functional DP to DP cable, i.e. no kinks or bends affecting either end? I checked with my TV cable is good.
  3. Have you unplugged and plugged both ends of the DP cable in to their respective connectors on the Hack and display? Ensuring they are fully seated in their connectors. I'm not using any connector. DP cable only.
  4. Have you tried using a different DP cable? NO
  5. Have you tried using a different DP out connector from the RX 6800 XT? YES
 
What version of DP is the monitor? Does the cable match? I've seen it before when the DP cable is an older spec version and won't work on a newer DP revision.
I tested both DP versions 1.1 and 1.2, as supported by my monitor.
 
Sounds like the ‘Auto Switching’ feature on the display is not working properly. The display should automatically switch to the new connection when you plug in the DP cable.

I am assuming that you don’t have a HDMI cable connected at the same time, which might cause the auto function to prioritise the HDMI connection over the DP connection.
 
Sounds like the ‘Auto Switching’ feature on the display is not working properly. The display should automatically switch to the new connection when you plug in the DP cable.

I am assuming that you don’t have a HDMI cable connected at the same time, which might cause the auto function to prioritise the HDMI connection over the DP connection.
Yes, I have an HDMI cable for another machine with a single monitor. I also tried using a single DP cable, but the issue persists.

Could it be related to a setting in the config.plist file or a missing kext?
 
Could it be related to a setting in the config.plist file or a missing kext?
No.

It will most likely be an issue related to the DP cable.

Look at purchasing a new high end DP cable, and use the DP cable with no other cables connected to the display, other than power. Then connect any USB or HDMI cables to see which if any cause the issue to reoccur. I use the DP cable linked below.

 
Last edited:
No.

It will most likely be an issue related to the DP cable.

Look at purchasing a new high end DP cable, and use the DP cable with no other cables connected to the display, other than power. Then connect any USB or HDMI cables to see which if any cause the issue to reoccur. I use the DP cable linked below.

thnx will try with diff DP cable.
 
The DisplayPort connection from my Z390 Designare to a 4K mini-LED monitor also blanks out every once in a while for about 3-5 seconds, but there’s a KVM switch between the computer and monitor. I don’t experience these black outs on two other systems connected via the same KVM. The Designare has a 6600XT GPU whereas the others have 6800.

The blanking issue is rather infrequent so I’ve not attempted to troubleshoot it. The first four factors I would vary are (1) changing resolution and refresh rates, (2) removing KVM switch, (3) using different DP cable, (4) using different monitor.
 
The DisplayPort connection from my Z390 Designare to a 4K mini-LED monitor also blanks out every once in a while for about 3-5 seconds, but there’s a KVM switch between the computer and monitor. I don’t experience these black outs on two other systems connected via the same KVM. The Designare has a 6600XT GPU whereas the others have 6800.

The blanking issue is rather infrequent so I’ve not attempted to troubleshoot it. The first four factors I would vary are (1) changing resolution and refresh rates, (2) removing KVM switch, (3) using different DP cable, (4) using different monitor.
let me try this too.
 
I have experienced connection issues over DP between a 6800XT (saphire Nitro+) and a Samsung ultra-wide monitor LC34H892WJUXZG : DP looses signal at startup or the monitor takes ages to turn on after waking up the Hack.
It happens mostly at startup when the video signal is tuned off and on: after the Bios, while OC is loading or when macOS is loading the graphic card drivers. It's like they do not detect each-other. Most of the time I can remote access the Hack which is running at the minimum resolution like if I booted headless.

I tried multiple certified DP1.4 cables. The workaround was to turn on the monitor before waking up the Mac or turning it on.
I write "was" because since I updated to OC 1.0.2, mac OS 14 and WhateverGreen 1.6.9 things have improved. Maybe it is because I did a CMOS reset of the logic board in the process though...

Another reason DP won't work is when I connect my Macbook to the USB-C input first and then switch input to the PC connected over DP. The DP input stays blank regardless if the Hack booted Windows or macOS.
So I tend to blame a dodgy Samsung firmware, you get what you paid for.
 
  • Like
Reactions: leesurone
I have experienced connection issues over DP between a 6800XT (saphire Nitro+) and a Samsung ultra-wide monitor LC34H892WJUXZG : DP looses signal at startup or the monitor takes ages to turn on after waking up the Hack.
It happens mostly at startup when the video signal is tuned off and on: after the Bios, while OC is loading or when macOS is loading the graphic card drivers. It's like they do not detect each-other. Most of the time I can remote access the Hack which is running at the minimum resolution like if I booted headless.

I tried multiple certified DP1.4 cables. The workaround was to turn on the monitor before waking up the Mac or turning it on.
I write "was" because since I updated to OC 1.0.2, mac OS 14 and WhateverGreen 1.6.9 things have improved. Maybe it is because I did a CMOS reset of the logic board in the process though...

Another reason DP won't work is when I connect my Macbook to the USB-C input first and then switch input to the PC connected over DP. The DP input stays blank regardless if the Hack booted Windows or macOS.
So I tend to blame a dodgy Samsung firmware, you get what you paid for.
Same issue even after upgrading my Samsung monitor firmware :confused:
 
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.