On Wed, 6 Nov 2002, Wheeler, Fred (Research) wrote:
> I was experiencing this same lock up with XFree86 4.2.1, as shipped on the FreeBSD
>4.7-RELEASE CDs.
> I'm also using an Asus A7N266-VM with an Athlon XP1800+. The problem was fixed by
>changing my
> nv_drv.o to the one on Mark's web page (link is below). Thanks much for the fix.
>Here are my simple
> observations, in case they are helpful.
>
> I did in fact have to use -ignoreABI. I notice that Mark's nv_drv.o is about 1.5M
>and the one it
> replaces was about 50k.
That's because it was built with -g so it has full debug info in it.
When I tested the nForce support before 4.2.0 I only had my one early
board to test with. It may be the case (sounds like it from the bug
reports) that 4.2.0 (and 4.2.1 which was a bug fix version of 4.2.0, not
a new CVS release) may not work with newer nForce boards. I'm glad
there's a 4.3.0 release coming up which will have the support that's
in CVS.
Mark.
> After nv_drv.o is replaced, "xf86cfg -textmode" no longer lists all of the
> nVidia cards. I got a hang, and no log, even with -probeonly. I do not believe I'm
>using a kernel
> framebuffer. I did not specifically set one up, and nothing in the FreeBSD install
>process mentioned
> anything about a framebuffer. I have not yet been able to try Mozilla (just
>installed FreeBSD for
> the first time, coming up to speed). I have not seen anything unusual with any
>other X applications.
>
> Thanks,
> Fred Wheeler
>
>
>
> 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
>
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
