Hi Greg,

I'm new at this as well (I'm working on getting a 350 up and running) but
will offer a few things I have found out relating to your questions:


>-----Original Message-----
>From: [EMAIL PROTECTED]
[mailto:ivtv-devel->[EMAIL PROTECTED] On Behalf Of Gregory Stark
>Sent: Sunday, 7 August 2005 3:40 AM
>To: [email protected]
>Subject: [ivtv-devel] TV-Out is all black
>
>
>I have a PVR-350 and video capture is working fine with ivtv-0.2.0-rc3k
>drivers.
>
>However, when I use the dd command to test tv-out like the install docs
>describe I don't see any change on the composite output, just a black
>screen.
>
>I have a few questions:
>
>a) How do I know which /dev/video devices the drivers grabbed for input and
>   output? I found the input device by trial and error, it's /dev/video2.
>But
>   /dev/video18 gives an i/o error. /dev/video16 seems to work but no
output
>   is generated. It's possible it's the wrong device but it would be nice
if
>   the driver just told me which device it allocated when it loaded like
other
>   video grabber drivers.
>


I think you'll find ivtvctl will tell you what you want to now.

Try it with a -h to get a list of the flags you want.

-N      Will list the available outputs.
-L      Will give you the actual output being used.

There are flags for inputs etc as well.

If you are using Fedora or similar I believe you can do the following type
of thing in /etc/modprobe.conf:

options ivtv set-input=0


Likewise for outputs etc.


>b) How do I do the test_image feature that the docs describe. When I try it
>I
>   get "saa7127: Unknown parameter `test_image'" I assume these docs are
>just
>   out of date and refer to 0.1 drivers? But ivtvctl doesn't seem to have
an
>   equivalent option.
>


Are you using Jarod's most excellent guide? I get the test pattern without
difficulty using his instructions.


http://wilsonet.com/mythtv/fcmyth.php?SID&expandables=closed&ivtv=open&pvr35
0out=open



>c) Where do I find ivtv-fb? All the docs seem to imply it should be built
>and
>   installed along with the rest of the drivers. But there's no such file
in
>   the drivers directory. Where is it supposed to come from?
>

Jarod also describes the steps necessary to load up the framebuffer. Either
at boot in modprobe.conf or later with manual modprobes.


>
>-- 
>greg
>





-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to