[ANN]Bminer: a fast Equihash/Ethash/Cuckaroo29z miner for AMD/NVIDIA GPUs 16.4.9

[TONY_GUN]

v3.0.0 doesn't work for me. It appears to successfully connect to luckpool.org, receive a difficulty value from the server, and then says "Miner died, restarting"; repeat, ad nauseum. This is a Win7 x64 SP1 machine with (2) GTX 1060 3GB cards. DSTM 0.5.6 and 0.5.7 work fine (indeed, 0.5.7 is running now) on the same pool with the same credentials.

At this point I am done screwing around with this train wreck, as I am philosophically opposed to paying for the "privilege" of being a beta tester.

What is your MoBo and CPU? I have the same problem. Two identical rigs on the old 775 socket. But first rig with quad-core CPU core2quad Q8400 (bminer works excellent, about week uptime without errors). The second rig with the same mobo, same GPU's and dual-core CPU core2duo E6750 says "Miner died, restarting" too. On the same time DSTM 0.5.6 and 0.5.7 work fine on this E6750 rig.

[1714004740]

1714004740

[MagicSmoker]

What is your MoBo and CPU? I have the same problem. Two identical rigs on the old 775 socket. But first rig with quad-core CPU core2quad Q8400 (bminer works excellent, about week uptime without errors). The second rig with the same mobo, same GPU's and dual-core CPU core2duo E6750 says "Miner died, restarting" too. On the same time DSTM 0.5.6 and 0.5.7 work fine on this E6750 rig.

This was with an AMD Phenom II 955 and an Asus M4N75TD mobo on Windows 7 - so, completely different!

Still, pretty brazen to charge a devfee for an alpha-level program. I have the same complaint with Claymore's Cryptonight miner, which lies so bad about hashrate it should be made into a rug... <rimshot!>

 

[realbminer]

v3.0.0 doesn't work for me. It appears to successfully connect to luckpool.org, receive a difficulty value from the server, and then says "Miner died, restarting"; repeat, ad nauseum. This is a Win7 x64 SP1 machine with (2) GTX 1060 3GB cards. DSTM 0.5.6 and 0.5.7 work fine (indeed, 0.5.7 is running now) on the same pool with the same credentials.

At this point I am done screwing around with this train wreck, as I am philosophically opposed to paying for the "privilege" of being a beta tester.

It turns out there is a compatibility issue with luckpool.org. It will be addressed in the next release.

[realbminer]

Happy new year!

4.0.0 is released. Thanks everyone for the feedback.

There are quite a bit of improvements in this release:

• Minor performance improvement.
• Support older CPUs like Core 2 Duo.
• Support mining rigs that have more than 8 GPUs.
• Support luckpool.org.
• Removed the polling option.
• Introduced the option `-max-network-failures` which allows Bminer to exit after consecutive network failures.
• Various improvement on the UI.
• Localization for Russian and Chinese.

Happy mining!

[matmator]

this miner is equihash only?

[MagicSmoker]

The swiftness of the OP's response convinced me to give this Yet Another Chance... and it now works fine on luckpool. It's only been running a few minutes so I hesitate to report on performance, but dstm 0.5.7 was delivering a fairly consistent 610 sols/s with (2) GTX 1060 3GB and a total draw of 360W (ie - not just the cards).

So far, bminer 4.0.0 is reporting around 625 sols/w at the exact same draw of 360W, so it appears to have made significant improvement in the power draw while pulling just enough ahead of the competition to make the devfee worth paying.

I still would like to see cumulative run time reported to the console (calculating sols/w, which dstm does, seems superfluous unless you try out a lot of different cards in one slot while keeping the rest the same).

[NameTaken]

[syraka76]

[WARN] [2018-01-02T22:00:35+01:00] Get error: Connessione in corso interrotta forzatamente dall'host remoto., resetting in 5 seconds
[INFO] [2018-01-02T22:00:40+01:00] Connected to zcl.suprnova.cc:4142
[WARN] [2018-01-02T22:00:40+01:00] Get error: Connessione in corso interrotta forzatamente dall'host remoto., resetting in 5 seconds
[INFO] [2018-01-02T22:00:45+01:00] Connected to zcl.suprnova.cc:4142
[WARN] [2018-01-02T22:00:45+01:00] Get error: Connessione in corso interrotta forzatamente dall'host remoto., resetting in 5 seconds
[INFO] [2018-01-02T22:00:50+01:00] Connected to zcl.suprnova.cc:4142
[WARN] [2018-01-02T22:00:50+01:00] Get error: Connessione in corso interrotta forzatamente dall'host remoto., resetting in 5 seconds
[INFO] [2018-01-02T22:00:55+01:00] Connected to zcl.suprnova.cc:4142
[WARN] [2018-01-02T22:00:55+01:00] Get error: Connessione in corso interrotta forzatamente dall'host remoto., resetting in 5 seconds

[syraka76]

BMINER
Uptime
4 minuti
Speed (Sols / S)
2854.03
0   45   173   477.34   2.76
1   45   164   473.37   2.89
2   43   167   474.02   2.84
3   50   170   477.22   2.81
4   49   175   479.56   2.74
5   48   159   472.52   2.97
_______________________________________________________________________________ __

DSTM'S

0   GeForce GTX 1070   44   506.88   2.75   184.03   5 / 0   47
1   GeForce GTX 1070   45   508.78   2.83   179.65   3 / 0   41
2   GeForce GTX 1070   43   510.41   2.81   181.49   7 / 0   47
3   GeForce GTX 1070   50   501.70   2.73   183.96   10 / 0   41
4   GeForce GTX 1070   48   506.17   2.80   180.99   6 / 0   36
5   GeForce GTX 1070   48   503.25   2.90   173.75   4 / 0   47
Total   -   3037.21   2.80   1083.87   35 / 0   43

[ChuckD]

I've had success with version 3.0, running at 2900 H/s on 6x GTX 1070Ti's, but the version 4.0 code silently fails and immediately exits without any output.

I am running:  Windows 10, Nvidia driver ver 23.21.13.8813 (10/27/2017).

Not sure what, if any other info you'd like, but I'd be happy to assist further.

[realbminer]

I've had success with version 3.0, running at 2900 H/s on 6x GTX 1070Ti's, but the version 4.0 code silently fails and immediately exits without any output.

I am running:  Windows 10, Nvidia driver ver 23.21.13.8813 (10/27/2017).

Not sure what, if any other info you'd like, but I'd be happy to assist further.

I'm happy to help -- just wondering how did you run the miner?

My guess is that your command line parameters might be off. Can you try directly click on bminer.exe and to test whether it works?

Thanks.

[ChuckD]

Clicking on bminer.exe directly it runs ... so I copied over the new mine.bat file in the v.4 distribution and starting with the original var settings, it ran until I got all the way through to config'ing the API ... and it runs.   Sorry, I must have fat-fingered something in the original .bat, for all is good now.

BTW, love the graphs in the new API!

[car1999]

is it faster than ewbf and dstm?

[wetblanket]

This is WHY I keep trying to tell folks "specify watts, NOT PERCENT" on TDP numbers as % means NOTHING unless you specify the specific card model and even THEN it's confusing.

Absolutely, yes. That, and also specify if your OC settings are from Windows or Linux - there's a difference (one is double the other).

[tf2addict]

What is your MoBo and CPU? I have the same problem. Two identical rigs on the old 775 socket. But first rig with quad-core CPU core2quad Q8400 (bminer works excellent, about week uptime without errors). The second rig with the same mobo, same GPU's and dual-core CPU core2duo E6750 says "Miner died, restarting" too. On the same time DSTM 0.5.6 and 0.5.7 work fine on this E6750 rig.

This was with an AMD Phenom II 955 and an Asus M4N75TD mobo on Windows 7 - so, completely different!

Still, pretty brazen to charge a devfee for an alpha-level program. I have the same complaint with Claymore's Cryptonight miner, which lies so bad about hashrate it should be made into a rug... <rimshot!>

 

If only there was some way to validate hash rates at the pool.

[wetblanket]

Recently tested Bminer: agree, the performance is just amazing. More than 15% faster than EWBF on the same cards. Up to stable 320 Sol/s for 1060 3GB and 600 Sol/s for G1 1080.

But before mass moving to Bminer I have two questions:
1. What the "firmware.bin" file is for? Does Bminer reflash your video cards? Can this affect guarantee?
2. Why it keeps connections not only to the specified pool but two more hosts nowhere mentioned?

Good questions. Would also like to know an answer to those before mass moving to bminer.

I don't think these questions have actually been definitely answered? I see speculation on #2, and nothing on #1. Thanks.

[MagicSmoker]

If only there was some way to validate hash rates at the pool.

Is this sarcasm? If so, might want to add the  to the end of such a statement next time.

But yes, there is a way to determine the actual hashrate: mine for 24 hours and then recursively iterate the number of coins received versus the "average difficulty over the last 24 hours" on the calculators at, e.g., minethecoin.com, to find the hashrate.

But if you know of a better way I'd love to hear it.

[Vann]

Except the number of coins you receive is not just dependent on your hash rate. It also depends on the difficulty and the luck of pool, both of which can vary greatly over any given 24 hour period. It my experience, Bminer is ~3% faster compared to DSTM's miner. This is going by the reported hash rate and the average 24 hour hash rate graph reported on Flypool, which shows the effective hash rate is somewhat higher when using Bminer compared to using DSTM in the same 24 hour period.

[MagicSmoker]

Except the number of coins you receive is not just dependent on your hash rate. It also depends on the difficulty and the luck of pool, both of which can vary greatly over any given 24 hour period.

Yes, I addressed the concern in bold by using a calculator that applies the average hashrate for the last 24 hours... It would be hopeless to try to calculate that yourself as difficulty changes on a moment by moment basis.

As for pool luck, that is another reason why the test should be run for 24 hours, but if the pool is finding less than a couple blocks per day then even that length of time will be insufficient for a fair evaluation of miner performance. The only solution I know of for that is to do the testing on a pool with a much higher total hashrate/that finds blocks more often; at least 1 per hour, preferably 1 every few minutes.

[stash2coin]

Happy new year!

4.0.0 is released. Thanks everyone for the feedback.

There are quite a bit of improvements in this release:

• Minor performance improvement.
• Support older CPUs like Core 2 Duo.
• Support mining rigs that have more than 8 GPUs.
• Support luckpool.org.
• Removed the polling option.
• Introduced the option `-max-network-failures` which allows Bminer to exit after consecutive network failures.
• Various improvement on the UI.
• Localization for Russian and Chinese.

Happy mining!

Can confirm the miner is now working with 12 cards rig, the CPU load is about the same as EWBF, good job.