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.:eek:

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.

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.

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!

Multiple installations
 

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.
--

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.

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.)

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.

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.

I too appreciate the transparency from DL. It's a rare thing and much appreciated. Since this thread seems to have received the most participation in users sharing their configs/settings and more importantly, an update from Carlo when they discovered the one or two likely causes for the issue that's universal.

Anyway, besides giving this thread a bump, I noticed that if I selectmirror displays in system prefs (something I was prepared to cause a freeze or crash), the display attached to a DL to USB 3, went from lime green, to actually displaying what appears to be my login screen. I can only guess because the system prefs/ displays for that particular display is in the middle of the screen hiding the 3 accounts displayed on my login screen. Unfortunately, that's the only time I see anything different and requires a hard restart (holding down the power button). I'm also confirming that taking a screen shot of the diplay by dragging my trackpad pointer to that display (and using the cmd+shift+3 screenshot method), leaves you with a screen shot of your display how it should be displaying. It'definitely strange as it's like the lime green screen seems like a privacy measure - even though I know that's not what it is- I ony say that knowing that underneath the green, the display functions. More specifically, I'm able to drag things over there as well as blindly get them back .

Again the work by DL finding the likely issues and letting us know really is appreciated. Solid move and it's forr that reason and access to betas in the past which is why i haven't considered any other multi-screen solution. Thanks.

Hi All,

Update from us about this issue.

No solution yet. We are running a quite large number of experiments and still trying to get more info out of Apple.
I cannot share much, however we are aware of a few cases where the "yellow screen" issue can occasionally show pixels. This is one line of enquiry so if this happens to you, please let us know in which conditions.

As you can imagine this issue is higher than highest priority for us. Thank you for your comments and the useful information posted so far. Don't stop!

We have raised the 10.13.4 issue with Apple, it's ID 37385102.
We invite everyone to raise this problem with Apple. The bigger your deployment the better. Please let us know if the support team close as duplicate of an internal issue and let us know which is the internal issue.

Kind regards
Carlo

I can occasionally see the desktop 'behind the yellow' on my 13" mbp mid2012. however, its usually when swiping between desktops on the main screen it blinks for a moment. however it isnt consistent. another user happy to alpha test drivers if it can help

Interestingly, it seems like the eGPU stuff is causing all sorts of issues all around. Very similar issues were reported using eGPUs and High Sierra: https://forums.developer.apple.com/m.../264366#264366

The most interesting part (to me), is that where I noticed it thinks the external display is using the internal video card in the profiler, and in that thread, the same -- the external GPU seems to also be reported to be using the internal card(s).

Mind you, that thread is from late last year, but based upon Apple's docs, built-in eGPU support would be being added in to high sierra during this cycle.

I may be way off track, but it's an interesting coincidence if not related.

Another thing of note: I saw my full desktop momentarily immediately after login. It flashed up for a full second or so. I found this line interesting in the system log during that time:

Feb 19 12:02:24 clarity DisplayLinkUserAgent[263]: BUG in libdispatch client: kevent[EVFILT_MACHPORT] add: "No such file or directory" - 0x2


Also these:

Feb 19 12:02:34 clarity com.apple.xpc.launchd[1] (com.displaylink.useragent): This service is defined to be constantly running and is inherently inefficient.
Feb 19 12:02:34 clarity com.apple.xpc.launchd[1] (com.displaylink.useragent): Please switch away from OnDemand to KeepAlive.

Here's a link to see the full boot/login process if it helps: https://www.dropbox.com/s/2vc9z507fc...otlog.rtf?dl=0

Also I noticed if I kill -HUP the pid of DisplayLinkUserAgent, my desktop on that monitor flashes up for a second before the yellow takes over again.

So after doing all that, I unplugged everything and closed the lid (put the machine to sleep). When I woke it up this morning and attached all the peripherals, THE DISPLAYLINK MONITOR IS WORKING PROPERLY!

I have no idea why. Ask me for whatever you'd like and if I can provide it I will.

EDIT: The displaylink useragent is no longer running. Nor is the displaylink manager, but the monitor is up and running in full resolution and fully functional.

MBP mid-2012 13" i7 10.14.2b2

Hi,

On Mac Os 10.13.4 beta 3 (17E160e) still doesn't work, yellow screen in my case.

Thank you toastido,

Well this is all surprising it would definitely help to see your debug info in the working case. Can you please follow the instructions in https://support.displaylink.com/know...rticles/755301 and mention that the logs are for me?

Do you see any corruption on the internal screen or the screen you have connected to the built-in external port on your MBP?

Many thanks,
Carlo

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.

Well, I would be glad to, except now it's not working at all. I forgot to disable auto-updates and my machine updated to 10.13.4b3 overnight.

It's OK. Our experiments so far show that the yellow screen/working pixels is a temporary situation, albeit interesting of course. We'll keep looking.

Cheers
Carlo

I updated to beta 3 hoping for a fix (some reason i dont get updates on this thread to me email)
I still get the yellow screen only with mouse cursor.

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.

Sooooo this morning, I felt a little feisty, so I tried a thing.

┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:25]
└─[$] <> launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist
┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:26]
└─[$] <>

As soon as I unloaded the useragent, the monitor sprang to life and began functioning. It's laggy, but it's working.

Attached is the output from the information tool you requested as well.

Thank you we're looking at the logs, we'll have a new series of experiments to run.

Cheers,
Carlo

This worked for me as well. Second screen up and running. There is definitely lag and some rendering issues (white boxes over menu items, etc.) but it's mostly useful.

[QUOTE=toastido;85374]Sooooo this morning, I felt a little feisty, so I tried a thing.

┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:25]
└─[$] <> launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist
┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:26]
└─[$] <>

As soon as I unloaded the useragent, the monitor sprang to life and began functioning. It's laggy, but it's working.

Hi,
Can you please specify what exactly to enter in the commond line? Is it only the 2nd two lines each beginning with the $ sign and if so, it appears there are more brackets in your summary than I'm used to working with in Terminal.
Thanks very much.

[QUOTE=dizash;85386]Oh, sure. I'm using ZSH with some customizations, so that's why my command line looks like that. the actual command is:
launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist

[QUOTE=toastido;85387]Thanks Toastido - especially for the quick reply. Much appreciated!!!!

UPDATE: Immediately after utilizing the command, my DL Connected Monitor also SPRANG TO LIFE:

THANKS AGAIN TOASTIDO - this is huge for me!!!

[QUOTE=dizash;85388]NP. This will at least work until DisplayLink gets a real fix in place. It's more of a bandaid since it's a little laggy and whatnot, but at least it's a workaround for the time being.

This workaround doesn't work for me. Maybe it's hardware specific? I'm using an older Kensington SD3500v I believe. I can confirm the model if display link need it.

Same here. The monitor indicates it's receiving a signal, but the screen stays black.
--
Eric H.
--
NEC AccuSync LCD 72VX monitor

13.4.4 beta doesnt help - now the screen is just black instead of yellow.
and the 'work around' doesnt help either

I can confirm, there is no change with 10.13.4 beta 4.

im forgetting how to use a 2nd monitor lol

Hi all,
I installed the new version of the DisplayLink 4.1.11 on my 2012 MacBook Pro. I'm currently running MacOS HighSierra (version 10.13.4 (17E170c). I have the Dell D3100 port replicator/Dock. I ran the unload patch but still does not work. Its connected to my Mac though usb 3.0. The audio, network and USB ports work with no issues. The video is the only issue.
I tested the port replictor / dock with my Dell XPS laptop and it works like a charm. I think its an Apple related issue.

Any help is greatly appreciated, thank you in advance.

Hi All,

Another update from us. Unfortunately the workaround is not working anymore, as you noticed. There have been more changes in the new beta for eGPU which the team is investigating further. Keep your fingers crossed!

Thanks,

Michal

Thanks for keeping us updated! obviously 13.4 seems to have a big change in how it handles the eGPU. Any idea why this change was made or what benefits it might have long term?

Supporting an external graphics card would have many benefits for graphics intensive applications including games.

I imagine the biggest benefit to Macbook Display Link users would be support for clamshell mode (just guessing though).

+1

+1. The updates really are appreciated and says a lot about you guys. Thanks!

Just to follow up to my own post, what Beta giveth, Beta taketh away. I'm on the 17E170c build and alas I'm back to using a single monitor.