SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 110.

Bojcha

hero member

Activity: 848

Merit: 500

Quote from: BogdanCo on November 02, 2018, 03:38:31 AM

Use Soft Power Play Tables to get Memory to 1100 Mhz if possible...

ppt does not get memory to ~1100MHz.

Alcahest

newbie

Activity: 37

Merit: 0

Thank you for your help but it doesn't work...
Do you think it could be a problem of firewall ?

solutions4w

newbie

Activity: 7

Merit: 1

This one works for me:

{
"pools" :
[
{"pool" : "cryptonightv8.eu.nicehash.com:3367", "wallet" : "36GWXKPs3fp2RWbB2qc7fREss653c6o5nL.D31", "password" : "x", "nicehash" : true},
{"pool" : "cryptonightv8.usa.nicehash.com:3367", "wallet" : "36GWXKPs3fp2RWbB2qc7fREss653c6o5nL.D31", "password" : "x", "nicehash" : true},
{"pool" : "cryptonightv8.jp.nicehash.com:3367", "wallet" : "36GWXKPs3fp2RWbB2qc7fREss653c6o5nL.D31", "password" : "x", "nicehash" : true}
]
}

logicus

newbie

Activity: 57

Merit: 0

Quote from: Alcahest on November 02, 2018, 08:44:15 AM

Hello !

I have a problem with my rig (8 x RX VEGA 56) and SRB Miner on cryptonight v8.

Try this pools config :

{
"pools" :
[
   {"pool" : "stratum+tcp://cryptonightv8.eu.nicehash.com:3367", "nicehash" : true, "wallet" : "36GWXKPs3fp2RWbB2qc7fREss653c6o5nL.D31", "password" : "x"},
   {"pool" : "stratum+tcp://cryptonightv8.usa.nicehash.com:3367", "nicehash" : true, "wallet" : "36GWXKPs3fp2RWbB2qc7fREss653c6o5nL.D31", "password" : "x"},
   {"pool" : "stratum+tcp://cryptonightv8.jp.nicehash.com:3367", "nicehash" : true, "wallet" : "36GWXKPs3fp2RWbB2qc7fREss653c6o5nL.D31", "password" : "x"}
]
}

Alcahest

newbie

Activity: 37

Merit: 0

Thank you for your help but also with your syntax it doesn't work

Embarrassed

tg88

legendary

Activity: 2492

Merit: 1429

Top-tier crypto casino and sportsbook

Quote from: Alcahest on November 02, 2018, 08:44:15 AM

Hello !

I have a problem with my rig (8 x RX VEGA 56) and SRB Miner on cryptonight v8.

Here is my pools config :

Take a test with this syntax.

Quote

{
"pools" :
[

{"pool" : "stratum+tcp://cryptonightv8.eu.nicehash.com:3367", "wallet" : "36GWXKPs3fp2RWbB2qc7fREss653c6o5nL.D31", "password" : "x"},
{"pool" : "xmr-eu2.nanopool.org:14444", "wallet" : "42obT6dQSrC8YuP885n8mU6aHjcMzoFAyXqiSuB1JXmyUDYXTZSMfz5WbwaVe4vUMveKAzAiA4j8xgU i29TpKXpm42dDYs6.D31", "password" : "x"}

]
}

Alcahest

newbie

Activity: 37

Merit: 0

Hello !

I have a problem with my rig (8 x RX VEGA 56) and SRB Miner on cryptonight v8.

Here is my pools config :

Quote

{
"pools" :
[
   {
      "pool" : "stratum+tcp://cryptonightv8.eu.nicehash.com:3367",
      "wallet" : "36GWXKPs3fp2RWbB2qc7fREss653c6o5nL.D31",
      "password" : "x",
      "worker" : "D31"
   },
   {
      "pool" : "xmr-eu2.nanopool.org:14444",
      "wallet" : "42obT6dQSrC8YuP885n8mU6aHjcMzoFAyXqiSuB1JXmyUDYXTZSMfz5WbwaVe4vUMveKAzAiA4j8xgU i29TpKXpm42dDYs6.D31",
      "password" : "x"
   }
]
}

My rig can't connect to my two pools, i have different errors : "connection to pool lost", "could not login user to pool, try again" or "cant' connect to xxx pool"
Here is a screenshot :

http://www.noelshack.com/2018-44-5-1541165408-srb.jpg

I have verified my firewall and antivirus configuration and all is OK...
Do you have any idea ?

Thank you for your help!

KhorneFlake

newbie

Activity: 27

Merit: 0

Yes, the HBM is hotter than the core, but still good regarding defaults I had on the mainstream platform, with HBM going over 90C...

http://gpuz.techpowerup.com/18/11/02/wm2.png

Gtx1070rig

jr. member

Activity: 56

Merit: 4

I got a rly weird problem...

3 of my 6 rx 580s have elpida mem...

randomly i got similar results

``[2018-10-31 19:18:12] GPU0 : 950 H/s [T: 56c, RPM: 1264, CC: 1200 MHz, MC: 2050 MHz][BUS:1]
[2018-10-31 19:18:12] GPU1 : 955 H/s [T: 61c, RPM: 1071, CC: 1200 MHz, MC: 2050 MHz][BUS:2]
[2018-10-31 19:18:12] GPU2 : 956 H/s [T: 56c, RPM: 1038, CC: 1200 MHz, MC: 2050 MHz][BUS:3]
[2018-10-31 19:18:12] GPU3 : 951 H/s [T: 55c, RPM: 1251, CC: 1200 MHz, MC: 2050 MHz][BUS:6]
[2018-10-31 19:18:12] GPU4 : 951 H/s [T: 57c, RPM: 1109, CC: 1200 MHz, MC: 2050 MHz][BUS:7]
[2018-10-31 19:18:12] GPU5 : 955 H/s [T: 56c, RPM: 1001, CC: 1200 MHz, MC: 2050 MHz][BUS:8]``

with little higher voltage on mem then on samsung mem cards...

But mostly i got these results with the same oc settings:

``[2018-11-01 18:00:48] GPU0 : 952 H/s [T: 60c, RPM: 1262, CC: 1200 MHz, MC: 2050 MHz][BUS:1]
[2018-11-01 18:00:48] GPU1 : 952 H/s [T: 63c, RPM: 1252, CC: 1200 MHz, MC: 2050 MHz][BUS:2]
[2018-11-01 18:00:48] GPU2 : 933 H/s [T: 70c, RPM: 999, CC: 1200 MHz, MC: 2050 MHz][BUS:4]
[2018-11-01 18:00:48] GPU3 : 953 H/s [T: 64c, RPM: 1137, CC: 1200 MHz, MC: 2050 MHz][BUS:5]
[2018-11-01 18:00:48] GPU4 : 931 H/s [T: 67c, RPM: 1142, CC: 1200 MHz, MC: 2050 MHz][BUS:6]
[2018-11-01 18:00:48] GPU5 : 932 H/s [T: 70c, RPM: 1256, CC: 1200 MHz, MC: 2050 MHz][BUS:7]
[2018-11-01 18:00:48] Total: 5640 H/s``

I flashed all with Bios One Time Click... The Samsung cards work great...
Anything i can do, do get similar results instead of losing around 20H/s (v8) per card?
or lost i the silicon lottery?^^

BogdanCo

hero member

Activity: 729

Merit: 513

Quote from: KhorneFlake on November 02, 2018, 03:30:18 AM

Quote from: doktor83 on November 01, 2018, 11:40:44 PM

Quote from: KhorneFlake on November 01, 2018, 06:38:17 PM

I just wanted to report that I've solved my problem with one of my Vegas being quite spastic, like less than half hashrate of its sibling. My Windows key was deactivated for a while now, and I finally contacted the supports and they helped me reactivating my Windows copy. I got an update, and after restarting both cards are running at the same speed:

Edit: Um, it seems I started celebrating too early. My 4th miner report shows it dropped to around 1100h/s again...

you need to cool those vegas, set the fan to 3000rpm.
That is why the hashrate drops, hbm gets too hot

Both are pretty much the same temps wise, maybe the upper one has a degree more.. Much better now since I switched to the Threadripper platform and there's more space between them, on the mainstream Ryzen mobo they were too close.

Use Soft Power Play Tables to get Memory to 1100 Mhz if possible and also voltages a little down, you should get ~1900 H/s out of one Vega and temp around 50 degrees Celsius (depends of the Vega model). Keep in mind the HBM is ~10 degrees hotter than what you see on the screen.

KhorneFlake

newbie

Activity: 27

Merit: 0

Quote from: doktor83 on November 01, 2018, 11:40:44 PM

Quote from: KhorneFlake on November 01, 2018, 06:38:17 PM

I just wanted to report that I've solved my problem with one of my Vegas being quite spastic, like less than half hashrate of its sibling. My Windows key was deactivated for a while now, and I finally contacted the supports and they helped me reactivating my Windows copy. I got an update, and after restarting both cards are running at the same speed:

https://i.imgur.com/Sxk4zwu.png

Edit: Um, it seems I started celebrating too early. My 4th miner report shows it dropped to around 1100h/s again...

you need to cool those vegas, set the fan to 3000rpm.
That is why the hashrate drops, hbm gets too hot

Both are pretty much the same temps wise, maybe the upper one has a degree more.. Much better now since I switched to the Threadripper platform and there's more space between them, on the mainstream Ryzen mobo they were too close.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: Uaciuganadu on November 01, 2018, 05:29:13 PM

Quote from: doktor83 on November 01, 2018, 04:15:27 PM

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:[email protected]"
},
{
"pool" : "gulf.moneroocean.stream:10064",
"wallet" : "someaddress",
"password" : "MinerSRBAuto:[email protected]"
}
]
}

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.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: KhorneFlake on November 01, 2018, 06:38:17 PM

I just wanted to report that I've solved my problem with one of my Vegas being quite spastic, like less than half hashrate of its sibling. My Windows key was deactivated for a while now, and I finally contacted the supports and they helped me reactivating my Windows copy. I got an update, and after restarting both cards are running at the same speed:

Edit: Um, it seems I started celebrating too early. My 4th miner report shows it dropped to around 1100h/s again...

you need to cool those vegas, set the fan to 3000rpm.
That is why the hashrate drops, hbm gets too hot

KhorneFlake

newbie

Activity: 27

Merit: 0

I just wanted to report that I've solved my problem with one of my Vegas being quite spastic, like less than half hashrate of its sibling. My Windows key was deactivated for a while now, and I finally contacted the supports and they helped me reactivating my Windows copy. I got an update, and after restarting both cards are running at the same speed:

https://i.imgur.com/Sxk4zwu.png

Edit: Um, it seems I started celebrating too early. My 4th miner report shows it dropped to around 1100h/s again...

Uaciuganadu

newbie

Activity: 39

Merit: 0

Quote from: doktor83 on November 01, 2018, 04:15:27 PM

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:[email protected]"
},
{
"pool" : "gulf.moneroocean.stream:10064",
"wallet" : "someaddress",
"password" : "MinerSRBAuto:[email protected]"
}
]
}

doktor83

hero member

Activity: 2548

Merit: 626

i am more interested in your pools file, have you defined a 'cryptonight_type' for the monero ocean pool?

Uaciuganadu

newbie

Activity: 39

Merit: 0

Quote from: doktor83 on November 01, 2018, 03:11:23 PM

Quote from: Uaciuganadu on November 01, 2018, 01:56:37 PM

Hey Dok,

I have a strange issue where the miner crashes after multiple hours and this is the end of the log:

Code:

[2018-11-01 19:16:38] algo_switch: Pool requested algo switch to [normalv8]
[2018-11-01 19:16:38] Restarting miner with normalv8 algo
[2018-11-01 19:16:39] Miner version: 1.6.9
[2018-11-01 19:16:39] Windows version: 10.0 build 16299
[2018-11-01 19:16:39] Video driver version: 24.20.11021.1000
[2018-11-01 19:16:40] AMD Platform ID: 1
[2018-11-01 19:16:40] AMD platform FOUND
[2018-11-01 19:16:40] Found 3 AMD devices
[2018-11-01 19:16:40] CPU AES-NI: TRUE
[2018-11-01 19:16:40] GPU0: Radeon RX 580 Series [ellesmere] [8192 MB][I: 58.0][W: 8][T: 2][F: 4][K: 1][BUS: 6]
[2018-11-01 19:16:40] GPU1: Radeon RX Vega [gfx900] [8176 MB][I: 124.0][W: 16][T: 2][F: 4][K: 1][BUS: 9]
[2018-11-01 19:16:40] GPU2: Radeon RX Vega [gfx900] [8176 MB][I: 124.0][W: 16][T: 2][F: 4][K: 1][BUS: 3]
[2018-11-01 19:16:40] ADL is enabled
[2018-11-01 19:16:40] Algo switching mode enabled
[2018-11-01 19:16:40] Algo switch minimum time : 60 seconds
[2018-11-01 19:16:40] CryptonightV8 mode enabled
[2018-11-01 19:16:40] Starting init of mining threads
[2018-11-01 19:16:40] Created OCL context
[2018-11-01 19:16:40] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-11-01 19:16:40] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-11-01 19:16:40] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-11-01 19:16:40] Loading normalv8 kernel for DEVICE BUS_ID[6] ...
[2018-11-01 19:16:40] ctx->Program for DeviceID 0 (Thread 0) loaded
[2018-11-01 19:16:40] Created OCL command queue for DeviceID 0 (Thread 1)
[2018-11-01 19:16:40] Created OCL input buffer for DeviceID 0 (Thread 1)
[2018-11-01 19:16:40] Created OCL output buffer for DeviceID 0 (Thread 1)
[2018-11-01 19:16:40] Loading normalv8 kernel for DEVICE BUS_ID[6] ...
[2018-11-01 19:16:40] ctx->Program for DeviceID 0 (Thread 1) loaded
[2018-11-01 19:16:41] Created OCL command queue for DeviceID 1 (Thread 2)
[2018-11-01 19:16:41] Created OCL input buffer for DeviceID 1 (Thread 2)
[2018-11-01 19:16:41] Created OCL output buffer for DeviceID 1 (Thread 2)
[2018-11-01 19:16:41] Loading normalv8 kernel for DEVICE BUS_ID[9] ...
[2018-11-01 19:16:41] ctx->Program for DeviceID 1 (Thread 2) loaded
[2018-11-01 19:16:41] Created OCL command queue for DeviceID 1 (Thread 3)
[2018-11-01 19:16:41] Created OCL input buffer for DeviceID 1 (Thread 3)
[2018-11-01 19:16:41] Created OCL output buffer for DeviceID 1 (Thread 3)
[2018-11-01 19:16:41] Loading normalv8 kernel for DEVICE BUS_ID[9] ...
[2018-11-01 19:16:41] ctx->Program for DeviceID 1 (Thread 3) loaded
[2018-11-01 19:16:41] Created OCL command queue for DeviceID 2 (Thread 4)
[2018-11-01 19:16:41] Created OCL input buffer for DeviceID 2 (Thread 4)
[2018-11-01 19:16:41] Created OCL output buffer for DeviceID 2 (Thread 4)
[2018-11-01 19:16:41] Loading normalv8 kernel for DEVICE BUS_ID[3] ...
[2018-11-01 19:16:41] ctx->Program for DeviceID 2 (Thread 4) loaded
[2018-11-01 19:16:41] Created OCL command queue for DeviceID 2 (Thread 5)
[2018-11-01 19:16:41] Created OCL input buffer for DeviceID 2 (Thread 5)
[2018-11-01 19:16:41] Created OCL output buffer for DeviceID 2 (Thread 5)
[2018-11-01 19:16:41] Loading normalv8 kernel for DEVICE BUS_ID[3] ...
[2018-11-01 19:16:41] ctx->Program for DeviceID 2 (Thread 5) loaded

need much more info, like config file and pool, is it Monero Ocean?
All i see on the log is that miner switched algo to V8 and all gpu's were initialised.

Hello Dok,

Yes it is MoneroOcean.

Here is all the info that i can gather:

Code:

setx GPU_MAX_HEAP_SIZE 100
setx GPU_MAX_USE_SYNC_OBJECTS 1
setx GPU_SINGLE_ALLOC_PERCENT 100
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_MAX_SINGLE_ALLOC_PERCENT 100
@echo off
cd %~dp0

cls
for /f "tokens=2 delims==" %%a in ('wmic OS Get localdatetime /value') do set "dt=%%a"
set LOGTIME=%dt:~0,4%_%dt:~4,2%_%dt:~6,2%_%dt:~8,2%_%dt:~10,2%_%dt:~12,2%
set LOGTIME=%LOGTIME: =%
set LOGTIME=%LOGTIME:,=.%.txt

SRBMiner-CN.exe --config Config\config-normalv8.txt --pools pools-algoswitch.txt --logfile al_sw_%LOGTIME% --usealgoswitching --apienable --apiport 8888 --algoswitchmintime 60 --resetmineronalgoswitch --forcedshutdown --gpuerrorsalert 10

Code:

{
"cryptonight_type" : "normalv8",
"intensity" : 0,
"gpu_conf" :
[
{ "id" : 0, "intensity" : 58, "worksize" : 8, "threads" : 2},
{ "id" : 1, "intensity" : 124, "worksize" : 16, "threads" : 2},
{ "id" : 2, "intensity" : 124, "worksize" : 16, "threads" : 2}
]
}

Here is also the before algo switch part:

Code:

[2018-11-01 19:12:23] miner_result: Pool accepted result 0x00000C8C
[2018-11-01 19:13:37] hashrate: GPU0: 1664 H/s [BUS:6]
[2018-11-01 19:13:37] hashrate: GPU1: 4358 H/s [BUS:9]
[2018-11-01 19:13:37] hashrate: GPU2: 4013 H/s [BUS:3]
[2018-11-01 19:13:37] hashrate: Total: 10035 H/s
[2018-11-01 19:14:07] miner_result: Sending user result to pool
[2018-11-01 19:14:07] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"9f854439-7175-4484-857c-2e269bb611fe","job_id":"XnL9Z1tpMADL6pchdvgee27GVYdh","nonce":"56245b55","result":"8690bfce43bc39d95f3c799424eed05ed09e22c586e3529a554c4c303b250000","algo":"cn/msr"}}
[2018-11-01 19:14:07] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2018-11-01 19:14:07] miner_result: Pool accepted result 0x0000253B
[2018-11-01 19:14:32] miner_result: Sending user result to pool
[2018-11-01 19:14:32] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"9f854439-7175-4484-857c-2e269bb611fe","job_id":"XnL9Z1tpMADL6pchdvgee27GVYdh","nonce":"e92ead2a","result":"3c51abaa1bebf0cfd1bfe390a53182247cf8a3086166f67e025a7b3078050000","algo":"cn/msr"}}
[2018-11-01 19:14:33] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2018-11-01 19:14:33] miner_result: Pool accepted result 0x00000578
[2018-11-01 19:15:37] hashrate: GPU0: 1664 H/s [BUS:6]
[2018-11-01 19:15:37] hashrate: GPU1: 4359 H/s [BUS:9]
[2018-11-01 19:15:37] hashrate: GPU2: 4014 H/s [BUS:3]
[2018-11-01 19:15:37] hashrate: Total: 10037 H/s
[2018-11-01 19:16:33] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0707f0e9ecde052eab8922c9b0af7ed8221b276d0772a4a6f4339d75e3ea71f88dedb57738a5ee000000000b40cf5e95539d38a77e184d6b1ac203bc3273790356ef2d861042d29aa28f8f06","algo":"cn/msr","variant":"msr","job_id":"STVJ6+uLiMruqeLtHisVh40wdN9z","target":"8a330000","id":"9f854439-7175-4484-857c-2e269bb611fe"}}
[2018-11-01 19:16:38] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909a9e9ecde05b7718ace0f6f876881dcaf0b3dcfc5f83a011b4996db1e8a1f3376a593ba7c50000000004529dfdd46303bbbb9c3c72d5c487b69967c43d8bd7245629f6538919700382002","algo":"cn/2","variant":"2","job_id":"lo+EIlC3lfoB1YzY5uyG84rqVlBi","target":"8a330000","id":"9f854439-7175-4484-857c-2e269bb611fe"}}
[2018-11-01 19:16:38] algo_switch: Pool requested algo switch to [normalv8]

Is there any way to make the log more detailed for debug?

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: Uaciuganadu on November 01, 2018, 01:56:37 PM

Hey Dok,

I have a strange issue where the miner crashes after multiple hours and this is the end of the log:

Code:

[2018-11-01 19:16:38] algo_switch: Pool requested algo switch to [normalv8]
[2018-11-01 19:16:38] Restarting miner with normalv8 algo
[2018-11-01 19:16:39] Miner version: 1.6.9
[2018-11-01 19:16:39] Windows version: 10.0 build 16299
[2018-11-01 19:16:39] Video driver version: 24.20.11021.1000
[2018-11-01 19:16:40] AMD Platform ID: 1
[2018-11-01 19:16:40] AMD platform FOUND
[2018-11-01 19:16:40] Found 3 AMD devices
[2018-11-01 19:16:40] CPU AES-NI: TRUE
[2018-11-01 19:16:40] GPU0: Radeon RX 580 Series [ellesmere] [8192 MB][I: 58.0][W: 8][T: 2][F: 4][K: 1][BUS: 6]
[2018-11-01 19:16:40] GPU1: Radeon RX Vega [gfx900] [8176 MB][I: 124.0][W: 16][T: 2][F: 4][K: 1][BUS: 9]
[2018-11-01 19:16:40] GPU2: Radeon RX Vega [gfx900] [8176 MB][I: 124.0][W: 16][T: 2][F: 4][K: 1][BUS: 3]
[2018-11-01 19:16:40] ADL is enabled
[2018-11-01 19:16:40] Algo switching mode enabled
[2018-11-01 19:16:40] Algo switch minimum time : 60 seconds
[2018-11-01 19:16:40] CryptonightV8 mode enabled
[2018-11-01 19:16:40] Starting init of mining threads
[2018-11-01 19:16:40] Created OCL context
[2018-11-01 19:16:40] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-11-01 19:16:40] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-11-01 19:16:40] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-11-01 19:16:40] Loading normalv8 kernel for DEVICE BUS_ID[6] ...
[2018-11-01 19:16:40] ctx->Program for DeviceID 0 (Thread 0) loaded
[2018-11-01 19:16:40] Created OCL command queue for DeviceID 0 (Thread 1)
[2018-11-01 19:16:40] Created OCL input buffer for DeviceID 0 (Thread 1)
[2018-11-01 19:16:40] Created OCL output buffer for DeviceID 0 (Thread 1)
[2018-11-01 19:16:40] Loading normalv8 kernel for DEVICE BUS_ID[6] ...
[2018-11-01 19:16:40] ctx->Program for DeviceID 0 (Thread 1) loaded
[2018-11-01 19:16:41] Created OCL command queue for DeviceID 1 (Thread 2)
[2018-11-01 19:16:41] Created OCL input buffer for DeviceID 1 (Thread 2)
[2018-11-01 19:16:41] Created OCL output buffer for DeviceID 1 (Thread 2)
[2018-11-01 19:16:41] Loading normalv8 kernel for DEVICE BUS_ID[9] ...
[2018-11-01 19:16:41] ctx->Program for DeviceID 1 (Thread 2) loaded
[2018-11-01 19:16:41] Created OCL command queue for DeviceID 1 (Thread 3)
[2018-11-01 19:16:41] Created OCL input buffer for DeviceID 1 (Thread 3)
[2018-11-01 19:16:41] Created OCL output buffer for DeviceID 1 (Thread 3)
[2018-11-01 19:16:41] Loading normalv8 kernel for DEVICE BUS_ID[9] ...
[2018-11-01 19:16:41] ctx->Program for DeviceID 1 (Thread 3) loaded
[2018-11-01 19:16:41] Created OCL command queue for DeviceID 2 (Thread 4)
[2018-11-01 19:16:41] Created OCL input buffer for DeviceID 2 (Thread 4)
[2018-11-01 19:16:41] Created OCL output buffer for DeviceID 2 (Thread 4)
[2018-11-01 19:16:41] Loading normalv8 kernel for DEVICE BUS_ID[3] ...
[2018-11-01 19:16:41] ctx->Program for DeviceID 2 (Thread 4) loaded
[2018-11-01 19:16:41] Created OCL command queue for DeviceID 2 (Thread 5)
[2018-11-01 19:16:41] Created OCL input buffer for DeviceID 2 (Thread 5)
[2018-11-01 19:16:41] Created OCL output buffer for DeviceID 2 (Thread 5)
[2018-11-01 19:16:41] Loading normalv8 kernel for DEVICE BUS_ID[3] ...
[2018-11-01 19:16:41] ctx->Program for DeviceID 2 (Thread 5) loaded

need much more info, like config file and pool, is it Monero Ocean?
All i see on the log is that miner switched algo to V8 and all gpu's were initialised.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: Kgonla on November 01, 2018, 02:08:50 PM

For all of us who are having more or less H/s with 1.6.9 than with previous....
I think H/s shown by the program is inaccurate.

Examples:
Pressed H, shown 992 H/s
Pressed S, it says max H/s have been 985

Set worksize to 1
I press H all the time I want, always showing 0 H/s but getting some hashes
S says H/s 200+

So I think the H/s shown by the S command are OK but the ones shown by H or automatically are not.

Max is 'refreshed' every 30 seconds. You probably did not wait 30 seconds to press 'S' after you pressed 'H' and saw 992hs.

'H' shows average hashrate for a very short period, like 8-10 seconds.
'S' shows average for much more, that's why you had there 200hs.

Velmerk

newbie

Activity: 23

Merit: 0

Quote from: dingdongtobias on November 01, 2018, 01:19:23 PM

Quote from: Velmerk on November 01, 2018, 10:49:46 AM

Vega56 ref
1.6.8 auto Intensity = 120
1.6.9 auto Intensity = 112, HR little bit slowly, may be the same after tuning "fragments"...

intensiti 112 give smaller hash then intensity 120 ? VERY INTERESTING! Grin

Yes...VERY INTERESTING! Grin

1.6.8 auto Intensity = 120, HR ~14000
1.6.9 auto Intensity = 112, HR ~13900
1.6.9 manual Intensity = 116, HR ~13700
1.6.9 manual Intensity = 120, HR ~13800
1.6.9 manual Intensity = 124, HR ~13600

Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 110. (Read 237261 times)