display is blurry and too tall at 1400 x 1050

[Matt]

Binary package hint: xserver-xorg-video-intel

I tested the monitor at 1400 x 1050 on another machine and the display looks crisp and beautiful.

When I connect it to my toshiba laptop with the following video card:

00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)

1400 x 1050 is blurry and too tall. This is the monitor's preferred resolution.

I have no idea if this is a problem with my hardware, and I have not installed Windows on it to confirm that it may be a driver issue, but I wanted to post this bug here just in case I can do anything to help.

I am using a plain vanilla xorg.conf file with DCC for everything and no custom modelines. The modesetting driver seems to find the resolutions perfectly but they just don't look good when >= 1280 x 1024. I have also tried specifying a modeline for 1400 x 1050 at 60hz and also tried setting the hsync and vsync ranges explicitly, but these settings changes change nothing.

The display is a samsung syncmaster 203b.

The lower resolutions, in particular 1024 x 768 and 1152 x 864, look beautiful. I know the monitor is not broken and the problems seem to involve certain resolutions only. I recently used this same laptop with another large monitor at a high resolution and it worked fine.

Please let me know if there is anything I can do to help provide additional information for this bug.

[Matt (mmmurf)]

Oops, the title should say 1400 x 1050

[Siegfried Gevatter (rainct)]

@ Matt: I corrected the title. You can change it clicking on "Edit description/tags" on the "Actions" panel at left.

[Bryce Harrington (bryce)]

Is this still and issue in gutsy-beta?

[Matt (mmmurf)]

I have not yet tested it. I can test it with a live CD if you think that
would work...
-Matt

On 9/29/07, Bryce Harrington <email address hidden> wrote:
>
> Is this still and issue in gutsy-beta?
>
> --
> display is blurry and too tall at 1400 x 1050
> https://bugs.launchpad.net/bugs/125128
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Bryce Harrington (bryce)]

Hi Matt, yes it would be worth a try. Note that Gutsy-final is released, so you should test against that.

[Dragonheart (heiko-braun)]

I have this problem as well.
Same Monitor (samsung syncmaster 203b) and Ubuntu Gutsy

[Martin Skogevall (martin-skogevall)]

Same thing here. Gutsy installed.

I have a Dell Latitude D430 with intel-graphics and a Samsung SyncMaster 203B.
DVI works like a charm, but if connected through VGA the image gets too tall for the display.

The DPI-values seems to be bad also. With DVI I get very large fonts, if I restart with VGA the fonts are really small. I use Arial 8 as my font.

[Manfred Haelters (manfred-haelters)]

Created an attachment (id=13807)
My xorg.conf file - driver i810 works fine - driver intel does not work

I have a Thinkpad X60 Tablet edition that I use with an external TFT Samsung Syncmaster 203B screen. Since my Thinkpad only has a VGA external adapter, I can not test with DVI. (see below for more data)

If I attach the external screen on a normal xorg.conf file, the external screen does not show the normal resolution: the image is shifted to the right and the bottom 26 lines are not shown. On different fora, I've found that other people are also confronted with this problem:

A solution I found on the ubuntuforums was (http://ubuntuforums.org/showthread.php?p=3318820#post3318820)
Key ingredients:

    * i810 driver (instead if intel)
    * 915resolution patching for ALL depths (8, 16, 32)
    * VertRefresh 60.0 (exact figure)
    * Modeline "1400x1050" 121.8 1400 1488 1632 1864 1050 1053 1057 1089

However, the i810 does not allow me to use the XRandR possibilities, making roaming with my laptop very difficult.

If I use the xorg (as attached), I get the below XRandR output. There it does not detect the correct resolution of my external TFT screen. When playing a bit with the settings in xorg.conf and 915resolution, I can also get another resolution in XRandR: 1680x1050. When I try to put the external screen into 1680x1050 with xrandr:

xrandr --output VGA --mode 1680x1050

the OSD of the tft panel says that it is doing 1400x1050 at 65.3kHz, 60Hz NN...

If you need more information, or want me to test a newer driver, please tell me what to provide/test. While doing this, please note that it is the first time I do a bug report !

Thanks

Some more data:
----------------

lspci:
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)

Internal screen:
The Internal TFT screen has a native resolution of 1400x1050

External screen:
203B with native resolution of 1400x1050.

Default XRandr output:
Screen 0: minimum 320 x 200, current 1400 x 1050, maximum 1600 x 1600
VGA connected 1280x960+0+0 (normal left inverted right) 0mm x 0mm
   1600x1200 60.0
   1280x960 60.0*
LVDS connected 1400x1050+0+0 (normal left inverted right) 0mm x 0mm
   1400x1050 50.0*+ 85.3 74.8 70.0 60.0
   1280x1024 85.0 75.0 60.0
   1280x960 85.0 60.0
   1280x800 60.0
   1152x864 85.1 75.0
   1280x768 60.0
   1152x768 54.8
   1024x768 85.0 75.0 70.1 60.0
   832x624 74.6
   800x600 85.1 72.2 75.0 60.3 56.2
   640x480 85.0 72.8 75.0 59.9
   720x400 85.0
   640x400 85.1
   640x350 85.1
TV disconnected (normal left inverted right)

[Manfred Haelters (manfred-haelters)]

Created an attachment (id=13808)
A photo showing the problem - Taken with live Ubuntu 7.10

To clearly show the problem I've made a photo of the external screen when run with a standard xorg.conf (as provided by ubuntu 7.10). Here you can see clearly how the screen is shifted to the right and that the bottom panel is not longer visible due to the missing 26 bottom lines.

Please note that on the photo you can also see the XRandR information and the OSD showing that the signals are not correct (neither the resolution - which it does not even detect, as the refresh rate)

I will also upload a photo of the internal screen so that you can compare.

Lastly I will also upload the Xorg.log.0 as taken from the live cd (used to take the screenshots).

[Manfred Haelters (manfred-haelters)]

Created an attachment (id=13809)
The normal output expected - and shown on the internal screen

see previous comment for explanation

[Manfred Haelters (manfred-haelters)]

Created an attachment (id=13810)
The log file that goes with the above two screenshots

[Manfred Haelters (manfred-haelters)]

I have the same problem with the 203B on a Thinkpad X60 Tablet. This laptop only has a VGA output and no DVI. There is most probably a problem with the intel driver because the I810 driver is working. The latter is working with the following changes in my xorg.conf file:

Section "Monitor"
        Identifier "SyncMaster"
        DisplaySize 408 300
        HorizSync 30.0 - 81.0
        VertRefresh 60.0
        Option "DDC" "false"
        Modeline "1400x1050" 121.8 1400 1488 1632 1864 1050 1053 1057 1089
        Option "DPMS"
EndSection

Section "Screen"
        Identifier "Default Screen"
        Device "Intel Controller 0"
        Monitor "SyncMaster"
        DefaultDepth 24
        SubSection "Display"
                Depth 8
                Modes "1400x1050" "1280x1024"
        EndSubSection
        SubSection "Display"
                Depth 16
                Modes "1400x1050" "1280x1024"
        EndSubSection
        SubSection "Display"
                Depth 24
                Modes "1400x1050" "1280x1024"
        EndSubSection
EndSection

However, this solution is not optimal, since XRandR is not usable with the i810 driver with multiple screens (at least I don't know how).

Will this bug be forwarded to the developers of the intel driver or do we (I) have to to that ?

[Hong-liu (hong-liu)]

Would you please try a newer driver?

It seems the problem is our driver can't find a close clock for your 1400x1050@60Hz mode.
From your photo, the VertRefresh is 61.7KHz, and horizSync is only 57Hz. The closest clock (1864x1089*57 ~= 115MHz)we find is too far away from your desired mode (121.75MHz).
This problem was solved in a newer driver.

Thanks,
Hong

[Michael Fu (michael-fu-intel)]

see bug# 13856 comment# 4...

[Manfred Haelters (manfred-haelters)]

Using the latest version from git worked for me. Thanks for you time ! I will post this information on the ubuntuforums.

[Manfred Haelters (manfred-haelters)]

I've got a response to my bug report (http://bugs.freedesktop.org/show_bug.cgi?id=14148). The version from git give a solution to the problems. Here is how I installed it:

http://ubuntuforums.org/showthread.php?p=4180275#post4180275

It would be a good idea to use a more recent intel driver for Hardy, since many people will be happy (or at the least one: me)

[Bryce Harrington (bryce)]

Great news. Today we've uploaded the latest version of -intel, 2.2.0.90, so I'm assuming that fixes this. If not, please reopen.