System: Mac G4; Mac G5.
Description of problem:
The generic vided looks like someone got the byte or bit order backwards: the
colour [eh] looks like reverse video; and the text pixles are locally scrambled
(I can recognize that something is a letter, but I've no idea which one).
Version-Release number of selected component (if applicable):
What ever was shipped with FC 4 test 1
Steps to Reproduce:
1. Use the generic video on the above macs.
Is this a console problem, or in X? Precisely what hardware (video card,
CRT/LCD) is this seen with? Is it fixed by running the latest version of
Please file a bug in freedesktop.org bugzilla, so the other PPC/X developers
are aware of the issue, and it will get fixed in upstream CVS and included
in the 6.8.3 release.
http://bugs.freedesktop.org in the "xorg" component
Once you've filed the X.org report, please paste the URL here, so we can
track the issue there, and discuss with Xorg PPC developers centrally.
Once a fix gets checked into CVS on the stable branch, we'll review it
for consideration in our rpm packaging in future builds as well.
Thanks in advance.
Setting status to "NEEDINFO", awaiting upstream bug URL for tracking.
(In reply to comment #1)
> Is this a console problem, or in X? Precisely what hardware (video card,
It is the same for me when I tried to install FC4 test2 on an iMac G5 machine in
graphical mode. The welcome screen (or whatever) comes up, but it is unusable.
(I couldn't try X after a text installation yet. First I should backup MacOSX
and repartition the disk)
My hardware: iMac PowerPC G5, Nvidia GeForce FX 5200, (LCD 1440x900)
Probing for video card: NVIDIA GeForce FX (generic)
Probing for monitor type: Unknown monitor
... X server started successfully.
Created attachment 113363 [details]
X.log in /tmp/ramfs
If an upstream bug report has been filed for this issue, and you'd like
the X Devel team to track it for fixes, please update the bug with the
upstream bug URL, and reopen the bug and we will add it to our internal
Setting status to WONTFIX.
(In reply to comment #6)
> If an upstream bug report has been filed for this issue, and you'd like
> the X Devel team to track it for fixes, please update the bug with the
> upstream bug URL, and reopen the bug and we will add it to our internal
I would if I could find the bug! :-)
Does this still happen with the current kernel?