Resolution does not persist after reboot

[Andrew Barbaccia]

Binary package hint: xorg-driver-fglrx

Xorg does not seem to keep the screen resolution you set within the Catalyst Control Center after a reboot.

Hardcoding the resolution into the xorg.conf file will work, but this is not the intended functionality.

[Bryce Harrington (bryce)]

Hi andrew-monolithmc,

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.

[rat_poison (pm-rat-poison)]

Having encountered the same problem, I'm posting mine.
I haven't configured my xorg.conf manually.

Terminal outputs are inside the attached file

[rat_poison (pm-rat-poison)]

Probable Workaround (tested on Kubuntu):
Setting up Resolution through KRandRTray and starting it up on boot seems to fix the issue

[wgjohnson (wgjohnson)]

I encountered similar issue as reporter; when using Catalyst Control Center to add Big Desktop settings, changes aren't saved after reboot, or X restart.

Workaround:
As described by http://ubuntuforums.org/showthread.php?t=794551&p=#8 changes are preserved after X restart and reboot.

Resolution:
http://ubuntuforums.org/showthread.php?t=794551&page=2&p=#13

This bug doesn't seem to be a responsibility of Ubuntu necessarily but of ATI/AMD. Has any one contacted ATI/AMD regarding this issue? I don't mind putting in a bug report to ATI, I just don't want to double-efforts, or create noise for ATI.

[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.