Red Hat Bugzilla – Bug 599274
Xorg -configure generates xorg.conf which uses VESA driver
Last modified: 2018-04-11 04:39:25 EDT
Description of problem:
The generated xorg.conf specifies VESA driver, however if I run X without any config, it correctly loads the driver for the ati radeon HD3450 card. It is now impossible to get a config that matches the "default" as if you were to run without any xorg.conf at all.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Xorg -configure
uses radeon or whatever is used for radeon in F13 (not sure at the moment)
(In reply to comment #0)
> Description of problem:
> The generated xorg.conf specifies VESA driver, however if I run X without any
> config, it correctly loads the driver for the ati radeon HD3450 card. It is
> now impossible to get a config that matches the "default" as if you were to run
> without any xorg.conf at all.
* * X server log file (/var/log/Xorg.*.log), and
* output of the dmesg command,
(from running both with and without xorg.conf, which please attach as well) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Created attachment 422608 [details]
xorg.conf generated by Xorg -configure
Created attachment 422609 [details]
xorg.log when starting WITH the generated xorg.conf
Created attachment 422610 [details]
dmesg output after starting x WITH generated xorg.conf
Created attachment 422611 [details]
xorg.log when starting WITHOUT any xorg.conf
Created attachment 422614 [details]
dmesg output after starting x WITHOUT any xorg.conf
i believe the attached files are as requested.
i should note: the attached "with xorg.conf" files (including xorg.conf) were generated after booting to runlevel 3 with "nomodeset" on the command line, however i did verify the exact same results either way (the generated xorg.conf is byte-for-byte identical when booting with or without KMS).
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. 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 '13'.
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 13'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 13 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:
This bug got no love. I suggest a new "resolution":