On 6 Oct 2002, Mikkel Lauritsen wrote: > On Thu, 2002-10-03 at 22:35, Mark Vojkovich wrote: > > > I don't recall having any problems with 4.2.0 on nForce. I'm > > not sure that RedHat's "4.2.0" is really the same as a stock > > XFree86 4.2.0. There have be cases in the past where they have > > modified theirs. Try an official XFree86 4.2.0. > > I just did, and unfortunately the behavior is the exact same. > > Just to display my potential ignorance, what I did was to replace > nv_drv.o from the RedHat package with that from the binary distribution > at ftp.xfree86.org. I still get a hard lockup, and it seems as if the > log files that I am able to obtain reveal nothing at all. I guess they > are truncated at a more or less random point in time when the machine > hangs.
Copying the module should probably be fine. > > So... is there any way that I might try to look deeper into this, > preferably without having to rebuild X from scratch? > Do you get a full /var/log/XFree86.0.log if you do "XFree86 -probeonly" I put an nv_drv.o compiled from CVS on my web page at: http://www.xfree86.org/~mvojkovi/nv_drv.o Since it's newer than your server, you may need to add -ignoreABI to your server command line. (ie. "startx -- -ignoreABI"). Are you running some kernel framebuffer device like rivafb? It's possible that rivafb is not compatible with the "nv" driver on nForce. I never use something like rivafb. Mark. _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
