AndreasSantonio
Newbie
Offline
Activity: 34
Merit: 0
|
|
March 01, 2018, 10:43:36 AM |
|
In Ubuntu sometimes the window of the miner simply closes. Is there a script for automatic restart?
|
|
|
|
skomi84
Newbie
Offline
Activity: 8
Merit: 0
|
|
March 01, 2018, 11:31:01 AM |
|
For your Nvidia I recommend not to change work batch from default and use 2 cards in one instance without alternative mine thread. That should give least CPU load and best performance unless you have the "TeamViewer" bug.
Enabling multigpu Without options gives me much better hash rate conf 2x1060 3gb (non TI) , 19600 sol/s ( about 9800 per card ) but crash randomly. Hope for 0.3v to solve issues.
Very good job.
|
|
|
|
skomi84
Newbie
Offline
Activity: 8
Merit: 0
|
|
March 01, 2018, 11:51:44 AM |
|
Miner after 2-30minutes on 2x1060 3gb (non TI ,not OC , not MOD) , crash Problem signature: Problem Event Name: APPCRASH Application Name: lolMiner-mnx.exe Application Version: 0.0.0.0 Application Timestamp: 5a905403 Fault Module Name: lolMiner-mnx.exe Fault Module Version: 0.0.0.0 Fault Module Timestamp: 5a905403 Exception Code: c0000005 Exception Offset: 0000000000140746 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: ee46 Additional Information 2: ee468c567de3a5cb9ccd63beda0902f8 Additional Information 3: c37d Additional Information 4: c37d3ef5fedc854af2724675666ddf4e
hope this helps.
|
|
|
|
technick
Newbie
Offline
Activity: 22
Merit: 0
|
|
March 01, 2018, 11:55:17 AM |
|
For your Nvidia I recommend not to change work batch from default and use 2 cards in one instance without alternative mine thread. That should give least CPU load and best performance unless you have the "TeamViewer" bug.
work batch is default, but "TeamViewer" bug is present
|
|
|
|
elektrofusion7
Newbie
Offline
Activity: 12
Merit: 0
|
|
March 01, 2018, 06:13:39 PM |
|
conf 4xR9 270( not X) --set-work-batch 8 --set-sleep-duration 750 70% cpu usage (new intel gxxxx on h61) , hash rate 16000sol/s ( 3800 - 4200 per card ) , stable 24h
I set work-batch to 6. Now stable for days and 4300sol/s(gigabyte 270 fab oc to 975MHz) I did have some random problems. Like some cards lose connection to server but another card in same motherboard in that moment have connection, after some time another card same problem.... There was some error message but I forgot to save it. I restart miner and miner was slow in starting up. Restart computer...same problem, restart again everything is ok, so I don`t know what was the problem. Also then miner mine with normal hashrate but there is no found shares.
|
|
|
|
Lolliedieb (OP)
|
|
March 02, 2018, 09:27:51 AM |
|
Hi all finally I am back at my computer (was on a four days trip) and I am now pushing things for 0.3. Many people asked me in the meantime when this will come and what it will feature, so here is kind of the announcement: lolMiner-mnx 0.3 will arrive between March 12 and March 16 if nothing unexpected happens Features will be a complete rewritten stratum interface that hopefully is more stable and produces less crashes. Also I try to improve stability, buzzword: loosing single cards during mining. Finally I already found some improvements regarding hash-rate. I now can promise both vendors will gain at least 10%. Still I am searching for some more speed in particular on AMD cards. Beside the 0.3 announcement I want to say that I am amazed by the feedback I got the last weeks. Thank you all very much for your comments and your help in finding all the bugs and so on. This said I also want you to know that the list of early adopters and helpers closed two days ago. I will prepare a list of all that are eligible of claiming their fraction of the bug bounty in the beginning of next week. If the current market share and luck continues I will send out more then 50 mnx to the helpers. Still I have to prepare a kind of bucketing on how much help I got so it is kind of fair for you. Will see ^^ By the way: the income from first two weeks are parked right now - will gain some extra % for you By the way 50% of unclaimed mnx will be divided to the ones how did their claim and the rest will be send to a mnx faucet. So, thats the state of progress, hope to come with more news soon. Stay tuned
|
Check out lolMiner 1.56, an efficient miner for Ethash, Beam and many Cuckoo-Cycle and Equihash variants for AMD & Nvidia cards at low fees.
|
|
|
jezined
Newbie
Offline
Activity: 23
Merit: 0
|
|
March 02, 2018, 12:36:39 PM |
|
Hi all finally I am back at my computer (was on a four days trip) and I am now pushing things for 0.3. Many people asked me in the meantime when this will come and what it will feature, so here is kind of the announcement: lolMiner-mnx 0.3 will arrive between March 12 and March 16 if nothing unexpected happens Features will be a complete rewritten stratum interface that hopefully is more stable and produces less crashes. Also I try to improve stability, buzzword: loosing single cards during mining. Finally I already found some improvements regarding hash-rate. I now can promise both vendors will gain at least 10%. Still I am searching for some more speed in particular on AMD cards. Beside the 0.3 announcement I want to say that I am amazed by the feedback I got the last weeks. Thank you all very much for your comments and your help in finding all the bugs and so on. This said I also want you to know that the list of early adopters and helpers closed two days ago. I will prepare a list of all that are eligible of claiming their fraction of the bug bounty in the beginning of next week. If the current market share and luck continues I will send out more then 50 mnx to the helpers. Still I have to prepare a kind of bucketing on how much help I got so it is kind of fair for you. Will see ^^ By the way: the income from first two weeks are parked right now - will gain some extra % for you By the way 50% of unclaimed mnx will be divided to the ones how did their claim and the rest will be send to a mnx faucet. So, thats the state of progress, hope to come with more news soon. Stay tuned keep up the good work! I have been testing out your v0.22 lolminer running on my Dell laptop (7th gen i7 quad core CPU and M1200 Nvidia GPU) with ubuntu 16.04 and also Win10 and can confirm that Ubuntu produces a better Sol/s rate and is much more stable. So far my average Sol/s using just the M1200 is about 3.6KS/s which is about x10 better than 1 core of the i7 CPU (I cannot seem to get it to use multiple cores), but today I purchased a "refurbished" HP Omen Accelerator so that I can try out using this with a proper GPU card, however with the current prices for something like a GTX1080ti it's not quite worth it.. so I might start with a used GTX 970 someone is selling nearby online. If the GTX 970 is reported to be able to do 291.61 Sol/s for Zcash, what should I expect it to do with MNX?
|
|
|
|
mnxfl
Newbie
Offline
Activity: 19
Merit: 0
|
|
March 02, 2018, 12:55:05 PM |
|
970 mines at 9000 Sol/s. Even 750ti mines at 3900 Sol/s. Very efficient for Maxwell GPUs. .22 has worked perfectly for me in Windows and Linux.
|
|
|
|
jezined
Newbie
Offline
Activity: 23
Merit: 0
|
|
March 02, 2018, 01:24:52 PM |
|
970 mines at 9000 Sol/s. Even 750ti mines at 3900 Sol/s. Very efficient for Maxwell GPUs. .22 has worked perfectly for me in Windows and Linux.
thanks for that... so my built in Nvidia M1200 supposedly performs at about 3500 Sol/s according to the output from lolminer but the stats shown online at eu.minexpool.nl are a bit wild, with an average of around 4K Sol/s only 9000 Sol/s for a GTX 970? I'll see if I can talk the guy down in price from £150 to £100 or less
|
|
|
|
kgeorgiev
Copper Member
Newbie
Offline
Activity: 91
Merit: 0
|
|
March 02, 2018, 02:34:10 PM |
|
Hey guys, I went through the whole topic and it seems nobody has a solution for the "Teamviewer" bug yet, right ?
|
|
|
|
prostoegorii
Newbie
Offline
Activity: 2
Merit: 0
|
|
March 02, 2018, 04:51:40 PM |
|
Hey guys, I went through the whole topic and it seems nobody has a solution for the "Teamviewer" bug yet, right ?
lowering a hashrate on disconnection "Teamviewer"?
|
|
|
|
kgeorgiev
Copper Member
Newbie
Offline
Activity: 91
Merit: 0
|
|
March 02, 2018, 07:47:19 PM |
|
Hey guys, I went through the whole topic and it seems nobody has a solution for the "Teamviewer" bug yet, right ?
lowering a hashrate on disconnection "Teamviewer"? Yes, my 1060s go from 10k to 4-5k sols when i disconnect
|
|
|
|
Xaboom
Newbie
Offline
Activity: 6
Merit: 0
|
|
March 02, 2018, 07:53:52 PM |
|
Keep up the good work!!!
Impatiently waiting for v.3 , on all my rigs are amd cards.
|
|
|
|
prostoegorii
Newbie
Offline
Activity: 2
Merit: 0
|
|
March 02, 2018, 09:59:40 PM |
|
Hey guys, I went through the whole topic and it seems nobody has a solution for the "Teamviewer" bug yet, right ?
lowering a hashrate on disconnection "Teamviewer"? Yes, my 1060s go from 10k to 4-5k sols when i disconnect It's simple. Launch youtube for endless browsing
|
|
|
|
badfad
Jr. Member
Offline
Activity: 186
Merit: 4
|
|
March 03, 2018, 12:34:24 AM Last edit: March 03, 2018, 12:54:22 AM by badfad |
|
It's simple. Launch youtube for endless browsing
yes it works perfectly. Edit:Anyone got problem with payments yesterday? I received none.
|
|
|
|
Newton90
|
|
March 03, 2018, 01:03:50 PM |
|
very good work.but need to fix "teamviewer bug".on my rig@6*1060/3 hashrate drop when teamviewer closed from 8 and 9(on diffrent cards) to 4 and 8 ksol.with --set-work-batch 3 hashrate on all cards drop to 6 ksol.
p.s. Lolliedieb,do you plan to create miner for zero(equihash192_7)?
|
|
|
|
mRpqlz
Newbie
Offline
Activity: 2
Merit: 0
|
|
March 03, 2018, 02:20:57 PM |
|
Hey guys, I went through the whole topic and it seems nobody has a solution for the "Teamviewer" bug yet, right ?
lowering a hashrate on disconnection "Teamviewer"? Yes, my 1060s go from 10k to 4-5k sols when i disconnect It's simple. Launch youtube for endless browsing I have solved this problem by changing the work-batch parameter to 8
|
|
|
|
Lolliedieb (OP)
|
|
March 03, 2018, 10:32:31 PM |
|
p.s. Lolliedieb,do you plan to create miner for zero(equihash192_7)?
Lets get this one stable and fast first ^^ Equihash 192 / 7 would be kind of interesting ... but also challenging since it consumes more then 256 times the memory then Equihash 96/5. When lolMiner is stable and fast enough I will surely give a try
|
Check out lolMiner 1.56, an efficient miner for Ethash, Beam and many Cuckoo-Cycle and Equihash variants for AMD & Nvidia cards at low fees.
|
|
|
loewe1631
Newbie
Offline
Activity: 13
Merit: 0
|
|
March 04, 2018, 08:29:31 AM |
|
I set up a minexcoin pool myself and it works fine when I use optiminer and I get it when I use lolminer [ Connected! Subscribed to stratum server New target received: 0003333333333333400000000000000000000000000000000000000000000000 New job received: cd08 Start Mining ... ./run_miner.sh: line 22: 30972 Segmentation fault ./lolMiner-mnx --use-config $ CFGFILE $ @] And repeat this infinite loop Such a mistake, how can I solve it Thank you
|
|
|
|
Mulcrypto
Newbie
Offline
Activity: 6
Merit: 0
|
|
March 04, 2018, 12:46:15 PM |
|
Hi
Today I want to start mining MNX with my nvidia rig 6 GPU GTX 1060 6GB
In the cfg file I read that for multiple GPU we need to set the following:
--device 0,1,2,3,4,5
But when I run the miner it only shows device 0
Can somebody help me with this ?
these are my settings
@echo off
setlocal enableDelayedExpansion
Rem ################################# Rem ## Begin of user-editable part ## Rem #################################
Rem Insert your configuration file name here set "CNAME=example_config.cfg"
Rem ################################# Rem ## End of user-editable part ## Rem #################################
set "PARAMS=--use-config %CNAME%"
:MINE Start /wait /high lolMiner-mnx.exe !PARAMS! goto :MINE
########################################################## # This is an example configuration file for lolMiner-mnx # # # # Every line starting with "--" will be interpreted as # # the normal parameters passed to lolMiner-mnx. # # Every other parameter will be handled as a comment. # # # # Have fun mining! # ##########################################################
### User based configuration --server eu.minexpool.nl # Insert the pool address here --port 9999 # Insert your pool port here --user XS5urveU6ZVJZTD6yy8gNE9qnGLjMh5JSs.worker0 # Insert your user and worker names here --pass x # Insert your worker password here
### Device configuration --platform 0 # Insert the index of the platform you want to run on. Run lolMiner-mnx.exe --list-devices # to see all available platforms and the available devices for each platform --device 0,1,2,3,4,5 # Insert your devices to run the miner here. For multiple GPU pass a comma separated list, e.g.: 0,1 for using two GPUs
--set-work-batch 2 # Uncommend this line to set the work batch size. Default is 2 which is ideal for Nvidia customer GPUs. # For AMD GPUs try higher values, e.g. 8 or 12 to optimize performance. Higher values increase GPU memory use of lolMiner-mnx.
### Display log configuration #--set-short-stats-interval 5 # Uncommend to set the time interval (seconds) between the short term performance output. Set 0 to disable the output. #--set-long-stats-interval 60 # Uncommend to set the time interval (seconds) between the long term performance output. Set 0 to disable the output. # The value will also determine the length of the benchmark mode #--enable-time-print # Uncommend to allow lolMiner-mnx to print the system time in HH:MM:SS format before each performance output.
### Expert parameters - handle with care #--use-alt-mine-thread # Enables the mine thread handling of lolMiner-mnx 0.13. This will disable multi-GPU support. # Therefore only the first number in --device is handled. The Nvidia load hotfix is enabled by default. # Currently Intel devices are only working with this switch enabled.
#--set-sleep-duration 1000 # Sets the time span between polling the GPUs for completed work in microseconds. Lower values may stabilize # the performance, but also increase CPU load for all vendors. Setting the value to 0 will make lolMiner-mnx use one full # CPU core by 100% for handling all devices. If this is used with "--use-alt-mine-thread" it will disable the Nvidia hotfix. # Higher values reduce CPU load but may reduce hash speed. Default is 1000 microseconds = 1 millisecond.
|
|
|
|
|