Red Hat Bugzilla – Bug 472773
Wrong video mode selected when started without xorg.conf
Last modified: 2009-11-28 04:15:40 EST
Created attachment 324483 [details]
log from the attempt to run mga driver
I run "startx" and the mode selected has very low resolution and the picture was shifted to the left and to the top, so that those borders contained lines with high intensity of the light.
The console uses fb, set to 1152 x 864, 80 Hz, if that is relevant.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. 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 '10'.
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 10'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 10 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:
Probably a duplicate of bug 446726. It's a sad thing that we can't keep Matrox support on the level of Intel, ATI and NVIDIA :-(
*** This bug has been marked as a duplicate of bug 446726 ***