045e:0721 Microsoft LifeCam NX-3000 not detected

[Jürgen Liebmann]

Since upgrate from quantal to raring I have the a problem with the webcam "Microsoft LifeCam NX-3000". The webcam doesn't work.

The last good kernel is 3.8.0-15.25, while the bug first appears with kernel 3.8.0-16.26.

In /var/log/syslog I can see:
May 3 07:46:44 master kernel: [ 61.441466] uvcvideo: Found UVC 1.00 device Microsoft LifeCam NX-3000 (045e:0721)
May 3 07:46:44 master kernel: [ 61.441923] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
May 3 07:46:44 master kernel: [ 61.442272] uvcvideo: Failed to query (129) UVC probe control : -32 (exp. 26).
May 3 07:46:44 master kernel: [ 61.442275] uvcvideo: Failed to initialize the device (-5).
May 3 07:46:44 master kernel: [ 61.442350] usbcore: registered new interface driver uvcvideo
May 3 07:46:44 master kernel: [ 61.442352] USB Video Class driver (1.1.1)

The kernel is the actual kernel of raring (3.8.0-19-generic, package linux - 3.8.0-19.30).

But when I boot raring with kernel 3.5.0-27 (last kernel from quantal) the webcam it works fine:

May 3 07:39:36 master kernel: [ 370.964836] uvcvideo: Found UVC 1.00 device Microsoft LifeCam NX-3000 (045e:0721)
May 3 07:39:36 master kernel: [ 370.965309] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
May 3 07:39:36 master kernel: [ 370.966042] input: Microsoft LifeCam NX-3000 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input15
May 3 07:39:36 master kernel: [ 370.966208] usbcore: registered new interface driver uvcvideo
May 3 07:39:36 master kernel: [ 370.966212] USB Video Class driver (1.1.1)

WORKAROUND: Create a file /etc/modprobe.d/uvcvideo.conf with:
options uvcvideo quirks=0x100

---
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: liebmann 2988 F.... pulseaudio
 /dev/snd/controlC0: liebmann 2988 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
DistroRelease: Ubuntu 13.04
InstallationDate: Installed on 2011-05-13 (722 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Shuttle Inc. SH55J
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=/dev/sda1 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
RfKill:

Tags: raring
Uname: Linux 3.8.0-19-generic x86_64
UpgradeStatus: Upgraded to raring on 2013-04-25 (8 days ago)
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare users
dmi.bios.date: 06/18/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SH55J
dmi.board.vendor: Shuttle Inc.
dmi.board.version: V10
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd06/18/2010:svnShuttleInc.:pnSH55J:pvrV10:rvnShuttleInc.:rnSH55J:rvrV10:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: SH55J
dmi.product.version: V10
dmi.sys.vendor: Shuttle Inc.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1176126/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[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 1176126

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.

[Jürgen Liebmann (k-info-1)]

apport information

[Jürgen Liebmann (k-info-1)]

apport information

[Jürgen Liebmann (k-info-1)]

apport information

[Jürgen Liebmann (k-info-1)]

apport information

[Jürgen Liebmann (k-info-1)]

apport information

[Jürgen Liebmann (k-info-1)]

apport information

[Jürgen Liebmann (k-info-1)]

apport information

[Jürgen Liebmann (k-info-1)]

apport information

[Jürgen Liebmann (k-info-1)]

apport information

[Jürgen Liebmann (k-info-1)]

apport information

[Jürgen Liebmann (k-info-1)]

apport information

[Jürgen Liebmann (k-info-1)]

apport information

[Jürgen Liebmann (k-info-1)]

apport information

[Jürgen Liebmann (k-info-1)]

apport information

[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].

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-raring/

[Jürgen Liebmann (k-info-1)]

The mainline kernel (3.9.0-030900-generic) does not fix this bug.
Sorry I had a problem with adding tag!

[penalvch (penalvch)]

Jürgen Liebmann, as per http://global.shuttle.com/products/productsDownload?productId=1409 an update is available for your BIOS (SH55JSCG.107). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

[Jürgen Liebmann (k-info-1)]

I have updated BIOS to SH55JSCG.107, but it doesn't change anything.

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
080015
01/17/2011

[penalvch (penalvch)]

Jürgen Liebmann, thank you for updating your BIOS. Could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc3-saucy/ ?

[Jürgen Liebmann (k-info-1)]

Sorry, the mainline kernel (3.11.0-031100rc3-generic) doesn't fix this problem.
I have parallel installed the daily build of saucy, there's the same problem!

[penalvch (penalvch)]

Jürgen Liebmann, thank you for testing the newest mainline kernel. The next step is to commit bisect from Quantal to Raring, in order to identify the offending commit. Could you please do this via https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Jürgen Liebmann (k-info-1)]

The last good kernel is 3.8.0-15.25.
The bug appears with kernel 3.8.0-17.27 and higher!

[Jürgen Liebmann (k-info-1)]

Soory, the bug appears with kernel 3.8.0-16.26 and higher!

[penalvch (penalvch)]

Jürgen Liebmann, the next step is commit bisecting between kernel versions 3.8.0-15.25 and 3.8.0-16.26 in order to identify the offending commit via https://wiki.ubuntu.com/Kernel/KernelBisection .

[Jürgen Liebmann (k-info-1)]

Sorry, but here ends my knowledge about linux. I'm only a ubuntu user, not a kernel developer.
I'm not able to build a own kernel.

The last hints about this problem:

git log --all Ubuntu-3.8.0-15.25..Ubuntu-3.8.0-16.26 |grep UVC
->
    OminiVision webcam 0x05a9:0x2643 needs the same UVC_QUIRK_PROBE_DEF as
    same UVC_QUIRK_PROBE_DEF as other OmniVision model to be recognized
    Merge "msm8960_defconfig: Enable USB Video Class(UVC) Driver" into msm-3.4
    msm8960_defconfig: Enable USB Video Class(UVC) Driver
    USB Video Class(UVC) Driver is required to work with
    UVC driver for the same.
    While testing unplugging an UVC HD webcam with usb-redirection (so through
    ARM: defconfig : Add UVC camera support
    Add UVC USB camera support
    media_entity associated with a UVC entity when creating links. This

[Jürgen Liebmann (k-info-1)]

Now I 've tried to understand what happens by bisect. But when I followed the direction in wiki (https://wiki.ubuntu.com/Kernel/KernelBisection) I have some problems (see also
http://ubuntu.5.x6.nabble.com/Update-https-wiki-ubuntu-com-Kernel-KernelBisection-Inquiry-td4997067.html).
I have the same problems like described in http://forum.ubuntuusers.de/topic/kernel-fuer-git-bisect-kompilieren/#post-4465307.

I have done:
git clone git://kernel.ubuntu.com/ubuntu/ubuntu-raring.git
cd ubuntu-raring
git checkout -b mybisect origin/master
That's ok!

But when I say:
git bisect start Ubuntu-3.8.0-16.26 Ubuntu-3.8.0-15.25
I received:
Bisecting: a merge base must be tested
[405acc3402a3df8df967d1848947dc58f0059664] Linux 3.8.4
and the subdirectories debian and debian.master are deleted. Therefore I can't set an new version in debian.master/changelog and the the build of kernel to test with
fakeroot debian/rules clean
fakeroot debian/rules binary-headers binary-generic
fails!

I search in google how to build an own kernel and found:
cp /boot/config-$(uname -r) .config
make oldconfig
fakeroot make deb-pkg

This creates the files
linux-image-3.8.4+_3.8.4+-1_amd64.deb
linux-firmware-image_3.8.4+-1_amd64.deb
linux-headers-3.8.4+_3.8.4+-1_amd64.deb
linux-libc-dev_3.8.4+-1_amd64.deb

I can install and test them. The result is good:
git bisect good
Bisecting: 280 revisions left to test after this (roughly 8 steps)
[237e06fef3f2c5a461709904073f5ac587450839] UBUNTU: Temporarily disable module check on build

All the following 8 steps are as result bad I got the last revision:
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[74a6af256b4816bf95ca59323dc06b8001673a43] USB: EHCI: work around silicon bug in Intel's EHCI controllers

But I don't know is this result significant? Perhaps the the tags are non-linear?

So I tried to bisect the mainline kernels. I load the mainline kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/:
v3.8.4-raring -> this is ok!
v3.8.5-raring -> this implies the bug
Now I done:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
but the command "git bisect v3.8.4 good" fails with
fatal: Needed a single revision
Ungültige Referenz-Eingabe: v3.8.4

Now I don't know how continuing!
I would like to help, but I need a little "how to" that works fine and give the correct results!

[penalvch (penalvch)]

Jürgen Liebmann, when you are bisecting the upstream mainline kernel, it would be best to switch to commit numbers (ex. 74a6af256b4816bf95ca59323dc06b8001673a43) instead of kernel versions (ex. v3.8.4).

[Jürgen Liebmann (k-info-1)]

Thanks, but how I find the corresponding commit number to the kernel version?
I think, I need the last commit from v3.8.4 and the last commit from v3.8.5 to start the bisect.

[penalvch (penalvch)]

Jürgen Liebmann, you could do it graphically via web browsing https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/ or via the package gitk when you download the git repository.

[Jürgen Liebmann (k-info-1)]

Now I've bisected the upstream mainline kernel and I became the same results:
All commits after v3.8.4 are bad and the last revision I got is:

Bisecting: 0 revisions left to test after this (roughly 0 steps)
[74a6af256b4816bf95ca59323dc06b8001673a43] USB: EHCI: work around silicon bug in Intel's EHCI controllers

I have all builds done how I describe above. The method in wiki (mainline-build-one faec22ffe86d0732eb090c6e6cf5d38543a6a361 raring) fails with
"raring-amd64: chroot not found).

[penalvch (penalvch)]

Jürgen Liebmann, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc4-saucy/ ?

[Jürgen Liebmann (k-info-1)]

The last mainline kernel (linux-image-3.11.0-031100rc4-generic_3.11.0-031100rc4) doesn't fix this problem.

[penalvch (penalvch)]

Jürgen Liebmann, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ?

Thank you for your understanding.

[Jürgen Liebmann (k-info-1)]

This problem is solved!

After reporting bug upstream, the determined hint came from Laurent Pinchart.
I have tested webcam with setting the UVC_QUIRK_PROBE_DEF quirk. With them webcam works proberly.
Laurent will update the uvcvideo quirks table to set UVC_QUIRK_PROBE_DEF by default
for this webcam.

My workaround:
I created a file /etc/modprobe.d/uvcvideo.conf with this content:

options uvcvideo quirks=0x100

Now the webcam workes properly.

[Simon Bonner (simon-bonner)]

Just wanted to add that this fix also works for the Microsoft Lifecam nx-6000.

Thanks!