On Friday 17 November 2006 21:39, Han Holl wrote:
> On Friday 17 November 2006 19:10, Hans Verkuil wrote:
> > Never mind, it's not my day. Just forget I posted this. You have
> > the correct modules loaded, so just do the test with the different
> > inputs I suggested earlier. Sorry for the confusion.
>
> Ah. I'm glad I'm not going mad after all.
> I copied the drivers into the correct directory and ran:
> #!/bin/bash
> cd  /lib/modules/2.6.18-1.2849.fc6/kernel/drivers/media/video
> for i in 4 5 6 7 8
> do
>   cp ivtv-c$i.ko ivtv.ko
>   rmmod ivtv
>   sleep 2
>   modprobe ivtv
>   sleep 2
>   v4l2-ctl -i 1
>   echo $4
>   mplayer /dev/video0
> done
>
> dmesg showed that 5 times a driver was loaded and removed.
> Each and everytime the image was black and white.
>
> If you have any more suggestions, I'm quite willing to try anything.

Hmm, back to basics I think. Install the standard ivtv-0.8.x 
(http://ivtvdriver.org/viewcvs/ivtv/branches/0.8.tar.gz?view=tar).

1) Load the driver and post the INIT IVTV messages
2) run v4l2-ctl -i 1
3) start a capture and run in another shell v4l2-ctl --log-status. Post 
the output.
4) run (while capture is still in progress) 'ivtvctl -R chip=cx2584x' 
and post the output.

Now go back to ivtv-0.3.2q and:

1) Load the driver and post the INIT IVTV messages
2) Select a working S-Video input (let me know which input you chose)
3) Start a capture and run cx25840ctl -l and post the output.

Well, that should give me all the info I need. I really don't understand 
it.

Oh yes, if you play back on the 2.6.18 system something you captured 
with 0.3.2q, is it still color? Just in case there is some weirdness 
with mplayer :-)

        Hans

_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to