zot57
Newbie
Offline
Activity: 165
Merit: 0
|
|
April 05, 2018, 07:06:16 PM |
|
Can someone provide me with info what files I need I see posts using gpu.txt file, yet I don't see that in ZIP of SRbminer. So it would be great if someone can provide me with full files, I have 4x rx vega 64 cards and have no idea how to setup with this new algos.
Thanks
|
|
|
|
Baikal miner
Newbie
Offline
Activity: 53
Merit: 0
|
|
April 05, 2018, 07:51:38 PM |
|
|
|
|
|
heavyarms1912
|
|
April 05, 2018, 07:51:48 PM |
|
If the share is accepted dont worry. Stale share is a result that was sent after a new job arrived, its just an indication, so if server dont accept it, it would be a rejected share. Dont worry about it, maybe ill just remove that indication so people wont worry without a reason 😀
Yes probably that would be better idea. Or just keep a count of the potential stale shares. is there a way to figure out actual stale shares? no that is something only the pool knows. Also when diff is low jobs come very fast so thats another reason for stale shares. Alright. For some reason the miner just hangs on my 6xRX580 Rig regardless of intensity (tried 52, 45, 30). It works fine with single thread, autointensity val=59.
|
|
|
|
peterboy1
Newbie
Offline
Activity: 168
Merit: 0
|
|
April 05, 2018, 08:03:50 PM |
|
i think you should improve the stats, which gpu is giving rejects/invalid, and the like.
also, im having a problem with errors:
accepted/total shares: 577/580 (and i cant find in the logs.txt whats causing the missing 3 shares) network errors: 3 (maybe this is the reason?)
i think its related to error "pool is not responding"
is there something wrong with my setup?
i have 2 rigs connected with the same internet connection.
rig 1 doesnt have that problem, but rig 2 gave that error.
so i think its not pool related.
|
|
|
|
doktor83 (OP)
|
|
April 05, 2018, 09:05:31 PM |
|
i think you should improve the stats, which gpu is giving rejects/invalid, and the like.
also, im having a problem with errors:
accepted/total shares: 577/580 (and i cant find in the logs.txt whats causing the missing 3 shares) network errors: 3 (maybe this is the reason?)
i think its related to error "pool is not responding"
is there something wrong with my setup?
i have 2 rigs connected with the same internet connection.
rig 1 doesnt have that problem, but rig 2 gave that error.
so i think its not pool related.
yes, those 3 shares were lost cause they couldn't be sent to the pool (pool not responding). Probably connection was lost to the pool, nothing you can do about that.
|
|
|
|
RomanV0703
Newbie
Offline
Activity: 1
Merit: 0
|
|
April 05, 2018, 10:11:45 PM |
|
Doesn't work for my old 7970. Just crashes if I set Gives an error Error CL_INVALID_DEVICE when calling clCreateContext if I set
|
|
|
|
pbfarmer
Member
Offline
Activity: 340
Merit: 29
|
|
April 05, 2018, 11:01:24 PM |
|
Can you tell me if there is a chart of hashrate for Cryptonight heavy? or if Cryptonight heavy has same hashrate as cryptonight?
No. Your hashrate with cryptonight heavy is lower than cryptonight normal My rig does 54xx h/s with cryptonight normal but only 43xx with cryptonight heavy so far Crytonight heavy will be lower than cryptonight normal for any miner. @docktor83 mine are 4gb cards. I couldn't go higher than 59 on two threads; the miner hangs (perhaps too much load on CPU or low on virtual mem; didn't triage much) This is not true. Seems like this is the case for CPUs, and possibly any card w/ 4GB mem or less, but all my cards (except for an HD7950) are 8GB, and every one of those actually got about a 50H/s boost from CN-Heavy w/ xmr-stak. Haven't tried this miner yet (but will soon for Vega, since those didn't fare as well.)
|
|
|
|
doktor83 (OP)
|
|
April 05, 2018, 11:23:34 PM |
|
V1.2.3 - Fixed Nicehash extranonce thingy - Fixed a bug with gpu_conf settings. Those forks screw things up - Fixed devfee mining bug, again those forks.. - Added display of HW errors per thread
|
|
|
|
momodigital
Newbie
Offline
Activity: 24
Merit: 0
|
|
April 06, 2018, 12:03:57 AM |
|
V1.2.3 - Fixed Nicehash extranonce thingy - Fixed a bug with gpu_conf settings. Those forks screw things up - Fixed devfee mining bug, again those forks.. - Added display of HW errors per thread
Perfect, no stale share for 5 minnute... you are superman!
|
|
|
|
Marvell2
|
|
April 06, 2018, 12:11:35 AM |
|
seens slower than cast on vega 1500 mhs max
|
|
|
|
pbfarmer
Member
Offline
Activity: 340
Merit: 29
|
|
April 06, 2018, 12:33:56 AM |
|
seens slower than cast on vega 1500 mhs max
Is that for cn-heavy (monero / haven)? That's the best I've been able to do w/ any miner since the fork. Of course, cast doesn't support heavy yet.
|
|
|
|
cammino
Newbie
Offline
Activity: 7
Merit: 0
|
|
April 06, 2018, 03:41:19 AM |
|
RX550 Blockchain Drivers
STELLITE /* Type can be : normal, normalv7, lite, litev7, heavy */ "cryptonight_type" : "normal",
/* Intensity 0-> auto intensity, or value from 1-200 */ "intensity" : 26,
/* To use 2 threads per card set double_threads to true */ "double_threads" : true,
/* Gpu target temperature, leave it on 0 if you don't want to use this option */ "target_temperature" : 0,
/* If you use a SSL/TLS encrypted pool set this to true*/ "pool_use_tls" : false,
/* Mining pool address WITHOUT the stratum+tcp:// or stratum+tls:// part */ "pool" : "communitypool.stellite.cash:6688"
Rejects ONLY
SUMO /* Type can be : normal, normalv7, lite, litev7, heavy */ "cryptonight_type" : "heavy",
/* Intensity 0-> auto intensity, or value from 1-200 */ "intensity" : 26,
/* To use 2 threads per card set double_threads to true */ "double_threads" : true,
/* Gpu target temperature, leave it on 0 if you don't want to use this option */ "target_temperature" : 0,
/* If you use a SSL/TLS encrypted pool set this to true*/ "pool_use_tls" : false,
/* Mining pool address WITHOUT the stratum+tcp:// or stratum+tls:// part */ "pool" : "pool.sumokoin.hashvault.pro:5555",
Error CL_INVALID_BUFFER_SIZE when creating scratchpad buffer for DeviceID 0 (Thread 0)
|
|
|
|
|
ruk55
Newbie
Offline
Activity: 26
Merit: 0
|
|
April 06, 2018, 04:05:59 AM |
|
haven coin miner IP addresses banned ?SRBMiner liked force
|
|
|
|
pbfarmer
Member
Offline
Activity: 340
Merit: 29
|
|
April 06, 2018, 04:10:56 AM |
|
RX550 Blockchain Drivers
STELLITE /* Type can be : normal, normalv7, lite, litev7, heavy */ "cryptonight_type" : "normal",
/* Intensity 0-> auto intensity, or value from 1-200 */ "intensity" : 26,
/* To use 2 threads per card set double_threads to true */ "double_threads" : true,
/* Gpu target temperature, leave it on 0 if you don't want to use this option */ "target_temperature" : 0,
/* If you use a SSL/TLS encrypted pool set this to true*/ "pool_use_tls" : false,
/* Mining pool address WITHOUT the stratum+tcp:// or stratum+tls:// part */ "pool" : "communitypool.stellite.cash:6688"
Rejects ONLY
SUMO /* Type can be : normal, normalv7, lite, litev7, heavy */ "cryptonight_type" : "heavy",
/* Intensity 0-> auto intensity, or value from 1-200 */ "intensity" : 26,
/* To use 2 threads per card set double_threads to true */ "double_threads" : true,
/* Gpu target temperature, leave it on 0 if you don't want to use this option */ "target_temperature" : 0,
/* If you use a SSL/TLS encrypted pool set this to true*/ "pool_use_tls" : false,
/* Mining pool address WITHOUT the stratum+tcp:// or stratum+tls:// part */ "pool" : "pool.sumokoin.hashvault.pro:5555",
Error CL_INVALID_BUFFER_SIZE when creating scratchpad buffer for DeviceID 0 (Thread 0)
Rejects generally mean incorrect algo. You should be using normalv7 for stellite according to https://bitcointalk.org/index.php?topic=3167363.msg33955720#msg33955720CL_INVALID_BUFFER_SIZE errors means you're running out of GPU mem. Reduce your intensity.
|
|
|
|
cammino
Newbie
Offline
Activity: 7
Merit: 0
|
|
April 06, 2018, 04:52:05 AM |
|
|
|
|
|
cammino
Newbie
Offline
Activity: 7
Merit: 0
|
|
April 06, 2018, 06:27:38 AM |
|
RX550 SUMOCOIN intensity: 13 only 5xRX550 - 1500 h/s IF (e.g. STELLITE) intensity: 26 5xRX550 - 2400 h/s Thanks for miner! Need FAN management and gpu/mem clock management.
|
|
|
|
momodigital
Newbie
Offline
Activity: 24
Merit: 0
|
|
April 06, 2018, 08:50:27 AM |
|
Using "cryptonight_type" : "heavy", at hashvault sumokoin hashrate become low from 400 to 349
[2018-04-06 16:44:00] ADL initialised successfully! [2018-04-06 16:44:00] Connecting to pool.sumokoin.hashvault.pro:5555 [2018-04-06 16:44:00] Connected to pool. [2018-04-06 16:44:00] Pool difficulty: 50000 [2018-04-06 16:44:00] Pool sent a new job (ID: E/Ry9SoPgarEad9X9DfTfSpVhZO/) [2018-04-06 16:44:00] Pool sent a new job (ID: eKPkEyN1oL6zWI+vn4a3wzCw9mVW) [2018-04-06 16:44:02] Pool accepted result 0x0000E8F0 [2018-04-06 16:44:03] Pool difficulty: 499996 [2018-04-06 16:44:03] Pool sent a new job (ID: xfUrTkBCiD3l8Df9LnWkhCnFjKYt) [2018-04-06 16:44:04] Pool accepted result 0x0000770E [2018-04-06 16:44:17] GPU0[T0]: 348.0 H/S (T: 38c, RPM: 2037) [2018-04-06 16:44:17] GPU0[T1]: 349.0 H/S (T: 38c, RPM: 2037) [2018-04-06 16:44:17] GPU1[T2]: 351.0 H/S (T: 42c, RPM: 2247) [2018-04-06 16:44:17] GPU1[T3]: 346.0 H/S (T: 42c, RPM: 2247) [2018-04-06 16:44:17] GPU2[T4]: 349.0 H/S (T: 42c, RPM: 2269) [2018-04-06 16:44:17] GPU2[T5]: 350.0 H/S (T: 42c, RPM: 2269) [2018-04-06 16:44:17] GPU3[T6]: 349.0 H/S (T: 41c, RPM: 2315) [2018-04-06 16:44:17] GPU3[T7]: 347.0 H/S (T: 41c, RPM: 2315) [2018-04-06 16:44:17] GPU4[T8]: 342.0 H/S (T: 40c, RPM: 2216) [2018-04-06 16:44:17] GPU4[T9]: 354.0 H/S (T: 40c, RPM: 2216) [2018-04-06 16:44:17] GPU5[T10]: 348.0 H/S, (T: 51c, RPM: 1971) [2018-04-06 16:44:17] GPU5[T11]: 348.0 H/S, (T: 51c, RPM: 1971) [2018-04-06 16:44:17] GPU6[T12]: 349.0 H/S, (T: 41c, RPM: 2249) [2018-04-06 16:44:17] GPU6[T13]: 349.0 H/S, (T: 41c, RPM: 2249) [2018-04-06 16:44:17] GPU7[T14]: 349.0 H/S, (T: 40c, RPM: 2207) [2018-04-06 16:44:17] GPU7[T15]: 349.0 H/S, (T: 40c, RPM: 2207) [2018-04-06 16:44:17] Total: 5577.0 H/S
while at fairpool just work smooth:
[2018-04-06 16:47:47] Pool accepted result 0x001AB010 [2018-04-06 16:47:47] GPU0[T0]: 423.0 H/S (T: 40c, RPM: 2141) [2018-04-06 16:47:47] GPU0[T1]: 406.0 H/S (T: 40c, RPM: 2141) [2018-04-06 16:47:47] GPU1[T2]: 409.0 H/S (T: 44c, RPM: 2335) [2018-04-06 16:47:47] GPU1[T3]: 418.0 H/S (T: 44c, RPM: 2335) [2018-04-06 16:47:47] GPU2[T4]: 404.0 H/S (T: 46c, RPM: 2389) [2018-04-06 16:47:47] GPU2[T5]: 424.0 H/S (T: 46c, RPM: 2389) [2018-04-06 16:47:47] GPU3[T6]: 420.0 H/S (T: 44c, RPM: 2362) [2018-04-06 16:47:47] GPU3[T7]: 403.0 H/S (T: 44c, RPM: 2362) [2018-04-06 16:47:47] GPU4[T8]: 420.0 H/S (T: 43c, RPM: 2337) [2018-04-06 16:47:47] GPU4[T9]: 410.0 H/S (T: 43c, RPM: 2337) [2018-04-06 16:47:47] GPU5[T10]: 385.0 H/S, (T: 55c, RPM: 2008) [2018-04-06 16:47:47] GPU5[T11]: 398.0 H/S, (T: 55c, RPM: 2008) [2018-04-06 16:47:47] GPU6[T12]: 410.0 H/S, (T: 45c, RPM: 2379) [2018-04-06 16:47:47] GPU6[T13]: 418.0 H/S, (T: 45c, RPM: 2379) [2018-04-06 16:47:47] GPU7[T14]: 419.0 H/S, (T: 44c, RPM: 2345) [2018-04-06 16:47:47] GPU7[T15]: 405.0 H/S, (T: 44c, RPM: 2345) [2018-04-06 16:47:47] Total: 6572.0 H/S
Help please.....
|
|
|
|
peterboy1
Newbie
Offline
Activity: 168
Merit: 0
|
|
April 06, 2018, 09:23:49 AM |
|
sorry for the noobie question, but your premade start.bat is for the miner to restart right incase there is failure. now how to add parameters in your start.bat?
|
|
|
|
doktor83 (OP)
|
|
April 06, 2018, 09:27:24 AM |
|
sorry for the noobie question, but your premade start.bat is for the miner to restart right incase there is failure. now how to add parameters in your start.bat?
:START FOR /F %%x IN ('tasklist /NH /FI "IMAGENAME eq %EXE%"') DO IF %%x == %EXE% goto RUNNING %EXE% -c config.txt -addyourparameterhereTIMEOUT /T 15 /NOBREAK goto START
|
|
|
|
|