Samsung Odyssey Monitor Causes Kernel Panics When Connected via DisplayPort 1.4 visa Docking Station

The fix for this situation was to use a VESA certified DisplayPort 1.4 cable to connect the TS4 to the Samsung Monitor. I tried a multitude of cables and the ONLY one that worked was a VESA certified cable from Club3D - Model: CAC-2068. I can only assume the Samsung is EXTREMELY picky when it comes to cables, as everything worked flawlessly when connecting to other monitors, regardless of the cable used.

Also, for USB-C to DisplayPort, Apple Support recommended one from Plugable - Model: USBC-DP. This was said to be tested "known good". I have not tried it, but thought I'd pass that along.

Also, please note that Apple's official documentation for the 15" M2 MacBook Air states it supports up to 60hz refresh rate. I have been using it at 120hz without an issue since changing the cable.

I have not had a kernel panic or crash in a few weeks now.

I hope this helps others out there. Good luck!

After further investigation, it has become very clear this is a driver issue in MacOS.

I suspect Samsung provides the driver for inclusion in the MacOS kernel. Does anyone know which company writes the driver? What is the best way to make the owner of the driver aware of the problems?

I just heard back from my case manager with Apple Support (who has been AWESOME). For everyone's information:

Thanks for reaching out! The drivers for the display are submitted to Apple through the manufacturer of the devices themselves, unless a generic device driver is used instead. 

Since the model (and not “Generic Display”) for all Samsung displays usually show up under System Settings > Displays and under System Information > Hardware when they’re plugged in, this indicates Samsung submits updated drivers to Apple to be included in the operating system.

In short, Samsung would be responsible for the driver for your display. 

Please let me know if you need any further clarification or assistance.

You read that correctly, but with 1 caveat:

The Mac only panics when connected to the dedicated, traditional, DisplayPort 1.4 port. It does NOT panic if connected to the dock (or the Mac) via USB-C to DisplayPort (on the monitor).

Update: Spoke too soon. When connected USB-C on the TS4 to the DisplayPort 1.4 port on the monitor, the Mac kernel panicked. Same logs as before.

Also of note - if I connect USB-C on the Mac to the DisplayPort 1.4 port on the monitor, it does not panic. It does, however, continuously wake the monitor to the stand by screen until it sleeps 60 seconds later. This repeats over and over again.

You read that correctly, but with 1 caveat:

The Mac only panics when connected to the dedicated, traditional, DisplayPort 1.4 port. It does NOT panic if connected to the dock (or the Mac) via USB-C to DisplayPort (on the monitor).

A couple of additional things:

1. If I can make the monitor stop turning on and off constantly I will accept the work around of having to connect the monitor with a USB-C (MacBook Air) to DisplayPort 1.4 (Samsung Odyssey Monitor).
2. The only stable connection I have had any success with is Belkin USB-C to HDMI dongle, and then HDMI cable to the monitor. I hate the loss of higher refresh rates, and the fact I have to use a dongle.
3. I would like to use the dock as intended.

More details that may provide clues:

When using DP1.4 the monitor does not power down. I realize most Samsung TVs do not completely power off unless the power button is held down on the remote, but this is a monitor, and I expect different behavior.

When I press the power button normally to power off the monitor while the MacBook is connected, the monitor remains detected as a connected device extending the desktop.

With the monitor "powered off," if the last input was set to DisplayPort, it will not power on normally. I can barely make out the window animation of the monitor "powering on/off" when I press the power button on the remote, but it never goes beyond a completely black/blank screen. The only way to get the monitor back to normal function is to hold down the power button on the remote control.

None of these problems occur when using HDMI, but I lose the faster refresh rates and other color benefits I get when using DP1.4. Not to mention I just want the product I purchased to work properly.

Do these new developments suggest hardware issues? Software? Both?

I am going to contact Support again and confirm Apple owns the driver, and that the dev team has been made aware of the issue. I'll report back what my findings.

Thanks!

That has not worked for me. In fact, I'm just watching the MacBook repeatedly crash when sleeping and then waking itself up. Over and over again. So frustrated.

Good luck!