[Savage40] Some oddness - agp init failure with one particular window manager.

[John Connors]

I have a few-weeks-old CVS. It runs fine with ratpoison-0.14 and 
Afterstep 1.18.1 (direct rendering is fast) - but fails to initalise (no 
agp) on Afterstep 2.00.4 - so, back to slow rendering for me.

My first guess was it's out of AGP memory..but that seems not to be the 
case, according to the log, Afterstep is using 4mb of the 8mb available 
and the driver claims it's fine with just 4mb in the logs. Since it 
actually fails to initalise AGP shortly after, maybe it's telling lies?

Is there anyway I can get a more detailed log? Isn't there some magic 
environment variable? I'm going to compile down afterstep to just use 2 
desktops with 2 screens each to see if that saves memory. Also, I 
noticed in the logs a line about /dev/dri/card0 failing to open, result 
= -1, (Unknown error 999), and the device file exists.

/proc/pci says I have a Savage Mobile (Savage MX/MV (rev18), and am 
running 2.6.10, and that I have a Intel 440BX/ZX/DX AGP Bridge..

If I can get some more detailed logs and they will be of value, or you 
want me to try with latest CVS, I will..


-- 
Cyborg Animation Programmer
http://yagc.blogspot.com
http://badbyteblues.blogspot.com