 Averaging 3,200kh/s with 2 Fury's. 382 Clock, 300 Read Count. Using current Darkwinde build. 31 hrs running. I haven't tried different RC settings yet. 60 watts per Fury after putting all of the four fans on a separate power supply. I had an old fan controller that lets me control RPM to cut down the noise. One of the extra fans I'm using is a Delta that is (was) very loud. |
|
|
|
Just for the hell of it I changed that line of code in my last build of bfgminer to info->read_count = info->read_count * 8/10; so that it was .8 instead of .75...didn't notice much of a difference really. I only let it run for half a day but the poolside numbers didn't really look much higher than normal, the local hashrate was in the 1.7-1.8 range though. Maybe higher gives better results? The Zeus doc indicated it was 3/8 and maybe 3/4 later. All the code I looked at showed 3/4. So how do we figure out what it does? Which is faster readcount 3/8 or 7/8? I guessed the smaller fraction would be faster readcount timeout but don't know for sure. Newer code lets us specify readcount like we do chips and clock etc. Default is 300. So would 250 be a quicker readcount? How does diff affect readcount? Lots of questions ...........  Edit: just started Darkwinde's new build with default rc at 300 and will see how it does. |
|
|
|
looks like Zeus has changed readcount in the latest code https://github.com/zeusminer/cgminer_zeus if(info->read_count>opt_zeus_readcount){
info->read_count = opt_zeus_readcount;//send a new work every 10 secondsno more info->read_count = info->read_count * 3/4; I don't understand it well enough to know if we can optionally set readcount in the new code or not. There's other new stuff in there also. I'm hoping this new code lets us push through the .7 freq to kh/s ratio. |
|
|
|
|
Zeusminer makes the chips and the devices.
GAWMiners would be an OEM distributor (Fury)
ZoomHash would be a distributor (Blizzard)
Zeusminer also sells direct to anyone (Blizzard)
|
|
|
|
|
1,602 kH/s 24hr avg on pool now. 60 hours running, no restarts etc. The longer it runs the better it gets.
|
|
|
|
So for the time being we've reached a limit. J4bberwock is going try to break through on the hardware side. A few guys are working on software. Can we improve on the kh/s to freq ratio? Can anyone explain the effect of raising or lowering readcount timeout? 4.3 Readcount Timeout
After we send one command packet to the chained chips, that BIG chip will cover all the 32 bits nonce in a certain TIME. So we must send a new work to it before that, otherwise its hash power is wasted.
Cgminer’s readcount timeout is used for that. Every count means 0.1 second. We now set the readcount to be 3/8 of the covering time. It may be 3/4 later.
Current software builds use 3/4 for 6 chips or 96 chips etc. Can this be optimized for 6 chips? Small improvements with the kh/s to freq ratio would produce substantial gains. 381 * .7 * 6 = 1600 381 * .75 * 6 = 1714 |
|
|
|
I have them in ... :-(
OK 1 2 3
First:
i go to Seed Manager, and setup an New Config like "Zeus"
In this, i Put in, the Config data ..
Then i go to miner.. and set Start ?
Greetings..
Did you build from https://github.com/zeusminer/cgminer_zeus ? My build from there won't start either. |
|
|
|
// support for --set-device
// must be set before probing the device I think this means use set options before specify com port. Poolside hashrate (24hr avg) is down to 1,514 kH/s I'll run: --set zus0:ignore_golden_nonce=1 --set zus:freq=383 --set zus:cores=8 --set zus:chips=6 -S zus:\\.\COMxx and see if any improvement after a couple of hours Edit: I quit it again. Seems like it is running at stock frequencies. Could be my build. |
|
|
|
|
I'm running Windows - not sure if that would work.
The path seems optional. I get an error about "doesn't have permission on the com port" (not an exact quote)
Just tried --set zus0:ignore_golden_nonce=1 and it didn't crash so maybe that is one way to use it in Windows.
edit: so I'll try 383 again using --set zus0:ignore_golden_nonce=1 --set zus:freq=383 --set zus:cores=8 --set zus:chips=6
|
|
|
|
kramble mentioned there was a chance 383 would work. I switched back to 380 as it seemed to be losing hashrate at 383. I may test again later. ------------------------cut------------------------- etc. If you have a buggy ZeusMiner unit that is not recognized, you can try using the following argument: --set zus@/path/to/zeus:ignore_golden_nonce=1 Note that you should not use the above unless needed, and you should specify the path to the affected device. Otherwise other cp210x ASICs will be recognized as a ZeusMiner. I can't figure out how to use: --set zus@/path/to/zeus:ignore_golden_nonce=1 edit: going back to Darkwinde's build to try to get the hashrate back up. 24hr avg on this device has dropped to 1,518 kH/s  |
|
|
|
There's a missing "{" at the start of conf file you posted. Make sure it is in yours. {
"pools": [
{
"notes": "PiMP Testing/Donations - Scrypt 1",
"url": "stratum+tcp://de3.miningpool.co:3902",
"user": "User.USER",
"pass": "x"
},
{
"notes": "PiMP Testing/Donations - Scrypt 2",
"url": "stratum+tcp://de3.miningpool.co:3902",
"user": "USER.USER",
"pass": "x"
}
],
"api-listen": true,
"api-port": "4028",
"expiry": "120",
"nocheck-golden": true,
"chips-count": "6",
"ltc-clk": "328",
"log": "5",
"no-pool-disable": true,
"queue": "9999",
"hotplug": "5",
"scan-serial": [
"/dev/ttyUSB0",
"/dev/ttyUSB1",
"/dev/ttyUSB2",
"/dev/ttyUSB3",
"/dev/ttyUSB4",
"/dev/ttyUSB5",
"/dev/ttyUSB6",
"/dev/ttyUSB7",
"/dev/ttyUSB8",
"/dev/ttyUSB9"
],
"scan-time": "30",
"scrypt": true,
"verbose": true,
"shares": "0",
"kernel-path": "/usr/local/bin",
"api-allow": "W:127.0.0.1",
"api-description": "cgminer v3.1.1-zm"
} |
|
|
|
nwoolls has been busy: https://bitcointalk.org/index.php?topic=626361.msg7409154#msg7409154 //max clock 383MHz, min clock 200MHz
if (chip_clk > 383)
chip_clk = 383;
else if (chip_clk < 200)
chip_clk = 200; 383 seems to work but I just started it. I'll run it for a couple of hours to see where the hashrate stabilizes. My first try at compiling anything so your results may be better  |
|
|
|
|
Does cgminer start but can't find device or does cgminer not start at all?
|
|
|
|
|
I don't know if better.
I can run one at 381 clk and the other at 380. Not sure if I can do that with 1 instance.
For some reason one likes 381 and the other likes 380
Just hit 1,584 kH/s 24hr avg poolside with the one running 381 clk.
|
|
|
|
|
with bfgminer I run a batch file for each Fury , 2 Fury's, 2 batch files
each batch file specifies a different com port
You can run multiple devices in one instance but with two miners I run one instance per miner. I have 2 bfgminer windows running at the same time.
|
|
|
|
|
Show Posts
