amdcccle settings do not persist lucid

[cornbread]

setting monitors in amdcccle settings say to restart for many changes to take affect. After restart nothing changes.

This happens even if the change does not require restart.

Very frustrating.

[Bryce Harrington (bryce)]

Not enough information has been provided to troubleshoot. See http://wiki.ubuntu.com/X/Reporting for instructions on reporting X issues.

[cornbread (corn13read)]

lspci -nn | grep VGA
02:00.0 VGA compatible controller [0300]: ATI Technologies Inc Juniper [Radeon HD 5700 Series] [1002:68b8]

[cornbread (corn13read)]

what's the deal with this? do i have to post more logs?

[Bryce Harrington (bryce)]

A more detailed description of the problem would help; as it is I gather you're having some sort of problem with amdcccle not saving stuff, and that it's frustrating, but that doesn't give enough information to determine if it's a legitimate defect in Ubuntu that needs developer attention, or if it's just something peculiar with your configuration, and you just need technical support to work through it. (If the latter, then please start at http://answers.launchpad.net/ubuntu or ubuntuforums.)

[cornbread (corn13read)]

I HAVE JUST DONE A FRESH INSTALL and the issue still persists. how can that be something particular with "my configuration"? How can I PROVE that this is a bug?

steps taken:

1. Fresh beta 2 64bit install
2. run all updates
3. install amd drivers through jockey
4. restart
5. change monitor settings
6. restart
7. SEE NO CHANGES

02:00.0 VGA compatible controller: ATI Technologies Inc Juniper [Radeon HD 5700 Series]

[ronan (ronan-jajoro)]

I've have the same problem.
I go into amdcccle (Administrative), change to dual monitor setup and click apply. Change happens immediately and everything works. I then reboot and the change has reverted and I'm back to cloned screens.
Device is a Radeon HD 4850
Drivers/Software
fglrx - 2:8.723.1-0ubuntu2
fglrx-amdcccle - 2:8.723.1-0ubuntu2
fglrx-kernel-source - 2:8.660-0ubuntu6
xorg-driver-fglrx 2:8.660-0ubuntu4

[Felix Kuehling (felix-kuehling)]

The Catalyst Control Center stores its configuration settings in xorg.conf. If you've used the GNOME monitor applet in the past, it applies its settings when you log in and overrides any settings stored in xorg.conf.

Try deleting ~/.config/monitors.xml, log out and log back in. Does that make settings you changed in the Catalyst Control Center effective?

[ronan (ronan-jajoro)]

No change, but ~/.config/monitors.xml was there.

I deleted ~/.config/monitors.xml, configured dual monitors in amdcccle and then rebooted. The monitors went back to cloned screes.

Also, there is no difference between xorg.conf before and after amdcccle change.

[Sheridan Hutchinson (sheridan-shezza)]

I also find that the settings do not persist between reboot.

The easy way for me to tell this is to:

1.) Set force v-sync on;

2.) Reboot

3.) Wobble a window (compiz..) and observe the tear;

4.) Load the Catalyst settings menu (admin version);

5.) Set v-sync off, click apply, then force v-sync on;

6.) Wobble a window (compiz..) and observe no tear;

[Launchpad Janitor (janitor)]

[Expired for fglrx-installer (Ubuntu) because there has been no activity for 60 days.]

[Ciro Santilli 六四事件 法轮功 (cirosantilli)]

Reproduce on 14.04. Settings don't even persist if I just close and reopen amdcccle without reboot.

[Ryan Harkin (ryanharkin)]

I see this problem also. It worked in 12.04, but I can't remember if it worked in 12.10, but it definitely hasn't worked since.

I have two HD6570 cards rather than just one.

I open the AMD Catalyst Catalyst Control Center (Administrative), enable the 3rd monitor, reboot, and it's not saved the setting. As I said, it worked fine on 12.04.

The open source drivers work, to a fashion. But they are so buggy and laggy that they're barely usable.

Now to find a recent version of this bug for 14.04 or 14.10 and see if anyone is making progress there....

[Bedlore (brendan-dbinformatics)]

Also suffering this,
Linux hyssop 3.13.0-63-lowlatency #103-Ubuntu SMP PREEMPT
amdcccle 2.21

Anyone find a work around?