Logitech QuickCam Messenger

paragn · 03-20-2006, 10:02 PM

hi moocow82,
Tell me what you got working? Quickcam Messenger with spca5xx driver??

moocow82 · 03-21-2006, 09:38 AM

I am running SUSE 10.0 kernel 2.6.13-15.8-default with the Logitech Quickcam Messenger.

I followed Brett's post. Make sure to run

Quote:

./install

for the QuickcamAutostart as a normal user instead of root.

natewlew · 03-31-2006, 10:03 PM

I have a logitech quickcam communticate and I am having some trouble try to compile the driver.
When I run "make install" in the "qc-usb-messenger-1.2" directory I get a "make: *** [qc-driver.o] Error 1".

Can someone please give me some help?

bretts5964 · 04-01-2006, 01:13 AM

If you're running SUSE Linux, then posting output from the following commands might be useful since much about the quickcam kernel module depends on specific information about your kernel, distro version and hardware model.

Code:

# uname -r
2.6.13-15.8-default

# cat /etc/SuSE-release
SUSE LINUX 10.0 (i586)
VERSION = 10.0

# lsusb | grep Logitech
Bus 001 Device 002: ID 046d:08f5 Logitech, Inc.

# hwinfo --usb | grep quickcam
  Driver: "quickcam"
    Driver Status: quickcam is active
    Driver Activation Cmd: "modprobe quickcam"

If you're running Debian, post your output anyway. (A couple of those should work on any Linux distro). Otherwise, you might try this deb source package:

qc-usb-messenger-source_1.1-2_all.deb
http://bugs.debian.org/cgi-bin/bugre...=300555;msg=21

If your kernel version is 2.4 on Debian, then that would make big a difference compared to 2.6 on SUSE. Maybe this deb package will automagically patch the quickcam driver for you. Can't say for sure though.

Good luck,
Brett

natewlew · 04-01-2006, 10:43 PM

nate@debian:~$ uname -r
2.4.27-2-386
nate@debian:~$ cat /etc/SuSE???????
nate@debian:~$ lsusb
Bus 001 Device 002: ID 046d:08ad Logitech, Inc.
nate@debian:~$ hwinfo --usb
bash: hwinfo: command not found

I don't know what to put in for the second command. I can't get hwinfo to work. I installed it with apt but, still nothing.
I seem to be having trouble with my modutils.
I tried the messenger 1.1 but I still get the same error. I need to some how downgrade my modutils to an older version.

Here is a post I made in Software:

http://www.linuxquestions.org/questi...d.php?t=430544

Thanks for the Reply, Nate

bretts5964 · 04-02-2006, 01:11 AM

Hi Nate,

You do realize that this is specifically a forum for SUSE/Novell questions? I saw your distro info next to your nick, and figured you might be running both SUSE and Debian. You didn't say, so I wasn't sure. Anyway, two of the commands were valid on your Debian system, and were revealing.

I think this is the code where your compile is failing:

qc-driver.c

Code:

static struct usb_device_id qc_device_table[] = {
	{ USB_DEVICE(0x046D, 0x08F0) },		/* QuickCam Messenger */
	{ USB_DEVICE(0x046D, 0x08F5) },		/* QuickCam Communicate */
	{ USB_DEVICE(0x046D, 0x08F6) },		/* QuickCam Messenger (new) */
	{ }
};

The output from your "lsusb" shows:

Quote:

Originally Posted by natewlew

nate@debian:~$ lsusb
Bus 001 Device 002: ID 046d:08ad Logitech, Inc.

Vendor ID 046D is "Logitech", and Device ID 08AD is "Quickcam Communicate STX". In other words, your device is not supported by the qc-usb-messenger driver since the device doesn't match. I have an earlier model "Quickcam Communicate", device ID 046D:08F5, so technically not the same camera.

Try the "Debian spca5xx" download on this site:
http://mxhaard.free.fr/download.html

I checked the source, and it lists your device, (among many others):

spca5xx.c

Code:

{USB_DEVICE(0x046d, 0x08ad)},	/* Logitech QCCommunicate STX */

And it also appears to support 2.4 kernels, which you seem to be running:

Quote:

Originally Posted by natewlew

nate@debian:~$ uname -r
2.4.27-2-386

Brett

natewlew · 04-02-2006, 01:42 AM

I only run Dedian but, I will take help when I can get it.

I run commands:

make clean
make
make install

It runs for about 2 seconds with no errors but that is it.

Then I run:

lsmod

Quote:

Module Size Used by Not tainted
nls_iso8859-1 2780 1 (autoclean)
isofs 23092 1 (autoclean)
floppy 44120 0 (autoclean)
af_packet 11048 1 (autoclean)
mousedev 3604 1
hid 19076 0 (unused)
input 3040 0 [mousedev hid]
audio 37752 1
usb-uhci 19504 0 (unused)
usbcore 52268 1 [hid audio usb-uhci]
es1371 23820 1
ac97_codec 11252 0 [es1371]
soundcore 3268 6 [audio es1371]
gameport 1388 0 [es1371]
ide-scsi 8272 0
scsi_mod 86052 1 [ide-scsi]
ne2k-pci 4192 1
8390 5280 0 [ne2k-pci]
crc32 2848 0 [8390]
parport_pc 19432 0
parport 21608 0 [parport_pc]
ide-cd 27072 1
cdrom 26212 0 [ide-cd]
rtc 5768 0 (autoclean)
ext3 65388 1 (autoclean)
jbd 34628 1 (autoclean) [ext3]
ide-detect 288 0 (autoclean) (unused)
via82cxxx 9256 1 (autoclean)
ide-disk 12448 4 (autoclean)
ide-core 91832 5 (autoclean) [ide-scsi ide-cd ide-detect via82cxxx ide-disk]
unix 12752 202 (autoclean)

But I get no '/dev/video0"

Here is the instuctions:

Quote:

Kernel 2.4.x
configure your kernel
make dep
go to the spca5xx directories
make clean (to be sure)
make
if all goes right as root :
make install

I really don't get configure your kernel or make dep?

I do thank you for your help. I do know this is a suse forum but I haven't recieved any replys on my other thread.

bretts5964 · 04-02-2006, 10:47 AM

Those instructions are a bit vague, but generally involve kernel compile steps. These may vary depending on which distro you're using, and of course the kernel version.

So I'm not sure how much I can help at this point since I don't use Debian, don't use a 2.4 kernel, and don't have the same camera hardware (though the name would lead you to think otherwise).

I'm a SUSE user, so of course I'd recommend using it. Then you'd be able to try installing a precompiled spca5xx driver, here:
http://moking.free.fr/raoul/SuSE10.0....10-1.i586.rpm

Probably a less extreme option would be to try easycam:
https://wiki.ubuntu.com/Webcam

It's for Ubuntu, not Debian, but uses deb packages and might work. If not, you could always switch to Ubuntu. Not my thing, but if you already like Debian, then it might suit you especially if you're using it for your desktop system. Its popularity would give you a larger community to ask your questions at least. Not to mention a new 2.6 kernel. ;-)

Ubuntu Forums > Logitech QuickCam communicate STX
http://ubuntuforums.org/showthread.php?t=114429

Brett

natewlew · 04-02-2006, 03:37 PM

Ya, Dedian, didn't you know!

Thanks for all of your help, Brett. I finally got this cam working with the driver you recommended. (spca5xx) I didn't realize I had to restart my computer.

All I had to do was run:

Make clean
make
make install

It hardly did anything but when I restarted, the webcam cam turned on.

Even though you are a Suse user you give pretty good help.

Thanks

reddog1 · 04-03-2006, 04:52 PM

Howdy all,

i have been attempting to get my Logitech Quickcam Pro 4000 working, thanks to this post i think i'm partially there, but with a couple issues. I installed using the directions from Bretts post above

see below

). Everthing seems to have installed fine, but when i try using Xawtv, the light on the top of the cam comes on and the screen goes full, but no images are showing. Also, i tried configuring the cam for use in aMSN, again the light comes on but the screen is all grey with no images. The fact that the light comes on leads me to believe its working , but is not configured correctly. I'm just not sure where to go from here.

I posted some output that brett requested, hopefully that will be a start. Any help would be great. I am a bit CLI challenged

, but i follow directions well, Thanks in advance for any help !!

Code:

rich@linux:~> uname -r
2.6.13-15.8-smp

rich@linux:~> cat /etc/SuSE-release
SUSE LINUX 10.0 (i586)
VERSION = 10.0

linux:/home/rich # lsusb | grep Logitech
Bus 001 Device 004: ID 046d:08b2 Logitech, Inc. QuickCam Pro 4000

Quote:

Just got back from some serious googling, and found a workable, if not perfect solution. Get the qc-usb-messenger driver packaged specifically for SUSE 10.0 here:

raoulrpm.youm.org/SuSE_10.0/Q...uSE10.i586.rpm

This works with the latest SUSE kernel (single CPU only), and must be forced to install over the top of /lib/modules/2.6.13-15.8-default/modules.* files, which can be rebuilt with "depmod -a". Install with these commands:
Code:

rpm -Uvh qc-usb-messenger-1.1-modules-2.6.13-15.8-default-SuSE10.i586.rpm --force depmod -a

Now download the QuickcamAutostart package from here:

raoulrpm.youm.org/SuSE_10.0/Q...rt-1.02.tar.gz

Unpack it, then install with this command:
Code:

./install

Apparently, adding the quickcam module to the usual SUSE module startup (in the /etc/sysconfig/kernel file) happens too early in the boot sequence. This QuickcamAutostart utility will wait until KDE starts before loading it. I got my camera to work with Gqcam, kdetv and XawTV.

My output from the command: "dmesg | grep quickcam"
Code:

quickcam: module not supported by Novell, setting U taint flag. quickcam [19.646665]: ----------LOADING QUICKCAM MODULE------------ quickcam [19.646675]: struct quickcam size: 4028 quickcam: QuickCam USB camera found (driver version QuickCam Messenger/Communicate USB $Date: 2004/12/30 10:00:00 $) quickcam: Kernel:2.6.13-15.8-default bus:1 class:FF subclass:FF vendor:046D product:08F5 quickcam [19.646739]: poisoning qc in qc_usb_init quickcam [19.994089]: E00A contains 08F5 quickcam: Sensor VV6450 detected quickcam [20.171968]: Quickcam snapshot button registered on usb-0000:00:04.2-1/input0 quickcam: Registered device: /dev/video0 usbcore: registered new driver quickcam

Brett

bretts5964 · 04-03-2006, 10:04 PM

Here's what I can tell you about your camera...

Your camera is NOT supported by the qc-usb-messenger driver. Your USB device ID is 046d:08b2, so the driver you need is "pwc", which supports the following Logitech cameras, (and many other non-Logitech):

Code:

 { USB_DEVICE(0x046D, 0x08B0) }, /* Logitech QuickCam Pro 3000 */
 { USB_DEVICE(0x046D, 0x08B1) }, /* Logitech QuickCam Notebook Pro */
 { USB_DEVICE(0x046D, 0x08B2) }, /* Logitech QuickCam Pro 4000 */
 { USB_DEVICE(0x046D, 0x08B3) }, /* Logitech QuickCam Zoom (old model) */
 { USB_DEVICE(0x046D, 0x08B4) }, /* Logitech QuickCam Zoom (new model) */
 { USB_DEVICE(0x046D, 0x08B5) }, /* Logitech QuickCam Orbit/Sphere */

A GPL licensed pwc module is actually included with the SUSE kernel, and can be loaded dynamically (without recompiling the kernel). Just enable the pwc module in your kernel:

Code:

modprobe pwc

Then add it to /etc/sysconfig/kernel file so it starts up automatically, add to the end of this line:

Code:

MODULES_LOADED_ON_BOOT="dazuko capability pwc"

If that doesn't work, or if you just want a challenge, then there's a reverse engineered version of pwc which exploits the camera's features more fully, or so I'm told.

Philips USB Webcam Driver for Linux
http://www.saillard.org/linux/pwc/RP...0.6a-1.src.rpm

But first, your output shows you are using an SMP kernel. Do you have 2 or more CPU's in your box? If not, then you should switch to the default (single CPU) kernel. Your journey is long...

If you actually DO have multiple CPU's, then proceed.

As root, install the source code and create a binary RPM for your system:

Code:

rpm -Uvh pwc-10.0.6a-1.src.rpm --force
cd /usr/src/packages
rpmbuild -ba SPECS/pwc.spec --nodeps

If the build is successful, then install the new RPM:

Code:

cd RPMS/i586   
rpm -Uvh kernel-modules-pwc_2.6.13-15.8-smp-10.0.6a-1_suse10.0.i586.rpm

In case you're wondering, the site below is where I figured out which driver your camera needs. It has the best listing of device ID's to choose the correct driver that I have found so far, (look for "Other Linux camera drivers" about half way down the page):

Logitech Quickcam QC-USB driver for Linux
http://www.ee.oulu.fi/~tuukkat/quickcam/quickcam.html

Brett

reddog1 · 04-03-2006, 11:20 PM

hello Brett,

first, thank you for your time, and effort ! i appreciate it !

I have un-installed the "qc-usb-messenger driver". i ran "hwinfo" command with the following results, obviously edited to shorten things up.

Camera Info- This is the return i got without installing another driver. as you will see i already have the "phillips-webcam" driver installed.

Code:

58: USB 00.0: 10f00 Camera
  [Created at usb.122]
  UDI: /org/freedesktop/Hal/devices/usb_device_46
d_8b2_noserial_if0
  Unique ID: ADDn.fy1veyDQJaA
  Parent ID: k4bc.AoUvUKO1+l1
  SysFS ID: /devices/pci0000:00/0000:00:1d.0/usb1
/1-1/1-1:1.0
  SysFS BusID: 1-1:1.0
  Hardware Class: camera
  Model: "Logitech Camera"
  Hotplug: USB
  Vendor: usb 0x046d "Logitech Inc."
  Device: usb 0x08b2
  Driver: "Philips webcam"
  Speed: 12 Mbps
  Module Alias: "usb:v046Dp08B2d0000dc00dsc00dp00
icFFisc00ip00"
  Driver Info #0:
    Driver Status: pwc is active
    Driver Activation Cmd: "modprobe pwc"
  Config Status: cfg=no, avail=yes, need=no, acti
ve=unknown
  Attached to: #57 (Hub)

Next is my cpu info, although i dont not "phyisically" have dual cpu's, i do have a hyperthreading enabled cpu.

Code:

6: None 00.0: 10103 CPU
  [Created at cpu.290]
  Unique ID: rdCR.j8NaKXDZtZ6
  Hardware Class: cpu
  Arch: Intel
  Vendor: "GenuineIntel"
  Model: 15.2.7 "Intel(R) Pentium(R) 4 CPU 3.06GH
z"
  Features: fpu,vme,de,pse,tsc,msr,pae,mce,cx8,ap
ic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,ac
pi,mmx,fxsr,sse,sse2,ss,ht,tm,pbe,cid,xtpr
  Clock: 3415 MHz
  Cache: 512 kb
  Units/Processor: 2
  Config Status: cfg=no, avail=yes, need=no, acti
ve=unknown

77: None 01.0: 10103 CPU
  [Created at cpu.290]
  Unique ID: wkFv.j8NaKXDZtZ6
  Hardware Class: cpu
  Arch: Intel
  Vendor: "GenuineIntel"
  Model: 15.2.7 "Intel(R) Pentium(R) 4 CPU 3.06GH
z"
  Features: fpu,vme,de,pse,tsc,msr,pae,mce,cx8,ap
ic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,ac
pi,mmx,fxsr,sse,sse2,ss,ht,tm,pbe,cid,xtpr
  Clock: 3415 MHz
  Cache: 512 kb
  Units/Processor: 2
  Config Status: cfg=no, avail=yes, need=no, acti
ve=unknown

Should i proceed as though i have one processor or two?

Thanks again for your time !

ps, im gonna test the cam as-is, without any more modifications. This didnt work previously, but who knows.

bretts5964 · 04-03-2006, 11:44 PM

Well, obviously the SUSE installer decided to go with an SMP kernel, so don't change it. Your hyperthreaded CPU looks like two as far as the kernel knows. This just means that you can't use any precompiled RPM's that reference the "default" kernel rather than "smp" because they will try to install to the wrong place. Either of the pwc modules should work. The pwc module from Saillard.org is compiled to your kernel specifically, and the one that comes with the kernel is already installed.

I believe that the hwinfo command is not standard Linux, but rather is a SUSE specific tool. It only shows what hardware was detected, and any associated drivers. If the pwc driver is already loaded, then did you load it or did it start on its own?

reddog1 · 04-04-2006, 12:19 AM

ok, the pwc module loaded on its own, and further tests of the cam, came up with no video. Tried testing in "kdetv" as well as "aMSN"

kdetv returns: unable to grab video, try playing with the v4L config, (i dont remember that verbatum). Nothing seems to work at the moment.

Also you mentioned:

Quote:

This just means that you can't use any precompiled RPM's that reference the "default" kernel rather than "smp" because they will try to install to the wrong place.

In the future, should i be looking for RPM's that are specifically "smp"?

bretts5964 · 04-04-2006, 01:03 AM

Oh yeah, forgot to mention. You should already have video4linux installed, so check to see if they're installed with these commands:

Code:

rpm -q v4l-conf
rpm -q v4l-tools
rpm -q xawtv

If you install xawtv through YAST, it should add the v4l RPM's as dependencies automatically.

Also, after you issue the "modprobe pwc" command to load the driver, do the following depmod command to rebuild the module dependencies. Then reboot.

Code:

/sbin/depmod -a -F /boot/System.map-2.6.13-15.8-smp 2.6.13-15.8-smp >/dev/null 2>&1 || true

I don't run smp, but you shouldn't have any problems with RPM's at the application level, like KDE, Firefox or whatever, but could run into issues with hardware drivers or some system level utilities like fsck or gcc. I'm not an expert, but that's my guess. This is for sure: any RPM that provides a kernel module must install the drivers in the correct location, which is always associated with a specific kernel version.