Another way to force the rig into no overclocking at all is to copy the "noOC" file from /live/image/BAMT/CONTROL into the /live/image/BAMT/CONTROL/ACTIVE dir. Or you can do individual GPUs, you'll see all the files you can copy to that folder in the CONTROL dir. To remove that option, all you have to do is delete the file from that ACTIVE dir.
Also, if your rig is unstable and reboots, sometimes the management code (mother) will auto gen a file based on the specific GPU it had trouble with and put it in that ACTIVE dir, so that is a place to look if your wondering why it won't ever overclock again.
Lastly, I know you had a question about logs to look for, but I believe most of those services had been disabled as to reduce the number of writes to the USB stick for longevity. (IIRC) There might be one, but you'll have to hunt for it in the readme.
I'm not 100% sure, as I have not looked very closely at the perl code written by lodcrappo, but I'm not 100% sure that the /BAMT/CONTROL/ACTIVE stuff works with cgminer. I was under the impression that it only worked when you used phoenix as the miner. overclocking would be handled by atitweak as a seperate process when using phoenix. since cgminer has it's own built in overclocking/fan control stuff noOC doesn't work.
Again, I'm not 100% sure of that.
Yeah, that could very well be the case. Back in the day when I was building rigs, I always started with phoenix first, got all the cards stable for a week or so, then started tweaking, OC, changing mining software etc.
Speaking of changing the mining software, has anyone seen this happen? Update to the latest cgminer 3.0.0 and when you go to compile it want you to install libusb-1.0, (For supporting BFL FPGAs) so you do an apt-get install libusb-1.0 and it does it, then you can compile, everything is fine and cgminer runs. But then when you reboot, it comes up to a Debian login screen?? Strangest thing. I was going to mess around with it again later this evening to see if I can reproduce the steps on a different USB stick.