[mythtv-users] PVR-350 TV Output
timwilhoit at cox-internet.com
Tue Jan 6 22:48:20 EST 2004
Wouldn't it be great if someone could add the 350 tv out to Jarods
From: mythtv-users-bounces at mythtv.org
[mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Torsten Schenkel
Sent: Monday, January 05, 2004 7:47 AM
To: Discussion about mythtv
Subject: Re: [mythtv-users] PVR-350 TV Output
Am Mo, den 05.01.2004 schrieb Bill Mackintosh um 03:56:
> I have built a system around RedHat's Fedora Core 1 and followed
> Jarod's page at http://wilsonet.com/mythtv/ and have succeeded in
> getting MythTV to work on the PC. Everytime I follow the directions
> for enabling the ivtv-fb output at
> http://ivtv.writeme.ch/tiki-print.php?page=TvOutHowto I can compile
> the driver (I have used ivtv-031125A-0.12, ivtv-031125A and
> decoder-alpha-311003A versions) and install it, and can get MythTV to
> output the video to the television, however the mythfrontend process
> (or possibly the entire OS) locks up after approximately 15-20
> seconds, faster if I change channels (using external receiver
> w/appropriate channel changing perl script specified in MythTV setup)
> or rewind/FF the video
Known bug (stop-dec). Get ivtv latest CVS and try that. Lot's happened
in the meantime. 0.1.6 is (nearly) rock solid here. Actual is 0.1.8(pre)
> When compiling the ivtv-fb driver, I get a couple of "#warning Using
> temporary hack for missing I2C driver-ID for" error messages, one for
> saa7114 and one for tveeprom.c. I have also seen the onscreen error
> message in the terminal window while viewing the logs"warning: cannot
> reserve video memory at 0x15000000 (not absolutely sure of the error #
> there, sorry!)
Normal messages, the ivtv chips don't have i2c codes yet.
> Since MythTV works just fine w/out the ivtv-fb driver installed, I'm
> fairly confident this is the culprit. W/out the TV output, the system
> is virtually useless to me since I don't want to watch TV on a CRT.
It's a problem with decoding (done without ivtv-fb) and OSD (using the
framebuffer) interaction (irq collisions). Should be mostly solved in
recent issues of ivtv.
> I am a new linux user, basically got into it just to get MythTV setup
> and running. I am very versed in DOS/Windows however, and am willing
> to learn Linux! :)
You have gotten further than most :-) What you are seeing are known
issues with the driver version you use.
> I've tried to include as much system info as I can below. Any help
> you can offer in getting this working will be most appreciated!
> PC Specs
> BioStar M7VKG motherboard
> Athlon 1.2GHz CPU
> 2 x 256MB PC 133MHz memory modules (for a total of 512MB onboard)
> Visiontek GEForce 3 TI200 AGP graphics card
> Hauppauge PVR-350
> Sohoware 10/100 NIC
> Soundblaster Live Value! soundcard (As a side question, is this
> actually necessary since the PVR-350 is doing all the
> encoding/decoding of the audio?)
Not for TV/MPEG2 display with myth, but for Music, DVD and so on.
> Maxtor 20GB ATA100 master drive (root, boot and swap partitions)
> Western Digital 80GB ATA133 slave drive (mounted as /d_hdd and will be
> used as video storage drive if I can get MythTV working correctly with
> the video output)
> 16X DVD-ROM drive
> 3 1/2" floppy drive
> Software Specs
> Running RedHat Fedora Core 1 running custom kernel
> 2.4.22-1.2135.nptl_27 as specified on Jarod's site.
> Using OSS as sound module, not ALSA
> Have updated via apt-get to ALL latest modules/drivers. No other
> updates available.
> Running mythtv .13 + all add on modules
Nothing special here. You should be fine with newer drivers. The
driver's in the flux, so expect thing to break every now and then. Keep
a working copy around.
Walkthrough: MythTV on Epia with PVR350 using Debian:
More information about the mythtv-users