Displaylink ceases to work in 10.13.4

[roadtest]

I am new Mac user and just purchased this new MacBook Pro(2.9G I7 with 16GB DDR3 memory/dual graphics(Intel HD graphics 630 and Radeon 560). Laptop is connected to a USB3.0 dock station with two DVI ports.

After installing the latest macos update and reinstall DisplayLink driver 4.1.11. My two monitors are working fine. Then I disconnected laptop, work somewhere else for few hours, then came back, reconnect to the USB dock. Both monitors has no output. Reboot laptop doesn't make any difference. I have to uninstall the driver and reinstall it. From what I can see after driver installation, all three monitors(two external monitors and one built one) are using Intel HD graphics 630 card. After I disconnect/reconnect the USB dock, it reports Radeon 560 is being used, as a result, all output to the two external monitors. Other than reinstalling the driver, I haven't figured out way to choose graphic card.

I did try to reload the DisplayLink driver without reinstallation. The "kextunload/kextload" complains there already has one instance using the driver and doesn't allow me to unload driver from cli, which is strange behavior.

[njoerd]

I can confirm that the problem persists in Beta 2. Had to uninstall the displaylink driver completely to not go insane since my integrated screen got glitchy and flickery after installing beta2.

[toastido]

It's been what, 3 weeks now, and all I've heard is that they believe they have identified the issue and hope to have it resolved shortly.

DisplayLink guys - please let us know what's going on here. Some of us rely on your technology for our business and it's difficult to go without.

That being said, if you have a beta driver, I for one would be glad to test it for you.

Thanks!

[aehsmu]

I echo the sentiments of users frustrations.

I currently have 4 Macs that are hobbled due to the broken DisplayLink driver.

Being a developer myself, I understand the problems related to OS changes.

However, a reply to this thread from DisplayLink folks would be helpful.
--
Eric H.
--

[RGloverii]

While we are all currently impacted by this issue, I think it’s important to note that we have caused this issue ourselves by installing an Apple BETA product on presumably PRODUCTION machines. That is a risk, and we are now suffering the result of that risk.

I can not fault DisplayLink for not providing a fix yet. That is the point of developer betas. To flesh out incompatibilities and resolve before general release of the update.

[toastido]

Originally Posted by RGloverii

While we are all currently impacted by this issue, I think it’s important to note that we have caused this issue ourselves by installing an Apple BETA product on presumably PRODUCTION machines. That is a risk, and we are now suffering the result of that risk.

While I can appreciate what you are saying, nobody is blaming DisplayLink for the issue. We're just pushing to get it fixed. (Besides, if apple were to release 10.13.4 to the public today, it'd still be broken.)

Originally Posted by RGloverii

I can not fault DisplayLink for not providing a fix yet. That is the point of developer betas. To flesh out incompatibilities and resolve before general release of the update.

Again, we're just anxious to get the fix. I have even offered to test a "beta" fix to see if it works outside of a lab environment for them.

Another thing to note, is that most developers (like myself) keep up to date with developer/public betas so we can do just that, flesh out incompatibilities and resolve before GA. That is why we would have installed it on "production" machines.

Not blaming anyone, or even getting mad; Just requesting updates to this issue.

[RGloverii]

I think that DisplayLink tends to be more open and communicative regarding issues and status than most established vendors. And I appreciate that.

Yes, this incompatibility is inconvenient to all of us on this thread. And it goes without saying that we would like to see a fix ASAP. I simply don’t see any need to further impress upon DisplayLink that we want a fix. They are well aware of the need for a fix. Not only for us on this thread, but for ALL consumers of their products.

As for potential DisplayLink beta releases: This is something they already do. They are made public when available for testing.

I hope I don’t come across as being rude. That’s not my intent. I’m just providing my thoughts as someone who has utilized their products both personally and professionally for a long time.

[aehsmu]

Originally Posted by njoerd

I can confirm that the problem persists in Beta 2. Had to uninstall the displaylink driver completely to not go insane since my integrated screen got glitchy and flickery after installing beta2.

Installed beta 3 this morning and then re-installed DisplayLink 4.1

I now see no signal, flicker, or any sign of life on the connected monitor.
--
Eric H.
--

[Alanant]

Originally Posted by aehsmu

Installed beta 3 this morning and then re-installed DisplayLink 4.1

I now see no signal, flicker, or any sign of life on the connected monitor.
--
Eric H.
--

Same experience for me on Beta 3.

[slvrscoobie]

Originally Posted by bkgryl33

Like all on this thread I updated to High Sierra and now my AOC monitor is rendered useless. Display Link team we need YOU to get a solution. Registering a bug with Apple is not going to make anything happen. Please help.

Then roll back your OS to the last STABLE version. We all run Betas knowing there could be issues. this is one of them. Dont get feisty with DisplayLink because your running beta software they got the same time you did, and things arent working properly. If this is a major issue, use the Stable release where Displaylink works properly. These are designed for DEVELOPER machines, you know like the ones at Displaylinks office.