Forager 18.07.1 releasedhttps://github.com/yuzi-co/Forager/releasesChangelog: - Update miners: - JCEMiner 0.31a - Fix wrapper for multi-GPU with mkxMiner - CoolMiner 1.5 - Exavator 1.5.8a - SRBMiner 1.6.4 - CCMiner zEnemy 1.12a - ClaymoreDual 11.9 - CPU Xmrig 2.6.4 - AMD Xmrig 2.7.2b - Disable Delos by default (Reports of possible trojan? Enable at your own risk) - Cpuminer YesPower - Fix pool speed on BlazePool - Update FairPool, CryptoKnight, CoinCalc, WhatToMine pools - Rework error handling, Retry on network errors - Fix PercentToSwitch - Cancel current miner if Worker count is below MinWorkers parameter - Rename Cryptonight algos to shorter form (Cn, CnLite, etc.). You can rename benchmark files to skip re-benchmarking - Small fixes
|
|
|
|
read first page. 32 bit is not supported Requirements:
1. A x86_64 architecture CPU with a minimum of SSE2 support. This includes Intel Core2 and newer and AMD equivalents. In order to take advantage of AES_NI optimizations a CPU with AES_NI is required. This includes Intel Westbridge and newer and AMD equivalents. Further optimizations are available on some algos for CPUs with AVX and AVX2, Sandybridge and Haswell respectively. Older CPUs are supported by cpuminer-multi by TPruvot but at reduced performance. 2. 64 bit Linux OS. Ubuntu and Fedora based distributions, including Mint and Centos are known to work and have all dependencies in their repositories. Others may work but may require more effort. 64 bit Windows OS is supported using the pre-compiled binaries package or may be compiled with mingw_w64 and msys. Legacy version 3.5.9.1 May provide better performance on some algos with older CPUs that don't have AES NI. The legacy version is required to mine hodl with a non-AES CPU. Most users should use the master version. https://github.com/JayDDee/cpuminer-opt/releases/tag/v3.5.9.1 |
|
|
|
|
18.4.1 were buggy, so just stay away
Best would be 18.3.4 and 18.6.1
Different CN algos act differently on those, but the difference is very slight, so only if you are min/maxing a rig for specific algo - it's worth testing, otherwise just pick any of them
Blockchain are outdated and pointless, unless you use a specific miner that has kernel compiled for it, like MkxMiner for lyra2v2, but even then, lyclMiner is significantly better.
|
|
|
|
|
No rejects on Nicehash and Zergpool
Still getting rejects on Zpool and BlockMasters
|
|
|
|
Claymore dual 11.9 released... fixes keccak rejects
updated |
|
|
|
Yes, it's a fork of Megaminer, (which is a fork of MultiPoolMiner in itself) Why would I need to change file structure if it works for me? The parts that don't work for me - I have rewritten (just see my commit count on git (950+ commits, vs 350+ of tutulino)  ) Plus I have added new functionality, better logic, new miners, new pools and update regularly |
|
|
|
"The response content cannot be parsed because the Internet Explorer engine is not available, or Internet Explorer's first-launch configuration is not complete. Specify the UseBasicParsing parameter and try again."
Run IE and complete configuration steps. @Quake4 You can add "-UseBasicParsing" to Invoke-WebRequest to prevent this issue |
|
|
|
Benchmarking with mkxminer gives wrong localspeeds, it summorize for only one card and not multiple on my AMD rig.
Known problem?
I think regression in wrapper code from adding lyclMiner. I will check it tomorrow. In any case, lyclMiner should give significantly better hashrate, so if it works for you, mkxMiner is less important ) Alright, i will give this miner a shot. there are so many out nowdays ive started to loose track. fixed mkxMiner for multi-gpu in last commit |
|
|
|
You seem a good guy working on your software so, I decided to give Forager a try:
I have some rigs, always mixed AMD&Nvidia mining in the past Neoscrypt with AMD during the day, CN during the night , and using Nemos miner for NVidia
Download latest release 1.8
Script is saying that there is a new version 1.7z available... not sure if its updated( or olddated in this case)
automaticly or not
I selected ahashpool&zergpool cutting the algos in half, exclusing all Asic related
Sw is saying 15 miner 100 combination.
but
MKXminer can't be downloaded ( I have a 100 MB Adsl)strange..
lyclMiner ? I haven't seen any batch ,json ps1 file related to it so, may be its the
it have taken 2 hour to download and haven't finished yet.
There is a quick windows popup from time to time but I think we are stuck in one of the CCminer releases Tpruvot I think. I suspect something on Gitub ?
Isn't much easier to at least download one AMD and one Nvidia sw and start benchmarking ?
meanwhile downloading other?
I will keep tryng for another hour, then I will stop and I will try again on monday
latest is 18.07 (yes, i changed version numbering) If you have problems downloading specific miner, get the url from the miner json file, download it manually and put in Forager/Downloads folder |
|
|
|
Benchmarking with mkxminer gives wrong localspeeds, it summorize for only one card and not multiple on my AMD rig.
Known problem?
I think regression in wrapper code from adding lyclMiner. I will check it tomorrow. In any case, lyclMiner should give significantly better hashrate, so if it works for you, mkxMiner is less important ) |
|
|
|
thx for the kill process update. Does anyone here actually use this with NVidia miners? I'm getting crashes and hard resets all over the place. My list of excluded miners is growing (every time a miner crashes the system I remove it): ExcludeMiners_NVIDIA = N-hsrminer_hsr*,N-NsCudaMiner*,N-CryptoDredge*,N-CcminerSTS*,N-CcminerDumax*,N-Prospector*,N-CcminerEnemy*,N-SuprMinerSP*
There are definitely NVIDIA users. I cannot test NVIDIA miners myself due to lack of hardware, but I know it works for many users. If a miner fails to run on your system, in most cases its a driver/overclock issues or hardware incompatibility. Try running the problematic miners yourself to verify the issue. The downloaded miners are in the "Bin" folder If they fail when you run them yourself, there isn't much I can help. You can try requesting help in the relevant miner topic. It's also possible that the parameters I use to start the miners are incorrect or incomplete. You can check the exact parameters used to launch the miners in the log file and test them. If you find a configuration error, I will gladly fix it. |
|
|
|
hi, with latest code the endless error loop still occurs: Stop-Process : Cannot stop process "Idle (0)" because of the following error: Access is denied
At C:\miner\Forager\Include.ps1:128 char:17
+ Stop-Process -InputObject $Process -Force
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : CloseError: (System.Diagnostics.Process (Idle):Process) [Stop-Process], ProcessCommandException
+ FullyQualifiedErrorId : CouldNotStopProcess,Microsoft.PowerShell.Commands.StopProcessCommand
Stop-Process : Cannot stop process "Idle (0)" because of the following error: Access is denied
last useful entries in logfile are 11:03:20.88 Info N-CcminerEnemy-1.12/X17/X17 with Power Limit 0 (id 34-0) for group NVIDIA is the best combination for device group, last was N-SuprMinerSP-4.0a/X16r/X16r with Power Limit 0 (id 84-0) for group NVIDIA
11:03:20.88 Info Killing in 0 sec. N-SuprMinerSP-4.0a/X16r/X16r with Power Limit 0 (id 84-0) for group NVIDIA with system process id 0
this happens after some time during the benchmarking which really takes forever and repeats on each restart since there are so many miners that fail -- most fail right at startup (close immedately after being started), and the script usually catches the failing miner -- but before the endless error loop happens it apparently doesn't detect that the miner process is not running, just sits there with 0% load until the interval ends and then goes into the loop described above. I will fix the "Cannot stop process" error Full log would be useful to identify why do we even get to such state, can you please post it as well? update:Changed process launch and process kill logic to better handle errors. Available in last git repo commit |
|
|
|
|
api reports wrong servers for bitcoin-gold
host_list: "hub.miningpoolhub.com;us-east.hub.miningpoolhub.com;asia.hub.miningpoolhub.com;europe.hub.miningpoolhub.com",
instead of:
host_list: "us-east.equihash-hub.miningpoolhub.com;asia.equihash-hub.miningpoolhub.com;europe.equihash-hub.miningpoolhub.com",
|
|
|
|
Forager 18.07 releasedhttps://github.com/yuzi-co/Forager/releasesChangelog: - Updated and new miners: - CoolMiner 1.4 - CastXMR 1.3.0 - JCEMiner 0.29e - Prospector 0.1 fix api - BMiner 9.0 - SRBMiner 1.6.2 - lyclMiner 0.1.5 - CCminerOurMiner 1.0 - CCminerTpuvot 2.3.0 - CCminerDumax 0.9.3 - Excavator 1.5.6a - CCminerEnemy 1.12 - EWBF 0.3 - lolMiner144 0.38 - CryptoDredge 0.6.0 - Update pools: - FairPool, SuprNova, PhiPhi, NLpool, MPH - Support Wild Keccak algo (not recommended to mine in auto mode due to long init) - Display Runtime and current coins in window title - Allow excluding specific Algos/Coins for pools - Better support for new CryptoNight Algos - Support for new Equihash algos - Use nvidia-smi to get Nvidia power usage even when Afterburner enabled (more accurate information) - Fix some runtime errors
|
|
|
|
It forces me to redownload vcredistx86 for every benchmark and it makes it annoying to benchmark because i have to sit there the whole time and wait for it to ask me to redownload/repair vcredist86, then press "no" to skipit so I can continue benchmarking. Please fix
Solved in last commits |
|
|
|
hi, Just tried the latest Forager code (cloned from github), as MegaMiner seems abandoned.. there are, however, some issues. There are a couple error messages repeated before every new interval: Cannot index into a null array.
At C:\miner\Forager\Include.ps1:425 char:17
+ ... $PnpDeviceProperties = ($PnpDevices | Where-Object {$Vend ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : NullArray
Doesn't seem to cause any problems, though. However on two out of three systems I tested, one hard crashes, and one goes into an endless error loop, something like "cannot kill process "IDLE". Unfortunately the error is not written into the log, have to catch and copy it again. This is all on Nvidia rigs where MegaMiner has been running fine and stable for many months. I'll take a look. I believe the code throwing the error is redundant now Fixed in latest commit And I hope you can provide something so I can check the issue you are experiencing. Send me the logs, even if they don't show the errors, maybe I'll discover something since I know how it should work  Is there a way to disable specific algos for specific pools.
reason is that when dual mining with claymore, zpool and ahash will show hi reject rates (50%) for keccak, but nicehash will be ok.
thanks.
I will add such option, I also noticed this behavior Added now in latest commit |
|
|
|
hi, Just tried the latest Forager code (cloned from github), as MegaMiner seems abandoned.. there are, however, some issues. There are a couple error messages repeated before every new interval: Cannot index into a null array.
At C:\miner\Forager\Include.ps1:425 char:17
+ ... $PnpDeviceProperties = ($PnpDevices | Where-Object {$Vend ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : NullArray
Doesn't seem to cause any problems, though. However on two out of three systems I tested, one hard crashes, and one goes into an endless error loop, something like "cannot kill process "IDLE". Unfortunately the error is not written into the log, have to catch and copy it again. This is all on Nvidia rigs where MegaMiner has been running fine and stable for many months. I'll take a look. I believe the code throwing the error is redundant now And I hope you can provide something so I can check the issue you are experiencing. Send me the logs, even if they don't show the errors, maybe I'll discover something since I know how it should work Is there a way to disable specific algos for specific pools.
reason is that when dual mining with claymore, zpool and ahash will show hi reject rates (50%) for keccak, but nicehash will be ok.
thanks.
I will add such option, I also noticed this behavior |
|
|
|
|
Show Posts
