[RV350] fglrx unable to display 1440x900 resolution

[Joao Amaro]

Using Ubuntu 8.10 / Intrepid (updated using update manager)

 xorg-driver-fglrx
  Installed: 2:8.543-0ubuntu3
  Candidate: 2:8.543-0ubuntu3

When i change the resolution to 1440x900 (xrandr -s 1440x900) the resolution is not working
Even using modeline from: # gtf 1440 900 60
  # 1440x900 @ 60.00 Hz (GTF) hsync: 55.92 kHz; pclk: 106.47 MHz
  Modeline "1440x900_60.00" 106.47 1440 1520 1672 1904 900 901 904 932 -HSync +Vsync

It is acting as 1600x900 @ 59Hz .
I'm using an ASUS VW193D-B lc .

If change to "ati" or "radeon" driver, the resolutions works fine, but i can't use compiz.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface [8086:2570] (rev 02)
     Subsystem: ASUSTeK Computer Inc. P4P800/P5P800 series motherboard [1043:80f2]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV350 AR [Radeon 9600] [1002:4152] (prog-if 00 [VGA controller])
     Subsystem: Info-Tek Corp. Device [18bc:0418]

[Bryce Harrington (bryce)]

Hi joao-amaro,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[Joao Amaro (joao-amaro)]

Hi Bryce.
Here they go.

[Mario Limonciello (superm1)]

Joao:
Can you try using the fglrx-amdcccle tool instead? Randr 1.2 isn't supported by the fglrx driver out of the box, so this would possibly be part of the problem.

[Joao Amaro (joao-amaro)]

Hi Mario.

Already tried it . No success.
When I change the resolution to 1400x900 using amdcccle I have the same result.
My monitor says that the current resolution is: 1600x900 55Khz 59Hz

:(

[Bryce Harrington (bryce)]

I've posted a new version of the -fglrx driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get fglrx 8.620 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.