Problem with 046d:08af Logitech Quickcam Easy/Cool - broken with in-kernel drivers, works with gspcav1
Hi,
I just tried out the in-kernel gspca drivers for my 046d:08af Logitech, Inc. QuickCam Easy/Cool, however I don't get any picture with cheese and only green noise with skype.
Before using the in-kernel drivers the webcam used to work quite well with the old out-of-kernel gspcav1 drivers.
I compared both drivers and the old ones used the SENSOR_HV7131B, whereas the new driver detects the HV7131R(c)
snippet old driver:
case 0x08af: spca50x->desc = LogitechQCCool; spca50x->bridge = BRIDGE_ZC3XX; spca50x->sensor = SENSOR_HV7131B;
output dmesg after plugin camera in
usb 4-2: new full speed USB device using uhci_hcd and address 6 usb 4-2: configuration #1 chosen from 1 choice gspca: probing 046d:08af zc3xx: probe 2wr ov vga 0x0000 zc3xx: probe sensor -> 11 zc3xx: Find Sensor HV7131R(c) gspca: probe ok usbcore: registered new interface driver zc3xx zc3xx: registered
I already tried out the module_param force_sensor for the values 4,5,6 - but neither gave an appropriate result.
I hope you can help me resolve this issue - I would be glad if I could help testing/debugging the problem.
Best Regards,
Peter
Quoted 28 lines · On Sun, 28 Jun 2009 15:14:10 +0200 Peter Hüwe <[email protected]> wrote:
I just tried out the in-kernel gspca drivers for my 046d:08af Logitech, Inc. QuickCam Easy/Cool, however I don't get any picture with cheese and only green noise with skype.
Before using the in-kernel drivers the webcam used to work quite well with the old out-of-kernel gspcav1 drivers.
I compared both drivers and the old ones used the
SENSOR_HV7131B, whereas the new driver detects the HV7131R(c)snippet old driver:
case 0x08af: spca50x->desc = LogitechQCCool; spca50x->bridge = BRIDGE_ZC3XX; spca50x->sensor = SENSOR_HV7131B;output dmesg after plugin camera in
usb 4-2: new full speed USB device usinguhci_hcdand address
6 usb 4-2: configuration #1 chosen from 1 choicegspca: probing 046d:08af zc3xx: probe 2wr ov vga 0x0000 zc3xx: probe sensor -> 11 zc3xx: Find Sensor HV7131R(c) gspca: probe ok usbcore: registered new interface driver zc3xx zc3xx: registered
Quoted 5 lines
I already tried out the
module_paramforce_sensorfor the values 4,5,6 - but neither gave an appropriate result.I hope you can help me resolve this issue - I would be glad if I could help testing/debugging the problem.
Hi Peter,
Did you use the v4l2 wrapper when running the applications? (look in my page for more information)
Otherwise, the sensor value set in the old gspcav1 driver was not used:
the sensor was and is still found by probing the webcam hardware.
Best regards.
Signature · 2 lines
Ken ar c'hentañ | ** Breizh ha Linux atav! ** Jef | http://moinejf.free.fr/
Quoted 2 lines
Did you use the v4l2 wrapper when running the applications? (look in my page for more information)
Not that I know - atleast not explicitly.
Quoted 2 lines
Otherwise, the sensor value set in the old gspcav1 driver was not used:
the sensor was and is still found by probing the webcam hardware.
Yeah - you're right, i'm sorry - I enabled debug messages on the old gspcav1 driver and it says
gspca: [zc3xx_config:669] Find Sensor HV7131R(c)
so you're right - mea culpa :)
However I created an usbmon output for both and they seem to differ a bit (not only in the usb-enum)
You can find the files here:
http://www.hs-augsburg.de/~phuewe/usbmon-output.tar.gz
Would be very nice if we could find the source of my problem and fix it.
Best Regards,
Peter
Quoted 2 lines
Did you use the v4l2 wrapper when running the applications? (look in my page for more information)
Hi,
I tried using cheese with LD_PRELOAD=/usr/lib64/libv4l/v4l1compat.so - and it works!
However this does not work with skype :/ (skype does not allow preloading)
Any suggestions how I get skype to use the compat wrapper?
Thank you,
Peter
Quoted 7 lines · On Sun, 28 Jun 2009 22:50:58 +0200 Peter Hüwe <[email protected]> wrote:
I tried using cheese with LD_PRELOAD=/usr/lib64/libv4l/v4l1compat.so - and it works!
However this does not work with skype :/ (skype does not allow preloading)
Any suggestions how I get skype to use the compat wrapper?
Hi Peter,
You must export LD_PRELOAD. I use a simple script:
#!/bin/sh export LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so exec /usr/bin/skype
Cheers.
Signature · 2 lines
Ken ar c'hentañ | ** Breizh ha Linux atav! ** Jef | http://moinejf.free.fr/
Am Montag 29 Juni 2009 09:25:41 schrieb Jean-Francois Moine:
Quoted 6 lines
Quoted 1 line
Any suggestions how I get skype to use the compat wrapper?
You must export
LD_PRELOAD. I use a simple script:#!/bin/sh export LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so exec /usr/bin/skype
Hi,
unfortunately this doesn't work with skype :/
~ $ cat startskype.sh
#!/bin/sh
export LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so
exec /usr/bin/skype
~ $ ./startskype.sh
ERROR: ld.so: object '/usr/lib/libv4l/v4l1compat.so' from LD_PRELOAD cannot be
preloaded: ignored.
seems that I have to stick with my old kernel :/
Peter
Quoted 9 lines · On Mon, 29 Jun 2009 12:30:09 +0200 Peter Hüwe <[email protected]> wrote:
unfortunately this doesn't work with skype :/
~ $ cat
startskype.sh
#!/bin/sh
export LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so
exec/usr/bin/skype
~ $ ./startskype.sh
ERROR: ld.so: object '/usr/lib/libv4l/v4l1compat.so' fromLD_PRELOADcannot be preloaded: ignored.
Hi Peter,
Indeed, you are running a 64bits application:
#!/bin/sh export LD_PRELOAD=/usr/lib64/libv4l/v4l1compat.so exec /usr/bin/skype
Cheers.
Signature · 2 lines
Ken ar c'hentan | ** Breizh ha Linux atav! ** Jef | http://moinejf.free.fr/
Am Montag 29 Juni 2009 12:40:34 schrieb Jean-Francois Moine:
Quoted 9 lines
Hi Peter,
Indeed, you are running a 64bits application:
#!/bin/sh export LD_PRELOAD=/usr/lib64/libv4l/v4l1compat.so exec /usr/bin/skypeCheers.
Hi :)
/usr/lib is just a link to /usr/lib64 -
$ ls -lahd /usr/lib lrwxrwxrwx 1 root root 5 20. Dez 2008 /usr/lib -> lib64
but I tried it explicitly with both versions:
ERROR: ld.so: object '/usr/lib32/libv4l/v4l1compat.so' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object '/usr/lib32/libv4l/v4l1compat.so' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object '/usr/lib64/libv4l/v4l1compat.so' from LD_PRELOAD cannot be preloaded: ignored.
Seems I have to wait till skype releases a v4l2 compatible skype binary - but regarding the development cycle of skype this will be ... ahem ... never :)
Thanks!
Peter
Quoted 10 lines · On Mon, 29 Jun 2009 12:54:34 +0200 Peter Hüwe <[email protected]> wrote:
/usr/libis just a link to/usr/lib64-$ ls -lahd /usr/lib lrwxrwxrwx 1 root root 5 20. Dez 2008 /usr/lib -> lib64but I tried it explicitly with both versions:
ERROR: ld.so: object '/usr/lib32/libv4l/v4l1compat.so' fromLD_PRELOADcannot be preloaded: ignored.
ERROR: ld.so: object '/usr/lib32/libv4l/v4l1compat.so' fromLD_PRELOADcannot be preloaded: ignored.
Quoted 6 lines
ERROR: ld.so: object '
/usr/lib64/libv4l/v4l1compat.so' fromLD_PRELOADcannot be preloaded: ignored.Seems I have to wait till skype releases a v4l2 compatible skype binary - but regarding the development cycle of skype this will be ... ahem ... never :)
It is not a skype problem but a loader problem. If you have both the 32 and 64 bits libraries, it means that your skype is statically linked (you may check it by 'file /usr/bin/skype'). Then, get a dynamically linked version.
Cheers.
Signature · 2 lines
Ken ar c'hentañ | ** Breizh ha Linux atav! ** Jef | http://moinejf.free.fr/
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Am Dienstag 30 Juni 2009 12:26:11 schrieben Sie:
Quoted 7 lines
What is sure is that skype has no problem. It is a loader problem.
May you check the type of
/usr/lib32/libv4l/v4l1compat.so?And, also, what gives 'ldd
/opt/skype/skype'?Cheers.
Hi,
d'oh :) -
file /usr/lib32/libv4l/v4l1compat.so -> No such file or directory
After I compiled the v4l in 32 bit mode for my machine, skype _WORKS_ again and it seems the picture is _even better_ than before! Unfortunately gentoo did not built the 32 bit version itself, which is usually the case.
I'm really sorry for blaming the driver, skype while it was only my fault - mea culpa.
Thank you very much for your support and your great work - you made my day :)
Peter