On Tue, 2008-03-11 at 11:07 +0000, ivor@xxxxxxxx wrote: > Not sure if this helps or adds that much to the discussion... (I think > this was concluded before) > But I finally switched back to kernel 2.6.22.19 on March 5th (with > current v4l-dvb code) and haven't had any problems with the Nova-t 500 > since. Running mythtv with EIT scanning enabled. > > Looking in the kernel log I see a single mt2060 read failed message on > March 6th and 9th and a single mt2060 write failed on March 8th. These > events didn't cause any problems or cause the tuner or mythtv to fail > though. ah. So this begs the question: What changed between 2.6.22 and 2.6.24? huh... funny, heh? So, if 2.6.24 is finger pointed, I'm interested in a solution, as I have a planned upgrade to it in about a month's time. Nico _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb