You are not logged in.

#1 2010-12-23 18:07:25

carlocci
Member
From: Padova - Italy
Registered: 2008-02-12
Posts: 368

Logitech Quickcam Messenger [046d:08f0]

I was extremely surprised when the kernel gave me the illusion of plug and play, using the gspca driver for this device.
Unfortunately the gspca driver only supports the 046d:08da cam with the same name.
It looks like the actual driver to be used is the one at http://mag.cx/messenger/ , which is prepackaged in community under the name qc-usb-messenger.
Unfortunately, despite seemingly detecting everything...

usb 3-1: new full speed USB device using ohci_hcd and address 3                 
qcmessenger: QuickCam USB camera found (driver version QuickCam Messenger/Communicate USB 1.8 $Date: 2008/05/26 00:00:00 $)                                     
qcmessenger: Kernel:2.6.36-ARCH bus:3 class:FF subclass:FF vendor:046D product:08F0                                                                             
qcmessenger [43.124095]: poisoning qc in qc_usb_init                            
qcmessenger [43.132971]: E00A contains 08F0                                     
qcmessenger: Sensor VV6450 detected                                             
input: Quickcam snapshot button as /devices/virtual/input/input6                
qcmessenger [43.136258]: Quickcam snapshot button registered on usb-0000:00:02.1-1/input0                                                                       
qcmessenger: Registered device: /dev/video0                                     
qcmessenger [43.234773]: failed qc_v4l_ioctl()=-515                             
[drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID   
qcmessenger [ 8.410065]: failed qc_v4l_ioctl()=-515

... it doesn't work

carlocci ~/temp  $  xawtv                                                       
This is xawtv-3.95, running on Linux/i686 (2.6.36-ARCH)                         
xinerama 0: 1024x768+0+0                                                        
/dev/video0 [v4l]: ioctl VIDIOCGCAP: Inappropriate ioctl for device             
libv4l2: error getting capabilities: Inappropriate ioctl for device             
ioctl: VIDIOC_QUERYCAP(driver="";card="";bus_info="";version=0.0.0;capabilities=0x0 []): Inappropriate ioctl for device                                         
no video grabber device available                                               

Does a wrong ioctl mean it's not the right driver?
Is it common that devices with the same id are in fact different devices?

Any help is very welcome,
thanks for your time.

Offline

Board footer

Powered by FluxBB