Hi everybody --
I didn't see any posts on this for 3170 on this, so I thought I'd share a little of my own experiences.
I installed Parallels 3170 on OS X 10.4.8, on a new dual-core MacBook Pro with built-in iSight. After installation, my iSight camera stopped working in OS X, and in Win XP SP2 also... it was like this under 3150 too.
Looking in System Profiler, I saw that Built-In iSight Camera was listed under USB Bus, *not* USB High-Speed Bus. A little probing of my system logs showed that there was some kind of overflow either in voltage or bandwidth; I can't remember which. Some light grepping turned up errors that looked like this: "QuickTimeUSBVDCDigitizer: Cannot get enough bandwidth. Desired: 3072, available 1023".
To get my iSight back, I simply instructed OS X to unload the Parallels USB kernel driver. After logging into my Administrator account (I keep my admin account separate from my day-to-day user acount, I typed this in an open Terminal window:
sudo kextunload -b com.parallels.kext.ConnectUSB
The driver unloaded successfully, and presto! I got my iSight back. Not only that, but the iSight is once again listed in System Profiler as a high-speed device. Excellent!
(If you want, you can verify that the Parallels USB kernel extension is running, or not, by typing this: kextstat | grep USB -- note the vertical pipe symbol before 'grep'. You should see something like this: 81 0 0x97b000 0x4000 0x3000 com.parallels.kext.ConnectUSB (2.5.0) <36 11 6 5 4 3>)
After going through all this (and it only took a minute or two, really), I started to think about what's going on. I suspect what's happening is that the USB driver written by the Parallels team isn't a high-speed driver, and it somehow can't handle the bandwidth needs of the iSight camera.
Medium-term, I am sure Parallels will fix this. In the short term, this quick hack will suffice. The downside to this, of course, is that it means you can't use USB devices inside a running VM.
If this duplicates somebody else's post, sorry to repeat the obvious. If not, I hope it helps some people out there who have been frustrated. I certainly have been, although it doesn't diminish my admiration for what the Parallels team has been able to achieve. It's a great product.
Andrew
I didn't see any posts on this for 3170 on this, so I thought I'd share a little of my own experiences.
I installed Parallels 3170 on OS X 10.4.8, on a new dual-core MacBook Pro with built-in iSight. After installation, my iSight camera stopped working in OS X, and in Win XP SP2 also... it was like this under 3150 too.
Looking in System Profiler, I saw that Built-In iSight Camera was listed under USB Bus, *not* USB High-Speed Bus. A little probing of my system logs showed that there was some kind of overflow either in voltage or bandwidth; I can't remember which. Some light grepping turned up errors that looked like this: "QuickTimeUSBVDCDigitizer: Cannot get enough bandwidth. Desired: 3072, available 1023".
To get my iSight back, I simply instructed OS X to unload the Parallels USB kernel driver. After logging into my Administrator account (I keep my admin account separate from my day-to-day user acount, I typed this in an open Terminal window:
sudo kextunload -b com.parallels.kext.ConnectUSB
The driver unloaded successfully, and presto! I got my iSight back. Not only that, but the iSight is once again listed in System Profiler as a high-speed device. Excellent!
(If you want, you can verify that the Parallels USB kernel extension is running, or not, by typing this: kextstat | grep USB -- note the vertical pipe symbol before 'grep'. You should see something like this: 81 0 0x97b000 0x4000 0x3000 com.parallels.kext.ConnectUSB (2.5.0) <36 11 6 5 4 3>)
After going through all this (and it only took a minute or two, really), I started to think about what's going on. I suspect what's happening is that the USB driver written by the Parallels team isn't a high-speed driver, and it somehow can't handle the bandwidth needs of the iSight camera.
Medium-term, I am sure Parallels will fix this. In the short term, this quick hack will suffice. The downside to this, of course, is that it means you can't use USB devices inside a running VM.
If this duplicates somebody else's post, sorry to repeat the obvious. If not, I hope it helps some people out there who have been frustrated. I certainly have been, although it doesn't diminish my admiration for what the Parallels team has been able to achieve. It's a great product.
Andrew
