Any news on a new beta?

[trevize]

I'm running 10.9.5 build 13F24 and I have 2 DisplayLink adapters. Going from one build seed to the next, having 2 adapters sometimes works and sometimes doesn't. 1 Seems to always work in some form or fashion with the bugs that have been pointed out many times on this very forum.

I can also boot Yosemite and have relatively the same experience with Mavericks.

So when are we going to see some beta trying to fix current issues? I'm a willing participant in testing and I'd bet there are many others. I ask as it seems to be very quiet @ DisplayLink with any progress on fixing current issues and maintaining compatibility with future versions of OSX.

[alphadog]

I would just like better performance on Mavericks.... things were fine for a while, then my MBA started crashing every night - it is fine if i don't leave DL plugged in, but if I leave it plugged in, it crashes overnight probably from sleep or resume - but I am not there to pin it down. Not just a windowserver crash but the whole OS.

Hoping for a fix.

[trevize]

Just installed DP7 and now it seems it is completely disabled to use the DisplayLink. Heads up!

[trevize]

Got the DisplayLink to work again on DP7.

Had to manually remove the kext and re-install the DisplayLink software. The DisplayLink uninstaller no longer functions on DP7.

[dafnordad]

I am new to this and not a techie. Just bought a Vianect AIR TV HDMI extender for my Macbook Pro running 10.9.4 OS. Was told by DEVOLO that they have no driver to support this OS. I was directed to DP and downloaded the Display driver. Each time I connect the the HDMI adapter to the MAC, it crashes and continues to restart and crash until I remove the adapter.

What can I do short of returning the Devolo to amazon in Germany where it was purchased?

[displaylinker]

Got the DisplayLink to work again on DP7.

Had to manually remove the kext and re-install the DisplayLink software. The DisplayLink uninstaller no longer functions on DP7.

Where is this kext file located? Just in case I have the same issue here.

[trevize]

Where is this kext file located? Just in case I have the same issue here.

The uninstaller works on the version of OS X you are running. You should use that.

Also.... me answering the above speaks volumes for exactly my fear.

Where are the DisplayLink support people? Why has there been no response at all to requests for information? Is OS X development dead for DisplayLink? Sure would be nice to know before more people spend money buying adapters!

I've called, I've emailed and I've posted on this forum. I've heard nothing at all, gotten no response what so ever. Are the lights even on?

[Carlo]

The uninstaller works on the version of OS X you are running. You should use that.

Also.... me answering the above speaks volumes for exactly my fear.

Where are the DisplayLink support people? Why has there been no response at all to requests for information? Is OS X development dead for DisplayLink? Sure would be nice to know before more people spend money buying adapters!

I've called, I've emailed and I've posted on this forum. I've heard nothing at all, gotten no response what so ever. Are the lights even on?

Hi Trevize,

We're still working on the Mac drivers do not worry.
However I have to set your expectations: it is unlikely that the next beta will address the most annoying Mavericks/Yosemite issues.
It's true that we are still looking for workarounds, but the real fix has to be in the OS to bring it back to the full functionality of OSX 10.8.x.

About the uninstaller, it looks like there is an issue in code authentication since the DP6.
It's not difficult to work around and the next version of the SW will have a working uninstaller.

Please write here if you need to uninstall manually. There is a tedious list of files to delete, different for each OS version.

Cheers,
Carlo

[unusedusername]

Please write here if you need to uninstall manually. There is a tedious list of files to delete, different for each OS version.



Hi Carlo,

Please post the list for the third refresh of public beta: 10.10.0 (14A361p)

[alphadog]

I just wish you would decide if you will continue to support OS X or not. Updates for this beta are almost non-existent. Feedback to customers is just as infrequent.

I have to unplug this adapter every night, or my MBA crashes when it wakes. I understand Apple has made things difficult, but you could post incremental changes. Some of them must work. Your developers are developing, your QA team is testing, and I assume you are checking in changes that work. How about sharing some?

At least publicly post how to remove the drivers so I can have a stable system and move to a Thunderbolt dock - OS X 10.9.4.

[Carlo]

Hi Carlo,

Please post the list for the third refresh of public beta: 10.10.0 (14A361p)

To uninstall you should remove all of the following files (some may not be present on your system) then reboot:
/Library/Extensions/DisplayLinkDriver.kext
/Library/Extensions/DisplayLinkEthernetDriver.kext
/Library/StartupItems/DisplayLinkAgent
/Library/LaunchAgents/com.displaylink.useragent.plist
/Library/LaunchAgents/com.displaylink.useragent-prelogin.plist
/Library/LaunchDaemons/com.displaylink.launchd.plist
/Library/LaunchDaemons/com.displaylink.displaylinkmanager.plist
/Library/Preferences/com.displaylink.plist
/Library/Receipts/DisplayLink Software Installer.pkg
/Applications/DisplayLink/DisplayLink Software Uninstaller.app
/Library/Application Support/DisplayLink
/Library/PrivilegedHelperTools/DisplayLink
/var/db/receipts/com.displaylink*

Administrator access is required.

Cheers,
Carlo

[alphadog]

10.9.5 was just released. No mention of any video fixes, or any other bugs reported by many (sleep/wake; finder-thumbnail windows, etc)

Maybe this will get us a driver update?

[alphadog]

I got tired of having to undock my system every night and the random window server crashes so I got a Thunderbolt dock - it was only a bit more then my Toshiba Dynadock, and since I only can use one monitor with Displaylink, why not try it.

So far it is perfect. No screen lag as with Displaylink, no crashes. And Elgato has a nifty undock icon that unmounts all drives.

Either Apple/DisplayLink will fix the issues, or Thunderbolt monitors will come down in price - whichever happens first will get me back my multimonitor support.

[alanpuccinelli]

10.9.5 was just released. No mention of any video fixes, or any other bugs reported by many (sleep/wake; finder-thumbnail windows, etc)

Maybe this will get us a driver update?

FWIW I did the 10.9.5 update and it would seem that the latest beta 2.2 driver while it works still suffers from the same problems and is probably even more unstable. I'm getting constant window server crashes now. Bummer that things are moving in the wrong direction. OSX support hasn't been good since 10.8 and we're on the eve of 10.10 now.

Can you outline what it is that Apple has done or isn't doing in the newest versions of OSX that's causing such problems? What is it that the OS isn't supporting now that it once did?

[K447]

...

We're still working on the Mac drivers do not worry.

… it is unlikely that the next beta will address the most annoying Mavericks/Yosemite issues.

It's true that we are still looking for workarounds, but the real fix has to be in the OS to bring it back to the full functionality of OSX 10.8.x.

...This has gone far, far beyond 'worry'.

It is abundantly clear that the software architecture used for DisplayLink on Mac OS X has deep problems working with modern Mac computers. The problems are particularly acute when using more than one external display.

That these ongoing driver problems persist through TWO major updates of the Max OS X software suggests that the DisplayLink software/driver implementation on Mac is simply beyond repair. At least it seems to be well beyond the control of DisplayLink.

It is important not only that the actual hardware work as expected, it is critical that the software driver design be able to withstand updates and changes from Apple. It is to be expected that Apple will update Mac OS X and will make changes. It is not acceptable that DisplayLink be unable to cope with these changes.

I have been tolerating the DisplayLink driver limitations by NOT updating the OS X when 10.9 became available. Now 10.10 is arriving and I still have no upgrade path while using DisplayLink drivers.

I am currently running OS X 10.8.5 (12F45) on a 2013 MacBook Air with three external displays (1920x1200 each). One display is connected to the MacBook Air DisplayPort and two via an Acer 'Universal USB 3.0 Docking Station' (http://store.acer.com/store/aceramer/en_US/pd/ThemeID.35703000/productID.297410400) dual monitor HDMI/DVI adapter (with wired ethernet, etc) using the DisplayLink DL3000 chipset.

http://store.acer.com/DRHM/Storefront/Company/acerna/images/details/main/Acc_Dock_NPDCK11003_main.png

Until recently the DisplayLink drivers did allow all three external screens to work, but at times the DisplayPort connected HDMI monitor would power on but appear black. The computer 'thinks' that display is working and I can move the mouse pointer into the area where it should be visible on that screen, but nothing actually appears. The blank monitor appears in the screen Arrangement section of System Preferences. If I unplug the DisplayPort cable from the MacBook Air and wait a minute or so, reconnecting the cable would often restore correct operation of that screen.

I do not have issues with cursor lag and rarely see screen image corruption.

Today the DisplayPort screen refuses to activate despite several power cycles of the computer. Disconnect and reconnect the DisplayPort cable also does not help. The two DisplayLink screens are working fine!

... I really am approaching the end of my tolerance for codling and generally putting up with the DisplayLink 'powered' product.
Update: My DisplayPort to HDMI cable was causing intermittent trouble, cleaned connector contacts and is now working as before.
All three external (plus MacBook Air internal) displays now working as they were before (which means sometimes the DisplayPort screen does not reappear after sleep).
Still does not help with the ongoing DisplayLink/OS X update conflicts.

I just read a news item (https://www.npd.com/wps/portal/npd/us/news/press-releases/apple-and-chrome-boost-us-retail-pc-back-to-school-sales/) that Apple Mac computers are now more than a quarter of all personal computers sold in the USA (http://appleinsider.com/articles/14/09/24/apples-macs-rack-up-more-than-14-of-back-to-school-pc-sales-in-2014). And a far higher percentage of computers that are 'not cheap'. Customers who have money to spend are buying Apple products.

I suggest it is time for DisplayLink to reboot their approach to Mac driver support. Much more focus and technical resources (money) need to be allocated to the problem. If the driver(s) need to be redesigned from the ground up, then please do so.

I would happily PAY for a driver that actually worked properly, reliably, and continued to work going forward.

[alanpuccinelli]

FWIW I did the 10.9.5 update and it would seem that the latest beta 2.2 driver while it works still suffers from the same problems and is probably even more unstable. I'm getting constant window server crashes now. Bummer that things are moving in the wrong direction. OSX support hasn't been good since 10.8 and we're on the eve of 10.10 now.

Can you outline what it is that Apple has done or isn't doing in the newest versions of OSX that's causing such problems? What is it that the OS isn't supporting now that it once did?

Looks like I may have been hasty in blaming the displaylink driver on my crashes. Turns out I had a stick of RAM actually go bad on me... even still the multimonitor experience still leaves a lot to be desired.