[r128] no dri or xgl on imac g3

Please try Gutsy Beta, and attach Xorg.0.log

this bug is still in gutsy. Xorg.0.log in attachment

Can you also try running without any xorg.conf?
I am afraid that 8MB is too little to have DRI and 24bit mode though. Please attach the log from running in 16bit.

the only mode that is possible on this imac is: 1024x768 24 bit. Here is the Xorg.0.log when running 16 bit mode (I get a messed up screen).

With 16bit you get DRI, but that's maybe also why it gets messed up. Can you try 16bit and disable DRI with the "NoDRI" option?

adding
option "NoDri"
to the video card Device section didn't help to get the messed up screen away. Xorg.0.log in attachment.

adding
option "NoDri" "true"
to the video card Device section didn't help also. Xorg.0.log in attachment again.

Please see how I wrote NoDRI, not NoDri.

Stil no luck: here is my xorg.conf and Xorg.0.log

Section "Device"
 Identifier "ATI Technologies Inc Rage 128 RL/VR AGP"
 Driver "ati"
 Option "UseFBDev" "true"
 Option "ForcePCIMode" "true"
 Option "SWCursor" "true"
 Option "NoDRI"

Do you need to use FBDev ?

Section "Monitor"
 Identifier "iMac"
 Option "DPMS"
 HorizSync 60-60
 VertRefresh 75-117

Is 60-60 correct?

I think it is.

60-60 works with 24 bit color: this is autoconfigured by Ubuntu live cd. I guess it's not the screen's fault: even though the display looks messed up, it's still static (no flickering). So I think the screen can handle the resolution, but the video chip fails to give a good output.

Yes, I need FBDev.

I looked at bug #22976 which confirms the HorizSync range, and bug #63072 which mentions some FB trouble. Have you tried without UseFBDev?

I spotted this in your log:
(WW) R128(0): Option "NoDRI" is not used

You must use another way of disabling DRI:

Section "Module"
 Disable "glx"
 Disable "dri"
EndSection

By the way, https://wiki.ubuntu.com/PowerPCFAQ suggests HorizSync 58-62.

hehe,

Disable "dri"

works. Now on 16 bit. No glx of course. logs in attachment.

Then it seems like the DRI is broken on these cards. You can file (or look for) an upstream bug, or wait for the r128 support to be merged into the radeon driver (this is on-going upstream) and hope that it will help.

Hmm, the log says:
(--) R128(0): Chipset: "ATI Rage 128 Pro VR PR (PCI)" (ChipID = 0x5052)
but your lspci output said:
ATI Technologies Inc Rage 128 PR/PRO AGP 4X TMDS

Is this an AGP card or a PCI card?

I use the "ForcePCIMode" "true" option. They advised me this option at the forum to get dri working. Maybe that's why xorg reports another card. I will remove it and send a new log.

here it is

I guess it is an AGP card then, it is just wrong in the driver code description (in src/r128_chipset.h).

Should I report a bug somewhere else also?

Yes, thanks, it would be great if you could look for existing bugs and if necessary file a new bug at https://bugs.freedesktop.org
I guess this a well known issue among g3-owners, but I don't know if the r128-developers are aware of it or have enough information to work on it.

I don't know if this will fix this specific issue, but I've backported a bunch of high importance patches that upstream recommended, that fix problems sort of like this one, so I think it would be worth the time to test. Please try this .deb and report what you find:

http://people.ubuntu.com/~bryce/Testing/ati/

If we can determine that the patches in this deb fix this bug, they may be candidates for backporting to Hardy.

Thanks for taking the time to report this bug and helping to make Ubuntu better. In the development cycle for Intrepid there have been some vast improvements in the open source ati video driver and we could use your help testing them. Could you please download the latest Alpha CD image of Intrepid and test this particular bug just using the Live CD? You can find the latest image at http://www.ubuntu.com/testing . Your testing can help make Ubuntu and the open source ati driver even better! Thanks in advance.

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.