Hi,
yes this bug is reported and I'm working on it. I will remove the linux version until a fix is available.
Sorry-
Happens in Windows version as well |
|
|
|
Forager 20.01 releasedhttps://github.com/yuzi-co/Forager/releasesChangelog: * Miner updates (too many to list) * ZergPool RandomX/SFX and Cryptonight support * Use CoinPaprika for WTM coin prices * Many new algos * Move SHA256 hashes to separate file * Fixes for miners and algos
|
|
|
|
Forager 19.07 releasedhttps://github.com/yuzi-co/Forager/releasesMiner updates: - NanoMiner 1.5.2 - XMRig AMD 2.14.5 - XMR-Stak 2.10.6 - TeamRed 0.5.6 - BMiner 15.7.6 - Ethminer 0.18 - CpuMinerOpt 3.9.6.1 - WildRigMulti 0.19 - GMiner 1.53 - NBMiner 24.2 - lolMiner 0.8.5 - SRBMiner 1.9.1 - CryptoDredge 0.20.2 - RHMiner 1.5.3 - KBMiner 1.3.11 - MiniZ 1.4o - TRex 0.12.1 - ClaymoreDual 14.7 Support new NiceHash pool Update algos
|
|
|
|
Hello!
With dual mining ETH+Pascal, the number of rejected shares for Pascal is about 50%. Can this be fixed someway?
Thanks!
Its a surprise that there are accepted shares, since Pascal coin changed their algo completely |
|
|
|
|
No problem, we can provide you with "filler" posts ))
|
|
|
|
@Claymore: Dual mining ETH + VBK is still not possible with AMD cards, right?
Hi, what about dual mining ETH + PASC? Anyone here mining that way? I try to ming ETH ( https://ethermine.org/) and PASC ( https://pasc.nanopool.org/help), but claymore get a lot of rejected/invalid/stale shares (don't remember exactly). Could anyone can send me correct mining config with these pools above or suggest other pool (PASC) to mine? Thanks. Pascal has a new, CPU only algo. Old algo is useless now |
|
|
|
It's possible in prerun launch a file.bat for every algoritm with setBaseClockOffset and setMemoryClockOffset ?
Currenty no, but i'll take a look at implementing something like that |
|
|
|
If they are compiled with MinGW, the performance will be lower. Cross-compile with GCC does a better job optimizing
This statement caught my attention. The binaries are cross-compiled with GCC in a mingw environment runing on Linux. What are you referring to that is better? Right, I meant that cross compile is faster than using Cygwin on Windows. Not MinGW... Mixed them up )) |
|
|
|
Forager 19.06 releasedhttps://github.com/yuzi-co/Forager/releasesChangelog: Miners: - NanoMiner 1.3.4 - CCMinerRFv2 1.0.2 - CryptoDredge 0.20.1 - CCMinerVerus (CPU) 3.5 - CpuMinerOpt 3.9.1.1 - SGMinerFancyIX 0.6 - GMiner 1.45 - WildRigMulti 0.17.3 - TTMiner 2.2.5 - XMRig 2.14.4 - zEnemy 2.0 - CCMinerDyn 3.0 - ClaymoreEth 14.6 - SRBMiner 1.8.9 - GrinPro 2.2 - CpuMinerMulti 1.3.6.3 (Rainforest2) - TRex 0.11 - RHMiner 1.5.2 - CryptoDredge 0.16.3 with algos missing from latest - NBMiner 23.2.1 Other: - Support miner definitions in ps1 format and combine different Cuda variants - Fix start on Win10 1903 - Update memory requirements for some miners - Update Readme files - Support share count for wrapper - Other minor fixes
|
|
|
|
* I'm consistently getting about 5% less hashrate for yescrypt than with older v3.8.8 for the exact same configuration. I didn't take more metrics but I think some other algos have slightly less performance as well.
If they are compiled with MinGW, the performance will be lower. Cross-compile with GCC does a better job optimizing If it's not the case, it might be something in the recent changes |
|
|
|
TPruvot has it, does it work better? I've already looked at the code. My first glance shows it's a completely new algo and can't benefit from any of the canned optimizations. To optimize it requires a detailed analysis of the code to look for opportunities to vectorize either serially, parallelly, or not at all. I expect the scalar code to be near optimum already. It's a huge task to do the whole algo at once. Not really interested at this time. Hashrate displayed by the miner, both thread and share, are artificially calculated based on the number of iterations over time. The pool calculates based on the number and difficulty of submitted valid shares. Perhaps there's a math error in the miners calculations. Tpruvot has the first version of the algo, but they released a tweaked one (RFv2). There is also a pull request with RFv2, but it has the same issue. Anyway, I get your point about not being interested )) |
|
|
|
Fee is 2%??? You must be joking  Could immediately put 5% or better than 20%. Then everyone would choose your option for sure. If no joke, I do not understand why to choose your option when there are other options where only 1% ask. Troll... Just a sample of algos on 1660ti Cuckaroo29 Gminer - 4.9h (2% fee) BMiner - 4.2 (2% fee) NBMiner - 4.15 (2% fee) Equihash192 GMiner - 24.6 (2%) MiniZ - 22.7 (2%) EWBF - 20.7 (2%) Equihash150 GMiner - 17.63 (2%) MiniZ - 17.31 (2%) BMiner - 16.6 (2%) Wonder which I should choose... |
|
|
|
cpuminer-opt v3.9.0 is released.https://github.com/JayDDee/cpuminer-opt/releases/tag/v3.9.0Added support for Windows CPU groups. (not available in precompiled binaries) Fixed BIP34 coinbase height. Prep work for AVX512. Added lyra2rev3 for the vertcoin algo change. Added yespower, yespowerr16 (Yenten) Added phi2 algo for LUX back to life after a year  Welcome back! |
|
|
|
v14.4 Beta:
- improved mining speed for Nvidia cards by about 1% (depends on card model). Note that dual mining for Nvidia cards suffers from this optimization, use old versions if you use dual mining on Nvidia cards.
- a bit reduced intensity of all Nvidia straps.
- added "-sintensity" option to adjust strap intensity for Nvidia cards, see Readme for details.
кoгдa для Linux бyдeт? Teмy читaли, вooбщe? Клeймop пиcaл, чтo нe бyдeт дeлaть для Линyкca, пoтoмy чтo oн в нём нe paзбиpaeтcя. Этo я cвoими cлoвaми вкpaтцe. и чтo oпять нa виндy пepexoдить c xaйвa нe peзoннo 120 кapт А в чем проблема? А если все работает, то переходить ради 1% на одном майнере? Тем более что Ethash далеко не самый выгодный алгоритм сейчас |
|
|
|
fair enough, thanks for reply. quoted for the next lazy person.
next lazy person will again be lazy check last posts )) |
|
|
|
v14... Only for win10x64? Or win7(have no compute mode) maybe work too ?
Yes it will work in Win7x64 too. But as you said, no compute mode, so you will see low hashrate. did you get paid off to keep it windows only?  but seriously, read his last posts, he explained why... |
|
|
|
Forager 19.05 releasedhttps://github.com/yuzi-co/Forager/releasesChangelog: Miners: - CCMinerRFv2 1.0.1 (Rainforest2) - TTMiner 2.2.3 - ClaymoreEth 14.0 - GMiner 1.42 - WilRigMulti 0.16 - SRBMiner 1.8.8 - CryptoDredge 0.19 - BMiner 15.5.3 - MiniZ 1.3n3 - NanoMiner 1.2.4 - TeamRed 0.4.5 - MultiMiner 1.2 (linux) - CCMinerVerus 3.4 - Improve NVIDIA support - Add last run speed and shares to Stats screen - Support setting powerlimits in Watts (NVIDIA with Afterburner Off only) - Additional fixes
|
|
|
|
So, without disabling secure boot no chances to run with straps, right? It's not good...
Do you really need secure boot on your rigs? I could sign the driver, then some people will use my miner as malware, as always, then some AV will mark it as virus, then the certificate would be revoked... No way. I didn't need SB on all my rigs. But on some of them I work and SB can't be disabled on them... That's why I ask... You can make separate exe-utility for installing driver and sign them. Miner can use this tool for installing/uninstalling driver and even if miner will marked as virus, driver installed by separate tool with sign will not revoked! Just think about it, please. I'm sure that it can solve many questions in future. And another one question: you made memory straps by yourself? Or you take it from somewhere? Can you share this straps for us, so we just flash it on our bioses. Those who can't use driver? P.S. Some time ago zawawa (he maked GGS miner) can apply memory straps in his miner without any drivers on the fly... So it's exist a way to do it so... Zawawa was using a driver - phymem.sys ( https://github.com/zawawawa/GatelessGateSharp/tree/v1.3/phymem) |
|
|
|
|
Show Posts
