Built in iSight camera no longer recognized after updating to 2.2 Beta driver
 

I'm wondering if any others are having issues with system recognizing built in laptop camera after updating driver? I made the mistake yesterday of updating my display link driver to beta 2.2 on my 17" MBP and now the built in camera no longer works. If I uninstall the driver then the camera goes back to functioning properly. I previously had the 2.1 driver installed with absolutely no problems. If I uninstall 2.2 and reinstall 2.1 the camera still doesn't work. In fact when I look into System Information, the camera section is blank when the driver is installed indicating that no camera is detected. So it appears I am left with a choice of a camera or a display link display, but not both.
Any suggestions would be much appreciated.

camera works fine for me - 2013 MBA. I had it stop working a few months ago and did the Mac resets ... forgot what they are called PRM or something and it worked again.

Thanks. I did the Vram, Pram resets or whatever they're titled and that didn't have any effect. Also ran through a start up disk repair again without positive results.

Hi MacSus,

This is very interesting. Can you please first collect the System Profile when our driver is uninstalled, then install the driver and use this tool http://www.displaylink.com/support/ticket.php?id=269
And then send us all information using http://www.displaylink.com/support/ask_question.php

Cheers
Carlo

Thanks Carlo. I sent the information on its way.

I'm looking at it now.

The USB device for iSight is there and is enumerated, but it looks like the main configuration is different from what I'd expect in the normal case. It seems to be matching the correct driver so the driver should not really make a difference.

Is this happening with just the DL drivers loaded or do you also need the device to be connected to see the problem?

Carlo

This happens whether the device is connected or not. The problem only goes away when I uninstall the DL driver.

*Update: As strange as it sounds, this morning I updated to OSX 10.9.3 and the problem seems to have been resolved.

It was an Apple bug in 10.9.2. They did something which broke all apps which used virtual displays and then fixed it in 10.9.3. Here is just one of many threads discussing it:

http://forums.macrumors.com/showthread.php?t=1687738