Nick Rout wrote:
On Sun, 24 Jul 2005 13:42:29 -0700
Scott Simpson wrote:
Fedora Core 3, Latest ATrpms, 2.6.11-1.27_FC3 kernel, Chris Kennedy rc3k
drivers
I have a machine with two video cards:
video 0 is a PVR-350
video 1 is an AverTV Studio card
/dev/video1 records correctly when I do a "cat /dev/video1 >
/tmp/test.mpg" but video0 doesn't. I just get garbage on the screen when
I play it back with mplayer.
Are you sure you have that round the right way? From the output below
the Aver card looks like a straight bt878 framegrabber with no mpeg
encoder on board. Therefore cat /dev/videoX >/tmp/test.mpeg will NOT
work with the Aver card.
By gum I think you're right. This would explain what I'm seeing.
I therefore think that video1 is probably the PVR-350 and video0 is the
Aver. I am not 100% sure how to check, but there should be a log of
kernel messages which will tell you.
bttv is loading first looking at /var/log/messages.
Also if you look at the output of lsmod it should show the (reverse)
order of the modules loaded, the first one to load should be video0, the
second video1 etc, although you can change this by passing options to
the module (in bttv for the Aver the option is video_nr=X then the video
device will be /dev/videoX)
Output from lsmod:
...
ivtv 820708 1 ivtv_fb
...
bttv 158353 0
So far you look right.
Try using a normal tv watching program like xawtv. It will work with a
framegrabber like the Aver, but will not work with the PVR (as xawtv
does not have an mpeg decoder). Try
xawtv -c /dev/video0 and
xawtv -c /dev/video1
The one that works is the Aver card.
OK. I didn't have xawtv, but I did try "tvtime -d /dev/video0" and
"tvtime -d /dev/video1". /dev/video0 worked, /dev/video1 didn't.
Sounds like I have the order reversed. What confused me was that
/var/log/messages said the Hauppauge card was card #0, but I think is
just the first of *all the Hauppauge cards*, not the first video device
in the system.
Now I have another problem with the message
2005-07-25 19:17:43.324 RemoteFile::Read() failed in
RingBuffer::safe_read().
when I run mythfrontend, but
http://lists.debian.org/debian-amd64/2005/03/msg00940.html seems to
indicate that this is a mutex problem that I'll have to compile from
source to get around. Odd, it complains that it is happening on debian
64bit and I'm running on 32bit AMD processor with Fedora Core 3. But
that's another kettle of fish.
Thanks for your help!
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
