[Radeon 200m (RC410)] Screen resolution issues in Intrepid

[Dimitri]

Binary package hint: xserver-xorg-video-ati

Intrepid only offers me only the native resolution of the display (1280x786). However, for presentation purposes, I would want to be able to go to 1024x786 or 800x600. These resolutions are offered for the display on VGA-out, but if I select them, I only get a subset of the entire screen.

$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 768, maximum 2080 x 768
VGA-0 connected (normal left inverted right x axis y axis)
   1360x768 59.8
   1024x768 60.0
   800x600 60.3
   640x480 59.9
LVDS connected 1280x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1280x768 60.0*+
S-video disconnected (normal left inverted right x axis y axis)

FGLRX driver allows me to change resolution of my laptop screen to lower resolutions.

Similarly to other bug reports and the solution to them I tried the following, with no luck:

 Option "UseFBDev" "true"
 Option "IgnoreEDID" "true"

More information:

$ lspci | grep VGA
01:05.0 VGA compatible controller: ATI Technologies Inc RC410 [Radeon Xpress 200M]

xorg.conf:

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
 DefaultDepth 24
 SubSection "Display"
  Virtual 2080 768
 EndSubSection
EndSection

Section "Module"
 Load "glx"
EndSection

Section "Device"
 Identifier "Configured Video Device"
 Driver "radeon"
 Option "AGPMode" "8"
 Option "AccelMethod" "EXA"
 Option "ColorTiling" "on"
 Option "EnablePageFlip" "true"
 Option "GARTSize" "64"
 Option "XAANoOffscreenPixmaps" "true"
 Option "UseFBDev" "true"
EndSection

[Dimitri (dvanlanduyt)]

Oh, I forgot: package version is: 1:6.10.99.99+git20090218.9a108f0a-0ubuntu0tormod2~intrepid

[Dimitri (dvanlanduyt)]

read-edid and ddcprobe results:

$ sudo get-edid
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 200
 VBE string at 0x11110 "ATI RADEON XPRESS 200M Series"

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
EDID claims 19 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
�N

ddcprobe

$ sudo ddcprobe
vbe: VESA 2.0 detected.
oem: ATI RADEON XPRESS 200M Series
memory: 16384kb
mode: 320x200x32k
mode: 320x200x64k
mode: 320x200x16m
mode: 1600x1200x256
mode: 640x400x256
mode: 640x480x256
mode: 640x480x32k
mode: 640x480x64k
mode: 640x480x16m
mode: 1600x1200x32k
mode: 800x600x256
mode: 800x600x32k
mode: 800x600x64k
mode: 800x600x16m
mode: 1600x1200x64k
mode: 1024x768x256
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x256
mode: 1280x1024x32k
mode: 1280x1024x64k
mode: 1280x1024x16m
edid: �
edidfail

[Dimitri (dvanlanduyt)]

A log file of FGLRX driver which succeeds in getting the information through EDID

[Tormod Volden (tormodvolden)]

Can you please attach the log from using -ati and default xorg.conf?

[Dimitri (dvanlanduyt)]

Log from using customized xorg.conf (as above) in attachment

[Dimitri (dvanlanduyt)]

Log from default xorg.conf (after dpkg-reconfigure -phigh xserver-xorg) in attachment

[Tormod Volden (tormodvolden)]

I think this needs to be reported upstream. They will likely request that you try against a newer xserver. Do you have the chance to test Jaunty (for example from a live CD)?

You are welcome to report the upstream report yourself on bugs.freedesktop.org, otherwise we will do it.

[Dimitri (dvanlanduyt)]

I will only be able to test Jaunty in two weeks. Is it possible to manually enforce the lower resolutions (e.g. by editing the xorg.conf file)? If so, can you tell me how?

Please report upstream, I am not familiar with Bugzilla, took me a while to get around launchpad ;-)

[Tormod Volden (tormodvolden)]

You can try adding modes manually, see for instance http://wiki.debian.org/XStrikeForce/HowToRandR12 You can look up the Modelines in the fglrx log.

[Dimitri (dvanlanduyt)]

That does not work, maybe it is related to the bug, or is it a different one?

$ xrandr --newmode "800x600" 68.93 800 1056 1104 1408 600 687 693 816
dimitri@placeholder:~$ xrandr --addmode LVDS "800x600"X Error of failed request: BadMatch (invalid parameter attributes)
  Major opcode of failed request: 153 (RANDR)
  Minor opcode of failed request: 18 ()
  Serial number of failed request: 16
  Current serial number in output stream: 17

[Bryce Harrington (bryce)]

We'd like to forward this issue upstream, but first it must be retested on latest Jaunty to make sure the issue still happens there with the latest code. ISO images are available at http://cdimages.ubuntu.com/releases/jaunty/. If you can reproduce it in the LiveCD environment, you shouldn't need to modify your installed system. Also please attach a fresh Xorg.0.log from this testing.

[Tormod Volden (tormodvolden)]

There was an upstream commit today "radeon: just add some common modes for LVDS", I haven't checked further so I don't know if it will change anything for you, but please test the packages in my PPA https://launchpad.net/~tormodvolden/+archive/ppa which include this commit (-ati and -radeon version 1:6.11.0.99+git20090304.b1fd883b-0ubuntu0tormod).

[Dimitri (dvanlanduyt)]

That commit has indeed fixed the issue. Great! Thank you very much! I presume this will make it into jaunty?

[Tormod Volden (tormodvolden)]

Good to hear. Yes, this will be included in the 6.12 release that we hope to get into Jaunty before Beta.

[Tormod Volden (tormodvolden)]

For reference, the fix was most likely in commit http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/commit/?id=e88b0eac8cab8b54b769fd7b4ad3b3b65a90de09

[Bryce Harrington (bryce)]

This change is included in xserver-xorg-video-ati-6.11.0+git20090310.945ccbbd now uploaded to jaunty.