Show Posts
After a lot of digging, I've found what I think is a bug in BAMTs monitoring perl script.
I noticed the clock speed on my R9 290 fluctuates (DISPLAY=:0.0 /usr/local/bin/atitweak -s), and sometimes outputs a decimal MHz value.
Theres a regex inside /opt/bamt/common.pl (search for "monster"), that tries to match the clock speed as an integer value. When its not an integer value, the regular expression fails and the function returns no GPU's.
An easy fix is to replace the (\d+) section with (.)
I noticed the clock speed on my R9 290 fluctuates (DISPLAY=:0.0 /usr/local/bin/atitweak -s), and sometimes outputs a decimal MHz value.
Theres a regex inside /opt/bamt/common.pl (search for "monster"), that tries to match the clock speed as an integer value. When its not an integer value, the regular expression fails and the function returns no GPU's.
An easy fix is to replace the (\d+) section with (.)
zeddy is right that this is the cause of the problem, but that regex modification didn't work for me. What you can do is go to that area by searching for monster, then find the capture group (\d+) after engine\sclock\s. Change it from (\d+) to (\d+\.*\d+) . This will match properly for both digits and digits with a decimal.
After this change, you shouldn't see GPUs disappearing from the BAMT web interface any longer. Hope this helps someone.
