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

[mrpcrp2]

good miner for no more than 3 gpu rigs
if cards more than 3 in rig , gpu utilization fall down less 30% even though powerfull cpu (i3 , i5)
win7x64 , 417.35 , 8Gb RAM , 82 Gb swap

[1713935765]

1713935765

[1713935765]

1713935765

[1713935765]

1713935765

[Derloda]

I tried on leafpool. Login to pool successful, but then messages like
[ERRO] [2019-01-08T20:36:13+01:00] Failed to parse the response: %!s(*stratum.RawIncomingMessage=0xc042152dd0), error: json: cannot unmarshal number -22 into Go struct field .code of type uint
[ERRO] [2019-01-08T20:36:16+01:00] Failed to parse the response: %!s(*stratum.RawIncomingMessage=0xc0421767d0), error: json: cannot unmarshal number -22 into Go struct field .code of type uint
[ERRO] [2019-01-08T20:36:16+01:00] Failed to parse the response: %!s(*stratum.RawIncomingMessage=0xc042152e80), error: json: cannot unmarshal number -22 into Go struct field .code of type uint

cannot unmarshal number -22 into Go struct field .code of type uint

forever

I tried it with just worker and and with worker name and email while replacing @ and / with corresponding special characters in URI format

Hi evlo, sorry that Bminer didn't support leaf pool at this moment.
Bminer supports Sparkpool and beepool already, please use other pools instead first.

when support for Leaf?

Would like to see leaf support too

[cryptoyes]

good miner for no more than 3 gpu rigs
if cards more than 3 in rig , gpu utilization fall down less 30% even though powerfull cpu (i3 , i5)
win7x64 , 417.35 , 8Gb RAM , 82 Gb swap

Exactly my findings too. This miner is relying too much on the CPU which becomes the bottleneck and can't handle more interrupt requests to GPUs ... he seems to be trying to improve this, and said v12.2.0 optimized cpu usage but i found no improvement for my 13 gpu rigs.

[arielbit]

good miner for no more than 3 gpu rigs
if cards more than 3 in rig , gpu utilization fall down less 30% even though powerfull cpu (i3 , i5)
win7x64 , 417.35 , 8Gb RAM , 82 Gb swap

Exactly my findings too. This miner is relying too much on the CPU which becomes the bottleneck and can't handle more interrupt requests to GPUs ... he seems to be trying to improve this, and said v12.2.0 optimized cpu usage but i found no improvement for my 13 gpu rigs.

note: 1080ti only (3 card rigs)

i'm a 4 gpu per rig miner so migrating to 3 gpu is quite easy...assembling a 3 gpu rig and taking a gpu from other rigs makes me 4 rigs (of 3 gpus) hehe..

now, cpu observation, same settings.. q8400, q9400 and anything around that generation gives 15.x G/s, starting from AMD x3 720, x4 960T to fx 6300 can give around 16.x G/s and i7 8700k rig gives 17.x G/s

can mine at 4gb ram, 33gb page file in windows 7.

i remember back when ethminer was still the miner i'm using until claymore makes an ETH miner and continue to optimize it i noticed that my rig with a e8400 cpu has a bit lower hash rate than my q9000 series rigs even when the miner claymore made was already optimized, i replaced the cpu and hashrate increased.

[GEBucky]

I am getting 1% or less rejects on f2pool with 3 1080ti rig. CPU usage is about 40pct on both cores: CPU Type   DualCore Intel Pentium G4400T, 2900 MHz (29 x 100). Have 12GB RAM and 30GB Virtual Memory on Windows 10. GPU utilization is 99pct on all 3.

Note that if anyone is going through MRR as a proxy you are going to get high rejects on grinmint - need to use f2pool it that's how you are configured.

[obm_dan]

Support for bminer 12.2.0 has been added to Foreman. Now you can monitor your miners remotely and see exactly what you’re making - no wallet addresses needed.  

[erdnapa]

^ yes , I also have more reject on eu grinmint server, than on chineese f2pool. And I am from eu
I also have very low hash on spark with 12.1, did not try this new 12.2 version on spark yet. NBminer works perfect on spark 0% rejects

It should be fixed in 12.2.0. I should have be more specific on the release notes. :-)

Same here high # of rejects, but running 12.2.0:

Code:

Rejected share #0 ({"code":-32502,"message":"Failed to validate solution"}) 

[NCarter84]

When will we be able to use 4gb cards?

[realbminer]

^ yes , I also have more reject on eu grinmint server, than on chineese f2pool. And I am from eu
I also have very low hash on spark with 12.1, did not try this new 12.2 version on spark yet. NBminer works perfect on spark 0% rejects

It should be fixed in 12.2.0. I should have be more specific on the release notes. :-)

Same here high # of rejects, but running 12.2.0:

Code:

Rejected share #0 ({"code":-32502,"message":"Failed to validate solution"}) 

I just ran for a brief moments:

Code:

[INFO] [2019-01-21T12:19:28+08:00] [GPU 0] Speed: 6.19 G/s Temp: 72C Fan: 72% Power: 222W 0.03 G/J
[INFO] [2019-01-21T12:19:28+08:00] [GPU 1] Speed: 3.77 G/s Temp: 66C Fan: 43% Power: 136W 0.03 G/J
[INFO] [2019-01-21T12:19:29+08:00] [GPU 2] Speed: 2.50 G/s Temp: 62C Fan: 53% Power: 84W 0.03 G/J
[INFO] [2019-01-21T12:19:33+08:00] Accepted share
[INFO] [2019-01-21T12:19:34+08:00] Accepted share
[INFO] [2019-01-21T12:19:40+08:00] Received new job 1
[INFO] [2019-01-21T12:19:42+08:00] Accepted share
[INFO] [2019-01-21T12:19:49+08:00] Total 12.45 G/s Accepted shares 40 Rejected shares 3

The rejected share issue should be gone now. The message of failed to validate solution is because the pool has form a new job before the shares from the miner arrive. It's expected but it will be nice to have a better message.

[erdnapa]

Its 6.9% for me. 514 out of 7443.
You also have 3 out of 40, 7.5%.
I would still consider those numbers quite high, no?

^ yes , I also have more reject on eu grinmint server, than on chineese f2pool. And I am from eu
I also have very low hash on spark with 12.1, did not try this new 12.2 version on spark yet. NBminer works perfect on spark 0% rejects

It should be fixed in 12.2.0. I should have be more specific on the release notes. :-)

Same here high # of rejects, but running 12.2.0:

Code:

Rejected share #0 ({"code":-32502,"message":"Failed to validate solution"}) 

I just ran for a brief moments:

Code:

[INFO] [2019-01-21T12:19:28+08:00] [GPU 0] Speed: 6.19 G/s Temp: 72C Fan: 72% Power: 222W 0.03 G/J
[INFO] [2019-01-21T12:19:28+08:00] [GPU 1] Speed: 3.77 G/s Temp: 66C Fan: 43% Power: 136W 0.03 G/J
[INFO] [2019-01-21T12:19:29+08:00] [GPU 2] Speed: 2.50 G/s Temp: 62C Fan: 53% Power: 84W 0.03 G/J
[INFO] [2019-01-21T12:19:33+08:00] Accepted share
[INFO] [2019-01-21T12:19:34+08:00] Accepted share
[INFO] [2019-01-21T12:19:40+08:00] Received new job 1
[INFO] [2019-01-21T12:19:42+08:00] Accepted share
[INFO] [2019-01-21T12:19:49+08:00] Total 12.45 G/s Accepted shares 40 Rejected shares 3

The rejected share issue should be gone now. The message of failed to validate solution is because the pool has form a new job before the shares from the miner arrive. It's expected but it will be nice to have a better message.

[logitech69]

BTW if you are using bminer on windows, on grinmint pool DO NOT format your bat file as follows:

Code:

%SCHEME%://sample@this.com.worker@%POOL%

doing this will create a new dashboard for you on grinmint under the email sample@this.com.worker
you can search for this email in the dashboard search box. using a syntax like this will not show under sample@this.com with a worker named "worker"

You can probably omit the worker and password and it will just show under your email as "default" worker. I was trying but grinmint is down right now so I havent tested it. I tried email/worker and that didnt show under my dashboard either. I'm still trying to find the correct syntax for grinmint.

also on grinmint you dont need to include the password when mining and it is highly suggested you do NOT because bminer uses an unencrypted port

so no password is safer? please explain...

[fistsofgod]

BTW if you are using bminer on windows, on grinmint pool DO NOT format your bat file as follows:

Code:

%SCHEME%://sample@this.com.worker@%POOL%

doing this will create a new dashboard for you on grinmint under the email sample@this.com.worker
you can search for this email in the dashboard search box. using a syntax like this will not show under sample@this.com with a worker named "worker"

You can probably omit the worker and password and it will just show under your email as "default" worker. I was trying but grinmint is down right now so I havent tested it. I tried email/worker and that didnt show under my dashboard either. I'm still trying to find the correct syntax for grinmint.

also on grinmint you dont need to include the password when mining and it is highly suggested you do NOT because bminer uses an unencrypted port

so no password is safer? please explain...

you only need to send the password the first time, to create your account. after the first connection you can then remove the password from config file.

the way grinmint works you never actually HAVE to have a password established for your email you use in the config, though you should for security and is accomplished on your first connection per email used.

[realbminer]

Its 6.9% for me. 514 out of 7443.
You also have 3 out of 40, 7.5%.
I would still consider those numbers quite high, no?

^ yes , I also have more reject on eu grinmint server, than on chineese f2pool. And I am from eu
I also have very low hash on spark with 12.1, did not try this new 12.2 version on spark yet. NBminer works perfect on spark 0% rejects

It should be fixed in 12.2.0. I should have be more specific on the release notes. :-)

Same here high # of rejects, but running 12.2.0:

Code:

Rejected share #0 ({"code":-32502,"message":"Failed to validate solution"}) 

I just ran for a brief moments:

Code:

[INFO] [2019-01-21T12:19:28+08:00] [GPU 0] Speed: 6.19 G/s Temp: 72C Fan: 72% Power: 222W 0.03 G/J
[INFO] [2019-01-21T12:19:28+08:00] [GPU 1] Speed: 3.77 G/s Temp: 66C Fan: 43% Power: 136W 0.03 G/J
[INFO] [2019-01-21T12:19:29+08:00] [GPU 2] Speed: 2.50 G/s Temp: 62C Fan: 53% Power: 84W 0.03 G/J
[INFO] [2019-01-21T12:19:33+08:00] Accepted share
[INFO] [2019-01-21T12:19:34+08:00] Accepted share
[INFO] [2019-01-21T12:19:40+08:00] Received new job 1
[INFO] [2019-01-21T12:19:42+08:00] Accepted share
[INFO] [2019-01-21T12:19:49+08:00] Total 12.45 G/s Accepted shares 40 Rejected shares 3

The rejected share issue should be gone now. The message of failed to validate solution is because the pool has form a new job before the shares from the miner arrive. It's expected but it will be nice to have a better message.

interesting..let me run a little bit longer and see what I can find.

[cryptoyes]

beam:// is still not supported ...

Code:

bminer -uri beam://<wallet>.worker%2Fbill.gates%40microsoft.com:x@beam-eu.leafpool.com:3333

invalid value "beam://<wallet>.worker%2Fbill.gates%40microsoft.com:x@beam-eu.leafpool.com:3333" for flag -uri: Unsupported scheme
Bminer: When Crypto-mining Made Fast (v12.2.0-937f19b)

beam+ssl:// seems to only work on sparkpool ...

Code:

bminer -uri beam+ssl://<wallet>.worker%2Fbill.gates%40microsoft.com:x@beam-eu.leafpool.com:3333

[ERRO] [2019-01-21T16:34:02+02:00] Failed to parse the response: %!s(*stratum.RawIncomingMessage=0xc420281440), error: json: cannot unmarshal number -22 into Go struct field .code of type uint
[ERRO] [2019-01-21T16:34:03+02:00] Failed to parse the response: %!s(*stratum.RawIncomingMessage=0xc420281540), error: json: cannot unmarshal number -22 into Go struct field .code of type uint

Do you have a special deal with sparkpool or what? This has been reported a long time ago and you released 3 new versions since then ... feels like you are ignoring it, and the fact that it only works on sparkpool feels like sparkpool is hardcoded. Disappointing.

[sprstoner]

Is there a way to setup Bminer with Sparkpool on Grin.
Miner is runing and shares are accepted but there is no worker on the pool.
I think it is because of the mail address, it is messing with syntax of miner.
I have tried to escape it like in the manual but worker still not showing up at the pool.
Any suggestion?

I noticed that if you connect the miner to the Sparkpool using youremail@mail.com.rigname then you need to input youremail@mail.com.rigname in the worker field to see the stats, not sure if that is the right way doh

EDIT: I checked the guide on Sparkpool and they changed the form of bminer setup  https://support.sparkpool.com/hc/en-us/articles/360015730673-Configuration-for-Bminer

EDIT2: Don't know why they put %% between username (email) and worker name ?! Bminer just stops working like that

https://i.imgur.com/25iL2Jh.jpg

this is working on grinmint too, thanks!

[dk702]

^ yes , I also have more reject on eu grinmint server, than on chineese f2pool. And I am from eu
I also have very low hash on spark with 12.1, did not try this new 12.2 version on spark yet. NBminer works perfect on spark 0% rejects

It should be fixed in 12.2.0. I should have be more specific on the release notes. :-)

Will C31 ever be supported?

[cost82el]

no c31 for win...read this https://www.daz3d.com/forums/discussion/120541/windows-10-reserving-vram-links-to-posts-at-microsoft-forum
On Windows 10 systems 2.0 GB of VRAM of 11 GB cards is not available for rendering tasks
windows sucks

[realbminer]

lots of "share rejected due to low difficulty"

11 accepted 24 rejected

testing grin on win7 12.1.0

if it is happen when you test on grinmint pool, this problem should have been fixed in Bminer 12.2.0, please try and let me know if it works.
https://bminer.me/releases/

it works on grinmint, 130 accepted - 8 rejected

How do you format the -uri with the email address?

SET ADDRESS=mail@mail.com
SET USERNAME=%ADDRESS%

all workers are displayed as "default"

https://medium.com/@realbminer/bminer-grin-mining-on-grinmint-pool-f0e3d160e260
I have updated the tutorial today, you can specify the worker name on grin mint pool by following it.

[cryptoyes]

The rejected share issue should be gone now. The message of failed to validate solution is because the pool has form a new job before the shares from the miner arrive. It's expected but it will be nice to have a better message.

That can't be true, because running 12.0.1 gets no rejects in the middle of a job (only at the same time of a new job) whereas 12.1.0 and 12.2.0 have tons of rejects right int he middle of jobs. About 2% difference in rejected share between the two, consistently. Mining on f2pool.

[HeueysaJuaust]

12.2.0    %15 reject shares.