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

In the Remote Monitor

Under RUNNING TIME what does the number inside the parenthesis mean?

Like

64:00 (1)

Hi Claymore,

Thanks for the great miner!

I have a number of rigs with 380x cards, one with a mix of 380 and 380x and a "new" one with one ASUS STRIX-RX480-O8G-GAMING and one ASUS DUAL-RX480-O4G. They all run Ubuntu 14.04.4, except for the new one that runs Ubuntu 16.04.1

The rigs with the 380x and the 380/380x cards run smoothly since day 1, but the "new" one has the following problems:
1. The two cards cannot work together. ethdcrminer64 just crashes at random intervals. The situation is even worse under Windows 10: the system just reboots... I don't even get a decent BSOD. My solution is to run (under Ubuntu) two instances of the miner, one for very card.
2. The hashing speed goes up and down. The RX480 with 4GB hashes between 15MH/s and 21.5MH/s and the RX480 with 8GB hashes between 17MH/s and 25MH/s
3. I get LOTS of system errors. By lots, I mean 100GB of kernel and syslog messages in a couple of hours. I've disabled syslog and set -dbg -1, but still... I'm pasting a few dmesg messages below

[  848.570829] amdgpu 0000:01:00.0: GPU fault detected: 147 0x05d88801
[  848.570830] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x081048BB
[  848.570831] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04088001
[  848.570832] VM fault (0x01, vmid 2) at page 135284923, read from 'TC6' (0x54433600) (136)
[  848.570894] amdgpu 0000:04:00.0: GPU fault detected: 147 0x05f88801
[  848.570895] amdgpu 0000:04:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x081048BF
[  848.570896] amdgpu 0000:04:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02088001
[  848.570898] VM fault (0x01, vmid 1) at page 135284927, read from 'TC6' (0x54433600) (136)
[  848.570932] amdgpu 0000:01:00.0: GPU fault detected: 147 0x05e80801
[  848.570933] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x081048BD
[  848.570934] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04008001
[  848.570935] VM fault (0x01, vmid 2) at page 135284925, read from 'TC0' (0x54433000) (
[  848.570946] amdgpu 0000:01:00.0: GPU fault detected: 147 0x05d04801
[  848.570947] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x081048BA
[  848.570948] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04048001
[  848.570949] VM fault (0x01, vmid 2) at page 135284922, read from 'TC4' (0x54433400) (72)

Any help on any of the problems will be greatly appreciated.

TIA,
Agis

Difficulty means share target? Pool sets it.


I copied History.txt from Windows machine to Linux and Linux changed its time for some reason to future. Have no idea why it happend since other files have correct timestamp and original History.txt has correct time. May be another Linux "feature". You have to wait a day until it work, or change time on your system, or disable time checking in "tar" somehow.


Yes, Windows 10 Anniversary + latest drivers wddm 2.1.


I'll try to reproduce it, PM me the complete log file.


Yes it must work in Linux+gpupro drivers. All features must work except fan management.

Which generation riser/cable?

I saw that with the narrow first generation ones. But haven't seen it with the wider ones with 3 capacitors.

Hi Claymore, I changed from V7.1 to 7.2 and used the new low intensity dag creation and it works great. I can overclock my undervolted 390's a bit more and it starts up ok!

But I have the same problem now with the program hanging with the "miner thread hanged, restarting" dialog box that requires clicking to proceed.

Edit: It doesn't happen every time there is a problem and the miner restarts, sometimes it restarts OK. OS is Windows 10, Eth/SC

The dialog box says...

"EthDcrMiner64.exe has stopped working" A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.   > Close program <

The last few lines in the log file were...

17:08:19:259   bc4   recv: 51
17:08:19:259   bc4   srv pck: 50
17:08:19:290   bc4   srv bs: 0
17:08:19:290   bc4   sent: 208
17:08:19:446   c2c   got 36 bytes
17:08:19:446   c2c   buf: {"id":4,"result":true,"error":null}

17:08:19:446   c2c   parse packet: 35
17:08:19:446   c2c    SC: Share accepted (390 ms)!

17:08:19:446   c2c   new buf size: 0

The temp monitor will work in linux right ? if it is overheat it will stop the gpu

@claymore

thanks for v7.2

---------------------

i have always a little problem, not with claymore maybe with psu !?
my rig have 6 gpu, 4 x RX470 and 2 x R9 Fury.

if i use 6 gpu with claymore, after 5 min my rig shutdown, reboot ...
before when i have try the first time, the rig shutdown immediatly when it load dag.

i have search and read, i have change my config with gpu-psu :
gpu 0 r9 alone
gpu 1 & 2 rx together
gpu 3 & 4 rx together
gpu 5 r9 alone

my psu is lepa p1700m platinium.

what i can do ?

ps : i run with 5 gpu with claymore and 1 with ethos, no problem it's stable.

Claymore my miner thread hangs frequently, and it wont restart. I mean when remote-connect to the machine and on the miner window press down arrow "miner thread hanged, restarting" message pops up, but untill I do so, the machine just stays in freeze mode for 4 - 6 hours causing me significant loss. I need to keep checking on machines almost regular. I have set the miner to restart every 60 minutes with -r 60 but nothing happens. I'm using Ver 7.1 of your miner on RX 470's, 16.9.2 drivers on Win 10.

Claymore, is there any workaround for gtx 1080 (372.90 / win 10) and not getting 5 Mhs ?

Single:
ETH=19
DCR=1750

Dual:
ETH=17
DCR=210

It is better to get something one

Hey Bro,
Depending upon your cards you will have to find the best setting of dcri flag. Start low (20 or something like that ) and use "+" key to slowly increase until the ether mining starts to fall more than 5%. If you want keep an eye on power consumption. In certain situations dual mining may not be profitable more as your power consumption increases / AC power needed to keep mining cool increases / more downtime because of throttling after some time of mining etc. So just find your Efficiency (max) on the curve and then use that setting thereafter.

Tried different settings, double mining not profitable.
The main ethereum power strongly falls. On SIA twice

Is there any way to specify difficulty in dual mining? like lbry static difficulty setting? (sgminer code /sgminer -a lbry -o stratum+tcp://lbry.suprnova.cc:6256 -u suprnova.1 -p d=16 -I 21 -g 4 -w 256  allows d= " " setting for that. It will be great to add it in dual miner too. )
Thank you

Riser or.. power cable.. I have GPU error very often and.. finally I realized that plug was slightly melted...

Like in previous version... What does it mean?

INCREASE DECRED INTENSITY--

You can increase the intensity for your secondary coin with the "dcri" flag.  I have mine set at "dcri 75", more than twice the default value of "dcri 30".  This will more than double your hash rate for Decred (DCR), and have little effect on your Ethereum (ETH) hash rate.  The cards from nVidia are very good for this, my 980ti gets a hash rate over 500MH/s on SiaCoin (SC).       --scryptr

Speed shall decrease twice?
Read that DUAL mining occurs without loss of power

Is that faster than V4.4 for the R9 390 or the 280x?

It is something related to google drive. Logout from google account and try to download, it's already there.

Thanks Claymore !

Is it going to be posted on google drive soon ? I don't see it yet.

1. I did not change anything in speed. If you think that v7.0 works faster - use it. Because I cannot fix issue that does not exist.
2. You can only disable entire monitoring with "-tt 0".
3. Try all "-etha" values and see hashrates, then select the best for your card. It will not take much time. "-etha" is applied for AMD cards only.
4. In solo mode miner doesn't use stratum. So miner sometimes connects to geth and asks for current job. Default value is good for local network. Original ethminer has same option called "--farm-recheck".


No. When I do it, I will mention it in "History.txt".