Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 829.

QuadraQ

sr. member

Activity: 480

Merit: 250

Quote from: coinpops on June 11, 2017, 08:12:34 PM

Hello, I'm having an issue with Claymore not detecting my GPUs.

Claymore has been working great with my two RX 480s in the PCIe 16x slots in my motherboard. Since I want to see if I can use more GPUs, I bought two 1x->16x PCIe risers that are now plugged in to my mobo's PCIe 1x slots with my two 480s. They seem to be working fine in Windows -- they're shown in the device manager and in Radeon Settings. But when I start Claymore, it's saying that no GPUs were found.

Any ideas?

Did you connect power to the riser cards?

coinpops

newbie

Activity: 5

Merit: 0

Hello, I'm having an issue with Claymore not detecting my GPUs.

Claymore has been working great with my two RX 480s in the PCIe 16x slots in my motherboard. Since I want to see if I can use more GPUs, I bought two 1x->16x PCIe risers that are now plugged in to my mobo's PCIe 1x slots with my two 480s. They seem to be working fine in Windows -- they're shown in the device manager and in Radeon Settings. But when I start Claymore, it's saying that no GPUs were found.

Any ideas?

mmrj9

newbie

Activity: 3

Merit: 0

Hello guys, can anyone post here a start.bat file ready for Eth + Pascal dual mining pls Cheesy

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: ?? on ??

According to what I observed, it may be legitimate misreporting of Eth hashrate whilst dual-mining.

Probably you mean that different GPU rounds take different time in your tests, am I correct? There are two reasons for it at least:
1. You started two separate miners, both try to load GPU completely so different GPU rounds will have different time. My miner uses different approach. You can press "s" key to see hashrate for latest GPU round, press it many times and see if there are fluctuations, for Polaris card you should notice them but they are related to item #2 below.
2. At some circumstances GPU can be slower for a second or so, then work a few seconds at 100%, and so on. Especially Polaris cards. It was a problem in v9.0 but I've almost fixed it in recent versions, these fluctuations are low and rare now even on Polaris. v8 is free of this issue, but has lower speed for second coin.
Anyway, may be I should also show additional counter that measures hashrate for a minute when "s" is pressed, I will try to add it in next update.

QuadraQ

sr. member

Activity: 480

Merit: 250

So I recently added two GTX 1060 cards to my mining rig to go with my trusty AMD 7970. I have the latest AMD and CUDA drivers installed, specifically AMD 17.6.1 and Nvidia CUDA 8.0.61. I'm mining in dual mode with ETH and DCR, and the 1060's are brand new and not overclocked (at least not yet).

So everything was going fine until about 5:20 am last night. Looking through the log files here are the relevant bits if info:

Code:

05:20:50:355 161c NVML: cannot get current temperature, error 15
05:20:50:359 161c NVML: cannot get fan speed, error 15
...
05:20:53:253 734 GPU 2, GpuMiner cu_k00 failed 30, unknown error
05:20:53:312 1748 GPU 1, GpuMiner cu_k00 failed 30, unknown error
05:20:53:465 1748 GPU 1, GpuMiner kx failed 1
05:20:53:325 1624 parse packet: 234
05:20:53:484 734 GPU 2, GpuMiner kx failed 1
05:20:53:477 1748 Set global fail flag, failed GPU1
05:20:53:483 1624 ETH: job is the same
05:20:53:499 734 Set global fail flag, failed GPU2
05:20:53:540 1748 GPU 1 failed
05:20:53:563 d04 GPU 1, GpuMiner cu_k00 failed 30, unknown error
05:20:53:592 d04 GPU 1, GpuMiner kx failed 1
05:20:53:604 734 GPU 2 failed
05:20:53:616 1188 GPU 2, GpuMiner cu_k00 failed 30, unknown error
05:20:53:532 1624 new buf size: 0
05:20:53:630 161c NVML: cannot get current temperature, error 999 (an internal driver error occurred)
...
05:20:56:809 161c NVML: cannot get current temperature, error 999 (an internal driver error occurred)
05:20:56:813 161c NVML: cannot get fan speed, error 999 (an internal driver error occurred)
05:20:56:872 161c NVML: cannot get current temperature, error 999 (an internal driver error occurred)
05:20:56:876 161c NVML: cannot get fan speed, error 999 (an internal driver error occurred)
...
05:21:19:101 161c WATCHDOG: GPU error, you need to restart miner :(
...
05:21:20:339 161c Restarting OK, exit...

When the next log file begins after the restart, one of the GTX 1060 cards isn't even recognized:

Code:

05:21:23:634 101c OpenCL platform: AMD Accelerated Parallel Processing
05:21:23:638 101c OpenCL platform: NVIDIA CUDA
05:21:23:644 101c OpenCL initializing...
05:21:23:649 101c AMD Cards available: 1
05:21:23:654 101c GPU #0: Tahiti, 3072 MB available, 28 compute units
...
05:21:24:269 101c CUDA initializing...
05:21:24:273 101c NVIDIA Cards available: 1
05:21:24:277 101c CUDA Driver Version/Runtime Version: 8.0/8.0
05:21:24:286 101c GPU #1: GeForce GTX 1060 6GB, 6144 MB available, 10 compute units, capability: 6.1
05:21:24:291 101c Total cards: 2
05:21:33:321 101c NVML version: 8.376.51

I noticed that when I ran GPU-Z to check on the driver versions, it recognized all three cards BUT one of the 1060's didn't show a checkmark for CUDA anymore! After I restarted and checked GPU-Z again, both cards showed checkmarks for CUDA again. Weird.

These are the driver versions according to GPU-Z

Code:

22.19.171.1 (Crimson 17.6.1) Beta
21.21.13.7651 (ForceWare 376.51) Beta

I'm using Windows 8.1 Pro 64-bit with all the latest updates, and Claymore's Dual miner v9.5.

I don't think the cards overheated since just before the errors above the miner reported temperatures that should be well within specifications:

Code:

05:19:46:774 161c GPU0 t=80C fan=67%; GPU1 t=82C fan=75%, GPU2 t=79C fan=70%
05:19:46:778 161c em hbt: 250, dm hbt: 0, fm hbt: 62,
05:19:46:783 161c watchdog - thread 0 (gpu0), hb time 266
05:19:46:788 161c watchdog - thread 1 (gpu0), hb time 125
05:19:46:793 161c watchdog - thread 2 (gpu1), hb time 63
05:19:46:798 161c watchdog - thread 3 (gpu1), hb time 15
05:19:46:803 161c watchdog - thread 4 (gpu2), hb time 46
05:19:46:808 161c watchdog - thread 5 (gpu2), hb time 0
...
05:19:50:112 1624 ETH - Total Speed: 48.685 Mh/s, Total Shares: 154, Rejected: 0, Time: 04:02
05:19:50:116 1624 ETH: GPU0 12.885 Mh/s, GPU1 17.799 Mh/s, GPU2 18.001 Mh/s
05:19:50:120 1624 DCR - Total Speed: 1737.263 Mh/s, Total Shares: 645, Rejected: 0
05:19:50:124 1624 DCR: GPU0 901.935 Mh/s, GPU1 415.303 Mh/s, GPU2 420.025 Mh/s

I'm stumped. Obviously stability is king for any mining rig, and I'm concerned this may keep happening but I don't know what to do to address it. Any ideas?

VTdude12

member

Activity: 76

Merit: 10

Thanks to everyone who responded to my post!

To this...

Quote from: Aquazi on June 11, 2017, 03:53:04 PM

reported hashrate depends on the valid shares you submit.

You can have lower or higher than the calculated one.

You should atleast wait 24 hours and see how much they are aligned.

If there's a -10% difference it's likely that you are having memory errors.

Are you saying maybe overclocked too much / under volt? Or true hardware issue? Didn't think this would be the case if claymore was able to run stably for 24/7 Huh

thaelin

newbie

Activity: 64

Merit: 0

OK I have beat this old dog hard, is there some setting in Win7 Ult 64 that you have to set to see more than 3 cards? Hve just built 2 seven head machines with Asus z270A Celeron dual core 3gig 8gig ram and so far 6 each evga gtx 1060 SSC 6 gig cards. Sad to see all that hash power resting and not working. I really need help on this one. Great software and runs with no rejects at all for me. Really cant see doing win10 cause of all the junk in it. I was a beta tester for it and had to back away.

thay

Aquazi

full member

Activity: 215

Merit: 100

Quote from: VTdude12 on June 11, 2017, 12:59:06 PM

Question about ETH mining on ethermine.org pool...

My rig within Claymore is hashing at ~198MH, but the pool is displaying the following:

Hashrate as reported by miner to pool = ~198MH
Effective current hashrate = 174MH
Avg Effective hashrate 24hr = 175MH

I know some variation between miner and pool is expected, but >20MH seems like a lot to me!!!

Anyone experienced this before? Huh

Fixes? Or known issue? Thanks!!!

reported hashrate depends on the valid shares you submit.

You can have lower or higher than the calculated one.

You should atleast wait 24 hours and see how much they are aligned.

If there's a -10% difference it's likely that you are having memory errors.

myty

newbie

Activity: 3

Merit: 0

Hello.
I am using R9 380 Nitro Sapphire.
When i am mining solo Ethereum all is working fine, but when i dual mine with DECRED i am get artefacts.
Why is that?
Thank you!

grubiorz

newbie

Activity: 6

Merit: 0

Any tips on improving gtx 1070 hashrate?
Currently I'm getting ~81,8Mh/s with 3x overclocked gtx 1070, but whattomine.com shows they should do ~85,5Mh/s. When mining only ETH the hashrate increases to ~82,5, so stil lower than expected.
Other coins are mined with exactly the same hashrate as showed on whattomine.
CUDA 8, windows 7 x64, 375.95 driver

pehoko

full member

Activity: 232

Merit: 100

Seems that catalyst driver not working, only crimson.

Simon_Grape

newbie

Activity: 41

Merit: 0

Quote from: VTdude12 on June 11, 2017, 12:59:06 PM

Question about ETH mining on ethermine.org pool...

My rig within Claymore is hashing at ~198MH, but the pool is displaying the following:

Hashrate as reported by miner to pool = ~198MH
Effective current hashrate = 174MH
Avg Effective hashrate 24hr = 175MH

I know some variation between miner and pool is expected, but >20MH seems like a lot to me!!!

Anyone experienced this before? Huh

Fixes? Or known issue? Thanks!!!

VTdude - i see the same thing on ethermine.org. My average hashrate never hits my reported hashrate

pehoko

full member

Activity: 232

Merit: 100

OpenCL error -4 (0) - cannot create DAG on GPU

I get this error, gpu r9 380 4gb

VTdude12

member

Activity: 76

Merit: 10

Question about ETH mining on ethermine.org pool...

My rig within Claymore is hashing at ~198MH, but the pool is displaying the following:

Hashrate as reported by miner to pool = ~198MH
Effective current hashrate = 174MH
Avg Effective hashrate 24hr = 175MH

I know some variation between miner and pool is expected, but >20MH seems like a lot to me!!!

Anyone experienced this before? Huh

Fixes? Or known issue? Thanks!!!

EarthZephyR

newbie

Activity: 4

Merit: 0

Is it true that nvidia get more hashrate on linux?

edwardspitz

sr. member

Activity: 546

Merit: 250

Quote from: edwardspitz on June 11, 2017, 12:06:32 PM

Quote from: Claymore on June 11, 2017, 08:12:47 AM

Quote from: edwardspitz on June 11, 2017, 07:11:14 AM

Can't seem to find api.txt - anyone knows if documentation for Claymore API can be found anywhere?

Download v9.5 for Windows, unpack it and check "Remote manager" folder.

Oh shoot, knowing about this could have saved me some work

I have been working on a new log format, because I was not really happy about the existing one. The one I have written makes a http request to port 3333 and parses the result. It writes two separate logs that looks that look like this:

GPU's:

Code:

2017-06-11T17:27:31Z02:00, machine: minr, id: GPU0, temp: 72, fan: 53, speed: 28.778, shares: 178
2017-06-11T17:27:31Z02:00, machine: minr, id: GPU1, temp: 72, fan: 40, speed: 29.183, shares: 209
2017-06-11T17:27:31Z02:00, machine: minr, id: GPU2, temp: 67, fan: 70, speed: 24.047, shares: 214
2017-06-11T17:27:31Z02:00, machine: minr, id: GPU3, temp: 74, fan: 70, speed: 28.903, shares: 50
2017-06-11T17:27:41Z02:00, machine: minr, id: GPU0, temp: 72, fan: 53, speed: 28.770, shares: 178
2017-06-11T17:27:41Z02:00, machine: minr, id: GPU1, temp: 72, fan: 40, speed: 29.194, shares: 209
2017-06-11T17:27:41Z02:00, machine: minr, id: GPU2, temp: 68, fan: 70, speed: 24.051, shares: 215
2017-06-11T17:27:41Z02:00, machine: minr, id: GPU3, temp: 74, fan: 70, speed: 28.906, shares: 51

Totals:

Code:

2017-06-11T17:25:31Z02:00, machine: minr, total_speed: 110.921, total_shares: 634, total_rejected: 1, avg_speed_per_card: 27.73, avg_shares_per_card: 158.5, avg_temp: 66.5, avg_fan: 58.25
2017-06-11T17:25:41Z02:00, machine: minr, total_speed: 110.939, total_shares: 635, total_rejected: 1, avg_speed_per_card: 27.73, avg_shares_per_card: 158.75, avg_temp: 67.5, avg_fan: 58.25
2017-06-11T17:25:51Z02:00, machine: minr, total_speed: 110.912, total_shares: 635, total_rejected: 1, avg_speed_per_card: 27.73, avg_shares_per_card: 158.75, avg_temp: 68.5, avg_fan: 58.25
2017-06-11T17:26:01Z02:00, machine: minr, total_speed: 110.876, total_shares: 636, total_rejected: 1, avg_speed_per_card: 27.72, avg_shares_per_card: 159, avg_temp: 69, avg_fan: 58.25

My script is working, but using the `miner_getstat1` would have been a lot cleaner. There is one thing missing from miner_getstat1 though and that is a timestamp.

I'm not sure how to send a TCP request to the API in Linux. Can you provide an example?

Ok I figured it out:

Code:

$ exec 3<>/dev/tcp/192.168.1.186/3333
$ echo -e '{"id":0,"jsonrpc":"2.0","method":"miner_getstat1"}' >&3
$ cat <&3

edwardspitz

sr. member

Activity: 546

Merit: 250

Quote from: Claymore on June 11, 2017, 08:12:47 AM

Quote from: edwardspitz on June 11, 2017, 07:11:14 AM

Can't seem to find api.txt - anyone knows if documentation for Claymore API can be found anywhere?

Download v9.5 for Windows, unpack it and check "Remote manager" folder.

Oh shoot, knowing about this could have saved me some work

I have been working on a new log format, because I was not really happy about the existing one. The one I have written makes a http request to port 3333 and parses the result. It writes two separate logs that looks that look like this:

GPU's:

Code:

2017-06-11T17:27:31Z02:00, machine: minr, id: GPU0, temp: 72, fan: 53, speed: 28.778, shares: 178
2017-06-11T17:27:31Z02:00, machine: minr, id: GPU1, temp: 72, fan: 40, speed: 29.183, shares: 209
2017-06-11T17:27:31Z02:00, machine: minr, id: GPU2, temp: 67, fan: 70, speed: 24.047, shares: 214
2017-06-11T17:27:31Z02:00, machine: minr, id: GPU3, temp: 74, fan: 70, speed: 28.903, shares: 50
2017-06-11T17:27:41Z02:00, machine: minr, id: GPU0, temp: 72, fan: 53, speed: 28.770, shares: 178
2017-06-11T17:27:41Z02:00, machine: minr, id: GPU1, temp: 72, fan: 40, speed: 29.194, shares: 209
2017-06-11T17:27:41Z02:00, machine: minr, id: GPU2, temp: 68, fan: 70, speed: 24.051, shares: 215
2017-06-11T17:27:41Z02:00, machine: minr, id: GPU3, temp: 74, fan: 70, speed: 28.906, shares: 51

Totals:

Code:

2017-06-11T17:25:31Z02:00, machine: minr, total_speed: 110.921, total_shares: 634, total_rejected: 1, avg_speed_per_card: 27.73, avg_shares_per_card: 158.5, avg_temp: 66.5, avg_fan: 58.25
2017-06-11T17:25:41Z02:00, machine: minr, total_speed: 110.939, total_shares: 635, total_rejected: 1, avg_speed_per_card: 27.73, avg_shares_per_card: 158.75, avg_temp: 67.5, avg_fan: 58.25
2017-06-11T17:25:51Z02:00, machine: minr, total_speed: 110.912, total_shares: 635, total_rejected: 1, avg_speed_per_card: 27.73, avg_shares_per_card: 158.75, avg_temp: 68.5, avg_fan: 58.25
2017-06-11T17:26:01Z02:00, machine: minr, total_speed: 110.876, total_shares: 636, total_rejected: 1, avg_speed_per_card: 27.72, avg_shares_per_card: 159, avg_temp: 69, avg_fan: 58.25

My script is working, but using the `miner_getstat1` would have been a lot cleaner. There is one thing missing from miner_getstat1 though and that is a timestamp.

I'm not sure how to send a TCP request to the API in Linux. Can you provide an example?

Xiadas

full member

Activity: 322

Merit: 100

Blockchain Just Entered The Real World

Quote from: ne0x86 on June 11, 2017, 10:36:18 AM

Hi, stills necessary run 15.12 crimson version or can run newer one like 16.3.2 (for example).

For the new cards, you should run the new drivers.

Simon_Grape

newbie

Activity: 41

Merit: 0

For all of you struggling to keep your rigs cool this time of year.. This dude has a cool idea

https://www.youtube.com/watch?v=E-_9F8R_PFU

huntingthesnark

member

Activity: 357

Merit: 26

Thanks both - back to driver fun and games eh! I'd hoped as device manager was happy I'd dodged that bullet. Hey ho.

Cheers much!

Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 829. (Read 6590565 times)