Bug 38426 - Disconnected device seen as connected resulting in wrong display resolution selected
Summary: Disconnected device seen as connected resulting in wrong display resolution s...
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-17 18:59 UTC by Jeff B.
Modified: 2018-06-12 18:42 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log with xrandr --prop output appended to it. (26.20 KB, application/octet-stream)
2011-06-17 18:59 UTC, Jeff B.
no flags Details

Description Jeff B. 2011-06-17 18:59:47 UTC
Created attachment 48122 [details]
Xorg.0.log with  xrandr --prop output appended to it.

Hi,

I just installed the latest version of Slackware (13.37) and my 1600x900 monitor got a 1024x768 screen stuck in it.  This all worked fine in the previous version of Slackware.  After poking around I believe the problem is with the new version of Xorg's init which comes with the new Slackware.  The problem is not hardware since I haven't changed the hardware, and the problem is not my desktop software since I see the same thing in KDE and XFCE.

Here are the version numbers:

    X.Org X Server 1.9.5
    Release Date: 2011-03-17
    X Protocol Version 11, Revision 0
    Build Operating System: Slackware 13.37 Slackware Linux Project
    Current Operating System:
        Linux atomik 2.6.37.6-smp #1 SMP Sat Apr 9 14:01:14 CDT 2011 i686
    Kernel command line: BOOT_IMAGE=Smaller-Linux ro root=801 vt.default_utf8=0
    Build Date: 18 March 2011  12:08:03AM


Here is a condensation of what appears in Xorg.0.org. (Full Xorg.0.log and xrandr --prop output attached.)  It is clear from the /var/log/Xorg.0.log file that Xorg recognizes that VGA1 has several modes which are recognized, the 1600x900 being the desired one:

        [  1694.617] (II) intel(0): Printing probed modes for output VGA1
        [  1694.617] (II) intel(0): Modeline "1600x900"x60.0  ...
        [  1694.617] (II) intel(0): Modeline "1280x1024"x60.0 ...
        [  1694.617] (II) intel(0): Modeline "1152x864"x75.0  ...
        [  1694.617] (II) intel(0): Modeline "1024x768"x75.1  ...
        [  1694.617] (II) intel(0): Modeline "1024x768"x60.0  ...
        ...

and that the output (no monitor, not even a connector) on LVDS1 also has several modes

        [  1694.548] (II) intel(0): Printing probed modes for output LVDS1
        [  1694.548] (II) intel(0): Modeline "1280x800"x58.1  ...
        [  1694.548] (II) intel(0): Modeline "1024x768"x60.0  ...
        ...

Xorg.log then goes on to say:

        [  1694.617] (II) intel(0): Output LVDS1 connected
        [  1694.617] (II) intel(0): Output VGA1 connected

which makes no sense since LVDS1 output is physically not connected.  I have seen other Xorg.0.log output which recognizes that circuitry is there but is not connected, so why does this new version of Xorg think LVDS1 is connected?

So, given that Xorg (falsely) thinks that LVDS1 is connected it then apparently tries to use the highest resolution mode it has in common with the two outputs (Using fuzzy aspect match for initial modes) namely "1024x768"x60.0.

        [  1694.617] (II) intel(0): Using fuzzy aspect match for initial modes
        [  1694.617] (II) intel(0): Output LVDS1 using initial mode 1024x768
        [  1694.617] (II) intel(0): Output VGA1 using initial mode 1024x768

which is wrong.

How can I work around this automatically short of going back to an older version of Xorg?


Thanks in advance,
Jeff B.
Comment 1 Adam Jackson 2018-06-12 18:42:55 UTC
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.