Red Hat Bugzilla – Bug 127629
Resolution does not change automatically when docked
Last modified: 2007-11-30 17:10:45 EST
Description of problem:
I installed FC2 on my Dell Inspiron 8500 with it undocked and had to
modify xorg.conf to allow for my 1920x1200 screen resolution as I had
to do with FC1. However, when docked the screen remains at 1920x1200
resolution. With FC1 and XFree86, the resolution switched
automatically between 1920x1200 (undocked) and 1600x1200 (docked)
depending on the docked status.
Version-Release number of selected component (if applicable):
- Fedora Core release 2 (Tettnang)
See steps below
Steps to Reproduce:
1. Install FC2 on laptop with non-standard display capability
2. modify /etc/X11/xorg.conf by adding 1920x1200 to front of Screen
3. Reboot undocked. X11 will properly display 1920x1200 on laptop LCD
4. Reboot docked. X11 will improperly display 1920x1200 on external CRT
When docked, resolution remains at 1920x1200
When docked, resolution should default back to 1600x1200
Please find my /etc/X11/xorg.conf attached.
Created attachment 101795 [details]
/etc/X11/xorg.conf file used on affected laptop
I am no X11 expert, but a similar configuration worked in XFree86.
Just FYI, my current work-around is to manually change the screen
resolution every time I login using the gnome-display-properties tool.
This is undesirable because this wasn't required when using FC1 and
This seems to be a configuration issue, but it isn't completely
clear. Please file a bug report in upstream X.org bugzilla at
http://bugs.freedesktop.org in the "xorg" component, in order
to maximize the number of potential developers aware of this
issue who may be able to investigate and/or make a suggestion.
If you paste your upstream bug URL here, we will also track the
issue in upstream bugzilla.
I will open the bug with X.org. Will post URL when it's available.
The reason why I don't believe this is a configuration issue is that
the desired behavior was acheived by simply switching to the Nvidia
I know RH cannot support Nvidia's release without source code.
There's no way of telling what it's doing to automagically adjust the
Perhaps this bug would be more appropriately filed against the nv
video driver? However, I didn't see 'nv' in the component list so
this was the best I could do.
We don't have a separate component per driver, just for the X
package as a whole.
The "nv" driver, while open source code, is mostly useless unless
you are an Nvidia employee, as it is completely obfuscated and
programs registers on the hardware by hexadecimal register number,
with hex values. The hardware documentation is also unavailable.
In order to have a bug in the "nv" driver investigated and fixed,
one needs to report the bug to X.Org directly, and hopefully
the "nv" driver maintainer or someone from Nvidia can investigate
the issue. We can then track the issue in the upstream bugzilla
once we're made aware of the URL, and consider using any bugfixes
that become available. We do not directly develop the "nv" driver
or have knowledge of Nvidia hardware operation however, so we're
reliant on Nvidia to provide bug fixes and hardware updates.
Thanks for reporting upstream.
Setting status to "UPSTREAM", and awaiting bug URL for tracking.
See included upstream bugzilla link