I was able to get this going - I now have audio and video displayed on  
the PVR-350 TV Out.  I found the FC6 instructions I'm following at  
http://wilsonet.com/mythtv/printer-friendly.php?SID&expandables=closed&ivtv=open&pvr350out=open
to be pretty accurate in getting MythTV working and recommend it.   
Though some of the lower level tests identified in these instructions  
still don't work (ivtvfbctl in particular), it doesn't seem to effect  
MythTV's ability to display live TV or record.

For the archives, step 7 in the list below claims there is no need to  
convert BusID derived by scanpci from hex to decimal.  This is  
incorrect - I tried it both ways and only decimal representation works.


Quoting Ricardo Lugo <[EMAIL PROTECTED]>:

> Mr. Moodyjunk,
>
> I think your problems stem from the howto you have selected to
> follow. The order is way out of whack for setting up a PVR-350's TV-
> out and all this stuff about mplayer is really not relevant when the
> machine is being used for X-windows SOLELY via PVR-350 TV-out. Not to
> mention it has outdated information about the ivtv driver
> (specifically, that ivtv now supports mplayer -vo xv).
>
> But let's get back to the basics. I'm going to write an outline on
> what you need to do to get the ivtv driver and X via the TV-out up
> and running, then hopefully you can pick up and go back through the
> rest of the howto and get myth installed.
>
> 0) Install Xorg and KDE
>       - it usually comes installed by default on fedora
>
> 1) Install the ivtv firmware: (looks like you already did this)
>       - http://ivtvdriver.org/index.php/Firmware
>
> 2) Install the ivtv kernel modules:  (looks like you already did this)
>       - your favorite binary repository (RPMs, portage, apt-get, or whatever)
>       - or http://ivtvdriver.org/index.php/Download and compile it
> yourself (but note that you need your kernel's source, too)
>       - don't forget to `depmod -a`
>
> 3) Install the ivtv Xdriver (very important!)
>       - http://ivtvdriver.org/index.php/Download
>       - copy it to /usr/X11R6/lib/modules/drivers/
>
> 4) modprobe ivtv
>
> 5) modprobe ivtv-fb
>
> 6) Check `dmesg` make sure there are no errors with the loading of
> those modules, and `lsmod` to make sure they actually were loaded.
>
> 7) Set up your /etc/X11/xorg.conf
>       - remove the section "device" that corresponds to your normal video
> card (if such a section exists)
>       - put in a section "device" for your 350, per link below:
>       - http://www.mythtv.org/wiki/index.php/XV_on_PVR-350
>       - change the line "Option" "ivtv" "/dev/fb2" to whatever your fb
> device is
>       - you can see all your fb choices by executing `ls /dev/fb*`
>       - change the line "BusID "PCI:..." to your appropriate id
>       - you can find out your BusID by executing  `X -scanpci` (no need to
> convert hex/dec!)
>
> 8) execute `startx`or change init levels or whatever it is that
> fedora needs to restart X (`killall -HUP X`)?
>       - you should get an X-windows console on your tv-out
>       - if not, you can figure out what went wrong by looking at /var/log/
> Xorg.0.log
>       - be prepared to mess around with your xorg.conf file a lot, this
> might take a few tries to get right.
>
> 9) Continue with the rest of the howto, pick it up at "Running X on
> the PVR-350's TV-out - The final touch is to rebuild..."
>       - and make sure you do the whole section 14 - automatic startup.
>
> Hope that helps.
> - Rick
>
> On Dec 20, 2006, at 4:02 PM, [EMAIL PROTECTED] wrote:
>
>>
>> Sdkovacs wrote:
>>>> DVR:~ # mplayer -vo x11 /tmp/test_capture.mpg
>>>> MPlayer 1.0rc1-4.1.1 (C) 2000-2006 MPlayer Team
>>>> CPU: AMD Athlon(tm) Processor (Family: 6, Model: 6, Stepping: 2)
>>>> CPUflags:  MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 0
>>>> Compiled with runtime CPU detection.
>>>> Can't open joystick device /dev/input/js0: No such file or directory
>>>> Can't init input joystick
>>>> mplayer: could not connect to socket
>>>> mplayer: No such file or directory
>>>> Failed to open LIRC support. You will not be able to use your
>>>> remote control.
>>>>
>>>> Playing /tmp/test_capture.mpg.
>>>> MPEG-PS file format detected.
>>>> VIDEO:  MPEG2  720x480  (aspect 2)  29.970 fps  8000.0 kbps
>>>> (1000.0 kbyte/s)
>>>> Xlib:  extension "XFree86-VidModeExtension" missing on display ":
>>>> 20.0".
>>>>
>>>
>>> Mr. Moodyjunk,
>>>
>>> Are you running the mplayer command on the system console or are you
>>> SSHed into your mythbox? Mplayer is not outputting to screen :0 which
>>> leads me to believe you are not on the console.
>>>
>>> I noticed this from your post:
>>>
>>> Xlib:  extension "XFree86-VidModeExtension" missing on display ":
>>> 20.0".
>>>
>>>
>>> So try the mplayer command from the physical display.
>>>
>>
>>
>> I am actually VNC'd (SSH under the covers I believe) into the box
>> without any keyboard/mouse/display physically attached.  I connected a
>> physical display and indeed get video on the display via mplayer,
>> proving that the video is being captured correctly.  Thanks for that
>> pointer.
>>
>> However, my goal is to view recordings via MythTV on a television
>> using PVR-350 TV Out.  I get sound, but not picture on the TV when
>> issuing:
>>      ivtvfbctl /dev/fb1 --globalalpha=off --localalpha=on
>>                (fails with "IVTVFB_IOCTL_GET_STATE failed" as above)
>>      dd if=/dev/video0 of=/dev/video16 bs=64k
>> I suspect the problem is the ivtvfbctl failure, but the ivtvfbctl help
>> doesn't describe what the globalalpha and localalpha parms are trying
>> to do, nor what the IVTVFB_IOCTL_GET_STATE failure means.
>>
>> Also, the instructions I'm following say to issue
>> /usr/lib/ivtv/ptune-ui.pl, but that file is not found.  I don't know
>> if the two problems are related.
>>
>>
>>
>> _______________________________________________
>> ivtv-users mailing list
>> [email protected]
>> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>




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

Reply via email to