[i815] X server doesn't use resolution capabilities

In my HARDY-installation

mueller@dhcppc4:~$ cat /etc/X11/xorg.conf
# xorg.conf (X.Org 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 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 "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "de"
 Option "XkbVariant" "nodeadkeys"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
EndSection

Section "Device"
 Identifier "Configured Video Device"
 Option "UseFBDev" "true"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
# Von mue:
# Identifier "Default Screen"
# Device "Intel Corporation 82815 CGC [Chipset Graphics Controller]"
# DefaultDepth 24
# SubSection "Display"
# Modes "1280x1024"
# EndSubSection
EndSection

Section "ServerLayout"
 Identifier "Default Layout"
 Screen "Default Screen"
EndSection

mueller@dhcppc4:~$ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 Chipset Graphics Controller (CGC) [8086:1132] (rev 02)

mueller@dhcppc4:~$ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 Chipset Graphics Controller (CGC) [8086:1132] (rev 02)
mueller@dhcppc4:~$ sudo ddcprobe
[sudo] password for mueller:
vbe: VESA 3.0 detected.
oem: Intel(R) 810, Intel(R) 815 Chipset Video BIOS
vendor: Intel Corporation
product: Intel(R) 810, Intel(R) 815 Chipset Hardware Version 0.0
memory: 1024kb
memory: 4096kb
mode: 132x25 (text)
mode: 132x43 (text)
mode: 132x50 (text)
mode: 132x60 (text)
mode: 320x200x64k
mode: 640x400x256
mode: 640x480x256
mode: 640x480x32k
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x16
mode: 800x600x256
mode: 800x600x32k
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x256
edid:
edidfail

mueller@dhcppc4:~$ xrandr
Screen 0: minimum 640 x 480, current 800 x 600, maximum 800 x 600
default connected 800x600+0+0 0mm x 0mm
   800x600 60.0* 56.0
   640x480 60.0

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Similar symptoms appear with MGA G200 AGP on a uptodate hardy system. With upgrade to hardy the highest possible resolution reduced to 800x600@60 Hz (the hardware supports at least 1280x1024@75 Hz).

matthias@hans:~$ cat /etc/X11/xorg.conf
# xorg.conf (X.Org 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 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 "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "de"
 Option "XkbVariant" "nodeadkeys"
 Option "XkbOptions" "lv3:ralt_switch"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
EndSection

Section "Device"
 Identifier "Configured Video Device"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
EndSection

Section "ServerLayout"
 Identifier "Default Layout"
 Screen "Default Screen"
EndSection

matthias@hans:~$ lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: Matrox Graphics, Inc. MGA G200 AGP [102b:0521] (rev 03)

matthias@hans:~$ sudo ddcprobe
[sudo] password for matthias:
Calling INT 0x42 (F000:F065)
 EAX is 0xBD50
vbe: VESA 2.0 detected.
oem: Matrox Graphics Inc.
memory: 2048kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x256
mode: 1280x1024x256
mode: 80x60 (text)
mode: 132x25 (text)
mode: 132x43 (text)
mode: 132x50 (text)
mode: 132x60 (text)
mode: 640x480x32k
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x32k
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x32k
mode: 1024x768x64k
edid:
edidfail

matthias@hans:~$ xrandr
Screen 0: minimum 400 x 300, current 800 x 600, maximum 800 x 600
default connected 800x600+0+0 0mm x 0mm
   800x600 60.0* 56.0
   640x480 60.0
   400x300 60.0 56.0
matthias@hans:~$

Xorg.0.log contains:

(II) MGA(0): I2C bus "DDC P1" initialized.
(II) MGA(0): I2C device "DDC P1:ddc2" registered at address 0xA0.
(II) MGA(0): I2C device "DDC P1:ddc2" removed.
(II) MGA(0): I2C Monitor info: (nil)
(II) MGA(0): end of I2C Monitor info
(--) MGA(0): No DDC signal
(II) MGA(0): DDC Monitor info: (nil)
(II) MGA(0): end of DDC Monitor info

I've managed (I think so) to install the Xserver from gutsy into my hardy system. That doesn't make the problem disappear. So I suspect my problems aren't the fault of the X server packages.

My workaround is to include the following into the Monitor section of xorg.conf:

 HorizSync 30-92
 VertRefresh 50-85

ATTENTION! This may damage monitors which aren't capable to work with these refresh rates!

The original bug report seems to be a driver-specific issue with intel. Other bug reporters should file separate bugs.

Matthias, please also re-test against Jaunty and attach a fresh Xorg.0.log if the issue is still happening there.

The Xorg.0.log is from the Jaunty installation live system on my computer (I didn't install ist). Is this sufficient?

Could you please also run `lspci -vvnn > lspci-vvnn.txt` and attach that file to this bug report? Thanks ahead of time.

The file was created in the live system Jaunty Alpha 5.

[This is an automatic notification.]

A new major version of the -intel driver is now available in Karmic.

This version includes a major reworking of the acceleration
architecture, which resolves a huge number of issues. We do not know
whether it resolves the issue you reported.

Would you mind testing Karmic Alpha-2 and seeing if it is still a
problem? CD ISO images are available here:

  http://cdimages.ubuntu.com/releases/karmic/

If the issue can still be reproduced on karmic, please report here with
your findings, and attach a fresh Xorg.0.log from your test, and we will
be able to forward the bug upstream.

Otherwise, if the bug no longer exists in Karmic, let us know that as
well.

In the off chance you encounter different bugs while attempting to test
Karmic, please report those as new bug reports.

The gnome-display-properties told me that it didn't recognice the monitor. The Xorg.0.log is from the Karmic live system on my computer (I didn't install it).

Hi Matthias,

I've forwarded your bug upstream to https://bugs.freedesktop.org/show_bug.cgi?id=22698 - please subscribe to this bug report in case upstream needs further information or wishes you to test something. Be aware though that upstream has declared 815 no longer supported so this is kind of a long shot.

Btw the similar MGA issue you reported before is similar only in symptom; that uses a different video driver and looks to be failing for an unrelated reason (failing to read EDID I guess). We'll just focus on -intel on this bug though.

added the linux kernel to this bug.

Matthias,
       Since the kernel does modesetting these days, would you mind testing this against the latest Lucid alpha? Also, in the event that you still encounter this issue, could you test this against the latest vanilla kernel?

Thanks!

-Jfo

Marking the xorg item as invalid.

-JFo

Dear Jeremy,

Lucid alpha doesn't manage to use the resolution capabilities of my hardware with it's default configuration.

Dear Jeremy,

using the Kernel from
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=summary
yields in Xorg.0.log:
(EE) GARTInit: Unable to open /dev/agpgart (No such file or directory)
(EE) intel(0): AGP GART support is not available. Make sure your kernel has
        agpgart support or that the agpgart kernel module is loaded.
...
Fatal server error:
no screens found
...

I've taken /boot/config-2.6.32-14-generic as .config for the kernel, started "make silentoldconfig" and chose the default answers.

Additionally I discovered the file Xorg.failsafe.log (whose role isn't clear to me).

@Matthias -- thanks for your testing. In the past you have included ddcprobe output and xrandr output. Could you collect those too for the lucid boot please. Also could you confirm whether the Xorg.failsafe.log is recent date wise, if so could you include that. Thanks.

My System is booted with the Ubuntu kernel:
matthias@lucid:/var/log$ cat /proc/version
Linux version 2.6.32-16-generic (buildd@rothera) (gcc version 4.4.3 (Ubuntu 4.4.3-3ubuntu1) ) #24-Ubuntu SMP Sat Mar 6 12:33:21 UTC 2010

My Xorg.failsafe.log seems not to be so recent today:
matthias@lucid:/var/log$ ls -l Xorg.failsafe.log
-rw-r--r-- 1 root root 29922 2010-02-23 12:35 Xorg.failsafe.log

Closing this bug with Won't fix as this kernel is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!