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

Tuxclocker options unavailable. #23

Open
donalddoyson opened this issue Jul 26, 2019 · 6 comments
Open

Tuxclocker options unavailable. #23

donalddoyson opened this issue Jul 26, 2019 · 6 comments

Comments

@donalddoyson
Copy link

https://cdn.discordapp.com/attachments/416042010508787712/604418940365570214/unknown.png

https://cdn.discordapp.com/attachments/416042010508787712/604419028706000906/unknown.png

As can be seen in the above pictures, I have absolutely no sliders available for use. The only one I can use is the fan curve slider, and that is if i switch to manual mode, but nothing else. Any help is appreciated

@Lurkki14
Copy link
Owner

Activate the featuremask as explained in the README.

@eiglow
Copy link

eiglow commented Oct 30, 2019

I activated the featuremask, but I still have the same issue. I'm using a Radeon HD 7970 with amdgpu, on KDE Neon with kernel 5.0.0-32-generic. This might be relevant:

$ sensors -u
amdgpu-pci-1c00
Adapter: PCI adapter
vddgfx:
ERROR: Can't get value of subfeature in0_input: Can't read
fan1:
  fan1_input: 0.000
temp1:
  temp1_input: 53.000
  temp1_crit: 120.000
  temp1_crit_hyst: 90.000
power1:
ERROR: Can't get value of subfeature power1_average: Can't read
ERROR: Can't get value of subfeature power1_cap: Can't read

I'll also add that this is the output I get from tuxclocker itself when run in the terminal (with sudo):

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QMetaObject::connectSlotsByName: No matching signal for on_newProfile_clicked()
QMetaObject::connectSlotsByName: No matching signal for on_newProfile_closed()
QMetaObject::connectSlotsByName: No matching signal for on_editProfile_closed()
amdgpu: amdgpu_bo_cpu_map failed. (-13)
radeonsi: Failed to create a context.

@Lurkki14
Copy link
Owner

I'm not sure if there's a way to edit the clocks or voltages on Pitcairn GPU's using the amdgpu driver, the only information about it I see is on the proprietary drivers

@eiglow
Copy link

eiglow commented Oct 31, 2019

is that also the case for Tahiti GPUs?

@Lurkki14
Copy link
Owner

I'd assume so since the amdgpu support for it is marked as experimental. I'll keep this issue open in case I can find a way to edit the powerplay table some other way.

@eiglow
Copy link

eiglow commented Nov 1, 2019

I appreciate it, good luck on finding a solution!

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

3 participants