Pages:
Author

Topic: [ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.4 (July 22) - page 20. (Read 30771 times)

newbie
Activity: 11
Merit: 0
After working 30s goes to 0 Sol/s and than crashes. 3x1070 + 3x1080 works in stock...
jr. member
Activity: 230
Merit: 1
V0.3 is really running good and stable with my 1070's.
Lolliedieb - How about optimizing AMD cards, especially Vega cards? Cheesy
newbie
Activity: 84
Merit: 0
Pool problem, it's under attacks.
newbie
Activity: 45
Merit: 0
Anybody have same problems? Every 10-15 mins lolminer 0.31 losing connect to eu.minexpool.nl and trying to reconnect (need for this around 2-3 mins)
This problem of pool or lolminer? Problem start after anonce of 0.31
jr. member
Activity: 230
Merit: 1
Please advise me whether this is a pool problem or a problem in setting up my miner. It is very strange that the pool began to fall often.

Also please advise me what can be corrected in the settings of my miner,because sometimes it hangs and stops working. Since it can work 10 hours without failures, and then after restart it can stop working in an hour or two (randomly).

It seems that this was a pool problem - almost all pools were down today for some time since the complete mining ecosystem of the coin was under attack.

As for the random crashes no solution yet, but always try to make it more stable. Already working on new ideas for that.

@ All that send me their mnx address because of the bug / new miner bounty campaign:
The payments just left my wallet!  Grin
It remained approx 11 mnx unclaimed, that will reach the faucet soon.

You can see the transactions done on this address:
https://minexexplorer.com/?r=explorer/address&hash=XJ47v5a4Axv192U8Q9CjkidvwHh9CQZz3u
Here you see one outgoing transaction splitting the value in two parts, one smaller (to one of you) and one larger (as self transaction from the wallet software).
clicking on the larger one you can see the next outgoing transaction and so on. Overall there should be 30 transactions in this chain right now. The 31st will be the one to faucet Smiley

Thanks you all very much for your support!  Cool

Thank you I received my payment Smiley
newbie
Activity: 84
Merit: 0
It could be that miner is now better optimized for 1080, I'm getting 18-19 and before was no more than 16 and I'm not complaining Cheesy
newbie
Activity: 29
Merit: 0
As you can see, 1060s are obeying clock/power limit, but 1080 does not, leading to regular crashes of this card.

Well I do not influence the clocks of your card at all - I just run a program there, but do not set any clocks or fan speeds nor voltages - nothing. lolMiner does not even read this values, because in OpenCL standard its not designated to do so.

So if your card is not following your power target setting, this is an driver / overclocking tool or cards bios bug, but non of the miner, since it just takes no influence in that.
Okay.. then why this wasn't an issue with lolminer v0.2x. 1080 at these same clocks was hashing at 12-13ksol max, but 0.3x always at 15 (only for this one card/1080). the hardware and os are the same, I only updated the miner. Could this be that lolminer is only showing 15Ksol, but the actual hashrate is lower?

Driver Version: 390.25
Code:
Linux ****** 4.8.17-ethos49 #6 SMP Tue Aug 29 23:24:18 CDT 2017 x86_64 x86_64 x86_64 GNU/Linux
member
Activity: 433
Merit: 48
As you can see, 1060s are obeying clock/power limit, but 1080 does not, leading to regular crashes of this card.

Well I do not influence the clocks of your card at all - I just run a program there, but do not set any clocks or fan speeds nor voltages - nothing. lolMiner does not even read this values, because in OpenCL standard its not designated to do so.

So if your card is not following your power target setting, this is an driver / overclocking tool or cards bios bug, but non of the miner, since it just takes no influence in that.
newbie
Activity: 29
Merit: 0
My cards running at stock clocks (or close to stock)
card 1 is EVGA GTX1080 SC (gddr5x)/180w plimit, the other 5 are GIGABYTE GTX1060 6GB G1 Gaming (gddr5)/120w plimit
Code:
0, 2018/03/16 23:28:17.998, 114.26 W, 1771 MHz, 3802 MHz, 1771 MHz
1, 2018/03/16 23:28:18.002, 152.82 W, 1759 MHz, 4353 MHz, 1759 MHz
2, 2018/03/16 23:28:18.007, 105.52 W, 1771 MHz, 3802 MHz, 1771 MHz
3, 2018/03/16 23:28:18.012, 105.22 W, 1771 MHz, 3802 MHz, 1771 MHz
4, 2018/03/16 23:28:18.017, 109.44 W, 1746 MHz, 3802 MHz, 1746 MHz
5, 2018/03/16 23:28:18.027, 105.53 W, 1771 MHz, 3802 MHz, 1771 MHz

As you can see, 1060s obeys clock/power limit setting, but 1080 isn't (lolminer only), leading to regular crashes of this card.
Code:
23:30:28 Average speed (60s): 15400.6 sol/s | 10537 sol/s | 10426.1 sol/s | 10307 sol/s | 10182.4 sol/s | 10298.4 sol/s Total: 67151.5 sol/s
No matter what clocks I apply, lolMiner rides 1080 at max clocks.

Please look into it and fix that asap. Thanks in advance.
member
Activity: 433
Merit: 48
Please advise me whether this is a pool problem or a problem in setting up my miner. It is very strange that the pool began to fall often.

Also please advise me what can be corrected in the settings of my miner,because sometimes it hangs and stops working. Since it can work 10 hours without failures, and then after restart it can stop working in an hour or two (randomly).

It seems that this was a pool problem - almost all pools were down today for some time since the complete mining ecosystem of the coin was under attack.

As for the random crashes no solution yet, but always try to make it more stable. Already working on new ideas for that.

@ All that send me their mnx address because of the bug / new miner bounty campaign:
The payments just left my wallet!  Grin
It remained approx 11 mnx unclaimed, that will reach the faucet soon.

You can see the transactions done on this address:
https://minexexplorer.com/?r=explorer/address&hash=XJ47v5a4Axv192U8Q9CjkidvwHh9CQZz3u
Here you see one outgoing transaction splitting the value in two parts, one smaller (to one of you) and one larger (as self transaction from the wallet software).
clicking on the larger one you can see the next outgoing transaction and so on. Overall there should be 30 transactions in this chain right now. The 31st will be the one to faucet Smiley

Thanks you all very much for your support!  Cool
newbie
Activity: 12
Merit: 0
newbie
Activity: 23
Merit: 0
With --optim OFF Nvidia GTX 1060 3GB increased from 10300 to 11100-11200 sol / s at 80 watts consumption
Thank you

I am running the same card and also found that --optim OFF was better, but with overclocking mine can churn through about 13000Sol/s but using almost 115W power (on Linux).

Is yours running with any overclocking and is it Windows or Linux?
newbie
Activity: 4
Merit: 0
Dear Lolliedeb,
Hello!

Your new versions are really good.
Below you can see a picture with a mistake.

https://b.radikal.ru/b17/1803/75/dd5583eb4e4f.jpg

Please advise me whether this is a pool problem or a problem in setting up my miner. It is very strange that the pool began to fall often.

Also please advise me what can be corrected in the settings of my miner,because sometimes it hangs and stops working. Since it can work 10 hours without failures, and then after restart it can stop working in an hour or two (randomly).
newbie
Activity: 6
Merit: 0
Hey Lolliedeb

how do you run the miner using your processor and threads.

Thanks
hero member
Activity: 2100
Merit: 562
I am using v.31 right now and seems that my hash increase, I got 8700-9.2k sol using rx 480 8gb watching now if it is stable or not.

Thanks for your work dude!!
hero member
Activity: 910
Merit: 1002
Lolliedieb, I can't use OFF and STD both in same bat file  - --optim OFF,STD,STD,OFF not work.
newbie
Activity: 15
Merit: 0
Eu.minexpool ceased to work, but the program continued to try to connect to it and did not fail.
It's good
newbie
Activity: 84
Merit: 0
I'm using --platform 0 for my nvidia rig, as with all previous versions. Never had this kind of error.
This error happens with latest version, if I close miner and open it again.
After restart, it works as usual.
Same error with Auto for platform, just checked.
Started 0.3 version, without rebooting rig and this version also stuck but it listed devices.
I use auto for batch size, it gives me this values:
Code:
Using device with id 0 (GeForce GTX 1080 Ti )
Using device with id 1 (GeForce GTX 1070 )
Using device with id 2 (GeForce GTX 1080 )
Using device with id 3 (GeForce GTX 1080 Ti )
Using device with id 4 (GeForce GTX 1060 3GB )
Using device with id 5 (GeForce GTX 1080 Ti )
Using device with id 6 (GeForce GTX 1060 3GB )
Using device with id 7 (GeForce GTX 1080 Ti )
Selected work-batch for device 0: 24
Selected work-batch for device 1: 32
Selected work-batch for device 2: 24
Selected work-batch for device 3: 24
Selected work-batch for device 4: 20
Selected work-batch for device 5: 24
Selected work-batch for device 6: 20
Selected work-batch for device 7: 24
I guess I will return to 0.3 version, it worked more than 24 hours without error Cheesy
member
Activity: 433
Merit: 48
That is intetesting - so you set the platform number to a non existing value. Does this also happen with --platform AUTO?
newbie
Activity: 84
Merit: 0
with this 0.31 versions getting this new error on nvidia rig:
http://i63.tinypic.com/3026xz4.jpg
This happens if I close miner and open it again, only rebooting helps.
Pages:
Jump to: