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

juhakall

sr. member

Activity: 658

Merit: 250

Quote from: Taugeran on October 16, 2013, 04:49:31 PM

Quote from: village.idiot on October 16, 2013, 04:25:33 PM

Don't know what I'm doing, but messing around it looks like
\home\pi\bfgminer-3.2.1

ok that would be ~/bfgminer-3.2.1

insert this as your bfgminer startup script:

#!/bin/bash
screen -S bfgminer -d -m su - pi /home/pi/bfgminer-3.2.1/.bfgminer -D 2>/home/pi/bfgminer-3.2.1/logs/activity.log

try than and see if it works

afterward you should be able to ssh in as [email protected] and execute:

Code:

screen -r bfgminer

this should bring up a bfgminer window with lots of debug info flying on screen.

todo: figure out how to garbage collect every N time period (e.g. 24 hrs) to create a rolling log

Try this to get the rolling log:

Code:

cp /home/pi/bfgminer-3.2.1/logs/activity.log /home/pi/bfgminer-3.2.1/logs/activity-`date +%s`.log
echo > /home/pi/bfgminer-3.2.1/logs/activity.log

echo will flush the file contents without deleting it, and bfgminer will just keep appending to that same file like nothing happened.

village.idiot

sr. member

Activity: 270

Merit: 250

Thanks
I'll give that a try

Taugeran

hero member

Activity: 658

Merit: 500

CCNA: There i fixed the internet.

Quote from: village.idiot on October 16, 2013, 04:25:33 PM

Don't know what I'm doing, but messing around it looks like
\home\pi\bfgminer-3.2.1

ok that would be ~/bfgminer-3.2.1

insert this as your bfgminer startup script:

#!/bin/bash
screen -S bfgminer -d -m su - pi /home/pi/bfgminer-3.2.1/.bfgminer -D 2>/home/pi/bfgminer-3.2.1/logs/activity.log

try than and see if it works

afterward you should be able to ssh in as [email protected] and execute:

Code:

screen -r bfgminer

this should bring up a bfgminer window with lots of debug info flying on screen.

todo: figure out how to garbage collect every N time period (e.g. 24 hrs) to create a rolling log

village.idiot

sr. member

Activity: 270

Merit: 250

Don't know what I'm doing, but messing around it looks like
\home\pi\bfgminer-3.2.1

Taugeran

hero member

Activity: 658

Merit: 500

CCNA: There i fixed the internet.

Quote from: village.idiot on October 16, 2013, 03:02:13 PM

Trying this again since I never got a response...

I'm running bfgminer on a Pi.
Thanks to the help of DrGuns4Hands, it can boot up and run unassisted.
However, when the pool was experiencing the recent DDoS attacks,
I heard the fan slow down for a long period but couldn't see the fault messages that would have been displayed if I had opened a terminal and started bfgminer manually.
So, how do I automatically start it with the output displayed or,
even better, how do I see the output messages using SSH?

I know this is really simple for you guys. A little help, please.

what is the location of your bfgminer instalation relative to your rPi ~/ directory?

village.idiot

sr. member

Activity: 270

Merit: 250

Trying this again since I never got a response...

I'm running bfgminer on a Pi.
Thanks to the help of DrGuns4Hands, it can boot up and run unassisted.
However, when the pool was experiencing the recent DDoS attacks,
I heard the fan slow down for a long period but couldn't see the fault messages that would have been displayed if I had opened a terminal and started bfgminer manually.
So, how do I automatically start it with the output displayed or,
even better, how do I see the output messages using SSH?

I know this is really simple for you guys. A little help, please.

Taugeran

hero member

Activity: 658

Merit: 500

CCNA: There i fixed the internet.

Quote from: Mudbankkeith on October 14, 2013, 02:02:08 PM

Quote from: vulgartrendkill on October 14, 2013, 12:03:01 PM

Quote from: NorbyTheGeek on October 14, 2013, 11:54:09 AM

Like others, I have a couple Blue Fury units on order, so in anticipation I upgraded to 3.3.0. It's working great with my Jalapeno and my USB Block Erupters under Windows.

From looking at others' posts, I wonder if my setup is using a different driver for my block erupters. My erupters show up as ICAx instead of BESx. Is that due to the USB driver I use for them, or do they always show up as ICA under Windows?

Is there something I should be doing different for these units?

I`m not sure it makes a great difference but I use

Code:

-s erupter:all

to get the "BES" showing instead of "ICA"

This is only needed when you have a mix of devices and need them to show in the process window.
mostly -S all Is good enough to hash.

when it uses the erupter driver the timings used by bfgminer are different( remember when the BES first came out, we had to use --icarus-options). this has been coded into the BES driver to provide better resolution for timing like sending new work at the tail end of a work unit (~12 second on a standard clocked BES)

aspirez

newbie

Activity: 41

Merit: 0

I found that already, but thanks

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: aspirez on October 16, 2013, 04:32:19 AM

Hi,
can someone explain me how to build BFG miner for windows with static libralies, like that in the win32/64 prebuilded zip's?

None of my builds use static libraries.
They are compiled on Gentoo GNU/Linux using the included make-release script.

Zammo

full member

Activity: 152

Merit: 100

Quote from: smoothrunnings on October 16, 2013, 04:34:12 AM

How do I setup second pool as failover using the command line in Windows?

I have 3.3.0 installed, the 64bit but when I hit P I see something appear at the bottom of the screen but then its over written a second later buy the application, is this a bug, IDK? This is why I asking about adding the second pool (failover) to the command line so I don't have have to worry about doing it in the application itself.

Thanks,

If you want easy to use GUI for BFGMiner, try CGWatcher - http://manotechnology.blogspot.co.uk/p/cgwatcher.html

Makes it much easier to use and configure

smoothrunnings

hero member

Activity: 630

Merit: 501

Quote from: Zammo on October 16, 2013, 03:52:33 AM

I have 3.3.0 running on Win7 x64. I haven't had any issues. I have 28 USB erupters, 3.3.0 seems to detect the erupters perfectly. When I used 3.2.1, I often needed to restart BFGMiner several times before all the erupters were detected

I agree, 3.3.0 seems to be more stable on Windows than 3.2.1, I was getting periods where a hub of USB keys would disconnect and reconnect, but I don't seem to have that problem now with 3.3.0.

smoothrunnings

hero member

Activity: 630

Merit: 501

How do I setup second pool as failover using the command line in Windows?

I have 3.3.0 installed, the 64bit but when I hit P I see something appear at the bottom of the screen but then its over written a second later buy the application, is this a bug, IDK? This is why I asking about adding the second pool (failover) to the command line so I don't have have to worry about doing it in the application itself.

Thanks,

aspirez

newbie

Activity: 41

Merit: 0

Hi,
can someone explain me how to build BFG miner for windows with static libralies, like that in the win32/64 prebuilded zip's?

Zammo

full member

Activity: 152

Merit: 100

I have 3.3.0 running on Win7 x64. I haven't had any issues. I have 28 USB erupters, 3.3.0 seems to detect the erupters perfectly. When I used 3.2.1, I often needed to restart BFGMiner several times before all the erupters were detected

HellDiverUK

hero member

Activity: 1246

Merit: 501

My 1st Gen Blades are sitting at 2.6% and 3.4% HW errors. It's pretty normal for them. The Block Erupters are all sitting between 0.5-0.7% HW errors. Again, normal.

vulgartrendkill

hero member

Activity: 518

Merit: 500

Quote from: HellDiverUK on October 16, 2013, 02:43:43 AM

3.3.0 is running well here, Win32 version running on Windows 8.1 Ent. Currently only controlling a few Block Erupters and two Blades.

Yep same here. 10 BE and 2 Gen 2 blades running a total of 24.50 ghs.

I have noticed that rejects are about 3 %. Any idea how I can reduce these or is that acceptable? Hw errors at .98 %.

HellDiverUK

hero member

Activity: 1246

Merit: 501

3.3.0 is running well here, Win32 version running on Windows 8.1 Ent. Currently only controlling a few Block Erupters and two Blades.

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: vulgartrendkill on October 14, 2013, 12:03:01 PM

Quote from: NorbyTheGeek on October 14, 2013, 11:54:09 AM

Like others, I have a couple Blue Fury units on order, so in anticipation I upgraded to 3.3.0. It's working great with my Jalapeno and my USB Block Erupters under Windows.

From looking at others' posts, I wonder if my setup is using a different driver for my block erupters. My erupters show up as ICAx instead of BESx. Is that due to the USB driver I use for them, or do they always show up as ICA under Windows?

Is there something I should be doing different for these units?

I`m not sure it makes a great difference but I use

Code:

-s erupter:all

to get the "BES" showing instead of "ICA"

This is only needed when you have a mix of devices and need them to show in the process window.
mostly -S all Is good enough to hash.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: juhakall on October 14, 2013, 01:20:58 PM

Quote from: Luke-Jr on October 14, 2013, 01:09:59 PM

Quote from: juhakall on October 14, 2013, 08:41:34 AM

Is it possible to alter the difficulty target for the stratum proxy? I tried it with my BitFury ASIC, and it was getting flooded with diff 0 shares, and the miner's CPU became overloaded. I only got around 60GH/s hashrate when the real hashrate was 95GH/s. The proxy could be a nice alternative to get good backup pool support and the performance of chainminer, which still seems to be a bit faster than BFGMiner.

chainminer doesn't support stratum, so I don't think this will help. Sad

I tried it with the slush stratum proxy, of course. Yes, two proxies there. As I said, it did produce valid shares at around 60GH/s, and was only limited by the CPU because BFGMiner's proxy didn't set a higher diff target. Another solution I've tried is BFGMiner's getwork proxy, but that won't work because it doesn't support RollNTime.

These kludges would be useful only because BFGMiner still is around 1% slower than chainminer with BFSB miners.

What does this mean exactly?: "Third hashrate displayed is now based on nonces found, adjusted for pool rejected/stale shares. It should still be approximately equivalent to your effective/earning hashrate, but with better accuracy."

At first I thought it was purely based on difficulty accepted ((difficulty_accepted/seconds_elapsed*2^32) hashes per second), but the numbers don't match.

That's what it used to be. Now it's based on (good_nonces * (difficulty_accepted / difficulty_submitted)) for better resolution.

juhakall

sr. member

Activity: 658

Merit: 250

Quote from: Luke-Jr on October 14, 2013, 01:09:59 PM

Quote from: juhakall on October 14, 2013, 08:41:34 AM

Is it possible to alter the difficulty target for the stratum proxy? I tried it with my BitFury ASIC, and it was getting flooded with diff 0 shares, and the miner's CPU became overloaded. I only got around 60GH/s hashrate when the real hashrate was 95GH/s. The proxy could be a nice alternative to get good backup pool support and the performance of chainminer, which still seems to be a bit faster than BFGMiner.

chainminer doesn't support stratum, so I don't think this will help. Sad

I tried it with the slush stratum proxy, of course. Yes, two proxies there. As I said, it did produce valid shares at around 60GH/s, and was only limited by the CPU because BFGMiner's proxy didn't set a higher diff target. Another solution I've tried is BFGMiner's getwork proxy, but that won't work because it doesn't support RollNTime.

These kludges would be useful only because BFGMiner still is around 1% slower than chainminer with BFSB miners.

What does this mean exactly?: "Third hashrate displayed is now based on nonces found, adjusted for pool rejected/stale shares. It should still be approximately equivalent to your effective/earning hashrate, but with better accuracy."

At first I thought it was purely based on difficulty accepted ((difficulty_accepted/seconds_elapsed*2^32) hashes per second), but the numbers don't match.

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