chandler767,

I had the same thought, and was curious all day what type of workaround could get this to work. Glad to report that for the first time in a few months I have my DisplayLink device working great...

This whole problem is bizarre, because the drivers seemed to work for a month after I got it, but then started having the Finder crash issue, Login screen missing, and Flash crashing in the browser problem.

So here is what I did (this just happend, I may recreate everything later to give more details).

Install driver, reboot. Do not plug in displayport device yet (I did, but I guessed where the login button was, not sure if the results will be the same if device is not plugged in)

After login, plug in device and monitor.

Open terminal, and type:

Logout, Login and you should be good to go.

If this doesnt work, try (your system will probably crash/Kernel Panic):

Then startup again, login and run the kextload command above, logout and login.

If you need to reboot, try unplugging the USB adapter, then rebooting or shutting down. After login plug it in.


This entire set of instructions may be as simple as: Do not boot with the device plugged in, if you can you are missing the login buttons, and can guess, just plug in device, reload kext and logout/login.

I take no responsibility for the accuracy of the above..it may just be my luck..this is a '12 13" MBP, 10.8.2.

Let me know how this works for everyone..very hacky and a PITA, but maybe DL can get a workaround going in the meantime.

Tried to unload the kext on my vintage MBP 3.1 and got a kernel panic in com.apple.iokit.IOGraphicsFamily.

Dynamic graphics kext unloading is an old limitation in OS X, it seems to have been resolved in ML but it's evidently not reliable.
But the idea is interesting, we'll investigate further.

Cheers,
Carlo

DisplayLink drivers BSOD (Win 7 - Parallels)
 

One hidden, hard-to-find FAQ item explains that DisplayLink drivers do not run in virtual machines (like VMware, Parallels).
I guess they don't. They don't even warn you--just install, and take it all down to a BSOD.
Days and days to rebuild drive from scratch.
Thanks.
I believe J5Create.com has functioning drivers (and support USB 3.).

DiplayLink Mountain Lion Fix
 

Hey guys,
I FINALLY found a way to fix the issue with the display link monitors! Full use and all with ML and the 10.8 driver. It requires you to use a script that I have uploaded here:
http://www.c-bit.co/resources/DisplayLink.scpt
To set it up watch this video:
http://youtu.be/XJLN3LSYtMQ

**IMPORTANT Notes:**
-Always unplug your DisplayLink monitor before turning on your computer or the bug will still occur. Only plug in after you login!
-The script may still require a password after login for some people. Type it in and hit ok.
-Sorry if the video is a tad blurry.

Updates?
 

I have 150 users currently using display link and half of them have already been upgraded to Mountain Lion 10.8.2. Every user that has experienced an issue has had 7-10 crashes directly caused by the display link driver. Do we have an ETA other than sometime in Q1? I can provide as many crash reports as necessary to aid in a fix.

Unfortunately, I cannot go through Chandler767's fix with all of my users. It's fine for a one person but it's not a temp-fix for a whole office.

Thanks chandler767! It works!
 

chandler767, thanks for fixing the problem (for me at least). Display Link should give you some $$ for your time :D

Ha, I wish.

I'm just tried briangig and chandler767's solution of the kextload and it appears to have solved the issues of Finder crashing, Login box not working and Flash crashing.

However the third screen (second external as I already have one out the mini-DisplayPort on my iMac 21.5") still isn't displaying any image and if I go to Displays in System Preferences it doesn't show anything.

The device I'm using is USB 2 HDMI from Maplin, and the product code it gives is UHD-100 U3 from running system_profiler SPUSBDataType on Terminal.

I've fixed my Mountain Lion problems.

I've bought a 27 inch monitor and put my DisplayLink adapter in a drawer. Thanks for nothing DisplayLink :(

Couldn't wait any longer.

Any fix for Projector issues?

Hey thanks for the script and notifier application!

What language did you write the application for the notifier application in? would like to help to improve it so it can be hidden :)

Applescript.

Ok, so if we as a community can figure this out, shouldn't DsiplayLink be able to get a seamless solution working?

Also, is there a way to disable USB ports during the login process, then renable them automatically? If so, wouldn't this work the same as unplugging and plugging back in the device?

Unfortunately its not that easy...

Hi All

About a week ago, Apple released v10.8.3 OSX update to developers. The release notes don't mention the login issue being fixed, but we have been testing this and the Login issues seem to have "gone away".

We're wondering if this is just coincidence in our testing, as we know it is timing related, or is it fixed for anyone else on here with access to the 10.8.3 developer release?

Thanks

Wim

thanks for that! will be doing some more testing/messing with the code this weekend to see if it's possible to integrate the script and the application.

did however get the application to hide and just run in the background except popping up and showing in the dock when the message is displayed. :)

I would, but I don't use the beta's anymore after a huge hiccup from using one of the beta's last year haha. Have you guys looked at chandler767's temporary solution? it's a simple work around and should help your techs if they don't already know the problems or how to find a solution around the current problems.

Ready for this one?

I haven't used my DisplayLink adapter in a few weeks, the drivers have long been uninstalled.

This week I was having some memory problems, related to the 16GB I updated to back in Sept. I finally isolated the bad DIMM, so I am running on one 8GB. I decided to boot into single user mode to double check this one with memtest overnight (this included a fsck of the main HD).

This morning I rebooted, and I have no login screen...I guess the location and login, and my Finder is crashing, just like I had the DL drivers installed. I ran the uninstaller from my Desktop, and it said no drivers found (which was correct).

I rebooted, and the login screen was there that time. I had to leave for work, but I thought this was a very bizarre issue.

TL;DR: I had the no login/Finder crashing problem with NO DisplayLink drivers installed after I ran memtest in single user mode overnight.

Testing 10.8.3 w/ 1.8 driver
 

I am currently running 10.8.3 on my MBPR. I will use my display link driver to test.

10.8.3 w/ 1.8 driver Does not Fix
 

Previously I posted that I would test the theory that issues with display link manager were fixed with 10.8.3. I have crash logs every day from 12/7/12- present of display link manager crashing. If it would be helpful I can send a zip of my logs.

10.8.3 works; but don't claim support on 10.8 just yet!
 

I've installed OS X 10.8.3 (12D38) on a late-2011 13" MBP, with a DL-195 connected to a 24" 90deg rotated DVI HP display.

No random crashes after a full week. The HP display doesn't go live until after login and looks as it should.

After a really bad DisplayLink driver-support issue on 10.7, I waited several months before upgrading to 10.8 and after seeing that 10.8 was "supported" on the driver download page. (Yes, the DL driver was the only thing holding me back!)

I did not have an appreciation of the severity of the issues in KB333 until I had experienced them myself. I would recommend not saying that 10.8 is supported on the Driver Download page until a user can use the driver normally. I don't consider random crashes of Finder and other apps, caused by a OS bug or DL driver issue, as being "supported".

Glad it wasn't your bug in the end, DL, but you still fail on communication. Luckily that's something you can easily fix going forward. ;-)

jpap

Apple problem?
 

It looks like it might be a general problem in Mac OS X 10.8 with third party display drivers.

I tried out AirParrot (external display via AirPlay on Apple TV - it also sets up a display driver) - exactly the same symptoms as described here:
* no login window (managed to log in simply by entering the password blindly)
* some types of output don't show - e.g. iTunes video

This is extremely uncool - devices are only partly functional.

If DisplayLink have a workaround, by all means please publish it.

If the problem can be traced to Apple.. well, blame Apple and demand a fix.

Dear jpap,

I personally think that this is a very sensible conclusion.
The 1.8 we shipped months and months ago is still the same and the user experience seems to be good on 10.8.3 for most people. Yet, on some platforms the 10.8.0 user experience was awful (not for everyone, I've never seen the login issue on my Mac for example).

Determining where the blame lies is not the most important thing here, even if it's not with DisplayLink.

We need to ensure that in the future solutions like ours can interoperate well with OS X. Apple already fixed at least six critical bugs in ML that affect our devices, including some USB 3 ones that the forum will never be aware of.
This shows that Apple is actively interested in improving the OS and hopefully will bring other improvements as well.

We can help as OS X developers. You can help as Mac customers by raising the issues not only here but with Apple as well, to raise awareness.

All in all, I'm optimistic. I think 2013 will be a great year for USB graphics on OS X.

Carlo

With the new year upon us, is it possible to provide an estimate for the revised driver update - the constant screen flicker issue continues to a major irritant.

MickM I looked at your previous posts but it's not clear to me what kind of flicker you are experiencing. Is window content or full screen flickering? Only with some applications/OS functions or always?
Any specific triggers? What Mac model do you have?

As many other Mountain Lion issues it may be an OS issue, if I were you I'd open a bug on bugreport.apple.com as well so both us and Apple are aware of it.

Regards,
Carlo

Black screen Mountain Lion
 

My screen is completely black - and I can't find the monitor in Settings/monitors. Seems like the installation doesn't work in 10.8.2. Anybody else having this problem?

I also have issues with the DisplayLink an am dissapointed in the lack of information listed on the "Works with 10.8 with these small issues" page.

I have an issue where my mouseclicks are about 1/8th of an inch off where the mouse is pointing, and windows are drawn about the same distance "off" For example, I can not see the + sign for New Tab in the Firefox browser.

I had flickering issues when playing videos before, but can not duplicate it right now, so will leave that as a "maybe Apple fixed it" mention.

I also will have the adapter not power up when I return after having the computer off for the night. I typically swap USB ports and it works fine for a bit before it happens again.

I would love to see more communication, not just buried 10 pages deep in this thread, would be willing to try beta drivers to see if they help. I just find it amazing that their has not been a single update to the driver for this device since July, over 6 months ago.

Displaylink is banking on Apple soon releasing 10.8.3 and hoping it fixes everyone's issues. My USB display has been sitting unused on the shelf for months now...

The issue is the same for me as described above:

Mac OSX 10.8.2, driver v.1.8, monitor is blank and does not appear in the Displays page in Settings.

Workaround is to uninstall the driver, restart, reinstall the driver, restart.

Very unpleasant. Looking forward to a prompt reply from DisplayLink!

Flicker disappears at natural pixel resolution on main display.
 

RE: the screen flicker issue (ghost rectangles from the edges of previously drawn + moved rectangles).

I use SwitchResX. The screen flicker doesn't occur when I set the resolution of my main display at maximum (2880 * 1800). I have only seen the screen flicker on the main display, not the DisplayLink-connected displays.

Not sure if this has been mentioned, (didn't have time to trawl through this thread). Hope it might give a clue.

Good luck guys.

Suggestion
 

Put up weekly driver updates. Then you guys can tighten the feedback loop. There seem to be plenty of people willing to test new drivers.

Is the mac driver code open source?

Hi Carlo,

Sorry for the delay getting back to you. The screen flickering I'm am experiencing is almost entirely restricted to the Mail screen of icloud.com. Go www.icloud.com and you'll be at the screen where you can choose to enter into Mail, Calendar, Contacts etc. If you go into Mail (and only Mail, the rest are OK) then you'll see your 3 column view with all your mailboxes, message list and message contents. Just move your mouse around the screen and you'll go into a fit with all the screen flickering. In case it matters, I'm using a 15" MacBook Pro Retina running 10.8.2. I would appreciate it if anybody else could chime in and confirm this. Also, I just tried the new 2.0 alpha version and the problem is still there :-(.

Hi,

I's unlikely to be an issue specific to our driver (any version), it's probably some hardware acceleration used by the browser that is not correctly supported by the OS software renderer. We'll reproduce and open our own bug on bugreporter.

Carlo

Thanks Carlo. If you are able to confirm this behavior then I would appreciate you mentioning it in this thread. Your post also gave me another idea - when I get into work (where I have a DisplayLink device connected to my MacBook Pro Retina) I'll try accessing my icloud email from another browser and see if I still get screen flickering.

Well guess what - it was a Safari issue! I just tried viewing my icloud email from within Firefox and there are no screen flickers at all :-). I was on the verge of dumping Safari anyway because it crashes way too often. Now I'm a happy camper! Sorry also about a couple of my previous exasperated posts where I was kind of dry about the state of the DisplayLink driver.