On Thu, Jan 02, 2003 at 10:42:33PM +0100, Michel D?nzer wrote: > On Don, 2003-01-02 at 04:27, [EMAIL PROTECTED] wrote: > > On Wed, Jan 01, 2003 at 04:30:50PM +0100, Michel D?nzer wrote: > > > On Mit, 2003-01-01 at 04:19, [EMAIL PROTECTED] 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. >
Wouldn't the problem be with the radeon driver if Q3A worked properly prior to the merge from the trunk on Nov. 6, 2002, as is the case? Please tell me if I don't know what I'm talking about. -Jonathan ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
