Topic: [ANN]Bminer: a fast Equihash/Ethash/Cuckaroo29z miner for AMD/NVIDIA GPUs 16.4.9 - page 124. (Read 148347 times)

I don't need to post dumb questions on this forum because I use reddit and I did my own research before making mining rigs when I built them months ago. It's also wrong to say both my posts are praising Bminer, my first post was simply asking for Acrefawn to add bminer support to his watchdog script and thanking him for being responsive when I donated for the premium version. Laughable assumption to think this forum is the only source of information and nobody can own mining rigs without asking stupid questions here.

I did however end up switching back to DSTM for now though since I decided an extra 1-2% hash rate isn't really worth the risks of using a somewhat shady miner.

Ok, this is fu**ing ridiculous ... you need to remove that shady private connection to your website:


Your server went down and the miner stopped mining. This is seriously not cool. Besides being shady AF, you are also costing us money. My miners just wasted 1h ...

Find a way to remove this shady and ridiculous private connection. Otherwise, EVERYONE SHOULD STAY AWAY FROM THIS MINER! Your rigs can go down whenever @realbminer wishes, or when his server goes down, etc.

// Yes, my internet connection was solid when this was happening.

Thanks

5.4.0 has released.

• Fix a reconnection issue in the network layer.
• Show additional statistics in console.
• Allow cross-domain requests to access the API.
• Fix the compatibility issue with docker.
• Introduce the option -share-check to make the time of recovering from no accepted shares configurable.

Happy mining!

What you're experiencing is the (bad) nvidia driver allocating GPUs. That's not bminer's fault (you can start any gpu app and you'll see the same). That delay is particularly long in Linux, but I don't believe you when you say it's 2-4 minutes. I use G3930 systems too and the delay is 80-90 seconds with 13 GPUs.

Your other connectivity issues can't be the miner's fault. The pool or your own connection happened to have issues.

Regarding the other posts: I'm still a amused by the trust people put in tests done with a single card ...

I don't defend bminer - the developer is way too shady, sorry (see here) - but some things are unrelated and can be explained.

About 12 hours into my informal evaluation of zhash.pro and both the first payout rolled in as predicted while average hashrate reported at the pool - with difficulty fixed at 8192 - has remained steady at about 1860 Sols/s. So far, so good, then. Ping time isn't the lowest for me - 137ms average - but doesn't seem to be an issue with the difficulty vs. hashrate I am running.

I've already tested this, you can read it in message if you read it properly unfortunately it still doesn't work. I have to use watchdog=false because on systems with 8+ gpus you cannot run this miner properly, because the cpu usage in the beginning is too high - first 2-4 min that the miner needs to initialize it self to max speed,...then the cpu lowers to normal state 40-60% on low cost G3930. I've reported this bug already and few others too.

Now what's even more bizarre regarding this connectivity issue:
- yesterday: half of the mining farm was still working with bminer properly, the other half still had connection issues, so i switched back to ewbf with problematic rigs
- today: even the other half couldn't connect,...so switching back to ewbf/dstm permanently until this issue is properly addressed.

I'm also getting these too often:


I don't get it for all my miners, but most of them are getting it at some point ... what exactly does that mean?

... and then there's this, again, pretty often:

After some testing, I can confirm that bminer is definitely computing more invalid solutions than ewbf and dstm. These are not stales, but actually invalid:


I get stales too:

Hello,

How to get the previous version? 5.3.0 always crash on my machine.

Thanks for advance.

I just switched over to it but 2 things I'm noticing. 1) even though I put in the slushpool stratum server URL in the miner.bat file, when it starts it immediately connects to "zec-eu1.nanopool.org:6666" and 2) my rate monitoring on slushpool is not changing at all.

I realize there's a dev fee baked in, but how long does that mine actively for the dev and when will it actually start mining to my pool/wallet settings?

Here's the connection line from the beginning of the logfile:
[INFO] [2018-02-11T22:34:42-05:00] Connected to zec-eu1.nanopool.org:6666

My config (with address removed):
SET ADDRESS=MYZCASHADDRESS

SET USERNAME=%ADDRESS%.w

SET POOL=sec.slushpool.com:4444

SET SCHEME=stratum

START "Bminer: When Crypto-mining Made Fast" bminer.exe -uri %SCHEME%://%USERNAME%@%POOL% -api 127.0.0.1:1880 -logfile

any help/info would be appreciated.

And yes, I did google for this but didn't find much...

After readings 41 pages of posts, I have decide to not use bminer and go back to dstm 0.5.8 for the following reasons:

1. The management API does not include pool information.  I change pools from time to time based on profit/difficulty.  I have a app that monitors the management API and reminds me which coin I am mining.  Every other mining software I have encountered includes this.  Not knowing what coin I am mining is a deal breaker.

2. There is a private connection to bmine every 10-15 minutes.  Too often, unknown, closed source.  This a major security risk for me.  I could spent the time to hack into this.  But there is not point until #1 is addressed.

3. The actual hashrate is in question.  The tests so far all have some minor flaws to be conclusive.  I not blaming the person doing the test.  It just doesn't hold up to statistical rigor.  I could devise and run a test that will provide evident supporting my claims (including margin of error), but no point for me until #1 is addressed.

4. 2% devfee seems high.  A 1% to 1.5% would be more enticing.  But if I was inclined to investigate #2, I would also do a man-in-the-middle attack and redirect the devfee to my wallet  .  I have no interest in doing this.  But there is a difference between supporting the devs and being raped by them.

5. To many newbies posting here (including myself) makes it fell like a scam.  Hey, Spiralx, what do you call a person who buys a 7x1070 Ti and a 6x1060 (3gb) rig, never posts anything about "what to mine?", "what software to use?", "how to make a wallet work?", no support questions, no opinions about coins/hardware, an instant expert on his large hardware investment, then makes only 2 posts?  Oh yeah, both posts are praising biminer?

so does ---nofee work in bminer? or does a cut still go to the dev?

should i switch to dstm? and is its 2% fee non removable?

Hey realbminer,

I believe there is a minor bug in bminer.
It seems when running under linux with IPv4 and IPv6 installed, the API starts only on IPv6.
This seems to occur when the '-api' parameter is set to '-api 0.0.0.0:1880'.
This rig was freshly installed with a minimal version of ubuntu 16.04.3.
I've also experienced the same issue on other versions of linux including CentOS.

I CAN access it via IPv6, however, the availability of IPv6 on some other machines is limited in my environment AND, going forward there are some API connections I'd like to use that would need IPv4 compatibility.


Before anyone starts in on me about opening the API access, I require access to the API on the local network. It's well protected.

Oh, I also have a request: Please add the device name for each device on the default API webpage. When there are multiple types of GPUs it can be difficult to tell what type each is. Especially with many rigs.

Thank you for your time and work.

Why are you using 'max-network-failures 5' & 'watchdog=false'? Shouldn't you leave it at the default so it will continue to try to recover the connection, especially if you are complaining of a bug saying it's not connecting?

The documentation on bminer.me states:

Interesting... I had more or less the same experience with vast underpayment with them, too, despite them finding blocks fairly consistently. I've learned to not trust any pool that doesn't charge a fee.

About 20 minutes ago I pointed a rig at http://zhash.pro/ to try them out. Although you have convinced me to mine some ZEC at Flypool - which has, indeed, proven to be very trustworthy - I still want to mainly mine ZEN. Hopefully Zcash.pro doesn't disappoint.

To anyone still mining on zenmine.pro, you are getting scammed (that 0% fee is fooling a lot of people) ... https://bitcointalksearch.org/topic/be-careful-with-zenminepro-the-pool-has-payment-issues-not-the-first-time-2750121

I experienced the exact same issue and reported about it a few pages back. Pretty much the worst bug imaginable for a miner, in my opinion.

I certainly do not get these speeds on my GTX 1060's

• 315-325 Sol/s on GTX 1060

I get 285 around there, what am i missing.

@realbminer

Today there was a problem with the zenmine.pro mining pool,...don't know what was up but after investigating I've found out that bminer still has some sort of connection problems...see the picture below,...all this time the GPU was at full load,...although it didn't had a proper connection to the pool and I couldn't see it on the minning pool. Then I've switched to ewbf/dstm, both miners connected immediately and are working properly?

I use following in a batch file:
I've tried without SSL connection to the pool, and the result was the same. Everything that's written in a console is written also in a log file,...so nothing new can be obtained from the log file.



This is a huge issue! I've lost at least half of the hashrate because of this bug.