Bug 494420 - F-11 beta fails in graphical mode on Powerbook G3
F-11 beta fails in graphical mode on Powerbook G3
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-r128 (Show other bugs)
powerpc Linux
low Severity medium
: ---
: ---
Assigned To: Dave Airlie
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-04-06 15:43 EDT by Tom Lane
Modified: 2018-04-11 07:54 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 07:42:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
X.log (29.93 KB, text/plain)
2009-04-07 13:36 EDT, Tom Lane
no flags Details

  None (edit)
Description Tom Lane 2009-04-06 15:43:44 EDT
Description of problem:
If I try to install in graphical mode on an Apple Powerbook G3 "Pismo" (yeah, it's ancient), anaconda fails to detect the display hardware properly.  I see various random screen flashes before it settles on a pattern of blue and white diagonal stripes, which I would say represent failure to sync if this were an analog display; but LED displays are always digital no?

Version-Release number of selected component (if applicable):
whatever is on the the F11 beta ISO

How reproducible:

Steps to Reproduce:
1. try to install ...
Additional info:
The last couple of messages on tty4 are about "putting AGP V2 device into 1x mode".  Unsure if that's related.  Also, tty5 shows a lot of repetitions of "(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument" followed by "[dix] Could not init font path element catalogue:/etc/X11/fontpath.d, removing from list!"

The bug may be of long standing.  I had a non-graphical F-9 install on this machine.  I don't remember exactly why I chose non-graphical, but it might've been because X didn't work then either.
Comment 1 Matěj Cepl 2009-04-07 12:23:32 EDT
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

When the anaconda crashes, please, switch to the console (Ctrl+Alt+F2) and cp /tmp/X* to some other place -- USB stick, some other computer via network, some on the Internet, and please attach it to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.
Comment 2 Tom Lane 2009-04-07 13:36:36 EDT
Created attachment 338552 [details]

Here you go --- the only such file in /tmp was X.log.  (The usual socket files were there too of course)
Comment 3 Bug Zapper 2009-06-09 09:21:41 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 4 Matěj Cepl 2009-11-05 13:25:36 EST
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command

yum upgrade --enablerepo='*-updates-testing'

Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Comment 5 Tom Lane 2009-11-06 20:43:44 EST
Hmm, neither of the proposed ways to test seems applicable here.  The F12 beta composes do not cover PPC, and I don't see how I can yum-update an install disk, which would be needed to get a testable F11 anaconda.
Comment 6 Bug Zapper 2010-04-27 09:31:40 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 7 Bug Zapper 2010-06-28 07:42:55 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.