2008/1/23, Janne Grunau <[EMAIL PROTECTED]>: > > On Tuesday 22 January 2008 12:41:47 Eduard Huguet wrote: > > 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, > > either that or a not yet found bug in mythtv. Most of them are either > reception (or dvb driver dependent) I don't see them with my DVB-C > cards but occasionally on DVB-T. > > > and usually causes MySQL table corruption > > that must be fixed using "myisamchk". > > That's very odd. I've never seen or heard something like that. Please > post more details (mythtv and mysql version, ...) the the mythtv > developer mailing list. > > Janne >
Thanks. I'll try to do so as soon as I get again these errors. It seems to be running fine currently. In addition, I've added an automatic "myisamchk -f /var/lib/mysql/mythconverg/*.MYI" command to my daily MythTV maintenance script (whichs performs backup, optimization, etc...). That should fix any database corruption that might have occurred. Anyway, my specs are the following: - Barebone Asus Pundit P1-AH2 (Athlon64 3800+, 1 GB Ram) - Gentoo x86_64 - Hauppauge Nova-T 500 - HG drivers + lastest 4 patches published - MythTV 0.20.2_p14972 (lastest stable in Portage) - MySQL 5.0.44-r2 (lastest stable in Portage) Best regards, Eduard
_______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
