Displaylink ceases to work in 10.13.4

[anderslu]

No external screens visible in macOs here as well.

Using a MacBook Pro 15-inch, 2017
2.8 GHz i7
16GB RAM
Intel HD 630 / AMD Radeon Pro 555
Targus DOCK177USZ
2x Lenovo T2334pA monitors

[slvrscoobie]

same here, one displayport monitor working fine, displaylink is all yellow, but i do see the mouse cursor.

[bhlc]

I also saw a yellow screen on the monitor connected through a du3200 after installing 10.13.4 beta. It was also affecting my MacBook pro's built in monitor. I tried reinstalling the DL driver, which fixed the issue with the built-in display, but now the external monitor isn't seeing a signal.

MacOS 10.13.4 Beta (17E139j)
MacBook Pro (Retina, 15-inch, Late 2013)
2.3 GHz Intel Core i7
16 GB 1600 MHz DDR3

[M. Holkamp]

After installing the 10.13.4 beta i saw the screens, than it turned yellow.
I removed the driver and installed the latest version.
Now i don't see the extrenal monitors.

I have attached the result of the DisplayLink info tool.

[anthony.gelibert]

On my side, kernel panic at each startup.
I had to boot in "safe mode" to be able to access to my system.

MacBook Pro 15" (end 2013).

[russjr08]

Originally Posted by anthony.gelibert

On my side, kernel panic at each startup.
I had to boot in "safe mode" to be able to access to my system.

MacBook Pro 15" (end 2013).

I am having the exact same issue MBP 15" Mid-2012. Stacktrace didn't point toward a display link kext though, just the default Apple graphics one.

[toastido]

I too have this issue. The lemon screen. After 10.13.4b1.

I've tried:
1) rebooting
2) manually pulling the kext (that didn't end well)
3) uninstall the driver/reinstall the driver
4) uninstall the 4.1 driver, install 4.0 driver (didn't even see the adapter anymore)
5) uninstall 4.0, reinstall 4.1 (back to lemon-lime monitor)

It's annoying AF, and needs to be resolved soon.

Mac specs:
2012 13" MacBook Pro w/i7 2.9ghz, 16gb ram, 1TB ssd


See attachments for what it looks like.

[Alanant]

DisplayLink team, would you have an update on this issue? I understand that Apple have caused the problem, which is likely related to eGPU support, and that it is a beta after all but it would be good to know if you guys are on top of it and are planning to release a version of your software that takes into account the changes. Thanks!

[justaskingaquestion]

I have one of the newest MBP 15in with TB3 ports, and I've been sticking with MacOS 10.13.3 ever since this problem emerged for fear of losing my display. Looking into it again, I see some confusing reports about whether this problem only exists for older models or if it is an issue for me as well. Can somebody help clarify?

I have

2017 MBP 15in with 4 TB3
Dell P2715Q 4k display, though I've been running it at 2560x1440 because everything is too small otherwise (I've only ever connected to this display via DisplayLink so I don't know if directly connecting gives me any more flexibility here)
I also use DisplayLink for mouse/keyboard/ethernet
I used to use DisplayLink for audio, though I've found that to be a very poor quality connection, especially when the computer is doing any heavy lifting.

With this setup, if I upgrade to 10.13.4 or later, will I still have to use the workaround via AirDisplay? If so, will I be able to use 2560x1440?

If I am limited to 1080p, does anybody have any recommendations for alternate hardware/hubs that can meet my needs in newer MacOS? When I bought this late last year I thought DisplayLink was the ticket, but maybe not?

[Poly]

Originally Posted by justaskingaquestion

I have one of the newest MBP 15in with TB3 ports, and I've been sticking with MacOS 10.13.3 ever since this problem emerged for fear of losing my display. Looking into it again, I see some confusing reports about whether this problem only exists for older models or if it is an issue for me as well. Can somebody help clarify?

I have

2017 MBP 15in with 4 TB3
Dell P2715Q 4k display, though I've been running it at 2560x1440 because everything is too small otherwise (I've only ever connected to this display via DisplayLink so I don't know if directly connecting gives me any more flexibility here)
I also use DisplayLink for mouse/keyboard/ethernet
I used to use DisplayLink for audio, though I've found that to be a very poor quality connection, especially when the computer is doing any heavy lifting.

With this setup, if I upgrade to 10.13.4 or later, will I still have to use the workaround via AirDisplay? If so, will I be able to use 2560x1440?

If I am limited to 1080p, does anybody have any recommendations for alternate hardware/hubs that can meet my needs in newer MacOS? When I bought this late last year I thought DisplayLink was the ticket, but maybe not?

Of course you can connect your 4k display directly to the Mac either via TB3-to-DisplayPort or TB3-to-HDMI dongle. It gives you more flexibility and probably a higher refresh rate at 60Hz if you choose DisplayPort. Adapters can be purchased from Apple or 3rd party vendors via an online shop of your choice.

If you upgrade to 10.13.5 (.4 is deprecated) and you still want to connect your monitor via DisplayLink then you won't be able to run your screen at 4k or hi-dpi scaled resolutions (e.g. 2560x1440). The current beta driver is a poor workaround and provides only two inferior options, clone mode and extended (2nd) AirPlay display that is limited to 1080p – a terrible resolution choice for a 4k display. Other ports such as USB, Ethernet and audio won't be affected after upgrade.