Hey joblo, the past few days the Windows Defender antivirus started to flag your binaries. I am not sure if you're aware but that hasn't happened before. Just though I'd let you know.
--ypsi
Thanks for the heads up. There seems to be a recent increase in miners being flagged. |
|
|
|
|
Seems like a problem with PCIe2 or PCIe3. Could be config, check the BIOS for PCIe settings. Otherwise it might be a bad slot.
Test the slots seperately.
|
|
|
|
I am having trouble compiling it on digitalocean cloudhosting. I am using the Ubuntu 14.04 drop. Here is my config.log output. https://pastebin.com/z1Jh7mRY  I am not an experienced compiler, so I have no clue what is wrong. I have installed dependencies. $ sudo apt-get install g++ libcurl4-openssl-dev libncurses5-dev pkg-config automake yasm git and done ./autogen.sh Try following the instructions in RELEASE_NOTES. |
|
|
|
I have a 1950X CPU and tested mining monero XMR with cpuminer.
The algo supports AES SSE2 as indicated by cpuminer, but there is no such exe from the release,
we would need something compiled for cpuminer-aes-sse2.exe
When I run it on 26 cores, using the cpuminer-aes-avx2.exe it gives 365 H/s
When I run it using cpuminer-sse2.exe it gives 424 H/s.
********** cpuminer-opt 3.6.8 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
Forked from TPruvot's cpuminer-multi with credits
to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
Wolf0, Jeff Garzik and Optiminer.
CPU: AMD Ryzen Threadripper 1950X 16-Core Processor
CPU features: SSE2 AES AVX AVX2 SHA
SW built on Jul 31 2017 with GCC 4.8.3
SW features: SSE2 AES AVX AVX2
Algo features: SSE2 AES
Start mining with SSE2 AES
You should repeat your tests, I suspect the difference has more to do with thread mapping that AVX2. There is no AVX2 code in cryptonight to explain any difference in performance. But your choice of the number of threads makes it impossible to map correctly to the available cores. It is likely that some threads are bouncing from core to core causing erratic performance. I recommend trying with 16 threads which matches the cache size and avoids hyperthreading. You should generally choose the build based on your CPU's capabilities, not the algo. However some users have reported lower performance using AVX2 on Ryzen CPUs. |
|
|
|
Sorry for the dumb question, but if i download the files there is no *.exe to start. Where can i find it?
Download the binaries, not the source code. |
|
|
|
IGPUs use system memory so it could affect CPU mining of memory hard algorithms. Reduce the resolution
or use console mode to minimize the impact.
If system memory is a concern, you'd also want to get into the BIOS and reduce the amount of system RAM allocated for the integrated graphics, if that hasn't already been set to the minimum. It isn't so much the amount of system memory available but that the IGPU competes with the miner for cache space. |
|
|
|
|
IGPUs use system memory so it could affect CPU mining of memory hard algorithms. Reduce the resolution
or use console mode to minimize the impact.
|
|
|
|
Thanks for the miner.
Is there any command to reduce the number of cores the miner is using or any other way to reduce heat and efficiency?
Thanks
Yes you can limit the number of threads and there are some other options. Always check the help: cpuminer --help Note temperature limit only works on Linux. |
|
|
|
|
Give it up with cudaminer, it's over 3 years out of date. The only algos it supports are either dead or taken
over by ASICs. The code won't compile with new tools and won't run on new hardware when compiled with
old tools.
Use one of the many forks of ccminer that are actively developped.
|
|
|
|
It does make sense. Turning on the pagefile solved his problem, it wasn't defective memory. More GPUs require more virtual mem.
Add up all the mem on your GPUs and make sure your virtual mem (ram+pagefile) is bigger.
Let me clear this thing for you, windows takes all the physical memory first and if there is no more then takes from pagefile. So he clearly had a defective module on which was causing the problem cause if he had not then the system would work perfectly cause that is just how memory on windows work. You're way off base. First a defective memory module will crash the system the first time it's accessed unless it's completely invisible and appears to be an empty slot. Second, how pagefile (aka swap) works is beside the point. The point is more GPUs require more VM and if the requirements are more than the avaiable RAM it needs to use the pagefile. |
|
|
|
make sure the page file is on some how either set it to auto or manual if you turn it off with 2 or more GPU's and try to mine, you might get out of memory errors an then the PC stops mining , the main thing is it's on some how, i found out the hard way with 4 gpu rigs. ... with !6gb to 32 gb of memory with windows 10 pro....once i turned the page file back on the out of memory errors i was getting stopped. ... setting it manually works to.
It seems windows needs it on if your mining. after I got the errors i went on line an found a nice write up on why it should be left on .... i used to keep it off, on my 32 gb boxes till i started GPU mining.
sorry don't have that blog bookmarked or i would link it.
You know what you are saying makes no sense right? your memory modules were likely defective and it needed another thing which was not defective. Pagefile is the last thing called to be in use for any program, as long as you have lots of memory then your pagefile even if set will never be used. It does make sense. Turning on the pagefile solved his problem, it wasn't defective memory. More GPUs require more virtual mem. Add up all the mem on your GPUs and make sure your virtual mem (ram+pagefile) is bigger. |
|
|
|
Is there anyone that actually manages to mine on Nicehash (USA, EU, whichever) with their CPU's on a Linux box?
I've had difficulties compiling cpuminer-opt and cpuminer-multi from different forks, yet they all eventually throw stratum_recv_line failed at my head.
The nheqminer I never got to actually compile in the first place.
Nicehash sets the stratum difficulty too high for CPU miners so it takes longer to find a solution and the stratum sometimes times out. But poolside hash rate seems in line with local reporting. |
|
|
|
and is the hashrate the same? because if with nicehash it's faster, you know where those Watts are going...
NH 400KH/s BF 365KH/s Fact is that having GPU at 86°C against 72°C IS really a problem Since this is a thread about ccminer I'll try to bring this on topic. I noticed a similar issue with neoscrypt using ccminer. It runs 7C higher than other algos. It pushes my already hot 980 to 86C. As Pallas implied higher hashrates require more power and produce higher temps which is usually a good thing. But of all the algos that I think could stress a GPU that much, neoscrypt is low on the list. Other than improving the cooling (I already have a box fan in front of my 980) I don't know that anything can be done. |
|
|
|
Why? It's derived from GPL'd code, therefore it cannot be legally prevented to be distributed by anyone that gets it. In fact it's SP who's violating the GPL by not releasing the source code for his miners derived from GPL code. Those who pay him are enablers. |
|
|
|
whats most profitable to cpu mine right now or best long term coins to hol;d onto that this program can do?
also how bout XMR (monero) music coin and DMD diamon
are any of those profitable cpu mining on a core i5 7600k
I don't recommend coins. Do your own research, there's lots of info available. |
|
|
|
|
Typical whiny little child. Accuse me of being a bully then launch a personal attack with false accusations
of deleting your post. Just go away.
|
|
|
|
|
The waves are petty regular, don't usually see that from Nicehash. Maybe some other rental
with a schedule.
|
|
|
|
Loud beeping noise continue even after adding the second card, tried with 3 cards running, still beeping sound occurs. It doesn't do any beeping noise when a single card is running.
In OP you said it ran fine with 3. Looks like a bad GPU (edit: or riser). |
|
|
|
is this miner compatible with mac os x . i can't build it. can anyone send builded version with xevan alog support ?
Thanks.
Sorry, no MAC support. I should be possible (it compiles on FreeBSD) but I know nothing about MAC development so I can't help. |
|
|
|
Not on my todo list
your cpuminer can do it, i find it strange that you can not implement it here too It's a boring task. Any volunteers? Maybe an opportunity for a budding Cuda programmer to sharpen their skills. Not me. |
|
|
|
|
Show Posts
