Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shader clock limited to 0.5 ghz when applying an overclock #42

Open
Supertacoz opened this issue Sep 11, 2022 · 1 comment
Open

Shader clock limited to 0.5 ghz when applying an overclock #42

Supertacoz opened this issue Sep 11, 2022 · 1 comment

Comments

@Supertacoz
Copy link

Supertacoz commented Sep 11, 2022

I have an rx 6600, and am using the latest kernel version (5.19.5) and whenever I apply an overclock to my rx 6600, the shader clock gets limited 0.5ghz, resulting in significantly lower performance. (Note: I am using ubuntu)

@Supertacoz
Copy link
Author

Supertacoz commented Sep 11, 2022

Upon further testing, it seems it only limits the shader clock when "unlock limits" is checked. if any other kind of overclock is applied, the shader clock will behave normally. Also, It seems when any overclock of any kind is applied, the power draw of the card refuses to go beyond 27 watts, while loading the defaults makes it draw power normally.

@Supertacoz Supertacoz changed the title Shader clock stuck at 0.5 ghz when applying an overclock Shader clock limited to 0.5 ghz when applying an overclock Sep 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant