2.4.10-ac11 is very fine; gcc-3.0.1 is broken

2001-10-20
2002-10-01
  • Hello everybody again!

    I wrote yesterday into this forum because I couldn't get the qce or dexxa driver to work (Segmentation fault). Now I know that this is was due to using gcc 3.0.1 (which I installed because the mplayer configuration script asked me kindly four (!) times to do so, because 2.96 is oh-so-buggy).

    While trying to compile another kernel (because I've been told 2.4.10 is broken), I had to "upgrade" to gcc 2.96 again.
    When the Dexxa driver worked out of the box, I got suspicious and did some testing, that I would like to share with you:

    First of all: gcc 3.0.1 is broken. Avoid.

    Kernel 2.4.10-ac11 with ext3-patch is working fine with both drivers! (I don't know about a plain 2.4.10 kernel and I'm not going to check it out.)

    The only strange thing is, that gqcam keeps writing "ioctl (VIDIOCSWIN): Invalid argument" to my xterm, but I works fine. Anyway, I guess that's not your business, is it?

    Kernel 2.4.12-ac3 is just working with Jonas' dexxa-driver. All programs are working fine (appart from VIDIOCSWIN-errors with gqcam).

    The qce driver from the CVS with the new hdcs.c from the website crashes the system totally and instantly. (Hey, what did you do? I never had a total system crash in the last 2 years!)

    The qce driver from the CVS with the new hdcs.c AND a patch from Peter is "just" not working. Here's a dmesg output:

    ----------------------------------------------
    usb.c: registered new driver quickcam
    USB testing Class ff SubClass ff
    USB Quickcam camera found using: $Id: quickcam.c,v 1.85 2001/09/18 17:38:33 wildfox Exp $
    quickcam: probe of HDCS1000 sensor = 00 0c id: 08
    quickcam: probe of BP100 sensor = 00 00 id: 64
    quickcam: probe of VV6410 sensor = 19 00 id: 19
    quickcam: VV6410 sensor detected
    load_vv6410_mod
    vv6410_init
    vv6410_init ok
    vv6410_set_gains
    vv6410_set_shutter
    vv6410_set_size
    vv6410_set_window 0 0 352 288
    vv6410_start
    quickcam: frame size is the old one? (180)
    ----------------------------------------------

    Okay, that's all for today!
    Happy debugging! ;-)

    cu
    Ruwen

     
    • ... it's 961179-0700

       
    • I have here 2 webcam and Linux Kernel 2.4.4 SuSE.
      and tried all of your drivers withoyt success.

      1. Camera Logitech QiuckCam Express with HDCS1020, gives USB product 0870

      This Cameras HDSC is not detected because its i2c[0] is 10 not 8 and the usb devid does not match. I could fix that in the quickcam module code, but testing the camera leads to an Seg.Fault.

      The Camera is detected by the mod_dexxa and attached to /dev/vide0. The testquickcam does report its parameters without Seg.Fault but hangs if you read a frame, sometimes hanging the whole system. mmap reading gives just 0s.

      2. THe 2nd camera is a DEXXA with usb product id 0840 is is detected by none of the drivers. I could not find aout the Sensor, since I has no name on it and does not exactly match the pictures on the net. It seems to be of the HDSC kind, because it as 11pin on each of the 4 sides of the die. The STV0600-1  is clearly visible at the other side of the board..

      How can I get a driver that works at least with one of my cameras or otherwise find information on how to fix the code myself?

      Christian (ckotz1@swarthmore.edu)

       
    • Rakesh Agrawal
      Rakesh Agrawal
      2001-11-14

      I've also tried to get my new QuickCam Express working. The USB hardware is of the UHCI variety (VIA VT82C686B southbridge/SuperIO). Relevant entry from /proc/bus/usb/devices:

      T:  Bus=02 Lev=01 Prnt=01 Port=00 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=046d ProdID=0870 Rev= 1.00
      S:  Product=Camera
      C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 90mA
      I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=dexxacam
      E:  Ad=81(I) Atr=01(Isoc) MxPS=   0 Ivl=  1ms
      E:  Ad=82(I) Atr=03(Int.) MxPS=   1 Ivl= 16ms
      I:  If#= 0 Alt= 1 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=dexxacam
      E:  Ad=81(I) Atr=01(Isoc) MxPS=1023 Ivl=  1ms
      E:  Ad=82(I) Atr=03(Int.) MxPS=   1 Ivl= 16ms

      Relevant entries from dmesg:

      usb.c: registered new driver dexxacam
      dexxa.c: Dexxa webcam found (rev. 0x0100)
      usbvideo.c: dexxacam on /dev/video0: canvas=180x148 videosize=180x148
      usbvideo.c: Packet Statistics: Total=96. Empty=0. Usage=100%
      usbvideo.c: Transfer Statistics: Transferred=0 B Usage=0%
      usbvideo.c: Packet Statistics: Total=22944. Empty=0. Usage=100%
      usbvideo.c: Transfer Statistics: Transferred=0 B Usage=0%
      usbvideo.c: Packet Statistics: Total=96. Empty=0. Usage=100%
      usbvideo.c: Transfer Statistics: Transferred=0 B Usage=0%
      usbvideo.c: Packet Statistics: Total=96. Empty=0. Usage=100%
      usbvideo.c: Transfer Statistics: Transferred=0 B Usage=0%
      usbvideo.c: Packet Statistics: Total=6016. Empty=0. Usage=100%
      usbvideo.c: Transfer Statistics: Transferred=0 B Usage=0%
      usbvideo.c: Packet Statistics: Total=96. Empty=0. Usage=100%
      usbvideo.c: Transfer Statistics: Transferred=0 B Usage=0%
      usbvideo.c: Packet Statistics: Total=96. Empty=0. Usage=100%
      usbvideo.c: Transfer Statistics: Transferred=0 B Usage=0%
      usbvideo.c: Packet Statistics: Total=9632. Empty=0. Usage=100%
      usbvideo.c: Transfer Statistics: Transferred=0 B Usage=0%

      This is what xawtv gives me:
      This is xawtv-3.64, running on Linux/i686 (2.4.12)
      sh: v4l-conf: command not found
      v4l-conf had some trouble, trying to continue anyway
      ioctl: VIDIOCMCAPTURE(0,fmt=7,size=8x4): Invalid argument
      ioctl: VIDIOCMCAPTURE(0,fmt=15,size=8x4): Invalid argument
      ioctl: VIDIOCMCAPTURE(0,fmt=5,size=8x4): Invalid argument
      v4l: timeout (got SIGALRM), hardware/driver problems?
      ioctl: VIDIOCSYNC(0): Interrupted system call
      ioctl: VIDIOCMCAPTURE(0,fmt=1,size=8x4): Invalid argument
      ioctl: VIDIOCMCAPTURE(0,fmt=13,size=8x4): Invalid argument
      no way to get: 384x288 32 bit TrueColor (LE: bgr-)
      no way to get: 384x288 32 bit TrueColor (LE: bgr-)

      I get no picture at all.

       
      • Rakesh Agrawal
        Rakesh Agrawal
        2001-11-14

        v4l-conf was not in my PATH; remedying this didn't give me a picture, however.

        Here is the remedied xawtv output:

        This is xawtv-3.64, running on Linux/i686 (2.4.12)
        /dev/video0 [v4l]: no overlay support
        v4l-conf had some trouble, trying to continue anyway
        ioctl: VIDIOCMCAPTURE(0,fmt=7,size=8x4): Invalid argument
        ioctl: VIDIOCMCAPTURE(0,fmt=15,size=8x4): Invalid argument
        ioctl: VIDIOCMCAPTURE(0,fmt=5,size=8x4): Invalid argument
        v4l: timeout (got SIGALRM), hardware/driver problems?
        ioctl: VIDIOCSYNC(0): Interrupted system call
        ioctl: VIDIOCMCAPTURE(0,fmt=1,size=8x4): Invalid argument
        ioctl: VIDIOCMCAPTURE(0,fmt=13,size=8x4): Invalid argument
        no way to get: 384x288 32 bit TrueColor (LE: bgr-)
        no way to get: 384x288 32 bit TrueColor (LE: bgr-)

         
        • Rakesh Agrawal
          Rakesh Agrawal
          2001-12-10

          Well, the 2.4.16 kernel and the current CVS qce-ga driver works. However, the overlay that XawTV displays has an odd pattern in the bottom sixth of the image, where part of the image is displayed with a magenta and green pattern. (It's hard to describe, and trying a screengrab does not capture the overlay. Stills captured by XawTV are correct.)

          Also, is it possible to increase the frame rate of capture?

          Thanks a lot for your efforts!

           
          • Incidentally, running XFree86 using a framebuffer console X server with vesafb does not show this issue. Only using the 2D accelerator's 'native' driver (ATi Radeon LE; radeon.o) causes the problem I mentioned. So it seems that the problem has more to do with an immature display driver than the qce driver.

             
            • Rakesh Agrawal
              Rakesh Agrawal
              2002-01-02

              That was me, of course, forgetting to log in.

               
    • If you solve it please tell me! I get the same errors as you. my webcam id:  861050-1010.

      Marcus (marwil-0@student.luth.se)

       
      • Rakesh Agrawal
        Rakesh Agrawal
        2001-12-10

        Just follow the instructions on the qce-ga site about obtaining the CVS version of the driver, and build it with 'make'. Then run quickcam.sh provided as part of the source. Next, run xawtv, and it ought to give you a low-framerate picture.

         
    • Hi, I got SuSE 7.3 - Kernel 2.4.16 and finaly got my
      dexxa-quickcam to work! but only with xawtv!!!!
      After 2 times starting xawtv it is notlonger pssible to access the /dev/video1 (tv-card is 0)

      Only after reconnect the cam to the usbport it will be available again?! Any clues...?

       
    • Hi, i would like to know if there is any documentation on this driver, i'm a newbie on this stuff and i need to grab images from the camera in raw format for a project i'm carrying on.

      Thanks in advance,

      /Manuel <manuelmeATieeeDOTcom>