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

[psihotoc]

Guys why my hashrate falls on 0 after 30 + minutes mining. Coin Minexcoin like all norms works and after Bach and on zero.

[Cuzzle]

Any watchdog type of script that might help with this issue?

0.34 will come next week (hopefully) ... and with a new (real) watchdog script for Windows power shell that should do the job

This is excellent news as lolminer crashes on various rigs (its running on 9 rigs, mix of nvidia and amd) at random time and random rigs.

I can find no pattern or similiarity. All these rigs were rock solid for weeks on other mining programs (not a criticism, just providing information, I appreciate your program and efforts a lot)

[psihotoc]

In General, the problem with 0 hashrate was solved by new risers. Was the riser for the power Molex I replaced the riser with power 6 pin all stabilized and no departures and the hash of all smooth maps became.

[Anon11073]

Any watchdog type of script that might help with this issue?

0.34 will come next week (hopefully) ... and with a new (real) watchdog script for Windows power shell that should do the job

I am looking forward to the new version.
I hope it will be more stable behavior on Windows version.

Good job, Lolliedieb.

[reciu]

hey anyone knows is lolMiner works on SMOS i cant run it  on windows and hiveos works great!

[gizmochefmogwai]

As I said, this miner crashs randomly, it is confirmed by other people...

Please work on it on linux distro if you plan to du some updates on Windows.

I confirm this miner cause big SATA crashes, and need hard reboot. Before this arrive, I can see some cards running at 0.

Building fuc-ing watchdog script is not an acceptable programmer answer, please make a safer code and maybe stop devfee during this beta test.

Hello,

Works like a charm on 12* 1070 rig, but only for 8 hours.

After this delay, huge crash some GPU disconnected, SATA bug with no access on OS commands (reboot, etc.., not found)

No OC, Ubuntu server 16.04, Driver Version: 390.48

Check this clinfo for last GPU :

Code:

  Device Name                                     GeForce GTX 1070
  Device Vendor                                   NVIDIA Corporation
  Device Vendor ID                                0x10de
  Device Version                                  OpenCL 1.2 CUDA
  Driver Version                                  390.48
  Device OpenCL C Version                         OpenCL C 1.2
  Device Type                                     GPU
  Device Profile                                  FULL_PROFILE
  Device Topology (NV)                            PCI-E, 0f:00.0
  Max compute units                               15
  Max clock frequency                             1746MHz
  Compute Capability (NV)                         6.1
  Device Partition                                (core)
    Max number of sub-devices                     1
    Supported partition types                     None
  Max work item dimensions                        3
  Max work item sizes                             1024x1024x64
  Max work group size                             1024
  Preferred work group size multiple              32
  Warp size (NV)                                  32
  Preferred / native vector sizes
    char                                                 1 / 1
    short                                                1 / 1
    int                                                  1 / 1
    long                                                 1 / 1
    half                                                 0 / 0        (n/a)
    float                                                1 / 1
    double                                               1 / 1        (cl_khr_fp64)
  Half-precision Floating-point support           (n/a)
  Single-precision Floating-point support         (core)
    Denormals                                     Yes
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 Yes
    Round to infinity                             Yes
    IEEE754-2008 fused multiply-add               Yes
    Support is emulated in software               No
    Correctly-rounded divide and sqrt operations  Yes
  Double-precision Floating-point support         (cl_khr_fp64)
    Denormals                                     Yes
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 Yes
    Round to infinity                             Yes
    IEEE754-2008 fused multiply-add               Yes
    Support is emulated in software               No
    Correctly-rounded divide and sqrt operations  No
  Address bits                                    64, Little-Endian
  Global memory size                              8513978368 (7.929GiB)
  Error Correction support                        No
  Max memory allocation                           2128494592 (1.982GiB)
  Unified memory for Host and Device              No
  Integrated memory (NV)                          No
  Minimum alignment for any data type             128 bytes
  Alignment of base address                       4096 bits (512 bytes)
  Global Memory cache type                        Read/Write
  Global Memory cache size                        245760
  Global Memory cache line                        128 bytes
  Image support                                   Yes
    Max number of samplers per kernel             32
    Max size for 1D images from buffer            134217728 pixels
    Max 1D or 2D image array size                 2048 images
    Max 2D image size                             16384x32768 pixels
    Max 3D image size                             16384x16384x16384 pixels
    Max number of read image args                 256
    Max number of write image args                16
  Local memory type                               Local
  Local memory size                               49152 (48KiB)
  Registers per block (NV)                        65536
  Max constant buffer size                        65536 (64KiB)
  Max number of constant args                     9
  Max size of kernel argument                     4352 (4.25KiB)
  Queue properties
    Out-of-order execution                        Yes
    Profiling                                     Yes
  Prefer user sync for interop                    No
  Profiling timer resolution                      1000ns
  Execution capabilities
    Run OpenCL kernels                            Yes
    Run native kernels                            No
    Kernel execution timeout (NV)                 Yes
  Concurrent copy and kernel execution (NV)       Yes
    Number of async copy engines                  2
  printf() buffer size                            1048576 (1024KiB)
  Built-in kernels
  Device Available                                Yes
  Compiler Available                              Yes
  Linker Available                                Yes
  Device Extensions                               cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_nv_create_buffer

NULL platform behavior
  clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...)  No platform
  clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...)   No platform
  clCreateContext(NULL, ...) [default]            No platform
  clCreateContext(NULL, ...) [other]              Success [NV]
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU)  No platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU)  No platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR)  No platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM)  No platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL)  No platform

[Good cat]

Hi people. And what you get by means of lolminer now?

[Cuzzle]

Hi people. And what you get by means of lolminer now?

what?

https://www.youtube.com/watch?v=WsJSRP7cZVo&ab_channel=dondrapersayswhat

[Good cat]

Hi people. And what you get by means of lolminer now?

what?

https://www.youtube.com/watch?v=WsJSRP7cZVo&ab_channel=dondrapersayswhat

What?

[Lolliedieb]

Finally its there: A new version of lolMiner ^^   

More concretely: 0.34 is there


Similar as in the past I did not plan to do this version, but the changes I planned for 0.4 were too fundamental and so well – I wanted to have this intermediate version with its fixes done before.

Here are the download links:
[Lin 64] Click me (0.34, Linux) MD5 of package: 4b6a86481177fe4d09e4dcc71fe20828
[Win 64] Click me (0.34, Windows) MD5 of package: 27075cf216144bc4f47fc139b1fdb7e7


So, what is new:

Windows only: A new watchdog.
This version of lolMiner comes with a watchdog script written in power shell. Basically it detects when the miner is stuck / has 0 sol/s and so on and can restart it if required. You can start it by clicking run_miner.cmd while the old run script is also on board.

To configure the new watchdog you have to edit the watchdog-lolminer-v0.34.ps1 file. Especially you should give the name of your config file in the beginning.

The watchdog is able to reboot the rig after a certain number of miner restarts. To enable this feature you have to set $global:allowReboot=$true in the header of the watchdog on line 18. For the reboot feature to be effective you should place the watchdog in your auto-start.

Also you can allow it do do a screen shot on every crash by setting  $global:allowScreenshot=$true on line 19. The parameter in line 18 controls the number of restarts before the watchdog closes itself or reboots the rig.

In order to handle 0 sol/s cases the watchdog will require admin rights on your computer when it starts. This allows the watchdog to reset your GPU drivers before a new restart attempt. Because of this we made the watchdog open source so you can verify it does no harm to your system.

Fixed a bug in stratum code:
Before the miner got stuck when the first pool in list was not avaiable. This is fixed now. Also the miner no longer closes when the first pool reports an authorization of miner problem, but it now tests all failover pools in a row before exiting due to missing authorization

Changed behavior of –exit-on-zero
Well … did not find a better headline for this. The parameter –exit-on-zero does not exist any more / has no effect. Instead when the miner detects that a GPU did not come back from a mining task properly it will print an error message and close. The same is true when a device does not finish a task for more then 30 seconds.

New internal stratum behavior
The stratum code now monitors for shares not tested (if they are below target) or not submitted. When there was no single share tested for a minute or no share submitted for 10 minutes, the miner will stop working and close itself, so the restart scripts or the Windows watchdog can restart it.

New parameter: --continue-on-error
This is the counterpart to the above two described changes. If this parameter is set the miner will continue working even when an error occurred.
New parameter: --stats-digits <number>
This will set the number of digits printed in statistics messages. E.g. if you set it to 0 the decimal delimiter and everything behind will be cut of. The default is 1.

Slight changes in work management
The change is something I wanted to test for 0.4. Basically it now tries to do the transfer from and to the cards asynchronously. Especially on AMD cards this helps reducing the difference in speed between –work-batch HIGH and AUTO and lower values. Higher is still mining faster but the difference to lower values is now smaller

New parameter: --disable-double-buffer
This is the counterpart to the work management change. For some drivers (the open source Clover OpenCL drivers on Linux) this is required because not all drivers support the change. 

New parameter: --disable-suprnova-for-fee
This parameter is meant to remove the suprnova pool from the list of fall-backs for the miners dev fee. Reason is that this pool is blocked in some countries and that the miner may get stuck on an ISP block of this pool.

lolMiner-mnx now got a license.txt file
Well that was required xD

lolMiner-mnx now displays proper AMD device names
Well its not yet perfect, but I think “Radeon RX 470/480; RX 570/580” is better then “Ellesmere” - but I may be wrong ^^


I hope you have fun with this release. I will now prepare the next steps. As said the planned changes to 0.4 are rather massive, therefore it may take some time.

---------------------
For the stats:
Overall hash rate of all lolMiners out there: 185 Msol/s
Market share: 84%

[Cuzzle]

Finally its there: A new version of lolMiner ^^   

More concretely: 0.34 is there


Similar as in the past I did not plan to do this version, but the changes I planned for 0.4 were too fundamental and so well – I wanted to have this intermediate version with its fixes done before.

Here are the download links:
[Lin 64] Click me (0.34, Linux) MD5 of package: 4b6a86481177fe4d09e4dcc71fe20828
[Win 64] Click me (0.34, Windows) MD5 of package: 27075cf216144bc4f47fc139b1fdb7e7


So, what is new:

Windows only: A new watchdog.
This version of lolMiner comes with a watchdog script written in power shell. Basically it detects when the miner is stuck / has 0 sol/s and so on and can restart it if required. You can start it by clicking run_miner.cmd while the old run script is also on board.

To configure the new watchdog you have to edit the watchdog-lolminer-v0.34.ps1 file. Especially you should give the name of your config file in the beginning.

The watchdog is able to reboot the rig after a certain number of miner restarts. To enable this feature you have to set $global:allowReboot=$true in the header of the watchdog on line 18. For the reboot feature to be effective you should place the watchdog in your auto-start.

Also you can allow it do do a screen shot on every crash by setting  $global:allowScreenshot=$true on line 19. The parameter in line 18 controls the number of restarts before the watchdog closes itself or reboots the rig.

In order to handle 0 sol/s cases the watchdog will require admin rights on your computer when it starts. This allows the watchdog to reset your GPU drivers before a new restart attempt. Because of this we made the watchdog open source so you can verify it does no harm to your system.

Fixed a bug in stratum code:
Before the miner got stuck when the first pool in list was not avaiable. This is fixed now. Also the miner no longer closes when the first pool reports an authorization of miner problem, but it now tests all failover pools in a row before exiting due to missing authorization

Changed behavior of –exit-on-zero
Well … did not find a better headline for this. The parameter –exit-on-zero does not exist any more / has no effect. Instead when the miner detects that a GPU did not come back from a mining task properly it will print an error message and close. The same is true when a device does not finish a task for more then 30 seconds.

New internal stratum behavior
The stratum code now monitors for shares not tested (if they are below target) or not submitted. When there was no single share tested for a minute or no share submitted for 10 minutes, the miner will stop working and close itself, so the restart scripts or the Windows watchdog can restart it.

New parameter: --continue-on-error
This is the counterpart to the above two described changes. If this parameter is set the miner will continue working even when an error occurred.
New parameter: --stats-digits <number>
This will set the number of digits printed in statistics messages. E.g. if you set it to 0 the decimal delimiter and everything behind will be cut of. The default is 1.

Slight changes in work management
The change is something I wanted to test for 0.4. Basically it now tries to do the transfer from and to the cards asynchronously. Especially on AMD cards this helps reducing the difference in speed between –work-batch HIGH and AUTO and lower values. Higher is still mining faster but the difference to lower values is now smaller

New parameter: --disable-double-buffer
This is the counterpart to the work management change. For some drivers (the open source Clover OpenCL drivers on Linux) this is required because not all drivers support the change. 

New parameter: --disable-suprnova-for-fee
This parameter is meant to remove the suprnova pool from the list of fall-backs for the miners dev fee. Reason is that this pool is blocked in some countries and that the miner may get stuck on an ISP block of this pool.

lolMiner-mnx now got a license.txt file
Well that was required xD

lolMiner-mnx now displays proper AMD device names
Well its not yet perfect, but I think “Radeon RX 470/480; RX 570/580” is better then “Ellesmere” - but I may be wrong ^^


I hope you have fun with this release. I will now prepare the next steps. As said the planned changes to 0.4 are rather massive, therefore it may take some time.

---------------------
For the stats:
Overall hash rate of all lolMiners out there: 185 Msol/s
Market share: 84%

This is AWESOME news!! I will be migrating my farm to this version today, starting with my most troublesome rigs. Thanks so much!   

[Cuzzle]

Working through your pdf and I see the following, thanks a TON for including this feature!! I wish all miners did this. 

--stats-digits <number>
This parameter adjusts the number of decimal digits that are printed in the statistics output. The minimum is
0, which corresponds to no digits beyond decimal delimiter printed. The default is one.

[bugnotme]

Lolliedieb,
Could we expect any performance improvements in future releases?

[xberg]

Hi,
Thanks for 0.34 release!

Reading your release notes it seems that this version still does not support Fiji (AMD R9 Fury / Nano)? Is this still planned for 0.4.0?

Many thanks!

[Lolliedieb]

Working through your pdf and I see the following, thanks a TON for including this feature!! I wish all miners did this. 

Your welcome
For 0.4 I plan to allow that users can switch sol/s for ksol/s ... lets see

Lolliedieb,
Could we expect any performance improvements in future releases?

Yes, the 0.34 already mines a bit faster compared to 0.33. On my Linux test rig about 2% faster on my Windows AMD Kaveri machine about 5%. Not that big numbers, but faster is faster
For 0.4 I will likely add the support for binary kernels. That may allow the download of Kernels that are optimized for your GPU. Also maybe I provide Kernels then with inline assembler code for more speed. Lets see ^^

Reading your release notes it seems that this version still does not support Fiji (AMD R9 Fury / Nano)? Is this still planned for 0.4.0?

The release notes are not complete - else it would take longer to write them as to write the new code ^^
I just checked the OpenCL Kernel code in AMD offline compiler:

Code:

Target GPU detected:
Fiji (Graphics IP v8)
	AMD FirePro (TM) S9300 x2
	AMD MxGPU
	AMD Radeon (TM) Graphics Processor
	AMD Radeon (TM) R9 Fury Series
	AMD Radeon Graphics Processor
	Radeon (TM) Pro Duo
	Radeon Pro SSG Development Kit

Building for Fiji... succeeded.

So the Kernel builds and also the code runs on my test systems with other AMD GCN V3 platforms (I have no Fiji card here, but well - chip architecture is the same) ... so IMAO it should run with 0.34

[xberg]

Hi,

YES! I confirm that 0.3.4 works with AMD Fiji (Fury).
You can add to your benchmark on first page:

AMD R9 Nano: 11.5k (stock clock, same result at 2G or HIGH).
AMD R9 Fury X: 12.3K
AMD Radeon Pro Duo: 23.8k

Good job!

How can I calculate profitability for this mining?

[catfish78]

Lolliedieb,
0.34 running faster (4%) in my R9 200 cards!
Thank You!

[Lolliedieb]

YES! I confirm that 0.3.4 works with AMD Fiji (Fury).
You can add to your benchmark on first page:

AMD R9 Nano: 11.5k (stock clock, same result at 2G or HIGH).
AMD R9 Fury X: 12.3K
AMD Radeon Pro Duo: 23.8k

Great to hear that and thank you for the numbers Also good to know that the 2G / High deliver approx the same. That was purpose of the changes to bring this a bit closer together, so people with virtual memory problems do not lose any more so much hash speed when using lower work batch sizes.

How can I calculate profitability for this mining?

Every hour there are on average 20 Blocks found with 2.5 MNX each, so 50 MNX per hour created. Of this 40 go to miners and the other 10 to minex bank. So your income is approximately

(Your Hash / Network Hash) * 960 MNX / day

From that still you must subtract pool and miner fee.

For example with rigs doing 190k one has 0.1% of network hash rate and thus gets 0.96 - pool and miner fee per day.
Be careful with mining calculators, many existing forget the MNX going to the minex bank and thus overestimating the income.   

[Anon11073]

Hello, Lolliedieb.

I am trying v 0.34, but the screen got drowned when I started up.
Is this normal? The executable file is "run_miner.cmd".

Also, is it possible to adjust the load with v 0.4?

[Cuzzle]

Hello, Lolliedieb.

I am trying v 0.34, but the screen got drowned when I started up.
Is this normal? The executable file is "run_miner.cmd".

Also, is it possible to adjust the load with v 0.4?

What do you mean 'drowned'?