Bug 138500 - Radeon mobility 9600 dualhead misconfigured on Acer Travelmate 8000 laptop
Radeon mobility 9600 dualhead misconfigured on Acer Travelmate 8000 laptop
Status: CLOSED CANTFIX
Product: Fedora
Classification: Fedora
Component: system-config-display (Show other bugs)
3
i686 Linux
medium Severity low
: ---
: ---
Assigned To: Adam Jackson
:
Depends On:
Blocks: FC6Target
  Show dependency treegraph
 
Reported: 2004-11-09 12:58 EST by Philip Van Hoof
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-10-30 17:17:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Philip Van Hoof 2004-11-09 12:58:38 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20041020 Epiphany/1.4.4

Description of problem:
I had to add these options to the primary Device-section of my
xorg.conf file manually to get the monitor connected to the analog
port of my laptop detected. I assume that "LVDS, LVDS" is needed to
get the monitor working if it's attached on the digital port.

Option	"MonitorLayout" "LVDS,CRT"
Option	"UseFBDev"  "false"


Version-Release number of selected component (if applicable):
system-config-display-1.0.23-1

How reproducible:
Always

Steps to Reproduce:
1. Select the dual-head tab.
2. Select an Analog monitor (they are in the list indeed)
3. Restart X

Actual Results:  The xorg.conf file is almost correct. However, it
didn't added the options needed to get the second monitor working.

Expected Results:  The monitor, connected to the analog connector of
my laptop, should have worked. 

Additional info:

A working xorg.conf file:

http://www.freax.be/files/acer_travelmate/xorg.conf.fc3
Comment 1 Adam Jackson 2006-03-03 10:32:02 EST
Mass update: move dual head bugs from FC5 to FC6, no way they can get fixed
before FC5 release at this point.
Comment 2 Matthew Miller 2006-07-10 16:58:16 EDT
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!
Comment 3 John Thacker 2006-10-30 17:17:42 EST
Closing per lack of response to previous request for information.
This bug was originally filed against a much earlier version of Fedora
Core, and significant changes have taken place since the last version
for which this bug is confirmed.

Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only.  Please install a still supported version and retest.  If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version.  Otherwise, if this a security issue, please change the
product to Fedora Legacy.  Thanks, and we are sorry that we did not
get to this bug earlier.

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