From: Leif D. <lde...@re...> - 2002-02-20 03:43:01
|
On 19 Feb 2002, Sergey V. Udaltsov wrote: > > That's because tunnel tries to use alpha blending _and_ fog, which isn't > > possible on mach64 (we're looking into a workaround though). If you > OK. For a moment, I just will remember this fact. > > > 2. For some reason, X server gets signal 11 after closing any GL > > > program. Is it registered bug? Can I help with debugging (with my > > > XFree.0.log/dmesg)? > > > > Hmmm, I haven't seen that. Post the logs and we can take a look. > OK. With my pleasure. > > Actually, almost all the stuff in this file is from the initialization. > Till the line "Open APM successful". > > Actions: > 1. In vt1, I do /usr/X11R6-DRI/bin/X > 2. In vt2, I do > DISPLAY=:0.0 glxinfo.. > 3. Switch to vt4. The whole system crashes but glxinfo returns some > sensible data. > If I use glxgears instead, it runs till I stop it (by Ctl-C in vt2) and > X terminates with the same signal 11. > > Does it have something to do with vt management? Yes, I think so. There are still locking issues to resolve between the Mesa driver, drm and the DDX driver. Switching vts when an GL app is running will most likely lock the card at this point. You should be able to run glxinfo and glxgears from an xterm without a problem. Does X crash if you run glxgears from an xterm? btw, your Xlog seems to end at the message about virtual resolutions being limited due to ... Is that really the end? (maybe I'm having problems with the charset). -- Leif Delgass http://www.retinalburn.net |