Logitech QuickCam Messenger with Skype on Linux :: Brave Cobra's Hideout :: If Linux doesn't have the solution, you have the wrong problem.

I finally got my webcam to work on skype (sort of). I have a Logitech QuickCam Messenger (046d:08da), which is a v4l2 (video4linux v2) device. Skype only (still) works with v4l version 1. Thus “Houston, we’ve got a problem”!

I almost solved the puzzle.

First thing I needed to do was to find out what type of webcam I had.

Code

# lsusb | grep Logitech
Bus 002 Device 002: ID 046d:08da Logitech, Inc. QuickCam Messanger

Note the wrongly spelled Mess”a”nger, but that’s beside the point. So my webcam is a Logitech QuickCam Messenger (according to lsusb)

At Ubuntu’s wiki, I found that my webcam was supported by the gspca driver.

Now the gspca drivers finally got into the Linux kernel at version 2.6.27. Very nice, which means I don’t have to get the driver sources anymore. Recompiling my kernel got my webcam supported through the zc3xx driver of gspca.

Code

#make menuconfig
Device Drivers - Multimedia devices - Video Capture Devices - V4L USB Devices - GSPCA based webcams - [M] zc3xx USB Camera Driver
#make modules_install
#update-modules
#modprobe zc3xx

So now I had a working v4l2 device. You can test whether the cam is working with:

Codemplayer -tv driver=v4l2:device=/dev/video0 -fps 25 tv://

However when trying to run this as a v4l device (thus version 1), it fails. I had the v4l1_compat module loaded into my kernel, and still no go:

Codemplayer -tv driver=v4l:device=/dev/video0 -fps 25 tv://

Thus I installed the libv4l library, hoping it would allow me to preload the libv4l1compat.so and thus forcing it to look at the webcam as a v4l1 device instead of a v4l2 one.

CodeLD_PRELOAD=/usr/lib/libv4l/v4l1compat.so mplayer -tv driver=v4l:device=/dev/video0 -fps 25 tv://

And that worked like a charm…now trying this with skype almost got me where I wanted

CodeLD_PRELOAD=/usr/lib/libv4l/v4l1compat.so skype

The image, Skype produces, is still flipped of a vertical axis. No apparent reason why yet, since mplayer displays it correctly, using the preload with v4l1.

Let’s just hope no one notices… for now…