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

Hy,

my config file :

BFGMiner will start, but in the wrong version. Its start 3.2.90 and not 3.10.0

with "M+" i can add USBs, but the antminer will only listed as ICA.

I think you need to decide if you will use bfgminer or cgminer ............. not both (cgminer.conf is overruling your BFGminer session)

Hy,

Thx for answer. But its not work.

You're missing a dash.  It's --set-device, not -set-device

Simple.

Hy,

i will install the bfgminer on raspberry. But its dont work.

What i do:

But now i become bfgminer version 3.2.90 with no support on antminers


And when i will start bfgminer with options :

i become only this error:

What is wrong here?

Hi, i have a problem.
If i set the thread concurrency over 24700 the miner doesn t mine! 

I have a r9 290x, windows 7, cpu sempron 145

With this setup  get 880khs:
-I 20 -g 1 --thread-concurrency --lookup-gap 2 --gpu-powertune 30   

 gpu clock 938  memory clock 1500


can someone help me?? 

thx

Thanks Luke, although I don't recall ever seeing it before last night.  Maybe just never noticed it...

Now I'm trying to figure out why my all time average and effective average has changed.  I was pretty much 2's across the board until last night, but there were lots of rebuilds on the system yesterday.

bfgminer version 3.10.0 - Started: [2014-02-07 10:15:53] - [  0 days 02:24:
 [M]anage devices [P]ool management [ S]ettings [D]isplay options [H]elp [Q]u
 Connected to us-east.multipool.us diff 64 with stratum as user Cassey.miner
 Block: ...b3a79105 #752072  Diff:7.65k (54.79Gh/s)  Started: [12:40:22]
 ST:8  F:3  NB:43  AS:0  BW:[871/ 10 B/s]  E:2.80  I: 3.54 BTC/hr  BS:9.36k
 6            | 12.73/ 6.46/ 5.37Gh/s | A:319 R:45+6( 14%) HW:8/.06%
----------------------------------------------------------------------------
 AMU 0:       |  2.06/ 1.08/ 0.91Gh/s | A: 50 R: 7+0( 12%) HW:2/.10%
 AMU 1:       |  2.06/ 1.08/ 0.83Gh/s | A: 60 R:11+5( 21%) HW:2/.10%
 AMU 2:       |  2.05/ 1.08/ 0.96Gh/s | A: 59 R: 6+0(9.2%) HW:1/.05%
 AMU 3:       |  2.05/ 1.08/ 0.91Gh/s | A: 54 R: 7+0( 11%) HW:1/.05%
 AMU 4:       |  2.06/ 1.08/ 0.93Gh/s | A: 53 R: 4+1(8.7%) HW:2/.10%
 AMU 5:       |  2.05/ 1.08/ 0.86Gh/s | A: 44 R:10+0( 18%) HW:0/none
----------------------------------------------------------------------------
 [2014-02-07 12:40:18] Accepted 0347e94d AMU 0  pool 0 Diff 78/64
 [2014-02-07 12:40:22] Network difficulty changed to 7.65k (54.79Gh/s)
 [2014-02-07 12:40:22] Stratum from pool 0 detected new block

Maybe its just a reporting change? When I look at the pool stats I see:

Active Workers
      Hashrate
Coin   Worker Name   1 minute   10 minute
btc   Cassey.miner2am   13744   12599

Which is a bit higher than the 12Gh/s I expected, but in line with the 20-second decaying rates reported above.

This is during probe, before the "clock" option exists.
It should still be set successfully when initialising the device.
I'll reduce the message to debug loglevel so as to avoid confusing people...

You may have a typo somewhere in the script.  I know that happened to me and I had a Z instead of an X for the clock speed.  I usually put all the -S and --stuff-here info at the end of the script before I run it.  Also, the speeds adjust over time.  You don't immediately hit 2 Gh/s until the program has hashed for a while because the data set that calculates the speed is so small.  Bigger data set = more accurate hash rate...

Sorry guys, I wasn't clear.

This was working fine until I pulled a new clone from github yesterday and rebuilt bfgminer.  The behavior is different now: its almost like the code is trying to push the chips dynamically, although it settled in around 1.8 rather than 2 per antminer after running for several hours.

Trying again right now on the chance I caught Luke in the middle of updating something last night.

Yep, still seeing it - although just for a second before the screen clears and the normal window appears.
 
./bfgminer -S antminer:all --set-device antminer:clock=x0981 -o ...

 [2014-02-07 10:10:52] AMU: Applying rule antminer:clock=x0981: Unknown option: clock

bdgminer then proceeds to run with the reported 20s decaying hashrate ramping up quickly to around 1.6 and then up about 0.01 S per cycle until around 2.0, then slowly moving up from there (at 2.04-2.07 across my 6 antminers right now).  It appears Luke is trying to auto-set clockrates in the most current version.

Cassey

and your command line/config is?

--set-device antminer:clock=x0881

works here.

Pulled a new clone this evening and now seeing:

[2014-02-07 02:36:31] AMU: Applying rule antminer:clock=x0981: Unknown option: clock

... when bfgminer launches.

Suggestions?

Should be the other way around... They should all be BEE and work.

Still leaves the issue that most of the Erupters won't submit any hashes.

I'm looking at this...

http://i237.photobucket.com/albums/ff265/Simulo/bfgminer-3.jpg

Check out all the non-ICA, non-BFL miners.

....it shouldn't do that. If I get them as ICAs then they work...slightly higher HW rate than I'd like (above 15%) for the Host they're on (if it was PC it'd be below 2%).

Try -S bitforce:all -S erupter:all so that the BFL unit gets scanned first.  Or since you only have one, you can find it's path by doing this:


Then you can use the path discovered with -S bitforce:/dev/ttyUSB## -S erupter:all

this is my batch file for antminers
bfgminer.exe  --set-device antminer:clock=x0981 --icarus-options 115200:2:2 --no-submit-stale -o http://stratum.bitcoin.cz:3333 -O worker:pasword -S antminer:all

Hi

Quick question

Is there a way to set max temp for a Butterfly labs 30GH/S?

Ps sorry

I was trying to make a .bat to autorun BFGminer but it just crashes.

This is what I have:-

bfgminer -S bifury:all -S antminer:all --set-device antminer:clock=x0981

When I put that in a command window it works fine but crashes if launched in a .bat

-and-

If I use -S erupter:all then the BFL unit fails to run. It does run if I don't use an "-S". But then only the BFL unit is detected and hashing. I then have to go M+ and 'all', because for whatever reason after about 9 'erupter:/dev/ttyUSB##' I get nothing but "No device found".

...which then leads back to the issue of BFGminer throwing drivers at the Erupters to see which ones stick.
And it's been roughly 9hrs and 11 of the 18 Erupters have failed to submit anything (no A or R), just 100% HW.
--It's always 11. And it can be any of the 18, so no, they are not going bad. Remember, this all works just fine all 19 Units hashing away on Windows.

And because I was getting pissed off and exhausted (woohoo, up til ~3AM), at Linux (because BFGminer works flawlessly on Windows), I didn't do the proper thing and actually list what I'm using.

OS: Debian Wheezy with LXDE and xRDP
Controller/Host: BeagleBone Black
Miners: (1) BFL Jalapeno 7GH; (18) Block Erupter 330 MHz/ea
Updates: Updated as of Feb. 3rd, 2014 using sudo apt-get

Here's a relevant portion of my BFGMiner.conf if that helps:



Why do you have Icarus timings at all? That stuff is baked in when you set it for erupter. From your post, it sounds like you're trying to force Icarus detection instead of the more appropriate Erupter. Any reason?