PDA

View Full Version : 10.10.3 Blank Screen after update from 10.10.2


kevinh2
05-07-2015, 09:33 PM
My system was working fine until an Apple update in late March or early April. Now my Displaylink monitor is blank. The screen maps in my system settings, and I can move my mouse to the screen (although I can't see the mouse)

I uninstalled and reinstalled the 2.4.1b software, but still not working.

My DisplayLink device works because I tested it on another of my MacBook Pros.

I attached the log file. Hopefully I used it correctly to gather the needed info.

thx

Carlo
05-08-2015, 12:02 PM
Hi Kevin,

We have spotted a possible problem on this specific system: you have a kernel extension called vhhcd.kext that has created similar issues for a different user.

It seems to be connected with a SW called VirtualHere. Could you try uninstalling the vhhcd.kext kernel extension and check if the issue is still there?

Best regards,
Carlo

kevinh2
05-08-2015, 02:43 PM
Works after removing the kext file.

Now the question is whether the issue is DisplayLink or VirtualHere. Any thoughts? I will contact VirtualHere as well.

thx.

virtualhere
05-08-2015, 10:21 PM
@Carlo: Im a developer from virtualhere. if you know the conflict with your driver let me know and ill make a fix to my driver if its something to do with vhhcd. I suspect you are polling the system for all USB Host Controllers and are only expecting Apple ones and your system then stops the polling...just a guess...Michael

Carlo
05-09-2015, 08:15 AM
@Carlo: Im a developer from virtualhere. if you know the conflict with your driver let me know and ill make a fix to my driver if its something to do with vhhcd. I suspect you are polling the system for all USB Host Controllers and are only expecting Apple ones and your system then stops the polling...just a guess...Michael

Thank you Michael,
Yes that's the kind of issue we would have expected but it is much more weird than that! We'll contact you directly.

Cheers,
Carlo

virtualhere
05-17-2015, 04:10 AM
OK this is now confirmed fixed in 2.9.5 of the virtualhere client.

Carlo
05-18-2015, 08:18 AM
Thank you Michael,

This was a fast workaround!

Cheers,
Carlo