[r128] Can't install Feisty Fawn Herd 4, graphic card problem

[Slobodan D. Sredojevic]

I can't test/install Feisty Fawn 7.04 Herd 4, when it comes to starting X it presents black screen, keyboard is functional Ctrl+Alt+F1 gives: "Ubuntu is loading..." and Ctrl+Alt+F7 gives black screen again.

01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS

So, I suspect this may be a problem: Ubuntu enables DRI by default in xorg.conf, it tries to load r128 module but we have this bug open for some time now:
https://bugs.freedesktop.org/show_bug.cgi?id=5562

I saw this in Edgy Eft (and Fedora Core 6) too - workaround for installing it was to replace /etc/X11/xorg.conf with working one that is different for these lines I need to comment:

# Load "glx"
# Load "dri"

# Section "DRI"
# Mode 0666
# EndSection

With Edgy Eft it was different in that way that I had console working, not with Herd 4 .

One can get Ati Rage 128 DRI working only with this kernel config:

CONFIG_DRM=y
CONFIG_DRM_R128=y

It gives ~ 460 fps in glxgears then.

[Clmason (clmason)]

I see the exact same problem on an iMac G3 400 (Rage 128 RL/VR AGP). Disabling
DRI gets it to work, otherwise it hangs. I get the same error others have
reported in other places:

(EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025
(EE) R128(0): Idle timed out, resetting engine...

This is still happening after updating to xorg 6.9.0 on Debian unstable.

[Michel-tungstengraphics (michel-tungstengraphics)]

Sounds like it could be a duplicate of bug 1889.

[Erik Andrén (erik-andren)]

Any improvements by using custom drm modules from dri.freedesktop.org?
Also please try with a current version of xorg and the ati driver.

[Jlfenton65 (jlfenton65)]

I'm using the latest xorg in Ubuntu 6.10 on an iMac DV+ (450MHz G3 and ATI Rage
128 VR RL video). I have the same problem as described in the thread. Anymore
work on this yet?

[Slobodan D. Sredojevic (sredojevics)]

I can't test/install Feisty Fawn 7.04 Herd 4, when it comes to starting X it presents black screen, keyboard is functional Ctrl+Alt+F1 gives: "Ubuntu is loading..." and Ctrl+Alt+F7 gives black screen again.

01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS

So, I suspect this may be a problem: Ubuntu enables DRI by default in xorg.conf, it tries to load r128 module but we have this bug open for some time now:
https://bugs.freedesktop.org/show_bug.cgi?id=5562

I saw this in Edgy Eft (and Fedora Core 6) too - workaround for installing it was to replace /etc/X11/xorg.conf with working one that is different for these lines I need to comment:

# Load "glx"
# Load "dri"

# Section "DRI"
# Mode 0666
# EndSection

With Edgy Eft it was different in that way that I had console working, not with Herd 4 .

One can get Ati Rage 128 DRI working only with this kernel config:

CONFIG_DRM=y
CONFIG_DRM_R128=y

It gives ~ 460 fps in glxgears then.

[Daniel Stone (daniels)]

Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.

[Slobodan D. Sredojevic (sredojevics)]

Please ignore first paragraph --> used medium was problematic. All the rest is true, still.

I have written to the xorg devel ml, please read it:
http://lists.freedesktop.org/archives/xorg/2007-March/022610.html

I propose following if doable:

For this particular card (all cards that use r128):
- Disable DRI in /etc/X11/xorg.conf by default during install process and after it

This way, install will be possible and with DRI disabled for this particular card one benifit in ability to Suspend to RAM (using S2RAM utility), please look here:
http://dri.freedesktop.org/wiki/ATIRage128

I believe this is the best for Ubuntu for the current state of the driver.

[Bryce Harrington (bryce)]

Is this still an issue on Gutsy?

[Brice Goglin (brice-goglin)]

Looks like Debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412228 as well, reproducible with 6.6.3 and 6.7.197.

[Bryce Harrington (bryce)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Michel-tungstengraphics (michel-tungstengraphics)]

Does

    Option "CCEusecTimeout" "100000"

(or even larger values; the default is 10000) work around the problem?

[Jose Jorge (jjorge)]

I just tested

Option "CCEusecTimeout" "100000"

it doesn't change anything to the display.

[Michel-tungstengraphics (michel-tungstengraphics)]

(In reply to comment #8)
> I just tested
>
> Option "CCEusecTimeout" "100000"
>
> it doesn't change anything to the display.

Did the log file show the option being effective? What about "1000000"?

Anyway, as people claim that this problem doesn't affect x86, maybe there was an architecture specific regression at some point, in which case somebody would need to track that down...

[Orion-cora (orion-cora)]

Created an attachment (id=23137)
Xorg log

Just saw this with Fedora 10 on Dell Precision 340 with ATI Technologies Inc Rage 128 Pro Ultra TF, so it can happen on x86. This is with no xorg.conf. Will try again with Option "CCEusecTimeout" "1000000"

[Orion-cora (orion-cora)]

With:

(**) R128(0): Option "CCEusecTimeout" "1000000"

X crashes on startup. Display is garbled - seems to be related to what was last displayed.

[Nico R. (n-roeser)]

I can always reproduce this on x86, so this bug occurs at least on PowerPC and on x86.

[Mattst88 (mattst88)]

This bug is older than the one I'm marking it as a duplicate of. The other has more information and logs, so I figured it'd be better to not lose that stuff. Will move CCs in this bug to the other.

*** This bug has been marked as a duplicate of bug 23996 ***

[Str8bs (str8bslinux)]

Specific to this bug where X never starts, rather than lockups after starting, I have more recent (Ubuntu 12.04) logs in downstream https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-r128/+bug/1023975

Only workarounds I have found are to ForcePCIMode or Disable DRI. Could this be a uninorth_agp problem? Without really understanding what I am reading, the "AGP apterture is 256M @ 0x0" and "AGP V2 device into 0x mode" seem strange to me.
On iMac with Rage128 Ultra 16M

Summary of relevant (Speculated) from dmesg:
dmesg | grep AGP
[ 0.585628] Linux agpgart interface v0.103
[ 29.655997] agpgart-uninorth 0000:00:0b.0: Apple UniNorth/Pangea chipset
[ 29.658518] agpgart-uninorth 0000:00:0b.0: configuring for size idx: 64
[ 29.736441] agpgart-uninorth 0000:00:0b.0: AGP aperture is 256M @ 0x0
[ 43.502188] agpgart: Couldn't find an AGP VGA controller.
[ 43.502261] agpgart-uninorth 0000:00:0b.0: putting AGP V2 device into 0x mode

dmesg | grep -i vga
[ 0.047384] vgaarb: loaded
[ 32.545041] vgaarb: this pci device is not a vga device
[ 33.354151] vgaarb: this pci device is not a vga device
[ 33.964274] agpgart: Couldn't find an AGP VGA controller.

From Xorg.0.log
[ 265.172] (EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025
[ 265.172] (EE) R128(0): Idle timed out, resetting engine...
[ 282.882] (EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025
[ 282.882] (EE) R128(0): Idle timed out, resetting engine...
[ 298.704] (EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025
[ 298.705] (EE) R128(0): Idle timed out, resetting engine...