chris gareau

what happined to the gspca-spca561 driver,
it is still there bit my webcam doesn't work
I think some kernal upgrade may be to blame, don't ans me witch one, I
don't know there have been a fiew scence the thing stoped working
dmesg | tail reveals nothing usfull, looks like everything is fine.
[root@diehardp4 ~]# dmesg | tail
usb 3-1: USB disconnect, address 10
gspca: disconnect complete
usb 3-1: new full speed USB device using uhci_hcd and address 11
usb 3-1: configuration #1 chosen from 1 choice
gspca: probing 046d:092e
gspca: probe ok
usb 3-1: New USB device found, idVendor=046d, idProduct=092e
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: Camera
usb 3-1: Manufacturer:
[root@diehardp4 ~]#

any ideas????????????

wes newell

v4l not loaded? Webcam crapped out (my old QC did not long ago).

--
Want the ultimate in free OTA SD/HDTV Recorder? http://mythtv.org
My Tivo Experience http://wesnewell.no-ip.com/tivo.htm
Tivo HD/S3 compared http://wesnewell.no-ip.com/mythtivo.htm
AMD cpu help http://wesnewell.no-ip.com/cpu.php

doug laidlaw

Yes, I have been through all this.

In the kernel used by 2008.1, gspca support was a module, and you would
install a dkms package, which took care of it all.

With kernel 2.6.27, gspca support is part of the kernel itself. I am still
getting my 2009.0 system up and running, but if you install the
kernel-source, there is a .txt file listing the supported webcams.

My problem is that I have the E 2500, which came out apparently at the
beginning of 2007, or even earlier, but not soon enough to be supported in
the 2.6.27 build. I think that I corresponded with you on
comp.os.linux.hardware about that. The option listed at actionshrimp.com
is no longer available under the new setup. The 046d:092e doesn't seem to
be listed in my copy of the patch for the old setup. If your webcam isn't
in the list, you would need to write a module for it. I suspect that one
could rename an existing module, but I am not a programmer.

If your webcam is in the list, with 2.6.27 the module you need to modprobe
is no longer gspca or gspcav, it has _main at the end. Add that ending to
your old modprobe command. Each webcam supposedly has its own secondary
module, but as I recall, the only one you need to modprobe is
gspca(v)_main. You can set your parameters either directly in
modules.conf, or with MCC's setup facility.

I am sorry if I am a bit vague about the details, but I haven't got kernel
source installed at the moment. On the other list, you seemed to be able
to understand what I am saying.

HTH,

Doug.
--
Efficiency is intelligent laziness.
-- Arnold H. Glasgow.

web dreamer

Doug Laidlaw a écrit ce vendredi 9 janvier 2009 11:32 dans
<inlj36-65p.ln1@dougshost.douglaidlaw.net> :


If you ar SHURE a module works for your hardware but that the hardware
doesn't get that module associated to it even when you load it, just backup
this file:
/usr/share/ldetect-lst/pcitable.d/90default.lst.gz
(from ldetect-lst package)
extract it, edit it, append what follows:
0x046d 0x092e "gspca"
Then recompact it to a gz file and add:
gspca
to /etc/modprobe.preload
I'm not shure it works, but it's worth the try. And if you copied the
original /usr/share/ldetect-lst/pcitable.d/90default.lst.gz you can revert
back.

--
Web Dreamer

doug laidlaw

Thanks for that tip. I have had mine working with the old dkms, patched as
I mentioned. It uses the gspca driver, but isn't listed. Your fix may be
just what I need.

Doug.
--
Husbands are like the fire on the hearth - likely to go out if left
unattended.
- W.G.P.

doug laidlaw

Chris, if you want to try that, just add '0x' in front of each number you
quoted. It hasn't worked for me yet. Instead of gspca you will need
gspcav_main (the name of the new module) in modprobe.preload, and it
doesn't exist on my system yet. I installed kernel-devel, and I have a
directory /usr/src/linux-2.6.27.7-desktop-1mnb/drivers/media/video/gspca/
but the module isn't built yet. actionshrimp.com said to build it with
"make menuconfig." I will leave it at that for now.

Doug.
--
Judge a man by his questions rather than by his answers.
- Voltaire

doug laidlaw

The module is gspca_main, not gspcav_main. There don't seem to be any USB
devices in that file. I assume that the directory is pcitable.d because it
deals with PCI devices. Looking at
http://lists.debian.org/debian-devel.../msg00622.html

there should be a separate usbtable.d for USB devices. And there is one,
with its own 90default.lst.gz. This is looking more promising...

(I like reporting in stages.) I added my Webcam to 90default.lst.gz and
to usbtable.gz in the directory above, which seems identical. Still
not detected.

Doug.
--
If a thing is worth doing, it is worth doing badly.
- G.K. Chesterton.

web dreamer

Doug Laidlaw a écrit ce dimanche 11 janvier 2009 04:42 dans
<qd6o36-9lv.ln1@dougshost.douglaidlaw.net> :


Did you also add the module's name in /etc/modprobe.preload?
/etc/modprobe.preload is to automatically load the module at boot, and
usbtable.d is to associate the module to the device's ID.
The "usbtable.d" is to make the "naming" more "logical" for a usb device
indeed, but it can work also with pcitable.d, if it does there and not with
usbtable.d, it could be a BUG.

--
Web Dreamer

doug laidlaw

Yes, I did. There are apparently two modules involved: gspca_main, and one
for the device.

I notice that Kernel 2.6.28 has a few changes to the gspca area. It may be
worthwhile checking them out. I used up most of my monthly bandwidth
allocation trying to get a stable system, and I could only download the
latest source and compile it. My immediate problem is out of the way: I
won't be needing my Webcam under Skype and Linux. I had it working with
Skype under Mandriva 2008.1 by patching its kernel, but the current one is
entirely different.

As regards 90default.lst.gz and , no other entry has a module listed
opposite, only the Hex identifier and a description, so that was what I
did.

Doug.
--
The complete truth is not the prerogative of the human judge.
- Judge Meir Shamgar.

web dreamer

Doug Laidlaw a écrit ce mercredi 14 janvier 2009 09:12 dans
<8cj046-k56.ln1@dougshost.douglaidlaw.net> :

You need to put the hex description and the "module" (not the description).
If you check this file, some modules are defined in it.

--
Web Dreamer