Screens & Graphics not setting correct resolution

I'm confirming this. displayconfig-gtk's behavior is very erratic around here - it never suceeds changing the default system resolution and at login only a part of the screen is visible, with the same pan & scroll thing.

I am experiencing exactly the same problems

I'd like to corroborate this for my Thinkpad T61p which has a 1920x1200 display.

I use the VESA driver exclusively. I find that the Screen Model titled 'LCD Panel 1920x1200' has no entry for this resolution. The maximum resolution supported is in fact 1600x1200.
This means that I need to manually edit xorg.conf and add Modelines for this resolution.

Does the Plug'n'Play monitor work for you?

Could you please append the output of the following two commands:

sudo get-edid|parse-edid

sudo ddcprobe

Thanks

Hi Sebastien.

On Wed, 2007-10-03 at 20:55 +0000, Sebastian Heinlein wrote:
> Does the Plug'n'Play monitor work for you?

If you mean choosing Plug'n'Play in the 'Choose Screen' dialog, it
doesn't work, in the sense that it doesn't allow me to select any other
resolution apart from 640x480.

> Could you please append the output of the following two commands:

Sure.

> sudo get-edid|parse-edid

root@Blackpearl:~# get-edid|parse-edid
parse-edid: parse-edid version 1.4.1
get-edid: get-edid version 1.4.1

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
        Function supported
        Call successful

        VBE version 300
        VBE string at 0x11110 "NVIDIA"

VBE/DDC service about to be called
        Report DDC capabilities

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
        Function supported
        Call successful

        Monitor and video card combination does not support DDC1
transfers
        Monitor and video card combination does not support DDC2
transfers
        0 seconds per 128 byte EDID block transfer
        Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
        Read EDID

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
        Function supported
        Call failed

The EDID data should not be trusted as the VBE call failed
Error: output block unchanged
parse-edid: IO error reading EDID

> sudo ddcprobe

root@Blackpearl:~# ddcprobe
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: G84 Board - NV_NB8P Chip Rev
memory: 14336kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 1280x1024x16
mode: 1280x1024x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
edid:
edidfail

Hmm. Interesting, so ddcprobe doesn't return 1920x1200 as a valid
resolution!!! How then do things work when I manually put in modelines
for 1920x1200 !!!

I hope this information is of help.

Thanks!!
Robin

@Rawbin: your monitor is of bad quality, since it has got a broken edid information. could you please attach your inf monitor driver or the sync ranges from the manual?

Sebastien, its actually a Thinkpad T61p laptop. That would use an LCD
Panel driver, I'm guessing. I wonder if other T61p users are
experiencing the same ?

On Thu, 2007-10-04 at 06:51 +0000, Sebastian Heinlein wrote:
> @Rawbin: your monitor is of bad quality, since it has got a broken edid
> information. could you please attach your inf monitor driver or the sync
> ranges from the manual?

I've got sync ranges for 1920x1200 from the modelines section of my
xorg.conf, would that help ?

Am attaching the file here.

Thanks for the time!

Cheers,
Robin

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder3) Wed Sep 12 14:29:35 PDT 2007

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf(5) manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "ServerLayout"
 Identifier "Default Layout"
  screen 0 "Default Screen" 0 0
 Inputdevice "Generic Keyboard"
 Inputdevice "Configured Mouse"
 Inputdevice "stylus" "SendCoreEvents"
 Inputdevice "cursor" "SendCoreEvents"
 Inputdevice "eraser" "SendCoreEvents"
 Inputdevice "Synaptics Touchpad"
EndSection

Section "Files"

 # path to defoma fonts
 Fontpath "/usr/share/fonts/X11/misc"
 Fontpath "/usr/share/fonts/X11/cyrillic"
 Fontpath "/usr/share/fonts/X11/100dpi/:unscaled"
 Fontpath "/usr/share/fonts/X11/75dpi/:unscaled"
 Fontpath "/usr/share/fonts/X11/Type1"
 Fontpath "/usr/share/fonts/X11/100dpi"
 Fontpath "/usr/share/fonts/X11/75dpi"
 Fontpath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
 Load "bitmap"
 Load "ddc"
 Load "extmod"
 Load "freetype"
 Load "int10"
 Load "vbe"
 Load "glx"
 Load "GLcore"
 Load "v4l"
EndSection

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "gb"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
 Option "Device" "/dev/input/mice"
 Option "Protocol" "ImPS/2"
 Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
 Identifier "Synaptics Touchpad"
 Driver "synaptics"
 Option "SendCoreEvents" "true"
 Option "Device" "/dev/psaux"
 Option "Protocol" "auto-dev"
 Option "HorizScrollDelta" "0"
EndSection

Section "InputDevice"
 Identifier "stylus"
 Driver "wacom"
 Option "Device" "/dev/input/wacom"
 Option "Type" "stylus"
 Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "InputDevice"
 Identifier "eraser"
 Driver "wacom"
 Option "Device" "/dev/input/wacom"
 Option "Type" "eraser"
 Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "Input...

I'll do so later today when i get back home ...

> From: <email address hidden>
> To: <email address hidden>
> Date: Wed, 3 Oct 2007 20:55:35 +0000
> Subject: [Bug 139027] Re: Screens & Graphics not setting correct resolution
>
> Does the Plug'n'Play monitor work for you?
>
> Could you please append the output of the following two commands:
>
> sudo get-edid|parse-edid
>
> sudo ddcprobe
>
> Thanks
>
> --
> Screens & Graphics not setting correct resolution
> https://bugs.launchpad.net/bugs/139027
> You received this bug notification because you are a direct subscriber
> of the bug.

_________________________________________________________________
Climb to the top of the charts!  Play Star Shuffle:  the word scramble challenge with star power.
http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_oct

I'm not quite sure if my bug is the same as reported here, but I let others decide.

To begin with, when I start my computer, the monitor goes off soon after the grub menu and comes back on just before the login screen. This happens with the live CD too, and prevents me from checking the installation CD for defects (the checking seems to happen, but I'm not able to see the result). The problem was present already on my earlier Gutsy installation (started perhaps two weeks ago), but I thought it might be because of the experiments I had made with the Nvidia driver (from the Nvidia web site). The monitor doesn't cause the problem, because I tried with another one and got same behaviour.

This is a step by step description of my observations after the installation was finished:

Login screen refresh rate was at 60 Hz and the screen was vertically stretched (not exceeding the screen edges).

Desktop resolution was at 1280 x 768, which means that the desktop was vertically stretched (my monitor being a regular 21" CRT). Refresh rate was 60 Hz.

Graphics card was detected right ("NVIDIA Geforce 8800 Series").

The monitor was not detected. The description was "Custom 1".

I changed monitor model to "Sony GDM-f500/f500t9", which allowed me to select a resolution of 1400 x 1050 and a refresh rate of 85 Hz in "Screen and graphics preferences". A message "All users must log out for changes to take effect" (my translation from Finnish) appeared. I closed the message window to take notes. When I re-opened it, all resolution options above 1280 x 1024 had disappeared. The only available refresh rate was 60 Hz. The selection I made for the monitor ("Sony GDM-f500/f500t9") was still there. I selected the resolution 1280 x 960, which worked at 60Hz refresh rate.

Next I logged out. After logging back in and opening "Screen and graphics preferences", nothing had changed, except that 85 Hz was added as a second option for refresh rate (so now there were 60 Hz and 85 Hz). I selected 85 Hz and it worked. Still no resolutions available above 1280 x 1024.

I decided to reboot and see what that would do. The desktop resolution changed from 1280 x 960 to 1280 x 768 and the refresh rate to 60 Hz (the option for 85 Hz disappeared) without my intervention (other than rebooting). The long list of available resolutions came back though, and I tried to select 1400 x 1050. The resolution changed to something else than that. I would guess 1280 x 1024, because ther were black margins on the right and left edges of the screen, but the desktop wasn't malformed (the "Screen and graphics preferences" and "Screen resolution" kept showing 1400 x 1050). Now the refresh rate option of 85 Hz was back again, and I selected it to see what would happen. It worked and the screen resolution went to 1400 x 1050, which it was supposed to be.

Next I rebooted again to see if things would be stable now. Unfortunately not. The resolution was back in 1280 x 768 (vertically stretched) and refresh rate at 60 Hz (the only option). Here I thought that it's time to make a bug report :-) Well, I had to log out once more to change the system language to English to find the right names for the setting...

here is the output from : sudo get-edid|parse-edid

parse-edid: parse-edid version 1.4.1
get-edid: get-edid version 1.4.1

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
        Function supported
        Call successful

        VBE version 300
        VBE string at 0x11110 "NVIDIA"

VBE/DDC service about to be called
        Report DDC capabilities

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
        Function supported
        Call successful

        Monitor and video card combination does not support DDC1 transfers
        Monitor and video card combination does not support DDC2 transfers
        0 seconds per 128 byte EDID block transfer
        Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
        Read EDID

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
        Function supported
        Call failed

The EDID data should not be trusted as the VBE call failed
Error: output block unchanged
parse-edid: IO error reading EDID

output from : sudo ddcprobe
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: G80 Board - p356h01 Chip Rev
memory: 14336kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 1280x1024x16
mode: 1280x1024x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
edid:
edidfail

I add to my report that in my installation resolution and refresh rate settings are instable both with nv and nvidia driver. I just did a complete re-installation with Daily live, October 11, and the problems continue. If I keep playing with the display settings, after some time I'm able to set the desired resolution, but when I reboot the computer I have to go through the process again.

My display settings have been stable for the last day and a half, including some ten reboots. Perhaps some changes have already been made? If necessary, I might do one more re-install to see if the problem still exists in an untouched system.

I'm experiencing the same problem with the release candidate desktop installation.
I have a 24" Acer capable of 1920x1200@75Hz and I'm only getting 1600x1200@50Hz.
I'm using an Nvidia GEForce FX card with the proprietary driver.

@johnhedge: Please append the output of the following commands "sudo get-edid|parse-edid" and "sudo ddcprobe".

Thanks

# get-edid|parse-edid
parse-edid: parse-edid version 1.4.1
get-edid: get-edid version 1.4.1

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
        Function supported
        Call successful

        VBE version 300
        VBE string at 0x11110 "NVIDIA"

VBE/DDC service about to be called
        Report DDC capabilities

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
        Function supported
        Call successful

        Monitor and video card combination does not support DDC1 transfers
        Monitor and video card combination supports DDC2 transfers
        0 seconds per 128 byte EDID block transfer
        Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
        Read EDID

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
        Function supported
        Call failed

The EDID data should not be trusted as the VBE call failed
EDID claims 255 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
parse-edid: EDID checksum failed - data is corrupt. Continuing anyway.
parse-edid: first bytes don't match EDID version 1 header
parse-edid: do not trust output (if any).

        # EDID version 255 revision 255
Section "Monitor"
        Identifier "___:ffff"
        VendorName "___"
        ModelName "___:ffff"
        # DPMS capabilities: Active off:yes Suspend:yes Standby:yes

        Mode "4095x4095" # vfreq 9.770Hz, hfreq 80.018kHz
                DotClock 655.350000
                HTimings 4095 4350 4605 8190
                VTimings 4095 4158 4221 8190
                Flags "Interlace" "+HSync" "+VSync"
        EndMode
        Mode "4095x4095" # vfreq 9.770Hz, hfreq 80.018kHz
                DotClock 655.350000
                HTimings 4095 4350 4605 8190
                VTimings 4095 4158 4221 8190
                Flags "Interlace" "+HSync" "+VSync"
        EndMode
        Mode "4095x4095" # vfreq 9.770Hz, hfreq 80.018kHz
                DotClock 655.350000
                HTimings 4095 4350 4605 8190
                VTimings 4095 4158 4221 8190
                Flags "Interlace" "+HSync" "+VSync"
        EndMode
        Mode "4095x4095" # vfreq 9.770Hz, hfreq 80.018kHz
                DotClock 655.350000
                HTimings 4095 4350 4605 8190
                VTimings 4095 4158 4221 8190
                Flags "Interlace" "+HSync" "+VSync"
        EndMode
EndSection

# ddcprobe
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: NV34 Board - p162-1n Chip Rev
memory: 131072kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 1280x1024x16
mode: 1280x1024x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
edid:
edid: 1 3
id: ad61
eisa: ACRad61
serial: 7290137f
manufacture: 29 2007
input: composite sync, sync o...

I've just done a complete re-install and something strange happened. The
resolution was 1900x1200 60Hz using Ubuntu drivers but after an update and
reboot we're back to 1600x1200 60Hz!

On 18/10/2007, Sebastian Heinlein <email address hidden> wrote:
>
> @johnhedge: Please append the output of the following commands "sudo
> get-edid|parse-edid" and "sudo ddcprobe".
>
> Thanks
>
> --
> Screens & Graphics not setting correct resolution
> https://bugs.launchpad.net/bugs/139027
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I have a similar issue with my T61.

Ubuntu correctly detects and displays the screen resolution when freshly installed. However, screen and graphics does not have the correct behavior.

It does not detect the screen dimensions properly (only lists smallest resolution with plug and play), and when I manually select my monitor size it displays only a portion of the desktop and I have to "pan" to see the rest.

I have a similar problem with my T61. I tried to provide the output of "sudo get-edid|parse-edid", but it says get-edid command not found. It appears that read-edid package is not available for amd64. I can work around the problem by choosing a LCD monitor, but then I there are some problems with the display on a projector.

Here is the output of sudo ddcprobe
vbe: VESA 3.0 detected.
oem: Intel(r)Crestline Graphics Chip Accelerated VGA BIOS
vendor: Intel Corporation
product: Intel(r)Crestline Graphics Controller Hardware Version 0.0
memory: 7616kb
mode: 1280x1024x256
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 1024x768x256
mode: 1024x768x64k
mode: 1024x768x16m
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 640x480x256
mode: 800x600x256
mode: 640x480x64k
edid:
edid: 1 3
id: 2887
eisa: IBM2887
serial: 00000000
manufacture: 0 2005
input: analog signal.
screensize: 33 21
gamma: 2.200000
dpms: RGB, no active off, no suspend, no standby
dtiming: 1680x1050@59
dtiming: 1680x1050@49
monitorid: LP154W02-TL0

I've got the same problem as the initial poster. I'm having to pan 'n' scan, and the "Screens and Graphics" doesn't work. Attached is some output. Does anyone have a workaround for this yet?

The same problem here...

Using LG 20" screen L204WS resolution 1680 x 1050 @60 Hz, Intel GMA 900 Integrated graphics and I only see 46% X 55 % off the desktop when chose that setting, so instead I use the setting 1280 x 1024 @75Hz and then get the wrong aspect ratio. The screen gets 28% to wide (but still the whole desktop is visible, so it's at least better)

The xdpyinfo | grep -B1 dot gives this reply =>
dimensions: 1680x1050 pixels (431x272 millimeters)
resolution: 99x98 dots per inch

Screen info (In Swedish) http://www.itbutikken.se/i/157143/1.htm

As I think looks perfect, but unfortunately it isn't

Thank you for reporting this bug and for your efforts to make Ubuntu better. As Xorg has improved this past year, an unfortunate side effect of these improvements is that it has rendered several design assumptions in displayconfig-gtk obsolete. So, starting with Hardy we are no longer putting displayconfig-gtk forth as a primary configuration tool, and are putting our development focus into the Screen Resolution applet. As a result, we do not plan to fix this bug and thus are closing it.

For more background on this change, please see this page: [WWW] https://wiki.ubuntu.com/X/DisplayConfigGtk