Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 162733 - Resolution of external video from laptop fixed at 800x600
Resolution of external video from laptop fixed at 800x600
Product: Fedora
Classification: Fedora
Component: xorg-x11 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: X/OpenGL Maintenance List
David Lawrence
: 163312 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2005-07-08 00:58 EDT by Graham freeman
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-14 04:56:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
xorg.conf (3.67 KB, text/plain)
2005-07-08 01:36 EDT, Graham freeman
no flags Details
Log file from X start-up (50.75 KB, text/plain)
2005-07-08 01:37 EDT, Graham freeman
no flags Details

  None (edit)
Description Graham freeman 2005-07-08 00:58:30 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913

Description of problem:
I need to use my laptop with external data projection facilities.  Under an old RedHat system with XFree86, I had no trouble, even if the screen resolution was 1600x1200.  With FC2 and FC4, the resolution I am using on the local screen is 1280x1024.  Only an 800x600 piece of the area gets projected through the video connection.

I have tried this in 3 venues.  With a small portable data projector, I have no problem; the full 1280x1024 is projected.  In the other venues (large halls with fixed facilities), I only get the 800x600 displayed.

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

How reproducible:

Steps to Reproduce:
1. Connect and turn on the data projector.
2. Boot the computer

Actual Results:  800x600 portion of the screen display is projected.  If I move the mouse, the displayed area always tracks the cursor.

Expected Results:  The projected screen should match the screen on the local laptop.

Additional info:

The laptop I am using is an IBM ThinkPad.
Comment 1 Graham freeman 2005-07-08 01:36:35 EDT
Created attachment 116505 [details]
Comment 2 Graham freeman 2005-07-08 01:37:43 EDT
Created attachment 116506 [details]
Log file from X start-up
Comment 3 Walter Justen 2005-08-26 06:07:56 EDT
*** Bug 163312 has been marked as a duplicate of this bug. ***
Comment 4 Mike A. Harris 2005-08-30 06:08:01 EDT
Please report this issue to X.Org developers by filing a bug report in
the X.Org bugzilla located at http://bugs.freedesktop.org in the "xorg"

Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.

Setting status to "NEEDINFO_REPORTER", awaiting X.Org bug URL for
Comment 5 Graham freeman 2005-09-01 02:34:19 EDT
I am sorry for the duplicate bug report (163312).  I did not keep a record of
the bug number.
In that report, I indicated that I found a solution to the problem, by
hand-editing the X configuration file:

Section "Device"
	Identifier  "Card0"
#	Driver      "ati"
	Driver      "radeon"
	Option      "MonitorLayout"  "LVDS, SVGA"
	VendorName  "ATI Technologies Inc"
	BoardName   "Radeon RV200 LX [Mobility FireGL 7800 M7]"
	BusID       "PCI:1:0:0"

Given that it is not a problem with Xorg itself but rather with the way X is set
up in Fedora, I would have thought that reporting it to Xorg would not be
Comment 6 Mike A. Harris 2005-09-14 04:56:21 EDT
It isn't a problem with the way X gets configured, it is a problem in that
the driver does not autodetect the hardware properly and make it
automatically do what you expect.  If the driver can't autodetect things
and automatically work without configuration, then the configuration tool
can't autodetect it either, and you have to specify the configuration
manually no matter what.

So this is a driver problem, and must be filed at X.org.

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