V1.6.4
- Added possibility/support to set GPU'S with cmd parameters directly in start.bat
- Added parameter --sendallstales , which enables sending of every stale share
- Minor bug fixes
+ So command line setup of GPU'S is finally here. Here are the parameters that can be used:
--ccryptonighttype value (algo to use)
--cgpuid value (gpu id, comma separated values, use --listdevices to see available)
--cgpuintensity value (gpu intensity, comma separated values)
--cgputhreads value (number of gpu threads, comma separated values)
--cgpuworksize value (gpu worksize, comma separated values)
--cgputargettemperature value (gpu temperature, comma separated values)
--cgputargetfanspeed value (gpu fan speed in RPM, comma separated values)
--cgpuadltype value (gpu adl to use (1 or 2), comma separated values)
--cgpukernel value (gpu kernel to use (1 or 2), comma separated values)
Parameters : --cgpuid, --cgpuintensity and --cgputhreads MUST BE USED, the others are optional
If you want to set everything in cmd line, you still need to have an empty config.txt file (which contains just : {}, or any other parameter like api etc etc )
Ex. for GPU and POOL setup from CMD:
Use 1 GPU with id 0 , intensity 120, 2 threads on algo cryptonight v7 on nanopool:
SRBMiner-CN.exe --ccryptonighttype normalv7 --cgpuid 0 --cgpuintensity 120 --cgputhreads 2 --cpool xmr-eu1.nanopool.org:14444 --cwallet 4A5hJyu2FvuM2azexYssHW2odrNCNWVqLLmzCowrA57xGJLNufXfzVgcMpAy3YWpzZSAPALhVH4Ed7x o6RZYyw2bUtbm12g.donation
Use 5 GPUS with id 0,1,2,3,4 , intensities 56,56,55,58,55, 2 threads for each GPU, on algo cryptonight v7 on nanopool:
SRBMiner-CN.exe --ccryptonighttype normalv7 --cgpuid 0,1,2,3,4 --cgpuintensity 56,56,55,58,55 --cgputhreads 2,2,2,2,2 --cpool xmr-eu1.nanopool.org:14444 --cwallet 4A5hJyu2FvuM2azexYssHW2odrNCNWVqLLmzCowrA57xGJLNufXfzVgcMpAy3YWpzZSAPALhVH4Ed7x o6RZYyw2bUtbm12g.donation
+ --sendallstales is now a default parameter in start.bat
When a new job arrives to the miner, and a result from a previous job is sent to the pool, this is called a stale share. A low percent of pools accepts stale shares, they generally reject the share with an 'Invalid job id' error.
Now in SRB i made this logic : if a new job arrives, a share for a previous job is not sent IF it's not sent in a period less than a second since the new job arrived. It looks like some pools accept stale shares even for a few seconds after a new job was dispatched.
This parameter turns off the 1 second rule, and sends every stale share there is. This could potentially lead to an increase in effective share rate, but also you can get a lot more rejected shares, it all depends on the pool you are using.
Oh yeah, you can also get shares rejected when a pool switch/reconnect/job timeout happens, in situations where the pool difficulty is low and you produce a lot of shares, but in the process of doing the calculations (which can take 1-2 sec depending on your hardware) the connection to the pool drops, these share are tried to be sent while you are not logged on the pool, so you will get now a nice warning that a network error has occured and your shares wont be sent.
Dok, please, spent some your time for :
1 Add to stat info, by pressing "s", info about i/w/t too.
2 If it possible in hashrate info add the voltage
3 Can you rec the json info to file from miner. Browser cannot rec to disk any data. Very need.