[ATrpms-users] Fwd: Live TV in MythTV not working (ivtv.. big suprise there!)

[Keith C]

I accidentally replied to Matt instead of the list :

On Jul 12, 2006, at 2:05 AM, Matt wrote:

> No matter what I try I can't get live TV working in MythTV.  When I
> initially boot up I can get in and use it just fine, sound works, I  
> can
> change channels etc...  If I exit out and come back in though it hangs
> with a black screen every time.  If have to kill mythfrontend from a
> remote machine otherwise the system will eventually lock up
> completely.   That leaves me with a completely dead zombie backend
> process I can't do anything about until I reboot.  Until then  
> mythtv is
> completely dead.
>
> Here's my setup:
>
> FC5 (2.6.17-1.2145_FC5 x86_64, previous .17 kernel had the same  
> problem,
> .16 no channel changing)
> ivtv 0.7 + kernel module
> nvidia 8762 (have a 6200 card)
>
> These are the errors I get in mythfrontend (backend log shows card not
> responding error only):
>
>
> =====================  Intital start of live TV... works but errors as
> you can see ========================================
> 2006-07-12 02:16:05.611 TV: Attempting to change from None to  
> WatchingLiveTV
> 2006-07-12 02:16:05.629 Using protocol version 26
> 2006-07-12 02:16:05.754
> RingBuf(/storage/mythtv/recorded/1044_20060712021605.mpg): Invalid  
> file
> (fd 17) when opening '/storage/mytht
> v/recorded/1044_20060712021605.mpg'. 12 retries remaining.
> 2006-07-12 02:16:06.260
> RingBuf(/storage/mythtv/recorded/1044_20060712021605.mpg): Invalid  
> file
> (fd 17) when opening '/storage/mytht
> v/recorded/1044_20060712021605.mpg'. 11 retries remaining.
> 2006-07-12 02:16:06.833 Disable DPMS
> 2006-07-12 02:16:09.016
> RingBuf(/storage/mythtv/recorded/1044_20060712021605.mpg): Waited 2
> seconds for data to become available...
> 2006-07-12 02:16:09.016 Checking to see if there's a new livetv  
> program
> to switch to..
> 2006-07-12 02:16:11.064
> RingBuf(/storage/mythtv/recorded/1044_20060712021605.mpg): Waited 4
> seconds for data to become available...
> 2006-07-12 02:16:11.064 Checking to see if there's a new livetv  
> program
> to switch to..
> 2006-07-12 02:16:15.160
> RingBuf(/storage/mythtv/recorded/1044_20060712021605.mpg): Waited 8
> seconds for data to become available...
> 2006-07-12 02:16:15.160 Checking to see if there's a new livetv  
> program
> to switch to..
> 2006-07-12 02:16:23.095
> RingBuf(/storage/mythtv/recorded/1044_20060712021605.mpg) Error:  
> Waited
> 16 seconds for data, aborting.
> 0: start_time: -9223372036854.775 duration: -9223372036854.775
> stream: start_time: -9223372036854.775 duration: -9223372036854.775
> bitrate=0 kb/s
> 2006-07-12 02:16:23.106 AFD: Opened codec 0xb4afa0, id(MPEG2VIDEO)
> type(Video)
> 2006-07-12 02:16:23.106 NVP: Disabling Audio, params(-1,-1,-1)
> 2006-07-12 02:16:23.106 NVP: Disabling Audio, params(0,-1,-1)
> X Error: BadMatch (invalid parameter attributes) 8
>   Major opcode:  141
>   Minor opcode:  14
>   Resource id:  0x1ca
> =====================  Re-entry into live TV
> =========================================
> 2006-07-12 02:16:23.196 VideoOutputXv Error: Couldn't get the color  
> key
> color,
>                         probably due to a driver bug or limitation.
>                         You might not get any video, but we'll try  
> anyway.
> 2006-07-12 02:16:23.759 TV: Changing from None to WatchingLiveTV
> 2006-07-12 02:16:24.617 Using realtime priority.
> 2006-07-12 02:16:24.720 Video timing method: USleep with busy wait
> 2006-07-12 02:16:26.119 NVP: Prebuffer wait timed out 10 times.   
> <=====
> this repeats indefinitely
>
> I'm not sure where to even start with this....  Nvidia problem?  My  
> same
> xorg.conf worked fine FC4 i386.

No, it looks ok to me.

>   IVTV problem?  That driver is crap,
> something breaks EVERY SINGLE time I do a yum update.. seriously.. why
> is the quality control that bad?

IVTV only breaks because of the continuous progress that is being  
made towards getting it included in the kernel.  Thats said, mine has  
never broken from a yum upgrade.  Ever.  I do pay attention to the  
ivtv lists, though, which I don't think the average user should have  
to do.

>   MythTV problem?
>
> The invalid file and data wait errors I don't get at all.  The volume
> it's on is on a totally different set of disks then anything else and
> aren't getting touched at all.  They are local disks that run ~90MB/s
> too.  (Hardware RAID 5).. same setup as user FC4 where everything  
> worked.

Invalid file doesn't necessarily mean a problem with the file  
system.  It just means that Myth backend told the frontend that it  
was going to start recording into so and so file and frontend went  
looking for it.  If the backend failed to record, the file wouldn't  
get created.  So, I think we need to see 2 things : your dmesg log  
from when ivtv gets loaded (to make sure that the backend has a valid  
ivtv to use) and the backend logs from an attempt at watching LiveTV  
(usually in /var/tmp/mythbackend.log).

>
> The "Couldn't get coloc key color" error, what's that one about?

That just means you have an nvidia card newer than the 5000 series  
that doesn't support the color key thing.  That warning has been  
removed from mythtv in svn head.

Keith C