Wrong resolution in GDM when using external monitor connected to laptop - Intel chipset

[Louis Nichols]

I have an HP laptop, with an external monitor connected to RGB. The graphics is Intel mobile. I will post some relevant files after this.

When I boot, xsplash treats the external monitor correctly, and the boot screen is quite beautiful at 1650x1080 resolution.

But right before gdm starts, the same boot screen suddenly turns to I think 1280x800 on the external monitor, after which gdm is displayed the same way.

As a side note, I used to have this problem also in Kubuntu i686, before installing Ubuntu. However, the problem was not there a while ago, when using Karmic. I don't remember exactly if it started happening once I started using Lucid.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: libxrandr2 2:1.3.0-3
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
Architecture: amd64
Date: Sun May 2 00:49:02 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: libxrandr

[Louis Nichols (lucian-iuga-gmail)]

OK. I have found a workaround to this. I am attaching the changed /etc/gdm/Init/Default which does the trick for me (I added line 14). Note that I shut down LVDS because I keep the lid of the laptop shut. It may be different for others.

So, this solution is very specific and this remains a bug imho. Although, I am not sure it should still be allocated to xrandr or to gdm.

[Louis Nichols (lucian-iuga-gmail)]

OK. I want to nuance on my latest.

While it is true that I get gdm screen as it should, the xsplash still looks funky for a split second right before gdm. I hadn't noticed it before, because I tested by simply re-starting gdm.

So what happens to xsplash... it is not the resolution that changes, but the placement on screen. I simply get just a portion of the splash image, as if a 1680x1050 image is displayed on a 1280x800 screen, with the top left corner where it should. Unfortunately, I can not do a screenshot, but if the description is not enough and it is needed, I can take a picture of it.

So it may in fact be a issue with xsplash, in the end. :) I dunno.

There are probably a lot of details for a bug that is very low on anyone's priority list, but well... there you have it! :)

[Randall Smith (randall-tnr)]

In your modified /etc/gdm/Init/Default, try changing

/usr/bin/xrandr --output VGA1 --mode 1680x1050 --output LVDS1 --off

to this:

/usr/bin/xrandr --output VGA1 --auto --output LVDS1 --off

A little less specific

I wonder what will happen now when the VGA is not attached?

-Randall

[Adam Dingle (adam-yorba)]

Louis, you said that this bug is "very low on anyone's priority list" but it affects me too and is a major nuisance. At home, I always boot up my laptop with the lid closed and an external monitor on. GDM fails to set the correct resolution, and the resolution is still wrong after I log in: I have to run xrandr to correct it. I believe that GDM (or the X server?) is failing to realize that the lid is closed and that the laptop display should be ignored (at least, that's the behavior I would like). Instead, GDM (or the X server) is choosing the highest resolution common to both the laptop display and the external monitor

[Timo Aaltonen (tjaalton)]

Do you have the same bug with 11.04 or newer? Testing with a livecd should be sufficient.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

[Fabián Rodríguez (magicfab)]

Same problem here, I am using Ubuntu 11.04 64 bit with an Intel chipset.

$ sudo lspci -s 00:02.0 -kvnn
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1652]
 Flags: bus master, fast devsel, latency 0, IRQ 44
 Memory at ddc00000 (64-bit, non-prefetchable) [size=4M]
 Memory at c0000000 (64-bit, prefetchable) [size=256M]
 I/O ports at e000 [size=64]
 Expansion ROM at <unassigned> [disabled]
 Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
 Capabilities: [d0] Power Management version 2
 Capabilities: [a4] PCI Advanced Features
 Kernel driver in use: i915
 Kernel modules: i915

[Fabián Rodríguez (magicfab)]

I've also tested this with the latest 11.10 nightly - same problem. The desktop picture I am attaching is immediately after booting from a live USB version, the GDM screen is immediatly afte logout from that live session.

[mstfa cmly (mstfacmly)]

New data on the issue:

It would appear this only occurs when the system is started up with an external monitor attached. Booting or rebooting without the external monitor has the X server properly detect the displays and allows for a hassle-free experience.

Upstream would need to be informed of this detection issue.

[komputes (komputes)]

Hello Fabián,

The hardware which you are reporting an issue with is not the same as that of the original poster:
Bug hardware: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
Your hardware: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)

As well, please note that this bug concerns 10.04 whereas you are reporting an issue with 11.04. Please open a new bug from the affected hardware, using the following command:

$ ubuntu-bug xserver-xorg-video-intel

Thank you.

[Fabián Rodríguez (magicfab)]

Thanks David, I've filed bug #874241 although I believe it's the same issue (same driver).

Please don't close *this* bug as I'll be testing 10.04 LTS 64 bit which I consider going back to.

[Bryce Harrington (bryce)]

Fabian, your bug is probably handled best by filing a new bug report. The symptoms described in this bug report are fairly generic and can be caused by a variety of underlying issues.

Re-closing as expired.