I've tried to edit the idmcam.c file from /usr/arc/linux-2.4.22/etc. (not on linux machine right now..), and editing the line that references to id# 800D to 8333 (which is the id # of my stingray model reported by usbview). It does not, however, install the ibmcam module when it boots up. Could someone help me trouble shoot this problem?

After searching google, I found someone else has had this problem before here:

http://www.dragoninc.on.ca/mail-arch...3-01/0237.html

BUT they didn't get it fixed either. Do any of those kernel hackers out their know why changing 0x300d to 0x8333 in ibmcam.c and recompiling doesn't work?

I am having trouble with this Veo Stingray web camera ProdID=8333 as well. I wrote to Veo and they were no help, big surprise there. I have gotten a little farther than you since I was able to get the ibmcam module to load. However, there is still no activity from the camera, even the LED won't light up. I noticed that Rev= 0.01 within the /proc/bus/usb/devices file (see below). The devices supported in ibmcam have different Rev levels.

cat /proc/bus/usb/devices

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 4
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB OHCI Root Hub
S: SerialNumber=e8891000
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1
P: Vendor=0545 ProdID=8333 Rev= 0.01
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=81(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
...

I changed three lines in ibmcam.c then compiled, mv the new ibmcam.o to /lib/modules/2.4.20-20.9/kernel/drivers/usb, depmod -a. After the depmod the modules.usbmap file showed the new settings for ProdID and Rev (actually listed in map as bcdDevice_lo and bcdDevice_hi). When the camera was plugged into one of my usb ports the ibmcam module loaded. Here is the output from a diff on the old module code compared to the new.

diff ibmcam.c ~/ibmcam/ibmcam.c

41c41
< #define VEO_800D_PRODUCT_ID 0x800D /* Veo Stingray, repackaged Model 4 */
---
> #define VEO_800D_PRODUCT_ID 0x8333 /* Veo Stingray, repackaged Model 4 */
3689c3689
< case 0x030A:
---
> case 0x0001:
3909c3909
< { USB_DEVICE_VER(IBMCAM_VENDOR_ID, VEO_800D_PRODUCT_ID, 0x030a, 0x030a) }, /* Model 4 */
---
> { USB_DEVICE_VER(IBMCAM_VENDOR_ID, VEO_800D_PRODUCT_ID, 0x0001, 0x0001) }, /* Model 4 */

Not sure how much this is going to help, but it is a start. I did locate another message on the net from someone who said they were close, but darn if I can find it again. If I do I'll post it and maybe we can get something working.

-----
Bill

I should have mentioned that I tried it for both Model 2 and Model 4 with no success.

-----
Bill

My modules.usbmap file has the ibmcam listed with 8333, but the module still isn't loaded when my camera is plugged in. What associates usb devices to modules in linux, cause it's not working?

I'm not an expert at this, but I'll try to get you at least as far as I am. Does your modules.usbmap file also have the correct Rev level listed next to the ProdID? Start by checking what the Rev level is in your devices file. For example, from my earlier post my devices file has the line:

P: Vendor=0545 ProdID=8333 Rev= 0.01

My modules.usbmap file has the following line after making changes to the ibmcam module, compiling, moving the module, and performing depmod -a.

ibmcam 0x000f 0x0545 0x8333 0x0001 0x0001 0x
00 0x00 0x00 0x00 0x00 0x
00 0x00000000

I needed to adjust ibmcam.c to have the same combination of Vendor, ProdID, and Rev as the webcam in order to get the module to load. The Vendor number was already in the program. I changed the ProdID in the define. The Rev was a little more difficult to locate. Towards the end of the module there is a case statement and a static struct that need to be changed to get the right Rev into the map. As shown in my diff statement these are located at line 3689 and line 3909 of ibmcam.c.

-----
Bill

Try using google.com/linux using the words "veo stingray" for info. This is how I found what I needed to set mine up, but I no longer have it or my notes or I'd help out more. This google site is also a good place to find all kinds of linux info.

Bones, does your Veo Stingray have a ProdID=8333? If it does and your camera is working would you share the diff between my ibmcam.c and your current ibmcam.c? I have found plenty of information using google.com/linux for other ProdID's of this webcam. The best information so far has been at www.linux-usb.com/ibmcam. This appears to be a new strain of Veo Stingray.

I'll see if I can find my notes, I no longer have the stingray but it was like 18 months ago. I don't throw much away so my notes should be here somewhere, if not I can borrow it back long enough to find out over the weekend.

II just found that the
P: Vendor=545 ProdID=800c Rev= 3.0a, sorry

Guess it wasn't all that long ago, just seems like it.

Thanks for taking a look. ProdID 800C and 800D are now part of the ibmcam module. I believe they became part of the kernel in version 2.4.19. Some of the articles I found suggested changing the ProdID, but there appears to be more to it than that.

You got that right!