Bastien Raich wrote: >hello all. >I recently bought a Creative Webcam Plus from my japanese vendor. I >checked the model and webpages, and saw that it is supported by the >ov511 driver. > >I recompiled a 2.4.3 kernel (I'm running RH7.1) with ov511-1.39 version. > >FIRST PROBLEM: after rebooting and loading the ov511 module, the >installation instructions say \ >"2.Make sure that USB is working: Check that /proc/bus/usb/devices >exists and contains data" >in my case, it actually does not exist. > You must have "Preliminary USB device filesystem" enabled in the kernel config, under the "USB support" section.
>however, I can see that my camera is recognized and the driver loaded, >as /dev/video and /dev/video0 exist (as well as video1, video2 and >video3). also, dmesg commande shows that it found the USB camera >(creative webcam 3) and successfully loaded the module. > Unless you are using devfs (which dynamically generates these files), they will always exist. They are created during the OS installation. The files in /dev are just special files that reference devices, regardless of whether the devices or drivers are actually present. The best way to tell whether the driver is working is to look at /var/log/messages . You should see something like: Jul 3 21:10:20 hal9000 kernel: hub.c: USB new device connect on bus1/2/4, assigned device number 28 Jul 3 21:10:20 hal9000 kernel: ov511.c: USB OV511+ camera found Jul 3 21:10:20 hal9000 kernel: ov511.c: camera: Creative Labs WebCam 3 Jul 3 21:10:20 hal9000 kernel: ov511.c: Sensor is an OV7620 >what to do with this ? > >SECOND PROBLEM: I can't have neither web3cam nor xawtv (webcam app) >working. >in the first case, when I'm compiling the app, it simply says that it >"can't see /dev/video" and make exits. I checked and have chmod >correctly to 666. > That is very strange. I can compile it without my camera being connected. If I remember correctly, /dev/video in RH 7.1 is a directory, not a symlink to /dev/video0.You will have to specify /dev/video0 manually: For w3cam, try "./configure --with-device=/dev/video0" For Xawtv, try "xawtv -c /dev/video0" >in the second case, it does simply not take any picture. I'm trying to >do as simple as possible (once = 1, configured for "local", not ftp, >etc...) I don't know what to set for "source", it says "composite1", or >"TV", but I don't know what this correspond to. I get 2 error messages: >- the first gives a list of parameters all set to 0, as well as the >depth, and says it's invalid. >- the second says the source is not good (composite1...) > Perhaps this is becuase of the /dev/video thing. If it still does this with /dev/video0, let me know. > >I'm lost. I'd just like to get something working, or find the simplest >v4l app to grag at least ONE picture !!.. > I agree that these things are confusing. I will update my installation instructions to be more clear on them. The authors of video programs should probably discontinue the practice of defaulting to /dev/video as well. Using a symlink for device selection doesn't make much sense anyway, IMHO. -- Mark McClelland [EMAIL PROTECTED] _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: http://lists.sourceforge.net/lists/listinfo/linux-usb-users
