LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Webcam Drivers for Mandriva: Help! (https://www.linuxquestions.org/questions/linux-hardware-18/webcam-drivers-for-mandriva-help-560059/)

rm_-rf_windows 06-07-2007 07:10 PM

Webcam Drivers for Mandriva: Help!
 
I'm on Mandriva 2007.0, kernel 2.6.17-5mdv.

My Webcam is the Logitech QuickCam Communicate STX Webcam. I think that's what it is called, here's a picture of it:

http://products.howstuffworks.com/logitech-quickcam-communicate-stx-webcam-review.htm


Code:

[root@localhost ~]# lsusb
Bus 003 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 003: ID 046d:08f5 Logitech, Inc.
Bus 002 Device 001: ID 0000:0000
[root@localhost ~]#

Here are some of the sites I've consulted:

http://mxhaard.free.fr/download.html
http://fr2.rpmfind.net/linux/rpm2htm...submit=Search+
http://help.lockergnome.com/linux/We...ict412781.html
http://club.mandriva.com/xwiki/bin/v...ardwareWebcams
http://www.steletch.org/spip.php?article39
...and there were others too...


Here's what I get when I run the following in the terminal:
Code:

[root@localhost ~]# urpmq --fuzzy dkms
dkms
dkms-abituguru
dkms-actuator
dkms-adm8211
dkms-aic79xx
dkms-cdemu
dkms-cluster
dkms-em8300
dkms-fuse
dkms-fusion
dkms-ipw3945
dkms-ivtv-0.4
dkms-ivtv-0.6
dkms-ivtv-0.7
dkms-lazyfs
dkms-libafs
dkms-lirc
dkms-lirc-parallel
dkms-mcs7830
dkms-minimal
dkms-ndiswrapper
dkms-nozomi
dkms-omnibook
dkms-ozscr
dkms-pwc
dkms-qc-usb-messenger
dkms-qvm86
dkms-spca5xx
dkms-unionfs
dkms-usbvision
dkms-visdn
dkms-vloopback
dkms-zaptel
dkms-zd1211
[root@localhost ~]# urpmi dkms-spca5xx
Tous les paquetages sont déjà installés (=The packages associated with dkms-spca5xx are all already installed)
[root@localhost ~]#

Code:

[root@localhost spca5xx-0.60.00-1mdv2007.0]# less dkms.conf
(...)
PACKAGE_VERSION="0.60.00-1mdv2007.0"

# Items below here should not have to change with each driver version
PACKAGE_NAME="spca5xx"
MAKE[0]="make -C ${kernel_source_dir} SUBDIRS=${dkms_tree}/${PACKAGE_NAME}/${PAC
KAGE_VERSION}/build modules"
CLEAN="make -C ${kernel_source_dir} SUBDIRS=${dkms_tree}/${PACKAGE_NAME}/${PACKA
GE_VERSION}/build clean"
BUILT_MODULE_NAME[0]="$PACKAGE_NAME"
DEST_MODULE_LOCATION[0]="/kernel/drivers/usb/media"
REMAKE_INITRD="no"
AUTOINSTALL="YES"
dkms.conf lines 1-11/11 (END)

...And yes, I have rebooted my computer after installing the drivers.

I've spent several hours battling it out with my browser, my computers, my Webcam and IM client configuration settings. The camera doesn't even light up!

This is what I would like to be able to do:

1/ First and foremost, use the Webcam with IMs such as aMSN, Kopete, etc.
2/ Be able to film things, to record video with the Webcam
3/ Or course, to be able to test and configure the Webcam (I'd need a little program for this)

Can anybody offer me some assistance?

Thanks!

maroonbaboon 06-09-2007 08:52 AM

Apparently Logitech put out several different cameras under this name, with different USB ID's. But you seem to be in luck as your cam is on the list for the driver here:

http://home.mag.cx/messenger/

The bad news is that you will probably have to compile and install it yourself, unless some kind person has packaged it for your distro.

rm_-rf_windows 06-10-2007 05:15 AM

Ah man! That's great! I had a look at the site. The third link is my webcam! Great!

...But I'm not sure how to compile it! I didn't see any instructions. Are there a lot of steps involved? I'm

I already messed around with my kernel, and I think it's caused some problems. I did this to install dkms-spca5xx. I must admit, I didn't really know what I was doing, and now I don't know how to revert back to the old kernel.

I did create a 'backups' directory before doing so, but I'm not sure what needs to be done exactly to revert back. Here are the details:
Code:

[root@localhost boot]# ls
backups/          initrd-2.6.17-5mdv.img  message-graphic
boot.0300          initrd.img@            message-text
config@            kernel.h@              System.map@
config-2.6.17-5mdv  kernel.h-2.6.17-5mdv    System.map-2.6.17-5mdv
fr-latin1.klt      map                    vmlinuz@
grub/              message@                vmlinuz-2.6.17-5mdv
[root@localhost boot]# cd backups
[root@localhost backups]# ls

config-2.6.17-5mdv.backup    System.map-2.6.17-5mdv.backup
kernel.h-2.6.17-5mdv.backup  vmlinuz-2.6.17-5mdv.backup
[root@localhost backups]#

I created the "backups" directory.

So, two questions:
1/ How do I get my old kernel back? What's the easiest way to do it?
2/ How do I install the drivers for my webcam?

Thanks a lot!

maroonbaboon 06-10-2007 09:51 AM

Hard to know exactly how to get your system back to its original state, without knowing exactly what you did. Also I see Mandriva uses the GRUB bootloader, which I'm not familiar with. It looks like you can boot the computer, or you wouldn't be able to list the directories. In that case as a last resort you can always back up your personal files and reinstall.

As for installing the new driver you at least need to install the kernel header files (also known as 'include' files) which match the kernel you are running. These make sure that your new driver module is compatible with the existing kernel. Usually the distro supplies these as a package. Instructions for compiling the new driver are usually included with the driver code - look for anything called README or INSTALL.

With luck you should not have to mess with the kernel itself. Sorry if that's all a bit vague, but its difficult to give specific instructions without knowing the quirks of a particular distro.

rm_-rf_windows 06-12-2007 12:14 AM

maroonbaboon,

Actually, I don't know if reinstalling the old kernel is necessary, the system seems to be working fine now. I finally figured out how to update the system without getting error messages, so that is no longer a problem. I have another problem I'm working on resolving: I don't get any sound...

Anyway, it's the Webcam driver that interests me the most. How do you go about installing it?

Electro 06-12-2007 01:12 AM

I read the README file for qc-usb-messager. It should be straight forward. If you can not get it work post what you did and any errors that might have came up.

In order to compile it, make sure you have the kernel source code that matches your version. Also make sure you have the gnu C/C++ compiler and any glibc headers. To known what kernel version you are running, type uname -r.

Sound is easy, post your sound card and then we can tell you how to do. Though harddrake can help you setup most sound cards. If it does setup your sound card, use alsamixer to the the settings.

maroonbaboon 06-12-2007 06:05 AM

The outline for compiling/install a new driver is

1. Download the source code (often a tar.gz or tar.bz2 file).
2. Unpack (gzip (or bzip2) -cd driver.tar.gz | tar xvf -).
3. Change into the newly unpacked directory.
4. Read documentation :study:
5. Do any extra configuration.
6. Run 'make'
7. Run 'make install' (need to be root for this).
8. Load your new module ('modprobe ....)
9. Enjoy new hardware :)

Of course, it is rarely this simple :(

rm_-rf_windows 06-26-2007 12:35 AM

Well, I've been working on learning more about make, makefiles and 'make install'... I've gone through a good deal of the installation process, have received some warnings (about the kernel version, etc.)... In any case, I'm stuck here:
Code:

You decided to do it, here we go...
=== Leaving root mode ===
The driver detected the following supported cameras:
quickcam [27.144298]: ----------LOADING QUICKCAM MODULE------------
quickcam [27.144310]: struct quickcam size: 4148
quickcam: QuickCam USB camera found (driver version QuickCam Messenger/Communicate USB 1.5 $Date: 2006/11/05 00:00:00 $)
quickcam: Kernel:2.6.17-5mdv bus:2 class:FF subclass:FF vendor:046D product:08F5
quickcam [27.144377]: poisoning qc in qc_usb_init
quickcam [27.155106]: E00A contains 08F5
quickcam: Sensor VV6450 detected
quickcam [27.156616]: Quickcam snapshot button registered on usb-0000:00:02.1-2/input0
quickcam: Registered device: /dev/video0
usbcore: registered new driver quickcam
I will be using , if there are more cameras I'll not test them.
Press Ctrl+C to quit, Enter to continue --->

Testing if  is correct.
ls: : Aucun fichier ou répertoire de ce type
[!] You don't have read/write access to .
On many distributions, you should add yourself into the
"video" group by giving command
        adduser linux video
and then log in again to be able to access the video.
A quick alternative is just to do
        chmod a+rw
WARNING: If you press Enter, I'll try to continue anyway,
but this probably will fail. You SHOULD press Ctrl+C now.
Press Ctrl+C to quit, Enter to continue --->
[linux@localhost qc-usb-messenger-1.6]$ id linux
uid=1000(linux) gid=1000(linux) groupes=1000(linux),82(video)
[linux@localhost qc-usb-messenger-1.6]$

Any idea what's wrong here? How could I make the webcam available to all users by default (that is, make it so that all users are automatically members of 82(video))?

Thanks.

P.S. - I just tried to use RealPlayer and no longer get an image... Might this have something to do with the above installation? Crap!!

P.P.S. - I just noticed that I have an Ekiga Quickcam USB icon on my desktop. A good sign?

maroonbaboon 06-26-2007 02:30 AM

Quote:

Originally Posted by rm_-rf_windows
Any idea what's wrong here?

Well - the kernel module seems to have installed OK, which is a good sign. But for some reason it doesn't like the permissions you set, although 'linux' is in the 'video' group so should be able to access the camera. Try ls -l '/dev/video0' to check the permissions.

Quote:

How could I make the webcam available to all users by default
Sure you want to do this? Make sure you don't forget it's running :) I think the suggested 'chmod a+rw /dev/video0' should do this. All users will not be in the video group, but it won't matter.

Quote:

I just tried to use RealPlayer and no longer get an image... Might this have something to do with the above installation? Crap!!
I don't know how they could be connected. Are you sure you are not trying to run it as root. Typically root does not have access by default to your X11 server.

Quote:

I just noticed that I have an Ekiga Quickcam USB icon on my desktop. A good sign?
Again I'm not familiar with this. I think Ekiga is some kind of webcam app. Have you tried running it? You need some sort of application to test out the cam. Most distros at least have 'xawtv'.

rm_-rf_windows 06-26-2007 02:47 AM

Here's what I get:
Code:

[linux@localhost ~]$ ls -l /dev/video0
lrwxrwxrwx 1 root root 10 jun 26 07:30 /dev/video0 -> v4l/video0
[linux@localhost ~]$

Shall I install anyway?

maroonbaboon 06-26-2007 08:08 AM

Use 'ls -l /dev/v4l/video0' instead. You can worry about permissions when you have the camera working for a single user.

The permissions on the /dev files have nothing to do with the installation. It just looks like the installation process tried to do some testing. The main thing is to make sure the kernel module 'quickcam' is loaded (if that's what it's called). Check the output of the 'lsmod' command to see if it is in the list. If it's not there try 'modprobe quickcam' (as root).

Once the module is loaded you can try it out with an application like xawtv. So long as you have no other video devices installed (like TV tuner cards) just running 'xawtv' at the command line should give you a picture. If you get error messages at that stage you will have a better idea of what needs to be fixed up.

rm_-rf_windows 06-26-2007 11:33 AM

Hmm... This stuff is a bit beyond me... Please bear with me... I need more specific instructions because "modprobe" and even "make" and "make install" are completely new to me.
Code:

Use 'ls -l /dev/v4l/video0' instead.
This is what's in my "dev" directory:
Code:

[linux@localhost dev]$ ls v*
vcs  vcs2  vcs4  vcs6  vcsa    vcsa1  vcsa3  vcsa5  vcsa7
vcs1  vcs3  vcs5  vcs7  vcsa0@  vcsa2  vcsa4  vcsa6

vcc:
0@  1@  2@  3@  4@  5@  6@  7@  a0@  a1@  a2@  a3@  a4@  a5@  a6@  a7@
[linux@localhost dev]$

lsmod (as root) gives me this:
Code:

[root@localhost ~]# lsmod
Module                  Size  Used by
appletalk              32812  2
ipx                    25860  2
p8023                  2368  1 ipx
ipt_IFWLOG              3780  2
ipt_psd                44488  1
ip_set_iptree          7368  2
xt_tcpudp              3776  11
xt_state                2688  7
xt_pkttype              2496  4
iptable_raw            2496  0
xt_CLASSIFY            2464  0
xt_CONNMARK            2912  0
xt_MARK                2976  0
xt_length              2592  0
xt_connmark            2592  0
xt_physdev              3024  0
xt_policy              4320  2
xt_multiport            3904  4
xt_conntrack            2976  0
ipt_ULOG                7204  0
ipt_TTL                2752  0
ipt_ttl                2464  0
ipt_TOS                2688  0
ipt_tos                2240  0
ipt_TCPMSS              4288  0
ipt_set                3008  2
ipt_SAME                2976  0
ipt_REJECT              5184  4
ipt_REDIRECT            2848  0
ipt_recent            10188  0
ipt_owner              2560  0
ipt_NETMAP              2752  0
ipt_MASQUERADE          3936  0
ipt_LOG                7232  10
ipt_iprange            2432  0
ipt_hashlimit          8168  0
ipt_ECN                3424  0
ipt_ecn                2752  0
ipt_DSCP                2688  0
ipt_dscp                2272  0
ipt_CLUSTERIP          7652  0
ipt_ah                  2496  0
ipt_addrtype            2432  0
ip_set_portmap          4896  0
ip_set_macipmap        4836  0
ip_set_ipmap            4896  0
ip_set_iphash          7908  0
ip_set                19196  11 ip_set_iptree,ipt_set,ip_set_portmap,ip_set_macipmap,ip_set_ipmap,ip_set_iphash
ip_nat_irc              2912  0
ip_nat_tftp            2272  0
ip_nat_ftp              3648  0
ip_conntrack_irc        6000  1 ip_nat_irc
ip_conntrack_tftp      4088  1 ip_nat_tftp
ip_conntrack_ftp        6960  1 ip_nat_ftp
iptable_nat            7652  0
ip_nat                15692  8 ipt_SAME,ipt_REDIRECT,ipt_NETMAP,ipt_MASQUERADE,ip_nat_irc,ip_nat_tftp,ip_nat_ftp,iptable_nat
ip_conntrack          48320  13 xt_state,xt_CONNMARK,xt_connmark,xt_conntrack,ipt_MASQUERADE,ip_nat_irc,ip_nat_tftp,ip_nat_ftp,ip_conntrack_irc,ip_conntrack_tftp,ip_conntrack_ftp,iptable_nat,ip_nat
nfnetlink              5912  2 ip_nat,ip_conntrack
radeon                113632  2
drm                    62676  3 radeon
iptable_mangle          3104  1
ipv6                  237120  12
iptable_filter          3232  1
ip_tables              12740  4 iptable_raw,iptable_nat,iptable_mangle,iptable_filter
x_tables              12132  40 ipt_IFWLOG,ipt_psd,xt_tcpudp,xt_state,xt_pkttype,xt_CLASSIFY,xt_CONNMARK,xt_MARK,xt_length,xt_connmark,xt_physdev,xt_policy,xt_multiport,xt_conntrack,ipt_ULOG,ipt_TTL,ipt_ttl,ipt_TOS,ipt_tos,ipt_TCPMSS,ipt_set,ipt_SAME,ipt_REJECT,ipt_REDIRECT,ipt_recent,ipt_owner,ipt_NETMAP,ipt_MASQUERADE,ipt_LOG,ipt_iprange,ipt_hashlimit,ipt_ECN,ipt_ecn,ipt_DSCP,ipt_dscp,ipt_CLUSTERIP,ipt_ah,ipt_addrtype,iptable_nat,ip_tables
snd_usb_audio          74496  1
snd_usb_lib            15072  1 snd_usb_audio
snd_rawmidi            19936  1 snd_usb_lib
snd_hwdep              7556  1 snd_usb_audio
snd_seq_dummy          3620  0
snd_seq_oss            31392  0
snd_seq_midi_event      7072  1 snd_seq_oss
snd_seq                49488  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device          7212  4 snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq
forcedeth              26508  0
snd_pcm_oss            40384  0
snd_mixer_oss          16096  1 snd_pcm_oss
af_packet              17960  2
snd_intel8x0          29372  1
snd_ac97_codec        96868  1 snd_intel8x0
snd_ac97_bus            2848  1 snd_ac97_codec
snd_pcm                70116  4 snd_usb_audio,snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer              19620  2 snd_seq,snd_pcm
snd_page_alloc          8712  2 snd_intel8x0,snd_pcm
snd                    46500  16 snd_usb_audio,snd_rawmidi,snd_hwdep,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore              8096  1 snd
floppy                55172  0
video                  13924  0
thermal                11240  0
processor              21448  1 thermal
fan                    4036  0
container              3968  0
button                  5808  0
battery                8260  0
ac                      4292  0
ide_cd                35776  0
binfmt_misc            9800  1
loop                  15400  0
nls_cp437              6464  1
vfat                  11104  1
fat                    46876  1 vfat
nls_utf8                2624  2
ntfs                  266940  1
supermount            34128  1
dm_mod                49944  0
cpufreq_ondemand        6956  0
cpufreq_conservative    6952  0
cpufreq_powersave      2400  0
cpufreq_nforce2        5456  0
nvidia_agp              7068  1
agpgart                27240  2 drm,nvidia_agp
ehci_hcd              29160  0
ohci_hcd              19012  0
usbcore              113472  5 snd_usb_audio,snd_usb_lib,ehci_hcd,ohci_hcd
evdev                  8864  1
tsdev                  7040  0
ext3                  124936  2
jbd                    51028  1 ext3
[root@localhost ~]#

I then did the modprobe thing (not knowing what the h*ll I was doing, of course (lol)):
Code:

[root@localhost ~]# modprobe quickcam
[root@localhost ~]# lsmod
Module                  Size  Used by
quickcam              71236  0
videodev                8064  1 quickcam
appletalk              32812  2
ipx                    25860  2
p8023                  2368  1 ipx
ipt_IFWLOG              3780  2
... (etc.)

Then...
Code:

[root@localhost ~]# This is xawtv-3.95, running on Linux/i686 (2.6.17-5mdv)
can't open /dev/video0: No such file or directory
v4l-conf had some trouble, trying to continue anyway
v4l2: open /dev/video0: Aucun fichier ou répertoire de ce type
v4l2: open /dev/video0: Aucun fichier ou répertoire de ce type
v4l: open /dev/video0: Aucun fichier ou répertoire de ce type
no video grabber device available

[1]+  Exit 1                  xawtv
[root@localhost ~]#

Quote:

If you get error messages at that stage you will have a better idea of what needs to be fixed up.
What next?

Thanks man!

maroonbaboon 06-26-2007 08:28 PM

Page formatting has gone berserk on this thread for some reason - page is now about 3x screen width, making it very hard to read and enter text. Anybody know who to complain to?

In post #10 you have a link /dev/video0 in your /dev directory, but now it's disappeared. I'm guessing then that your system is using 'udev' to dynamically create and remove these entries. It's a good sign that the 'quickcam' module is loaded. Probably the first thing to try is to unplug the cam from the PC, wait a few seconds and plug it back in. This might trigger 'udev' to recreate /dev/video0 and hopefully put you in business.

Alternatively just rebooting with the camera attached might have the same effect.

gerryggg 04-27-2008 01:12 PM

Kernel Mismatch
 
when trying to compile the quickcam driver which I successfully did under other distros, I get the message

[!] Kernel source version mismatch
This script assumes that the running kernel should be the same as the kernel sources against which the driver will be compiled but they don't seem to be. Kernel source is "2.6.22.18-1mdvcustom" but running kernel is "2.6.22.18.desktop-1mdv."
You may need to do "make bzImage" to correct this error.

The kernel sources I installed were listed as 2.6.22.18-1mdv. I also have no idea what they mean by "make bzImage." Can anyone help me? I had been running Kubuntu 7.10, but when the upgrade to the final 8.04 beta scrambled my installation I decided to take a look at the Mandriva Powerpack 2008 cd I had gotten with a magazine. I like it, but have been having a few teething problems.


All times are GMT -5. The time now is 10:23 AM.