Topic: Open Source XPM (Primecoin) GPU Miner & Pool xpmforall.org - page 8. (Read 109866 times)

@eXtremal.ik71, let's have another scam? As with bitcoin prime. And that is boring already. 

what is this shit ..... 2882 confirmations


Pending ([163 of 2880)   XPM   90.52027785

2019-06-08 08:53:19

Address: AMePdnePJaCDMjZYvBwm1GL8NF3rH
Txid: dbecf6fe93bcfa2090ab41b4610fb58ed29401cd21dcc79fc3865770b4ad
https://c.radikal.ru/c07/1906/0d/36145e9c4246.png][url=https://radikal.ru]https://c.radikal.ru/c07/1906/0d/36145e9c4246.png[/url]

Checked xpmclient with AMD driver version 19.5.2 - no such problems with WattMan, everything works stable.

@eXtremal.ik71

Is there any way to completely disable any interaction of xpmclient with AMD WattMan? As we see, even if value of "powertune" parameter is set to "-1", it still proceeds interaction with WattMan setting powerlimit value to -1%, instead of changing nothing (as mentioned in comment, value "-1 means don't change", that is correct for else parameters of this section, but not for "powertune" as we have seen).

Previously, with older AMD drivers, this was not a problem.
But now the fact is that recent AMD drivers have a lot of new problems, on some PCs interaction of 3-rd party software with WattMan causes improper functioning of the driver that eventually ends up with driver crash, and in some cases - OS crash.

If PC is used for running xpmclient solely, then no any issues occur (though the problem is there, and we can see this if to run AMD control panel and open WattMan tab - driver will get crashed, and in about 3 of 5 cases OS will also get crashed several seconds later).
But in case if PC is also being used for another tasks, this becomes a problem. Attempt to launch any another software that utilizes GPU, especially simultaneously with xpmclient being running, often ends up with driver or OS crash.

On those PCs where we down-graded AMD drivers to versions of 2018 this problem disappeared. But older drivers have lack of some options and have another common issues, so users prefer to use recent drivers versions.

There is also another interesting fact - that problem with driver remains until OS restart even if xpmclient application has been already closed. This indicates that interaction of xpmclient with WattMan causes some sort of corruption to driver that remains until OS restart and causes improper functioning of the driver itself and of another software that utilizes GPU.

If xpmclient was not launched after OS restart then no any issues with driver or with any software occur.

So i'd suggest for the new xpmclient build to add an option that would allow to control whether interaction with WattMan is enabled or is completely disabled.


These issues were confirmed to occur with driver version v19.5.1.
I'm gonna check this with v19.5.2 as well next days, and will add one more comment for that.

All is well. Continue on.   

telegramm: xpm_bot

Hello!!!
This is a monitor for XPM miners.
Only for the pool 'http://coinsforall.io.'

It looks like memory overclocked too much.

Not possible without rebuild, I'll add config parameter for logging in next version.
Now have a problem with high orphan rate, calculator assume that pool not have orphans at all.

@eXtremal.ik71

is this good or not?

here you can download 10.2.2 version https://drive.google.com/file/d/1QjJkRWHxxOMR1-_RJNV6EaVdH08nzioW/view?usp=sharing
it contains linux and win version.

Hello ALL.
Can it possible to disable the write logs into file at v10.3?
I am running miner for USB-drive and want to minimize writes at drive for avoid it come dead soon.
Any ideas are welcome. Thanks for advice.

Good day, for all
I have a problem, and I could not find the client version 10.2.2 (xpmclient) for linux on the net. The reason for the numerous searches is that judging by the messages on the forum in the corresponding branch, 10.3 has a less stable hashrate than 10.2. The site has 10.2, but it does not contain a linux binaries. Or is the xpmclient file in the archive the client version 10.2 for linux?
I ask you to give a link to download exactly 10.2 for linux (amd64), if it does not make it difficult ...
Best regards, and sorry for my bad english...

Sorry. I'm so stupid. two days f$$k with vega, but one check in config "amd" and "amd vega" i have missed...

Can anyone help with vega config? Gpu crashes at once miner recieve work. I have tried Win7x64 with drivers 18.5.1,18.6.1,18.11.2, miners 10.2.2, 10.3. Then I try on win10x64(18.6.1 and 18.5.1 install failed every time, 18.11.2 install succesful) by this guide https://bytwork.com/articles/vega-mayning-monero. Disable "EnableUlps" and CrossfireAutolink, try Overdriventtool settings(and try low clocks with hi voltage), try with monitor on iGPU. And have no changed - crash on recieve work. wtf with vega? rx480(580), r9 290, gtx10xx is just works, vega not...

Later I will power +25~30%
The daily income is the same as the calculator result.

But the 10.3 version of the GPU often digs half of the crash, the probability is quite high.
Even the mining window closed for no reason.

In version 10.2.2, such overclocking parameters are very stable, but become unstable at 10.3, and even the core 1150 / memory 2000 collapses.

Ultimately supported by version 10.3

# GPU crash handling
# Enter OS terminal command here
# for example:
#   onCrash = "shutdown -r 1"
onCrash = "taskkill /f /im xpmclient.exe";

Automatically forced to close the mining software when the GPU crashes.

Then with the batch file
:1
TIMEOUT 10
tasklist | find /i "xpmclient.exe"  || echo %date% %time% XPM START >> log.txt && start xpmclient
goto 1

Monitor mining software for execution and monitor every 10 seconds.

If you do not execute, you can automatically restart the mining software.

The last current parameter is

platform = "amd";
cpuload = "1";
target = "auto";
sieveSize = "420";
weaveDepth = "40960";
width = "auto";
windowSize = "8192";
multiplierLimits = ["25", "31", "34"];

The parameters of multiplierLimits = ["25", "31", "34"];
The test result is more than the calculator.

What is the benefit to the pool owner? 

Due to the fact that for several days the entire crypto market has been growing, the profitability of cryptocurrency mining has been increasing with each passing hour. It is very nice to watch! I hope that the mining industry will come to life!

But now it is not a difficult problem, it is the difference between the actual number of mining and the result calculated by the calculator.

looks like difficulty has gone back up
http://xpm.muuttuja.org/charts/

Hello, may I have someone encountered this problem?

GPU has RX570, a total of 9
My computing power has 3.13 CPD

In theory, the final test difficulty is 11.30, and there will be 16 XPM in one day.

But when I actually tested for an hour, it only increased by 0.42 XPM, which is equivalent to about 10 XPM per day, which is very different from the result of the calculator.

It is the same whether  use version 10.2.2 or 10.3.
Whether the driver version is the latest 19.3.1 or the mining driver is the same
My parameters are set as follows

platform = "amd";
cpuload = "1";
target = "auto";
sieveSize = "420";
weaveDepth = "40960";
width = "auto";
windowSize = "8192";
multiplierLimits = ["24", "31", "35"];


Overclocking parameters are the same as Core 1300 / Memory 1750, or Core 1150 / Memory 2000

The average daily is lower than the computer 10~14 XPM
But it started to decrease after February 24~ there are 24 XPM in one day.

I have been digging for half a year, but never less than the calculator is so big

64 bit, ofcourse.