On Wednesday 08 November 2006 01:03, Chris Mohler wrote: > Anne, > > Have you had a look at this page yet: > http://linuxtv.org/v4lwiki/index.php/Zoran_devices_%28zr36057%2C_zr36067%29 > > Esp: > http://linuxtv.org/v4lwiki/index.php/Zoran_devices_%28zr36057%2C_zr36067%29 >#module_loading_options > I wasn't aware of that page, but I don't think there is much new there. Most of it is from the mjpegtools webpage, which I do know. I did check out the links on the page, though. Basically, this all worked in FC4, so either I've forogtten something vital that I had to do when I installed FC4 or something has changed dramatically. At this stage I don't know which it is. > I'd be curious to see the output from your modprobe command. > I think these are the only relevant lines. video 21061 0 compat_ioctl32 5569 1 zr36067 i2c_algo_bit 12873 1 zr36067 i2c_core 25537 8 w83627hf,eeprom,i2c_isa,i2c_ec,adv7175,saa7110,i2c_viapro,i2c_algo_bit videocodec 12245 2 zr36060,zr36067 videodev 27073 1 zr36067 v4l1_compat 16453 1 videodev v4l2_common 26305 1 videodev I don't know about the first line, but as you can see the zr36067 module is loading correctly. What may be relevant from the url you gave me is "v4l_bufsize=$number where $number is the size of one buffer v4l_nbufs=$number where $number is the number of the buffers reserved for the card Ideally, (v4l_nbufs * v4l_bufsize) = (totalmem - append= in your lilo.conf) What I'm using (DC10+) : modprobe zr36067 v4l_bufsize=512 card=2 v4l_nbufs=32 " but I'm not sure how I am intended to use this. I tried a modprobe with those settings, which didn't seem to make any difference, but that was after the 36067 had been loaded at bootup. > You might also try installing mjpegtools - I see it in the freshrpms > repo. I'm not familiar with that program. > I am. It is a set of command-line tools, and what I use for the video processing. I installed the livna package. In the past I have only used mjpegtools built from the mjpegtools source. That could be relevant. Just as a reminder, these are the messages I see in a console (with comments interspersed): [anne@david ~]$ xawtv This is xawtv-3.95, running on Linux/i686 (2.6.18-1.2798.fc6) WARNING: v4l-conf is compiled without DGA support. ##Is this the problem? WARNING: couldn't find framebuffer base address, try manual configuration ("v4l-conf -a <addr>") ## I never had to beforex ioctl: VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=678;fmt.win.w.top=27;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x8cf2784;fmt.win.clipcount=0;fmt.win.bitmap=(nil)): Invalid argument #How do I find out/fix what is invalid? no way to get: 384x288 32 bit TrueColor (LE: bgr-) ##I don't know if it used 32-bit before [anne@david ~]$ [anne@david ~]$ [anne@david ~]$ tvtime Running tvtime 1.0.1. Reading configuration from /etc/tvtime/tvtime.xml Reading configuration from /home/anne/.tvtime/tvtime.xml videoinput: Can't get tuner info: Invalid argument Your capture card driver: zoran [DC10plus[0]/PCI:0000:00:0b.0/2309] does not support studio-quality colour images required by tvtime. This is a hardware limitation of some cards including many low-quality webcams. Please select a different video device to use with the command line option --device. ## Is this the 32-bit problem again? Message from the card was: Invalid argument Thank you for using tvtime." Anne
Attachment:
pgpyAm2GJNdDW.pgp
Description: PGP signature
