Created attachment 20340 [details]
Apple Power Mac G4 MDD (PowerMac3,6) - see http://support.apple.com/kb/SP63 - mine is the Dual 1 GHz model.
Gentoo Linux 2008.0 (started about 1 year ago with 2007.1)
Kernel 2.6.27 (started with 2.6.22)
X.org 7.4 (started with 7.2)
radeon driver: x11-drivers/xf86-video-ati-6.9.0 (started with 6.7.197, 6.8.0)
When there was no problem:
The Radeon 9000 Pro AGP 4x has a DVI output connector and an ADC (Apple Display Connector). It originally shipped with a DVI-to-VGA adaptor.
The output was okay with this DVI-to-VGA adaptor and a CRT monitor.
I then bought a TFT monitor -
I connected it directly via DVI.
I wasn't able to get a screen upon initialization without red flicker since.
*) red flickering after first X initialization.
*) red flickering is gone when changing the screen resoltion.
e.g. "xrandr -s 1280x1024" and then "xrandr -s 1680x1050" (panel resolution) fixes the red flickering; same with Ctrl-Alt-+ and Crtl-Alt--
*) I today discovered that setting Option "ReducedBlanking" in
the /etc/X11/xorg.conf Monitor Section resolved the red flickering on first
*) the red flickering _always_ reappears after console switching (when
returning to the X console).
Others with the same problem:
Created attachment 20341 [details]
Correction to the previous statement:
Option "ReducedBlanking" doesn't change anything. I had forgotten that I had put the lines "xrandr -s 1280x1024 ; xrandr -s 1680x1050" into my /usr/kde/3.5/share/config/kdm/Xsetup which then (quite quickly) changed resoultion and thus removed the red flickering from the screen.
Sorry for the false statement.
BTW, Giuliano told me that the older radeon driver 6.3.3 works on ppc with DVI, so I will try that one as the next step.
Okay, it was off course x11-drivers/xf86-video-ati-6.6.3 (not 6.3.3). But anyway, it fails compilation right at the start with x11-base/xorg-server-1.5.2 (X.org 7.4) due to changed structs in atibus.c, atichip.c, and some more...
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.