so when u ssh into the rig and check the core clocks (aticonfig --adapter=all --odgc) there is still the default clock active? or is it the max clock and the actual clock is 1129?
that would mean that your power target is to low i would say so the gpu is downclocking to stay stable.
that would mean that your power target is to low i would say so the gpu is downclocking to stay stable.
I left my power target alone, so i do not think it is that.
I have never used SSH. But it does not look too difficult, but where do I find proper login credentials for each rig?
A: miner/miner .... root/miner1324
than i dont understand what u mean. who is telling you the different clocks?
The default clock of my current bios is set to 1191. But the smOS dashboard displays the clock as 1128. It is also hashing as if the clock is ACTUALLY set to 1128. When smOS first boots, before the miner starts, when the OC profile is applied it does not say anything about down-clocking. If, instead of leaving the OC settings blank, I type "1191" in the core clock field, the OC profile is then applied on startup, outputting "1191 ----> 1191"
First boot after flashing the GPU, it hashed at 29.3 and smOS dashboard displayed 1191 as the core clock. After 10-20mins the hashrate dropped to ~27-28 and the dashboard began displaying the core clock as 1128. Every restart since, the card has hashed at 27-28h right off the bat, and the dashboard always displays core clock as 1128.
edit: I would like to ssh into the rig to check your suggestion, but I have never done that before. I have installed Putty and am tying to figure out what the proper ip/port is.
your ip you should know
is it in your local network then ask your router for DHCP leases ... port is 22 ... user and password is miner ...
after logging in you need to type the following:
Code:
export DISPLAY=:0
aticonfig --adapter=all --odgc
aticonfig --adapter=all --odgc
Putty just tells me "Network Error: Connection Refused"
Sorry, I've done hardware repair for years, and am finally paying for avoiding networking
... i dunno if 200ms is causing stales ... 
so the how-to section is correct?