Oh, I unplugged and plugged it in again and now it works again. Before today I never had to do that. Unplugging it means crawling on the floor behind the computer, so I rather not do that all the time.

Hi,

Changing component, this likely is a kernel issue.

Can you do lsusb in a terminal and copy and paste the output (or at least the line corresponding to your webcam) here, so that we know exactly which model you've ?

Thanks & Regards,

Hans

$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 003 Device 003: ID 0b05:17d0 ASUSTek Computer, Inc. 
Bus 003 Device 007: ID 045e:00dd Microsoft Corp. Comfort Curve Keyboard 2000 V1.0
Bus 003 Device 008: ID 045e:076e Microsoft Corp. 
Bus 003 Device 002: ID 174c:2074 ASMedia Technology Inc. 
Bus 003 Device 005: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Because I can't tell what of this is the webcam here some more using uvcdynctrl:


$ uvcdynctrl -l
Listing available devices:
  video0   Microsoft® LifeCam HD-5001
    Media controller device: /dev/media0
ERROR: Unable to open media controller device '/dev/media0': Permission denied (Error: 13)
ERROR: Unable to list device entities: Invalid device or device cannot be opened. (Code: 5)

$ sudo chmod a+rw /dev/media0

$ uvcdynctrl -l
Listing available devices:
  video0   Microsoft® LifeCam HD-5001
    Media controller device: /dev/media0
    Entity 1: Microsoft® LifeCam HD-5001. Type: 65537, Revision: 0, Flags: 1, Group-id: 0, Pads: 1, Links: 0
      Device node
      Entity: 1, Pad 0, Flags: 1
    Entity 2: Extension 5. Type: 131072, Revision: 0, Flags: 0, Group-id: 0, Pads: 2, Links: 1
      Subdevice:       Entity: 2, Pad 0, Flags: 1
      Entity: 2, Pad 1, Flags: 2
      Out link: Source pad { Entity: 2, Index: 1, Flags: 2 } => Sink pad { Entity: 1, Index: 0, Flags: 1 }
    Entity 3: Processing 4. Type: 131072, Revision: 0, Flags: 0, Group-id: 0, Pads: 2, Links: 1
      Subdevice:       Entity: 3, Pad 0, Flags: 1
      Entity: 3, Pad 1, Flags: 2
      Out link: Source pad { Entity: 3, Index: 1, Flags: 2 } => Sink pad { Entity: 2, Index: 0, Flags: 1 }
    Entity 4: Selector 3. Type: 131072, Revision: 0, Flags: 0, Group-id: 0, Pads: 2, Links: 1
      Subdevice:       Entity: 4, Pad 0, Flags: 1
      Entity: 4, Pad 1, Flags: 2
      Out link: Source pad { Entity: 4, Index: 1, Flags: 2 } => Sink pad { Entity: 3, Index: 0, Flags: 1 }
    Entity 5: Camera 1. Type: 131072, Revision: 0, Flags: 0, Group-id: 0, Pads: 1, Links: 1
      Subdevice:       Entity: 5, Pad 0, Flags: 2
      Out link: Source pad { Entity: 5, Index: 0, Flags: 2 } => Sink pad { Entity: 4, Index: 0, Flags: 1 }

Btw. the microphone of the webcam is listed in the KDE mixer (and in audacity and in Chrome), but I don't get anything when I try using that to record (the analog microphone input of my PC has a *really* loud background noise, so I tried to use the webcam's microphone).

Hmm,

Can you do dmesg > log, and then attach the generated log file here?

Thanks,

Hans

Created attachment 863327 [details]
dmesg > log

Thanks for the information, I've mailed the upstream uvc webcam driver maintainer with some info from your dmesg. He may very well enter a comment directly into this bug, if not I'll let you know when he gets back to me.

Hi,

I've just heard back from the uvc driver maintainer.

First of all, can you try creating a "/etc/modprobe.d/uvc_video.conf" file with as contents:

options uvc_video quirks=0x00000100

And then reboot, and see if that helps?

If that does not help, can you try booting into a previous kernel (by pressing a key in grub, and then selecting an older kernel). And see if that helps, and if it does report the working kernel version number here ?

Thanks & Regards,

Hans

As I mentioned before replugging the camera did work and now I don't even have to replug it. Don't know what was the problem. Anyway, the built in microphone does not work. Would the quriks setting help with that as well? What exactly does it do?

(In reply to Mathias Panzenböck from comment #9)
> As I mentioned before replugging the camera did work and now I don't even
> have to replug it.

Ah, likely a timing related bug in the cams firmware then, which you just happen to trigger, I've the same with my (slightly different) microsoft cam, closing this bug then.

> Don't know what was the problem. Anyway, the built in
> microphone does not work. 

Try doing:
sudo yum install pavucontrol
pavucontrol

Then go to the input devices tab, and see if the mic is there, if it is there make it the default, and try talking into it and see if the volume bar below it moves. If it does everything is working fine, and the problem may have been that it was not the default, or your application somehow needs to be configured to use it.

If the volume bar does not move, or the mic is not there please file a new bug for this against component kernel. Note that you may have better luck actually getting some help with the mic by sending a mail to the alsa-devel mailinglist though.

> Would the quriks setting help with that as well?

No, the quirk setting only works for video related problems.

> What exactly does it do?

Avoid some trouble some uvc commands.