[Intel-gfx] i915 KMS wrong resolution later on boot

[Peter Clifton]

On Fri, 2010-01-08 at 11:15 +0100, Carlos R. Mafra wrote:
> I have a laptop with 1280x800 and an external monitor with
> 1280x1024, and the end result after boot and entering X is
> that I get both at the wrong resolution of 1024x768.
> (after running xrandr I can fix the resolution)
> 
> The laptop has this card
> 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
> 
> and my kernel has
> 
> CONFIG_DRM_I915=y
> CONFIG_DRM_I915_KMS=y
> 
> On 2.6.33-rc3+ (and previous kernels too) the KMS gets the
> correct resolution in the beginning of the boot and later
> sets it wrong. Grepping 'drm' from the dmesg shows me this:
> 
> [    1.988283] calling  drm_core_init+0x0/0x137 @ 1
> [    1.988379] [drm] Initialized drm 1.1.0 20060810
> [    1.988429] initcall drm_core_init+0x0/0x137 returned 0 after 95 usecs
> [    1.995913] [drm] set up 7M of stolen space
> [    2.022311] [drm] initialized overlay support
> [    2.554262] [drm] TV-12: set mode NTSC 480i 0
> [    2.792262] [drm] DAC-6: set mode 1280x1024 28
> [    2.856261] [drm] LVDS-8: set mode 1280x800 2a
> [    3.901189] fb0: inteldrmfb frame buffer device
> [    3.903369] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
> [    9.881037] [drm] DAC-6: set mode 1024x768 2c
> [   10.272108] [drm] LVDS-8: set mode 1024x768 2d
> [   31.845095] [drm] DAC-6: set mode  2b
> 
> and see how at ~2 secs the resolutions are correct and then at
> ~10 secs (when X is starting) they are wrong. Why does this happen?
> I am using OpenSUSE 11.2 so my userspace is new.
> 
> The whole dmesg is here:
> http://www.aei.mpg.de/~crmafra/dmesg-drm.txt
> 
> (my kernel has one btrfs patch and a i915 patch to keep the
> outputs disabled after s2ram, http://lkml.org/lkml/2009/12/31/13
> but the problem happens regardless)

Could be that something in your Xorg userspace is calling xrandr to poke
the monitors into a previously recorded configuration. I believe
gnome-settings-daemon does this, for example.

You might try moving / deleting ~/.config/monitors.xml if it exists. It
doesn't any more on my box, but I'm not sure why... perhaps the data
moved somewhere else.