A wild guess (bash me on the head if I'm wrong), but when you switched kernel, did you do 'make distclean' in your v4l-dvb directory? Unless you do, the code will keep compiling (and installing) for the previous kernel, and your new kernel will only use the stock drivers. That would explain why you're seeing disconnects again. I made that mistake once... // J On Mon, 2008-03-24 at 10:02 +0000, Nicolas Will wrote: > On Mon, 2008-03-24 at 09:47 +0000, Ivor Hewitt wrote: > > > > Nicolas Will wrote: > > > Guys, > > > > > > I have upgraded my system to the new Ubuntu (8.04 Hardy), using > > 2.6.24, > > > 64-bit. > > > > > Just thought I'd add, in case anyone was wondering, that I'm still > > not > > having any problems with vanilla 2.6.22.19 and current v4l-dvb tree. > > MythTV multirec with eit scanning enabled. > > One or two I2C read failed a day in the kernel log, and an occasional > > I2C write failed. > > That was exactly my situation before upgrading my system, which brought > the new kernel version. > > Now, with 2.6.24, the disconnects are back with a vengeance, just as it > was nearly a year ago. > > I hope that the logs provided will help shed a light on this. > > If not, I'm ready to turn debug on on all I can, even if it means > generating gigs of logs. > > Nico > > > _______________________________________________ > linux-dvb mailing list > linux-dvb@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
