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

[Foss]

Luke-Jr
Hi, why diff show 0 when scrypt mining? In cgminer show 32 or 64, depending of pool

[Luke-Jr]

Hi, why diff show 0 when scrypt mining? In cgminer show 32 or 64, depending of pool

cgminer is showing Ldiff (Litecoin difficulty).
BFGMiner is showing pdiff (pool difficulty).

[Foss]

Hi, why diff show 0 when scrypt mining? In cgminer show 32 or 64, depending of pool

cgminer is showing Ldiff (Litecoin difficulty).
BFGMiner is showing pdiff (pool difficulty).

Exactly pool difficulty in BFGMiner is 0, and Ldiff is 894. in cgminer pool difficulty is 32, and Ldiff is 58.6M. Here my settings:
@echo off
setx GPU_MAX_ALLOC_PERCENT 100
bfgminer.exe --scrypt -o stratum+tcp://mining.eu.hypernova.pw:3333 -u user -p password -d 0,1 -I 20,19 -w 256 -v 1 -g 1 --lookup-gap 2 --thread-concurrency 21772,16192 --queue 0 -s 1, whats wrong?

[xyzzy099]

Hi, why diff show 0 when scrypt mining? In cgminer show 32 or 64, depending of pool

cgminer is showing Ldiff (Litecoin difficulty).
BFGMiner is showing pdiff (pool difficulty).

Exactly pool difficulty in BFGMiner is 0, and Ldiff is 894. in cgminer pool difficulty is 32, and Ldiff is 58.6M. Here my settings:
@echo off
setx GPU_MAX_ALLOC_PERCENT 100
bfgminer.exe --scrypt -o stratum+tcp://mining.eu.hypernova.pw:3333 -u user -p password -d 0,1 -I 20,19 -w 256 -v 1 -g 1 --lookup-gap 2 --thread-concurrency 21772,16192 --queue 0 -s 1, whats wrong?

From the cgminer README/FAQ:

Q: Why do the scrypt diffs not match with the current difficulty target?
A: The current scrypt block difficulty is expressed in terms of how many
multiples of the BTC difficulty it currently is (eg 28) whereas the shares of
"difficulty 1" are actually 65536 times smaller than the BTC ones. The diff
expressed by cgminer is as multiples of difficulty 1 shares.

It looks like BFGMiner does not do the same re-calculation that CGMiner does.

[Luke-Jr]

Hi, why diff show 0 when scrypt mining? In cgminer show 32 or 64, depending of pool

cgminer is showing Ldiff (Litecoin difficulty).
BFGMiner is showing pdiff (pool difficulty).

Exactly pool difficulty in BFGMiner is 0, and Ldiff is 894. in cgminer pool difficulty is 32, and Ldiff is 58.6M. Here my settings:
@echo off
setx GPU_MAX_ALLOC_PERCENT 100
bfgminer.exe --scrypt -o stratum+tcp://mining.eu.hypernova.pw:3333 -u user -p password -d 0,1 -I 20,19 -w 256 -v 1 -g 1 --lookup-gap 2 --thread-concurrency 21772,16192 --queue 0 -s 1, whats wrong?

You're confusing Litecoin's network difficulty with Litecoin-difficulty-unit.

Target	pdiff	bdiff	Ldiff
BC network (today)	31.3M	31.3M	2T
LTC network (today)	894.212	894.198	58.6M
pdiff 1	1	0.999985	65536
bdiff 1	1.000015	1	65537
Ldiff 1	0.000015	0.000015	1

[Foss]

Luke-Jr
I mean this:
 
will you improve it?

[Luke-Jr]

Luke-Jr
I mean this:
 
will you improve it?

BFGMiner is the improvement already. It is not difficulty 64, it is difficulty 0.001.

[viriat0]

hello folks,

is normal this happen?

 [2013-07-26 22:41:40] Stratum from pool 0 requested work update
 [2013-07-26 22:41:41] Accepted 05f4ca86 ICA 1  Diff 42/2
 [2013-07-26 22:42:00] Stratum from pool 0 requested work update
 [2013-07-26 22:42:06] Stratum from pool 0 requested work update
 [2013-07-26 22:42:13] Stratum from pool 0 requested work update
 [2013-07-26 22:42:18] Stratum from pool 0 requested work update
 [2013-07-26 22:42:25] Stratum from pool 0 requested work update

Conected on 50BTC.

cheers

[Taugeran]

hello folks,

is normal this happen?

 [2013-07-26 22:41:40] Stratum from pool 0 requested work update
 [2013-07-26 22:41:41] Accepted 05f4ca86 ICA 1  Diff 42/2
 [2013-07-26 22:42:00] Stratum from pool 0 requested work update
 [2013-07-26 22:42:06] Stratum from pool 0 requested work update
 [2013-07-26 22:42:13] Stratum from pool 0 requested work update
 [2013-07-26 22:42:18] Stratum from pool 0 requested work update
 [2013-07-26 22:42:25] Stratum from pool 0 requested work update

Conected on 50BTC.

cheers

What is your total hashrate in bfgminer?

[viriat0]

hello folks,

is normal this happen?

 [2013-07-26 22:41:40] Stratum from pool 0 requested work update
 [2013-07-26 22:41:41] Accepted 05f4ca86 ICA 1  Diff 42/2
 [2013-07-26 22:42:00] Stratum from pool 0 requested work update
 [2013-07-26 22:42:06] Stratum from pool 0 requested work update
 [2013-07-26 22:42:13] Stratum from pool 0 requested work update
 [2013-07-26 22:42:18] Stratum from pool 0 requested work update
 [2013-07-26 22:42:25] Stratum from pool 0 requested work update

Conected on 50BTC.

cheers

What is your total hashrate in bfgminer?

1000MH/S

3 USB Asicminer

Use:

/bfgminer# ./bfgminer -o pool.50btc.com:8332 -u username -p 123 -S all --icarus-options 115200:1:1 --icarus-timing 3.0=100

thanks

[Taugeran]

hello folks,

is normal this happen?

 [2013-07-26 22:41:40] Stratum from pool 0 requested work update
 [2013-07-26 22:41:41] Accepted 05f4ca86 ICA 1  Diff 42/2
 [2013-07-26 22:42:00] Stratum from pool 0 requested work update
 [2013-07-26 22:42:06] Stratum from pool 0 requested work update
 [2013-07-26 22:42:13] Stratum from pool 0 requested work update
 [2013-07-26 22:42:18] Stratum from pool 0 requested work update
 [2013-07-26 22:42:25] Stratum from pool 0 requested work update

Conected on 50BTC.

cheers

What is your total hashrate in bfgminer?

1000MH/S

3 USB Asicminer

Use:

/bfgminer# ./bfgminer -o pool.50btc.com:8332 -u username -p 123 -S all --icarus-options 115200:1:1 --icarus-timing 3.0=100

thanks

Does it have large strings of the stratum request events frequently or just every once in a while. With a 1Ghash/sec rig you should see results far outstrip requests.

[vpereira]

what is the best way to bootstrap a x6500? I have one, with fan and heatsink that after some minutes, it get SICK and DEAD. bfgminer, compiled yesterday from github. Im running it together with 3 usb erupter..

[Zeronic]

what is the best way to bootstrap a x6500? I have one, with fan and heatsink that after some minutes, it get SICK and DEAD. bfgminer, compiled yesterday from github. Im running it together with 3 usb erupter..

Even with the zadig_v2.0.1.160 driver, I can't get BFGminer to see any of my X6500.

[vpereira]

for me, i have a cluster with 12 fpgas running on raspberrypi. I isolated one x6500 and I'm trying to run it, together with the pi and it simply get sick and die

anybody running a x6500 + bfgminer? which cmline params do you use?

[jml]

Hello,

I have been running a pi (I have two pi's; R1 and R2) with a ZTEX 1.15x and 2 CM1 FPGA boards running BFGMiner 3.0.2. I recently upgraded to version 3.1.2 and acquired 7 USB Block Erupters plugged into a DLINK 7 port hub which maximum amperage is 3A.

The CM1 and ZTEX do not have significant problems in running but upon installing the new BE, it only takes about one hour until the pi crashes and needs to be restarted. I have tried both hardware revisions and I can confirm that it still crashes on both.

I reduced the load on the USB device from 7 to 5 (5 * 0.51 = 2.5amps) and it still makes the pi crash to the point of needing a hard restart. I am now testing with 4 USB BE plugged into the hub.

The arguments used when executing BFGMiner is "-S all".

I am not sure if this is a problem with power draw which I am trying to eliminate or a software problem that is causing the pi to crash.

Any help is greatly appreciated.

[Luke-Jr]

Hello,

I have been running a pi (I have two pi's; R1 and R2) with a ZTEX 1.15x and 2 CM1 FPGA boards running BFGMiner 3.0.2. I recently upgraded to version 3.1.2 and acquired 7 USB Block Erupters plugged into a DLINK 7 port hub which maximum amperage is 3A.

The CM1 and ZTEX do not have significant problems in running but upon installing the new BE, it only takes about one hour until the pi crashes and needs to be restarted. I have tried both hardware revisions and I can confirm that it still crashes on both.

I reduced the load on the USB device from 7 to 5 (5 * 0.51 = 2.5amps) and it still makes the pi crash to the point of needing a hard restart. I am now testing with 4 USB BE plugged into the hub.

The arguments used when executing BFGMiner is "-S all".

I am not sure if this is a problem with power draw which I am trying to eliminate or a software problem that is causing the pi to crash.

Any help is greatly appreciated.

A backtrace may be useful.
Rebuild with

Code:

make clean && ./configure CFLAGS='-O0 -ggdb' && make

Note that -O0 is OH ZERO.

Then start bfgminer with

Code:

gdb --args ./bfgminer YOUR OPTIONS ETC -S all

When it crashes, run

Code:

thr app all bt

... and post the output from this (it will be many pages).

[jml]

Hello,

I have been running a pi (I have two pi's; R1 and R2) with a ZTEX 1.15x and 2 CM1 FPGA boards running BFGMiner 3.0.2. I recently upgraded to version 3.1.2 and acquired 7 USB Block Erupters plugged into a DLINK 7 port hub which maximum amperage is 3A.

The CM1 and ZTEX do not have significant problems in running but upon installing the new BE, it only takes about one hour until the pi crashes and needs to be restarted. I have tried both hardware revisions and I can confirm that it still crashes on both.

I reduced the load on the USB device from 7 to 5 (5 * 0.51 = 2.5amps) and it still makes the pi crash to the point of needing a hard restart. I am now testing with 4 USB BE plugged into the hub.

The arguments used when executing BFGMiner is "-S all".

I am not sure if this is a problem with power draw which I am trying to eliminate or a software problem that is causing the pi to crash.

Any help is greatly appreciated.

A backtrace may be useful.
Rebuild with

Code:

make clean && ./configure CFLAGS='-O0 -ggdb' && make

Note that -O0 is OH ZERO.

Then start bfgminer with

Code:

gdb --args ./bfgminer YOUR OPTIONS ETC -S all

When it crashes, run

Code:

thr app all bt

... and post the output from this (it will be many pages).

Thanks for the reply,

I have done that and I am now waiting for it to fail.

[jml]

Hello,

I have been running a pi (I have two pi's; R1 and R2) with a ZTEX 1.15x and 2 CM1 FPGA boards running BFGMiner 3.0.2. I recently upgraded to version 3.1.2 and acquired 7 USB Block Erupters plugged into a DLINK 7 port hub which maximum amperage is 3A.

The CM1 and ZTEX do not have significant problems in running but upon installing the new BE, it only takes about one hour until the pi crashes and needs to be restarted. I have tried both hardware revisions and I can confirm that it still crashes on both.

I reduced the load on the USB device from 7 to 5 (5 * 0.51 = 2.5amps) and it still makes the pi crash to the point of needing a hard restart. I am now testing with 4 USB BE plugged into the hub.

The arguments used when executing BFGMiner is "-S all".

I am not sure if this is a problem with power draw which I am trying to eliminate or a software problem that is causing the pi to crash.

Any help is greatly appreciated.

A backtrace may be useful.
Rebuild with

Code:

make clean && ./configure CFLAGS='-O0 -ggdb' && make

Note that -O0 is OH ZERO.

Then start bfgminer with

Code:

gdb --args ./bfgminer YOUR OPTIONS ETC -S all

When it crashes, run

Code:

thr app all bt

... and post the output from this (it will be many pages).

Thanks for the reply,

I have done that and I am now waiting for it to fail.

Luke, I get the following screen:

Code:

GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/sudo...(no debugging symbols found)...done.
(gdb)

I have executed the following:

Code:

gdb --args sudo ./bfgminer -S all

Do I need to do anything else?

[purelithium]

Luke, is there any way to force BFGMiner to use the old(non-agressive clocks) bitstream for the MMQ? Ever since 2.9.x whenever you introduced the bitstream that aggressively clocks the MMQ higher and higher, I've noticed the HW errors being insane. Right now running for almost a week, the HW errors on 3.1.3 are 15%. That's a lot of hashes wasted. The software just keeps clocking the chips higher and higher, increasing the HW errors and decreasing the effective hashrate. If the clocking code was tied to the HW errors, that would better maximize hashrate, I think. If the HW errors exceed a certain % of shares, to lower the clocks progressively until it goes back below that threshold.

I know a few weeks ago you made a commit on github to be able to adjust the clocks in the Manage Devices menu, but there hasn't been a release since.

Can you either release this new clock-adjusting feature so I can set my clocks manually back to 210mhz where I actually got 840 mh/s Or maybe fix the bitstream/clocking code(sorry not a programmer, not sure what is involved here)?

Thanks! love the software as always!

[vpereira]

Hello,

I have been running a pi (I have two pi's; R1 and R2) with a ZTEX 1.15x and 2 CM1 FPGA boards running BFGMiner 3.0.2. I recently upgraded to version 3.1.2 and acquired 7 USB Block Erupters plugged into a DLINK 7 port hub which maximum amperage is 3A.

The CM1 and ZTEX do not have significant problems in running but upon installing the new BE, it only takes about one hour until the pi crashes and needs to be restarted. I have tried both hardware revisions and I can confirm that it still crashes on both.

I reduced the load on the USB device from 7 to 5 (5 * 0.51 = 2.5amps) and it still makes the pi crash to the point of needing a hard restart. I am now testing with 4 USB BE plugged into the hub.

The arguments used when executing BFGMiner is "-S all".

I am not sure if this is a problem with power draw which I am trying to eliminate or a software problem that is causing the pi to crash.

Any help is greatly appreciated.

A backtrace may be useful.
Rebuild with

Code:

make clean && ./configure CFLAGS='-O0 -ggdb' && make

Note that -O0 is OH ZERO.

Then start bfgminer with

Code:

gdb --args ./bfgminer YOUR OPTIONS ETC -S all

When it crashes, run

Code:

thr app all bt

... and post the output from this (it will be many pages).

Thanks for the reply,

I have done that and I am now waiting for it to fail.

Luke, I get the following screen:

Code:

GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/sudo...(no debugging symbols found)...done.
(gdb)

I have executed the following:

Code:

gdb --args sudo ./bfgminer -S all

Do I need to do anything else?

in the gdb shell you should write "run" and wait until it crashes.. then you could get more hints from the crash....not sure if it helps you.. there is any core file in your running directory?