Date: Thu, 25 Aug 2011 04:21:58 -0500 From: "Conrad J. Sabatier" <conrads@cox.net> To: Polytropon <freebsd@edvax.de> Cc: freebsd-questions@freebsd.org Subject: Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+ Message-ID: <20110825042158.3644b0d6@cox.net> In-Reply-To: <20110825103731.4cddea94.freebsd@edvax.de> References: <20110814032206.49ad7062.freebsd@edvax.de> <20110814025520.GA75595@orange.esperance-linux.co.uk> <20110814052211.02213877.freebsd@edvax.de> <alpine.BSF.2.00.1108132132480.78948@wonkity.com> <20110814054942.5e08fb77.freebsd@edvax.de> <20110816141503.16603a52@serene.no-ip.org> <20110825103731.4cddea94.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 25 Aug 2011 10:37:31 +0200 Polytropon <freebsd@edvax.de> wrote: > On Tue, 16 Aug 2011 14:15:03 -0500, Conrad J. Sabatier wrote: > > > > Yes, the driver performs quite admirably. :-) No more gnashing my > > teeth in envy of others with true hardware-accelerated drivers. > > I'm currently using that driver, and everything seems to > work as intended. The only problem I have is that the > driver has different DPI opinions as the previous ones. > This makes some fonts unreadable. I found that I can > easily change the Gtk+ base font by a ~/.gtkrc-2.0 > with something like ``gtk-font-name="Tahoma 12"'' in > it, but this of course doesn't apply everywhere. Yes, I noticed this, too, as soon as I switched to using this driver. Fonts shrank all over the place. :-) I hadn't considered adjusting the DPI. That sounds like an interesting possibility. > There seems to be a solution to handle DPI settings in > X directly, so I put "DisplaySize 410 305" in the monitor > section of xorg.conf. The monitor is an Eizo FlexScan F980 > 21" CRT with BNC cabling, so no autodetect magic. But some > things still are wrong, maybe I should try ``Option "DPI" > "96 x 96"'' in the device section - I'm not sure which > values should be used, 72 or 75 or 96 or 115... > > Additionally, the gv program has a problem (but it already > had that on _each_ of the three drivers): The keys for > selecting pages are squished. > > This is how they should look like: > > http://t16web.lanl.gov/Kawano/gnuplot/intro/plotcalc7.png > > They are like this: > > +-----+ +-----+ +-----+ +-----+ > |* ===| | ===| | ===| | ===| > | ===| |* ===| | ===| | ===| > |* ===| | ===| |* ===| | ===| > | ===| |* ===| | ===| | ===| > +-----+ +-----+ +-----+ +-----+ > > SHOULD like. Currently, they look like this: > > +-----+ +-----+ +-----+ +-----+ > |#####| |#####| |#####| |#####| > +-----+ +-----+ +-----+ +-----+ > > You can't tell which is which. > > The gv program uses Xaw3d for the display elements. Maybe nVidia > is not compatible with that? Or it's also a "wrong DPI" effect? > Everything else in gv works as intended. Hmm, sorry, I don't know about that. You may find the following link helpful: http://www.retrevo.com/support/Eizo-F980-Monitors-manual/id/1360bh645/t/2/ > On the other hand, mplayer can now change brightness and contrast > again; I have put "vo=gl" in ~/.mplayer/config and it works. :-) Cool, I'll have to try that. > > > I'd like to point out that the nvidia driver comes with > > > nice documentation: /usr/local/share/doc/NVIDIA_GLX-1.0/README > > > contains lots of great stuff. > > > > The html version is even nicer to work with: > > > > file:///usr/local/share/doc/NVIDIA_GLX-1.0/html/index.html > > Thanks for the pointer, yes, that's really informative. During > the near future, I'm interested in getting Twinview + Xinerama > working (as I actually have _two_ 21" CRTs of the same type) > and TV out working. There's almost too much documentation for this driver. So much to look at and tinker with. Great fun it is, though. :-) -- Conrad J. Sabatier conrads@cox.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110825042158.3644b0d6>