On Fri, Feb 28, 2003 at 01:29:28AM -0500, Branden Robinson wrote: > If you're handy with Debian packaging, you could roll a custom XFree86 > 4.2.1-6 package with above patches removed, and see if that changes > anything. If not, it's an upstream problem.
Haven't tried this yet. > Note that the switch to the GCC 3.2-based toolchain has had somewhat > negative consequences on the Mesa 3D acceleration modules; for instance, > the Radeon accelerator is completely inoperative. This, too, is an > upstream problem. So another experiment might be to compile XFree86 > 4.2.1-6 with gcc-2.95 and see if that makes the problem go away. Yup good guess, more data follows: Starting X with just an xterm running, the gcc-2.95 build seems perfectly normal. However, if I start an xterm with the gcc-3.2 build, the xterm background isn't cleared at all - the only place anything is written to the screen is the shell prompt. I've seen this bug with an earlier build of X, which I think I reported at the time: <Phil goes and reads bug no 178261> Ah ha. OK more data. If I install the gcc-3.2 build of the Xserver, then turning setting PciRetry on results in the screen corruption as described in bug No 178261. Using the gcc-2.95 build, I can set PciRetry on with no problems. If PciRetry is off, then the gcc-3.2 build is fine, no problems running glxinfo and so on. So there must be something in the PCI code which is breaking under gcc-3.2! I'll leave PciRetry off for the moment. cheers, Phil -- http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
