OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 104.

ThinkFast

member

Activity: 69

Merit: 10

bfgminer -u xxx_RHD5570bfg -p xxx -d 1 -c bfgminer.conf
bfgminer.conf
{
"url" : "http://mint.bitminter.com:8332"
}

bfgminer version 3.4.0 - Started: [2013-10-27 21:55:56] - [ 0 days 00:00:45]
[M]anage devices [P]ool management [_S]ettings [D]isplay options [H]elp [Q]uit
Connected to us1.bitminter.com diff 1 with stratum as user xxx_RHD5570bfg
Block: ...2d46a0b0 #266459 Diff:391M ( 2.80Ph/s) Started: [21:55:56]
ST:2 F:0 NB:1 AS:0 BW:[ 2/ 0kB/s] E:0.00 I: 0.00 BTC/hr BS:0
1 66.0C | 70.39/71.09/ 0.00Mh/s | A:0 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------
OCL 0: 60.0C | OFF / 0.0/ 0.0 h/s | A:0 R:0+0(none) HW:0/none
OCL 1: 66.5C | 71.43/71.03/ 0.00Mh/s | A:0 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------

Code:

[2013-10-27 21:55:53] Loaded configuration file bfgminer.conf
 [2013-10-27 21:55:54] Probing for an alive pool
 [2013-10-27 21:55:55] Switching pool 0 http://mint.bitminter.com:8332 to stratu
m+tcp://us1.bitminter.com:3333
 [2013-10-27 21:55:56] Pool 0 http://mint.bitminter.com:8332 alive
 [2013-10-27 21:55:56] Network difficulty changed to 391M ( 2.80Ph/s)
 [2013-10-27 21:55:56] Stratum from pool 0 detected new block
 [2013-10-27 21:55:56] Pool 0 is hiding block contents from us
 [2013-10-27 21:55:57] Stratum from pool 0 requested work update
 [2013-10-27 21:55:58] OCL 0 (thread 0) being disabled
 [2013-10-27 21:55:58] OCL 0 (thread 1) being disabled
 [2013-10-27 21:56:00] Disabling extra threads due to dynamic mode.
 [2013-10-27 21:56:00] Tune dynamic intensity with --gpu-dyninterval
 [2013-10-27 21:56:27] Stratum from pool 0 requested work update
 [2013-10-27 21:56:57] Stratum from pool 0 requested work update
 [2013-10-27 21:57:02] Stratum from pool 0 requested work update
 [2013-10-27 21:57:07] Accepted 8afaaed2 OCL 1  Diff 1/1
 [2013-10-27 21:57:32] Stratum from pool 0 requested work update
 [2013-10-27 21:58:02] Stratum from pool 0 requested work update
 [2013-10-27 21:58:32] Stratum from pool 0 requested work update
 [2013-10-27 21:59:03] Stratum from pool 0 requested work update
 [2013-10-27 21:59:20] Accepted 6fc651cc OCL 1  Diff 2/1
 [2013-10-27 21:59:33] Stratum from pool 0 requested work update
 [2013-10-27 22:00:03] Stratum from pool 0 requested work update
 [2013-10-27 22:00:10] Accepted b46c7e2f OCL 1  Diff 1/1
 [2013-10-27 22:00:33] Stratum from pool 0 requested work update

Why so many "Stratum from pool 0 requested work update" requests?
I must doing something seriously wrong?

Edit: Forgot to mention: I'm running cgminer on d=0 and bfgminer on d=1 on the same PC in WXPSP3.
Could there be a port conflict? If so, is there a way to resolve it and still run both miners?

Nemo1024

legendary

Activity: 1680

Merit: 1014

Quote from: Luke-Jr on October 26, 2013, 06:52:21 PM

Quote from: Nemo1024 on October 26, 2013, 06:48:54 PM

Will 3.4.0 retry failed COM ports when initialising USB BEs? I guess I can try tomorrow, but it's be nice to have a confirmation befor re-installing the UPS monitoring software.

When you tell it to, like 3.3 and 3.2 did...

From command line? Can't seem to find the appropriate switch. I'm running from my own unattended front-end with -T

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: af_newbie on September 12, 2013, 04:28:26 PM

I was wondering if you could add JSONP commands to your APIs.
JSONP extension of your APIs would allow to access bfgminer directly from any static (local to browser) page.
AJAX calls can be made from the browser directly to API port. No cross-domain issues.

How about CORS? That seems to be the way to go nowadays...?

juhakall

sr. member

Activity: 658

Merit: 250

Is there any way to determine the BSB2ab style device names from API replies? I can't use ProcID, because the naming scheme differs when there are more chips. For example, I have BSB devices with 16 or 32 chips. ProcID 0 on BSB0 is BSB0a, but ProcID 0 on BSB2 is BSB2aa.

This would be useful because --set-device use the letter naming scheme as arguments when setting options for individual chips.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: purelithium on October 27, 2013, 08:57:46 AM

Quote from: Luke-Jr on October 26, 2013, 11:26:17 PM

Quote from: purelithium on October 26, 2013, 10:11:11 PM

WeBisect keeps timing out and not refreshing once the new build is ready. I don't have time now. Maybe I'll try again tomorrow. Back to 3.2.1 for me.

Are you giving it enough time? It needs to actually build each commit Wink

Like I said before, 5-10 minutes should be enough.

For a single build, probably.
Looking at the log for your session, though, it was hitting some commits that failed to build on Windows;
when this happens, it automatically skips them for you and moves on.
You can always come back to your session later, if it's taking too long.

purelithium

hero member

Activity: 504

Merit: 500

Quote from: Luke-Jr on October 26, 2013, 11:26:17 PM

Quote from: purelithium on October 26, 2013, 10:11:11 PM

WeBisect keeps timing out and not refreshing once the new build is ready. I don't have time now. Maybe I'll try again tomorrow. Back to 3.2.1 for me.

Are you giving it enough time? It needs to actually build each commit Wink

Like I said before, 5-10 minutes should be enough.

vpasic

sr. member

Activity: 266

Merit: 250

so I have 2 BFL singles 60gh and I want to mine BTC with first and TRC with second unit.
In BFGminer when I add -d 0 function it mines BTC in one CMD window with one miner but when I add -d 1 function in second CMD window BFGminer can't find second BFL unit.
Please help.
Thanks

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: purelithium on October 26, 2013, 10:11:11 PM

WeBisect keeps timing out and not refreshing once the new build is ready. I don't have time now. Maybe I'll try again tomorrow. Back to 3.2.1 for me.

Are you giving it enough time? It needs to actually build each commit Wink

purelithium

hero member

Activity: 504

Merit: 500

WeBisect keeps timing out and not refreshing once the new build is ready. I don't have time now. Maybe I'll try again tomorrow. Back to 3.2.1 for me.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: purelithium on October 26, 2013, 09:15:37 PM

webisect failed. The first build it gave me was an old version(3.1.1) even though I told it to work from 3.2.1, and the commandline flags i tried giving, weren't accepted. I tried skipping the build, but no new build was supplied(after waiting 5-10 min for it to auto refresh.

Fixed this - the branches weren't up to date, so webisect didn't have 3.4.0 yet.
You should be able to continue the same session safely now.

purelithium

hero member

Activity: 504

Merit: 500

webisect failed. The first build it gave me was an old version(3.1.1) even though I told it to work from 3.2.1, and the commandline flags i tried giving, weren't accepted. I tried skipping the build, but no new build was supplied(after waiting 5-10 min for it to auto refresh.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: purelithium on October 26, 2013, 08:52:09 PM

This is what happens when I run bfgminer using the flags passed by MultiMiner. This rig mines fine on 3.2.1, but for some reason 3.3.0+ won't work. crossposted in the MultiMiner thread, as well.

Please bisect this.

purelithium

hero member

Activity: 504

Merit: 500

This is what happens when I run bfgminer using the flags passed by MultiMiner. This rig mines fine on 3.2.1, but for some reason 3.3.0+ won't work. crossposted in the MultiMiner thread, as well.

Code:

C:\Mining\MultiMiner\Miners\bfgminer>bfgminer --scan-serial erupter:all --scan-s
erial opencl:auto -o pool1.us.multipool.us:3335 -u user -p "" -o coin
otron.com:8322 -u user -p taco -d 0 -d 1 -d 2 -d 3 -d 4 -d 5 -d 6 -d
7 -d 8 -d 9 -d 10 -d 11 -d 12 -d 13 -d 14 -d 15 -d 16 -d 17 -d 18 -d 19 -d 20 -d
 21 -d 22 -d 23 -d 24 -d 25 -d 26 -d 27 -d 28 -d 29 -d 30 -d 31 --api-listen --a
pi-port 4029 --api-allow W:127.0.0.1, -T
 [2013-10-26 21:46:13] Started bfgminer 3.4.0
 [2013-10-26 21:46:22] Probing for an alive pool
 [2013-10-26 21:46:23] Pool 1 is hiding block contents from us

 [2013-10-26 21:46:23] Network difficulty changed to 5.39M (38.61Th/s)

 [2013-10-26 21:46:23] Switching to pool 1 http://coinotron.com:8322 - first ali
ve pool
 [2013-10-26 21:46:23] Long-polling activated for http://coinotron.com:8344 (get
work)
 [2013-10-26 21:46:23] Pool 0 http://pool1.us.multipool.us:3335 alive

 [2013-10-26 21:46:23] Pool 0 is hiding block contents from us

 [2013-10-26 21:46:23] Switching to pool 0 http://pool1.us.multipool.us:3335

 [2013-10-26 21:46:24] OCL 0 (thread 32) being disabled
 [2013-10-26 21:46:24] OCL 0 (thread 33) being disabled
 [2013-10-26 21:46:24] OCL 1 (thread 34) being disabled
 [2013-10-26 21:46:24] OCL 1 (thread 35) being disabled
 [2013-10-26 21:46:24] OCL 2 (thread 36) being disabled
 [2013-10-26 21:46:24] OCL 2 (thread 37) being disabled
 [2013-10-26 21:46:24] OCL 3 (thread 38) being disabled
 [2013-10-26 21:46:24] OCL 3 (thread 39) being disabled
 [2013-10-26 21:46:24] OCL 4 (thread 40) being disabled
 [2013-10-26 21:46:24] Disabling extra threads due to dynamic mode.

 [2013-10-26 21:46:24] OCL 4 (thread 41) being disabled
 [2013-10-26 21:46:24] Tune dynamic intensity with --gpu-dyninterval

 [2013-10-26 21:46:24] Staged work underrun; increasing queue minimum to 2

 [2013-10-26 21:46:24] Staged work underrun; increasing queue minimum to 3

 [2013-10-26 21:46:24] Staged work underrun; increasing queue minimum to 4

 [2013-10-26 21:46:24] BES 1 being disabled
 [2013-10-26 21:46:24] Staged work underrun; increasing queue minimum to 5

 [2013-10-26 21:46:25] Accepted 0b8c7bc1 BES14  pool 0 Diff 22/2

 [2013-10-26 21:46:26] Accepted 45517d95 BES12  pool 0 Diff 3/2

0x855e10 : [unknown module] : [unknown file]
0x452c56 : C:\Mining\MultiMiner\Miners\bfgminer\bfgminer.exe : /home/luke-jr/Pro
jects/Education/Tonal/BitCoin/bfgminer/make-release-tmp/bfgminer-3.4.0-tmp/adl.c
 (1133) : in function (gpu_autotune)
0x41feef : C:\Mining\MultiMiner\Miners\bfgminer\bfgminer.exe : /home/luke-jr/Pro
jects/Education/Tonal/BitCoin/bfgminer/make-release-tmp/bfgminer-3.4.0-tmp/miner
.c (9554) : in function (bfg_watchdog)
0x41fe29 : C:\Mining\MultiMiner\Miners\bfgminer\bfgminer.exe : /home/luke-jr/Pro
jects/Education/Tonal/BitCoin/bfgminer/make-release-tmp/bfgminer-3.4.0-tmp/miner
.c (9523) : in function (watchdog_thread)
Failed to init bfd from (C:\Mining\MultiMiner\Miners\bfgminer\pthreadGC2.dll)
0x6248671b : C:\Mining\MultiMiner\Miners\bfgminer\pthreadGC2.dll : pthread_creat
e
Failed to init bfd from (C:\Windows\syswow64\msvcrt.dll)
0x764d1287 : C:\Windows\syswow64\msvcrt.dll : itow_s
Failed to init bfd from (C:\Windows\syswow64\msvcrt.dll)
0x764d1328 : C:\Windows\syswow64\msvcrt.dll : endthreadex
Failed to init bfd from (C:\Windows\syswow64\kernel32.dll)
0x75b5336a : C:\Windows\syswow64\kernel32.dll : BaseThreadInitThunk
Failed to init bfd from (C:\Windows\SysWOW64\ntdll.dll)
0x77e59f72 : C:\Windows\SysWOW64\ntdll.dll : RtlInitializeExceptionChain
Failed to init bfd from (C:\Windows\SysWOW64\ntdll.dll)
0x77e59f45 : C:\Windows\SysWOW64\ntdll.dll : RtlInitializeExceptionChain

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: Nemo1024 on October 26, 2013, 06:48:54 PM

Will 3.4.0 retry failed COM ports when initialising USB BEs? I guess I can try tomorrow, but it's be nice to have a confirmation befor re-installing the UPS monitoring software.

When you tell it to, like 3.3 and 3.2 did...

Nemo1024

legendary

Activity: 1680

Merit: 1014

Will 3.4.0 retry failed COM ports when initialising USB BEs? I guess I can try tomorrow, but it's be nice to have a confirmation befor re-installing the UPS monitoring software.

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: Mudbankkeith on October 26, 2013, 06:22:22 PM

Copied in my batch file from 3.3.0

works a treat straight from the box(well..... zip file really)

If you have no other devices listed, and no other usb services, then just use:-( -S all)

My Hardware Errors are about the same as before, but the Rejection rate is way down

Luke-Jr

legendary

Activity: 2576

Merit: 1186

If anyone has any regressions from 3.3.0 (like erupters not working consistently), please use http://luke.dashjr.org/tmp/code/webisect/webisect.php to figure out what broken it.

wmcorless

full member

Activity: 192

Merit: 100

paccoin

Quote from: Zammo on October 26, 2013, 06:02:24 PM

Quote from: xzempt on October 26, 2013, 05:20:02 PM

when i use the -S erupter:all it doesnt recognize any of my usb miners :\

3.4.0 won't recognise my usb erupters either

I am using the same .conf that I used with 3.3.0 and never had this issue before

if you are running on ubuntu, then try it as a superuser.
sudo su
also I use "-S all"

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Copied in my batch file from 3.3.0

works a treat straight from the box(well..... zip file really)

If you have no other devices listed, and no other usb services, then just use:-( -S all)

Zammo

full member

Activity: 152

Merit: 100

I changed nothing, ran it again and it is working fine. Very Strange

Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 104. (Read 1193219 times)