[mythtv-users] Can anyone confirm that Ticket 2664 made it into 0.20.1?

nospam312 nospam312 at gmail.com
Tue May 29 15:13:40 UTC 2007


> Please post exactly which capture card you are using (dmesg output
> might be useful) as there are known issues with some cards - the
> Hauppauge Nova-T 500 for example.

Have spent the last few days doing some testing with the trunk version
(revision 13500/13529) but it is still crashing.

When the crash occurs the only common item in the log near where it
failed is a line "PESPacket: Failed CRC check 0x0 != 0xffffffff for
StreamID = 0x0" note this is always with a 0x0 and 0xffffffff and not
more realistic values.

Could this be a case that has not been caught by the fix?

If this does not shed any light on the problem I would like to create
a segfault report to try to help further - can anyone point me to a
URL with what I need to do to help?

It still only appears to affect one multiplex so I do not think it is
hardware related - it is like Mythtv does not like the way one
multiplex is transmitting.

My cards are LifeView FlyDVB-T
(http://www.lifeview.com.tw/html/products/internal_tv/flydvbt.htm)
DVB: registering new adapter (saa7134[0]).
DVB: registering frontend 0 (Philips TDA10046H DVB-T)...

Any help greatly appreciated.


More information about the mythtv-users mailing list