Displaylink ceases to work in 10.13.4 - Page 3

slvrscoobie · 03-18-2018, 02:29 AM

Quote:

Originally Posted by kvd51

Hey Lawrence- your suggestion worked for me! Big time thanks. I just bought the AOC monitor and could not get it to work at all. Running 10.13.3 before installing the DisplayLink driver. Have not installed to 10.13.4

Damn, thought this was for 13.4, didnt do anything on Beta 5

Alanant · 03-19-2018, 10:56 PM

No difference in Beta 6 either.

Just guessing, but it seems to me like Apple are not going to fix this. As part of their upcoming eGPU support, they probably killed some legacy process that the likes of DisplayLink was using.

DisplayLink, do you have new software in the works to address this? Not long to go now until 10.13.4 is publicly available (10.13.3 and 10.13.2 both had 6 betas).

Poly · 03-20-2018, 03:51 AM

Quote:

Originally Posted by Alanant

No difference in Beta 6 either.
[...] As part of their upcoming eGPU support, they probably killed some legacy process that the likes of DisplayLink was using.

Apparently, Thunderbolt 3 docks are the only option now.

aehsmu · 02-12-2018, 04:37 PM

MacBook Pro (pre-TouchBar) - 10.13.4 Developer Beta

Driver causes main display to be extremely sluggish and jittery.

De-installing driver corrects the issue.

Am without 3rd monitor for the moment.

toastido · 02-12-2018, 04:56 PM

I found something that MIGHT be of importance.

I have a 13" mbp, with a SyncMaster 24" display attached to the miniDP port, and the other attached to a USB3->DVI DisplayLink adapter. I have the lemon screen issue on the 3rd monitor. Interestingly enough, MacOS *SEES* the 3rd monitor correctly, but thinks it's ALSO attached to the onboard video instead of the DisplayLink. Before, it showed the DisplayLink adapter as a separate video device with the monitor attached, now it shows this:

Screenshot 2018-02-12 10.54.45.jpg

Screenshot 2018-02-12 10.53.09.jpg

Thanks.

roadtest · 02-13-2018, 12:34 AM

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 · 02-15-2018, 08:08 AM

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 · 02-15-2018, 05:18 PM

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 · 02-21-2018, 06:24 PM

Quote:

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

slvrscoobie · 02-24-2018, 03:57 AM

Quote:

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.

02-12-2018, 04:37 PM	#4
aehsmu Junior Member Join Date: Feb 2018 Posts: 10	Redraw jittery, sluggish MacBook Pro (pre-TouchBar) - 10.13.4 Developer Beta Driver causes main display to be extremely sluggish and jittery. De-installing driver corrects the issue. Am without 3rd monitor for the moment. Last edited by aehsmu; 02-12-2018 at 04:41 PM.

02-13-2018, 12:34 AM	#6
roadtest Junior Member Join Date: Feb 2018 Posts: 1	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. Last edited by roadtest; 02-13-2018 at 12:38 AM.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

03-19-2018, 10:56 PM	#2
Alanant Member Join Date: Jan 2018 Posts: 31	No difference in Beta 6 either. Just guessing, but it seems to me like Apple are not going to fix this. As part of their upcoming eGPU support, they probably killed some legacy process that the likes of DisplayLink was using. DisplayLink, do you have new software in the works to address this? Not long to go now until 10.13.4 is publicly available (10.13.3 and 10.13.2 both had 6 betas).

02-12-2018, 04:56 PM	#5
toastido Junior Member Join Date: Feb 2018 Location: Huntsville, AL, USA Posts: 15	I found something that MIGHT be of importance. I have a 13" mbp, with a SyncMaster 24" display attached to the miniDP port, and the other attached to a USB3->DVI DisplayLink adapter. I have the lemon screen issue on the 3rd monitor. Interestingly enough, MacOS SEES the 3rd monitor correctly, but thinks it's ALSO attached to the onboard video instead of the DisplayLink. Before, it showed the DisplayLink adapter as a separate video device with the monitor attached, now it shows this: Screenshot 2018-02-12 10.54.45.jpg Screenshot 2018-02-12 10.53.09.jpg Thanks.

02-15-2018, 08:08 AM	#7
njoerd Junior Member Join Date: Jan 2018 Posts: 3	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.

02-15-2018, 05:18 PM	#8
toastido Junior Member Join Date: Feb 2018 Location: Huntsville, AL, USA Posts: 15	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!