[mythtv-users] FF and REW lockups with PVR-350

[Bennett Leve]

John,

Using:

ii  mythtv         0.18.1-2_km_i5 A personal video recorder application 
(clien
ii  mythtv-backend 0.18.1-2_km_i5 A personal video recorder application 
(serve
ii  mythtv-common  0.18.1-2_km_i5 A personal video recorder application 
(commo
ii  mythtv-databas 0.18.1-2_km_i5 A personal video recorder application 
(datab
ii  mythtv-debug   0.18.1-2_km_i5 Debugging symbols for MythTV
ii  mythtv-doc     0.18.1-2_km_i5 A personal video recorder application 
(docum
ii  mythtv-fronten 0.18.1-2_km_i5 A personal video recorder application 
(clien

-Bennett
John Harvey wrote:

>What version of mythtv are you using?
>
>John
>
>  
>
>>-----Original Message-----
>>From: mythtv-users-bounces at mythtv.org [mailto:mythtv-users-
>>bounces at mythtv.org] On Behalf Of Bennett Leve
>>Sent: 16 September 2005 04:38
>>To: mythtv-users at mythtv.org
>>Subject: [mythtv-users] FF and REW lockups with PVR-350
>>
>>All,
>>
>>I am experiencing the issues described in the list archives:
>>
>>  http://www.gossamer-threads.com/lists/ivtv/devel/19002?nohighlight=1
>>
>>Recently I built a box just to use for MythTV.  It has the following
>>hardware:
>>
>> ABIT IS7-V2 motherboard
>> Hauppauge PVR-350 using the mpeg video out option
>> Pentium IV 3.0 processor
>> 512mb of ram
>>
>>The Myth install is the latest Knoppmyth release and I have been very
>>happy with it except for two things.
>>
>>The freezes when hitting the FF or REW button really fast several times
>>and when I turn on hyper threading it freezes after only a few minutes
>>of displaying video.
>>
>>Reading the above thread it seems the hardware decoder that Hauppauge
>>puts on these cards is rather whimpie.   What I would like to know if
>>anyone has a workaround?  Is there anyway to throttle the throughput or
>>some other hack other than just being sure to not be too aggressive
>>hitting the buttons?  I know there must be lots of setups hitting this
>>problem.
>>
>>I would be interested to know of a motherboard/processor combo that does
>>not have this problem as well.  I have a X86_64 box running Suse, but I
>>use that for work and would rather keep it that way, but if it would be
>>more stable than the new P4 box I may switch them around.
>>
>>Sep 15 22:55:13 mythtvbe kernel: ivtv: 1000 ms time out waiting for
>>firmware
>>Sep 15 22:55:13 mythtvbe kernel: ivtv: Failed api call 0x00000015 with
>>result 0xfffffff0
>>Sep 15 22:55:13 mythtvbe kernel: ivtv: DEC: couldnt read clock
>>Sep 15 22:55:23 mythtvbe kernel: ivtv: 1000 ms time out waiting for
>>firmware
>>Sep 15 22:55:23 mythtvbe kernel: ivtv: Failed api call 0x0000000d with
>>result 0xfffffff0
>>Sep 15 22:55:23 mythtvbe kernel: ivtv: DEC: error pausing
>>Sep 15 22:55:26 mythtvbe kernel: ivtv: No Free Mailbox for cmd
>>0x00000015 after 100 tries!
>>Sep 15 22:55:26 mythtvbe kernel: ivtv: Mailbox[0] 0x00000053 flags
>>0x00000003
>>Sep 15 22:55:26 mythtvbe kernel: ivtv: Mailbox[1] 0x00000053 flags
>>0x00000003
>>Sep 15 22:55:26 mythtvbe kernel: ivtv: Firmware UNRESPONSIVE when trying
>>cmd 0x00000015!!!
>>Sep 15 22:55:26 mythtvbe kernel: ivtv: DEC: couldnt read clock
>>Sep 15 22:55:36 mythtvbe kernel: ivtv: 1000 ms time out waiting for
>>firmware
>>Sep 15 22:55:36 mythtvbe kernel: ivtv: Failed api call 0x0000000d with
>>result 0xfffffff0
>>Sep 15 22:55:36 mythtvbe kernel: ivtv: DEC: error pausing
>>Sep 15 22:55:46 mythtvbe kernel: ivtv: 1000 ms time out waiting for
>>firmware
>>Sep 15 22:55:46 mythtvbe kernel: ivtv: Failed api call 0x00000003 with
>>result 0xfffffff0
>>
>>Thanks for any help.
>>
>>-Bennett
>>_______________________________________________
>>mythtv-users mailing list
>>mythtv-users at mythtv.org
>>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>    
>>
>
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>mythtv-users mailing list
>mythtv-users at mythtv.org
>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>  
>