VMware Communities
howardchan
Contributor
Contributor

Apple Built-in iSight not working after upgrading to Fusion 3.1

Hello all,

I am experiencing some problems with my built-in iSight after upgrading to Fusion 3.1 and would like to have pointers as to how to resolve the problem.

I'm currently using a 13" MacBook with OS X 10.6.3.

I was previously running Fusion 3.0.2 with Windows 7 ultimate and I had absolutely no problem enabling and using my built-in iSight within the Windows environment under various applications, such as MSN Messenger.

I updated my Fusion to 3.1 yesterday and it appears that I am no longer able to connect my built-in iSight. When I try to check the box next to "Apple Built-in iSight", it gets checked for a second then the check-box gets unchecked afterwards. I noticed that within Windows 7 it says that I plugged in the device, then it was unplugged immediately.

I tried reinstalling the driver for iSight under the Windows environment and it doesn't help. I also tried looking up in Google but it appears that so far no one has raised this issue before.

I would really appreciate if anyone could let me have some ideas as to how to resolve this problem. Thanks a lot.

Howard

Reply
0 Kudos
34 Replies
rcardona2k
Immortal
Immortal

Try checking the status of the Apple iSight under Virtual Machine > Settings > USB, under the Plug-in Action column. Put a check on the device to see it attaches properly to your machine

Reply
0 Kudos
howardchan
Contributor
Contributor

Thanks for your comment.

However the problem that I am experiencing is that I couldn't keep my Apple iSight checked and hence the the column "Plug In Action" is always greyed out. I am unable to change the Plug In Action column and it currently says "Connect to your Mac".

I could, however, change to either Windows or Mac for the rest of my USB devices.

Thanks again.

Reply
0 Kudos
hodj1967
Contributor
Contributor

I too am having this problem. I upgraded this morning and now when I try to connect iSight in XP it just ding-dong connects then immediately dong-ding disconnects.

What is even weirder is that I also have an instance of XP installed on VirtualBox and this does the same thing!

The only other thing I have done recently is install "Java for Mac OS X 10.6 Update 2" V1.0 from Apple Software Update.

Looking around on the Net I see that quite a few people have experienced this on and off with pretty much every virtualization product at some point over the last few years.

Anyone got any bright ideas?

Some more info:

Looking at the logs it appears that something untoward is going on in the kernel.

From vmware-vmfusion.log

May 28 15:00:34.101: UsbArbitrator| Log for VMware Fusion pid=1228 version=3.1.0 build=build-261058 option=Release

May 28 15:00:34.101: UsbArbitrator| The process is 32-bit.

May 28 15:00:34.101: UsbArbitrator| Host codepage=UTF-8 encoding=UTF-8

May 28 15:00:34.101: UsbArbitrator| USBGM: Valid autoconnect lockout on port fd400000 expires in 1923 ms

May 28 15:00:34.102: UsbArbitrator| Rejecting autoconnect for:Apple Built-in iSight

May 28 15:00:36.424: UsbArbitrator| USBGM: Valid autoconnect lockout on port fd400000 expires in 2537 ms

May 28 15:00:36.424: UsbArbitrator| Rejecting autoconnect for:Apple Built-in iSight

From kernel.log

May 28 15:00:35 MacBook-Pro kernel[0]: USBF: 7687.289 IOUSBCompositeDriver[0x715a000](Built-in iSight) GetFullConfigDescriptor(0) returned NULL

I have some more results from experimentation. I can confirm that the same behaviour occurs in an existing instance of XP on VBox. I have completely reinstalled all Boot Camp drivers without curing the problem. I have also tried connecting both the Apple IR Receiver and Bluetooth Transceiver and both work fine. Both these devices are connected to the MacBook's UHCI controller (USB1.1) while the iSight is connected to the EHCI (USB2.0) controller. So I disabled USB2.0 support and tried connecting the iSight using only USB1.1 support but got the same behaviour. I also tried removing the USB controller completely and reinstalling but same problem.

I also see exactly the same behaviour in Vista on VirtualBox.

So it seems to me it is something to do with the interaction between the MacBook's EHCI controller and virtual machines. This was all working fine last week and, as I said above, the only change has been the Java update.

Reply
0 Kudos
whinshaw
Enthusiast
Enthusiast

Howard,

You may want to reinstall the drivers from the boot camp cd. Also, I see there is a boot camp update for the 13" located here.

Don't know if that update effects your macbook, but it was worth a guess.

Let me know if those don't work and I will try it with my Windows 7 Business runing 3.1.

Thanks,

If you find this information useful, please award points for

"correct"

or "helpful".

Wes Hinshaw

www.myvmland.com

If you find this information useful, please award points for "correct" or "helpful". Wes Hinshaw www.myvmland.com
Reply
0 Kudos
admin
Immortal
Immortal

I am unable to change the Plug In Action column and it currently says "Connect to your Mac".

That just controls what happens when you physically plug in the device while a VM is running; it's greyed out for an iSight since it's built in.

Reply
0 Kudos
admin
Immortal
Immortal

Could you send me the support logs, or attach them here? Thanks!

Reply
0 Kudos
howardchan
Contributor
Contributor

Thanks to all for suggestions.

Just to let you know, I have also tried the following but it does not appear to have resolved the problem:-

  1. creating a brand new virtual machine with Windows 7 Ultimate and immediately installed the iSight driver that comes with the Snow Leopard installation disc.

  2. removing and reinstalling the iSight drivers within the virtual machines

  3. removing and reinstalling VMWare Fusion

I also attach copies of the log files originally named "vmware.log" which I found within the packagecontents of my virtual machines running Windows 7 Ultimate:-

  1. The one named "Current Installation.log" represents the log file that I extracted from the virtual machine running Windows 7 Ultimate that I have been using since 3.0.0 without problems using the iSight.

  2. The one named "New Installation.log" represents the log file that I extracted from a newly created virtual machine running a clean copy Windows 7 Ultimate without anything else installed (including any sort of updates to Windows) except the iSight driver.

Please let me know if these are the files that you are looking for, if not, please let me know where I could locate the files.

Thanks again.

-h

P.S. I also managed to locate a log file named vmware-vmfusion.log and I have attached it to this message as well.

Message was edited by: howardchan

Reply
0 Kudos
lolorenzo
Contributor
Contributor

Hi! ...same problems!

MacBook Pro + 10.6.3 + VMware 3.1 + Xp Prof Service Pack 3

Reply
0 Kudos
YARGLTD
Contributor
Contributor

I've just wasted an hour or so of my life ..

Same as above ..also ran iSight install from D:\Boot Camp\Drivers\Apple installed OK but then said it had detected errors.

MacBook Pro + 10.6.3 + VMware 3.1 + Xp Prof Service Pack 3

Reply
0 Kudos
admin
Immortal
Immortal

FYI I attempted to reproduce the issue but it worked fine for me.

I've got Fusion 3.1 with Boot Camp 3.1.

Windows 7 x64

I directly used a Boot Camp partition rather then a VM with just the drivers installed. I'll test that next.

Edit:

I used a Windows 7 x64 VM that wasn't a boot camp partition. This time I installed the 3.0 iSight64 driver alone. The install succeeded. When I connected the isight it came up at the bottom that it wasn't installed correctly. Having experienced that before I checked the Device manager and I saw an unknown device called the isight but I also had the correct isight under imaging devices. I then installed a program to test the webcam and it showed that the webcam was working correctly in the VM. Through all of this the isight never disconnected in the settings of the VM.

@howardchan Have you tried reinstalling VMware Tools?

Also do you have any programs open on the mac at the time that uses the isight?

On the mac side do you have any non default Apple programs that use the isight?

Reply
0 Kudos
howardchan
Contributor
Contributor

AndrewPainter,

Thanks for your suggestions.

First to answer your questions:

Have you tried reinstalling VMware Tools? --> Yes

Also do you have any programs open on the mac at the time that uses the

isight? --> Yes and No, tried both but still wasn't working.

On the mac side do you have any non default Apple programs that use the

isight? --> Yes, Skype only.

Second, few points to note / ask:

1. I used Windows 7 Ultimate x86, would that make a difference vs. x64 version?

2. I have only one partition in my MacBook, so I'm just installing under my Mac HD and saving it under my user folder.

3. Is there anything that I can do on my side that might help? I will also try installing a x64 version later this evening and see how that goes.

Thanks again.

Howard

Reply
0 Kudos
hodj1967
Contributor
Contributor

I have just downgraded to Fusion 3.0.2 and iSight is now working again. It is clearly a Fusion 3.1 problem. I'm staying with 3.0.2 for the time being.

Reply
0 Kudos
YARGLTD
Contributor
Contributor

OK thanks, I think I may go down that route as well. FYI I did reinstall the VMWare Tools but no joy.

Here goes a rollback ...

Cheers

Steve

Reply
0 Kudos
lolorenzo
Contributor
Contributor

I have just downgraded to Fusion 3.0.2 and iSight is now working again. It is clearly a Fusion 3.1 problem. I'm staying with 3.0.2 for the time being.

Thanks for the experiment! I supposed to be so...

Reply
0 Kudos
hodj1967
Contributor
Contributor

Steve,

I did the same. Installed VMware Tools under 3.1 and re-installed all Apple Boot Camp drivers but without any luck. I'm still confused over the reason that it stopped working in VBox as well - how could upgrading Fusion cause that?! I've tried VBox again and it is still doing it so maybe it's some conflict between the two?

Anyway, I'm happy with 3.0.2.

Graeme

Reply
0 Kudos
W4ATK
Contributor
Contributor

Lorenzo

I had no problem getting iSight running on 3.1 after the upgrade. I

saw the original posts and upon checking my iSight was not there, so I

went to Settings, USB devices, clicked on iSight and everything worked.

Jim
Reply
0 Kudos
lolorenzo
Contributor
Contributor

Thanks... Now I'm trying to install Windows 7 64bit for a test.

If you want you can reed also this thread: iSigth.

Reply
0 Kudos
admin
Immortal
Immortal

Thanks for the logs, but they don't have the information we need. We would like to see the output of Help > Collect Support Information - please reproduce the problem, collect the information, and attach the resulting tgz.

Reply
0 Kudos
lolorenzo
Contributor
Contributor

I've now finished to install W7 64bit... all updates... same problems...

MacBook Pro C2D 2.16 + 10.6.3

See .tgz attached file.

Reply
0 Kudos