Bug 201163 - Anaconda doesn't detect monitor on dual-head system
Summary: Anaconda doesn't detect monitor on dual-head system
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server   
(Show other bugs)
Version: rawhide
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Dave Airlie
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-08-03 10:23 UTC by G.Wolfe Woodbury
Modified: 2018-04-11 12:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-12 12:20:36 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description G.Wolfe Woodbury 2006-08-03 10:23:40 UTC
Description of problem:
Anaconda finds and uses the active (first) video card on my system,
but does not properly detect the monitor type.  The installer display
is correct, but after firstboot, the lack of a proper monitor section
in the xorg.conf file makes for real problems.  This may actually
apply to a component in the xorg-x11 programs.

Version-Release number of selected component (if applicable):

How reproducible:
this has been going on for a few days now, three installs and
three failures.

Steps to Reproduce:
1. install rawhide of 2006-08-02
Actual results:
no monitor is detected or configured

Expected results:
monitor should be detected and configured properly

Additional info:

Celeron (Coppermine) @600MHz  256MB RAM   MSI-6382 mobo
Trident Cyberblade/i1 and ATI Radeon (Mach64) video cards
VIA Chipsets  etc....

Comment 1 Dave Airlie 2007-07-31 22:29:10 UTC
can you attach the /var/log/Xorg.0.log file please from when the machine boots?
you may need to use runlevel 3.

Comment 2 Matěj Cepl 2007-09-12 00:38:11 UTC
Since this bugzilla report was filed, there have been several major updates,
which may have resolved this issue. Users who have experienced this problem are
encouraged to upgrade their system to the latest version of their distribution

Please, if you experience this problem on the up-to-date system, let us now in
the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as

Comment 3 Matěj Cepl 2007-10-12 12:20:36 UTC
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional


Note You need to log in before you can comment on or make changes to this bug.