Sorry for the repost, but I too am having these issues. I am using ubuntu, with the 2.6.22-14-386 stock kernel. > It looks like the tuner callback function caused a kernel OOPS for > some reason. I do get an oops. Once more, it seems to lock my machine completely. It locks at the point it starts the nVidia driver I believe, but it could also be locking at X startup. Does not even get to KDM/GDM. I cannot even switch to a different tty. It gets stuck. My only option at that point is to hard reset, load a recovery kernel from the grub menu, login as root, and then do a make rminstall, reboot off the standard kernel and all is well again. Even a startx from the recovery kernel as root reproduces the same issue. > My suggestion: > 1. Delete EVERYTHING related to v4l-dvb that you have in your system > now: first, go into your v4l-dvb directory and do "make rminstall", > then "cd .." and "rm -rf v4l-dvb" > 2. Download the latest v4l-dvb tree from http://linuxtv.org/hg/v4l-dvb > 3. Go into the v4l-dvb directory and "make", then "make install" > 4. Reboot and see what happens. Done many times. I have used the tarballs, I have used direct mercurial access. Happens each time. If there is anything you need from me in the way of output, or testing, or doing something, I am all for helping in any way I can to help resolve the issue. Just tell me what ya need. =) -- "Do not taunt Happy Fun Ball" superhappyfunball@xxxxxxxxx "You fiend! Never have I encountered such corrupt and foul-minded perversity! Have you ever considered a career in the church?" -- Bishop of Bath and Wells _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
