Webcam fails to initialize 25% and flickers 75% of remaining times
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NULL Project |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
I've recently upgraded from Ubuntu Lucid to Maverick on my ASUS K50AF laptop. I'm mostly satisfied with the upgrade, but there are some issues.
One of these issues concerns the integrated USB-webcam (recognized as 13d3:5130 IMC Networks) which worked fine before the upgrade (kernel 2.6.32, besides the well known "upside-down" issue) but is pretty unstable after upgrading.
In (estimated) 25% of cases when I boot the laptop the webcam cannot be initialized. In these cases dmesg | grep "uvc" contains:
[ 687.093688] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (13d3:5130)
[ 687.093715] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
[ 687.093719] uvcvideo: Failed to query (129) UVC probe control : -108 (exp. 26).
[ 687.093723] uvcvideo: Failed to initialize the device (-5).
[ 687.093943] usbcore: registered new interface driver uvcvideo
In (estimated) 75% of remaining cases initialization is successfull, but the webcam picture is flickering, framerate is very low (1 pic every second) and the picture looks like a mosaik of small squares in some frames.
The problem can be in Cheese, Skype and Google Talk. In Cheese the webcam picture sometimes (about 50%) remains just black, although I can see a flickering image in Google Talk in the same session.
Everytime the image flickers, i can find a lot of lines
"uvcvideo: Failed to resubmit video URB (-27)." with dmesg | grep "uvc".
In the remaining 75% * 25% of logins the webcam works just fine. In sessions when the webcam is working, dmesg | grep "uvc" returns no error messages at all.
sudo modprobe -r uvcvideo
sudo modprobe uvcvideo
has no effect, resating the X-Server doesn't help, I need to restart the computer and hope for my 75%*25%-chance to use my webcam.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-23-generic i686
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: VT1708S Analog [VT1708S Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: VT1708S Analog [VT1708S Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xfbcf4000 irq 16'
Mixer name : 'VIA VT1708S'
Components : 'HDA:11060397,
Controls : 21
Simple ctrls : 14
CheckboxSubmission: 61adeb82f3b0980
CheckboxSystem: b62ae224500b03a
Date: Sat Nov 27 15:08:51 2010
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer INC. K50AF
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=de_AT.utf8
SHELL=/bin/bash
RelatedPackageV
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
dmi.bios.date: 12/29/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 202
dmi.board.
dmi.board.name: K50AF
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.00
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: K50AF
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
tags: | added: kernel-series-unknown |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
I don't have the flickering, although the video freezes up while using Skype after a few minutes.
and I see 5 new messages each time from the kernel log:
5x [time index] uvcvideo: Failed to resubmit video URB (-27).
this only affects the maverick kernels (2.6.35+) maybe a little earlier
as the lucid kernel (2.6.32), which I've reverted back to for a while doesn't have this issue
from what I can tell.
(my workaround for reverting is simply move the 2.6.35 kernel out of /boot then run update-grub
thus it only detects my younger 2.6.32 kernel, and then reboot)