From: Michel <mi...@da...> - 2003-01-02 21:42:41
|
On Don, 2003-01-02 at 04:27, th...@rp... wrote: > On Wed, Jan 01, 2003 at 04:30:50PM +0100, Michel D?nzer wrote: > > On Mit, 2003-01-01 at 04:19, th...@rp... wrote: > > > > > > If I increase the resolution to 1024x768 or push the texture resolution > > > to the max (both of which were simultaneously possible previously), the > > > Xserver quits to the console. > > > > You'd have to provide a server backtrace or at least a log snippet (if > > it contains any meaningful output) for this. > > Below is a backtrace. The problem only occurs with an AGP aperture > of 64 MB (which previously worked). I tried to get a backtrace with > the gdb modified for XFree86 modules, but it produced no meaningful > results; the attached backtrace is from the regular gdb. Lastly, the > Xserver does not crash as I previously mentioned. If Q3A is the only > program running, X exits to the console, but any input that I type is > not displayed. If I run Q3A from WindowMaker, Q3A is killed and my > desktop is left in an odd resolution that doesn't completely fit on my > laptop LCD (this is the point at which I retrieved the following > backtrace. Sounds like Q3A crashes, and the X server exits if it's the only client. You'd have to debug Q3A in that case. > Additionally, the pointer is fixed in the top left-hand corner of the > screen. That's normal if it crashes while it grabs the pointer. You could start it again (or another client which grabs the pointer) and exit cleanly to regain control of the pointer. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |