Re: [Dri-devel] Radeon DRI problems still =(
On Thu, Apr 12, 2001 at 01:16:06AM -0700, Simon Kirby wrote: After a few hours, the machine will lock up if I have the drm module loaded. It runs fine for days on end without it, so it's probably AGP related. Lockups happen a lot faster if I run a GLX app that uses more than a few textures. gears and similar run just fine, but something such as QuakeForge will lock up the system usually within a minute. By lockup, I mean that the machine no longer responds to the keyboard and the monitor pops up its no signal message. SysRq commands still work, but remote logins don't. I'm also seeing lockups with Quake3 on my ASUS P2B-DS dual Celeron board with my Radeon VE 32MB DDR. Actually, what is REALLY freakin' weird is that it seems to work just about to the point that I start typing something, at which point the next thing I type has to start with SysRq because it's locked tight.. It's truly bizarre, and nobody seems to have the slightest idea what could be causing it. I've tried every suggestion I've been given at least once - some with disasterous (but fixable, thankfully) results like changing AGP driving strength. Setting it to the suggested value caused the box not to boot at all. Old ISA video card to the rescue. I suspect we're seeing different problems, and I've pretty much concluded that whatever the hell is wrong, it's specific to my particular setup. It'd most likely take someone with an identical motherboard and video card (possibly also running at 100MHz as I am running it) to duplicate the problems I am having. I'm keeping my eyes open, but at the same time I'm looking into the possibility of a PCI card to replace my Voodoo2 and possibly some sort of setup that way. Sometimes it will play fine for a few CTF games, but it will usually die somewhere in the game. It seems to die either one of two ways -- either the screen will go blank or become corrupted (for example, scanning the first scan line for the entire screen while my second head on a PCI card remains fine), or the screen will just freeze. In the latter case, the machine will not respond to sysrq. In the former case, it will, and I can unmount and reboot cleanly. [..] I have yet to see anything die while I'm not playing Quake 3, so it seems GL-related. I suppose I should try running UT for a while and see if similar lockups occur. Well, if yu manage to track down the problem, I would be interested in the result. How does it work if you disable the use of the second head? -- Joseph Carter [EMAIL PROTECTED]Free software developer Joy wow... simple maths show that Debian developers have closed more than *31* *thousand* bug reports since our BTS exists! Joy that is about 30999 more than Microsoft ;) PGP signature
Re: [Dri-devel] Radeon lockups with Quake3
On Thu, Apr 12, 2001 at 08:56:12PM -0700, Simon Kirby wrote: I decided to upgrade to the newest (as of earlier today) DRI tree, along with 2.4.3-ac5. I was playing Quake3 again, and got a lockup which has never happened before: the monitor on my Radeon went blank, but Quake3 kept going (I could hear the sounds and still "t"alk and hear the transmission). Usually the sound will loop over and over and sysrq will either work or not work. This time everything worked except for the monitor, but it locked up as soon as I quit the game (blindly). The looping sound, blanked screen, and sysrq working case is exactly the one which I can reproduce faithfully with QuakeForge. I have not tried Q3A recently as I have no way of knowing exactly what it's doing whereas I obviously know QF pretty well.. I have been experiencing this combination of problems since 2.4.2. I currently use a slightly patched version of 2.4.3-ac4 (I've added lm-sensors and an updated bttv driver..) I've been temporarily out of commission for the past day or two, so I haven't tried -ac5 yet. Just so you know that the error is probably not a freak bug which only you have happen. Of course, it dies for me in seconds, not minutes. I'll see if I can produce your results under -ac5 in Q3A. If you have a Quake CD laying around (or don't mind tracking down the shareware pak file), could you give QuakeForge a shot? Perhaps something it does is killing it faster? I'm using the "quakeforge" CVS tree, usually the nq-glx target. It also happens with the qw-client-glx target. If I am real lucky, we are experiencing the same bug. -- Joseph Carter [EMAIL PROTECTED]Free software developer RFC 882 put the dot in .com, not Sun Microsystems -- Seen on Slashdot PGP signature
Re: [Dri-devel] Binary packages...
- Original Message - From: "Scott Call" [EMAIL PROTECTED] To: "dri-devel" [EMAIL PROTECTED] Sent: Friday, April 13, 2001 12:03 AM Subject: Re: [Dri-devel] Binary packages... On Wed, 11 Apr 2001, Adam K Kirchhoff wrote: FYI, the ftp server has a /pub/dri/release directory with binary modules and server, but the /pub/dri directory only has binary modules; no X server. Unfortunately, the X server in the release directory won't work with the newer binary modules in the /pub/dri directory, pretty much making them useless :-) The latest XFree86 binary lives in the "Extras-.*.gz" file. I found that out the other day :) Except that there's no Extras*.gz file in /pub/dri, only in /pub/dri/release. And the server in /pub/dri/release doesn't work with the binary modules in /pub/dri Adam ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Radeon DRI problems still =(
On Fri, Apr 13, 2001 at 05:02:42AM -0700, Joseph Carter wrote: Actually, what is REALLY freakin' weird is that it seems to work just about to the point that I start typing something, at which point the next thing I type has to start with SysRq because it's locked tight.. It's truly bizarre, and nobody seems to have the slightest idea what could be causing it. I've tried every suggestion I've been given at least once - some with disasterous (but fixable, thankfully) results like changing AGP driving strength. Setting it to the suggested value caused the box not to boot at all. Old ISA video card to the rescue. Hmm! Where is this option? I can't seem to find it in my BIOS anywhere. Perhaps it's only an option on newer boards. What other things have you tried? I suspect we're seeing different problems, and I've pretty much concluded that whatever the hell is wrong, it's specific to my particular setup. It'd most likely take someone with an identical motherboard and video card (possibly also running at 100MHz as I am running it) to duplicate the problems I am having. I'm keeping my eyes open, but at the same time I'm looking into the possibility of a PCI card to replace my Voodoo2 and possibly some sort of setup that way. Actually, I'm running the bus at 100 MHz. Dual Slot1 300A Celerons drilled soldered to run at dual 450 MHz, but I left that part out to increase the validity of my report. ;) Sometimes it will play fine for a few CTF games, but it will usually die somewhere in the game. It seems to die either one of two ways -- either the screen will go blank or become corrupted (for example, scanning the first scan line for the entire screen while my second head on a PCI card remains fine), or the screen will just freeze. In the latter case, the machine will not respond to sysrq. In the former case, it will, and I can unmount and reboot cleanly. [..] I have yet to see anything die while I'm not playing Quake 3, so it seems GL-related. I suppose I should try running UT for a while and see if similar lockups occur. Well, if yu manage to track down the problem, I would be interested in the result. How does it work if you disable the use of the second head? I haven't tried. It's on a PCI board (not the second head of the Radeon VE), so I didn't think it would be affecting it. As I'm running out of other things to try myself, I'll try this in a bit. Simon- [ Stormix Technologies Inc. ][ NetNation Communications Inc. ] [ [EMAIL PROTECTED] ][ [EMAIL PROTECTED]] [ Opinions expressed are not necessarily those of my employers. ] ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Binary packages...
Odd, I could swear there was one back on the 10th when I d/l'd them last... I remember having to d/l it because I was getting a PCI bus master symbol error in the r128 drivers Oh well, sorry to mislead you. -s Scott Call Router Geek, ATGi, home of $6.95 Prime Rib "Only the Phoenix rises and does not descend And everything changes. And nothing is truly lost." - Neil Gaiman, The Wake On Fri, 13 Apr 2001, Adam K Kirchhoff wrote: - Original Message - From: "Scott Call" [EMAIL PROTECTED] To: "dri-devel" [EMAIL PROTECTED] Sent: Friday, April 13, 2001 12:03 AM Subject: Re: [Dri-devel] Binary packages... On Wed, 11 Apr 2001, Adam K Kirchhoff wrote: FYI, the ftp server has a /pub/dri/release directory with binary modules and server, but the /pub/dri directory only has binary modules; no X server. Unfortunately, the X server in the release directory won't work with the newer binary modules in the /pub/dri directory, pretty much making them useless :-) The latest XFree86 binary lives in the "Extras-.*.gz" file. I found that out the other day :) Except that there's no Extras*.gz file in /pub/dri, only in /pub/dri/release. And the server in /pub/dri/release doesn't work with the binary modules in /pub/dri Adam ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Radeon lockups with Quake3
On Fri, Apr 13, 2001 at 01:32:39PM -0700, Simon Kirby wrote: I'm trying to compile the glx client but I'm not having much luck. Debian unstable. How are you compiling it over there? Okay, finally got qf-client-glx to compile (library conflicts with DRI tree). It starts up and runs, but I'm not able to find any multiplayer servers and it doesn't let me play single player. I'll search for some in xqf or something. However, in the mean time, there are some strange things happening. As soon as the client starts, my analog flatpanel starts to get all jittery -- pixels are all vibrating left and right. I can _sometimes_ see a single row of pixels jittering normally if the sync is misaligned, but quakeforge isn't even changing the resoution (1024x768) and it just suddenly starts going all funky. Each scanline is different, as if the horizontal sync is changing phase slightly. As soon as I quit, everything returns to normal. I just obscured the window trying to find a multiplayer server, and got a lock up. Sysrq worked, but my mouse was frozen. I hadn't even started playing yet. Trying again... Simon- [ Stormix Technologies Inc. ][ NetNation Communications Inc. ] [ [EMAIL PROTECTED] ][ [EMAIL PROTECTED]] [ Opinions expressed are not necessarily those of my employers. ] ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Radeon lockups with Quake3
On Fri, Apr 13, 2001 at 02:07:05PM -0700, Simon Kirby wrote: On Fri, Apr 13, 2001 at 01:32:39PM -0700, Simon Kirby wrote: I'm trying to compile the glx client but I'm not having much luck. Debian unstable. How are you compiling it over there? Okay, finally got qf-client-glx to compile (library conflicts with DRI tree). It starts up and runs, but I'm not able to find any multiplayer servers and it doesn't let me play single player. I'll search for some in xqf or something. However, in the mean time, there are some strange things happening. As soon as the client starts, my analog flatpanel starts to get all jittery -- pixels are all vibrating left and right. I can _sometimes_ see a single row of pixels jittering normally if the sync is misaligned, but quakeforge isn't even changing the resoution (1024x768) and it just suddenly starts going all funky. Each scanline is different, as if the horizontal sync is changing phase slightly. As soon as I quit, everything returns to normal. I just obscured the window trying to find a multiplayer server, and got a lock up. Sysrq worked, but my mouse was frozen. I hadn't even started playing yet. Trying again... Well, I compiled "nuq" instead (the single player version), and I just finished three levels without any problems (other than the weird pixel thing which doesn't happen in q3). I tried obscuring the window, changing virtual desktops, dragging everything over it, etc., and couldn't get it to lock up at all. Before, when I had my G200, I could cause a lockup with any GL program by dragging partially or fully obscuring the GL window. It seems that this isn't causing it, though, or something in the multiplayer client is. Simon- [ Stormix Technologies Inc. ][ NetNation Communications Inc. ] [ [EMAIL PROTECTED] ][ [EMAIL PROTECTED]] [ Opinions expressed are not necessarily those of my employers. ] ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Radeon DRI problems still =(
On Fri, Apr 13, 2001 at 12:10:11PM -0700, Simon Kirby wrote: Actually, what is REALLY freakin' weird is that it seems to work just about to the point that I start typing something, at which point the next thing I type has to start with SysRq because it's locked tight.. It's truly bizarre, and nobody seems to have the slightest idea what could be causing it. I've tried every suggestion I've been given at least once - some with disasterous (but fixable, thankfully) results like changing AGP driving strength. Setting it to the suggested value caused the box not to boot at all. Old ISA video card to the rescue. Hmm! Where is this option? I can't seem to find it in my BIOS anywhere. Perhaps it's only an option on newer boards. What other things have you tried? P2C/C2P(?) concurrency, turning off AGP-4x mode all together, and other settings. I posted my AGP-related settings about a week ago along with kernel info, system info, etc. I suspect we're seeing different problems, and I've pretty much concluded that whatever the hell is wrong, it's specific to my particular setup. It'd most likely take someone with an identical motherboard and video card (possibly also running at 100MHz as I am running it) to duplicate the problems I am having. I'm keeping my eyes open, but at the same time I'm looking into the possibility of a PCI card to replace my Voodoo2 and possibly some sort of setup that way. Actually, I'm running the bus at 100 MHz. Dual Slot1 300A Celerons drilled soldered to run at dual 450 MHz, but I left that part out to increase the validity of my report. ;) AMD Duron 800, running 100x8. I don't overclock - my CPU is already 109F as it is! -- Joseph Carter [EMAIL PROTECTED]Free software developer wichert solaris is bsd, so it should work * Espy takes wichert's crack pipe away PGP signature
