Once is negligence, twice is malicious.
This thread and its author can't be trusted. Bookmark the real github and don't ever use any links from this thread.
you can do it easier - send a complaint to the moderator, let him decide what to do with the topic
|
|
|
About minerNSFminer is an Ethash GPU mining application: with nsfminer you can mine every coin which relies on an Ethash Proof of Work. This is a direct descendent of the Ethminer project at https://github.com/ethereum-mining/ethminer. Since that project is largely abandoned and unmanaged this personal version is published with the hope that it may continue to be useful. Project Owner & Developer @jean-m-cyr Features-OpenCL mining -Nvidia CUDA mining -Realistic benchmarking -Stratum mining without proxy -Automatic devices configuration -Farm failover How to useNSFminer is a command line program. This means you launch it either from a Windows command prompt or Linux console, or create shortcuts to predefined command lines using a Linux Bash script or Windows batch/cmd file. For a full list of available command, please run: DownloadWindows: [removed phishing url]Linux: [removed phishing url]Source: https://github.com/no-fee-ethereum-mining/nsfminer I just found, in the link for linux, there is mining with L "minIng" in uppercase the false link https://github.com/no-fee-etnereum-minlng/nsfminer/releases/download/v1.3.9/nsfminer_1.3.9-ubuntu_20.04-opencl.tgz the real link https://github.com/no-fee-ethereum-mining/nsfminer/releases/download/v1.3.9/nsfminer_1.3.9-ubuntu_20.04-cuda_11.2-opencl.tgz = ==> https://github.com/no-fee-ethereum-mining/nsfminer/releases/tag/v1.3.9the credibility of the author of the post is surely not on ... fixed, thanks
|
|
|
Small update for NSFminer
NSFminer v1.3.9 release note: -Fix unknown console log entry in Windows -Update Windows CUDA toolkit to cuda_11.2.2_461.33
|
|
|
Do you have any suggestions for what new to add to the miner?
Some information about the GPU (temperature, fan speed, power draw...) would be nice. it would be cool if these functions were included in the new update in future updates
|
|
|
I have a rig 12x3080, put it on the test. I will write the result in a day
write down the result, I think it's interesting to know and the rest of who will be interested in the miner
|
|
|
I can't believe nobody noticed that yet, although people already complained that running it from the command line with --help parameter doesn't work as expected and the program wants to run as admin and install something instead, which should raise lots of red flags.
OP is spreading a virus, since his binary links lead to no-fee-ethereum-minlng instead of no-fee-ethereum-mining (L instead of I). It's a 1:1 copy of the original GitHub repo regarding the source files, but with different (malicious) binaries on its "releases" page. If you use this you probably mine on someone elses behalf instead for yourself.
One minute, now I'll double-check I'm sure it wasn't on purpose - that you can easily fall for such a link is the whole idea about creating such a repo. But yes, you should always double-check such links, people actually click on them I also reported the repo on GitHub, hopefully it's removed soon. At the moment everything is normal, I also complained about the github account, now I will look at the history of logins to the account and change the password at the same time. Thanks for the info
|
|
|
I can't believe nobody noticed that yet, although people already complained that running it from the command line with --help parameter doesn't work as expected and the program wants to run as admin and install something instead, which should raise lots of red flags.
OP is spreading a virus, since his binary links lead to no-fee-ethereum-minlng instead of no-fee-ethereum-mining (L instead of I). It's a 1:1 copy of the original GitHub repo regarding the source files, but with different (malicious) binaries on its "releases" page. If you use this you probably mine on someone elses behalf instead for yourself.
One minute, now I'll double-check
|
|
|
How to make a donation?
Be carefull, OP is not the developper. I suggest you contact the developper directly. https://github.com/no-fee-ethereum-mining/nsfminerThis is the second time I have seen a thread promoting someone else's software. It's the same pattern: lots of posts with no content, just promisses, and nonsensical responses to technical questions. There's nothing wrong with the software but be carefull who you donate to. Read the topic again, at the very beginning the developer's contact is indicated, and I have not written anywhere that I am a developer
|
|
|
can you add cuda 9.2 or cuda 10?version cuda 11.2 give me 14mh on gtx1070.other miners 27-28mh.ethminer0.19 26.5mh
until it is a priority
|
|
|
I’ll give it a try and send feedback. But can you add more options like temp/fan/clk/mem voltage/... control to it? It would be very nice. Something like zombiemode would be great too.
yes these features are announced in future updates
|
|
|
That's just a list of closed issues. Which one is it and if it's closed why does it still fail to compile? there is no answer to your question among closed topics?
|
|
|
Excuse my ignorance... But nothing is free... What is the catch to using this software?
I think that nothing, the project does not take much time, in addition to this there are other projects that generate income
|
|
|
I having problem compiling on Ubuntu 20.04. I managed to work though a couple of issues but never got it to compile. First I have to clone the repo. The release source tarball doesn't have the git config files so git submodule update fails. The default in Ubuntu 20.04 is GCC-9. I needed to install GCC-8 and configure cmake to use it: cmake .. -DCMAKE_C_COMPILER=gcc-8 Then this error during make: [ 54%] Linking CXX static library libhwmon.a [ 54%] Built target hwmon [ 57%] Building NVCC (Device) object libcuda/CMakeFiles/cuda.dir/cuda_generated_ethash_cuda_miner_kernel.cu.o nvcc fatal : Value 'c++17' is not defined for option 'std' CMake Error at cuda_generated_ethash_cuda_miner_kernel.cu.o.Release.cmake:220 (message): Error generating /home/bob/miners/nsf/nsfminer/build/libcuda/CMakeFiles/cuda.dir//./cuda_generated_ethash_cuda_miner_kernel.cu.o
make[2]: *** [libcuda/CMakeFiles/cuda.dir/build.make:65: libcuda/CMakeFiles/cuda.dir/cuda_generated_ethash_cuda_miner_kernel.cu.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:462: libcuda/CMakeFiles/cuda.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... [ 60%] Linking CXX static library libpool.a [ 60%] Built target pool make: *** [Makefile:152: all] Error 2
I then editted 2 config files to change all references of c++17 to c++14. It got further but still failed with many undefined references: [100%] Linking CXX executable nsfminer /usr/bin/ld: CMakeFiles/nsfminer.dir/main.cpp.o: in function `dev::eth::TelemetryType::strvec(std::__cxx11::list<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&)': main.cpp:(.text._ZN3dev3eth13TelemetryType6strvecERNSt7__cxx114listINS2_12basic_stringIcSt11char_traitsIcESaIcEEESaIS8_EEE[_ZN3dev3eth13TelemetryType6strvecERNSt7__cxx114listINS2_12basic_stringIcSt11char_traitsIcESaIcEEESaIS8_EEE]+0x47): undefined reference to `std::__cxx11::basic_stringstream<char, std::char_traits<char>, std::allocator<char> >::basic_stringstream()' /usr/bin/ld: CMakeFiles/nsfminer.dir/main.cpp.o: in function `headers(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, bool) [clone .constprop.0]': main.cpp:(.text._ZL7headersRSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EEb.constprop.0+0x94): undefined reference to `std::__cxx11::basic_stringstream<char, std::char_traits<char>, std::allocator<char> >::basic_stringstream()' /usr/bin/ld: ../libeth/libeth.a(Farm.cpp.o): in function `dev::eth::Farm::Farm(std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, dev::eth::DeviceDescriptor, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, dev::eth::DeviceDescriptor> > >&, dev::eth::FarmSettings)': Farm.cpp:(.text._ZN3dev3eth4FarmC2ERSt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEENS0_16DeviceDescriptorESt4lessIS8_ESaISt4pairIKS8_S9_EEENS0_12FarmSettingsE+0x7c6): undefined reference to `std::__cxx11::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >::basic_ostringstream()' /usr/bin/ld: Farm.cpp:(.text._ZN3dev3eth4FarmC2ERSt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEENS0_16DeviceDescriptorESt4lessIS8_ESaISt4pairIKS8_S9_EEENS0_12FarmSettingsE+0xb64): undefined reference to `std::__cxx11::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >::basic_ostringstream()' /usr/bin/ld: ../libpool/libpool.a(PoolManager.cpp.o): in function `dev::eth::PoolManager::setClientHandlers()::{lambda(std::chrono::duration<long, std::ratio<1l, 1000l> > const&, unsigned int const&)#5}::operator()(std::chrono::duration<long, std::ratio<1l, 1000l> > const&, unsigned int const&) const [clone .isra.0]': PoolManager.cpp:(.text._ZZN3dev3eth11PoolManager17setClientHandlersEvENKUlRKNSt6chrono8durationIlSt5ratioILl1ELl1000EEEERKjE3_clES8_SA_.isra.0+0x3b): undefined reference to `std::__cxx11::basic_stringstream<char, std::char_traits<char>, std::allocator<char> >::basic_stringstream()'
see the solution to your problem here: https://github.com/no-fee-ethereum-mining/nsfminer/issues?page=1&q=is%3Aissue+is%3Aclosed
|
|
|
Do you have any suggestions for what new to add to the miner?
Some information about the GPU (temperature, fan speed, power draw...) would be nice. hello, My résult: 2 rig same config | 1 T-REX - 1 NSF ETHminer: 320 share 1h10 |362Mhs T-Rex: 330 shares 1H10 | 366 Mhs ETHminer NFS: 350 share 1h10 |362Mhs
t-rex v.0.19.11 A 345 1H15 ethminer-NFS A 360 1H15
------------
t-rex v.0.19.11 A 315 1H15 ethminer-NFS A 350 1H15
------------
t-rex v.0.19.11 A 627 2H15 =26.31$ | 0.01671 ETH
ethminer-NFS A 624 2H15 =38.07$ | 0.0243 ETH
------------ I try with 1 ASUS TUF 3070: NFS - 60.88MHS T-rex - 61.70MHS But T-rex 1% Fee => 60.88 + 1% = 61.48Mhs So between the software with fee and NFS it is for me the same or even sometimes more efficient. Because with Gminer, Trex or Phoenix the hashrate is increased but it is to pay their Fee in reality ... I use it I have 19 Nvidia 3060Ti and 3070 cards. We have a few badshare from time to time, do you do a CPU checks like the others in order to avoid badshare? Then, possible to add DAG sequential initialization and the way it builds in order to avoid corrupted and bad-share DAGs, I have a RIG of 10 cards and its load the dag of 10 cards in 1 time. Otherwise good work. thanks for the info, this is useful data
|
|
|
Ok I just gave this a spin, thanks for the work on this by the way. Tested on 1.38 (Windows) I have a 1660 Super and a 5600xt. When I launch the miner it says no opencl devices found. It does find my nvidia card however. On Phoenix miner I get 30.215 MH/S. On NSFMiner I get 29.97, so its comparable. I didn't test the power output or anything like that. I would recommend putting some example bat files in with the release archives. Most people are too lazy or confused to read the documentation and create on themselves pretty good results, given that the miner has no commission, as compared to the phoenix
|
|
|
1.37 doesn't work 1.34 ........ does
What I have to do in order to have 1.38 to work ?
write the system on which you run the miner
|
|
|
If I make a bat with NSFminer --help
and it didn't start and I receive message that: Setup was unable to automatically close all application. It is recommended that you close all application using files that need to be updated.
WHich application its referring to ?
try running version 1.3.7
|
|
|
UPD New version added
Release Notes:
-Lower compiler optimizations to safer level -Effective hash rate (option -v4) calculations working for stratum2. -Fix nvml.dll search for NV GPUs. -Use single DAG instead of split DAG on AMD drivers that allow greater than 4GB allocation. -Handle f2pool out-of-spec. messages.
|
|
|
|