Closed NucleaPeon closed 1 year ago
The low-end GPUs are similar to APUs in that they can't reclock memory. If your card uses DDR2 or DDR3 - cheaper options than the GDDRs - it's one of those. APUs can be detected (usually) and that field not shown, but for fixed-clock ram cards it will look like that.
As for the shader clock, your GPU should be able to reclock that, but it depends on the kernel settings etc. Running a GL compositor like KDE may also cause it to stay high. So I'm not sure the measurement is wrong, it may be right but the system config/runtime keeps it like so.
For how to config that, I don't remember off hand, try searching phoronix for the r600 reclocking news years ago. I do remember for the first few years they ran at full clocks, before the dynamic scaling was introduced, and then it had a few different options to tweak.
@clbr Thanks for the informative reply! I don't have a lot of options for video cards that function well. The HD 4650 and the HD 6450 radeon cards display for me well enough, but after a while they freeze up the system due to 3d issues on POWER4 Big Endian systems. The 3xxx series was mentioned as being supported and so far the 3450 hasn't crashed on me yet. I'll be getting in some HD 3870 cards later and will compare those in radeontop.
You are correct, the HD 3450 uses DDR2 RAM.
It sounds like this is expected and therefore not a bug really, so I'll close this up and perhaps post on this when I have some information on the 3870 if I'm seeing anything similar or not.
Really appreciate it!
I installed radeontool, both versions 1.4 and then the latest master in git. I like this tool, though I'm seeing two things that seem off to me. My Shader Clock is at 100% regardless of what I'm doing; right now I'm at a KDE Plasma desktop with no windows, 1920x1200 res. My Memory Clock shows inf% and no bar on the right-hand side.
I'm using a PPC64 Big Endian 970MP cpu, though I don't think that would cause the issue. I also restarted and checked to make sure it wasn't a weird fluke, but I still see the same issue. Any helpful tips to debug the issue? I will do whatever I can to help debug it.