Date: Wed, 31 Dec 2014 01:45:16 +0100 From: Mark Martinec <Mark.Martinec+freebsd@ijs.si> To: freebsd-x11@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Removal of XAA acceleration in X.org, and older NVIDIA GeForce Message-ID: <dcf98997670b2c5ae9faf60e7d740522@mailbox.ijs.si> In-Reply-To: <de16f3c800cd58709888906db31b1495@mail.mikej.com> References: <9f15ce6462062541cbaf3919ec420315@mailbox.ijs.si> <20141222201853.08bfcc64@kalimero.tijl.coosemans.org> <60b1d359da424d31e6594bda091c63f3@mailbox.ijs.si> <dada65de7b3e54d0e6a7ef9bbbbb51ce@mailbox.ijs.si> <de16f3c800cd58709888906db31b1495@mail.mikej.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 2014-12-23 10:20, Mark Martinec wrote: >>> Tijl Coosemans wrote: >>>> This card is still supported by x11/nvidia-driver-304 >> >> Mark Martinec wrote: >>> Good suggestion! It does seem to draw screen and scroll >>> much faster than NV (although it seems to stall from time >>> to time (like unresponsive mouse) on a busy host). >>> Will need to test more thoroughly tomorrow when poudriere >>> builds will be over. Thanks! >> >> Actually it did not turn out well. Although nvidia-driver-304 with >> a GeForce 7300 GT does not suffer from slow scrolls and slow rendering >> of web pages, it frequently stalls (like every minute) and nothing >> happens for a dozen of seconds: mouse cannot move a cursor, a cursor >> may even temporarily disappear, typing on an xterm or konsole window >> is unresponsive. It appears as if a host is terribly busy, even though >> it is not (the yesterday's poudriere build was over, and I even >> rebooted the host, with nvidia driver loaded by a boot loader >> this time). >> >> After a dozen of seconds or so, things get back at being responsive >> again, until the next lockup. Occasionally a window may become >> scrambled, but rectifies itself after a while. After trying to >> work in this situation for a while, eventually screen turned black, >> with a host totally locked up - not even responding to ssh or ping >> or ctrl alt F1, or a soft ACPI power off button, so had to be >> forcibly rebooted. >> >> So in the end I had to revert back to the NV driver, which is >> now slow, but at least is stable and consistent. I guess we need >> to start looking for a new graphics board, quite unfortunate. >> >> Mark Michael Jung wrote: > FWIW on i386 current r275874 I do no have these lockup issues > with nvidia GeForce Go 7300 > > I did find that though loading the nvidia kernel module in > /boot/loader.conf was not enough, I had to create a small > xorg.conf simply containing > > Section "Device" > Identifier "Device0" > Driver "nvidia" > VendorName "NVIDIA Corporation" > EndSection > > or GLX instead of NV-GLX would try to be loaded Sure, I did that. (actually, nvidia-xconfig did that for me) > I also have both devd and hald running. Same here. So after a couple of days of suffering I gave up and ordered a new GeForce GT 730, arrived today. I was surprised that the nv driver reported that it is not supported. Switching to nvidia 340 driver now it works perfectly and is fast. So an eight year old GeForce 7300 GT or 7600 GS is too old to be supported by nv driver (and nvidia 304 driver was unstable with 7300, although it works with 7600 on another host on a lower resolution screen), yet a year old GT 730 is too young to be supported by nv. Luckily it works very well with nvidia-driver(-340). I wonder if 7300 GT + nvidia-driver-304 stuttering / holdups and instability can be due to a higher resolution of a monitor attached to that host, or (judging by the symptoms) may it be due to fighting over free memory with ZFS ARC under FreeBSD 10.1, which still seems unresolved: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187594 Bug 187594 - [zfs] [patch] ZFS ARC behavior problem and fix Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dcf98997670b2c5ae9faf60e7d740522>