05ca:181e [Dell Latitude E5520] My camera stopped showing video feed since about two weeks ago

[Reinis Zumbergs]

1) Kubuntu 12.04 amd64
2) v4l-utils: Installed: 0.8.6-1ubuntu1
3) It was working fine all the time on 11.10 and Precise Beta. And I believe it was still working after final release, but I'm not 100% sure.
4) The returned video is just black and a bit of faint colored circle in the middle

It's built in webcam of Dell Latitude E5520
In lsusb, I think, it shows as "Bus 001 Device 003: ID 05ca:181e Ricoh Co., Ltd"
In vlc it shows as "CN0CJ3P2724871B9C7XGA00" - "Laptop_Integrated_Webcam_FHD"

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: libv4l-0 0.8.6-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Tue May 15 21:19:34 2012
EcryptfsInUse: Yes
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120413)
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: v4l-utils
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: roodis 2087 F.... panel-11-mixer
CRDA:
 country DE:
  (2400 - 2483 @ 40), (N/A, 20)
  (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
  (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
  (5470 - 5725 @ 40), (N/A, 26), DFS
DistroRelease: Ubuntu 13.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=a297fcfa-1788-45f0-bee9-573714a9839a
InstallationDate: Installed on 2012-08-16 (220 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724)
MachineType: Dell Inc. Latitude E5520
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-14-generic root=UUID=01e049cf-b5c1-4115-8d98-00f0227207bf ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-14-generic N/A
 linux-backports-modules-3.8.0-14-generic N/A
 linux-firmware 1.104
Tags: raring
Uname: Linux 3.8.0-14-generic x86_64
UpgradeStatus: Upgraded to raring on 2013-03-05 (20 days ago)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo www-data
dmi.bios.date: 07/10/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.asset.tag: Min tie
dmi.board.name: 03PH4G
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.asset.tag: Min tie
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA02:bd07/10/2011:svnDellInc.:pnLatitudeE5520:pvr01:rvnDellInc.:rn03PH4G:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

[Guilherme Machado (gcmachado)]

Exactly the same problem here!

[Gregor Jasny (gjasny)]

Which program do you use to view the camera stream?

Could you please try qv4l2 and open the device in raw mode? If it is still broken this is most likely a kernel issue.

[Gregor Jasny (gjasny)]

Are there any errors in the kernel log? (run dmesg to find out)

[Reinis Zumbergs (reinis-zumbergs)]

dmesg seems to have a lot of private things in it. What should I look for?
For now I found these lines:
[ 14.390031] Linux video capture interface: v2.00
[ 14.633504] uvcvideo: Found UVC 1.00 device Laptop_Integrated_Webcam_FHD (05ca:181e)
[ 14.635082] input: Laptop_Integrated_Webcam_FHD as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input17
[ 14.635149] usbcore: registered new interface driver uvcvideo
[ 14.635151] USB Video Class driver (1.1.1)

I tried qv4l2 now. Clicked File - Open Raw Device - chose /dev/video0 - switched on Show frames and hit the red "record" button, but still the same results as described above.

[Reinis Zumbergs (reinis-zumbergs)]

Oh, and now I'm running Xubuntu Raring Ringtail. Kernel: Linux ... 3.8.0-14-generic #24-Ubuntu SMP Fri Mar 22 19:45:03 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 999875

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Reinis Zumbergs (reinis-zumbergs)]

apport information

[Reinis Zumbergs (reinis-zumbergs)]

apport information

[Reinis Zumbergs (reinis-zumbergs)]

apport information

[Reinis Zumbergs (reinis-zumbergs)]

apport information

[Reinis Zumbergs (reinis-zumbergs)]

apport information

[Reinis Zumbergs (reinis-zumbergs)]

apport information

[Reinis Zumbergs (reinis-zumbergs)]

apport information

[Reinis Zumbergs (reinis-zumbergs)]

apport information

[Reinis Zumbergs (reinis-zumbergs)]

apport information

[Reinis Zumbergs (reinis-zumbergs)]

apport information

[Reinis Zumbergs (reinis-zumbergs)]

apport information

[Reinis Zumbergs (reinis-zumbergs)]

apport information

[Reinis Zumbergs (reinis-zumbergs)]

apport information

[Reinis Zumbergs (reinis-zumbergs)]

apport information

[Reinis Zumbergs (reinis-zumbergs)]

BTW, how could I detrmine if it's not a physical issue in hardware?

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc4-raring/

[Reinis Zumbergs (reinis-zumbergs)]

Tested with the suggested kernel - same result.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Reinis Zumbergs (reinis-zumbergs)]

It took me lot's of hours over many weekends to finally upgrade BIOS. Dell is really trying to make it hard for us. None of the procedures in https://wiki.ubuntu.com/DellBIOS worked.

My BIOS' version A14. But unfortunately it has not solved my problem. The video feed is still black the same way.

My main installatiion is now 13.10 and I have alos tested 14.04 dailies. Same issue.

[Reinis Zumbergs (reinis-zumbergs)]

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
A14
12/26/2013

[penalvch (penalvch)]

Reinis Zumbergs, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc3-trusty/ and advise if this is reproducible?

[Reinis Zumbergs (reinis-zumbergs)]

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc3-trusty/ has only i386 packages and although directory name says "v3.14-rc3", inside there are only packages with "3.13 ... rc3" in their file names(?? :(). Anyway, I tried :) but got only blinking CapsLock. Then I searched and found out that one can not run 64 software on 32 kernel :)

 Then with high hopes tried amd64 packages from "v3.14-rc2-trusty", but they also gave me blinking CapsLock :(

Then I tried "v3.14-rc2-trusty" packages with my Trusty test installation, kernel worked but still no video.
Just realized that my original report is missing one detail - usually image appears for fraction of second, when "opening" video and then blanks out.

[penalvch (penalvch)]

Reinis Zumbergs, the next step is to bisect from 11.10 (kernel 3.0.x) to 12.01.01 (kernel 3.2.0-24.37-generic) in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]