From: Arthur Marsh on
Kent West wrote, on 13/05/10 23:12:
> I've got an older 600MHz PIII running Sid; if I boot into the installed
> 2.6.26-2-68 kernel, everything's fine, but if I boot into the installed
> 2.6.32-5-68 kernel, everything's fine until X is started (either
> manually or with a session manager or even when trying to create a new
> xorg.conf file using "X -config"). At that point, the screen goes black,
> the keyboard stops responding, and the Xorg.log fills up with :
>
> (EE) R128(0): Idle timed out, resetting engine...
> (EE) R128(0): R128CCEWaitForIdle: CCE stop -9
> (EE) R128(0): R128CCEWaitForIdle: CCE start -9
> (EE) R128(0): R128CCEWaitForIdle: CCE idle -9
> (EE) R128(0): Idle timed out, resetting engine...
> (EE) R128(0): R128CCEWaitForIdle: CCE stop -9
> (EE) R128(0): R128CCEWaitForIdle: CCE start -9
> (EE) R128(0): R128CCEWaitForIdle: CCE idle -9

Have you read http://ftp.x.org/pub/X11R6.9.0/doc/html/r128.4.html
or tried using the VESA driver instead of the R128 driver?

Arthur.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/oenmc7-k93.ln1(a)ppp121-45-136-118.lns11.adl6.internode.on.net
From: Phil Requirements on
On 2010-05-13 08:42:09 -0500, Kent West wrote:
> I've got an older 600MHz PIII running Sid; if I boot into the
> installed 2.6.26-2-68 kernel, everything's fine, but if I boot into
> the installed 2.6.32-5-68 kernel, everything's fine until X is
> started (either manually or with a session manager or even when

Hi, I don't know if this will fix your problem or not. But when
somebody says "my system worked fine with 2.6.26, now it won't work
with 2.6.32" there is one alarm bell that goes off in my head.

Sometime between 2.6.26 and 2.6.30 the Debian team removed proprietary
firmware blobs from the kernel. Several of these blobs are related
to ATI video drivers, including one for r128.

I had a similar issue to you when I moved from 2.6.26 to 2.6.30. I
don't think X stopped working for me, but performance went way
down. While troubleshooting the problem (for a long time), I found a
mention in the README.Debian that said this important firmware had
been removed. I think it was removed at 2.6.29

Do "aptitude show firmware-linux-nonfree" to see what I mean.

* Rage 128 CCE microcode (r128/r128_cce.bin)

I installed the firmware on my systems, but I'm not convinced it worked,
because my video performance doesn't seem as good as it was before.

Make sure to read the READMEs for your video card driver. I think it
will be in /usr/share/doc/r128.

Hope this helps,

Phil


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100523055708.GA2059(a)kasploosh.net
From: Wolodja Wentland on
On Thu, May 13, 2010 at 08:42 -0500, Kent West wrote:
> I've got an older 600MHz PIII running Sid; if I boot into the
> installed 2.6.26-2-68 kernel, everything's fine, but if I boot into
> the installed 2.6.32-5-68 kernel, everything's fine until X is
> started (either manually or with a session manager or even when
> trying to create a new xorg.conf file using "X -config"). At that
> point, the screen goes black, the keyboard stops responding, and the
> Xorg.log fills up with :
>
> (EE) R128(0): Idle timed out, resetting engine...
> (EE) R128(0): R128CCEWaitForIdle: CCE stop -9
> (EE) R128(0): R128CCEWaitForIdle: CCE start -9
> (EE) R128(0): R128CCEWaitForIdle: CCE idle -9
> (EE) R128(0): Idle timed out, resetting engine...
> (EE) R128(0): R128CCEWaitForIdle: CCE stop -9
> (EE) R128(0): R128CCEWaitForIdle: CCE start -9
> (EE) R128(0): R128CCEWaitForIdle: CCE idle -9

I've seen this recently in #debian and we were able to "fix" this with
the following in /etc/X11/xorg.conf

Section "Device"
Identifier "r128"
Driver "r128"
Option "NoAccel"
EndSection

the related bug report is [1] and this will disable acceleration for
your card, so it is not really a good fix. You might also want to make
sure that you have the firmware package(s) installed.

Good luck

Wolodja

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581216
--
.''`. Wolodja Wentland <wentland(a)cl.uni-heidelberg.de>
: :' :
`. `'` 4096R/CAF14EFC
`- 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC