Bug 80460 - RFE: Support Dualhead Display Setup
Summary: RFE: Support Dualhead Display Setup
Status: CLOSED DUPLICATE of bug 74132
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-xfree86
Version: 9
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Mike McLean
: 77308 (view as bug list)
Depends On: 80522
TreeView+ depends on / blocked
Reported: 2002-12-26 20:14 UTC by Jim Rich
Modified: 2008-01-17 17:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2006-02-21 18:50:36 UTC

Attachments (Terms of Use)

Description Jim Rich 2002-12-26 20:14:00 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218

Description of problem:
Anaconda defaults dualhead display setup to unuseable configuration.

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

How reproducible:

Steps to Reproduce:
1.Install phoebe to dualhead display, using for example Matrox G450 card.

Actual Results:  Monitor 2 displays exactly the same contents as monitor 1.

Expected Results:  Anaconda should give dualhead display users the option of
configuring either giant merged display, two independent display screens, or the
current default of two identical displays.

Additional info:

SuSE defaults to two independent display screens, which is at least useable. 
Most users would prefer a giant merged display, which is the Matrox default on
Windows or Linux, i.e., two 1600x1200 displays form a merged 3200x1200 display.

Comment 1 Michael Fulbright 2002-12-27 16:28:18 UTC
This would require support for dual head in redhat-config-xfree86.

Comment 2 Brent Fox 2003-01-02 17:13:08 UTC

*** This bug has been marked as a duplicate of 74132 ***

Comment 3 Tom Coughlan 2003-02-06 22:35:06 UTC
*** Bug 77308 has been marked as a duplicate of this bug. ***

Comment 4 Red Hat Bugzilla 2006-02-21 18:50:36 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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