Displaylink ceases to work in 10.13.4

[gpsutter]

Originally Posted by gpsutter

It works for me.

Sorry, my comment got separated. I was referring to clamshell mode, which works for me. At least I don't have to stare at a dead monitor.

[tommiy]

If I am not mistaken its been 12 days since any official word from DisplayLink on this matter. Its really beginning to look like these are now toast. Even over in the apple support thread the focus is on finding different solutions rather than holding out that Apple will assist to fix this. I don't think anyone thinks that Apple even wants to try to support those that created a separate industry that assisted in use of its devices in cross platform environments. Anyway, I've had to jettison my DisplayLink dock and go to an elgato due to the fact there is no known date when this will be fixed and no comms from DisplayLink on any kind of progress.

[Alanant]

10.13.5 Beta 2 does not fix the issue.

[paulgee31]

Originally Posted by tommiy

If I am not mistaken its been 12 days since any official word from DisplayLink on this matter. Its really beginning to look like these are now toast. Even over in the apple support thread the focus is on finding different solutions rather than holding out that Apple will assist to fix this. I don't think anyone thinks that Apple even wants to try to support those that created a separate industry that assisted in use of its devices in cross platform environments. Anyway, I've had to jettison my DisplayLink dock and go to an elgato due to the fact there is no known date when this will be fixed and no comms from DisplayLink on any kind of progress.

We've been here many times before. It takes time, often weeks before a set of drivers are released that offer a fix or partial fix but considering I've been using the same DisplayLink device since 2011 I can't complain about the support.

[strim]

I agree, DisplayLink is trying their best. They created 4.3 beta to clone displays pretty quickly. With adjusted screen resolution that provides workaround for me. Likely the proper solution depends on Apple side, while Apple seems to care not too much of the issue.

[tommiy]

Yes agree they may try their best but its now 3 months since the start of this thread and in that time there has been minimal information from DisplayLink on any progress. Thats a quarter of a year. If they can not manage to get any prospect that are worth informing people about in 12 weeks then I can not hold my breath for another 12 weeks to return to having multiple dislays. I had to purchase something else. It was my choice I agree but the lack of support engagement drove me there.

[Poly]

Originally Posted by tommiy

If they can not manage to get any prospect that are worth informing people about in 12 weeks then I can not hold my breath for another 12 weeks to return to having multiple dislays. I had to purchase something else. It was my choice I agree but the lack of support engagement drove me there.

You're getting a bit overemotional here, but it's totally understandable. As a private person at home you have more options to choose from, in enterprise environments you have to stick with the approved hardware a while longer, which is even more frustrating.

My guess is that without Apple support there is no easy way to fix this. Hopefully, with the final release of 10.13.5 both parties i.e. DisplayLink and Apple, will have sorted it out. I'm still on 10.13.3

There is one positive thing I noticed with the latest beta driver. It seems audio is now being directly delivered via HDMI, no need to plug in AUX jack separately. If only HDCP would have also worked eventually... But you still can't watch any HDCP protected movies via DisplayLink. *gasp*

[tommiy]

Actually I think I understand how I feel and I am not getting over emotional. I was over emotional when this became an enterprise issue and the company I worked for decided that this was the straw that broke the camels back and now no longer supports Macs within the environment at all. You see there was nothing publised in release notes by Apple that upgrading would break anything and so the extra work to rollback alot of Macs resulted in getting given a windows machine instead. They waited a couple of weeks and then decided that they could not continue on without support of knowing it would be corrected and the easiest, fastest, and cheapest solution was to get rid of Macs.

So, its at home now, becoming less of a work horse into a home use only paradigm. This seems to be what apple wants.

So not over emotional at all. I now have a windows machine for work that functions with DisplayLink even after microsoft push out updates. It also has USB-C ports so my Apples accessories function with it. My only loss is needing to use windows during a working day.

Originally Posted by Poly

You're getting a bit overemotional here, but it's totally understandable. As a private person at home you have more options to choose from, in enterprise environments you have to stick with the approved hardware a while longer, which is even more frustrating.

My guess is that without Apple support there is no easy way to fix this. Hopefully, with the final release of 10.13.5 both parties i.e. DisplayLink and Apple, will have sorted it out. I'm still on 10.13.3

There is one positive thing I noticed with the latest beta driver. It seems audio is now being directly delivered via HDMI, no need to plug in AUX jack separately. If only HDCP would have also worked eventually... But you still can't watch any HDCP protected movies via DisplayLink. *gasp*