O,  :-((

I thought that my camera was compatible. The cam is in the SPAC5xxLE
list...

        
Which camera are compatible with the Fox please ?

Thank's by advance.


>
> ok,
> 
> your cam is not supported by the driver :-) otherwise after this
line -->
> usb 1-1: new full speed USB device using hc-crisv10 and address 3
> there would be something saying that the spac driver claimed the device
> 
> the spac driver on the fox is s tripped down version. not all cams  
> supported by spac on a i386 are also supported on the fox
> 
> 
> 
> Quoting adeplante <[EMAIL PROTECTED]>:
> 
> >
> >
> > Hello,
> >
> > thank's for your help.
> >
> > The result is :
> >
> >>>>> [EMAIL PROTECTED] /root]717# spcaload
> > Using /lib/modules/2.6.15/kernel/drivers/media/video/videodev.ko
> > Using /lib/modules/2.6.15/kernel/drivers/usb/media/spca5xx/spca5xx.ko
> >
> >>>>>> Part of dmesg : (full after)
> > Linux video capture interface: v1.00
> > usbcore: registered new driver spca5xx
> > drivers/usb/media/spca5xx/spca_core.c: spca5xx driver 00.57.06LE
> > registered
> > usb 1-1: new full speed USB device using hc-crisv10 and address 3
> >
> >>>>>> [EMAIL PROTECTED] /root]717# servfox -d /dev/video0 -s 640x480 -w 7070
> >  servfox version: 1.1.3 date: 11:12:2005 (C) [EMAIL PROTECTED]
> > ERROR opening V4L interface
> >
> >
> >>>>>>>> Full output dmesg :
> >
> > [EMAIL PROTECTED] /root]717# dmesg
> > Linux version 2.6.15 ([EMAIL PROTECTED]) (gcc version 3.2.1 Axis release
> > R63/1.63) #13 PREEMPT Fri Apr 27 14:18:08 CEST 2007
> > Setting up paging and the MMU.
> > On node 0 totalpages: 2048
> >   DMA zone: 2048 pages, LIFO batch:0
> >   DMA32 zone: 0 pages, LIFO batch:0
> >   Normal zone: 0 pages, LIFO batch:0
> >   HighMem zone: 0 pages, LIFO batch:0
> > Linux/CRIS port on ETRAX 100LX (c) 2001 Axis Communications AB
> > Built 1 zonelists
> > Kernel command line: root=/dev/mtdblock3 init=/linuxrc
> > PID hash table entries: 128 (order: 7, 2048 bytes)
> > ds1302: RTC not found.
> > Enabling watchdog...
> > Dentry cache hash table entries: 4096 (order: 1, 16384 bytes)
> > Inode-cache hash table entries: 2048 (order: 0, 8192 bytes)
> > Memory: 13904k/16384k available (1321k kernel code, 2480k reserved,
> > 313k data, 64k init)
> > Calibrating delay loop... 99.53 BogoMIPS (lpj=497664)
> > Mount-cache hash table entries: 1024
> > NET: Registered protocol family 16
> > SCSI subsystem initialized
> > usbcore: registered new driver usbfs
> > usbcore: registered new driver hub
> > JFFS version 1.0, (C) 1999, 2000  Axis Communications AB
> > JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
> > io scheduler noop registered
> > io scheduler cfq registered
> > ETRAX 100LX serial-driver 1.25 $, (c) 2000-2004 Axis Communications AB
> > ttyS0 at 0xb0000060 is a builtin UART with DMA
> > ttyS2 at 0xb0000070 is a builtin UART with DMA
> > ttyS3 at 0xb0000078 is a builtin UART with DMA
> > fast_timer_init()
> > RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> > PPP generic driver version 2.4.2
> > PPP Deflate Compression module registered
> > ETRAX 100LX 10/100MBit ethernet v2.0 (c) 2000-2003 Axis
Communications AB
> > eth0: changed MAC to 00:40:8C:CD:00:00
> > ETRAX 100LX USB Host Controller version 1.00 (c) 2005, 2006 Axis
> > Communications AB
> > usb_devdrv: Etrax 100LX USB Revision 16 v1,2
> > usb_devdrv: Bulk timer interval, start:3 eot:6
> > usb_devdrv: Claimed interface for USB physical port 1
> > usb_devdrv: Claimed interface for USB physical port 2
> > crisv10_irq dbg: ctr_status_irq, controller status: host_mode
> > hc-crisv10 hc-crisv10.0: ETRAX 100LX USB Host Controller
> > hc-crisv10 hc-crisv10.0: reset
> > hc-crisv10 hc-crisv10.0: new USB bus registered, assigned bus number 1
> > hc-crisv10 hc-crisv10.0: start
> > hub 1-0:1.0: USB hub found
> > hub 1-0:1.0: 2 ports detected
> > Initializing USB Mass Storage driver...
> > usbcore: registered new driver usb-storage
> > USB Mass Storage support registered.
> > crisv10_irq dbg: ctr_status_irq, controller status: host_mode started
> > crisv10_irq dbg: ctr_status_irq, controller status: host_mode started
> > running
> > usb 1-2: new full speed USB device using hc-crisv10 and address 2
> > usbcore: registered new driver usbserial
> > drivers/usb/serial/usb-serial.c: USB Serial Driver core
> > drivers/usb/serial/usb-serial.c: USB Serial support registered for
> > FTDI USB Serial Device
> > usbcore: registered new driver ftdi_sio
> > drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters
Driver
> > drivers/usb/serial/usb-serial.c: USB Serial support registered for
pl2303
> > usbcore: registered new driver pl2303
> > drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor
driver
> > cse0: Probing a 0x04000000 bytes large window at 0xe0000000.
> > cse0: Probing for AMD compatible flash...
> > cse0: unknown flash device at 0x0, mfr id 0xc2, dev id 0x22a7
> > cse0: Found no AMD compatible device at location zero
> > cse0: Found 1 x16 devices at 0x0 in 16-bit bank
> > cse0: Found an alias at 0x400000 for the chip at 0x0
> > cse0: Found an alias at 0x800000 for the chip at 0x0
> > cse0: Found an alias at 0xc00000 for the chip at 0x0
> > cse0: Found an alias at 0x1000000 for the chip at 0x0
> > cse0: Found an alias at 0x1400000 for the chip at 0x0
> > cse0: Found an alias at 0x1800000 for the chip at 0x0
> > cse0: Found an alias at 0x1c00000 for the chip at 0x0
> > cse0: Found an alias at 0x2000000 for the chip at 0x0
> > cse0: Found an alias at 0x2400000 for the chip at 0x0
> > cse0: Found an alias at 0x2800000 for the chip at 0x0
> > cse0: Found an alias at 0x2c00000 for the chip at 0x0
> > cse0: Found an alias at 0x3000000 for the chip at 0x0
> > cse0: Found an alias at 0x3400000 for the chip at 0x0
> > cse0: Found an alias at 0x3800000 for the chip at 0x0
> > cse0: Found an alias at 0x3c00000 for the chip at 0x0
> >  Amd/Fujitsu Extended Query Table at 0x0040
> > cse0: Swapping erase regions for broken CFI table.
> > number of CFI chips: 1
> > cfi_cmdset_0002: Disabling erase-suspend-program due to code
brokenness.
> > cse1: Probing a 0x04000000 bytes large window at 0xe4000000.
> > cse1: Probing for AMD compatible flash...
> > cse1: unknown flash device at 0x0, mfr id 0xb930, dev id 0x2c4
> > cse1: Found no AMD compatible device at location zero
> > CFI: Found no cse1 device at location zero
> > cse0: 0x00400000 bytes of flash memory.
> >  Found a valid partition table at 0xf001000a-0xf0010056.
> >   /dev/flash1 at 0x00010000, size 0x00350000
> >   /dev/flash2 at 0x00360000, size 0x000a0000
> >  Adding readonly flash partition for romfs image:
> >   /dev/flash3 at 0x000e3408, size 0x0025e000
> > Creating 4 MTD partitions on "cse0":
> > 0x00000000-0x00010000 : "part0"
> > 0x00010000-0x00360000 : "part1"
> > 0x00360000-0x00400000 : "part2"
> > 0x000e3408-0x00341408 : "romfs"
> > I2C driver v2.2, (c) 1999-2004 Axis Communications AB
> >   ==> Improvements done by Geert Vancompernolle - December 2006
> > I2C Major: 254 / I2C Name: i2cgvc
> > gpio init
> > GPIO port G: in_bits: 0x01FFFF3F out_bits: 0x3200003E val: FDFFFF7C
> > GPIO port G: dir: 00000000 changeable: 01FFFF01
> > ETRAX 100LX GPIO driver v2.5, (c) 2001, 2002, 2003, 2004 Axis
> > Communications AB
> > err: timer0 irq for gpio
> > err: PA irq for gpio
> > ds1302: RTC not found.
> > NET: Registered protocol family 2
> > IP route cache hash table entries: 256 (order: -3, 1024 bytes)
> > TCP established hash table entries: 1024 (order: -1, 4096 bytes)
> > TCP bind hash table entries: 1024 (order: -1, 4096 bytes)
> > TCP: Hash tables configured (established 1024 bind 1024)
> > TCP reno registered
> > ip_conntrack version 2.4 (128 buckets, 1024 max) - 166 bytes per
conntrack
> > ip_tables: (C) 2000-2002 Netfilter core team
> > TCP bic registered
> > NET: Registered protocol family 1
> > NET: Registered protocol family 17
> > VFS: Mounted root (cramfs filesystem) readonly.
> > Freeing unused kernel memory: 64k freed
> > eth0: changed MAC to 00:40:8C:00:00:60
> > Linux video capture interface: v1.00
> > usbcore: registered new driver spca5xx
> > drivers/usb/media/spca5xx/spca_core.c: spca5xx driver 00.57.06LE
> > registered
> > usb 1-1: new full speed USB device using hc-crisv10 and address 3
> >
> >
> >>
> >> after all drivers are loaded, plug in the webcam and look if the
> >> device is found and the driver attaches itself to the device
> >>
> >> basically ...
> >>
> >> 1.) load drivers
> >> 2.) plug in webcam
> >> 3.) dmesg
> >> 4.) paste the output here
> >>
> >> John
> >>
> >> Quoting adeplante <azdep@>:
> >>
> >> > I don't understand, can you tell me more please ?
> >> >>
> >> >> does the driver register itself for the cam ?
> >> >>
> >> >>
> >> >>
> >> >> Quoting adeplante <azdep@>:
> >> >>
> >> >> > Hello,
> >> >> >
> >> >> > i sum up my problem :
> >> >> >
> >> >> > uname :
> >> >> > Linux axis 2.6.15 #13 PREEMPT Fri Apr 27 14:18:08 CEST 2007 cris
> >> > unknown
> >> >> >
> >> >> > spcaload : (a second time)
> >> >> > Using /lib/modules/2.6.15/kernel/drivers/media/video/videodev.ko
> >> >> > insmod: cannot insert
> >> >> >
`/lib/modules/2.6.15/kernel/drivers/media/video/videodev.ko': File
> >> >> > exists (-1): File exists
> >> >> > Using
> > /lib/modules/2.6.15/kernel/drivers/usb/media/spca5xx/spca5xx.ko
> >> >> > insmod: cannot insert
> >> >> >
`/lib/modules/2.6.15/kernel/drivers/usb/media/spca5xx/spca5xx.ko':
> >> > File
> >> >> > exists (-1): File exists
> >> >> >
> >> >> > servfox :
> >> >> >   servfox version: 1.1.3 date: 11:12:2005 (C) mxhaard@
> >> >> > ERROR opening V4L interface
> >> >> >
> >> >> >
> >> >> > dmesg :
> >> >> > Linux video capture interface: v1.00
> >> >> > usbcore: registered new driver spca5xx
> >> >> > drivers/usb/media/spca5xx/spca_core.c: spca5xx driver 00.57.06LE
> >> >> > registered
> >> >> >
> >> >> >
> >> >> > I use sdk 205.
> >> >> >
> >> >> > My cam is Logitech Communicate STX :  product ID -> 0x08d7.
> >> >> > This cam is ok on my pc with Fedora Core 6, kernel 2.6.20.
> >> >> >
> >> >> >
> >> >> > Anybody have an idea to help me ?
> >> >> >
> >> >> > Thank's by advance.
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > [Non-text portions of this message have been removed]
> >> >> >
> >> >> >
> >> >>
> >> >
> >> >
> >> >
> >>
> >
> >
> >
>


Reply via email to