doktor83 (OP)
|
 |
October 08, 2018, 06:09:09 PM |
|
i think i found something about the 570/580 8g cards and heavy algos. Going to check out a few more things then re-upload 1.6.8 with the fixes.
check new version/ same trouble (( also check without precompile binaries. same low rate 900-930 not 1000+ as on 1.6.7 possible need other drivers? use 18.3.4 Driver should be fine, but you could try 18.6.1. I have a mixed rig 570/580 8G and this is the result now, everything left on auto (intensity 0) 
|
|
|
|
abg00
Jr. Member
Offline
Activity: 288
Merit: 1
|
 |
October 08, 2018, 06:52:56 PM |
|
i think i found something about the 570/580 8g cards and heavy algos. Going to check out a few more things then re-upload 1.6.8 with the fixes.
check new version/ same trouble (( also check without precompile binaries. same low rate 900-930 not 1000+ as on 1.6.7 possible need other drivers? use 18.3.4 Driver should be fine, but you could try 18.6.1. I have a mixed rig 570/580 8G and this is the result now, everything left on auto (intensity 0) reinstall drivers to 18.6.1 same trouble with rate (( possible trouble because 12 card on rig? all 12 gpu rx570 8 gb no different swap 98 gb but 1.6.7 1000+ rate
|
|
|
|
RuMiner
Member

Offline
Activity: 168
Merit: 15
|
 |
October 08, 2018, 08:59:29 PM Last edit: October 08, 2018, 09:29:33 PM by RuMiner |
|
1.6.8 gave additional 6-8 hashes per Vega using same settings on normalv7. nice 
|
|
|
|
glowbg
Newbie
Offline
Activity: 5
Merit: 0
|
 |
October 08, 2018, 09:20:45 PM |
|
I'm using RX580 8G and version 1.6.8 is working slower with a total of 400H/s versus version 1.6.7 of heavy  i use auto (intensity 0)
|
|
|
|
dragonmike
|
 |
October 08, 2018, 10:26:39 PM |
|
What intensity/worksize/threads combo are you recommending on RX 570's 4GB for the new v8?
|
|
|
|
livada
Newbie
Offline
Activity: 417
Merit: 0
|
 |
October 08, 2018, 10:48:11 PM |
|
Hey Doc, thc for update !! Using Binary kernals on Vega 64: v7 : HR up from 2130 to 2145 v8 : HR is 580  Is that normal, only 580 H/s? Cause i think the devs said approx 7% drop so was expecting at least 1950 h/s I got the same HR result for v8 on both benchmark mode and mining on the test pools: "pool": "killallasics.moneroworld.com:7777", "difficulty": 10000, { "device": "GPU0", "device_id": 0, "model": "Radeon RX Vega", "bus_id": 19, "kernel_id": 1, "hashrate": 593, "core_clock": 1630, "memory_clock": 1100, "temperature": 54, "fan_speed_rpm": 4576 }, GPU was on dual thread and auto worksize, auto intensity how you solved this? Yes something not ok, try setting by hand for example 120/16 2 threads
I really hurried to push the v8 version, so of course bugs are to be expected, and we still have time to fix them until the fork
Hey Doc, Vega 64 - Cryptonight v8 analysis:Using binary kernals : 583 h/s Not Using Binary Kernals, Kernals compiled on each run and deleted Driver: 18.5.1 GPU: 1600 Mem: 1100 Volt : 840mVIntensity : 119 Worksize : 16 : 2019 H/s (94.338% on cn7) Intensity : 119 Worksize : 32 : 1963 H/s (91.745% on cn7) Intensity : 120 Worksize : 16 : 2025 H/s (94.626% on cn7) Intensity : 120 Worksize : 32 : 1983 H/s (92.663% on cn7) Intensity : 121 Worksize : 16 : 2032 H/s (94.953% on cn7) Intensity : 121 Worksize : 32 : 1975 H/s (92.289% on cn7) Intensity : 122 Worksize : 16 : 2038 H/s (95.234% on cn7) Intensity : 122 Worksize : 32 : 1992 H/s (93.099% on cn7) Intensity : 123 Worksize : 16 : 2043 H/s (95.467% on cn7) Intensity : 123 Worksize : 32 : 1984 H/s (92.710% on cn7) Intensity : 124 Worksize : 16 : 2049 H/s (95.748% on cn7)Intensity : 124 Worksize : 32 : 2000 H/s (93.458% on cn7) Intensity : 125 Worksize : 16 : Failed Intensity : 125 Worksize : 32 : Failed The above are avg HR from a run of 6 Vega 64s and the highest HR setting were tries multiple times for consistency. Great work doc, so thats a 4.25% drop from v7 !! not bad considering devs said 7% drop  i use your int work but HR only 1100  in v8
|
|
|
|
N2DCRYPT
Jr. Member
Offline
Activity: 148
Merit: 5
|
 |
October 08, 2018, 11:41:22 PM |
|
Nice Dok! Can confirm ~2035 H/s for a V64 on V8. ~2135 H/s on current V7. V8 Only works using your pre-compiled kernels though. Running 18.6.1 drivers which are recommended, strange that they can't compile for V8. Just wanted to pass the info along, thx for all your wonderful work, best CN miner in my book by a long shot!
|
|
|
|
adaseb
Legendary
Offline
Activity: 3878
Merit: 1733
|
 |
October 08, 2018, 11:45:19 PM |
|
Anyone still mining with the older Radeon 7970/280X or the R9 290 GPUs?
Was wondering what config you guys are using and what stability you guys get with this software, I am looking for an alternative to the Claymore XMR miner which will become obsolete when XMR forks on Oct 18th.
|
|
|
|
caki2004
Newbie
Offline
Activity: 3
Merit: 0
|
 |
October 09, 2018, 02:51:36 AM |
|
Could anyone help me,when i start the miner with my r9 290 i get the following error:
[2018-10-09 14:48:01] Error CL_LINK_PROGRAM_FAILURE when calling clLinkProgram [ctx->Program] for DeviceID 0 (Thread 0) [2018-10-09 14:48:01] Error CL_INVALID_PROGRAM when calling clGetProgramBuildInfo for length of build log output for DeviceID 0 (Thread 0)
|
|
|
|
starmax
Jr. Member
Offline
Activity: 69
Merit: 1
|
 |
October 09, 2018, 03:00:16 AM |
|
Nice Dok! Can confirm ~2035 H/s for a V64 on V8. ~2135 H/s on current V7. V8 Only works using your pre-compiled kernels though. Running 18.6.1 drivers which are recommended, strange that they can't compile for V8. Just wanted to pass the info along, thx for all your wonderful work, best CN miner in my book by a long shot!
Hmm, testing with a single Vega56. Was getting ~2035 with 1.6.7, now getting ~1630 with 1.6.8. Tried both the Normal and Maxi versions, same results. Using the 18.6.1 drivers, so not sure what to make of this 
|
|
|
|
doktor83 (OP)
|
 |
October 09, 2018, 04:28:39 AM |
|
What intensity/worksize/threads combo are you recommending on RX 570's 4GB for the new v8?
try 57/16/2
|
|
|
|
doktor83 (OP)
|
 |
October 09, 2018, 04:30:01 AM |
|
Nice Dok! Can confirm ~2035 H/s for a V64 on V8. ~2135 H/s on current V7. V8 Only works using your pre-compiled kernels though. Running 18.6.1 drivers which are recommended, strange that they can't compile for V8. Just wanted to pass the info along, thx for all your wonderful work, best CN miner in my book by a long shot!
Do you get an error when trying to compile, or ?
|
|
|
|
doktor83 (OP)
|
 |
October 09, 2018, 05:23:26 AM |
|
Could anyone help me,when i start the miner with my r9 290 i get the following error:
[2018-10-09 14:48:01] Error CL_LINK_PROGRAM_FAILURE when calling clLinkProgram [ctx->Program] for DeviceID 0 (Thread 0) [2018-10-09 14:48:01] Error CL_INVALID_PROGRAM when calling clGetProgramBuildInfo for length of build log output for DeviceID 0 (Thread 0)
On top where you have something like : GPU0: Radeon RX 580 Series [ellesmere] [8192 MB][Intensity 56.0][W: 8][T: 2][K: 1][BUS: 2] What do you have, [K: 1] or [K: 2] ? Also driver version?
|
|
|
|
doktor83 (OP)
|
 |
October 09, 2018, 07:33:09 AM Last edit: October 09, 2018, 09:47:11 AM by doktor83 |
|
It looks like the 18.3.4 drivers dont like my implementaion of V8 with the default worksize of 16 - tested on Vega56. This is why some of you get those 500-600-700hs speeds probably. On 18.6.1 it is OK, i will also test 18.5.1 , 18.5.2
EDIT:
From 18.5.1 is OK. I will check why on 18.3.4 isn't but it is not high priority.
Ok, so checked on 18.3.4 and it looks like its not my V8 implementation that is the problem, but something else.
Anyone out there can try 1.6.8 with Vega56 or 64 on Blockchain drivers?
|
|
|
|
samet_9511
Jr. Member
Offline
Activity: 81
Merit: 7
|
 |
October 09, 2018, 07:39:17 AM |
|
is it important worksize in config ?
i tried 8 and 16 and 12 i think no any effect. any idea ?
|
|
|
|
doktor83 (OP)
|
 |
October 09, 2018, 07:44:21 AM |
|
is it important worksize in config ?
i tried 8 and 16 and 12 i think no any effect. any idea ?
it is important. Which algo? Which gpu?
|
|
|
|
ZaGMaN
Newbie
Offline
Activity: 4
Merit: 0
|
 |
October 09, 2018, 09:23:05 AM |
|
Hi doktor83 Starting with version 1.6.5, on the normalv7 algorithm for R7 370 uses kernel 2 and give me 360h/s On version 1.6,4 and earlier, these cards work on kernel 1 and give me 440h/s What to do when the algorithm changes to normalv8 ?
|
|
|
|
doktor83 (OP)
|
 |
October 09, 2018, 09:39:22 AM |
|
Hi doktor83 Starting with version 1.6.5, on the normalv7 algorithm for R7 370 uses kernel 2 and give me 360h/s On version 1.6,4 and earlier, these cards work on kernel 1 and give me 440h/s What to do when the algorithm changes to normalv8 ?
you can give me access to a machine you have that card installed in, and i can try to rework kernel1 to work with R7 too
|
|
|
|
jazz1984
Jr. Member
Offline
Activity: 392
Merit: 5
|
 |
October 09, 2018, 10:00:33 AM |
|
Anyone still mining with the older Radeon 7970/280X or the R9 290 GPUs?
Was wondering what config you guys are using and what stability you guys get with this software, I am looking for an alternative to the Claymore XMR miner which will become obsolete when XMR forks on Oct 18th.
I tried to run the srmbminer on my 7970 with settings --cgpuintencity 15 --cgpuworksize 8 -cgputhreads 2, at the stock frequencies (925/1375) I got 360H / s on v7, its less than old claymore 11.3 (450)... but clay not support v8 PS Guys when need to change algo for Monero mining? Any dates?
|
|
|
|
sxemini
Member

Offline
Activity: 1559
Merit: 69
|
 |
October 09, 2018, 10:18:37 AM |
|
is it important worksize in config ?
i tried 8 and 16 and 12 i think no any effect. any idea ?
it is important. Which algo? Which gpu? For me too. I have a Rig with 6x RX550 4G. I mine Monero (CN V7) with 34 Intensity. 8 or 12 worksize change nothing in hashrate. I get arround 2900 hahes with this config.
|
|
|
|
|