<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2604" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>
<DIV><FONT face=Arial size=2>Paul,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I just (about two months ago) purchased an AMD64
system, 3500+ 90nm 939pin. I'm using it with a MSI K8N Neo2 Platinum
board. I first wanted to do as you are planning, run a 64-bit linux.
I purchased a pcHDTV card to use with the box. When I got all of it up and
running using a Debian port for AMD64, I found that I couldn't use
MythTV... I followed all the instructions and wasn't able to get it to work
reliably. I made a few posts to pcHDTV forum, myth-users, and
mythtvtalk.com but no one responded (and still haven't). Worried that
I wouldn't be able to get this project off the ground I reinstalled and used the
plain-jane 32-bit version of Debian and I have it working
beautifully.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>BTW: I am using DVB drivers.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Streaming an HD signal over the air and displaying
it takes anywhere from 60-85% cpu usage so don't plan on doing any HD
picture-in-picture with your AIR2PC cards. If you're just dumping it to
disk it's less than 10% cpu. I think I'm going to get one more
pcHDTV card so I can record a given channel and watch/record another one
simultaneously. Anywho, the problems I am having now are much less
annoying then the AMD64 issue of having the frontend lock up most of the time
just trying to watch a recording or going to watch live tv.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>My biggest issue with myth now is that
every once in a while, changing channels results in a garbled screen, while the
backend throws out messages like this:</FONT></DIV>
<DIV><!--StartFragment -->2005-03-10 20:47:00.157 DVB#0 WARNING - Transport
Stream Continuity Error. PID = 49 <BR>2005-03-10 20:47:00.157 DVB#0 WARNING -
Transport Stream Continuity Error. PID = 49 <BR>2005-03-10 20:47:00.157 DVB#0
WARNING - Transport Stream Continuity Error. PID = 49 <BR>2005-03-10
20:47:00.157 DVB#0 WARNING - Transport Stream Continuity Error. PID = 49
<BR>2005-03-10 20:47:00.157 DVB#0 WARNING - Transport Stream Continuity Error.
PID = 49 <BR>2005-03-10 20:47:00.157 DVB#0 WARNING - Transport Stream Continuity
Error. PID = 49 <BR><FONT face=Arial size=2></FONT></DIV>
<DIV><FONT face=Arial size=2>the frontend complains about this:</FONT></DIV>
<DIV><!--StartFragment -->[mpeg2video @ 0xb7869050]slice mismatch
<BR>[mpeg2video @ 0xb7869050]ac-tex damaged at 10 30 <BR>[mpeg2video @
0xb7869050]invalid mb type in P Frame at 7 33 <BR>[mpeg2video @ 0xb7869050]slice
mismatch <BR>[mpeg2video @ 0xb7869050]invalid cbp at 43 38 <BR>[mpeg2video @
0xb7869050]ac-tex damaged at 17 43 <BR>[mpeg2video @ 0xb7869050]mb incr damaged
<BR>[mpeg2video @ 0xb7869050]mb incr damaged <BR><FONT face=Arial
size=2></FONT></DIV>
<DIV><FONT face=Arial size=2>This locks up my DVB card until mythbackend
stops using it. I was originally killing both the frontend and
backend and restarting them both until I found a switch in the
setup to have mythbackend release the card when not in use by a
frontend. This makes it so that whenever it gets screwed up, I can just
exit live tv and reenter and it'll work again. It's a work-around but I'd
still like to fix the issue.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Well, if you decide to go AMD64 and use an AMD64
port of linux, good luck! If anyone has Debain AMD64 port working
with a pcHDTV card and Myth, I'd love to hear about your success.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Later,</FONT></DIV>
<DIV><FONT face=Arial size=2>-Greg</FONT></DIV></FONT></DIV></BODY></HTML>