The right resolution for my screen is not detected

Bug #567296 reported by Josef Engelfrost
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

The right resolution for my Samsung SyncMaster 2232BW screen is not detected when I plug it in into my laptop running Lucid. The resolution was correctly detected in Jaunty, but not in Lucid.

I'm not sure what package to assign this to.
---
Architecture: i386
DistroRelease: Ubuntu 10.04
DkmsStatus:
 virtualbox-ose, 3.1.6, 2.6.32-21-generic, i686: installed
 virtualbox-ose, 3.1.6, 2.6.32-20-generic, i686: installed
GdmLog:
 Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
 QFileSystemWatcher: failed to add paths: /home/josef/.config/ibus/bus
 Bus::open: Can not get ibus-daemon's address.
 IBusInputContext::createInputContext: no connection to ibus-daemon
 cat: /var/log/gdm/:0.log: No such file or directory
GdmLog1: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100225)
MachineType: LENOVO 076346G
Package: xserver-xorg-video-intel 2:2.9.1-3ubuntu4
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=04815653-2d47-4246-a98c-0638342ee065 ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Tags: lucid lucid
Uname: Linux 2.6.32-21-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/20/2007
dmi.bios.vendor: LENOVO
dmi.bios.version: 62ETC1WW (1.11 )
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnLENOVO:bvr62ETC1WW(1.11):bd04/20/2007:svnLENOVO:pn076346G:pvrLENOVO3000V100:rvnLENOVO:rnINVALID:rvrNotApplicable:cvnLENOVO:ct10:cvrN/A:
dmi.product.name: 076346G
dmi.product.version: LENOVO3000 V100
dmi.sys.vendor: LENOVO
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-21-generic

---
Architecture: i386
DistroRelease: Ubuntu 10.04
DkmsStatus:
 virtualbox-ose, 3.1.6, 2.6.32-21-generic, i686: installed
 virtualbox-ose, 3.1.6, 2.6.32-20-generic, i686: installed
GdmLog:
 Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
 QFileSystemWatcher: failed to add paths: /home/josef/.config/ibus/bus
 Bus::open: Can not get ibus-daemon's address.
 IBusInputContext::createInputContext: no connection to ibus-daemon
 cat: /var/log/gdm/:0.log: No such file or directory
GdmLog1: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100225)
MachineType: LENOVO 076346G
Package: xserver-xorg-video-intel 2:2.9.1-3ubuntu5
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=04815653-2d47-4246-a98c-0638342ee065 ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Tags: lucid lucid
Uname: Linux 2.6.32-21-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/20/2007
dmi.bios.vendor: LENOVO
dmi.bios.version: 62ETC1WW (1.11 )
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnLENOVO:bvr62ETC1WW(1.11):bd04/20/2007:svnLENOVO:pn076346G:pvrLENOVO3000V100:rvnLENOVO:rnINVALID:rvrNotApplicable:cvnLENOVO:ct10:cvrN/A:
dmi.product.name: 076346G
dmi.product.version: LENOVO3000 V100
dmi.sys.vendor: LENOVO
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-21-generic

Revision history for this message
Philip Muškovac (yofel) wrote :

Hi, thank you for taking your time to report this bug and helping to make Ubuntu better. Can you please attach your /var/log/Xorg.0.log to the report? Thanks.

tags: added: lucid
Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Josef Engelfrost (engelfrost) wrote :

No problem!

Revision history for this message
Philip Muškovac (yofel) wrote :

If I understand this right the monitor sends this EDID information when you connect it:

(II) intel(0): EDID vendor "CMO", prod id 4624
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 -hsync -vsync (49.3 kHz)
(II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)

affects: ubuntu → xserver-xorg-video-intel (Ubuntu)
Changed in xserver-xorg-video-intel (Ubuntu):
status: Incomplete → New
Bryce Harrington (bryce)
tags: added: resolution
Revision history for this message
Josef Engelfrost (engelfrost) wrote :

I don't really understand from the file what lines are for what monitor, but my laptop screen (LVDS1) has a resolution of 1280x800 when I don't use my external (VGA1) monitor. When I plug in my VGA monitor Kubuntu picks a resolution of 1024x768 on both screens. The resolutions I can pick from in "Screen Settings" are listen from line 268 onwards:
(II) intel(0): Printing probed modes for output VGA1
(II) intel(0): Modeline "1360x768"x59.8 84.75 1360 1432 1568 1776 768 771 781 798 -hsync +vsync (47.7 kHz)
(II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
(II) intel(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz)
(II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz)
(II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)

To get the proper resolution I run
xrandr --newmode "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync
xrandr --addmode VGA1 "1680x1050_60.00"
xrandr --output VGA1 --mode "1680x1050_60.00"

I got the new mode by running
josef@juni:~$ cvt 1680 1050
# 1680x1050 59.95 Hz (CVT 1.76MA) hsync: 65.29 kHz; pclk: 146.25 MHz
Modeline "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync

Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Incomplete
Revision history for this message
Chris Halse Rogers (raof) wrote :

Hm. Do you have a /etc/X11/xorg.conf file? If so, you might want to try moving it out of the way and seeing if that fixes this.

If not, could you please run “apport-collect 567296” - that will collect a bunch of useful logs.

Revision history for this message
Josef Engelfrost (engelfrost) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Josef Engelfrost (engelfrost) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : Dependencies.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : Lspci.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : Lsusb.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : PciDisplay.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : ProcModules.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : UdevDb.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : UdevLog.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : XorgLog.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : XorgLogOld.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : Xrandr.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : glxinfo.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : setxkbmap.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : xdpyinfo.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : xkbcomp.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote :

I just realized that I didn't have my other screen plugged in when I ran that command... Should I do it again with the screen plugged in?

Bryce Harrington (bryce)
tags: added: kubuntu
Revision history for this message
Chris Halse Rogers (raof) wrote :

Yes, please. It would be useful for you to collect the logs with the external screen (the one with the resolution problem) plugged in.

Revision history for this message
Josef Engelfrost (engelfrost) wrote : BootDmesg.txt

apport information

description: updated
Revision history for this message
Josef Engelfrost (engelfrost) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : Dependencies.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : Lspci.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : Lsusb.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : PciDisplay.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : ProcModules.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : UdevDb.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : UdevLog.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : XorgLog.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : XorgLogOld.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : Xrandr.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : glxinfo.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : setxkbmap.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : xdpyinfo.txt

apport information

Revision history for this message
Josef Engelfrost (engelfrost) wrote : xkbcomp.txt

apport information

Revision history for this message
Chris Halse Rogers (raof) wrote :

Your dmesg is full of
"""
[ 28.781441] [drm:edid_is_valid] *ERROR* EDID checksum is invalid, remainder is 130
[ 28.781446] [drm:edid_is_valid] *ERROR* Raw EDID:
[ 28.781451] <3>00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff ................
[ 28.781454] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[ 28.781457] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[ 28.781460] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[ 28.781463] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[ 28.781466] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[ 28.781469] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[ 28.781471] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
"""

This indicates that the kernel module is getting a bad EDID from your monitor, and the EDID is a table of information provided by the monitor telling the driver what resolutions it supports. This is likely to be your problem.

However, you say this worked in Jaunty? Could you please create the following /etc/X11/xorg.conf
"""
Section "Device"
    Identifier "My display"
    Driver "intel"
    Option "ModeDebug" "true"
EndSection
"""
and reboot, adding “nomodeset” to the kernel command line? This will disable the kernel's modesetting code and let the (older) modesetting code in the X driver try to set up your display. If that gets the correct resolution on your monitor, could you please attach the /var/log/Xorg.0.log file while using nomodeset and the external monitor? Thanks!

Revision history for this message
Josef Engelfrost (engelfrost) wrote :

I tried adding the xorg.conf file and rebooting with nomodeset, but no luck.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no activity for 60 days.]

Changed in xserver-xorg-video-intel (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.