On Sun, Jan 4, 2009 at 2:40 PM, Sander Sweers <[email protected]>wrote:
> On Sun, Jan 4, 2009 at 12:31, Paul van Gerven > <[email protected]> wrote: > >> > 3) That leaves the improper shutdown, which is certainly an issue with > >> > the > >> > ivtvfb module. Any ideas to debug this? > >> > >> Can you try to unload the ivtvfb module via "modprobe -r ivtvfb" and > >> check: > >> if this produces anything in the logs? > >> does it also lock the machine up, immediately or again at shutdown? > > > > This just results in a message that the module is still in use. Shouldn't > I > > stop the framebuffer first? (If so: how?) > > Yes, any program using the framebuffer should be stopped. > I took me quite long to get around to it (holidays are over), but I created a xorg.conf that doesn't start a framebuffer at all. Strangely, when I issue the modprobe command, it still says it is in use. Perhaps that's the fatal error when I try to shutdown. > > >> If you have closed source modules loaded could you disable them and see > >> if it still locks up? > > > > I have Nvidia drivers, but as I mentioned they are loaded on a separate > > X-server. Is it still worthwhile to try this? > > Maybe, the nvidia driver is a black box and there is no way to tell > what is going on. You can switch to the nv driver when testing. In > xorg.conf in de device section change nvidia to nv. > Done. The xorg.conf I mentioned used nv. > > >> It there any backtrace or error message just before it locks in the > kernel > >> log? > > > > Nope :( > > Maybe there is one after unloading the ivtvfb module. > I still cannot see anything interesting in /var/log/messages. > > Greets > Sander > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users >
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
