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

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: spooderman on October 21, 2013, 11:03:46 AM

Ah dude, every time I go out my miner stops working. It's a bfl 60gh. Usually it says something like this

Bugs don't get fixed unless they're reported Wink

Can you run BFGMiner in valgrind? It'll use a lot more CPU time, but it will also give a lot more info.

Code:

valgrind --leak-check=full --track-origins=yes bfgminer YOUR OPTIONS --debuglog 2>valgrind.log

spooderman

legendary

Activity: 1652

Merit: 1029

Ah dude, every time I go out my miner stops working. It's a bfl 60gh. Usually it says something like this

2d000-b6e2e000 rw-p 00000000 00:00 0
b6e2e000-b6e34000 r-xp 00000000 08:01 4854546 /usr/lib/i386-linux-gnu/libheimntlm.so.0.1.0
b6e34000-b6e35000 r--p 00005000 08:01 4854546 /usr/lib/i386-linux-gnu/libheimntlm.so.0.1.0
b6e35000-b6e36000 rw-p 00006000 08:01 4854546 /usr/lib/i386-linux-gnu/libheimntlm.so.0.1.0
b6e36000-b6e3d000 r-xp 00000000 08:01 4854579 /usr/lib/i386-linux-gnu/libkrb5support.so.0.1
b6e3d000-b6e3e000 r--p 00006000 08:01 4854579 /usr/lib/i386-linux-gnu/libkrb5support.so.0.1
b6e3e000-b6e3f000 rw-p 00007000 08:01 4854579 /usr/lib/i386-linux-gnu/libkrb5support.so.0.1
b6e3f000-b6e42000 r-xp 00000000 08:01 1442631 /lib/i386-linux-gnu/libcom_err.so.2.1
b6e42000-b6e43000 r--p 00002000 08:01 1442631 /lib/i386-linux-gnu/libcom_err.so.2.1
b6e43000-b6e44000 rw-p 00003000 08:01 1442631 /lib/i386-linux-gnu/libcom_err.so.2.1
b6e44000-b6e6a000 r-xp 00000000 Aborted (core dumped)

village.idiot

sr. member

Activity: 270

Merit: 250

Quote from: Taugeran on October 21, 2013, 02:19:19 AM

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.

hang in there bud. im still working out some bugs in a setup for ya. sorry its taken so long

Not a problem. It's not keeping me from mining.
I appreciate the help you've already been.
I've tried messing with a few things with screen, bfgminerstart.sh and rc.local but haven't found what I should be doing.
I thought what I wanted would be easy for a linux person.

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.

hang in there bud. im still working out some bugs in a setup for ya. sorry its taken so long

ewibit

legendary

Activity: 2955

Merit: 1049

BFL LS:
what goes wrong, what does this mean?

Code:

BFL 1a: Ran out of buffer space for results, discarding extra data

often after a time BFL LS get sick, stops and no restart; - only with unconnecting power and restart Bfgminer...

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: HellDiverUK on October 20, 2013, 09:15:43 AM

Oh, OK, so you're changing the terms, because classically a stratum proxy (like slush's one) allows a getwork client to mine on a stratum pool. Wink

Slush's Stratum proxy refers only to the upstream protocol.
It supports both getwork and Stratum clients. Wink

Quote from: HellDiverUK on October 20, 2013, 09:15:43 AM

So, back to the question - is the getwork proxy available on OpenWRT?

Should be.

HellDiverUK

hero member

Activity: 1246

Merit: 501

Oh, OK, so you're changing the terms, because classically a stratum proxy (like slush's one) allows a getwork client to mine on a stratum pool. Wink

That's cool, as long as I know what you're calling what.

So, back to the question - is the getwork proxy available on OpenWRT?

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: HellDiverUK on October 20, 2013, 09:06:26 AM

Quote from: Luke-Jr on October 20, 2013, 09:00:11 AM

The stratum proxy is fully supported on all platforms, including Win64.
It's only the getwork proxy that can't do Win64.

There's a difference?

Surely:
stratum proxy is for allowing getwork clients to mine on a stratum pool?
getwork proxy is for allowing getwork clients to mine on a stratum pool?

Confused. Huh

Stratum proxy is for allowing stratum clients to mine on stratum pool(s).
getwork proxy is for allowing getwork clients to mine on any pool(s).

HellDiverUK

hero member

Activity: 1246

Merit: 501

Quote from: Luke-Jr on October 20, 2013, 09:00:11 AM

The stratum proxy is fully supported on all platforms, including Win64.
It's only the getwork proxy that can't do Win64.

There's a difference?

Surely:
stratum proxy is for allowing getwork clients to mine on a stratum pool?
getwork proxy is for allowing getwork clients to mine on a stratum pool?

Confused. Huh

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: HellDiverUK on October 20, 2013, 07:46:24 AM

Quote from: Luke-Jr on October 18, 2013, 09:36:15 AM

Quote from: HellDiverUK on October 18, 2013, 02:51:39 AM

Luke-Jr, have you any idea if/when you'll be adding the stratum proxy module to the OpenWRT version of BFGMiner?

IIRC, it should be there in 3.3.0?

OK, cool. I didn't see anything specific in the READMEs about it being added, so assumed it was still not on OpenWRT, like it's still not on Win64 version.

I'll give it a spin sometime on OpenWRT...

The stratum proxy is fully supported on all platforms, including Win64.
It's only the getwork proxy that can't do Win64.

HellDiverUK

hero member

Activity: 1246

Merit: 501

Quote from: Luke-Jr on October 18, 2013, 09:36:15 AM

Quote from: HellDiverUK on October 18, 2013, 02:51:39 AM

Luke-Jr, have you any idea if/when you'll be adding the stratum proxy module to the OpenWRT version of BFGMiner?

IIRC, it should be there in 3.3.0?

OK, cool. I didn't see anything specific in the READMEs about it being added, so assumed it was still not on OpenWRT, like it's still not on Win64 version.

I'll give it a spin sometime on OpenWRT...

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: wmcorless on October 19, 2013, 11:59:12 PM

./bfgminer: --http-port: unrecognized option

This means libmicrohttpd wasn't found when you ran configure.

wmcorless

full member

Activity: 192

Merit: 100

paccoin

I'm trying to run ASICMINER Block Erupter Blades with BFGminer.
I'm running xubuntu and I installed the libmicrohttpd as was required.
However when I type:
./bfgminer --http-port 8330

I get this error:

./bfgminer: --http-port: unrecognized option

What am I doing wrong?

Also what should I put on the Blade for address and password?

Thanks.

Jimmy2011

hero member

Activity: 589

Merit: 500

Request for ppcoin solo mining support.

I tried to solo mining with bfgminer, however, it returned with a error message:

Code:

./bfgminer: --coinbase-addr: Invalid address

which seems that bfgminer only supports bitcoin address and doesn't support ppcoin address.

bitbanger

newbie

Activity: 9

Merit: 0

Hello..

Using bfgminer and a jalapeno..

When I press M to manage devices, I can then use up/down to select processor, but a couple times I did something to show all of them at once??? Anyone know how I did that or what is the command???

Thanks!

juhakall

sr. member

Activity: 658

Merit: 250

Quote from: dlasher on October 18, 2013, 03:28:56 PM

^^ perfect, thanks.. will go fix all my scripts.. Might want to update miner.php while you're at it to work with the API changes.

It already does. There is a $per_proc setting which controls how the data is displayed.

dlasher

sr. member

Activity: 467

Merit: 250

^^ perfect, thanks.. will go fix all my scripts.. Might want to update miner.php while you're at it to work with the API changes.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: dlasher on October 18, 2013, 03:24:29 PM

Luke-Jr:

Any reason why the extended-core information for BFL's (seeing all cores per Single, for example) went away from 3.2.90 to 3.3.0 via the API?

I used to get all 16 cores per single, now I see only summary information.

Per README.RPC...

Quote

API V2.0 (BFGMiner v3.3.0)

Removed API commands:
'devdetail' - Use newer 'devdetails' for same information.

Modified API commands:
'devs' - display status of each full device only (not processors)
'pga' - lookup and display device by device (not processor) number
'pgacount' - count only full devices (not processors)
'pgaenable' - enable all processors for a numbered full device
'pgadisable' - disable all processors for a numbered full device
'pgaidentify' - choose first processor of numbered full device
'pgaset' - choose first processor of numbered full device

Added API commands:
'procs'
'proc'
'proccount'
'procenable'
'procdisable'
'procidentify'
'procset'

dlasher

sr. member

Activity: 467

Merit: 250

Luke-Jr:

Any reason why the extended-core information for BFL's (seeing all cores per Single, for example) went away from 3.2.90 to 3.3.0 via the API?

I used to get all 16 cores per single, now I see only summary information.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: HellDiverUK on October 18, 2013, 02:51:39 AM

Luke-Jr, have you any idea if/when you'll be adding the stratum proxy module to the OpenWRT version of BFGMiner?

IIRC, it should be there in 3.3.0?

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