Description of problem:
I have my laptop connected to an external monitor. Instead of running at
resolution I configured X for, the monitor uses a lower resolution, meaning that
I have to pan around the screen. The laptop is a Sager NP5660, the monitor is a
ViewSonic P810. The native resolution of the laptop's display is 1600x1200,
which is what I selected in X's display configuration.
There's a convoluted workaround which might provide a clue as to the problem.
If I completely disconnect the monitor from the system (apparently it can still
be detected even if it's powered off?), reboot and run the X display
configuration, and restart X, _then_ connect the monitor, the monitor uses the
This problem did not happen in RH 8.0
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start up the system with the external monitor connected
Monitor uses lower resolution.
Monitor should use the resolution I configured.
I'll attach the output of xdpyinfo, in case it's helpful. This bug appears in
the 9.0 final release.
Created attachment 90740 [details]
This is the output from xdpyinfo _after_ executing the aforementioned
workaround. I'll check whether it's any different when the monitor is at the
Nope, no change in xdpyinfo output after I rebooted (and the monitor is now at
the lower resolution).
In the above workaround, I should note that re-running the display configuration
on each bootup isn't necessary. I can work around the problem by just booting
up with the monitor physically disconnected. Also, I tried to do the same
workaround with just stopping and starting the X server instead of rebooting,
but it doesn't work. This is driving me nuts, so I'll be happy to provide any
logs or files that might help narrow this down.
Can you attach your XFree Config files for both the laptop and the external
monitor and your XFree log file? Maybe comparing both of them somehow might
come up with an answer.
There is no "9.0" release, and there won't be. The release is:
Red Hat Linux 9
Not "Red Hat Linux 9.0"
Created attachment 90754 [details]
I'm not sure what you meant about XF86Config files for the laptop and the
monitor. I only have a single XF86Config, and this is it.
Created attachment 90755 [details]
XFree86 log when I start with the monitor disconnected
This is the XFree86 log when I start up with the monitor disconnected (and upon
reconnecting it, it's at the correct resolution).
Created attachment 90756 [details]
XFree86 log when I start with the monitor attached
This is the XFree86 log file when I start with the monitor connected and it
uses the incorrect lower resolution.
I thought you were reconfiguring your XFree Config file when trying to use the
monitor, is why I asked for both. Or at least changing it when trying to use
it. If you are changing it, then yes please attach the changed one as well.
Otherwise, what you have so far should be enough to start on, thanks.
Have you looked at the 'radeon' manpage and tried some of the options
The greater problem at least in my opinion, is that our configuration tool
is really created for configuring a machine with one single display, and
not for multihead configurations. As such, any user using multihead must
configure it themselves, and when doing so, if something doesn't work right,
they assume it is a bug and file a bug report. Often, it is not easy to
even determine if the problem being reported is a real bug in XFree86, a
bug in the config tool, or just end user misunderstanding on how to manually
configure the overly complex configuration themselves.
Not having this kind of hardware, makes it nontrivial for me to properly
assess the problem to determine on my own if it is a bug, or just a
misconfiguration or a shortcoming of our config tool.
I also suggest posting your problem on the firstname.lastname@example.org mailing list,
as that will provide feedback from many other users and developers with and
without this hardware, some of whom may have experienced the same problem
and perhaps found a solution already.
If you find an answer to the problem please update the bug report so I
know where it stands.
I made some progress here (thanks for the man page pointer). If I either set
CloneMode to 0, or set it to 2 and enable DDCMode, things work pretty much as
expected. I'm trying to figure out what the real difference is between these
sorry, CloneDisplay, not CloneMode.
This issue should be fixed in the current xorg-x11 6.8.1 release
which is present in our Fedora Development code base, known as
If this issue turns out to still be reproduceable in the latest
version of Fedora Core, please file 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.