![]() |
|
|
|
|
#1 |
|
Member
Join Date: Jan 2018
Posts: 39
|
welllllllllllllllllll cruddddd
got my Thunderbolt display today. plugged it in, works great, except.. wait, where is the 2nd monitor. oh. apparently you cant connect a thunderbolt display AND daisychain it to another Displayport display, it has to be ANOTHER thunderbolt display. GD Apple, you really dont make this easy (or its easy but extremely costly so Im back to my displaylink monitor. Can anyone confirm the newer QHD or 4K displaylink adapters are working before I buy a newer 2560x1440 monitor and find out it wont work... |
|
|
|
|
|
#2 |
|
Junior Member
Join Date: Jul 2018
Posts: 16
|
Well, everything was working great on my 2013 MacBook Air running Mojave Public Beta 5 and the latest Beta Drivers for a couple of days.
Today I got a my new 2018 MacBook Pro. I installed the latest Mojave Beta Public Beta 6 (18A353d) and the same (latest) DisplayLink Beta drivers and My 2nd monitor is blank with only the cursor showing up. If anyone else is running the same setup, please let me know your results. Sucks because some of my other apps (including Skype for Business and Symantec VIP) are either buggy, or not working under Mojave yet, but I installed the Beta strictly because of the second monitor. Last edited by Sofla David; 08-08-2018 at 08:37 PM. |
|
|
|
|
|
#3 | |
|
Member
Join Date: Jan 2018
Posts: 39
|
Quote:
|
|
|
|
|
|
|
#4 |
|
Junior Member
Join Date: Jul 2018
Posts: 16
|
|
|
|
|
|
|
#5 |
|
Junior Member
Join Date: Jul 2018
Posts: 16
|
Unfortunately, I'ver rebooted, Uninstalled, Rebooter, tried again, rebooted some more, and gone round and round till the cows come home, and I still get a blank display with just a mouse cursor.
I'm using a 2018 MacBook Pro 15" with the i9 processor. I'm running 10.14 Beta (18A353d) and the latest DisplayLink 4.3 Beta 5 driver. If I select "Mirror Displays" and then set "Optimize Display" to "MacBook Retina display", then It works (mirroring my display), but if I turn off the checkmark for "mirror displays", I get the blank screen again. I've hit a brick wall for now. It's most annoying because it *should* be working. Any suggestions are welcome. Last edited by Sofla David; 08-10-2018 at 02:10 AM. |
|
|
|
|
|
#6 |
|
Junior Member
Join Date: Aug 2018
Posts: 1
|
My work PC was recently changed over from a Windows 10 machine to a 2017 MacBook Pro. Working at home I use a Plugable UD-3900 dock, which I have been able to get one dispaly wokring with the beta 5 driver form July. This works well, but I really like 2 full size displays.
As a workaround, my IT group gave me a thunderbolt 3 adapter that has 1 hdmi port, and 3 usb 3.0 ports. This has enabled me to use my 2 full size dipslays. I plug one into the adapter via its HDMI port, and then I plug my DisplayLink based dock into one of the usb 3.0 ports. The dock has a display plugged in via DVI. Both displays work, and I keep the MacBook Pro closed, running in clam shell mode. My IT group will not allow an upgrade to Mojave when it is first released, so any fixes included in that will have to wait for me. This workaround meets my needs. |
|
|
|
|
|
#7 |
|
Junior Member
Join Date: Jul 2018
Posts: 16
|
I'm seeing a lot of posts on the internet from people who had gotten it working under Mojave Public Beta 5, and then are experiencing the blank screen with cursor just like me after installing Mojave Public Beta 6. Especially those of us with the newer 2017/1018 MacBook Pros.
I hope I'm wrong, but it would appear that Apple broke it again with Public Beta 6. I'm hoping DisplayLink can comment and either confirm, or deny that assumption soon so we can stop beating our heads against the wall trying to get it to work again or that Public Beta 7 comes out and fixes it again (one can hope). I guess the big lesson here is to always come check the DisplayLink forums before installing ANY update. Unfortunately, I got my new 2018 MacBook Pro the SAME day that Public Beta 6 was released, so I wasn't even aware I was installing a newer Beta at the time, and didn't consider that the next Beta might break it again. |
|
|
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|