- From: Irene Vatton <Irene.Vatton@inrialpes.fr>
- Date: Thu, 5 Jul 2007 10:06:37 +0200
- To: Keith Hopper <asgard@inspire.net.nz>
- Cc: www-amaya@w3.org
On Sunday 01 July 2007 19:06, Keith Hopper wrote: > In article <50416.195.224.154.166.1183104312.squirrel@mail.imalip.net>, > > Regis Boudin <regis@boudin.name> wrote: > > Hi Keith, > > > > I guess is you're being hit by the "other" GDK error. So far we've > > identified two conditions that trigger it : > > -When running AIGLX and the Composite extension, which can be worked > > around with what Irene suggested. > > -When using non-DRI GLX rendering with Mesa. DRI works fine, X11 software > > rendering is ok but slow, software GLX crashes. The problems is actually > > somewhere between wxWidgets, Mesa and Xserver, according to an X/Mesa > > developper. You can have a look at [1] for more informations. > > > > My guess would be that you run with DRI disabled... > > No! Why not using an Amaya version compiled with Mesa. It's slower, but it doesn't crash. The problems is actually in the OpenGL support by Nvidia. > > [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357439 > > I have looked at the above and run amaya under gdb with the --sync > argument. The XWindow problem arises in glXMakeCurrentReadSGI after > stepping 62 instructions - when the X11 major code 143 (the SGI-GLX opcode) > is in the rsi register. One more step and the Xwindow error is reported. > The last instruction executed loaded rdi with the hex value 0x315e780 - if > that is any help to you! > > As to configuration of the machine - > > Mother Board - ASUS M2N-NX > CPU - AMD Athlon x2-64 > Nvidia MCP61 revision 162 nForce 430/GeForce6100 chip set. > Linux SuSE version 10.2 (kernel 2.6.18.8-0.3) > X11 version 7.1.99.902 > > The file /etc/X11/xorg.conf has the following modules loaded - dbe, > type1, freetype, extmod, glx, v41. There is also the following section > which might be of relevance - > > Section "DRI" > Group "video" > Mode 0660 > End Section > > which seems to indicate that DRI is running. I note, however, that the mode > is different to the one given by one of the correspondents in the reference > (which was 0666). > > Note that it would probably be unwise to edit this xorg.conf file as > it is automatically generated by the SuSE SAX2 application during initial > installation. > > I don't know whether the following is relevant, but since my original > report, when using VNC from another machine there is a warning (not error) > from xgamma in respect of X11 Opcode 134 (XFree86-VidModeExtension) - > immediately after logging in at the other machine. > > At the moment that is all I can think of which might help in tracing > the problem. Please ask if you think there is anything else I can help > with. > > Keith Irène. ----- Irène Vatton INRIA Rhône-Alpes INRIA ZIRST e-mail: Irene.Vatton@inria.fr 655 avenue de l'Europe Tel.: +33 4 76 61 53 61 Montbonnot Fax: +33 4 76 61 52 07 38334 Saint Ismier Cedex - France
Received on Thursday, 5 July 2007 08:09:48 UTC