Bitcoin Forum
January 31, 2023, 04:52:14 AM *
News: Latest Bitcoin Core release: 24.0.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 [287] 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 ... 364 »
  Print  
Author Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching  (Read 236659 times)
shera037
Newbie
*
Offline Offline

Activity: 29
Merit: 0


View Profile
December 29, 2018, 12:35:54 PM
 #5721

for doktor83

ne mogu pm  Sad Sad Sad

pogaseno na pool-u

Quote
if exist {
      log.Printf("Duplicate share from %s@%s %v", login, cs.ip, params)
      //return false, &ErrorReply{Code: 22, Message: "Duplicate share"}
   }

   if !validShare {
      log.Printf("Invalid share from %s@%s", login, cs.ip)
      // Bad shares limit reached, return error and close
      if !ok {
         // return false, &ErrorReply{Code: 23, Message: "Invalid share"}
      }
      return false, nil
   }
   log.Printf("Valid share from %s@%s", login, cs.ip)

   cs.nextDiff = s.calcNewDiff(cs)

   if !ok {
      //return true, &ErrorReply{Code: -1, Message: "High rate of invalid shares"}
   }
return true, nil

zato ne prihvata a ne odgovori nista miner-u, jer kada odgovori sa ovim greskama otkacinje miner

1675140734
Hero Member
*
Offline Offline

Posts: 1675140734

View Profile Personal Message (Offline)

Ignore
1675140734
Reply with quote  #2

1675140734
Report to moderator
Make sure you back up your wallet regularly! Unlike a bank account, nobody can help you if you lose access to your BTC.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1675140734
Hero Member
*
Offline Offline

Posts: 1675140734

View Profile Personal Message (Offline)

Ignore
1675140734
Reply with quote  #2

1675140734
Report to moderator
zeef
Newbie
*
Offline Offline

Activity: 296
Merit: 0


View Profile
December 29, 2018, 01:48:44 PM
 #5722

For now I'm using your miners since month , but after 1.7.0 I cannot get my miners stable . All are running on 1.7.0 and crashing around once a week. I'm far from the best hashrate average 1920 h/s for all the rigs. I try to get the best hashrate but I do not know best setting for reference cards.
I post in the other thread too to get more chance to get help:-) latest version or srb and crashing and same for TRM..

This is the log at the crash ( same for all miners)
[2018-12-29 11:18:14] miner_result: Pool accepted result 0x000026A4
[2018-12-29 11:18:22] hashrate: GPU0: 1861 H/s [BUS:12]
[2018-12-29 11:18:22] hashrate: GPU1: 1927 H/s [BUS:27]
[2018-12-29 11:18:22] hashrate: GPU2: 1884 H/s [BUS:3]
[2018-12-29 11:18:22] hashrate: GPU3: 1923 H/s [BUS:18]
[2018-12-29 11:18:22] hashrate: GPU4: 1920 H/s [BUS:24]
[2018-12-29 11:18:22] hashrate: GPU5: 1943 H/s [BUS:9]
[2018-12-29 11:18:22] hashrate: GPU6: 1886 H/s [BUS:15]
[2018-12-29 11:18:22] hashrate: GPU7: 1927 H/s [BUS:21]
[2018-12-29 11:18:22] hashrate: Total: 15271 H/s
[2018-12-29 11:18:25] miner_result: Sending user result to pool
[2018-12-29 11:18:25] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"1","job_id":"64764","nonce":"ba8c00b0","result":"25c110c6e4606e5319aa9f5af76156e1e6b221c55237e4da8f175f06364e0000"}}
[2018-12-29 11:18:25] json_receive: {"id":1,"jsonrpc":"2.0","result":{"status":"OK"},"error":null}
[2018-12-29 11:18:25] miner_result: Pool accepted result 0x00004E36
[2018-12-29 11:18:32] miner_result: Sending user result to pool
[2018-12-29 11:18:32] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"1","job_id":"64764","nonce":"36a60090","result":"61d4bc628319756462503d5b2a998a43226065456c31c6de0a62e3b166450000"}}
[2018-12-29 11:18:32] json_receive: {"id":1,"jsonrpc":"2.0","result":{"status":"OK"},"error":null}
[2018-12-29 11:18:32] miner_result: Pool accepted result 0x00004566
[2018-12-29 11:18:33] miner_result: Sending user result to pool
[2018-12-29 11:18:33] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"1","job_id":"64764","nonce":"1ba60010","result":"bf043e2f595083f8bde62384eef736945926f626dbca4fe50e88b0041a6e0000"}}
[2018-12-29 11:18:33] json_receive: {"id":1,"jsonrpc":"2.0","result":{"status":"OK"},"error":null}
[2018-12-29 11:18:33] miner_result: Pool accepted result 0x00006E1A
[2018-12-29 11:18:43] miner_result: Sending user result to pool
[2018-12-29 11:18:43] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"1","job_id":"64764","nonce":"37cd0020","result":"60dc05569c283ab05b451d907bd4086b21778cb2783bffcbfa1b737465830000"}}
[2018-12-29 11:18:43] json_receive: {"id":1,"jsonrpc":"2.0","result":{"status":"OK"},"error":null}
[2018-12-29 11:18:43] miner_result: Pool accepted result 0x00008365
[2018-12-29 11:18:45] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"090986949de10534e1f20e6eae556262af5a2ac58b31c6cf93b046fa91ea55009542685ff6e9f40 0000000aae71b79d62e585c951fad9fce0d257235b57e05ea5533e283801246315a80de01","job_id":"64765","target":"cf8b0000"}}
[2018-12-29 11:18:45] pool_have_job: Pool sent a new job (ID: 64765)
[2018-12-29 11:18:57] miner_result: Sending user result to pool
[2018-12-29 11:18:57] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"1","job_id":"64765","nonce":"aa280040","result":"f84d394527ec04e5bf9dfab181fd968fd6fbaed3983a07fe751b3465c6460000"}}
[2018-12-29 11:18:57] json_receive: {"id":1,"jsonrpc":"2.0","result":{"status":"OK"},"error":null}
[2018-12-29 11:18:57] miner_result: Pool accepted result 0x000046C6
[2018-12-29 11:18:59] miner_result: Sending user result to pool
[2018-12-29 11:18:59] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"1","job_id":"64765","nonce":"75280090","result":"a9d09e3ca6e12eeb260451eaf4f67c7996b9be4a7ca86302e6280ad619300000"}}
[2018-12-29 11:19:00] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"090993949de105d961d240b17c4aa4a3e02d9d3d542ed8bd7692b27561a763f161e957a1b077ac0 0000000d332bb0ff3117b0060f9903e9d2be5808e5198984ab375eb39ad55ccbd6448d001","job_id":"64766","target":"cf8b0000"}}
[2018-12-29 11:19:00] json_receive: {"id":1,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Block expired"}}
[2018-12-29 11:19:00] pool_have_job: Pool sent a new job (ID: 64766)
[2018-12-29 11:19:17] miner_result: Sending user result to pool
[2018-12-29 11:19:17] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"1","job_id":"64766","nonce":"0f3300d0","result":"aad84fc4ac5913f6a513e57177aa113779e8882e21051d55fb5d7604cb070000"}}
[2018-12-29 11:19:17] json_receive: {"id":1,"jsonrpc":"2.0","result":{"status":"OK"},"error":null}
[2018-12-29 11:19:17] miner_result: Pool accepted result 0x000007CB
[2018-12-29 11:19:40] miner_result: Sending user result to pool
[2018-12-29 11:19:40] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"1","job_id":"64766","nonce":"df8b0070","result":"963eb439b4edfe088e79442d62d5a2a50d9a634489d30260f799b647075d0000"}}
[2018-12-29 11:19:40] json_receive: {"id":1,"jsonrpc":"2.0","result":{"status":"OK"},"error":null}
[2018-12-29 11:19:40] miner_result: Pool accepted result 0x00005D07
[2018-12-29 11:19:54] miner_result: Sending user result to pool
[2018-12-29 11:19:54] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"1","job_id":"64766","nonce":"09bc0040","result":"7403df0c0ee20430427622d4ac91b6c4f19e9c81655cc06409cf89a585210000"}}
[2018-12-29 11:19:54] json_receive: {"id":1,"jsonrpc":"2.0","result":{"status":"OK"},"error":null}
[2018-12-29 11:19:54] miner_result: Pool accepted result 0x00002185
[2018-12-29 11:20:00] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909cf949de105d961d240b17c4aa4a3e02d9d3d542ed8bd7692b27561a763f161e957a1b077ac0 0000000bbd2c3819f4b6f4a0cae913c63b6eb98688a653d5c2f786f2f17403ff183140a02","job_id":"64767","target":"cf8b0000"}}
[2018-12-29 11:20:00] pool_have_job: Pool sent a new job (ID: 64767)
[2018-12-29 11:20:03] watchdog: GPU0 [BUS: 12] hashing speed is 0 H/S
[2018-12-29 11:20:03] watchdog: GPU1 [BUS: 27] hashing speed is 0 H/S
[2018-12-29 11:20:03] watchdog: GPU4 [BUS: 24] hashing speed is 0 H/S
[2018-12-29 11:20:03] watchdog: GPU6 [BUS: 15] hashing speed is 0 H/S
[2018-12-29 11:20:14] watchdog: GPU0 [BUS: 12] hashing speed is 0 H/S
[2018-12-29 11:20:14] watchdog: GPU1 [BUS: 27] hashing speed is 0 H/S
[2018-12-29 11:20:14] watchdog: GPU4 [BUS: 24] hashing speed is 0 H/S
[2018-12-29 11:20:14] watchdog: GPU6 [BUS: 15] hashing speed is 0 H/S
[2018-12-29 11:20:23] hashrate: GPU0: 0 H/s [BUS:12]
[2018-12-29 11:20:23] hashrate: GPU1: 0 H/s [BUS:27]
[2018-12-29 11:20:23] hashrate: GPU2: 1885 H/s [BUS:3]
[2018-12-29 11:20:23] hashrate: GPU3: 1925 H/s [BUS:18]
[2018-12-29 11:20:23] hashrate: GPU4: 0 H/s [BUS:24]
[2018-12-29 11:20:23] hashrate: GPU5: 1943 H/s [BUS:9]
[2018-12-29 11:20:23] hashrate: GPU6: 0 H/s [BUS:15]
[2018-12-29 11:20:23] hashrate: GPU7: 1928 H/s [BUS:21]
[2018-12-29 11:20:23] hashrate: Total: 7681 H/s
[2018-12-29 11:20:25] watchdog: GPU crash detected, miner will try to restart
[2018-12-29 11:20:25] Restarting miner process

Same problem reported here since v1.7.1 or more the vega rig became unstable.  My rx580 rig have no problems with v1.7.4.
Vega 64 rig with v 1.7.4 get ramdom restarts, and i increase the mv in all gpus, lower intensity , and same problem!!
livada
Newbie
*
Offline Offline

Activity: 417
Merit: 0


View Profile WWW
December 29, 2018, 01:50:16 PM
 #5723


I am using two PSUs with a combined 1900w. The PSU is fine but the breaker is tripped. I also use overdriventool so the power consumption is around 1250w which is not bad at all for monero v8. It is just every few days I got this power surge. And after this happens, I have to start the miner few times to get a 1250w cause the first few starts always get a 1900w power so i have to stop the miner and restarted it.

It could be your intensity or overclock to much. Sometimes a gpu may crash and reset to default settings. Which on vega will increase power a lot. If ppt mod this won't happen.
Its not the software. Its your settings I would say

It makes sense. Could you take a look at my overdriventool setting? It is a vega 56 with 64 bios. memeory is set to 1100.

GPU_P0=852;800;0
GPU_P1=991;900;0
GPU_P2=1084;950;0
GPU_P3=1138;1000;0
GPU_P4=1200;1050;0
GPU_P5=1401;1100;0
GPU_P6=1536;1150;0
GPU_P7=1552;840
Mem_P0=167;800;0
Mem_P1=500;800;0
Mem_P2=800;950;0
Mem_P3=1100;875
Fan_Min=2750
Fan_Max=3500
Fan_Target=65
Fan_Acoustic=2400
Power_Temp=75
Power_Target=0

This is the v8 setting for miner.
{
"cryptonight_type" : "normalv8",
"intensity" : 120,
"worksize" : 16,
"double_threads" : true
}



Your PPT tabvle is BAD. This is not good.


USe this : 1130W form the WALL on v8 - i have 2*700W PSU only and all work fine with 6*vega 56 nitro+

GPU_P0=852;900;0
GPU_P1=991;900;0
GPU_P2=1084;900;0
GPU_P3=1138;900;0
GPU_P4=1150;900;0
GPU_P5=1202;900;0
GPU_P6=1212;900;0
GPU_P7=1442;900
Mem_P0=167;900;0
Mem_P1=500;900;0
Mem_P2=800;900;0
Mem_P3=1100;900
Fan_Min=2300
Fan_Max=4900
Fan_Target=56
Fan_Acoustic=2400
Power_Temp=75
Power_Target=0

or this for low consumation power

GPU_P0=852;800;0
GPU_P1=991;801;0
GPU_P2=1084;802;0
GPU_P3=1100;803;0
GPU_P4=1125;804;0
GPU_P5=1150;805;0
GPU_P6=1212;830;0
GPU_P7=1442;850
Mem_P0=167;800;0
Mem_P1=500;800;0
Mem_P2=800;802;0
Mem_P3=1100;860
Fan_Min=2300
Fan_Max=3500
Fan_Target=55
Fan_Acoustic=2400
Power_Temp=75
Power_Target=0
MingMining
Member
**
Offline Offline

Activity: 143
Merit: 10


View Profile
December 29, 2018, 10:02:38 PM
 #5724


I am using two PSUs with a combined 1900w. The PSU is fine but the breaker is tripped. I also use overdriventool so the power consumption is around 1250w which is not bad at all for monero v8. It is just every few days I got this power surge. And after this happens, I have to start the miner few times to get a 1250w cause the first few starts always get a 1900w power so i have to stop the miner and restarted it.

It could be your intensity or overclock to much. Sometimes a gpu may crash and reset to default settings. Which on vega will increase power a lot. If ppt mod this won't happen.
Its not the software. Its your settings I would say

It makes sense. Could you take a look at my overdriventool setting? It is a vega 56 with 64 bios. memeory is set to 1100.

GPU_P0=852;800;0
GPU_P1=991;900;0
GPU_P2=1084;950;0
GPU_P3=1138;1000;0
GPU_P4=1200;1050;0
GPU_P5=1401;1100;0
GPU_P6=1536;1150;0
GPU_P7=1552;840
Mem_P0=167;800;0
Mem_P1=500;800;0
Mem_P2=800;950;0
Mem_P3=1100;875
Fan_Min=2750
Fan_Max=3500
Fan_Target=65
Fan_Acoustic=2400
Power_Temp=75
Power_Target=0

This is the v8 setting for miner.
{
"cryptonight_type" : "normalv8",
"intensity" : 120,
"worksize" : 16,
"double_threads" : true
}



Your PPT tabvle is BAD. This is not good.


USe this : 1130W form the WALL on v8 - i have 2*700W PSU only and all work fine with 6*vega 56 nitro+

GPU_P0=852;900;0
GPU_P1=991;900;0
GPU_P2=1084;900;0
GPU_P3=1138;900;0
GPU_P4=1150;900;0
GPU_P5=1202;900;0
GPU_P6=1212;900;0
GPU_P7=1442;900
Mem_P0=167;900;0
Mem_P1=500;900;0
Mem_P2=800;900;0
Mem_P3=1100;900
Fan_Min=2300
Fan_Max=4900
Fan_Target=56
Fan_Acoustic=2400
Power_Temp=75
Power_Target=0

or this for low consumation power

GPU_P0=852;800;0
GPU_P1=991;801;0
GPU_P2=1084;802;0
GPU_P3=1100;803;0
GPU_P4=1125;804;0
GPU_P5=1150;805;0
GPU_P6=1212;830;0
GPU_P7=1442;850
Mem_P0=167;800;0
Mem_P1=500;800;0
Mem_P2=800;802;0
Mem_P3=1100;860
Fan_Min=2300
Fan_Max=3500
Fan_Target=55
Fan_Acoustic=2400
Power_Temp=75
Power_Target=0

Thanks Livada. I used this table and the power consumption is 30w less with almost same hashrate. Let's see if it can be stable for a while. My cards are all reference cards with 64 bios so it may consumes more power I guess.
livada
Newbie
*
Offline Offline

Activity: 417
Merit: 0


View Profile WWW
December 29, 2018, 11:01:59 PM
 #5725


I am using two PSUs with a combined 1900w. The PSU is fine but the breaker is tripped. I also use overdriventool so the power consumption is around 1250w which is not bad at all for monero v8. It is just every few days I got this power surge. And after this happens, I have to start the miner few times to get a 1250w cause the first few starts always get a 1900w power so i have to stop the miner and restarted it.

It could be your intensity or overclock to much. Sometimes a gpu may crash and reset to default settings. Which on vega will increase power a lot. If ppt mod this won't happen.
Its not the software. Its your settings I would say

It makes sense. Could you take a look at my overdriventool setting? It is a vega 56 with 64 bios. memeory is set to 1100.

GPU_P0=852;800;0
GPU_P1=991;900;0
GPU_P2=1084;950;0
GPU_P3=1138;1000;0
GPU_P4=1200;1050;0
GPU_P5=1401;1100;0
GPU_P6=1536;1150;0
GPU_P7=1552;840
Mem_P0=167;800;0
Mem_P1=500;800;0
Mem_P2=800;950;0
Mem_P3=1100;875
Fan_Min=2750
Fan_Max=3500
Fan_Target=65
Fan_Acoustic=2400
Power_Temp=75
Power_Target=0

This is the v8 setting for miner.
{
"cryptonight_type" : "normalv8",
"intensity" : 120,
"worksize" : 16,
"double_threads" : true
}



Your PPT tabvle is BAD. This is not good.


USe this : 1130W form the WALL on v8 - i have 2*700W PSU only and all work fine with 6*vega 56 nitro+

GPU_P0=852;900;0
GPU_P1=991;900;0
GPU_P2=1084;900;0
GPU_P3=1138;900;0
GPU_P4=1150;900;0
GPU_P5=1202;900;0
GPU_P6=1212;900;0
GPU_P7=1442;900
Mem_P0=167;900;0
Mem_P1=500;900;0
Mem_P2=800;900;0
Mem_P3=1100;900
Fan_Min=2300
Fan_Max=4900
Fan_Target=56
Fan_Acoustic=2400
Power_Temp=75
Power_Target=0

or this for low consumation power

GPU_P0=852;800;0
GPU_P1=991;801;0
GPU_P2=1084;802;0
GPU_P3=1100;803;0
GPU_P4=1125;804;0
GPU_P5=1150;805;0
GPU_P6=1212;830;0
GPU_P7=1442;850
Mem_P0=167;800;0
Mem_P1=500;800;0
Mem_P2=800;802;0
Mem_P3=1100;860
Fan_Min=2300
Fan_Max=3500
Fan_Target=55
Fan_Acoustic=2400
Power_Temp=75
Power_Target=0

Thanks Livada. I used this table and the power consumption is 30w less with almost same hashrate. Let's see if it can be stable for a while. My cards are all reference cards with 64 bios so it may consumes more power I guess.
if you use GPU_P7=1552mz thi use more power. try with 1440mhz and see. my card use 70W more if i use 1500+mhz for 100hr and temp go up 3-4C
MingMining
Member
**
Offline Offline

Activity: 143
Merit: 10


View Profile
December 30, 2018, 01:48:33 AM
 #5726



Thanks Livada. I used this table and the power consumption is 30w less with almost same hashrate. Let's see if it can be stable for a while. My cards are all reference cards with 64 bios so it may consumes more power I guess.
if you use GPU_P7=1552mz thi use more power. try with 1440mhz and see. my card use 70W more if i use 1500+mhz for 100hr and temp go up 3-4C

Thanks for the information, Livada. I will leave it for a while to make sure that one is stable. To me, stability is more important.
doktor83 (OP)
Hero Member
*****
Offline Offline

Activity: 2184
Merit: 625


View Profile WWW
December 30, 2018, 07:52:37 AM
Last edit: December 30, 2018, 09:39:21 AM by doktor83
 #5727


Same problem reported here since v1.7.1 or more the vega rig became unstable.  My rx580 rig have no problems with v1.7.4.
Vega 64 rig with v 1.7.4 get ramdom restarts, and i increase the mv in all gpus, lower intensity , and same problem!!

Driver version, algo, config file?

Does the miner restart, and work ok after that, or system freezes?
Can you describe ? Maybe i can find out what is happening

It was all ok on 1.7.0 ?

Also how often is this happening?
Is there any specific case you maybe noticed?

SRBMiner-MULTI thread - HERE
http://www.srbminer.com
GKumaran
Member
**
Offline Offline

Activity: 203
Merit: 10


View Profile
December 30, 2018, 09:41:42 AM
 #5728


Same problem reported here since v1.7.1 or more the vega rig became unstable.  My rx580 rig have no problems with v1.7.4.
Vega 64 rig with v 1.7.4 get ramdom restarts, and i increase the mv in all gpus, lower intensity , and same problem!!

Im running a Vega Rig, but has no such issues. Which algo are you having these issues?
doktor83 (OP)
Hero Member
*****
Offline Offline

Activity: 2184
Merit: 625


View Profile WWW
December 30, 2018, 09:42:40 AM
 #5729


Same problem reported here since v1.7.1 or more the vega rig became unstable.  My rx580 rig have no problems with v1.7.4.
Vega 64 rig with v 1.7.4 get ramdom restarts, and i increase the mv in all gpus, lower intensity , and same problem!!

Im running a Vega Rig, but has no such issues. Which algo are you having these issues?

Are you running the latest 1.7.4?

SRBMiner-MULTI thread - HERE
http://www.srbminer.com
abg00
Jr. Member
*
Offline Offline

Activity: 288
Merit: 1


View Profile
December 30, 2018, 10:37:53 AM
 #5730


Are you running the latest 1.7.4?

plz fix webchain algo and add rigid in new version
doktor83 (OP)
Hero Member
*****
Offline Offline

Activity: 2184
Merit: 625


View Profile WWW
December 30, 2018, 10:40:18 AM
 #5731

It's fixed, testing new version atm if all good i will upload it today

SRBMiner-MULTI thread - HERE
http://www.srbminer.com
sharix80
Newbie
*
Offline Offline

Activity: 31
Merit: 0


View Profile
December 30, 2018, 11:09:14 AM
 #5732

It's fixed, testing new version atm if all good i will upload it today

Good news. Thank you for your efficient work.
doktor83 (OP)
Hero Member
*****
Offline Offline

Activity: 2184
Merit: 625


View Profile WWW
December 30, 2018, 11:24:33 AM
 #5733

V1.7.5
- Added parameter --setup in cmd, which creates basic config files for user in interactive mode
- Added 'old_mode' parameter to config outside gpu_conf
- Added notification if using old kernel
- "worker" set in pools.txt now works for webchain too
- Fixed a few things regarding webchain mining


+ Added parameter --setup that creates basic configuration files for the user in an interactive mode. This is a quick way for beginners to set up everything and start mining.
Also added guided-setup.bat in the package that runs the --setup mode.

+ 'old_mode' was a gpu_conf only parameter until now

+ Webchain is a weird coin Smiley
To set the worker-id , use the 'worker' parameter in pools.txt file

SRBMiner-MULTI thread - HERE
http://www.srbminer.com
abg00
Jr. Member
*
Offline Offline

Activity: 288
Merit: 1


View Profile
December 30, 2018, 12:24:31 PM
 #5734

V1.7.5

+ Webchain is a weird coin Smiley
To set the worker-id , use the 'worker' parameter in pools.txt file

worker work
but no shares on webchain. hashrate on pool very low
abg00
Jr. Member
*
Offline Offline

Activity: 288
Merit: 1


View Profile
December 30, 2018, 12:57:39 PM
 #5735

1.7.5 bit more on 570\8gb card on tube algo
MadSciencist
Newbie
*
Offline Offline

Activity: 43
Merit: 0


View Profile
December 30, 2018, 12:58:13 PM
 #5736

I haven't mine cryptonight coins for long time. I wanted to switch for haven, but I'm getting only 400h per card (rx580 8GB).
I can set intensity to 270 and get over 1200 per card but SRBMiner is not submitting any hashes then. Anything over 50 intensity is not submitting any hashes (tried worksize 4, 8, 16, 32).
Any ideas?
zeef
Newbie
*
Offline Offline

Activity: 296
Merit: 0


View Profile
December 30, 2018, 01:17:33 PM
 #5737


Same problem reported here since v1.7.1 or more the vega rig became unstable.  My rx580 rig have no problems with v1.7.4.
Vega 64 rig with v 1.7.4 get ramdom restarts, and i increase the mv in all gpus, lower intensity , and same problem!!

Driver version, algo, config file?

Does the miner restart, and work ok after that, or system freezes?
Can you describe ? Maybe i can find out what is happening

It was all ok on 1.7.0 ?

Also how often is this happening?
Is there any specific case you maybe noticed?

Hi,

For me, yes all same version, algo and config only change version. Occured when i migrate from v1.7.0 to v1.7.2, v1.7.3 and v1.7.4.
For me occurs 4-6 hours. System freezes.

I notice that in v1.7.0 the auto intensity is set to 60 in my vega 64 setup, in version 1.7.4 the auto set to 56.
If i put 56 or 60 in v1.7.0 all ok, no crashes for days.. Smiley

Regards

carlosmonaco
Newbie
*
Offline Offline

Activity: 105
Merit: 0


View Profile
December 30, 2018, 01:26:14 PM
 #5738


Same problem reported here since v1.7.1 or more the vega rig became unstable.  My rx580 rig have no problems with v1.7.4.
Vega 64 rig with v 1.7.4 get ramdom restarts, and i increase the mv in all gpus, lower intensity , and same problem!!

Driver version, algo, config file?

Does the miner restart, and work ok after that, or system freezes?
Can you describe ? Maybe i can find out what is happening

It was all ok on 1.7.0 ?

Also how often is this happening?
Is there any specific case you maybe noticed?

For me I get some card hashing speed at 0h/s ( sometimes all together ), then miners restart by itself but failed to start , the system freeze ( restart needed) . I get that error more often after 1.7.0.
I post the log just above.
Windows 10 , Xmr ( V8) , 1.6.1.
PS : I tried to increase mV and lower clock speed and mem speed a lot but I still get this error since srb 1.7.1 on all rigs.
( No computing error before the crash , 1/24h for some)
abg00
Jr. Member
*
Offline Offline

Activity: 288
Merit: 1


View Profile
December 30, 2018, 02:17:13 PM
 #5739

I haven't mine cryptonight coins for long time. I wanted to switch for haven, but I'm getting only 400h per card (rx580 8GB).
I can set intensity to 270 and get over 1200 per card but SRBMiner is not submitting any hashes then. Anything over 50 intensity is not submitting any hashes (tried worksize 4, 8, 16, 32).
Any ideas?

write config here
compute mode on for this card?
i=57-59 for 8gb card
NCarter84
Jr. Member
*
Offline Offline

Activity: 195
Merit: 4


View Profile
December 30, 2018, 02:28:09 PM
 #5740

Dok - if we have all our stuff setup through the config-heavy, config-normalv8, config-mox, etc -- will we need to do anything new?

I have all my config files and pool files setup etc.
Pages: « 1 ... 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 [287] 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 ... 364 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!