Thanks very much, j03. I'll try testing that way.
I have not been able to find the bash script, but I'll look again. A couple questions:
1. Is Bertmod ZPM different from v4? Is this from the KNC forums?
2. Have you done any SPI voltage, SPI frequence, or per-die tuning in the KNC Advanced gui?
3. What's your order of procedure? I have:
-flash a KNC firmware
-run enablecores.bin (just out of habit)
-let the machine spin up
-ssh into cgminer
-"vi /etc/init.d/cgminer.sh" to get to clock settings
-adjust clock settings
-type esc, then a colon, and then "wq", then enter
-machine seems to reboot on it's own, i don't restart
-watch the new hashrate
-mess with tuning, even though I don't know what im doing
-compare pool and machine hash rates
-wonder what's going on (LOL)
Could you share? Thank you very much.
Bash script is here. Keep the original clock setting on line 61 and paste the script in beginning on the next line (line 62):
https://bitcointalk.org/index.php?topic=313978.msg4432410#msg4432410That script is for a 4 module, 4 VRM machine and assumes you modules are plugged in 0 through 3 connectors on the controller board. Change to your setup. Also, you need to add or subtract the number of module IF statements based on your machine. Mine is a Jupiter+2, so I added 2 additional statements for modules 4 and 5 that are plugged into the controller board.
The 4 die clock settings within each module IF statement assumes 4 VRM. If you have 8 VRMs, add 4 more within each IF statement.
1. Not sure about the diffs in Bertmod versions.
2. I haven't touched Advanced Tuning because I also have no idea what I'm doing there

3. My procedure is the same as yours but you forgot /etc/init.d/cgminer.sh restart after :wq the changes. Don't reboot the machine or you'll lose your changes. Also applying changes at Advanced Tuning wipes changes to cgminer.sh. There's instructions in this thread to make your custom cgminer.sh persist on reboot, but I haven't done it.
I currently get around 920GH/s on a Jupiter+2.