[i945] Regression: wrong GDM resolution when using external display on i945

[Bálint Magyar]

Binary package hint: xserver-xorg-video-intel

Ubuntu Intrepid beta upgraded from 8.04.1, all updates as of this post, running on an Intel GMA-950. Option "NoDRI" because of bug #277709, but it doesn't make a difference. Stock "empty" xorg.conf apart from that.

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)

On Hardy when I had an external display connected through VGA on boot, both GDM and GNOME resolution was automatically set to the native resolution of the TFT monitor. On Intrepid it's always 1024x768. After login the resolution is set correctly.

[John Leach (johnleach)]

This happens for me too on my Lenovo Thinkpad R61 (with an i965 though). With a second monitor just connected, the resolution of the gdm login screen on the internal screen is 1024x768, rather than 1280x800 as it should be (the external monitor I have connected is not widescreen, but it does go up and to and beyond 1280x1024.

This is with the latest updates for Intrepid and a completely standard basic xorg.conf (from running sudo dpkg-reconfigure -phigh xserver-xorg)

00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)

[slinger (slinger-to)]

Same thing for me on my Thinkpad X60 with Intel Corporation Mobile 945GM/GMS. Worked on Hardy without any Problems!

[kidrock (gabriele-1983)]

I also have the same problem after upgrading to Intrepid, with a :

00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02)

My monitor needs 1024x768 resolution but gdm start with a different resoluzion but when I start gnome the resolution is switched to 1024x768.

I also had the same problem with Hardy, but I could solve restarting the x server with a reboot or also with ctrl+alt+backspace.

[Tyler Rusk (tdrusk)]

I found a workaround/solution.

Install lxrandr. Click "Show the same screen on both Laptop LCD and external monitor.

Works great for me :).

[mbsullivan (mbsullivan)]

This could be fixed by adding some lines to xorg.conf, but because we are trying to move away from manually editing the xorg.conf file, another way should be preferred. One way is to use xrandr (not quite the same as lxrandr) to set the external monitor resolution upon gdm startup.

In order to do this, edit the /etc/gdm/Init/Default file (a script run @ the start of gdm), and insert a line similar to the following:

xrandr --output VGA --auto

Where "VGA" is the output name of your external monitor (can be found by looking at the output of "xrandr -q").

For lazy people, attached is a patch file that inserts the appropriate line into the file. To apply it:

sudo patch -d /etc/gdm/Init/ < gdm_init_patch.diff

Mike

[Bryce Harrington (bryce)]

[This is an automatic notice.]

We'd like to forward your bug upstream, however upstream requires
that you first test it against their newer driver code.

To save you the effort of building the driver from source, we've built
packages for the driver and its new dependencies.

So you have a couple options:

 1. Download and test .debs for intrepid, from:
     https://edge.launchpad.net/~intel-gfx-testing/+archive

 -or-

 2. Download and test the Jaunty alpha-2 (or newer) Live CD,
     (which includes a beta of the new xserver 1.6 as well).
     See http://cdimage.ubuntu.com/releases/9.04/ for ISOs

Thanks ahead of time! You can simply reply to this email to report your
findings.

P.S., if you wish to forward your bug upstream yourself, please follow
these directions to do so:
  http://intellinuxgraphics.org/how_to_report_bug.html

[Bálint Magyar (balintm)]

Tried with packages from the above-mentioned intel-gfx-testing PPA: the reported problem is still there.

[Bryce Harrington (bryce)]

Thanks for testing; this should go upstream. Setting to Triaged for now.

[Bryce Harrington (bryce)]

Can you let us know if this issue still occurs with the Jaunty release? If so, please also see if the 2.7.0 driver resolves it:
  https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates/

[Pixilarion (pixilarion)]

The solution provided by mbsullivan worked perfectly for me on Intrepid.

When I did an upgrade last week to Jaunty, the problem was still there. However, I reverted back to Intrepid, so I can't test the solution in Jaunty. I'll report back when I finally move to Jaunty.

[Bryce Harrington (bryce)]

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.