 Show Posts
|
|
Pages: [1] 2 »
|
|
The miner gives me error connecting to bsod pool, i think that is when it connects for dev fee
|
|
|
|
lots and lots of payments not arrived wo my address today  |
|
|
|
network is 7TH/s
where are the miners?
17TH/s anybody know big mining pools? Hey noname71rus You can try to look for more details regarding the pool at the "Node mining portal" of Hdac - https://github.com/Hdactech/nomp Thanks, do you know already working pools? besides moric & dac  Come to http://dac.signal2noi.se We will be big pool in a few days, just started mining! |
|
|
|
I prefer coinexchange.io and graviex. Soon MTI will be added in cb exchange. We mined mti and my mining cost was above 3 to 4k satoshi per coin.
I am very excited to see the price in opening. Seems team will continue to develop the project.
MTI value at beginning was 6600 sats, proportional to MN presale Devs never allowed to trade in discord. In facto they banned me and others fort trying to sell mined MTI. Is not fair not allowing coin trade, devs only wantes the money and run. Then devs halved MN cost, halving MTI max value to 3300 sats If you think it will have a price mora than 1000 sats in exchange, you are dreaming. MN owners will massively dump theyr thousands of MTI at exchange start. Then coin dies. Mining this shit is worthless. |
|
|
|
So, a bit earlier then I expected but since it is lolMiners birthday (one week old now) lets have a party  Time for version 0.2(Also known as: "The first feature release") Ok, got 5*1060 gpu working But hashrate is ridiculous |
|
|
|
It is displayed hash in cmd. My cpu usage is about 60% with 5 gpus working, it is a 6-core AMD FX 6300
At least it is good to know that now you are able to start the miner with the 5 GPUs. Stats a step from the situation before. It may be that the fix is too aggressive for your system and sometimes slows the miner too much. If that is ok for you I will try a different implementation of the fix and write you a private message tomorrow. Maybe the variant I have in mind (that I have to code first) works better then the current fix. (I will of cause also test it locally and insert it into next version if that is indeed better). Ok, i will test and send snapshots if there is error |
|
|
|
lolMiner-mnx.exe --server mnx.suprnova.cc --port 7077 --user HarleyQuinn2011.Ru --p x --device 0 --enable-nv-hotfix
pause
Error after 5 minutes! What can i do???
Please HELP!
Wait until next version of the miner |
|
|
|
The performance drops A LOT randomly, in my 1060s from 10000 to 2200 sols
Is this displayed or pool hash rate varying? The one displayed by the miner should be constant. If this is not the case then something goes wrong with the lower CPU usage fix. This one tries to sleep the CPU for a certain amount of time depending on Kernel execution. Now if system is under very high load the measured values for kernel duration may vary to much for the fix. How much CPU load do you have running all your cards simultaneously? It is displayed hash in cmd. My cpu usage is about 60% with 5 gpus working, it is a 6-core AMD FX 6300 |
|
|
|
So, as promised it is time for an update: Here are the binaries for version beta v 0.11:Linux 64: https://drive.google.com/open?id=1l7TXYEfXbdGgkpQbIQAz9JGaV-5vYVdFWindows 64: https://drive.google.com/open?id=1remeVpaiVhqKkKZyo966xiVRsP_4OfeZChanges:Added a new command line parameter "--enable-nv-hotfix".The parameter will reduce the required CPU utilization on Nvidia graphic cards. If you required 100 + x% CPU utilization (so one full core and parts of a second) it is likely that now you will need 10-15% + x. I can not get rid of the x because this is for checking if the solution is below the target. On my 2.1 ghz CPU with a GTX 1080 attached CPU utilization went down from 115% to ~20%. This will also help running multiple instances for large rigs. Unfortunately one will loose about 1-2% of mining speed on Nvidia hardware when enabling the switch. Therefore - and because the loss may be even larger for other vendors - the hotfix has to be enabled by command line for each instance. Added an automatic reconnect when the connection is broken.When a share is submitted and there is no acceptance message by the pool for the next 10 seconds the miner will reconnect to the pool in order to get back a stable connection. This helps the miner not to hang. By the way: I think I found one glitch in the windows version causing the crash that happens after a while. This seem to happen when the pool sends a new job but not with enough parameters (jobId, time, merkle_root....). The fall back method seems to work fine on Linux, but causes the crash on Windows. Therefore I would recommend testing different pools as long as this is not fixed, because the rate is not equal for all pools. I will try to get this fixed in next version. By the way beside bugfixing the next features I would like to implement are (in order of their priority): - The opportunity to run it on multiple GPUs with only one stratum instance. - A handbrake function for the miner. More concretely a switch that lowers the hashrate but such that the graphic card is not busy 100% over the time. May help for rigs with temperature problems or overambitious graphic drivers that kill tasks that cause too much GPU load. - An algorithm toggle. The algorithm used can be configured to create different memory pressure on the card. Changing from default behavior may improve the speed graphic cards will less compute cores per shader processor as NV Tesla P100 or AMD Vega series. I hope that I can make it implementing at least one feature and some of the left known bugs till next week Ps: Current hashrate of all lolMiners out there: about 820 ksol/s (1,5% market share) The performance drops A LOT randomly, in my 1060s from 10000 to 2200 sols |
|
|
|
I have 5 GTX 1060 but I only get one card. you can explain in detail how to run all 5 cards
One bat per card, selecting the right gpu But it crashes often with more than 1 instance running thanks for the answer, but so far nothing has helped. I turn on the second bat file, it divides the power of one video card in half Lol Of course, te second bat should point to another GPU, not the first one dear friend of mine and you can write me examples of bat files that are valid for 2 GTX 1060. if not hard I try and I for some reason do not work Create two files. One for starting the miner and one starting the first file for each GPU, something like this: (change the 'GPUs' variable to the number of GPUs you would like to use for mining mnx) @echo off
set /A GPUs=3
set /A GPUs-=1
FOR /L %%i IN (0,1,%GPUs%) DO (
ECHO Starting miner on GPU%%i
start "lolMiner GPU%%i" "minexcoin.bat" %%i
) @echo off
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_HEAP_SIZE 100
:MINE
lolMiner-mnx.exe --server mnx.suprnova.cc --port 7077 --user WorkerName.%1 --pass x --device %1
goto :MINE This will start lolMiner-mnx for the number of GPUs specified and restart when/if the miner crashes. great! |
|
|
|
I have 5 GTX 1060 but I only get one card. you can explain in detail how to run all 5 cards
One bat per card, selecting the right gpu But it crashes often with more than 1 instance running thanks for the answer, but so far nothing has helped. I turn on the second bat file, it divides the power of one video card in half Lol Of course, te second bat should point to another GPU, not the first one |
|
|
|
I have 5 GTX 1060 but I only get one card. you can explain in detail how to run all 5 cards
One bat per card, selecting the right gpu But it crashes often with more than 1 instance running |
|
|
|
|
I left all niche 6 instances of the miner, in 2 separate rigs. 2 instances in every rig crashed
We cannot use your mine if we cannot leave it unatended
|
|
|
|
What many pf you see is high CPU utilization caused by the Nvida OpenCL drivers. Expect some fix for this comming next two to three days. This is also the reason for large rigs to crash - 6 instances on Nvidia currently require a CPU with 8 threads... I will handle this next, definately.
CL Local Size is currently fixed to 256 because the opencl part requires it. Selecting a lower value might save some time in barriers but I know that this is currently not the bottleneck to handle to achieve more speed. But maybe a good idea for the future.
I am surprised how many Windows user are here. I definately have to find a Windows testing system for me to get the Windows port stable.
@qwep: What GPU and driver version do you have?
Hello, I really do not understand what command to add CPU in miner? got ryzen 7 1700, want to try it. btw GPU worked good, thank you. 1080 ti 20600 sol/s PL - 80, MEM - 450 1050 ti 6600 sol/s PL - 85, MEM - 350 What command line do you use? My 1050tu gives 3300 sols/s |
|
|
|
What many pf you see is high CPU utilization caused by the Nvida OpenCL drivers. Expect some fix for this comming next two to three days. This is also the reason for large rigs to crash - 6 instances on Nvidia currently require a CPU with 8 threads... I will handle this next, definately.
CL Local Size is currently fixed to 256 because the opencl part requires it. Selecting a lower value might save some time in barriers but I know that this is currently not the bottleneck to handle to achieve more speed. But maybe a good idea for the future.
I am surprised how many Windows user are here. I definately have to find a Windows testing system for me to get the Windows port stable.
@qwep: What GPU and driver version do you have?
With other opencl miner, i noticed that local size of 384/768 speeded up a lot things with nvidia I have 1060, 1070 and 1070ti with latest nvidia drivers |
|
|
|
|
With an i5-4690k , more than 3 instances of the miner with 1060s, the hashrate of every instance falls dramatically
When the miner crases, the error relates to libstdc++-6.dll
Can you put a parameter on miner to set -cl-local-work?
Perhaps the solution another miner developer adopted may be useful to you
He made a opencl miner that eat all cpu available, and the more gpus working, less performance for each one
There is an issue with NVIDIA GPUs leading to very high CPU usage. The reason is improper implementation of OpenCL by NVIDIA. When CPU thread waits for results from GPU, it does not stop, it spins in loop eating CPU resources for nothing.
There was impemented a workaround on this issue: before reading results from GPU current thread sleeps during small calculated time.
He resolved it and the miner is more stable and a lot faster.
|
|
|
|
Thanks will try it out. I am also getting lilboost system md error on some rigs? Thats interesting... on some but not on all? Can you provide more info about your configuration and how the rigs may differ? From libbost system md I assume that the rigs are running Windows? When i use a few instances, some of them crash and close
The maximum that I tested here were 2 instances running on two GTX 1080... So I do not know yet what happens with more. Can ypu give me more info about your config and what error message is given at crash time? Hope we can find the issue quickly. I will think during this evening how I can thank you early testers reporting bugs and hash rates. Will give a post on that tomorrow Tried 5 instances with nvidia 1060 and W10 2 of them eventually crashed with windows message "app stopped working" |
|
|
|
|
When i use a few instances, some of them crash and close
|
|
|
|
Dev-fee is too high and we are missing CUDA optimized miner. We already have OpenCL miner. So I suggest you lower the dev-fee and make a CUDA version.
Can you tell me where to find OpenCL miner for windows? mxMiner download I read about, but is it faster than lolminer? |
|
|
|
|
