Author

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

donator
Activity: 1610
Merit: 1325
Miners developer
v8.1:

- added Ethereum+Pascal mode for NVidia cards.
- improved "-di detect" option: now after GPU order detection miner starts mining with the detected order.
- now remote management is working in read-only mode by default.
- improved "-mport" option, now you can specify network adapter IP for incoming connections for remote management.
- added "-benchmark" option.
- fixed issue with "-retrydelay" option.
- added  "-v" option.
- a few minor bug fixes and improvements.
- EthMan: added option for font color selection.
newbie
Activity: 22
Merit: 0
Hi, i just started mining with claymore. 5 RX480 red devils, and on of them keeps hashing low, i copy what im getting

ETH - Total Speed: 102.287 Mh/s, Total Shares: 139, Rejected: 0, Time: 01:35
ETH: GPU0 4.220 Mh/s, GPU1 24.774 Mh/s, GPU2 24.149 Mh/s, GPU3 24.665 Mh/s, GPU4 24.718 Mh/s

Can you guys help me and tell why getting that low hash rate

Thanks

It occurs on the primary video card. You can either attach a monitor to it or a dummy vga dongle.
newbie
Activity: 1
Merit: 0
Hi Guys!

I got a problem, mining process hangs on Linux.

Callstack:

Code:
root@min-pc:/sys/devices/pci0000:00/0000:00:1c.5/0000:06:00.0# cat /proc/3277/stack
[] kcl_fence_default_wait+0x1d0/0x270 [amdkcl]
[] fence_wait_timeout+0x7d/0x160
[] amdgpu_bo_create_restricted+0x3af/0x520 [amdgpu]
[] amdgpu_bo_create+0xed/0x190 [amdgpu]
[] amdgpu_vm_init+0x194/0x2f0 [amdgpu]
[] amdgpu_driver_open_kms+0x64/0xe0 [amdgpu]
[] drm_open+0x1f3/0x410 [drm]
[] drm_stub_open+0xa9/0x120 [drm]
[] chrdev_open+0xbf/0x1b0
[] do_dentry_open+0x203/0x310
[] vfs_open+0x4c/0x70
[] path_openat+0x2eb/0x1440
[] do_filp_open+0x91/0x100
[] do_sys_open+0x12d/0x280
[] SyS_open+0x1e/0x20
[] entry_SYSCALL_64_fastpath+0x1e/0xa8
[] 0xffffffffffffffff

A big problem is the process in not interruptible (system restart required).

I use:

Code:
Linux min-pc 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
amdgpu-pro-16.60
newbie
Activity: 7
Merit: 0
Only 3 of my gpus work on one of my rigs. For some reason my 380 is not working but my 3 470s are im on 16.10.3 drivers I can post the log if you need it. Any suggestions?
newbie
Activity: 27
Merit: 0
Hi, i just started mining with claymore. 5 RX480 red devils, and on of them keeps hashing low, i copy what im getting

ETH - Total Speed: 102.287 Mh/s, Total Shares: 139, Rejected: 0, Time: 01:35
ETH: GPU0 4.220 Mh/s, GPU1 24.774 Mh/s, GPU2 24.149 Mh/s, GPU3 24.665 Mh/s, GPU4 24.718 Mh/s

Can you guys help me and tell why getting that low hash rate

Thanks

I had same problem with simplemining Linux running Claymore.

I switched back to Win 10 no problems.

Im running Win 10. Crimson 16.6 for drivers...

That GPU seems locked in core clock and memory clock, dont know why.

Im ticking with the settings of my cards, two of them i get it cool working, but when i apply the same settings to the others two i get

WATCHDOG: GPU 3 hangs in OpenCL call, exit o WATCHDOG: GPU 1 hangs in OpenCL call, exit

Can someone give tips on how to solve this two issues...


Look at this page. I Works with new drivers and modified BIOS.

https://www.techpowerup.com/228536/amd-bios-signature-check-re-enabled-with-relive-locks-out-polaris-bios-modders
newbie
Activity: 9
Merit: 0
Hi, i just started mining with claymore. 5 RX480 red devils, and on of them keeps hashing low, i copy what im getting

ETH - Total Speed: 102.287 Mh/s, Total Shares: 139, Rejected: 0, Time: 01:35
ETH: GPU0 4.220 Mh/s, GPU1 24.774 Mh/s, GPU2 24.149 Mh/s, GPU3 24.665 Mh/s, GPU4 24.718 Mh/s

Can you guys help me and tell why getting that low hash rate

Thanks

I had same problem with simplemining Linux running Claymore.

I switched back to Win 10 no problems.

Im running Win 10. Crimson 16.6 for drivers...

That GPU seems locked in core clock and memory clock, dont know why.

Im ticking with the settings of my cards, two of them i get it cool working, but when i apply the same settings to the others two i get

WATCHDOG: GPU 3 hangs in OpenCL call, exit o WATCHDOG: GPU 1 hangs in OpenCL call, exit

Can someone give tips on how to solve this two issues...

I had the same issue with my 6x XFX RX480 rig and became more stable when switched back to 16.9.2 crimson driver. All cards are flashed with Boysie's 29MH Low power bios mod. Getting 173MH/s on 6x XFX RX480 8GB with 850W power usage from the wall.
newbie
Activity: 48
Merit: 0
Hi, i just started mining with claymore. 5 RX480 red devils, and on of them keeps hashing low, i copy what im getting

ETH - Total Speed: 102.287 Mh/s, Total Shares: 139, Rejected: 0, Time: 01:35
ETH: GPU0 4.220 Mh/s, GPU1 24.774 Mh/s, GPU2 24.149 Mh/s, GPU3 24.665 Mh/s, GPU4 24.718 Mh/s

Can you guys help me and tell why getting that low hash rate

Thanks

I had same problem with simplemining Linux running Claymore.

I switched back to Win 10 no problems.

Im running Win 10. Crimson 16.6 for drivers...

That GPU seems locked in core clock and memory clock, dont know why.

Im ticking with the settings of my cards, two of them i get it cool working, but when i apply the same settings to the others two i get

WATCHDOG: GPU 3 hangs in OpenCL call, exit o WATCHDOG: GPU 1 hangs in OpenCL call, exit

Can someone give tips on how to solve this two issues...
sr. member
Activity: 441
Merit: 252
Hi, i just started mining with claymore. 5 RX480 red devils, and on of them keeps hashing low, i copy what im getting

ETH - Total Speed: 102.287 Mh/s, Total Shares: 139, Rejected: 0, Time: 01:35
ETH: GPU0 4.220 Mh/s, GPU1 24.774 Mh/s, GPU2 24.149 Mh/s, GPU3 24.665 Mh/s, GPU4 24.718 Mh/s

Can you guys help me and tell why getting that low hash rate

Thanks

I had same problem with simplemining Linux running Claymore.

I switched back to Win 10 no problems.
newbie
Activity: 48
Merit: 0
Hi, i just started mining with claymore. 5 RX480 red devils, and on of them keeps hashing low, i copy what im getting

ETH - Total Speed: 102.287 Mh/s, Total Shares: 139, Rejected: 0, Time: 01:35
ETH: GPU0 4.220 Mh/s, GPU1 24.774 Mh/s, GPU2 24.149 Mh/s, GPU3 24.665 Mh/s, GPU4 24.718 Mh/s

Can you guys help me and tell why getting that low hash rate

Thanks
full member
Activity: 231
Merit: 100
hello guys,
this week i bought 6 gpus XFX 480 8GB 1288 Mhz. i flashed all to 2080Mhz VRAM and change timing setting from 1775 to 2000Mhz .
2 of this 6 cards freeze on grey or black screen after 2-5 minutes, sometimes shows up artefacts. i change windows, amd drivers and claymore versions and  the problem still exists.
after that i take one of this card to test on another computer, i put it on pci-e x16 slot to test. on benchmark there isnt a problem. only when i start mining.
after that i change bios switch to default, without deleting drivers, the memory clock change to 2000 Mhz and performance change to 22-23 Mhz in claymore. and again freeze on grey or black screen after a couple of minutes. all pc crash until restart. i found that two of this cards are version 1.5. another cards are 2.3.
any idea what is the problem and where i make a mistake.
the benchmark on gaming there isnt a problem. are these cards has defective memory.

my 2 cents.

I think it might be overheating issue due to overclock (1 or more cards can't handle your OC settings)

or

Your power supply is not enough. Tried/done down Core voltage of the cards with AB?
full member
Activity: 231
Merit: 100
hello,
 I am new to Ethereum mining and could use some help setting up my batch file please. I am mining Ethereum only  on Windows 10 with Claymore on a AMD RX480 8gb with the latest driver and I had it tuned for efficiency+performance and was getting 27mh and the rig ran very quietly. My problem is that I have added another exact same card and no matter what I try I am still getting 27 mh on the original card and only stock 24mh on the new one. Also the fans are really loud and the tweaks I have in the code aren't applying to the second card. I am using a 1000 W power supply. I have looked all over for sample code for multiple cards and haven't had any luck. Also the miner is only showing the temperate reading of one card.

Here is my original code for my batch file with one card:

...

The tweaked setting are not applying on the second card it is showing this in MSI Afterburner:
GPU1 Core Clock: 1050
GPU2 Core Clock: 1291
GPU1 Memory Clock: 2200
GPU2 Memory Clock: 2000

I can imagine that the voltages I would like aren't being applied as well.

Do I need to set up the second card as another worker and/or create a separate batch file for the second card?
I spent just about all day trying different code with the same results so any help is much appreciated.

Thank You,
Nodgeman


I think you might want to learn how to flash your cards' BIOS, i.e. set Memory Clock straps from 1500/1750 to 2000 MHz values. Check youtube, pretty simple.
I flashed Sapphire and Gigabyte and upped hashrate from 53 to ~58Mh and stable.

Plus check your AB if you set to change settings for both or just one card at the time. That little 'gpu' word and 'bricky icons'
newbie
Activity: 17
Merit: 0
hello guys,
this week i bought 6 gpus XFX 480 8GB 1288 Mhz. i flashed all to 2080Mhz VRAM and change timing setting from 1775 to 2000Mhz .
2 of this 6 cards freeze on grey or black screen after 2-5 minutes, sometimes shows up artefacts. i change windows, amd drivers and claymore versions and  the problem still exists.
after that i take one of this card to test on another computer, i put it on pci-e x16 slot to test. on benchmark there isnt a problem. only when i start mining.
after that i change bios switch to default, without deleting drivers, the memory clock change to 2000 Mhz and performance change to 22-23 Mhz in claymore. and again freeze on grey or black screen after a couple of minutes. all pc crash until restart. i found that two of this cards are version 1.5. another cards are 2.3.
any idea what is the problem and where i make a mistake.
the benchmark on gaming there isnt a problem. are these cards has defective memory.
hero member
Activity: 729
Merit: 513
The memory leak must have to do with PAS before I started to mine PAS I did not have the issue but at 13GB memory of usage when I have 16GB memory the miner kept mining but would not actually send out the hash data.  At that point I had to restart it. So probably in the PAS routine.

Glad to hear a new update will be released though soon.

Ask if someone has same issue, I don't see any memory leaks in ETH+Pascal mode.

I have 2 rigs mining ETH + PASC and have no issue with them... One of it has 400+ hours since it started mining, that's more than 2 weeks without restarting...
newbie
Activity: 4
Merit: 0
Hi. I have one issue with Claymore. He didn't work well with 2gb ram on matherboard, just shut down below creating dag file. And again and again that same, but when i put 4gb it work well and without any problams. Nicehash work fine with 2gb, so what i do wrong with Claymore miner or need some special config in BAT file for that?!? If some one know how fix it please tell me. Thank you.

Win 8.1
Claymore 7.4/8
sr. member
Activity: 441
Merit: 252
It appears that 8.0 has a severe memory leak.  The miner reached 13GB of memory usage. This is no small leak that is a major leak. When it got that heavy it stopped sending out hashing power even though it was mining the remote manager said it had no hash power.

This is a well-known issue. Within a few days of launch Claymore released a new 8.0 which fixed the memory leak.

Perhaps he should have called it 8.01 or something so people would know that it fixed a problem.

It was ZEC miner v12.2, not this miner. ETH v8.0 miner has no known memory leaks and I did not release any updates for it. Though in 1-2 days I will release new version with Pascal support for NVidia and some other improvements.

Claymore, I apologize for spreading misinformation.

I hadn't had enough coffee yet and got the two miners confused Smiley I deleted my original post so as not to confuse more people.
legendary
Activity: 1428
Merit: 1000
https://www.bitworks.io
The memory leak must have to do with PAS before I started to mine PAS I did not have the issue but at 13GB memory of usage when I have 16GB memory the miner kept mining but would not actually send out the hash data.  At that point I had to restart it. So probably in the PAS routine.

Glad to hear a new update will be released though soon.

Ask if someone has same issue, I don't see any memory leaks in ETH+Pascal mode.

Not seeing anything here however X windows can cause a memory leak that manifests like this, took me weeks to run it down months ago.. Some X configurations will attempt to buffer when you have X running on GPUs in some configurations, a separate console using another GPU, and it does exactly this... I found it circa 7.x and thought for sure Claymore had a leak so we sent some PMs back and forth but it turns out it was X.. I needed to disable some things to stop it from happening, don't have the specifics in front of me but I did write them down somewhere..
donator
Activity: 1610
Merit: 1325
Miners developer
The memory leak must have to do with PAS before I started to mine PAS I did not have the issue but at 13GB memory of usage when I have 16GB memory the miner kept mining but would not actually send out the hash data.  At that point I had to restart it. So probably in the PAS routine.

Glad to hear a new update will be released though soon.

Ask if someone has same issue, I don't see any memory leaks in ETH+Pascal mode.
sr. member
Activity: 322
Merit: 250
The memory leak must have to do with PAS before I started to mine PAS I did not have the issue but at 13GB memory of usage when I have 16GB memory the miner kept mining but would not actually send out the hash data.  At that point I had to restart it. So probably in the PAS routine.

Glad to hear a new update will be released though soon.
donator
Activity: 1610
Merit: 1325
Miners developer
It appears that 8.0 has a severe memory leak.  The miner reached 13GB of memory usage. This is no small leak that is a major leak. When it got that heavy it stopped sending out hashing power even though it was mining the remote manager said it had no hash power.

This is a well-known issue. Within a few days of launch Claymore released a new 8.0 which fixed the memory leak.

Perhaps he should have called it 8.01 or something so people would know that it fixed a problem.

It was ZEC miner v12.2, not this miner. ETH v8.0 miner has no known memory leaks and I did not release any updates for it. Though in 1-2 days I will release new version with Pascal support for NVidia and some other improvements.
newbie
Activity: 28
Merit: 0
What is the hash rate for Sapphire R9 Fury?

R9 Fury is much more profitable to mine the ZCash. It cannot use the 4096 cores properly when mining ETH.
Jump to: