m03e5 commented 6 years ago

Please provide as much as possible information to reproduce the issue.

Basic information

Xeon X5660
AMD 6990
Win 10 Pro X64

Do you compiled the miner by our own? -no

Stability issue

Is the CPU or GPU overclocked? / No overclocking
Is the Main memory of the CPU or GPU undervolted? / No

When initially executed miner creates 2 config files, one for cpu and one for gpu. However when miner is running only cpu is mining, no AMD gpu visible and no errors, acts just like its not there. Its a dual GPU on one physical video card and i know it works as it was mining under nicehash, both gpu's are listed in device manager and obviously they are seen by miner as it creates config file for it... Here is config, generated during initial run of program.

/*

GPU configuration. You should play around with intensity and worksize as the fastest settings will vary.
index - GPU index number usually starts from 0
intensity - Number of parallel GPU threads (nothing to do with CPU threads)
worksize - Number of local GPU threads (nothing to do with CPU threads)
affine_to_cpu - This will affine the thread to a CPU. This can make a GPU miner play along nicer with a CPU miner.
strided_index - switch memory pattern used for the scratch pad memory
true = use 16byte contiguous memory per thread, the next memory block has offset of intensity blocks
false = use a contiguous block of memory per thread
"gpu_threads_conf" :
[
{ "index" : 0, "intensity" : 1000, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : true },
], */

"gpu_threads_conf" : [ // gpu: Cayman memory:384 // compute units: 24 { "index" : 0, "intensity" : 0, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : true }, // gpu: Cayman memory:384 // compute units: 24 { "index" : 1, "intensity" : 0, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : true },

],

/*

Platform index. This will be 0 unless you have different OpenCL platform - eg. AMD and Intel. */ "platform_index" : 0,

What am i doing wrong or not doing right?

m03e5 commented 6 years ago

Off top question - is there a way to disable device(cpu) in mining, i have another computer with core 2 duo, that is used for mining when miner running and its just useless... i have 3 video cards on that board that do work well though. I want to use only cards and not use cpu at all. Tried deleting config and its being re-created, tried modding config to a point that it cant be used and miner says invalid config and just quits, so video cards cant mine, any suggestions?

psychocrypt commented 6 years ago

--noCPU disable the cpu. Please post the full terminal output.

psychocrypt commented 6 years ago

I saw that the intensity is set to zero. Please increar the intensity by hand to 128, 256 or 512. Yor gpu has only 300MB free some other apps using to much memery. restart the system than delete the amd.txt an start the miner and check the intensity.

bovcan commented 6 years ago

try to change "platform_index" : 0, to 1 or 2.

Simaex commented 6 years ago

What driver are you using for HD6990? I have many issues with the card before I roll back to 15.7 driver but I never think that XMR-STAK can work with such old driver. I'll try to run 2.1 version of XMR-STAK and report results.

m03e5 commented 6 years ago

xmr-stak 2.1.0 30888a3

Brought to you by fireice_uk and psychocrypt under GPLv3. Based on CPU mining code by wolf9466 (heavily optimized by fireice_uk). Based on NVIDIA mining code by KlausT and psychocrypt. Based on OpenCL mining code by wolf9466.

Configurable dev donation level is set to 2.0%

You can use following keys to display reports: 'h' - hashrate 'r' - results 'c' - connection

[2017-12-11 09:37:52] : Start mining: MONERO [2017-12-11 09:37:52] : Starting NVIDIA GPU thread 0, no affinity. [2017-12-11 09:37:52] : Compiling code and initializing GPUs. This will take a while... [2017-12-11 09:37:54] : Device 0 work size 8 / 32. [2017-12-11 09:37:54] : Error CL_INVALID_BUFFER_SIZE when calling clCreateBuffer to create hash scratchpads buffer. [2017-12-11 09:37:54] : WARNING: AMD device not found [2017-12-11 09:37:54] : WARNING: backend AMD disabled. [2017-12-11 09:37:54] : Starting 1x thread, affinity: 0. [2017-12-11 09:37:54] : hwloc: memory pinned [2017-12-11 09:37:54] : Starting 1x thread, affinity: 2. [2017-12-11 09:37:54] : hwloc: memory pinned [2017-12-11 09:37:54] : Starting 1x thread, affinity: 4. [2017-12-11 09:37:54] : hwloc: memory pinned [2017-12-11 09:37:54] : Starting 1x thread, affinity: 6. [2017-12-11 09:37:54] : hwloc: memory pinned [2017-12-11 09:37:54] : Starting 1x thread, affinity: 8. [2017-12-11 09:37:54] : hwloc: memory pinned [2017-12-11 09:37:54] : Starting 1x thread, affinity: 10. [2017-12-11 09:37:54] : hwloc: memory pinned [2017-12-11 09:37:54] : Starting 1x thread, affinity: 12. [2017-12-11 09:37:54] : hwloc: memory pinned [2017-12-11 09:37:54] : Starting 1x thread, affinity: 14. [2017-12-11 09:37:54] : hwloc: memory pinned [2017-12-11 09:37:54] : Starting 1x thread, affinity: 16. [2017-12-11 09:37:54] : hwloc: memory pinned [2017-12-11 09:37:54] : Starting 1x thread, affinity: 18. [2017-12-11 09:37:54] : hwloc: memory pinned [2017-12-11 09:37:54] : Starting 1x thread, affinity: 20. [2017-12-11 09:37:54] : hwloc: memory pinned [2017-12-11 09:37:54] : Starting 1x thread, affinity: 22. [2017-12-11 09:37:54] : hwloc: memory pinned [2017-12-11 09:37:54] : Fast-connecting to ca.minexmr.com:3333 pool ... [2017-12-11 09:37:54] : Pool ca.minexmr.com:3333 connected. Logging in... [2017-12-11 09:37:54] : Difficulty changed. Now: 2000450. [2017-12-11 09:37:54] : Pool logged in. [2017-12-11 09:38:14] : Difficulty changed. Now: 2000450. [2017-12-11 09:38:16] : New block detected. HASHRATE REPORT - CPU | ID | 10s | 60s | 15m | ID | 10s | 60s | 15m | | 0 | 40.0 | 39.9 | (na) | 1 | 40.0 | 39.9 | (na) | | 2 | 40.0 | 39.9 | (na) | 3 | 40.1 | 40.0 | (na) | | 4 | 41.9 | 41.7 | (na) | 5 | 41.7 | 41.6 | (na) | | 6 | 40.0 | 38.7 | (na) | 7 | 39.9 | 38.3 | (na) | | 8 | 39.8 | 38.7 | (na) | 9 | 39.9 | 38.8 | (na) | | 10 | 41.8 | 40.5 | (na) | 11 | 41.5 | 40.2 | (na) |

HASHRATE REPORT - NVIDIA | ID | 10s | 60s | 15m | | 0 | (na) | 25.5 | (na) |

Totals: (na) 503.8 (na) H/s Highest: 0.0 H/s

6990 is very good card for xmr, it did 770hs which is same as 1080ti OC does on stock clocks.

m03e5 commented 6 years ago

I have not yet tried other suggestions, due to latest win10 update messing up system, had to undo update...took a while. Will do it a bit later. AMD driver is on screenshot and it is indeed 15.7.1 WHQL

Rebooting system, deleting all configs and re-run of xmr stack caused creation of new config files that are identical to the original ones posted above. PC has 100+GB of ram...no other programs/tasks are running when xmr stack runs. Screen attached to GT730. Thanks

Simaex commented 6 years ago

I've managed to get xmr-stak running. I changed intensity to non-zero value and then try to set bigger values. Maximum value that I was able to reach was 250. Overall performance is 3 times lower then using old 9,7 Claymore miner. I beleive that problem is with incorrect memory detection. Only 384 M per GPU are detected when 2G are available. Low hashrate of GPU6 corresponds to performance in other miners. Please advise how to proceed with optimisation. Please note that we have some sort of bug if intensity is set to zero, we get error not stopped adapter.

> xmr-stak 2.1.0 30888a3

Brought to you by fireice_uk and psychocrypt under GPLv3.
Based on CPU mining code by wolf9466 (heavily optimized by fireice_uk).
Based on NVIDIA mining code by KlausT and psychocrypt.
Based on OpenCL mining code by wolf9466.

Configurable dev donation level is set to 2.0%

You can use following keys to display reports:
'h' - hashrate
'r' - results
'c' - connection
-------------------------------------------------------------------
[2017-12-11 21:04:43] : Start mining: MONERO
WARNING: NVIDIA Insufficient driver!
[2017-12-11 21:04:43] : WARNING: backend NVIDIA disabled.
[2017-12-11 21:04:43] : Compiling code and initializing GPUs. This will take a while...
[2017-12-11 21:04:45] : Device 0 work size 8 / 32.
[2017-12-11 21:04:49] : Device 1 work size 8 / 32.
[2017-12-11 21:04:54] : Device 2 work size 8 / 32.
[2017-12-11 21:04:58] : Device 3 work size 8 / 32.
[2017-12-11 21:05:02] : Device 4 work size 8 / 32.
[2017-12-11 21:05:07] : Device 5 work size 8 / 32.
[2017-12-11 21:05:11] : Device 6 work size 8 / 32.
[2017-12-11 21:05:16] : Device 7 work size 8 / 32.
[2017-12-11 21:05:20] : Starting AMD GPU thread 0, no affinity.
[2017-12-11 21:05:20] : Starting AMD GPU thread 1, no affinity.
[2017-12-11 21:05:20] : Starting AMD GPU thread 2, no affinity.
[2017-12-11 21:05:20] : Starting AMD GPU thread 3, no affinity.
[2017-12-11 21:05:20] : Starting AMD GPU thread 4, no affinity.
[2017-12-11 21:05:20] : Starting AMD GPU thread 5, no affinity.
[2017-12-11 21:05:20] : Starting AMD GPU thread 6, no affinity.
[2017-12-11 21:05:20] : Starting AMD GPU thread 7, no affinity.
[2017-12-11 21:05:20] : Starting 1x thread, affinity: 0.
[2017-12-11 21:05:20] : hwloc: memory pinned
[2017-12-11 21:05:20] : Fast-connecting to xmr-eu1.nanopool.org:14433 pool ...
[2017-12-11 21:05:21] : Fast-connecting to xmr-eu2.nanopool.org:14433 pool ...
[2017-12-11 21:05:21] : TLS fingerprint [xmr-eu1.nanopool.org:14433] SHA256:w4iG797lQuvZmAG3XHXTSY2Xl4u83sB8cnHLGXKeAU8=
[2017-12-11 21:05:21] : Pool xmr-eu1.nanopool.org:14433 connected. Logging in...
[2017-12-11 21:05:21] : TLS fingerprint [xmr-eu2.nanopool.org:14433] SHA256:w4iG797lQuvZmAG3XHXTSY2Xl4u83sB8cnHLGXKeAU8=
[2017-12-11 21:05:21] : Pool xmr-eu2.nanopool.org:14433 connected. Logging in...
[2017-12-11 21:05:23] : Difficulty changed. Now: 120001.
[2017-12-11 21:05:23] : Pool logged in.
[2017-12-11 21:05:23] : Difficulty changed. Now: 120001.
[2017-12-11 21:05:23] : New block detected.
HASHRATE REPORT - CPU
| ID |    10s |    60s |    15m |
|  0 |   (na) |   (na) |   (na) |
---------------------------
HASHRATE REPORT - AMD
| ID |    10s |    60s |    15m | ID |    10s |    60s |    15m |
|  0 |   (na) |   (na) |   (na) |  1 |   (na) |   (na) |   (na) |
|  2 |   (na) |   (na) |   (na) |  3 |   (na) |   (na) |   (na) |
|  4 |   (na) |   (na) |   (na) |  5 |   (na) |   (na) |   (na) |
|  6 |   (na) |   (na) |   (na) |  7 |   (na) |   (na) |   (na) |
-----------------------------------------------------
Totals:     (na)   (na)   (na) H/s
Highest:     0.0 H/s
HASHRATE REPORT - CPU
| ID |    10s |    60s |    15m |
|  0 |   45.1 |   (na) |   (na) |
---------------------------
HASHRATE REPORT - AMD
| ID |    10s |    60s |    15m | ID |    10s |    60s |    15m |
|  0 |  130.9 |   (na) |   (na) |  1 |  135.2 |   (na) |   (na) |
|  2 |  142.9 |   (na) |   (na) |  3 |  147.2 |   (na) |   (na) |
|  4 |  153.7 |   (na) |   (na) |  5 |  159.4 |   (na) |   (na) |
|  6 |   97.1 |   (na) |   (na) |  7 |  158.1 |   (na) |   (na) |
-----------------------------------------------------
Totals:   1169.6   (na)   (na) H/s
Highest:  1170.0 H/s
__________________________________________________________________________
AMD.TXT 

> 
"gpu_threads_conf" : [
  // gpu: Cayman memory:384
  // compute units: 24
  { "index" : 0,
    "intensity" : 200, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : true
  },
  // gpu: Cayman memory:384
  // compute units: 24
  { "index" : 1,
    "intensity" : 210, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : true
  },
  // gpu: Cayman memory:384
  // compute units: 24
  { "index" : 2,
    "intensity" : 220, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : true
  },
  // gpu: Cayman memory:384
  // compute units: 24
  { "index" : 3,
    "intensity" : 230, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : true
  },
  // gpu: Cayman memory:384
  // compute units: 24
  { "index" : 4,
    "intensity" : 240, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : true
  },
  // gpu: Cayman memory:384
  // compute units: 24
  { "index" : 5,
    "intensity" : 250, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : true
  },
  // gpu: Cayman memory:384
  // compute units: 24
  { "index" : 6,
    "intensity" : 250, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : true
  },
  // gpu: Cayman memory:384
  // compute units: 24
  { "index" : 7,
    "intensity" : 250, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : true
  },

],

/*
 * Platform index. This will be 0 unless you have different OpenCL platform - eg. AMD and Intel.
 */
"platform_index" : 1,

m03e5 commented 6 years ago

So i tried various intensity and could not go over "250" anything beyond this renders miner not seeing AMD GU. With intensity value 250 card gives about half of what it should be able to do. Any other recommendations are welcome. Also, does anyone know what does that little switch do on 6990? (near CROSSFIRE )

xmr-stak 2.1.0 30888a3

Brought to you by fireice_uk and psychocrypt under GPLv3. Based on CPU mining code by wolf9466 (heavily optimized by fireice_uk). Based on NVIDIA mining code by KlausT and psychocrypt. Based on OpenCL mining code by wolf9466.

Configurable dev donation level is set to 2.0%

You can use following keys to display reports: 'h' - hashrate 'r' - results 'c' - connection

[2017-12-11 15:48:57] : Start mining: MONERO [2017-12-11 15:48:57] : Starting NVIDIA GPU thread 0, no affinity. [2017-12-11 15:48:57] : Compiling code and initializing GPUs. This will take a while... [2017-12-11 15:48:59] : Device 0 work size 8 / 32. [2017-12-11 15:49:04] : Device 1 work size 8 / 32. [2017-12-11 15:49:09] : Starting AMD GPU thread 0, no affinity. [2017-12-11 15:49:09] : Starting AMD GPU thread 1, no affinity. [2017-12-11 15:49:09] : Starting 1x thread, affinity: 0. [2017-12-11 15:49:09] : hwloc: memory pinned [2017-12-11 15:49:09] : Starting 1x thread, affinity: 2. [2017-12-11 15:49:09] : hwloc: memory pinned [2017-12-11 15:49:09] : Starting 1x thread, affinity: 4. [2017-12-11 15:49:09] : hwloc: memory pinned [2017-12-11 15:49:09] : Starting 1x thread, affinity: 6. [2017-12-11 15:49:09] : hwloc: memory pinned [2017-12-11 15:49:09] : Starting 1x thread, affinity: 8. [2017-12-11 15:49:09] : hwloc: memory pinned [2017-12-11 15:49:09] : Starting 1x thread, affinity: 10. [2017-12-11 15:49:09] : hwloc: memory pinned [2017-12-11 15:49:09] : Starting 1x thread, affinity: 12. [2017-12-11 15:49:09] : hwloc: memory pinned [2017-12-11 15:49:09] : Starting 1x thread, affinity: 14. [2017-12-11 15:49:09] : hwloc: memory pinned [2017-12-11 15:49:09] : Starting 1x thread, affinity: 16. [2017-12-11 15:49:09] : hwloc: memory pinned [2017-12-11 15:49:09] : Starting 1x thread, affinity: 18. [2017-12-11 15:49:09] : hwloc: memory pinned [2017-12-11 15:49:09] : Starting 1x thread, affinity: 20. [2017-12-11 15:49:09] : hwloc: memory pinned [2017-12-11 15:49:09] : Starting 1x thread, affinity: 22. [2017-12-11 15:49:09] : hwloc: memory pinned [2017-12-11 15:49:09] : Fast-connecting to ca.minexmr.com:3333 pool ... [2017-12-11 15:49:09] : Pool ca.minexmr.com:3333 connected. Logging in... [2017-12-11 15:49:10] : Difficulty changed. Now: 2000450. [2017-12-11 15:49:10] : Pool logged in. [2017-12-11 15:50:33] : New block detected. HASHRATE REPORT - CPU | ID | 10s | 60s | 15m | ID | 10s | 60s | 15m | | 0 | 31.3 | 31.8 | (na) | 1 | 37.3 | 37.1 | (na) | | 2 | 37.4 | 37.0 | (na) | 3 | 37.7 | 37.5 | (na) | | 4 | 39.5 | 39.2 | (na) | 5 | 36.0 | 36.3 | (na) | | 6 | 39.8 | 39.3 | (na) | 7 | 39.5 | 39.4 | (na) | | 8 | 39.8 | 39.6 | (na) | 9 | 39.5 | 39.5 | (na) | | 10 | 41.3 | 41.2 | (na) | 11 | 41.2 | 41.2 | (na) |

HASHRATE REPORT - AMD | ID | 10s | 60s | 15m | ID | 10s | 60s | 15m | | 0 | 150.2 | 150.1 | (na) | 1 | 150.4 | 150.5 | (na) |

HASHRATE REPORT - NVIDIA | ID | 10s | 60s | 15m | | 0 | (na) | 25.5 | (na) |

Totals: (na) 785.2 (na) H/s Highest: 0.0 H/s

m03e5 commented 6 years ago

I got switch figured: amd 6990 switch

m03e5 commented 6 years ago

while its very convenient to have a cpu+ ati+ nvda miners in one, having cards underperform significantly, it was decided to switch 6990 to claymore 9.7, now card does what it should hash - 766hs. I would be really happy to use xmr stack all in one if this problem would of have been fixed. Greets!

        Claymore CryptoNote GPU Miner  v9.7 Beta            ║

╚════════════════════════════════════════════════════════════════╝ XMR: 1 pool is specified Main pool is ca.minexmr.com:3333

Cards available: 2 GPU #0: name: Cayman, 2048 MB available, 24 units GPU #1: name: Cayman, 2048 MB available, 24 units Total cards: 2

Catalyst 15.x is REQUIRED for best performance and compatibility At least 16 GB of Virtual Memory is required for multi-GPU systems Make sure you defined GPU_MAX_ALLOC_PERCENT 100 Be careful with overclocking, use default clocks for first tests Initializing...

GPU #0: HashCnt = 768 GPU #1: HashCnt = 768 POOL version GPU #0: -a 3 mode selected GPU #1: -a 3 mode selected 1 pool specified. Remote management (READ-ONLY MODE) is enabled on port 3333 Press "m" key for tune mode, "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools Stratum - connecting to 'ca.minexmr.com' <158.69.xxx..xxx> port 3333 (unsecure) DevFee: Stratum - connecting to 'xmr.suprnova.cc' <145.239.xxx.xxx> port 5222 (unsecure) Stratum - Connected (unsecure) Stratum - Connected (unsecure) Pool Diff 200008 DevFee: Pool Diff 10000 DevFee: 12/12/17-10:39:15 - SHARE FOUND (target 5000) - (GPU 1 of 2) Speed: 766 h/s, Total Shares: 0, Rejected: 0, Mining time: 00:01 12/12/17-10:39:31 - SHARE FOUND (target 200007) - (GPU 1 of 2) Share accepted (140 ms)! 12/12/17-10:39:38 - New job received from ca.minexmr.com:3333 Speed: 766 h/s, Total Shares: 1, Rejected: 0, Mining time: 00:01

psychocrypt commented 6 years ago

please remove the amd.txt and try to generate the config again. an other app is reducing your memory to only 380MByte. This is the reason for your issu.

Simaex commented 6 years ago

I remove amd.txt several times, no change. No other apps use video adapters, this is a dedicated rig. Fresh reboot do not change anything. Claymore 9.7 is running on the system 385 H/s per GPU, 3040 H/s for 4 cards (8 GPU). Should I manually set different memory size in config? What size should I try (each GPU have 2G dedicated RAM) if it is reasonable to do so?

m03e5 commented 6 years ago

@Simaex - thought you have claymore 9.7 doing normally.... as mine does 766 stable(OC switch pos 1) with it. P.S. i ahve looked at the logs from claymore9.7 from nicehash and here some settings from it:

15:59:21:863 169c ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» 15:59:21:863 169c º Claymore CryptoNote GPU Miner v9.7 Beta º 15:59:21:878 169c ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ¼ 15:59:22:097 169c XMR: 1 pool is specified 15:59:22:097 169c Main pool is cryptonight.usa.nicehash.com:33355 Cards available: 2 15:59:22:972 169c GPU #1: name: Cayman, 2048 MB available, 24 units 15:59:22:972 169c Total cards: 1 15:59:22:988 169c Initializing... 15:59:22:988 169c card 0, m1 2048, m2 512 w 192 15:59:22:988 169c 0 m = 2 15:59:22:988 169c GPU #0: HashCnt = 768 15:59:22:988 169c POOL version 15:59:23:003 169c b155 15:59:24:066 169c GPU #0: -a 3 mode selected 15:59:37:629 169c 1 pool specified.

Simaex commented 6 years ago

@m03e5 I have CCNM 9.7 running, 785-807 H/s per card but it did not help much in tuning XMR-STAK :-)

psychocrypt commented 6 years ago

@Simaex Could you please run clinfo that I have a overview of your gpus and the memory which is reported by opencl.

psychocrypt commented 6 years ago

Which app sdk do you have installed. I compiled the binary with app sdk 3 maybe there is something incompatible with app sdk 2.X

m03e5 commented 6 years ago

@psychocrypt while it could matter how miner is compiled on @Simaex system, if he did it himself, but i am using already compiled (by Dev's) version for win. I would assume original compilation would be properly assembled to work on any system. looking forward to see the outcome. Thx

p.s. it seems that we all agree on one - it is VRAM related problem.

Simaex commented 6 years ago

I try to use pre-compiled windows version. Please find clinfo output. I run it when Claymore 9.7 was working. HD6990.txt

Simaex commented 6 years ago

No chances to get HD6990 working I assume :-(

m03e5 commented 6 years ago

As it appears like... 8(

On Dec 22, 2017 2:43 PM, "Simaex" notifications@github.com wrote:

No chances to get HD6990 working I assume :-(

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/fireice-uk/xmr-stak/issues/472#issuecomment-353679159, or mute the thread https://github.com/notifications/unsubscribe-auth/Ag1qA4745HBAnDMLUEZKWEPu9hDIA5djks5tDCKVgaJpZM4Q87Ll .

elizeche commented 6 years ago

Hi friends, I am new here ,but have almost same problem. Using Clarymore, and it keeps showing 0 h/s, no matter what I do. Maybe some step wrong, since I am new at mining world. Could someone help?Thanks!

error gpu

dougvj commented 6 years ago

I have the same problem on Arch Linux running the proprietary driver with failing to detect memory of the GPU (HD 6990). Setting intensity manually solves the problem (although I am not getting what the hashrate should be for this card, perhaps an unrelated issue as this card has just been repaired)

Attached is a clinfo dump and the autogenned amd.txt amd.txt clinfo.txt

Simaex commented 6 years ago

@elizeche your problem is that you are trying to use miner that do not support your card. Use 9.7 version and please look for appropriate thread to ask your questions. @dougvj what hashrate do you get for HD6990?

dougvj commented 6 years ago

@Simaex I get about 260H/s per GPU so about 520H/s for the entire card. Benchmarks indicate that this card can exceed 700H/s. Could merely be an optimization problem since none of the benchmarks I see use xmr-stak or it could be a problem with my particular card. I will spend more time investigating it this weekend trying different miners looking into throttling and so on, I just wanted to report that I see the same behavior of xmr-stak autosetting an intensity of 0 here.

Simaex commented 6 years ago

@dougvj I have four HD6990 - the same for each, 770 H/s for card with Claymore 9.7 but not more then 500 with xmr-stak when manually setting intensity.

FozanShahid commented 6 years ago

can i please get the claymore compiled one and the config file? XMR STAK is only using 50-60% of my HD6770 1GD5 and claymore gives error

TheBulitt commented 6 years ago

Claymore 9.7 is the only monero miner that will work with "Terascale" cards... all the other miners (including XMR-stak) only work on GCN 1.0 or newer cards (HD 7850 and up)

xmronadaily commented 6 years ago

There's still a lot of people out there using the old HD 5970s, 6990s, if Claymore managed to make it work in his miner, is there nothing that can be done for Stak miner? @psychocrypt @fireice-uk

Please, especially after the PoW change, all these TeraScale gpus will be out of work on XMR, would it be possible to fix this issue in the upcoming releases? Compensate the work with higher fee on older gpus or something, it will still be very much appreciated by miners and used nonetheless. Thank you for considering, looking forward to a reply.

psychocrypt commented 6 years ago

Could you try if this #624 PR is solving the issue? If so I can check if I can integrate this PR into our development tree. This PR used two memory spaces which should workaround the OpenCL limitations which allows that only a few hundret MB memory are allocateable.

xmronadaily commented 6 years ago

@psychocrypt Thank you so much for the reply. I can certainly try, but I'm afraid I'm a noob when it comes to actually understanding how to incorporate what's changed in that PR, would I need to build the miner from source with that PR included and if so, how would I go about it? I'm assuming that just trying the steps listed under "How To" wouldn't work on Xmas bug fix release?

I'm currently not home where my miners are, but I have teamviewer setup, and I just recently installed Ubuntu 16.04 on laptop here as dual boot, so if building from source is needed I'm sure I could manage if you could provide me with some how-to steps and I'd more than love to help you test this! Thanks once again for the reply!

Simaex commented 6 years ago

I am trying to compile with #624 as suggested but as for now receiving error (and a lot of warnings). Please advise how to proceed.

fatal error C1083: Cannot open include file: 'dlfcn.h': No such file or directory [C:\Users\alex\OneDrive\Documents\xmr-stak\build\xmr-s tak-backend.vcxproj]

psychocrypt commented 6 years ago

which version of visual studio do you use. Please post all command do you used to compile xmr-stak.

Simaex notifications@github.com schrieb am Di., 13. März 2018, 22:27:

I am trying to compile with #624 https://github.com/fireice-uk/xmr-stak/pull/624 as suggested but as for now receiving error (and a lot of warnings). Please advise how to proceed.

fatal error C1083: Cannot open include file: 'dlfcn.h': No such file or directory [C:\Users\alex\OneDrive\Documents\xmr-stak\build\xmr-s tak-backend.vcxproj]

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/fireice-uk/xmr-stak/issues/472#issuecomment-372824440, or mute the thread https://github.com/notifications/unsubscribe-auth/AYsxtm4EsRWGGA3pMBGL0OWZMfGjzuBvks5teDnLgaJpZM4Q87Ll .

Simaex commented 6 years ago

Visual Studio Community 2017 15.6.2 "C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\Tools\VsMSBuildCmd.bat" set CMAKE_PREFIX_PATH=C:\xmr-stak-dep\hwloc;C:\xmr-stak-dep\libmicrohttpd;C:\xmr-stak-dep\openssl cmake -G "Visual Studio 15 2017 Win64" -DCUDA_ENABLE=OFF -T v140,host=x64 .. cmake --build . --config Release --target install

psychocrypt commented 6 years ago

please emty the build folder and replace v140 with v141

Simaex commented 6 years ago

I have successfully build master version with #624 . Program is running with the same hash rate as before. The same 384 memory is detected per GPU. I try to change intensity manually and available memory size also but do not get even half the speed that HD6990 can run. Please advise what settings to check. The settingth for GPU0 are as automatically generated, the rest are modification I try to test. amd.txt

psychocrypt commented 6 years ago

Please post the hash rate with the default intensity and if you incrase the hash rate e.g. to 600. Alsotest if it helps to set strided_index to false. As I know the 6990 is a gpu with two sockets on one card. Do you see two gpu in your config if you have one physical gpu?

Simaex commented 6 years ago

A single HD6990 4G is actually two Caymane GPU with 2G memory each that are soldered on a single PCB. So in any miner so far I see it as two separate GPU. Hash rate up to 600 you mean intencity 600?

Simaex commented 6 years ago

Results with automatic amd.txt settings [2018-03-14 21:21:12] : New block detected. HASHRATE REPORT - CPU | ID | 10s | 60s | 15m | | 0 | 47.6 | 48.3 | (na) | Totals (CPU): 47.6 48.3 0.0 H/s

HASHRATE REPORT - AMD | ID | 10s | 60s | 15m | ID | 10s | 60s | 15m | | 0 | 125.9 | 125.9 | (na) | 1 | 125.7 | 125.7 | (na) | | 2 | 126.6 | 126.6 | (na) | 3 | 126.7 | 126.6 | (na) | | 4 | 125.2 | 125.4 | (na) | 5 | 125.7 | 125.6 | (na) | | 6 | 75.6 | 75.5 | (na) | 7 | 126.2 | 126.4 | (na) | Totals (AMD): 957.5 957.7 0.0 H/s

Totals (ALL): 1005.1 1005.9 0.0 H/s Highest: 1018.3 H/s

more stable after few minutes

HASHRATE REPORT - AMD | ID | 10s | 60s | 15m | ID | 10s | 60s | 15m | | 0 | 125.9 | 125.9 | (na) | 1 | 125.7 | 125.7 | (na) | | 2 | 126.4 | 126.5 | (na) | 3 | 126.5 | 126.6 | (na) | | 4 | 125.2 | 125.3 | (na) | 5 | 125.7 | 125.6 | (na) | | 6 | 110.6 | 116.6 | (na) | 7 | 126.3 | 126.3 | (na) | Totals (AMD): 992.4 998.6 0.0 H/s

Simaex commented 6 years ago

When I try to set intencity 600 I get [2018-03-14 21:32:56] : Error CL_INVALID_BUFFER_SIZE when calling clCreateBuffer to create hash scratchpads buffer. 550 did not cause error, waiting for stable hashrate.

psychocrypt commented 6 years ago

What is if you change strided_index to false?

Simaex commented 6 years ago

I make a mistake, maximum intensity is 509 Results are much better then before. I'll try to play with strided_index now

HASHRATE REPORT - AMD | ID | 10s | 60s | 15m | ID | 10s | 60s | 15m | | 0 | 254.6 | 254.8 | (na) | 1 | 253.8 | 254.0 | (na) | | 2 | 255.1 | 255.1 | (na) | 3 | 255.6 | 255.3 | (na) | | 4 | 255.6 | 255.6 | (na) | 5 | 255.4 | 255.6 | (na) | | 6 | 169.9 | 169.9 | (na) | 7 | 255.0 | 255.2 | (na) | Totals (AMD): 1955.0 1955.4 0.0 H/s

Simaex commented 6 years ago

With strided_index=false a small gain in performance HASHRATE REPORT - AMD | ID | 10s | 60s | 15m | ID | 10s | 60s | 15m | | 0 | 259.3 | 259.3 | (na) | 1 | 258.4 | 258.6 | (na) | | 2 | 259.6 | 259.6 | (na) | 3 | 260.2 | 260.1 | (na) | | 4 | 259.5 | 259.5 | (na) | 5 | 258.9 | 259.0 | (na) | | 6 | 171.2 | 171.3 | (na) | 7 | 258.1 | 258.0 | (na) | Totals (AMD): 1985.1 1985.4 0.0 H/s

Simaex commented 6 years ago

With strided_index=false it was possible to set intencity 512 so we get 100% gain in performance with #624 . Is it possible to make the same trick once more and run not two but three times the original ? As for now I was able to get 400+ from single GPU with old miner, but only 375 are really stable and worth trouble. amd.txt

HASHRATE REPORT - AMD | ID | 10s | 60s | 15m | ID | 10s | 60s | 15m | | 0 | 260.7 | 260.6 | (na) | 1 | 260.8 | 260.7 | (na) | | 2 | 259.6 | 259.9 | (na) | 3 | 261.7 | 261.7 | (na) | | 4 | 259.9 | 259.7 | (na) | 5 | 260.9 | 261.0 | (na) | | 6 | 172.2 | 172.2 | (na) | 7 | 258.7 | 258.5 | (na) | Totals (AMD): 1994.5 1994.5 0.0 H/s

Simaex commented 6 years ago

It seems that GPU6 low hashrate is corresponding with teamviewer activity

HASHRATE REPORT - AMD | ID | 10s | 60s | 15m | ID | 10s | 60s | 15m | | 0 | 260.4 | 260.4 | 260.6 | 1 | 261.0 | 261.0 | 260.9 | | 2 | 260.1 | 259.6 | 259.9 | 3 | 261.7 | 261.7 | 261.8 | | 4 | 259.7 | 259.2 | 259.6 | 5 | 261.0 | 261.0 | 261.0 | | 6 | 172.2 | 205.3 | 247.9 | 7 | 258.2 | 258.4 | 258.4 | Totals (AMD): 1994.3 2026.6 2070.0 H/s

xmronadaily commented 6 years ago

If it's worth anything, this is how it looks when Claymore miner is started. So these are two physical cards, each has two gpu cores, for a total of four.

ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» 15:47:28:011 b18 º Claymore CryptoNote GPU Miner v9.7 Beta º 15:47:28:013 b18 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ¼ 15:47:28:214 b18 XMR: 1 pool is specified 15:47:28:215 b18 Main pool is masari.superpools.net:7777 15:47:29:598 b18 Cards available: 4 15:47:29:599 b18 GPU #0: name: Cayman, 2048 MB available, 24 units 15:47:29:600 b18 GPU #1: name: Cayman, 2048 MB available, 24 units 15:47:29:601 b18 GPU #2: name: Cayman, 2048 MB available, 24 units 15:47:29:602 b18 GPU #3: name: Cayman, 2048 MB available, 24 units 15:47:29:603 b18 Total cards: 4 15:47:29:608 b18 Initializing...

15:47:29:609 b18 card 0, m1 2048, m2 512 w 192 15:47:29:609 b18 0 m = 2 15:47:29:612 b18 GPU #0: HashCnt = 768 15:47:29:613 b18 card 1, m1 2048, m2 512 w 192 15:47:29:613 b18 1 m = 2 15:47:29:614 b18 GPU #1: HashCnt = 768 15:47:29:615 b18 card 2, m1 2048, m2 512 w 192 15:47:29:616 b18 2 m = 2 15:47:29:617 b18 GPU #2: HashCnt = 768 15:47:29:618 b18 card 3, m1 2048, m2 512 w 192 15:47:29:619 b18 3 m = 2 15:47:29:620 b18 GPU #3: HashCnt = 768 15:47:29:621 b18 POOL version 15:47:29:622 b18 b155 15:47:33:992 b18 GPU #0: -a 3 mode selected 15:47:33:993 b18 GPU #1: -a 3 mode selected 15:47:33:995 b18 GPU #2: -a 3 mode selected 15:47:33:996 b18 GPU #3: -a 3 mode selected 15:47:43:440 b18 1 pool specified. 15:47:43:547 ae4 Stratum - connecting to 'masari.superpools.net

The full potenial of these cards on this miner with pretty standard clock setings is about ~ 375-380 h/s per gpu core, but with some OC they can go to 400 each core, so one card should be giving close to or over 800 h/s.

This is significant improvement that you're making on this issue, @psychocrypt and @Simaex , thank you so much! @Simaex would you please care sharing the compiled stak binaries with the #624 so that I can offer my cards for testing as well in case you're busy, etc?

bovcan commented 6 years ago

Teamviewer can be a pain. I rather use RDP, even if pc is in the LAN. I always have lag when using Teamviewer...

Simaex commented 6 years ago

Compiled xmr-stak 2.2.0 windows binaries with #624 Please share you results, xmr-stak-2.2.0_#624(AMD+CPU).zip

psychocrypt commented 6 years ago

please try to use two threads per device with the compiled pull request to fully utilze your 6990.

Simaex commented 6 years ago

Please elaborate how to do it. What settings should I alter? Or I need to run two instances of the miner?

fireice-uk / xmr-stak

Miner not using AMD 6990 GPU #472

Basic information

Stability issue

Platform index. This will be 0 unless you have different OpenCL platform - eg. AMD and Intel. */ "platform_index" : 0,

You can use following keys to display reports: 'h' - hashrate 'r' - results 'c' - connection

HASHRATE REPORT - NVIDIA | ID | 10s | 60s | 15m | | 0 | (na) | 25.5 | (na) |

Totals: (na) 503.8 (na) H/s Highest: 0.0 H/s

You can use following keys to display reports: 'h' - hashrate 'r' - results 'c' - connection

HASHRATE REPORT - AMD | ID | 10s | 60s | 15m | ID | 10s | 60s | 15m | | 0 | 150.2 | 150.1 | (na) | 1 | 150.4 | 150.5 | (na) |

HASHRATE REPORT - NVIDIA | ID | 10s | 60s | 15m | | 0 | (na) | 25.5 | (na) |

Totals: (na) 785.2 (na) H/s Highest: 0.0 H/s

while its very convenient to have a cpu+ ati+ nvda miners in one, having cards underperform significantly, it was decided to switch 6990 to claymore 9.7, now card does what it should hash - 766hs. I would be really happy to use xmr stack all in one if this problem would of have been fixed. Greets!

@Simaex - thought you have claymore 9.7 doing normally.... as mine does 766 stable(OC switch pos 1) with it. P.S. i ahve looked at the logs from claymore9.7 from nicehash and here some settings from it:

Results with automatic amd.txt settings [2018-03-14 21:21:12] : New block detected. HASHRATE REPORT - CPU | ID | 10s | 60s | 15m | | 0 | 47.6 | 48.3 | (na) | Totals (CPU): 47.6 48.3 0.0 H/s

more stable after few minutes

I make a mistake, maximum intensity is 509 Results are much better then before. I'll try to play with strided_index now

It seems that GPU6 low hashrate is corresponding with teamviewer activity