Bitcoin Forum
November 18, 2019, 06:40:33 PM *
News: Latest Bitcoin Core release: 0.18.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 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 ... 367 »
  Print  
Author Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching  (Read 231206 times)
bruslie
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
November 12, 2018, 07:29:08 PM
 #5301

hy @doktor83

Good Job about 1850 H/s on Tube ! thx a lot

only thing dont work anymore is hotkeys  H for hash ore S for stats ...
1574102433
Hero Member
*
Offline Offline

Posts: 1574102433

View Profile Personal Message (Offline)

Ignore
1574102433
Reply with quote  #2

1574102433
Report to moderator
1574102433
Hero Member
*
Offline Offline

Posts: 1574102433

View Profile Personal Message (Offline)

Ignore
1574102433
Reply with quote  #2

1574102433
Report to moderator
The Bitcoin Forum is turning 10 years old! Join the community in sharing and exploring the notable posts made over the years.
livada
Newbie
*
Offline Offline

Activity: 395
Merit: 0


View Profile WWW
November 12, 2018, 08:02:33 PM
 #5302

hy @doktor83

Good Job about 1850 H/s on Tube ! thx a lot

only thing dont work anymore is hotkeys  H for hash ore S for stats ...

are you sure? that you were not a bit confused?
 give me SS your HR 5min and your option- 1850 in tube ?
H and S work fine in 1.7.0
hbouma
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
November 12, 2018, 08:32:01 PM
 #5303

what to do if you get compute errors?

also getting compute errors, can't shake them, on vega FEs, 18.q3.1-oct1 driver, Heavy

Try lowering you memory clock by 10mhs, and see if that helps

I have a question about this as well. I've been getting the computing errors on a card as well on 1.6.9, but HWInfo doesn't show any GPU memory errors for the card (8GB RX 470 with 1900 Mhz memory). How are you detecting this as an overclocking hardware error when the card isn't able to? Or that the error is subtle enough to not yet be detected by hwinfo? I've already dropped the clock rate from 2000 to 1900 even though 2000 wasn't reporting any GPU errors for CN algos or etherhash either. So it seems odd that I have to keep dropping it further.

Thanks for all the work you've done on this miner!

Hal
sky2018miner
Newbie
*
Offline Offline

Activity: 33
Merit: 0


View Profile
November 12, 2018, 08:36:33 PM
 #5304

version 1.6.4 there are no errors on all algorithms that I tried to use v7, fast stelite, heavy, haven
in newer versions there are pitching errors on pitcairn
so i am using old 1.6.4
  for v8 I use two miners
  your 1.6.9 with rx 460, r9 285 and alternative for pitcairn r7 370 which is inconvenient for work
tvukoman
Jr. Member
*
Offline Offline

Activity: 62
Merit: 5


View Profile
November 12, 2018, 09:05:50 PM
Last edit: November 12, 2018, 09:33:07 PM by tvukoman
 #5305

hy @doktor83

Good Job about 1850 H/s on Tube ! thx a lot

only thing dont work anymore is hotkeys  H for hash ore S for stats ...

are you sure? that you were not a bit confused?
 give me SS your HR 5min and your option- 1850 in tube ?
H and S work fine in 1.7.0

yes Livada, i think its possible.

On Vega Asus Strix 64 i have 1800 h/s on bittube2. If you have worksize 9 (old reccomendation for vega 64 and bittube2) try lower it to default 8. For me bump 100 h/s from 1699 to 1800 :-)



Edit: Up is just today quick test. After a while, h/s droped to 1770 but that is also great :-).
Settings: 1442/920 core, 1100/910 memory.
"id" : 2, "intensity" : 61, "worksize" : 8, "threads" : 2
livada
Newbie
*
Offline Offline

Activity: 395
Merit: 0


View Profile WWW
November 12, 2018, 10:22:02 PM
Last edit: November 12, 2018, 10:41:02 PM by livada
 #5306

hy @doktor83

Good Job about 1850 H/s on Tube ! thx a lot

only thing dont work anymore is hotkeys  H for hash ore S for stats ...

are you sure? that you were not a bit confused?
 give me SS your HR 5min and your option- 1850 in tube ?
H and S work fine in 1.7.0

yes Livada, i think its possible.

On Vega Asus Strix 64 i have 1800 h/s on bittube2. If you have worksize 9 (old reccomendation for vega 64 and bittube2) try lower it to default 8. For me bump 100 h/s from 1699 to 1800 :-)

http://i65.tinypic.com/w1w944.jpg

Edit: Up is just today quick test. After a while, h/s droped to 1770 but that is also great :-).
Settings: 1442/920 core, 1100/910 memory.
"id" : 2, "intensity" : 61, "worksize" : 8, "threads" : 2


This is very nice HR.
MY rig not work with tube/hevay/haven and 1.6.1 driver and srbminer1.6.4 .1.6.9
but with 1.7.0 work.vega 56 nitro with hynix have 1600HR
https://image.prntscr.com/image/xy0brYM3QRKb-ko35LHTxg.jpg
and i use JCE for tube/haven/heavy (1700Hr)
https://image.prntscr.com/image/Gj5n234vTayImL_2_74Ptg.jpg
sinephase
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
November 13, 2018, 02:12:34 AM
 #5307

I could use some advice! My hashrate for RX 570 4GB cards on windows 10 64 bit has dropped to about 300 H/s mining monero.

I was getting over 700 H/s on these 2 days ago. I woke up to windows restarted and reverted back to 17 Relive drivers that I used to have installed for mining a few months ago. Now all the cards are only mining at 300 and I get warnings that they are dropping to 0 at some points.
I reinstalled with a clean install of 18.6.1 drivers and still have the same issue. I tried again with 18.11.1 and only 1 card, same issue. I'm using 1x risers and have backed off of any clock changes to stock, same problems.
I have an EVGA 1000 watt GQ PSU and only installed Comodo security on this computer. Other than trying to reinstall windows, I'm not sure what else could be the issue. Any tips would be appreciated! Thanks!
phuongitdl
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
November 13, 2018, 02:18:41 AM
 #5308

i am more interested in your pools file, have you defined a 'cryptonight_type' for the monero ocean pool?
Code:
{
"pools" :
[
{
"pool" : "gulf.moneroocean.stream:10064",
"wallet" : "someaddress",
"password" : "MinerSRBAuto:someemail@yahoo.com"
},
{
"pool" : "gulf.moneroocean.stream:10064",
"wallet" : "someaddress",
"password" : "MinerSRBAuto:someemail@yahoo.com"
}
]
}

Let me configure config.txt
thanks

OK, so no 'cryptonight_type' set here for MO. That's good.
Maybe you could try dropping the --forcedshutdown, and let the miner release the gpu resources before restarting, let's see is that going to help.

Same issue even without the --forcedshutdown :

Code:
[2018-11-11 14:06:36] miner_result: Sending user result to pool
[2018-11-11 14:06:36] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"3e1c2dcc-ce42-4712-b638-31a9485ce557","job_id":"wq6pDg+25VtBo7gaXQa7CebyLY0a","nonce":"8f9a5855","result":"a00c81d8d7272917d59e28d93a05495df4b64261aa242e27ff2a013895260000","algo":"cn/2"}}
[2018-11-11 14:06:36] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2018-11-11 14:06:36] miner_result: Pool accepted result 0x00002695
[2018-11-11 14:06:59] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909e4b6a0df05cfe653a87512bb81ca829c8902bc3211f297bdd0ea74ebebc645a63aa77926d500000000c4c2b3b1fd2b60fec3ebd2e0f9f991eb163dddb2842121cb1dad917c190899df0a","algo":"cn/2","variant":"2","job_id":"2OiAvtwB6oSaye9aWtZV+1XvRKEw","target":"c55d0000","id":"3e1c2dcc-ce42-4712-b638-31a9485ce557"}}
[2018-11-11 14:06:59] pool_have_job: Pool sent a new job (ID: 2OiAvtwB6oSaye9aWtZV+1XvRKEw) [normalv8]
[2018-11-11 14:07:10] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909eeb6a0df05d642cbd7021a28f075cbe5efb758164cd17afbc7f7c616947f8272adcbea6289000000001e01c1da1415b9933a5eab5aeb4df30ec126c136aafae218625dca2178b5b6a004","algo":"cn/2","variant":"2","job_id":"0Qop3NIK9e9KEv2Y6evPw9t5oEMi","target":"525e0000","id":"3e1c2dcc-ce42-4712-b638-31a9485ce557"}}
[2018-11-11 14:07:46] hashrate: GPU0: 898 H/s [BUS:6]
[2018-11-11 14:07:46] hashrate: GPU1: 2071 H/s [BUS:9]
[2018-11-11 14:07:46] hashrate: GPU2: 2033 H/s [BUS:3]
[2018-11-11 14:07:46] hashrate: Total: 5002 H/s
[2018-11-11 14:08:01] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0303bfb6a0df05ca2eca4f2aa7f0f671c084d71395005494165d48195beaac7e8056898e470e6800000000b565223ce7209f0ea3df853fd1da74048ec03ef67d8e7475225c0195001bd44d02","algo":"cn-heavy/xhv","variant":"xhv","job_id":"/AMlUbG+Z2/14tLhLr+uc35Gyp0Q","target":"525e0000","id":"3e1c2dcc-ce42-4712-b638-31a9485ce557"}}
[2018-11-11 14:08:01] algo_switch: Pool requested algo switch to [haven]
[2018-11-11 14:08:06] ocl_release: Device BUS_ID6 thread0 resources released
[2018-11-11 14:08:06] ocl_release: Device BUS_ID6 thread1 resources released
[2018-11-11 14:08:06] ocl_release: Device BUS_ID9 thread2 resources released
[2018-11-11 14:08:06] ocl_release: Device BUS_ID9 thread3 resources released
[2018-11-11 14:08:06] ocl_release: Device BUS_ID3 thread4 resources released
[2018-11-11 14:08:06] ocl_release: Device BUS_ID3 thread5 resources released
[2018-11-11 14:08:06] Restarting miner with haven algo
[2018-11-11 14:08:07] Miner version: 1.7.0
[2018-11-11 14:08:07] Windows version: 10.0 build 16299
[2018-11-11 14:08:07] Video driver version: 24.20.11021.1000
[2018-11-11 14:08:08] AMD Platform ID: 1
[2018-11-11 14:08:08] AMD platform FOUND
[2018-11-11 14:08:08] Found 3 AMD devices
[2018-11-11 14:08:08] CPU AES-NI: TRUE
[2018-11-11 14:08:08] GPU0: Radeon RX 580 Series [ellesmere] [8192 MB][I: 56.0][W: 8][T: 2][F: 0][A: 0][BUS: 6]
[2018-11-11 14:08:08] GPU1: Radeon RX Vega [gfx900] [8176 MB][I: 62.0][W: 8][T: 2][F: 1][A: 0][BUS: 9]
[2018-11-11 14:08:08] GPU2: Radeon RX Vega [gfx900] [8176 MB][I: 62.0][W: 8][T: 2][F: 1][A: 0][BUS: 3]
[2018-11-11 14:08:08] ADL is enabled
[2018-11-11 14:08:08] Algo switching mode enabled
[2018-11-11 14:08:08] Algo switch minimum time : 60 seconds
[2018-11-11 14:08:08] Cryptonight Haven mode enabled
[2018-11-11 14:08:08] Startup monitor disabled!!
[2018-11-11 14:08:08] Watchdog is in GPU disable mode
[2018-11-11 14:08:08] Starting init of mining threads
[2018-11-11 14:08:08] Created OCL context
[2018-11-11 14:08:08] Using kernel 1 for DeviceID 0 (Thread 0)
[2018-11-11 14:08:08] Using AES 0 for DeviceID 0 (Thread 0)
[2018-11-11 14:08:09] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-11-11 14:08:09] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-11-11 14:08:09] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-11-11 14:08:09] Loading haven kernel for DEVICE BUS_ID[6] ...
[2018-11-11 14:08:09] ctx->Program for DeviceID 0 (Thread 0) loaded
[2018-11-11 14:08:09] Using kernel 1 for DeviceID 0 (Thread 1)
[2018-11-11 14:08:09] Using AES 0 for DeviceID 0 (Thread 1)
[2018-11-11 14:08:09] Created OCL command queue for DeviceID 0 (Thread 1)
[2018-11-11 14:08:09] Created OCL input buffer for DeviceID 0 (Thread 1)
[2018-11-11 14:08:09] Created OCL output buffer for DeviceID 0 (Thread 1)
[2018-11-11 14:08:09] Loading haven kernel for DEVICE BUS_ID[6] ...
[2018-11-11 14:08:09] ctx->Program for DeviceID 0 (Thread 1) loaded
[2018-11-11 14:08:09] Using kernel 1 for DeviceID 1 (Thread 2)
[2018-11-11 14:08:09] Using AES 0 for DeviceID 1 (Thread 2)
[2018-11-11 14:08:09] Created OCL command queue for DeviceID 1 (Thread 2)
[2018-11-11 14:08:09] Created OCL input buffer for DeviceID 1 (Thread 2)
[2018-11-11 14:08:09] Created OCL output buffer for DeviceID 1 (Thread 2)
[2018-11-11 14:08:09] Loading haven kernel for DEVICE BUS_ID[9] ...
[2018-11-11 14:08:09] ctx->Program for DeviceID 1 (Thread 2) loaded
[2018-11-11 14:08:09] Using kernel 1 for DeviceID 1 (Thread 3)
[2018-11-11 14:08:09] Using AES 0 for DeviceID 1 (Thread 3)
[2018-11-11 14:08:09] Created OCL command queue for DeviceID 1 (Thread 3)
[2018-11-11 14:08:09] Created OCL input buffer for DeviceID 1 (Thread 3)
[2018-11-11 14:08:09] Created OCL output buffer for DeviceID 1 (Thread 3)
[2018-11-11 14:08:09] Loading haven kernel for DEVICE BUS_ID[9] ...
[2018-11-11 14:08:09] ctx->Program for DeviceID 1 (Thread 3) loaded
[2018-11-11 14:08:09] Using kernel 1 for DeviceID 2 (Thread 4)
[2018-11-11 14:08:09] Using AES 0 for DeviceID 2 (Thread 4)
[2018-11-11 14:08:09] Created OCL command queue for DeviceID 2 (Thread 4)
[2018-11-11 14:08:09] Created OCL input buffer for DeviceID 2 (Thread 4)
[2018-11-11 14:08:09] Created OCL output buffer for DeviceID 2 (Thread 4)
[2018-11-11 14:08:09] Loading haven kernel for DEVICE BUS_ID[3] ...
[2018-11-11 14:08:09] ctx->Program for DeviceID 2 (Thread 4) loaded
[2018-11-11 14:08:09] Using kernel 1 for DeviceID 2 (Thread 5)
[2018-11-11 14:08:09] Using AES 0 for DeviceID 2 (Thread 5)
[2018-11-11 14:08:10] Created OCL command queue for DeviceID 2 (Thread 5)
[2018-11-11 14:08:10] Created OCL input buffer for DeviceID 2 (Thread 5)
[2018-11-11 14:08:10] Created OCL output buffer for DeviceID 2 (Thread 5)
[2018-11-11 14:08:10] Loading haven kernel for DEVICE BUS_ID[3] ...
[2018-11-11 14:08:10] ctx->Program for DeviceID 2 (Thread 5) loaded


Here is another example:

Code:
[2018-11-11 21:30:57] pool_have_job: Pool sent a new job (ID: C7rG/ktMelBnqecGjwZ4B7IHWrYI) [heavy]
[2018-11-11 21:31:07] hashrate: GPU0: 862 H/s [BUS:6]
[2018-11-11 21:31:07] hashrate: GPU1: 1824 H/s [BUS:9]
[2018-11-11 21:31:07] hashrate: GPU2: 1839 H/s [BUS:3]
[2018-11-11 21:31:07] hashrate: Total: 4525 H/s
[2018-11-11 21:31:14] miner_result: Sending user result to pool
[2018-11-11 21:31:14] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"b4174d6c-8e0a-4501-88e6-3b23be0bf002","job_id":"C7rG/ktMelBnqecGjwZ4B7IHWrYI","nonce":"bd895555","result":"a1ac490f1fa789d050cac33f9f69737e8b0f98056e95062cb08fb3abe68f0000","algo":"cn-heavy/0"}}
[2018-11-11 21:31:14] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2018-11-11 21:31:14] miner_result: Pool accepted result 0x00008FE6
[2018-11-11 21:31:22] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909f486a2df052672f4b8497a74004740f17edc88cc2060eee8b8e05ae44d8628ec4ba61f255c0000000054e994d89e12ef7a2bf0163bba167f28289d312a3cb41bc06a96450822fd7e3901","algo":"cn-heavy/0","variant":"0","job_id":"GwH9wLBXtga3biaCDI5jPglYJJjf","target":"715e0000","id":"b4174d6c-8e0a-4501-88e6-3b23be0bf002"}}
[2018-11-11 21:31:22] pool_have_job: Pool sent a new job (ID: GwH9wLBXtga3biaCDI5jPglYJJjf) [heavy]
[2018-11-11 21:31:32] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"09099787a2df05a737f3dffb57b3533acf95d6f664f9adc68e93dee936750489f1542def83d93d00000000fe9dd9dbc25cbcb81754c4c4d9a96bf16b879121dcd4d6230557a17768ecbcae02","algo":"cn-heavy/0","variant":"0","job_id":"0LgUbPmJKHDKrbAbzGAf7zLUYGyP","target":"715e0000","id":"b4174d6c-8e0a-4501-88e6-3b23be0bf002"}}
[2018-11-11 21:31:32] pool_have_job: Pool sent a new job (ID: 0LgUbPmJKHDKrbAbzGAf7zLUYGyP) [heavy]
[2018-11-11 21:32:08] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0303f485a2df0503eae94e64af7b34bf11c6026c9af59511333a7e972039caaa5055cd05b3a5c200000000551b1e9077a8e4e52ced040f69bcb5f0abab07f336942460114aaabfcc229afe03","algo":"cn-heavy/xhv","variant":"xhv","job_id":"9mrvdpzan44ClfsiWDkxy2gNwsyx","target":"715e0000","id":"b4174d6c-8e0a-4501-88e6-3b23be0bf002"}}
[2018-11-11 21:32:30] algo_switch: Pool requested algo switch to [haven]
[2018-11-11 21:32:34] ocl_release: Device BUS_ID6 thread0 resources released
[2018-11-11 21:32:34] ocl_release: Device BUS_ID6 thread1 resources released
[2018-11-11 21:32:34] ocl_release: Device BUS_ID9 thread2 resources released
[2018-11-11 21:32:34] ocl_release: Device BUS_ID9 thread3 resources released
[2018-11-11 21:32:34] ocl_release: Device BUS_ID3 thread4 resources released
[2018-11-11 21:32:34] ocl_release: Device BUS_ID3 thread5 resources released
[2018-11-11 21:32:34] Restarting miner with haven algo
[2018-11-11 21:32:35] Miner version: 1.7.0
[2018-11-11 21:32:35] Windows version: 10.0 build 16299
[2018-11-11 21:32:35] Video driver version: 24.20.11021.1000
[2018-11-11 21:32:37] AMD Platform ID: 1
[2018-11-11 21:32:37] AMD platform FOUND
[2018-11-11 21:32:37] Found 3 AMD devices
[2018-11-11 21:32:37] CPU AES-NI: TRUE
[2018-11-11 21:32:37] GPU0: Radeon RX 580 Series [ellesmere] [8192 MB][I: 56.0][W: 8][T: 2][F: 0][A: 0][BUS: 6]
[2018-11-11 21:32:37] GPU1: Radeon RX Vega [gfx900] [8176 MB][I: 62.0][W: 8][T: 2][F: 1][A: 0][BUS: 9]
[2018-11-11 21:32:37] GPU2: Radeon RX Vega [gfx900] [8176 MB][I: 62.0][W: 8][T: 2][F: 1][A: 0][BUS: 3]
[2018-11-11 21:32:37] ADL is enabled
[2018-11-11 21:32:37] Algo switching mode enabled
[2018-11-11 21:32:37] Algo switch minimum time : 60 seconds
[2018-11-11 21:32:37] Cryptonight Haven mode enabled
[2018-11-11 21:32:37] Startup monitor disabled!!
[2018-11-11 21:32:37] Watchdog is in GPU disable mode
[2018-11-11 21:32:37] Starting init of mining threads
[2018-11-11 21:32:37] Created OCL context
[2018-11-11 21:32:37] Using kernel 1 for DeviceID 0 (Thread 0)
[2018-11-11 21:32:37] Using AES 0 for DeviceID 0 (Thread 0)
[2018-11-11 21:32:37] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-11-11 21:32:37] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-11-11 21:32:37] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-11-11 21:32:37] Loading haven kernel for DEVICE BUS_ID[6] ...
[2018-11-11 21:32:37] ctx->Program for DeviceID 0 (Thread 0) loaded
[2018-11-11 21:32:37] Using kernel 1 for DeviceID 0 (Thread 1)
[2018-11-11 21:32:37] Using AES 0 for DeviceID 0 (Thread 1)
[2018-11-11 21:32:37] Created OCL command queue for DeviceID 0 (Thread 1)
[2018-11-11 21:32:37] Created OCL input buffer for DeviceID 0 (Thread 1)
[2018-11-11 21:32:37] Created OCL output buffer for DeviceID 0 (Thread 1)
[2018-11-11 21:32:37] Loading haven kernel for DEVICE BUS_ID[6] ...
[2018-11-11 21:32:37] ctx->Program for DeviceID 0 (Thread 1) loaded
[2018-11-11 21:32:37] Using kernel 1 for DeviceID 1 (Thread 2)
[2018-11-11 21:32:37] Using AES 0 for DeviceID 1 (Thread 2)
[2018-11-11 21:32:37] Created OCL command queue for DeviceID 1 (Thread 2)
[2018-11-11 21:32:37] Created OCL input buffer for DeviceID 1 (Thread 2)
[2018-11-11 21:32:37] Created OCL output buffer for DeviceID 1 (Thread 2)
[2018-11-11 21:32:37] Loading haven kernel for DEVICE BUS_ID[9] ...
[2018-11-11 21:32:37] ctx->Program for DeviceID 1 (Thread 2) loaded
[2018-11-11 21:32:37] Using kernel 1 for DeviceID 1 (Thread 3)
[2018-11-11 21:32:37] Using AES 0 for DeviceID 1 (Thread 3)
[2018-11-11 21:32:37] Created OCL command queue for DeviceID 1 (Thread 3)
[2018-11-11 21:32:37] Created OCL input buffer for DeviceID 1 (Thread 3)
[2018-11-11 21:32:37] Created OCL output buffer for DeviceID 1 (Thread 3)
[2018-11-11 21:32:37] Loading haven kernel for DEVICE BUS_ID[9] ...
[2018-11-11 21:32:37] ctx->Program for DeviceID 1 (Thread 3) loaded
[2018-11-11 21:32:37] Using kernel 1 for DeviceID 2 (Thread 4)
[2018-11-11 21:32:37] Using AES 0 for DeviceID 2 (Thread 4)
[2018-11-11 21:32:38] Created OCL command queue for DeviceID 2 (Thread 4)
[2018-11-11 21:32:38] Created OCL input buffer for DeviceID 2 (Thread 4)
[2018-11-11 21:32:38] Created OCL output buffer for DeviceID 2 (Thread 4)

The miner just randomly seems to crash and the miner window gets closed. This seems to be some code exception that closes the miner.
It seems to only happen immediately after an algo switch. Would you be so kind to check the code again to see what could possibly close the miner abruptly when performing algo switch? Maybe some kind of race condition? I am also forced to use --resetmineronalgoswitch since i have some vega`s.



 



phuongitdl
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
November 13, 2018, 02:24:42 AM
 #5309

Now testing:

8x RX580 8GB
cclock 1250, mclock 2150, cvddc 910, mvddc 910
drivers 18.3.2
miner 1.7.0

algo Haven

intensity 58
worksize 16
thread 2
fragments 8

Hashrate 1152


before on 1.6.7 with intensity 58 ...  hashrate 1120

looking stable for now


Let me configure config.txt
charles2k
Sr. Member
****
Offline Offline

Activity: 323
Merit: 250


View Profile
November 13, 2018, 03:20:27 AM
 #5310

Any experience with R9 Fury cards? What is the best setting for them? (V8 and heavy) ?
djim123
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
November 13, 2018, 04:00:49 AM
 #5311

V1.6.9 vs V1.7.0 V8 comparison on my 7x Vega 56's


Vega #1 1891 1910 + 19 H/s
Vega #2 1871 1893 + 22 H/s
Vega #3 1884 1904 + 20 H/s
Vega #4 1852 1869 + 17 H/s
Vega #5 1844 1865 + 21 H/s
Vega #6 1855 1874 + 19 H/s
Vega #7 1840 1863 + 23 H/s
---------------------------------
Totals   13037 13178 +141 H/s or about +20 H/s for each Vega 56


Thx doc !~!

Can You share ,settings and configuration,please.

All settings for SRBMiner are the same for each Vega 56 and done in the V8 config file:

intensity: 112
worksize: 16
threads: 2

Vega 56's #1, #2 and #3 are in one system that has Radeon Adrenalin Edition 18.8.1 installed which actually produces high hash rates than the recommended Radeon Adrenalin Edition 18.5.1 installed in the system with Vega 56's #4, #5, #6 and #7.

These two systems are on a Biostar H81A motherboard and are using a single HP 1200 Watt Server Power Supply (87% Efficient) with a 17x 6-pin Breakout board. The motherboard is powered by an 180 watt Pico PSU that gets it's 12 volt input from a 6-pin connector on the breakout board. I like my systems only running on a single power supply.


System one is hashing on an  i3-4340 at 73 H/s and system two is hashing on an  i5-4570 at 195 H/s.

All power measurements are done at the wall with a Power Usage Monitor. That way the entire system is measured (motherboard, processor, memory, ssd) and the Vega 56's and it is the real power not the incomplete ones that only look at the software measurements like HWINFO which does not consider the inefficiencies of power supply and internal power conversion circuits or the rest of the system.

Realize that V8 is much more power hungry than V7 was.

I do not use soft power play tables as I have found that V7 and V8 basically run between P6 & P7 states on the core and P3 on memory. The Vega 56's are reference designs of various vendors with stock BIOS.

So my Wattman settings for six of the Vega 56's are:

Core:
Min P6 1212 MHz @ 905 mv
Max P7 1452 MHz @ 925 mv

Memory:
Min/Max P3 935 MHz @ 900 mv

Fans:
Min: 2700
Target: 4900

Temperature:
Max: 75
Target: 65

I do have one problematic Vega 56 that I have to run at:

Core:
Min P6 1212 MHz @ 960 mv
Max P7 1452 MHz @ 985 mv

Memory:
Min/Max P3 900 MHz @ 950 mv

With all that out of the way here are the final numbers:

System one 3x Vega 56's:

Vega #1 1911 H/s
Vega #2 1893 H/s
Vega #3 1904 H/s
--------------------
Total  Vega's 5708 H/s
i3-4340 adds 73 H/s
-------------------------
System Total:  5781 H/s

Total Power at the wall: 675 watts


System two 4x Vega 56's:

Vega #4 1869 H/s
Vega #5 1865 H/s
Vega #6 1874 H/s
Vega #7 1863 H/s
--------------------
Total  Vega's 7471 H/s
i5-4570 adds 195 H/s
-------------------------
System Total:  7666 H/s

Total Power at the wall: 898 watts






Thank You very much ,Sir

I forgot this setting ( I have since edited my original post)

EDIT: I forgot this setting. I needed to do this +10 as a few of the Vega 56's clocks were only in the high 1200's MHz and not the 1350+ MHz they should be and were flicking between P6 and P7 state.. It turned out those were being power limited. So be sure to do this setting also.
Power Limit +10

Thank You.
MinersRus
Member
**
Offline Offline

Activity: 203
Merit: 15


View Profile
November 13, 2018, 04:02:51 AM
 #5312

V1.6.9 vs V1.7.0 V8 comparison on my 7x Vega 56's


Vega #1 1891 1910 + 19 H/s
Vega #2 1871 1893 + 22 H/s
Vega #3 1884 1904 + 20 H/s
Vega #4 1852 1869 + 17 H/s
Vega #5 1844 1865 + 21 H/s
Vega #6 1855 1874 + 19 H/s
Vega #7 1840 1863 + 23 H/s
---------------------------------
Totals   13037 13178 +141 H/s or about +20 H/s for each Vega 56


Thx doc !~!

Quote
Did you bios mod your cards?

No

Quote
Did you use soft power play table?

No

Quote
XMR-stak did not work anymore for me so I am trying to use srbminer now. Any link or pointer would be appreciated.

Complete configuration details are here:

https://bitcointalk.org/index.php?topic=3167363.msg47808740#msg47808740
Elder III
Sr. Member
****
Offline Offline

Activity: 1064
Merit: 270


View Profile
November 13, 2018, 05:09:07 AM
 #5313

I could use some advice! My hashrate for RX 570 4GB cards on windows 10 64 bit has dropped to about 300 H/s mining monero.

I was getting over 700 H/s on these 2 days ago. I woke up to windows restarted and reverted back to 17 Relive drivers that I used to have installed for mining a few months ago. Now all the cards are only mining at 300 and I get warnings that they are dropping to 0 at some points.
I reinstalled with a clean install of 18.6.1 drivers and still have the same issue. I tried again with 18.11.1 and only 1 card, same issue. I'm using 1x risers and have backed off of any clock changes to stock, same problems.
I have an EVGA 1000 watt GQ PSU and only installed Comodo security on this computer. Other than trying to reinstall windows, I'm not sure what else could be the issue. Any tips would be appreciated! Thanks!

My first thought is to ask if you put each GPU in Compute Mode in Radeon Settings?
dingdongtobias
Newbie
*
Offline Offline

Activity: 152
Merit: 0


View Profile
November 13, 2018, 05:12:22 AM
 #5314


This is very nice HR.
MY rig not work with tube/hevay/haven and 1.6.1 driver and srbminer1.6.4 .1.6.9
but with 1.7.0 work.vega 56 nitro with hynix have 1600HR
and i use JCE for tube/haven/heavy (1700Hr)

jce hashrate drop after 1 hour 15% und fee 2% = total loss
abg00
Jr. Member
*
Offline Offline

Activity: 218
Merit: 1


View Profile
November 13, 2018, 06:13:52 AM
 #5315

The card and driver:

4. Also dont use 18.3.4
why? on heavy 18.3.4 is best rate for rx470\480\570\580 8 gb card and for rx560 4 gb card
test lot of times and reinstall 18.3.4 again
ivomm
Sr. Member
****
Online Online

Activity: 822
Merit: 401


All good things to those who wait


View Profile
November 13, 2018, 08:43:13 AM
 #5316

What is the best intensity for heavy/haven algo for 570 cards? Mine are about 700 on auto. Above intesity 34-ish they crash. On v8 they work perfect with intensity 59 ~ 940 h/s.
Kgonla
Newbie
*
Offline Offline

Activity: 128
Merit: 0


View Profile
November 13, 2018, 10:03:41 AM
 #5317

Some tricks for finding best intensity:

First of all, I'm talking about Rx 4-5 cards don't know about vegas.

Since version 1.7.0 lowering intensity from what you where using in 1.6.9 or older, gives better H/s

Run SRBMiner, let about a minute & go pressing H every 20-30 sec.
If you see 0 H/s Int is toooo High
If you see H/s going up & down, for example 900 - 700 - 850... Int is too high

In 1.6.9 and previous you have a point where the H/s was the best just with 1 or a few numbers down to the one you give the unstable H/s, since 1.7.0 it is different...

One example:
With my RX 580 4GB:
1.6.9 and previous - Best I = 61 - Setting 62 I have unstable H/s & 0's - About 1000 H/s
1.7.0 - Best I = 54 - Setting 55 or higher H/s go down, 950, 900 but is stable not like before - About 1012-1015 H/s

With my RX 580 8GB, in 1.6.9 best Int was 116, with 1.7.0 best is 100

For Heavy algo you need to use about half Int than with v8
The less the memory your card have, the lower the Int must be

In my tests the best I find for V8 is:

RX 580 4 GB
"intensity" : 54, "worksize" : 8, "threads" : 2, "fragments" : 16, "bralock" : 50
RX 580 8 GB
"intensity" : 100, "worksize" : 8, "threads" : 2, "fragments" : 16, "bralock" : 50

bralock does not do much & is not very sensitive, using 40, 50, 60 I don't see changes but H/s looks more stable
using new AES does nothing for me so I let the default 0

Expend 30 mintues tuning & you will have the best values for you.
FloppyPurpleGherkin
Jr. Member
*
Offline Offline

Activity: 200
Merit: 2


View Profile
November 13, 2018, 01:31:52 PM
 #5318

Some tricks for finding best intensity:

First of all, I'm talking about Rx 4-5 cards don't know about vegas.

Since version 1.7.0 lowering intensity from what you where using in 1.6.9 or older, gives better H/s

Run SRBMiner, let about a minute & go pressing H every 20-30 sec.
If you see 0 H/s Int is toooo High
If you see H/s going up & down, for example 900 - 700 - 850... Int is too high

In 1.6.9 and previous you have a point where the H/s was the best just with 1 or a few numbers down to the one you give the unstable H/s, since 1.7.0 it is different...

One example:
With my RX 580 4GB:
1.6.9 and previous - Best I = 61 - Setting 62 I have unstable H/s & 0's - About 1000 H/s
1.7.0 - Best I = 54 - Setting 55 or higher H/s go down, 950, 900 but is stable not like before - About 1012-1015 H/s

With my RX 580 8GB, in 1.6.9 best Int was 116, with 1.7.0 best is 100

For Heavy algo you need to use about half Int than with v8
The less the memory your card have, the lower the Int must be

In my tests the best I find for V8 is:

RX 580 4 GB
"intensity" : 54, "worksize" : 8, "threads" : 2, "fragments" : 16, "bralock" : 50
RX 580 8 GB
"intensity" : 100, "worksize" : 8, "threads" : 2, "fragments" : 16, "bralock" : 50

bralock does not do much & is not very sensitive, using 40, 50, 60 I don't see changes but H/s looks more stable
using new AES does nothing for me so I let the default 0

Expend 30 mintues tuning & you will have the best values for you.


Good info! Thanks.
livada
Newbie
*
Offline Offline

Activity: 395
Merit: 0


View Profile WWW
November 13, 2018, 03:44:07 PM
Last edit: November 13, 2018, 04:05:43 PM by livada
 #5319


This is very nice HR.
MY rig not work with tube/hevay/haven and 1.6.1 driver and srbminer1.6.4 .1.6.9
but with 1.7.0 work.vega 56 nitro with hynix have 1600HR
and i use JCE for tube/haven/heavy (1700Hr)

jce hashrate drop after 1 hour 15% und fee 2% = total loss

Mybe for you . on my rig HR is constant . Fee is BAD but 2,1% - 0,9% = 1,1% fee
1.70 give me 9559HR JCE give me 10110HR . 10110-9550 = 560HR .This is 5,5% more for JCE . 5,5-1,1 = 4,4% more on JCE
or
SRB 9550HR - 0,89% fee = 9465HR
https://image.prntscr.com/image/xy0brYM3QRKb-ko35LHTxg.jpg
JCE =10110HR - 2,1% fee =9898HR
https://image.prntscr.com/image/Gj5n234vTayImL_2_74Ptg.jpg

this is for vega 56 nitro with hynix mem. i not try srb1.7.0 with referent vega56 and vega 64
dingdongtobias
Newbie
*
Offline Offline

Activity: 152
Merit: 0


View Profile
November 13, 2018, 04:05:41 PM
 #5320


This is very nice HR.
MY rig not work with tube/hevay/haven and 1.6.1 driver and srbminer1.6.4 .1.6.9
but with 1.7.0 work.vega 56 nitro with hynix have 1600HR
and i use JCE for tube/haven/heavy (1700Hr)

jce hashrate drop after 1 hour 15% und fee 2% = total loss

Mybe for you . on my rig HR is constant . Fee is BAD but 2,1% - 0,9% = 1,1% fee
1.70 give me 9559HR JCE give me 10110HR . 10110-9550 = 560HR .This is 5,5% more for JCE . 5,5-1,1 = 4,4% more on JCE
or
SRB 9550HR - 0,89% fee = 9465HR
https://image.prntscr.com/image/xy0brYM3QRKb-ko35LHTxg.jpg
JCE =10110HR - 2,1% fee =9898HR
https://image.prntscr.com/image/Gj5n234vTayImL_2_74Ptg.jpg

you edit your post, say 0.8% haha

Current fees are:

2.1% for the GPUs on CN-Heavy/HVX/Tube
0.9% for the GPUs otherwise
1.5% for the AES CPUs
3.0% for the non-AES CPUs

why -0.9% ? 0.9% is v8 and other algo, CN-Heavy/HVX/Tube is 2.1%

SRB no 0.89, 0.85.

my hashrate jce start 1720hs after 1 hour = 1570hs and stay that forever
Pages: « 1 ... 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 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 ... 367 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!