Comment 48 for bug 1541082

Revision history for this message
Fritz Hudnut (este-el-paz) wrote : Re: [Bug 1541082] Re: [PowerMac3,1] Blotchy GUI graphics for images

On Fri, Jul 29, 2016 at 10:24 AM, ernsteiswuerfel <email address hidden>
wrote:

> Added the upstream bug to this tracker. Then I realized that strictly
> speaking this bug "X doesn't start with r128 driver (ATI RAGE)
> [powerpc]" has a different meaning from this one here "blotchy
> graphics". I think it's best to create a new Ubuntu Xorg bug and add the
> upstream info there.
>
> Sorry for the noise!
>
> @Fritz:
>
> Your xorg.conf looks fine. After altering parameters check your Xorg.log
> after you restarted X, to look what exactly went wrong with the driver you
> selected xorg.conf. Just use the different drivers "modesetting", "fbdev",
> "fbdevhw" with different bit depths and see what happens.
> If your monitor is capacle also always use the native resolution of your
> monitor. The Rage 128 is able to do 1920x1080 if you got the most recent PM
> 3,1 (http://identimac.com/modelDetails/Power%20Macintosh%20G4/23.html)
>

Yes, I'm also sorry for the "noise," but I decided to include it here as
well to show the personal efforts being expended to work on this problem .
. . and the resultant, "now it's not blotchy, now it is a blackish screen
with no images . . . that is happening, etc.

@ernsteiswuerfel:

OK, glad to hear that, yes, I thought it looked "OK" as well, but, it made
no difference in display showing up, or even trying to show up. Although
when I booted the live DVD session it took literally 3 or 4 minutes for the
cursor to appear and then the desktop; and perhaps I haven't been letting
it take that long with these recent efforts?? It's all become a tad bit
"odd" . . . in that trying the --configure gambit was returned as "failed"
. . . and looking through "lsmod" shows none of the usual suspects as far
as video drivers goes . . . and I did "autoclean" trying to remove "r128"
to see if that would let the xorg.conf get busy . . . and r128 didn't show
up in that list, so I did "sudo rm x-x-v-r128" (spelled out) and then it
said "no such file or directory" . . . .

And, multiple reboots and so forth, makes for a lot of time . . . .
Anyway, as it is now, the graphics are not "blotchy" . . . they are "gone"
so I don't know how I can support a "new" Bugzilla r128 bug with "evidence"
because . . . now the screen is black, etc . . . and there is an xorg.conf
file whereas before there wasn't, etc.

I did look over the Xorg.log a couple times . . . nothing of any apparent
relevance showed up, but then this area is an area of weakness . . . I have
the "dual-boot" install process down, and years back I spent endless hours
trying to get 12.04 to run the display on my old iMac 800 . . . now I'm
generally finding that it is easier to do a fresh install than to mess
around with the console on the tiny details . . . .

But, I was thinking this morning I have some notes about the display
"modes" where I have used something like "1024 x 768@60-32" . . . something
like that, and ***that*** did make a difference on my iBook to get the
display to work properly . . . possibly that is worth trying out . . . .
I'll post back on the "progress" . . . when I get there.

F