Search content
Sort by
Showing 10 of 10 results by suona
Mining and latest client version works fine.
The only problem is markets/exchanges - as always for Primecoin... Is offline for deposits and trading at the moment... :/
https://imgur.com/6AL4jrl
The only problem is markets/exchanges - as always for Primecoin... Is offline for deposits and trading at the moment... :/
https://imgur.com/6AL4jrl
Unfortunately it is very difficult to exchange primecoin sometimes...
Most of exchangers don't support it, those few that support it sometimes may have weeks of very low activity for this coin.
https://i.imgur.com/RyKp2s3.png
https://i.ibb.co/MBpjGVX/xpm-exchange-problem.png
Most of exchangers don't support it, those few that support it sometimes may have weeks of very low activity for this coin.
https://i.imgur.com/RyKp2s3.png
https://i.ibb.co/MBpjGVX/xpm-exchange-problem.png
Have checked client version 10.5 with "asm" kernel type on RX570, CPD increase is about 15-17% against client version 10.3. Works stable so far. Driver version is 19.1.2.
Apparently he develops this project alone. It is quite difficult for a single developer to maintain such a complicated freeware and opensource project. Especially if person has the job and the family when free time for any hobby like that becomes a very rare and precious resource, and furthermore when 3-rd parties add their own problems to the project - like the recent unstable AMD drivers. Not to mention of attacks against the pools - reliable protection costs more than those pools ever earn.
So this is normal he releases updates so rarely.
Unlike many other projects that exist due to money income, this one seems to still exist due to enthusiasm of one person. This rather deserves thankfullness even if result isn't that good as was expected.
Finally nobody is forced to use it, there are many else alt-coins. Also it is opensource - anyone could take part in development, but no one else seems to offer anything better for xpm.
I think writing constructive messages about existing problems may help developer to fix them. But simply negative feedbacks might rather suppress his motivation to proceed working on it, and barely may help to fix the problems.
So this is normal he releases updates so rarely.
Unlike many other projects that exist due to money income, this one seems to still exist due to enthusiasm of one person. This rather deserves thankfullness even if result isn't that good as was expected.
Finally nobody is forced to use it, there are many else alt-coins. Also it is opensource - anyone could take part in development, but no one else seems to offer anything better for xpm.
I think writing constructive messages about existing problems may help developer to fix them. But simply negative feedbacks might rather suppress his motivation to proceed working on it, and barely may help to fix the problems.
@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.
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.
390 and 480 -> -0.03 (0.04) cpd 
Same decrease on R9 380 and R9 390. Driver version is 19.3.2.