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

[NSPhotoX]

I must be doing something wrong with the GTX 1080 because I'm only putting out 16.5ksols not 19k as stated here. (V.34)
Work batch is set on HIGH and i've tried optimization on STD and OFF, both have returned same hashrates.
Any GTX 1080 miners willing to share their config if you're getting much more than 16.5ksols?

And I feel like a noobie dum dum. A slightly better overclocking is doing the trick. Got 'er up to 18ksols now.

[1714007480]

1714007480

[1714007480]

1714007480

[Anon11073]

Where can I download lolminer-mnx v 0.1 or 0.11 ?

Why do you need to download the old version?

Older versions of miners are inefficient and unstable.
However, I have a v0.13 miner(Windows version). Shall I upload?

[Lolliedieb]

Hey guys, i have a strange problem, i have in my rig Ryzen 1800x, RAdeon r9 280 and GTX 1080TI
The miner shows strange activity, it disables r9 280, and gives some pnp errors and then trying to disable some HD 3400 and in the end it just starts GTX 1080ti, no matter what i do, i cant start mining on R9 and ryzen....

Ah... the problem is that the watchdog is not prepared for AMD / Nvidia mixed rigs. Best is to comment out the "resetGPUs" line at the botom.of the watchdog. Next the miner atm only runs on Nvidia or AMD but not both at the same time. So you have to create two config files, one with --platform 0 and one with  --platform 1. Then start two copiesof the miner

I am currently testing your miner, it's showing as connected to mining pool: eu.minexpool.nl,  giving average speed and getting new jobs. However, I am not seeing my worker on the pool workers list, what could be the prob?

So it is connected and shows "submitting share" / "share accepted"? Then it is indeed connected to pool. What may be is that worker name and or used payout addr are not valid - at the moment the check for this is disabled on pool side (so one always got a acceptance of worker msg from pool) because there was a simple way of ddos on that routine bringing down the pool... then you will mine but not seeing anything in pool overview.


As for those searching for 0.13: write me a pm and I could send you something. Although I wonder why, because current 0.3x versions are both - faster and more stable. Just for comparison: at the moment all lolMiner together do 140Msol +... back then it was 2 Msol ... and that for good reason (the software was plainly not mature in any ways ^^)

[menruou]

this coin is obviously failing the past week.  Btc and most alts are way up. Mnx has lost value of more than 50000 satoshis.
Where are the buy orders from the bank as stated in the white paper?

[especial]

i'm using this, but if i start first mining on nvidia, when i start mining amd, nvidia freezes. its the same whenever i try to run mining on 2 diffirent devices. If i set mining on all amd, computer freezes and restarts. strange!

For now there is no possibility to run 2 instances, one would kill other one....

any solutions?

thank you

Hey guys, i have a strange problem, i have in my rig Ryzen 1800x, RAdeon r9 280 and GTX 1080TI
The miner shows strange activity, it disables r9 280, and gives some pnp errors and then trying to disable some HD 3400 and in the end it just starts GTX 1080ti, no matter what i do, i cant start mining on R9 and ryzen....

Ah... the problem is that the watchdog is not prepared for AMD / Nvidia mixed rigs. Best is to comment out the "resetGPUs" line at the botom.of the watchdog. Next the miner atm only runs on Nvidia or AMD but not both at the same time. So you have to create two config files, one with --platform 0 and one with  --platform 1. Then start two copiesof the miner

I am currently testing your miner, it's showing as connected to mining pool: eu.minexpool.nl,  giving average speed and getting new jobs. However, I am not seeing my worker on the pool workers list, what could be the prob?

So it is connected and shows "submitting share" / "share accepted"? Then it is indeed connected to pool. What may be is that worker name and or used payout addr are not valid - at the moment the check for this is disabled on pool side (so one always got a acceptance of worker msg from pool) because there was a simple way of ddos on that routine bringing down the pool... then you will mine but not seeing anything in pool overview.


As for those searching for 0.13: write me a pm and I could send you something. Although I wonder why, because current 0.3x versions are both - faster and more stable. Just for comparison: at the moment all lolMiner together do 140Msol +... back then it was 2 Msol ... and that for good reason (the software was plainly not mature in any ways ^^)

[NSPhotoX]

i'm using this, but if i start first mining on nvidia, when i start mining amd, nvidia freezes. its the same whenever i try to run mining on 2 diffirent devices. If i set mining on all amd, computer freezes and restarts. strange!

For now there is no possibility to run 2 instances, one would kill other one....

any solutions?

thank you

I'm currently mining on 4 nvidia cards and 1 amd card on the same system with no issues. I'm sure there is something minor that you're missing (I lose my pen while holding it sometimes too).
Just look over your cfg and batch files. You might try specifying an exact file path (c:\. . . . . \ . . . config.cfg) of the cfgs in the bat so you know for sure there isn't a mixup.

[Lolliedieb]

i'm using this, but if i start first mining on nvidia, when i start mining amd, nvidia freezes. its the same whenever i try to run mining on 2 diffirent devices. If i set mining on all amd, computer freezes and restarts. strange!

For now there is no possibility to run 2 instances, one would kill other one....

any solutions?

Do you do this in Windows? If yes with or without the watchdog? The watchdog is not really prepared for two miner instances at the same time, so running without may be an option.

[universekid]

Where can I download lolminer-mnx v 0.1 or 0.11 ?

Why do you need to download the old version?

Older versions of miners are inefficient and unstable.
However, I have a v0.13 miner(Windows version). Shall I upload?

With the old version 2-3x more coin mined as the new one. Please upload the old versios if you can. I want to try it again. Thanks!

[amdfxman1701]

Wouldn't this have more to do with the change in difficulty as opposed to the miner itself?

[especial]

does anyone have lolminer 0.34 without watchdog, i cant get it to work with amd and nvidia even separated

[mikebzh44]

Hi.

I was using lolMiner v030 for days (even months) on Suprnova pool.

Today, want to give a try on Minexpool and I upgrade to v034

But now I have segmentation fault when I start a miner, with v030 AND v034 on Minexpool AND Suprnova

I tryed v022 on Minexpool but : Error: There is noch such platform on this device

I'm running on Linux.

Don't know if it's helpfull but when I try to run OptiMiner, I have this error :

[2018-04-28 09:58:51.765] [default] [info] Optiminer/Equihash 2.1.1 (C) Optiminer 2017
[2018-04-28 09:58:51.765] [default] [info] Connecting to mnx.suprnova.cc:7077.
[2018-04-28 09:58:51.794] [default] [error] OpenCL error: Failed to list OpenCL platforms! (Unknown OpenCL error -1001)

Maybe it's an hardward problem but graphics cards are listed with lspci :

01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b82 (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 10f0 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1b82 (rev a1)
02:00.1 Audio device: NVIDIA Corporation Device 10f0 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1b82 (rev a1)
03:00.1 Audio device: NVIDIA Corporation Device 10f0 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1b82 (rev a1)
05:00.1 Audio device: NVIDIA Corporation Device 10f0 (rev a1)

And with nvidia-smi :

Code:

+-----------------------------------------------------------------------------+
| NVIDIA-SMI 381.22                 Driver Version: 381.22                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Graphics Device     On   | 0000:01:00.0      On |                  N/A |
| 37%   27C    P8    11W / 120W |     11MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  Graphics Device     On   | 0000:02:00.0      On |                  N/A |
| 37%   27C    P8    11W / 120W |     10MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  Graphics Device     On   | 0000:03:00.0      On |                  N/A |
| 37%   25C    P8    11W / 120W |     10MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   3  Graphics Device     On   | 0000:05:00.0      On |                  N/A |
| 37%   25C    P8    11W / 120W |     10MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0      1426    G   /usr/lib/xorg/Xorg                               8MiB |
|    1      1426    G   /usr/lib/xorg/Xorg                               7MiB |
|    2      1426    G   /usr/lib/xorg/Xorg                               7MiB |
|    3      1426    G   /usr/lib/xorg/Xorg                               7MiB |
+-----------------------------------------------------------------------------+

I didn't change my overcolck settings for a while.

What can I do ?

Thanks.

EDIT : Maybe my USB stick is corrupted because when I try to remove overclock settings, I get :

./nvidia-overclock.sh

ERROR: libatk-1.0.so.0: wrong ELF class: ELFCLASS32
       libnvidia-gtk3.so: cannot open shared object file: No such file or directory
       libatk-1.0.so.0: wrong ELF class: ELFCLASS32
       libnvidia-gtk2.so: cannot open shared object file: No such file or directory


ERROR: A problem occured when loading the GUI library. Please check your installation and library path. You may need to specify this library when calling nvidia-settings. Please run
       `nvidia-settings --help` for usage information.

As I'm running on a dedicated USB Linux distribution, I will try to make a new stick from scratch.

[Vudda]

I can't seem to find the watchdog for Linux in this thread, nor did it come with 0.34?

[Lolliedieb]

[2018-04-28 09:58:51.794] [default] [error] OpenCL error: Failed to list OpenCL platforms! (Unknown OpenCL error -1001)

Maybe it's an hardward problem but graphics cards are listed with lspci :

Hmm no... both miners seem to miss the OpenCL driver or the OpenCL ICD ... I think completely re-installing drivers from scratch will solve this.

I can't seem to find the watchdog for Linux in this thread, nor did it come with 0.34?

True, there is none. The Windows watchdog covers most of the Windows runtime bug the miner has, but that are plainly not presend on Linux. The only problem it covers that exist on Linux as well is 0 sol/s, but since Linux does not allow to deactivate a device and reset it completely without reboot that function would not work on Linux. So the simple Linux .sh script almost does all the job the watchdog could do :/

Wouldn't this have more to do with the change in difficulty as opposed to the miner itself?

I also think so... the difficulty is far higher now. The nethash was 50 to 65M when 0.13 was out but 0.21 not yet there. Today its 130 to 150 so the income at the moment is only half and less then back then - at same hash rate. To befair 0.34 computes hashes about 15% faster then the 0.1x versions and is more stable. Anyways... there was a seriozs bug in 0.1x versions causing trouble on pool side. If its ok for you give me a bit and I will put a kind of 0.13b version with that bug patched out here.

[FFI2013]

Is anyone mining with older r9 cards I have a mix rig with 270,280 and 390's and was wondering how they mined or expected hashrates 

[catfish78]

Is anyone mining with older r9 cards I have a mix rig with 270,280 and 390's and was wondering how they mined or expected hashrates 

270 - 4729 sol/s
270x - 5250 sol/s
280x - 9310 sol/s

1000 mV and stock core/mem

[ol92]

Hello dev,

Could you have a look to this other variant of equihash please?
https://bitcointalk.org/index.php?topic=3373738.new#new
Equihash 210/9

This could bring you new miners with leveraging on your existing miner...

[catfish78]

Is anyone mining with older r9 cards I have a mix rig with 270,280 and 390's and was wondering how they mined or expected hashrates 

Hashrates with heavily undervolted and -clocked summer settings: 950/1250 MHz core/mem  @ 970 mV

270 - 4670 sol/s
270x - 4800 sol/s
280x - 8700 sol/s

[Lolliedieb]

Hello dev,

Could you have a look to this other variant of equihash please?
https://bitcointalk.org/index.php?topic=3373738.new#new
Equihash 210/9

This could bring you new miners with leveraging on your existing miner...

Because I also got some private messages about that - I just can confirm that I am working on other Equihash variants as well and these include Equi 210/9 (Aion) as well as Equi 192/7 (Zero). But its still some way - the lolMiner concept was very memory hungry to get it up to speed and applying that for these coins is much more harder then for Minex. But this will have also a positive effect for Minexcoin - because I promised that once I switch over to more coins I will lower the fee to 1% for this one

Also I can confirm that I am working on the next version of this one. The updated OpenCL code is already done, currently I am investigating the possibility to ship the kernels in a binary fashion. As an advantage I could compile it for every device in an optimized way and also I can protect my work better from decompiling it that way. Currently I am still a bit shy on that because there may be devices where offline compiling is difficult (e.g. many miners do not support Vega yet because of that) and I do not want to blow the archive size because of so man binary kernels. Lets see if I come up with a proper solution

[Dormis]

Because of the positive initial interview results, there's no reason for us NOT to buy more. This s the best time to BUY and PARK. HAPPY PARKINGS GUYS!!!!!!!👍❤️

[Apocalypse Onion]

I just can confirm that I am working on other Equihash variants as well and these include Equi 210/9 (Aion) as well as Equi 192/7 (Zero).

BTCP have announced plans for 144/5. Hope you can do that one too! Bitmain sucks donkey balls but it's a good time to be a lolminer, lol.