[Dri-devel] lockups w/ AGP 4x
Using the texmem-0-0-1 branch from CVS and enabling AGP 4x in XF86Config-4 causes X to lock upon startup. If I have my xinitrc setup to run Quake III alone, I first get the bare black and white X background and cursor for about a second and then some strange lines move across a black screen; I can't switch VT's and ssh'ing in doesn't work. If I have my xinitrc setup to run windowmaker, however, I can ssh in. I then try to kill X via an HUP, but that doesn't work and I try kill -9. At that point, ssh stops working. If it helps at all, the texmem-0-0-1 branch I was previously using (from Nov. 1) works fine with AGP 4x. My system is a Mobile P-4 1.8 ghz with a 16 MB 4x AGP M7. Sorry if this message belongs in the users board. Thank you, Jonathan Thambidurai --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] lockups w/ AGP 4x
On Fri, Dec 13, 2002 at 10:45:45PM -0500, [EMAIL PROTECTED] wrote: > Using the texmem-0-0-1 branch from CVS and enabling AGP 4x in > XF86Config-4 causes X to lock upon startup. If I have my xinitrc > setup to run Quake III alone, I first get the bare black and white X > background and cursor for about a second and then some strange lines > move across a black screen; I can't switch VT's and ssh'ing in doesn't > work. If I have my xinitrc setup to run windowmaker, however, I can > ssh in. I then try to kill X via an HUP, but that doesn't work and I > try kill -9. At that point, ssh stops working. If it helps at all, > the texmem-0-0-1 branch I was previously using (from Nov. 1) works > fine with AGP 4x. My system is a Mobile P-4 1.8 ghz with a 16 MB 4x > AGP M7. Sorry if this message belongs in the users board. Do you have fast-writes enabled? Does it work at AGP 2x? I'll see if I can look into this in the next few days, but I've got a bunch of other stuff already on my plate. -- Smile! http://antwrp.gsfc.nasa.gov/apod/ap990315.html --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] lockups w/ AGP 4x
On Tue, Dec 17, 2002 at 12:56:38PM -0800, Ian Romanick wrote: > On Fri, Dec 13, 2002 at 10:45:45PM -0500, [EMAIL PROTECTED] wrote: > > Using the texmem-0-0-1 branch from CVS and enabling AGP 4x in > > XF86Config-4 causes X to lock upon startup. If I have my xinitrc > > setup to run Quake III alone, I first get the bare black and white X > > background and cursor for about a second and then some strange lines > > move across a black screen; I can't switch VT's and ssh'ing in doesn't > > work. If I have my xinitrc setup to run windowmaker, however, I can > > ssh in. I then try to kill X via an HUP, but that doesn't work and I > > try kill -9. At that point, ssh stops working. If it helps at all, > > the texmem-0-0-1 branch I was previously using (from Nov. 1) works > > fine with AGP 4x. My system is a Mobile P-4 1.8 ghz with a 16 MB 4x > > AGP M7. Sorry if this message belongs in the users board. > > Do you have fast-writes enabled? Does it work at AGP 2x? I'll see if I can > look into this in the next few days, but I've got a bunch of other stuff > already on my plate. > I did some testing with the latest texmem from CVS. Here is what happens (note that I rebooted my machine after installing the latest CVS radeon driver). AGP4x - If I first start X with WindowMaker as the window manager, everything seems to work fine. If I subsequently exit X and then start X and WindowMaker again, the X server seems to hang (the screen is black). I can ssh in; wmaker is not running. A regular kill command doesn't stop X, so I try kill -9; at that point, the machine completely locks up and the ssh connection stops working. Upon reboot, I try to play Quake3 (I run it in an instance of X without any other clients like window managers, etc.). After X starts, vertical lines run down the screen and I am forced to reboot. AGP2x - I can start WindowMaker several times without the problems listed before. Also, Quake3 will start. It has problems, however; if I set the texture detail to the max, after loading certain levels the X server will crash to the command line. Any resolution higher than 800x600 does the same thing. My AGP aperture is set to 64 MB. My system has 256 MB of system memory and 16 MB of video memory. Note that the game was running quite nicely with max settings and 1024x768 with the texmem CVS from Nov. 1 and AGP4X. I have never enabled fast-writes. Thank you, Jonathan Thambidurai --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] lockups w/ AGP 4x
On Tue, Dec 17, 2002 at 11:07:16PM -0500, [EMAIL PROTECTED] wrote: > On Tue, Dec 17, 2002 at 12:56:38PM -0800, Ian Romanick wrote: > > On Fri, Dec 13, 2002 at 10:45:45PM -0500, [EMAIL PROTECTED] wrote: > > > Using the texmem-0-0-1 branch from CVS and enabling AGP 4x in > > > XF86Config-4 causes X to lock upon startup. If I have my xinitrc > > > setup to run Quake III alone, I first get the bare black and white X > > > background and cursor for about a second and then some strange lines > > > move across a black screen; I can't switch VT's and ssh'ing in doesn't > > > work. If I have my xinitrc setup to run windowmaker, however, I can > > > ssh in. I then try to kill X via an HUP, but that doesn't work and I > > > try kill -9. At that point, ssh stops working. If it helps at all, > > > the texmem-0-0-1 branch I was previously using (from Nov. 1) works > > > fine with AGP 4x. My system is a Mobile P-4 1.8 ghz with a 16 MB 4x > > > AGP M7. Sorry if this message belongs in the users board. > > > > Do you have fast-writes enabled? Does it work at AGP 2x? I'll see if I can > > look into this in the next few days, but I've got a bunch of other stuff > > already on my plate. > > > > I did some testing with the latest texmem from CVS. Here is what > happens (note that I rebooted my machine after installing the latest > CVS radeon driver). > > AGP4x > - > If I first start X with WindowMaker as the window manager, everything > seems to work fine. If I subsequently exit X and then start X and > WindowMaker again, the X server seems to hang (the screen is black). I can > ssh in; wmaker is not running. A regular kill command doesn't stop X, > so I try kill -9; at that point, the machine completely locks up and > the ssh connection stops working. Upon reboot, I try to play Quake3 > (I run it in an instance of X without any other clients like window > managers, etc.). After X starts, vertical lines run down the screen > and I am forced to reboot. > > AGP2x > - > I can start WindowMaker several times without the problems listed > before. Also, Quake3 will start. It has problems, however; if I set > the texture detail to the max, after loading certain levels the X server > will crash to the command line. Any resolution higher than 800x600 > does the same thing. > > My AGP aperture is set to 64 MB. My system has 256 MB of system > memory and 16 MB of video memory. Note that the game was running > quite nicely with max settings and 1024x768 with the texmem CVS from Nov. 1 > and AGP4X. I have never enabled fast-writes. > > Thank you, > Jonathan Thambidurai > I would like to inform you that I have found the solution to the above-mentioned problems. These problems occur in several branches of XFree86 starting from about one-and-a-half months ago, I believe. The removal of two lines of code was all that was necessary to correct EVERY one of the above problems. It is as follows. File: xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.c Lines: 710 and 711 I understand that this code may be beneficial for some people, but I do not understand enough about X or the various registers of the graphics hardware to actually 'fix' the code and these lines wreak havok on my system. -Jonathan Thambidurai --- 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
Re: [Dri-devel] lockups w/ AGP 4x
On Mit, 2003-01-01 at 04:19, [EMAIL PROTECTED] wrote: > On Tue, Dec 17, 2002 at 11:07:16PM -0500, [EMAIL PROTECTED] wrote: > > On Tue, Dec 17, 2002 at 12:56:38PM -0800, Ian Romanick wrote: > > > On Fri, Dec 13, 2002 at 10:45:45PM -0500, [EMAIL PROTECTED] wrote: > > > > Using the texmem-0-0-1 branch from CVS and enabling AGP 4x in > > > > XF86Config-4 causes X to lock upon startup. If I have my xinitrc > > > > setup to run Quake III alone, I first get the bare black and white X > > > > background and cursor for about a second and then some strange lines > > > > move across a black screen; I can't switch VT's and ssh'ing in doesn't > > > > work. If I have my xinitrc setup to run windowmaker, however, I can > > > > ssh in. I then try to kill X via an HUP, but that doesn't work and I > > > > try kill -9. At that point, ssh stops working. If it helps at all, > > > > the texmem-0-0-1 branch I was previously using (from Nov. 1) works > > > > fine with AGP 4x. My system is a Mobile P-4 1.8 ghz with a 16 MB 4x > > > > AGP M7. Sorry if this message belongs in the users board. > > > > > > Do you have fast-writes enabled? Does it work at AGP 2x? I'll see if I can > > > look into this in the next few days, but I've got a bunch of other stuff > > > already on my plate. > > > > > > > I did some testing with the latest texmem from CVS. Here is what > > happens (note that I rebooted my machine after installing the latest > > CVS radeon driver). > > > > AGP4x > > - > > If I first start X with WindowMaker as the window manager, everything > > seems to work fine. If I subsequently exit X and then start X and > > WindowMaker again, the X server seems to hang (the screen is black). I can > > ssh in; wmaker is not running. A regular kill command doesn't stop X, > > so I try kill -9; at that point, the machine completely locks up and > > the ssh connection stops working. Upon reboot, I try to play Quake3 > > (I run it in an instance of X without any other clients like window > > managers, etc.). After X starts, vertical lines run down the screen > > and I am forced to reboot. > > > > AGP2x > > - > > I can start WindowMaker several times without the problems listed > > before. Also, Quake3 will start. It has problems, however; if I set > > the texture detail to the max, after loading certain levels the X server > > will crash to the command line. Any resolution higher than 800x600 > > does the same thing. > > > > My AGP aperture is set to 64 MB. My system has 256 MB of system > > memory and 16 MB of video memory. Note that the game was running > > quite nicely with max settings and 1024x768 with the texmem CVS from Nov. 1 > > and AGP4X. I have never enabled fast-writes. > > > > Thank you, > > Jonathan Thambidurai > > > > I would like to inform you that I have found the solution to the > above-mentioned problems. These problems occur in several branches of > XFree86 starting from about one-and-a-half months ago, I believe. The > removal of two lines of code was all that was necessary to correct > EVERY one of the above problems. It is as follows. > > File: xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.c > Lines: 710 and 711 A unified diff says more than a thousand words, but I assume it's about this: /* Workaround for some hardware bugs */ if (info->ChipFamily < CHIP_FAMILY_R200) OUTREG(RADEON_AGP_CNTL, INREG(RADEON_AGP_CNTL) | 0x000e0020); > I understand that this code may be beneficial for some people, but I > do not understand enough about X or the various registers of the > graphics hardware to actually 'fix' the code and these lines wreak > havok on my system. These lines of code come from XFree86 CVS, probably by Kevin E. Martin or Hui Yu, It would be interesting to hear their rationale behind this, putting them on CC:. > In my previous message, containing the suggested fix removing two > lines of code, I reported that it fixed all of the mentioned > problems. I have found this not to be the case. 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. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast --- 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
Re: [Dri-devel] lockups w/ AGP 4x
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: > > On Tue, Dec 17, 2002 at 11:07:16PM -0500, [EMAIL PROTECTED] wrote: > > > On Tue, Dec 17, 2002 at 12:56:38PM -0800, Ian Romanick wrote: > > > > On Fri, Dec 13, 2002 at 10:45:45PM -0500, [EMAIL PROTECTED] wrote: > > > > > Using the texmem-0-0-1 branch from CVS and enabling AGP 4x in > > > > > XF86Config-4 causes X to lock upon startup. If I have my xinitrc > > > > > setup to run Quake III alone, I first get the bare black and white X > > > > > background and cursor for about a second and then some strange lines > > > > > move across a black screen; I can't switch VT's and ssh'ing in doesn't > > > > > work. If I have my xinitrc setup to run windowmaker, however, I can > > > > > ssh in. I then try to kill X via an HUP, but that doesn't work and I > > > > > try kill -9. At that point, ssh stops working. If it helps at all, > > > > > the texmem-0-0-1 branch I was previously using (from Nov. 1) works > > > > > fine with AGP 4x. My system is a Mobile P-4 1.8 ghz with a 16 MB 4x > > > > > AGP M7. Sorry if this message belongs in the users board. > > > > > > > > Do you have fast-writes enabled? Does it work at AGP 2x? I'll see if I can > > > > look into this in the next few days, but I've got a bunch of other stuff > > > > already on my plate. > > > > > > > > > > I did some testing with the latest texmem from CVS. Here is what > > > happens (note that I rebooted my machine after installing the latest > > > CVS radeon driver). > > > > > > AGP4x > > > - > > > If I first start X with WindowMaker as the window manager, everything > > > seems to work fine. If I subsequently exit X and then start X and > > > WindowMaker again, the X server seems to hang (the screen is black). I can > > > ssh in; wmaker is not running. A regular kill command doesn't stop X, > > > so I try kill -9; at that point, the machine completely locks up and > > > the ssh connection stops working. Upon reboot, I try to play Quake3 > > > (I run it in an instance of X without any other clients like window > > > managers, etc.). After X starts, vertical lines run down the screen > > > and I am forced to reboot. > > > > > > AGP2x > > > - > > > I can start WindowMaker several times without the problems listed > > > before. Also, Quake3 will start. It has problems, however; if I set > > > the texture detail to the max, after loading certain levels the X server > > > will crash to the command line. Any resolution higher than 800x600 > > > does the same thing. > > > > > > My AGP aperture is set to 64 MB. My system has 256 MB of system > > > memory and 16 MB of video memory. Note that the game was running > > > quite nicely with max settings and 1024x768 with the texmem CVS from Nov. 1 > > > and AGP4X. I have never enabled fast-writes. > > > > > > Thank you, > > > Jonathan Thambidurai > > > > > > > I would like to inform you that I have found the solution to the > > above-mentioned problems. These problems occur in several branches of > > XFree86 starting from about one-and-a-half months ago, I believe. The > > removal of two lines of code was all that was necessary to correct > > EVERY one of the above problems. It is as follows. > > > > File: xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.c > > Lines: 710 and 711 > > A unified diff says more than a thousand words, but I assume it's about > this: > > /* Workaround for some hardware bugs */ > if (info->ChipFamily < CHIP_FAMILY_R200) > OUTREG(RADEON_AGP_CNTL, INREG(RADEON_AGP_CNTL) | 0x000e0020); > > > I understand that this code may be beneficial for some people, but I > > do not understand enough about X or the various registers of the > > graphics hardware to actually 'fix' the code and these lines wreak > > havok on my system. > > These lines of code come from XFree86 CVS, probably by Kevin E. Martin > or Hui Yu, It would be interesting to hear their rationale behind this, > putting them on CC:. > > > > In my previous message, containing the suggested fix removing two > > lines of code, I reported that it fixed all of the mentioned > > problems. I have found this not to be the case. 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.
Re: [Dri-devel] lockups w/ AGP 4x
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. > 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 --- 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
Re: [Dri-devel] lockups w/ AGP 4x
On 2 Jan 2003, Michel [ISO-8859-1] 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. > > > 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. FYI, running 'xvidtune -unlock' should also free the pointer. Adam --- 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
Re: [Dri-devel] lockups w/ AGP 4x
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
Re: [Dri-devel] lockups w/ AGP 4x
On Thu, Jan 02, 2003 at 10:09:49PM +, Ian Molton wrote: > My posts arent appearing on the DRI lists... so I am replying to you AND > the list. could you forward this to the list? > > > On 02 Jan 2003 22:42:33 +0100 > Michel D?nzer <[EMAIL PROTECTED]> wrote: > > > > 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. > > I have CVS as of Jan 1 installed here, on a Radeon 9000 pro. > > Quake3 runs fine, but the mouse **in q3 only** is jammed into the top > left corner. > > it works FINE in X windows, and Q3 releases it ok when it quits. > > it also grabs and releases ok when q3 is in windowed mode. > > the only problem is that as long as q3 has the mouse, it is stuck in the > top left of the q3 viewport. > This happed in the 1.32 patch of Q3A with the CVS versions of XFree86. There is a Linux-specific patch 1.32b which I think was built specifically to address this problem. I got mine from a link on Linuxgames.com. I beleive that id should have it on their ftp, however. -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
Re: [Dri-devel] lockups w/ AGP 4x
On Don, 2003-01-02 at 23:10, [EMAIL PROTECTED] wrote: > 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? Probably, but you still need to run Q3A in gdb to see where it crashes. :) -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast --- 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
Re: [Dri-devel] lockups w/ AGP 4x
Am Donnerstag, 2. Januar 2003 23:10 schrieb [EMAIL PROTECTED]: > 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. Your are definitely telling us the _truth_! I got it running from the beginning with my 3dfx Banshee/V3/V5 and latest Radeon 8500 QL. But I get the same as you with the latest driver stuff. Don't know exactly when it was broken. It runs fine (demo four) but is stuttering like hell during the intro and all cinematic (but works like a charm under 2.5.49+). The mouse is _NOT_ usable and still stuck in the upper left corner. Complete system hang after some X server restarts. Sometimes during the second run (KDE relogin). What we definitely need is a "feature freeze" phase before the XFree86 4.3.0 release. I never had such an unstable system before. 2.4.20 (-aa) XFree86 4.2.1 (SuSE 7.3) DRI CVS on-top with and without page flipping, AGP 1/2/4, fast write dual Athlon MP 1900+ AMD 768MPX Radeon 8500 QL -Dieter --- 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
