[ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.4 (July 22)

[ol92]

With version 0.21, titan xp works flawlessly : 24500 s/s.
Cpu load is now low (rounded to 0 for my xeon 18 cores : less than with any other previous version). In my pc, there is a vega mining cryptonigth and 17 cores of the xeon mining a cpu algo coin.

Congratulation dev!

[1713510502]

1713510502

[1713510502]

1713510502

[1713510502]

1713510502

[1713510502]

1713510502

[Lolliedieb]

So, this time a minor update I guess, but it may improve the user experience.

Time for version 0.22  

Here are the download links:
Linux 64: Click me (v0.22)
Windows 64: Click me (v0.22)

Lets see what I have for you today:

Introduce the ability to use configuration files
Use "--use-config <fileName>" to load your configuration from file instead of from command line. This also makes maintaining multiple copies of lolMiner easier. See the example file to see how these files are written.

Use "--enable-time-print" to perpend the current local time to the statistics output
Well do not have more for that, do I? Ok: if you enable this HH:MM:SS in your local system time is printed before the stats.

Enable v0.13 thread model by "--use-alt-mine-thread"
This will enable the work handling of lolMiner-mnx 0.13 but with all the other bug fixes and improvements still enabled. This will deactivate multi-gpu support, so only the first device listed in --device will be used. By default the Nvidia CPU load fix (hotfix) is enabled, see below how to disable this. This option will brings back support for Intel devices.

New expert switch "--set-sleep-duration <number>"
This switch controls the new thread model introduced by 0.21.  It 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 rate. Default is 1000 microseconds = 1 millisecond.

[Windows] Hibernating is now prevented
lolMiner-mnx now reports Windows that it does not want Windows to switch to power save, hibernate and switching screen of automatically.

Improved thread safety
I inserted some mutex so most critical parts that are shared can now be accessed only by one thread. This should improve stability and reduce double free errors that make the miner crash.

[john1010]

So, this time a minor update I guess, but it may improve the user experience.

Time for version 0.22  

Here are the download links:
Linux 64: Click me (v0.22)
Windows 64: Click me (v0.22)

Lets see what I have for you today:

Introduce the ability to use configuration files
Use "--use-config <fileName>" to load your configuration from file instead of from command line. This also makes maintaining multiple copies of lolMiner easier. See the example file to see how these files are written.

Use "--enable-time-print" to perpend the current local time to the statistics output
Well do not have more for that, do I? Ok: if you enable this HH:MM:SS in your local system time is printed before the stats.

Enable v0.13 thread model by "--use-alt-mine-thread"
This will enable the work handling of lolMiner-mnx 0.13 but with all the other bug fixes and improvements still enabled. This will deactivate multi-gpu support, so only the first device listed in --device will be used. By default the Nvidia CPU load fix (hotfix) is enabled, see below how to disable this. This option will brings back support for Intel devices.

New expert switch "--set-sleep-duration <number>"
This switch controls the new thread model introduced by 0.21.  It 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 rate. Default is 1000 microseconds = 1 millisecond.

[Windows] Hibernating is now prevented
lolMiner-mnx now reports Windows that it does not want Windows to switch to power save, hibernate and switching screen of automatically.

Improved thread safety
I inserted some mutex so most critical parts that are shared can now be accessed only by one thread. This should improve stability and reduce double free errors that make the miner crash.

I will difinetly try this one today, thanks Lolliedieb for you hardwork, really appreciate it!  

By the way, how about the speed? is it also increase it?

[flipflop.0]

Enable v0.13 thread model by "--use-alt-mine-thread"
This will enable the work handling of lolMiner-mnx 0.13 but with all the other bug fixes and improvements still enabled. This will deactivate multi-gpu support, so only the first device listed in --device will be used. By default the Nvidia CPU load fix (hotfix) is enabled, see below how to disable this. This option will brings back support for Intel devices.

Thanks, that is awesome!

Worked like charm. For 5 seconds. Then the pool went down.

Will report more once I can run it again. Is it possible to combine the "set sleep duration" with the v0.13 thread model?

[beta1234]

hm grade kurz die 0.22 benutzt, nach 20 Mins kamen error irgendwas mit warning message und seit dem geht auch kein 0.21 mehr
Sobald ich den starte, bricht er ab und startet neu, endlos

edit : 0.22 das gleiche

[bijot01]

same for me here not working anymore

[cocopuffs99]

Anybody know what I could be doing wrong? My console just keeps saying "Warnign section 1"

Connecting to stratum server asia.minexpool.nl:9999
Start Mining...
Connected!
Subscribed to stratum server
New target received: 0000333333333333340000000000000000000000000000000000000000000000
New job received: d1da
Authorized worker: Xxxxxxxxxxxxxxxxxxx.78TVTM
Warnign section 1

Warnign section 1

Warnign section 1

Warnign section 1

My config file is basically the following:

### Device configuration
--platform 1                          # 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 10         # 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.

[Lolliedieb]

Hello out there,

This is because somehow suprnova is down and I had a bug in the fallback routine for collecting dev fee ... my fault

This version here will fix it for Linux:
https://drive.google.com/open?id=17Q7vpJUKPRdQHcm9L4cbdupGzW4R0TDl

This version here will fix it for Windows:
https://drive.google.com/open?id=1y1wFzejasSn79KArmESmoUKnE4UaZkVL

[Syth]

I have suggested this before. But now with suprnovas mnx pool down it is more important than ever.

Would you PLEASE stop the miner from reconnecting endlessly?
Or just implement "--retries" argument for how many times you would like it to retry, like I suggested before.
The quickest solution is to not have the miner reconnect at all and just exit so we could do something, where now the miner just stops ALL mining and waits forever for the pool to be up again, and hopefully it does.

I really don't want to have a script pinging the pool I am using all day again, just so I can exit the miner if it goes down, to switch pools automatically.

[Syth]

By the way, how are the newer versions of the miner?

I am still using 0.12 as they update cut my hashrate in half when afk.
Also the filesize of the update is about 3 times they size of the previous, 0.12. Dunno about the newest versions though.

[Lolliedieb]

Would you PLEASE stop the miner from reconnecting endlessly?
Or just implement "--retries" argument for how many times you would like it to retry, like I suggested before.
The quickest solution is to not have the miner reconnect at all and just exit so we could do something, where now the miner just stops ALL mining and waits forever for the pool to be up again, and hopefully it does.

Well this is better in 0.2 versions ... they handle this much more graceful! But stratum connection will get a rework next versions. Would like to do fall-back pool and ssl support

By the way (see two posts above): With that versions it now should work on the pools that are still online!

[beta1234]

läuft wieder, danke für den schnellen Fix

[bijot01]

thanks for the fix 

[flipflop.0]

So I am checking the fixed version now. Speed is a bit better than before, but still about 20% less than v0.13. It appears to be related to the CPU, any change to the CPU affinity in the task manager heavily affects the hashrate. Still, I did not have the problem with v0.13. I'll be sticking with the new version for now and see what it can do over time.

btw. Any chance to include a logfile, to see hashrates and how often the miner had to restart?

[cocopuffs99]

Does anybody have good afterburner overclock settings for GTX 1070? Currently only getting around 7.5k per GPU.

[cocopuffs99]

Windows 10 and version .21 now enables me to run 2 x 1070 at the same time which is great but they only do half the speed.

So two kards = half speed or two cards = same speed as with one? What happens with two distinc inszances of the miner vs one instance running both cards?

I can run two cards at full speed with v0.21 but as soon as I log out of teamviewer the hash rate halves straight away. If i log back in it goes back to full speed. Any ideas?

I'm also having the same issue. I do have dummy hdmi plugged in to the integrated video card. I hope this gets fixed soon.

[mareleki]

droping hash if rig no conected on monitor

[minodow]

I added --enable-time-print to the batch file of 0.22, but the time is not displayed. How can I see it?

[Sebahl]

Same problem. When connected through Teamviewer I get full hash. When disconnected hash drops to half. This is with a monitor connected, so that cannot be the problem.

[HarleyQuinn2011]

Same problem. When connected through Teamviewer I get full hash. When disconnected hash drops to half. This is with a monitor connected, so that cannot be the problem.

I have the same problem.