Further testing has proved some of my earlier statements incorrect. I
apologize for my stupidity, but here is more correct information:
On older kernels, no ForcePCIMode option is needed to prevent CCE restart.
Still, when running without this option, GL apps do crash after a while, though
not ne
That patch didn't work for me a while ago when i tried it. It doesn't
seem to be the same problem, either, if you look at it closely.
--
R128 DRI lockup on PPC
https://launchpad.net/bugs/38949
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubu
This looks like just the thing:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=236187
--
R128 DRI lockup on PPC
https://launchpad.net/bugs/38949
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Never mind, that patch makes the CCE reset less, which actually makes it even
slower.
If i do the exact opposite (make it reset more), I get way more error messages,
but more resets means that the lock isn't as bad
i is assigned a smaller value in this case:
instead, CCE idle took i = 33
prob
Looking at it on my system, (Note that I've been messing around and am
using a lot of the stuff from hoary, without sucess sof ar), every other
time that R128CCEWaitForIdle is called, ret=0 and everything is fine.
When not 0, ret=-16 and engine is reset.
--
R128 DRI lockup on PPC
https://launchpa
So, I've installed debian stable with working dri and am now working my way up
to see what breaks
it. So far, I've installed the latest xorg (including xserver-xorg-video-ati,
Mesa, core xserver ,etc.)
and things are still working like a charm. So, it's probably not the direct
fault of either of
I can also report this bug on my ppc.
Using some old cds, I have found that my old hoary cds work (with agp, too),
while breezy and later don't.
Apparently, there has been some sort of regression?
--
R128 DRI lockup on PPC
https://launchpad.net/bugs/38949
--
ubuntu-bugs mailing list
ubuntu-bu
