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

bigjee

full member

Activity: 434

Merit: 107

Quote from: realbminer on January 09, 2018, 04:15:52 AM

Thanks everybody for the feedback. The 5.0.0 version has been released:

Minor performance improvement for GTX 1060.
Fixed performance regressions in 4.0.0 on Windows.
Optimization on the networking layer.
Show GPU ID in case of hardware errors.
Introduced the option -no-timestamps which suppresses the timestamps in the logging messages.

Happy mining!

You should probably put the Version number in the subject of this thread so ppl know easily when you update your miner.
e.g. [ANN] Bminer (v5.0): a fast Equihash miner for CUDA GPUs

That way ppl wont have to look at page 1 or 13 everytime to figure out if there's been an update.

Good job on bringing new versions I havent tested it yet but the last one didnt work for me. Will do so over the weekend.

hav

newbie

Activity: 16

Merit: 0

Code:

[INFO] [2018-01-09T17:18:26+01:00] Set target to 918387dad1e468f570415ac397d96646bae0ad99dbe78033de028099e46e0700
[INFO] [2018-01-09T17:18:26+01:00] Received new job 39
[INFO] [2018-01-09T17:18:26+01:00] Accepted share #192
[INFO] [2018-01-09T17:18:26+01:00] Accepted share #193
[INFO] [2018-01-09T17:18:26+01:00] Accepted share #194
[INFO] [2018-01-09T17:18:26+01:00] Accepted share #195
[INFO] [2018-01-09T17:18:26+01:00] Accepted share #196
[INFO] [2018-01-09T17:18:26+01:00] Accepted share #197
[INFO] [2018-01-09T17:18:26+01:00] Accepted share #198
[INFO] [2018-01-09T17:18:26+01:00] Set target to 54734c9f97375c7b0eb318eb75223b511137db8943bb58ec157d4becf5f30000
[INFO] [2018-01-09T17:18:26+01:00] Received new job 3a
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #199 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #200 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #201 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #202 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #203 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #204 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #205 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #206 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #207 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #208 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #209 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #210 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #211 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #212 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #213 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Rejected share #214 ([21,"job not found"])
[WARN] [2018-01-09T17:18:26+01:00] Get error: Too many rejected shares, resetting in 5 seconds
[WARN] [2018-01-09T17:18:31+01:00] Connection failed due to End of file, retrying in 5 seconds
[INFO] [2018-01-09T17:18:31+01:00] Connected to zen.suprnova.cc:3618
[INFO] [2018-01-09T17:18:36+01:00] Subscribed to stratum server
[INFO] [2018-01-09T17:18:36+01:00] Set nonce to 5e39000000000000000000000000395f
[INFO] [2018-01-09T17:18:36+01:00] Set target to 0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f00
[INFO] [2018-01-09T17:18:36+01:00] Received new job 3e
[WARN] [2018-01-09T17:18:36+01:00] Get error: A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied., resetting in 5 seconds 
[INFO] [2018-01-09T17:18:36+01:00] Connected to zen.suprnova.cc:3618
[INFO] [2018-01-09T17:18:41+01:00] Subscribed to stratum server
[INFO] [2018-01-09T17:18:41+01:00] Set nonce to e40a0008000000000000000008000ae5
[INFO] [2018-01-09T17:18:41+01:00] Set target to 0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f00
[INFO] [2018-01-09T17:18:41+01:00] Received new job 3e
[WARN] [2018-01-09T17:18:41+01:00] Rejected share #349 ([24,"unauthorized worker",null])
[WARN] [2018-01-09T17:18:41+01:00] Get error: A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied., resetting in 5 seconds 
[INFO] [2018-01-09T17:18:41+01:00] Connected to zen.suprnova.cc:3618
[INFO] [2018-01-09T17:18:46+01:00] Subscribed to stratum server
[INFO] [2018-01-09T17:18:46+01:00] Set nonce to d6ceff47000000000000000047ffced5
[INFO] [2018-01-09T17:18:46+01:00] Set target to 0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f00
[INFO] [2018-01-09T17:18:46+01:00] Received new job 3e
[WARN] [2018-01-09T17:18:46+01:00] Get error: A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied., resetting in 5 seconds 
[INFO] [2018-01-09T17:18:46+01:00] Connected to zen.suprnova.cc:3618

It happened again, any idea what this could be?

wetblanket

jr. member

Activity: 95

Merit: 2

Quote from: NameTaken on January 09, 2018, 11:15:11 AM

Quote from: wetblanket on January 09, 2018, 11:04:13 AM

Quote from: NameTaken on January 09, 2018, 10:43:18 AM

Code:

$ sudo systemctl reboot --force

like I mentioned?

https://bitcointalksearch.org/topic/miner-process-wont-exit-rig-wont-reboot-2693128

No, I didn't. The description of what it does scares me (re: filesystems, etc). Isn't there a possibility of system breakage?

Quote

When used with halt, poweroff, reboot or kexec, execute the selected operation without shutting down all units. However, all processes will be killed forcibly and all file systems are unmounted or remounted read-only. This is hence a drastic but relatively safe option to request an immediate reboot.

Quote

If --force is specified twice for these operations (with the exception of kexec), they will be executed immediately, without terminating any processes or unmounting any file systems. Warning: specifying --force twice with any of these operations might result in data loss.

Apologies! I obviously didn't read that closely enough. Thanks for taking the time to educate me... again!

sir_blacks

jr. member

Activity: 119

Merit: 3

@realbminer

I seen agen 4 permanent network connection done by bminer
1. Api = OK
2. Poll what is mine = OK
3. bminer.exe XXX.ip-79-137-XX.eu 6633 ESTABLISHED = ?!?!
4. bminer.exe XXX.31.69.XXX https ESTABLISHED = Huh

3 or 4 it suppose to be dev fee, BUT way 2 address ?!?!?! in version 3 was only 1 from 4 & 5 it came with 2 ?!??!?!

Quote from: Gelbstich on January 09, 2018, 10:59:20 AM

How do I have to write it in the .bat file if I want to enter the following (that's how you write in EWBF):
miner --server zen.2miners.com --port 7070 --user YOUR_ADDRESS.RIG_ID --pass x --eexit 3 --pec --fee 0

I don't know how to write the

Code:

--pass x --eexit 3 --pec --fee 0

part in the .bat file so bminer is able to read it correctly. Can anyone help me please?

bminer -devices 0 (card what you want to use) -uri stratum://wallet(or username).worker:pass@webpooladress:port -api 127.0.0.1:1880

look here for more details https://www.bminer.me/examples/

cheers

NameTaken

hero member

Activity: 630

Merit: 502

Quote from: wetblanket on January 09, 2018, 11:04:13 AM

Quote from: NameTaken on January 09, 2018, 10:43:18 AM

Quote from: wetblanket on January 09, 2018, 10:40:44 AM

Sorry if you saw my edit you'd see this causes trouble with reboots (have to do a hard power down/up via power button). Am mining on zcl suprnova.cc, ubuntu 16.04, this was with bminer 4.0.0.

Did you try

Code:

$ sudo systemctl reboot --force

like I mentioned?

https://bitcointalksearch.org/topic/miner-process-wont-exit-rig-wont-reboot-2693128

No, I didn't. The description of what it does scares me (re: filesystems, etc). Isn't there a possibility of system breakage?

Quote

When used with halt, poweroff, reboot or kexec, execute the selected operation without shutting down all units. However, all processes will be killed forcibly and all file systems are unmounted or remounted read-only. This is hence a drastic but relatively safe option to request an immediate reboot.

Quote

If --force is specified twice for these operations (with the exception of kexec), they will be executed immediately, without terminating any processes or unmounting any file systems. Warning: specifying --force twice with any of these operations might result in data loss.

The warning is only for if you use --force twice.

wetblanket

jr. member

Activity: 95

Merit: 2

Quote from: NameTaken on January 09, 2018, 10:43:18 AM

Quote from: wetblanket on January 09, 2018, 10:40:44 AM

Sorry if you saw my edit you'd see this causes trouble with reboots (have to do a hard power down/up via power button). Am mining on zcl suprnova.cc, ubuntu 16.04, this was with bminer 4.0.0.

Did you try

Code:

$ sudo systemctl reboot --force

like I mentioned?

https://bitcointalksearch.org/topic/miner-process-wont-exit-rig-wont-reboot-2693128

No, I didn't. The description of what it does scares me (re: filesystems, etc). Isn't there a possibility of system breakage?

Gelbstich

hero member

Activity: 562

Merit: 509

How do I have to write it in the .bat file if I want to enter the following (that's how you write in EWBF):
miner --server zen.2miners.com --port 7070 --user YOUR_ADDRESS.RIG_ID --pass x --eexit 3 --pec --fee 0

I don't know how to write the

Code:

--pass x --eexit 3 --pec --fee 0

part in the .bat file so bminer is able to read it correctly. Can anyone help me please?

NameTaken

hero member

Activity: 630

Merit: 502

wetblanket

jr. member

Activity: 95

Merit: 2

hav

newbie

Activity: 16

Merit: 0

https://imgur.com/NIvAdWq
after some time the miner just hangs and submits no shares...
Could this be a dev share issue?
It's not transparant how this happens.

I'm mining zencash on suprnova.

hav

newbie

Activity: 16

Merit: 0

wetblanket

jr. member

Activity: 95

Merit: 2

EDIT: Note that when this happens, I have to reboot the rig via the power button; `sudo reboot` just causes the machine to hang.

bminer has been chugging along for a couple of days now, but this morning I woke up to see the following. Any tips?

Code:

[INFO] [2018-01-09T02:17:56-08:00] [GPU 0] Speed: 508.98 Sol/s 272.31 Nonce/s
[INFO] [2018-01-09T02:17:56-08:00] [GPU 1] Speed: 508.21 Sol/s 272.46 Nonce/s
[INFO] [2018-01-09T02:17:57-08:00] [GPU 2] Speed: 502.58 Sol/s 269.03 Nonce/s
[INFO] [2018-01-09T02:17:57-08:00] [GPU 3] Speed: 505.43 Sol/s 269.04 Nonce/s
[INFO] [2018-01-09T02:17:58-08:00] [GPU 4] Speed: 504.83 Sol/s 270.48 Nonce/s
[INFO] [2018-01-09T02:17:59-08:00] [GPU 5] Speed: 506.09 Sol/s 271.16 Nonce/s
[INFO] [2018-01-09T02:18:02-08:00] Accepted share #18630
[INFO] [2018-01-09T02:18:02-08:00] Accepted share #18631
[WARN] [2018-01-09T02:18:04-08:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-01-09T02:18:10-08:00] Connected to zcl.suprnova.cc:4042
[INFO] [2018-01-09T02:18:10-08:00] Subscribed to stratum server
[INFO] [2018-01-09T02:18:10-08:00] Set nonce to e80000400000000000000000400000e9
[INFO] [2018-01-09T02:18:10-08:00] Set target to 0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f00
[INFO] [2018-01-09T02:18:10-08:00] Received new job 1
[INFO] [2018-01-09T02:18:10-08:00] Authorized
[INFO] [2018-01-09T02:18:11-08:00] Accepted share #18632
[INFO] [2018-01-09T02:18:12-08:00] Accepted share #18633
[INFO] [2018-01-09T02:18:13-08:00] Accepted share #18634
[WARN] [2018-01-09T02:18:18-08:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-01-09T02:18:19-08:00] Total 3036.12 Sol/s 1624.48 Nonce/s Accepted shares 18556 Rejected shares 67
[INFO] [2018-01-09T02:18:23-08:00] Connected to zcl.suprnova.cc:4042
[INFO] [2018-01-09T02:18:24-08:00] Subscribed to stratum server
[INFO] [2018-01-09T02:18:24-08:00] Set nonce to f20100380000000000000000380001f3
[INFO] [2018-01-09T02:18:24-08:00] Set target to 0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f00
[INFO] [2018-01-09T02:18:24-08:00] Received new job 1
[INFO] [2018-01-09T02:18:24-08:00] Authorized
[INFO] [2018-01-09T02:18:24-08:00] Accepted share #18637
[WARN] [2018-01-09T02:18:25-08:00] Get error: End of file, resetting in 5 seconds
[INFO] [2018-01-09T02:18:26-08:00] [GPU 0] Speed: 507.86 Sol/s 272.23 Nonce/s
[INFO] [2018-01-09T02:18:26-08:00] [GPU 1] Speed: 509.26 Sol/s 272.34 Nonce/s
[INFO] [2018-01-09T02:18:27-08:00] [GPU 2] Speed: 502.05 Sol/s 268.92 Nonce/s
[INFO] [2018-01-09T02:18:27-08:00] [GPU 3] Speed: 507.34 Sol/s 269.16 Nonce/s
[INFO] [2018-01-09T02:18:28-08:00] [GPU 4] Speed: 506.18 Sol/s 270.44 Nonce/s
[INFO] [2018-01-09T02:18:29-08:00] [GPU 5] Speed: 508.35 Sol/s 271.12 Nonce/s
[WARN] [2018-01-09T02:18:30-08:00] Connection failed due to Broken pipe, retrying in 5 seconds
[INFO] [2018-01-09T02:18:31-08:00] Connected to zcl.suprnova.cc:4042
[INFO] [2018-01-09T02:18:35-08:00] Subscribed to stratum server
[INFO] [2018-01-09T02:18:35-08:00] Set nonce to b80700780000000000000000780007b9
[INFO] [2018-01-09T02:18:35-08:00] Set target to 0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f00
[INFO] [2018-01-09T02:18:35-08:00] Received new job 8a
[WARN] [2018-01-09T02:18:35-08:00] Get error: Bad file descriptor, resetting in 5 seconds
[INFO] [2018-01-09T02:18:36-08:00] Connected to zcl.suprnova.cc:4042
[INFO] [2018-01-09T02:18:40-08:00] Subscribed to stratum server
[INFO] [2018-01-09T02:18:40-08:00] Set nonce to 98f9ff17000000000000000017fff997
[INFO] [2018-01-09T02:18:40-08:00] Set target to 0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f00
[INFO] [2018-01-09T02:18:40-08:00] Received new job 7c
[INFO] [2018-01-09T02:18:40-08:00] Received new job 7d
[WARN] [2018-01-09T02:18:40-08:00] Rejected share #18641 ([24,"unauthorized worker",null])
[WARN] [2018-01-09T02:18:40-08:00] Rejected share #18642 ([24,"unauthorized worker",null])
[WARN] [2018-01-09T02:18:40-08:00] Rejected share #18643 ([24,"unauthorized worker",null])
[WARN] [2018-01-09T02:18:40-08:00] Get error: Bad file descriptor, resetting in 5 seconds
[INFO] [2018-01-09T02:18:41-08:00] Connected to zcl.suprnova.cc:4042
[INFO] [2018-01-09T02:18:45-08:00] Subscribed to stratum server
[INFO] [2018-01-09T02:18:45-08:00] Set nonce to ca0100680000000000000000680001cb
[INFO] [2018-01-09T02:18:45-08:00] Set target to 0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f00
[INFO] [2018-01-09T02:18:45-08:00] Received new job 1
[WARN] [2018-01-09T02:18:45-08:00] Rejected share #18644 ([24,"unauthorized worker",null])
[WARN] [2018-01-09T02:18:45-08:00] Rejected share #18645 ([24,"unauthorized worker",null])
[WARN] [2018-01-09T02:18:45-08:00] Rejected share #18646 ([24,"unauthorized worker",null])
[WARN] [2018-01-09T02:18:46-08:00] Miner died! It will be restarted soon...
[INFO] [2018-01-09T02:18:52-08:00] Bminer: When Crypto-mining Made Fast (v4.0.0-433ffb1)
[INFO] [2018-01-09T02:18:52-08:00] Checking updates
[INFO] [2018-01-09T02:18:52-08:00] Starting miner on devices [0 1 2 3 4 5]
[INFO] [2018-01-09T02:18:53-08:00] Starting miner on device 0...
[INFO] [2018-01-09T02:18:53-08:00] [D0] GPU check watchdog has started
[INFO] [2018-01-09T02:18:53-08:00] Connected to zcl.suprnova.cc:4042
[INFO] [2018-01-09T02:18:53-08:00] Started miner on device 0
[INFO] [2018-01-09T02:18:53-08:00] Subscribed to stratum server
[INFO] [2018-01-09T02:18:53-08:00] Set nonce to 9efbff6f00000000000000006ffffb9d
[INFO] [2018-01-09T02:18:53-08:00] Set target to 0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f0f00
[INFO] [2018-01-09T02:18:53-08:00] Received new job 1
[INFO] [2018-01-09T02:18:53-08:00] Starting miner on device 1...
[INFO] [2018-01-09T02:18:53-08:00] [D1] GPU check watchdog has started
[INFO] [2018-01-09T02:18:53-08:00] Authorized
[INFO] [2018-01-09T02:19:23-08:00] [GPU 0] Speed: 0.00 Sol/s 0.00 Nonce/s
[INFO] [2018-01-09T02:19:35-08:00] Received new job 2
[INFO] [2018-01-09T02:19:53-08:00] [GPU 0] Speed: 0.00 Sol/s 0.00 Nonce/s
[INFO] [2018-01-09T02:19:59-08:00] Received new job 3
[INFO] [2018-01-09T02:20:23-08:00] [GPU 0] Speed: 0.00 Sol/s 0.00 Nonce/s
[INFO] [2018-01-09T02:20:53-08:00] [GPU 0] Speed: 0.00 Sol/s 0.00 Nonce/s
[INFO] [2018-01-09T02:20:53-08:00] [GPU 0] Speed: 0.00 Sol/s 0.00 Nonce/s
[INFO] [2018-01-09T02:21:23-08:00] [GPU 0] Speed: 0.00 Sol/s 0.00 Nonce/s
[FATA] [2018-01-09T02:21:53-08:00] Irrecoverable errors from miner in GPU 0: GPU hang detected

NameTaken

hero member

Activity: 630

Merit: 502

Quote from: MagicSmoker on January 09, 2018, 09:28:14 AM

Quote from: Andrey09 on January 09, 2018, 09:12:41 AM

What faster Bminer 5.0 or DSTM 0.5.8 ? Someone make compare with data from pool ?

I was getting around 305 Sols/s per GTX 1060 3GB using dstm 0.5.7 (didn't try 0.5.8 because some people were reporting issues with it) and now with bminer 5.0 I am getting around 310 Sols/s per GPU, or 1.6% improvement. Modest, but worthwhile. Mind you, it's only been running for about 1 hour at this point.

The -no-timestamps switch is a step in the right direction, but I still want to see cumulative mining time.

Using systemd I can run

Code:

systemctl status bminer

to display uptime, status and logs while

Code:

systemctl show bminer

dumps all the details I could want

Code:

Type=simple
Restart=always
NotifyAccess=none
RestartUSec=10s
TimeoutStartUSec=1min 30s
TimeoutStopUSec=10s
RuntimeMaxUSec=infinity
WatchdogUSec=0
WatchdogTimestamp=mar 2018-01-09 02:46:22 PST
WatchdogTimestampMonotonic=291102220341
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=2891
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusErrno=0
Result=success
ExecMainStartTimestamp=mar 2018-01-09 02:46:22 PST
ExecMainStartTimestampMonotonic=291102220311
ExecMainExitTimestampMonotonic=0
ExecMainPID=2891
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/opt/bminer/bminer ; argv[]=/opt/bminer/bminer -no-timestamps -api=0.0.0.0:12345 -uri=stratum://nametaken.44388:[email protected]:50466 ; ignore_errors=no ; start_time=[mar 2018-01-09 02:46:22 PST] ; stop_time=[n/a] ; pid=2891 ; code=(null) ; status=0/0 }
ExecReload={ path=/bin/kill ; argv[]=/bin/kill -HUP $MAINPID ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/bminer.service
MemoryCurrent=18446744073709551615
CPUUsageNSec=18446744073709551615
TasksCurrent=18446744073709551615
Delegate=no
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=infinity
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
TasksAccounting=no
TasksMax=18446744073709551615
Environment=DISPLAY=:0
UMask=0022
LimitCPU=18446744073709551615
LimitCPUSoft=18446744073709551615
LimitFSIZE=18446744073709551615
LimitFSIZESoft=18446744073709551615
LimitDATA=18446744073709551615
LimitDATASoft=18446744073709551615
LimitSTACK=18446744073709551615
LimitSTACKSoft=8388608
LimitCORE=18446744073709551615
LimitCORESoft=0
LimitRSS=18446744073709551615
LimitRSSSoft=18446744073709551615
LimitNOFILE=4096
LimitNOFILESoft=1024
LimitAS=18446744073709551615
LimitASSoft=18446744073709551615
LimitNPROC=7286
LimitNPROCSoft=7286
LimitMEMLOCK=65536
LimitMEMLOCKSoft=65536
LimitLOCKS=18446744073709551615
LimitLOCKSSoft=18446744073709551615
LimitSIGPENDING=7286
LimitSIGPENDINGSoft=7286
LimitMSGQUEUE=819200
LimitMSGQUEUESoft=819200
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=18446744073709551615
LimitRTTIMESoft=18446744073709551615
OOMScoreAdjust=0
Nice=19
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SyslogLevel=6
SyslogFacility=3
SecureBits=0
CapabilityBoundingSet=18446744073709551615
AmbientCapabilities=0
User=1000
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
PrivateDevices=no
ProtectHome=yes
ProtectSystem=full
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
KillMode=mixed
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=bminer.service
Names=bminer.service
Requires=system.slice sysinit.target
Wants=lightdm.service network-online.target
WantedBy=multi-user.target
Conflicts=ccminer.service dstm.service shutdown.target ewbf.service optiminer.service
ConflictedBy=dstm.service
Before=shutdown.target multi-user.target
After=lightdm.service system.slice sysinit.target network-online.target systemd-journald.socket basic.target
Description=Bminer Service
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/etc/systemd/system/bminer.service
UnitFileState=enabled
UnitFilePreset=enabled
StateChangeTimestamp=mar 2018-01-09 02:46:22 PST
StateChangeTimestampMonotonic=291102220342
InactiveExitTimestamp=mar 2018-01-09 02:46:18 PST
InactiveExitTimestampMonotonic=291098705658
ActiveEnterTimestamp=mar 2018-01-09 02:46:22 PST
ActiveEnterTimestampMonotonic=291102220342
ActiveExitTimestamp=mar 2018-01-09 02:46:17 PST
ActiveExitTimestampMonotonic=291097348517
InactiveEnterTimestamp=mar 2018-01-09 02:46:18 PST
InactiveEnterTimestampMonotonic=291097980346
CanStart=yes
CanStop=yes
CanReload=yes
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
NeedDaemonReload=no
JobTimeoutUSec=infinity
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=mar 2018-01-09 02:46:18 PST
ConditionTimestampMonotonic=291098705207
AssertTimestamp=mar 2018-01-09 02:46:18 PST
AssertTimestampMonotonic=291098705207
Transient=no
StartLimitInterval=10000000
StartLimitBurst=5
StartLimitAction=none

MagicSmoker

full member

Activity: 420

Merit: 184

Quote from: Andrey09 on January 09, 2018, 09:12:41 AM

What faster Bminer 5.0 or DSTM 0.5.8 ? Someone make compare with data from pool ?

I was getting around 305 Sols/s per GTX 1060 3GB using dstm 0.5.7 (didn't try 0.5.8 because some people were reporting issues with it) and now with bminer 5.0 I am getting around 310 Sols/s per GPU, or 1.6% improvement. Modest, but worthwhile. Mind you, it's only been running for about 1 hour at this point.

The -no-timestamps switch is a step in the right direction, but I still want to see cumulative mining time.

hav

newbie

Activity: 16

Merit: 0

Quote from: Andrey09 on January 09, 2018, 09:12:41 AM

What faster Bminer 5.0 or DSTM 0.5.8 ? Someone make compare with data from pool ?

In my pool results, it's about 20% faster, as dstm doesn't handle more than 2-3 cards well.
Downside is that you have to keep an eye on Bminer as it can randomly stop submitting shares or suddenly have a bunch of invalid shares.

Andrey09

newbie

Activity: 176

Merit: 0

What faster Bminer 5.0 or DSTM 0.5.8 ? Someone make compare with data from pool ?

hav

newbie

Activity: 16

Merit: 0

reports the same sol/s as EWBF but suprnova shows me lots more hashes, i switched over.
Thanks !

EDIT:

in a 4x 1060 rig

248 shares comitted and 9 rejected

realbminer

member

Activity: 461

Merit: 49

Thanks everybody for the feedback. The 5.0.0 version has been released:

Minor performance improvement for GTX 1060.
Fixed performance regressions in 4.0.0 on Windows.
Optimization on the networking layer.
Show GPU ID in case of hardware errors.
Introduced the option -no-timestamps which suppresses the timestamps in the logging messages.

Happy mining!

fortyniner

newbie

Activity: 27

Merit: 0

Very nice. I'm getting 191 sol/s on a 4GB GeForce 1050ti @ 1885 core/3888 mem.

cryptoyes

member

Activity: 297

Merit: 10

Quote from: realbminer on January 06, 2018, 09:36:23 PM

Quote from: cryptoyes on January 05, 2018, 07:45:36 AM

I started using this miner and I like it. I have a big issue with it though: many times the error message does not state which GPU crashed, it just says "Unrecoverable errors" without identifying which GPU. DSTM is better in that regard, as it always states which GPU and hence allows me to fine tune overclocking in rigs with many GPUs. Could you please add clear GPU ids in the error messages to allow us to parse logs and automate other functions?

Also, with bminer I get errors that do not produce a Xid error in the kernel -- this is weird and it's the first time it happens. All other miners I used (for various coins) trigger a Xid error. It sounds like some crashes are in fact bminer's fault rather than the hardware or too much overclocking. I have no way of debugging it though being closed source.

I think the GPU id is available in the error message. The error message looks like "Irrecoverable errors from miner in GPU 0 ..."

The Xid error I have ever seen is due to hardware errors. Can you paste the error logs here?

bminer is tested extensively under Linux and I'm not aware of Xid errors that are caused by the miner itself. However, bminer does stretch the GPU a little bit more for even more hashrate, so if you overclock the GPU you might want to tune the parameters a little bit.

No, you do not specify the GPU id in all error messages. Here's an example:

Code:

[FATA] [2018-01-03T16:05:03Z] Fatal cuda error. Terminate soon...
[WARN] [2018-01-03T16:05:08Z] Miner died! It will be restarted soon...

Just search your source code for error messages and you'll see which ones do not specify the GPU id.

Also, you misunderstood my point about Xid kernel driver errors. Once again, some of the errors reported by bminer are NOT also accompanied by a Xid driver error (in kern.log). No other miner does this. It's a problem when bminer doesn't report the GPU id in the error message since I have no idea which GPU is at fault (no Xid, no GPU id in bminer error).

Also, if the miner reports a problem with the hardware but the nvidia driver sees nothing wrong, then it's likely that you have a bug in your code. No other miner has this behavior - I tested dstm, ewbf, ethminer, claymore, ccminer for a long time; all errors reported by these miners are accompanied by Xid errors - that is, a hardware fault did indeed occur.

I don't think bminer is tested as extensively as you claim - it can't, really, given how new it is.

My system is a Ubuntu 16.04, nvidia 384.90, 384.98, 387.34, kernel 4.4.0.104.

I like bminer's speed though, which is why I'm taking the time to post here to help you.

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