Testing new headset and cameras

Birger Wathne birger at birger.sh
Tue Nov 10 11:15:46 UTC 2009


Sitat Birger Wathne <birger at birger.sh>:


> So.. Microsoft LifeCam Cinema, here we go. dmesg is promising for video,
> not
> so promising for audio (alsa traceback in dmesg output). Abrt caught it
> as a
> kernel issue but doesn't want to send it :-(

I ran a yum update and went from kernel -122 to -127. Rebooted without the
camera, plugged it in, and mic seems to work now.

This is what I now see in dmesg

usb 1-5: new high speed USB device using ehci_hcd and address 3
usb 1-5: New USB device found, idVendor=045e, idProduct=075d
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: Microsoft® LifeCam Cinema(TM)
usb 1-5: Manufacturer: Microsoft
usb 1-5: configuration #1 chosen from 1 choice
Linux video capture interface: v2.00
ALSA sound/usb/usbaudio.c:1295: 3:3:1: cannot get freq at ep 0x82
uvcvideo: Found UVC 1.00 device Microsoft® LifeCam Cinema(TM) (045e:075d)
input: Microsoft® LifeCam Cinema(TM) as
/devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0/input/input14
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
ALSA sound/usb/usbaudio.c:1295: 3:3:1: cannot get freq at ep 0x82
ALSA sound/usb/usbaudio.c:1295: 3:3:1: cannot get freq at ep 0x82

I have this nagging feeling I am getting audio input from bot the headset
and the camera now... Selecting one or the other (even selecting internal
audio card without any mic) I am getting the same readouts in the 'input
level' indicator when I make a sound. It doesn't matter which mic I enable
or which one I make the sound into...

-- 
birger




More information about the fedora-test-list mailing list