Behavior: Kernel Panic when waking from sleep, ONLY when connected to the TS4 via DisplayPort. Crashes vary from simple restarts to Recovery screens requiring reinstallation of the OS. When connected directly to the MacBook via USB-C cable, the laptop does not panic but the monitor constantly power cycles through the standby screen. Intermittently, when powered off while using DisplayPort input, monitor will not power on unless I hold down the power button on the remote.
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 has "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.
Thanks for responding! Appreciate it. Some points of clarification:
The CalDigit TS4 and M2 MacBook Air are both TB4. Wouldn't a TB4 cable work? Or do I need a TB3 cable? I've actually used a TB4/USB4 to DP1.4 cable with the same problems - kernel panics when connected to the CalDigit TS4, and constantly power cycles the monitor when connected directly to the Macbook. But I'm willing to try a TB3 cable if it would make a difference.
However, the CalDigit TS4 has a full size, traditional, DP 1.4 port on the back, and when I connect DP1.4 to DP1.4 the Macbook is guaranteed to crash upon wake. These are exactly the same ports, not dissimilar. Something is wrong with the DP on the monitor. See here: G7 Monitor Not Detecting DisplayPort - Samsung Community
I bought the items together as there was no mention of incompatibility, and with the MacBook Air limited to only 1 external display, this 43" display seemingly fit the bill. The monitor is also connected to a dual-boot workstation with Windows and Linux via HDMI. As described, this monitor should be great for my use cases.
I've seen the same Reddit threads, but upon a deep dive with their support team, I do not believe the docking station is the issue. I honestly believe Samsung needs to solve a software bug, but I'm willing to listen to any and all reasonable suggestions.
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?
This has to be a driver issue. Which company provides the driver for these monitors? Since upgrading to MacOS 15, the MacBook now crashes when it wakes from sleep connected via HDMI (used to be my workaround), and the monitor is set to 4k. It has not crashed (yet) if the monitor is set to 1080 or 1440. I have not tested if the monitor crashes over DP1.4 when the resolution is set below 4k yet.
When speaking to a "Big-A" Support representative, they said Samsung provides the driver to them for inclusion in the OS. Can anyone please confirm if that is true?
I just heard back from my case manager with "Big-A" Support (who has been AWESOME). For everyone's information:
Thanks for reaching out! The drivers for the display are submitted to "Big-A" 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 "Big-A" 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.
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. Also, for USB-C to DisplayPort, A-Support recommended one from Plugable - Model: USBC-DP
I have not had a kernel panic or crash in a few weeks now. I hope this helps others out there. Good luck!
