Re: Again with the nvidia...
It's in there:
(**) NVIDIA(0): Option "NoRenderAccel" "on"
But I also noticed this:
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-GLX
(II) Loading extension NV-CONTROL
Symbol __glXActiveScreens from module
/usr/X11R6/lib/modules/extensions/libdri.a is unresolved!
Symbol __glXActiveScreens from module
/usr/X11R6/lib/modules/extensions/libdri.a is unresolved!
So I commented out the DRI and the GLcore, which were suggestions I found
from a google search. Hopefully this will do it. The unresolved symbols
are from the dri module, because the nvidia driver doesn't supply them,
and GLcore is supplied by the nvidia driver itself.
Thoughts?
On Tue, 19 Aug 2003 15:47:45 +0200
Sebastian Kapfer <sebastian_kapfer@web.de> wrote:
> On Tue, 19 Aug 2003 05:40:09 +0200, Bradley Alexander wrote:
>
> > Option "NoRenderAccel" "on"
> >
> > to the device section of XF86Config-4. I did this and thought I had
> > the problem licked. But alas, I got bitten again.
> >
> > Any other wisdom on how to beat this other than tearing Gnome off of
> > my system?
>
> AFAICT, this XF86 crashes _are_ related to nVidia's RENDER acceleration
> (which is tagged experimental, so it's not a surprise that there are
> bugs in it). Especially GTK2 apps with AA seem to trigger the bug. Are
> you really sure that the driver recognized the option? There should be a
> comment about it in the XF86 log file. Another idea might be to turn off
> anti-aliasing.
--
--Brad
=========================================================================
Bradley M. Alexander |
gTLD SysAdmin, Security Engineer | storm [at] tux.org
========================================================================
Key fingerprints:
DSA 0x54434E65: 37F6 BCA6 621D 920C E02E E3C8 73B2 C019 5443 4E65
RSA 0xC3BCBA91: 3F 0E 26 C1 90 14 AD 0A C8 9C F0 93 75 A0 01 34
=========================================================================
Fetchez la vasche!
Reply to: