Red Hat Bugzilla – Bug 511037
screen is flickering on tty
Last modified: 2010-12-05 01:43:34 EST
Description of problem:
I have an old 19" CRT. When I boot to a tty (eg. in runlevel 3) the screen starts flickering after a few seconds. After a few minutes it is so hard flickering that I have to turn the monitor off. The control panel of my monitor says that the used resolution is 1280x1024@85Hz. 85 Hz is the maximum refresh rate in this resolution of my monitor.
I think this starts with kernel 2.6.30 and the disabled nomodeset option (which I've used before). I'm also not able to control the resolution with the vga option in grub.conf.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot to a tty
screen is flickering
screen should not be flickering and maybe not using the maximum refresh rate of an resolution (AFAIK CRTs should not be used with the maximum refresh rate)
1. cat /proc/cmdline
ro root=LABEL=live_rawhide rhgb quiet
2. 01:00.0 VGA compatible controller: ATI Technologies Inc R420 JI [Radeon X800PRO] (prog-if 00 [VGA controller])
I don't think there's any way to tell the modesetting code what resolution/refresh rate to use?
This behaviour is sometimes better and sometimes worse. ATM also X is flickering after a few seconds.
I should add that I have two different monitors (a 17" and a 19" CRT) connected to my graphics card. And that seems to be the problem. If I remove the 17" all is working fine. With it being connected it seems that the frequencies are mixed up in some way. My primary 19" shows plymouth only partly on the top left side of the screen (seems to be 1024x768 if I have to guess).
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. 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 '12'.
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 12'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 12 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:
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.