Re: failure of cheese with a Microsoft LifeCam NX-6000
On 2017-09-19, peter@easthope.ca <peter@easthope.ca> wrote:
> This problem might be an easier first step.
I don't understand what that means.
> lsub detects the LifeCam.
> root@dalton:/home/peter# lsusb | grep Micro
> Bus 001 Device 007: ID 045e:00f8 Microsoft Corp. LifeCam NX-6000
I read your lifecam is supported and uses the linux-uvc kernel driver.
http://www.ideasonboard.org/uvc/
> This screenshot shows that Ekiga recognizes the device but declines to
> activate it. The menu option is grey rather than black.
> http://http://easthope.ca/EkigaPreferences.png
I see nothing here. Maybe it's me. I read there's a configuration "druid"
(whatever that is) that sets everything up for you in ekiga.
https://wiki.archlinux.org/index.php/Webcam_setup
> The ekiga entries in /var/log/syslog pertain to the network
> connection. Nothing about the camera. Any ideas other than study more
> detailed debug output?
On the archlinux wiki it says:
Microsoft Lifecam Studio/Cinema
Under certain configurations, the Microsoft lifecam studio/cinema may request
too much usb bandwidth and fail see Uvcvideo FAQ. In this case, change the
buffering by loading the uvcvideo driver with quirks=0x80. Add it to
/etc/modprobe.d/uvcvideo.conf :
/etc/modprobe.d/uvcvideo.conf
## fix bandwidth issue for lifecam studio/cinema options uvcvideo quirks=0x80
Note: If delays are visible in the logs, or the camera works periodically, this
workaround should apply generally. Bigger values such as quirks=0x100 are
possible.
Anyway.
> Thanks, ... Peter E.
>
>
>
--
"Time flies like an arrow. Fruit flies like a banana." Groucho
Reply to: