- From: Regis Boudin <regis@boudin.name>
- Date: Thu, 5 Jul 2007 14:47:29 +0100 (BST)
- To: Irene.Vatton@inrialpes.fr
- Cc: "Keith Hopper" <asgard@inspire.net.nz>, www-amaya@w3.org
On Thu, July 5, 2007 09:06, Irene Vatton wrote: >> > 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. No. The usual problem is somewhere between Xserver and Mesa in GLX mode. It works fine when in full X11 software rendering mode, which is different. AFAIK, there is no problem with the nvidia driver. On the contrary, switching to the proprietary driver with its OpenGL library usually fixes the crashing issue and is much faster. >> > [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! The usual crash happens in glxMakeCurrent IIRC. >> 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). Just for reference, which driver do you use ? nv, nvidia, vesa ? vesa and nvidia don't use DRI at all, so you would be back in indirect rendering mode which triggers the error. If you run "nv", that's probably a new bug, then :( >> 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. I'm afraid Direct Rendering doesn't sound very compatible with VNC, but I might be wrong... >> 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. Thanks for the info. I'm interested in knowing if there is another bug indirectly affecting Amaya... Regis
Received on Thursday, 5 July 2007 13:48:10 UTC