Mmmh, disregard for now this report. I've just discovered that the errors were in the log since some days ago, so possibly they have no relationship with this patch.
Sorry for any inconvenience caused. Anyway, I'm going to let it some hours running and scanning with and without the patch to see if there is any problem with this patch and EIT. Best regards, Eduard 2008/1/22, Eduard Huguet <[EMAIL PROTECTED]>: > > Hi, > I've just applied the patch and compiled the drivers. I haven't tested > actual tuning, since I'm not in front of my computer now, but this is awaken > and idle so MythTV is currently simply scanning EIT data. So well, the > following messages has started appearing on my mythbackend.log: > > 2008-01-22 12:37:50.742 Error: offset>181, pes length & current can not be > queried > 2008-01-22 12:37:50.744 EITHelper: Added 2 events > 2008-01-22 12:37: 51.217 EITHelper: Added 7 events > 2008-01-22 12:37:51.339 330 secs left to system shutdown! > 2008-01-22 12:37:51.706 EITHelper: Added 3 events > 2008-01-22 12:37:52.164 EITHelper: Added 4 events > 2008-01-22 12:37:52.593 EITHelper: Added 2 events > 2008-01-22 12:37:53.011 EITHelper: Added 1 events > 2008-01-22 12:37:53.428 EITHelper: Added 1 events > 2008-01-22 12:37:55.208 Error: offset>181, pes length & current can not be > queried > 2008-01-22 12:37:56.982 Error: offset>181, pes length & current can not be > queried > 2008-01-22 12:38:01.411 320 secs left to system shutdown! > 2008-01-22 12:38:11.484 310 secs left to system shutdown! > 2008-01-22 12:38: 15.448 EITHelper: Added 1 events > 2008-01-22 12:38:21.553 300 secs left to system shutdown! > 2008-01-22 12:38:26.326 Error: offset>181, pes length & current can not be > queried > 2008-01-22 12:38:31.626 290 secs left to system shutdown! > 2008-01-22 12:38:41.698 280 secs left to system shutdown! > 2008-01-22 12:38:51.767 270 secs left to system shutdown! > 2008-01-22 12:38:54.451 Error: offset>181, pes length & current can not be > queried > > > The error about "offset>181 etc..." is usually due to the card receiving > corrupt data, and usually causes MySQL table corruption that must be fixed > using "myisamchk". I'm pretty sure this wasn't appearing these past days, > and today we are in a very good weather condition so I don't think it's > related a bad signal reception. > > I'm going to unapply the patch and test again after repairing the > database. > > Best regards, > Eduard > > > > > >
_______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
