If this problem is only happening when installed from hardware drivers - there is another caveat:
It's likely only happening if you previously had fglrx installed at some point with a configuration file in /etc/ait still present. Jockey isn't presenting a UI to show the user there was a configuration file change that they need to acknowledge.
If this problem is only happening when installed from hardware drivers - there is another caveat:
It's likely only happening if you previously had fglrx installed at some point with a configuration file in /etc/ait still present. Jockey isn't presenting a UI to show the user there was a configuration file change that they need to acknowledge.