Author

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

legendary
Activity: 2576
Merit: 1186
Where is the version of bfgminer for android (not the bfl version)
You get to compile it yourself...
Could you be bribed.. with BTC?
Possibly, but when I looked at it last, it would be numerous hours to figure out how to build Android's bionic library sensibly.
On top of that, I haven't the slightest idea how to make an Android package or upload it to Google Play, and I suspect doing so might not be possible with free software. Sad

It'd probably be much faster/cheaper to find someone who does regular Android development. Smiley
hero member
Activity: 868
Merit: 1000
Where is the version of bfgminer for android (not the bfl version)
You get to compile it yourself...

Could you be bribed.. with BTC?
legendary
Activity: 2576
Merit: 1186
Where is the version of bfgminer for android (not the bfl version)
You get to compile it yourself...
hero member
Activity: 868
Merit: 1000
Where is the version of bfgminer for android (not the bfl version)
newbie
Activity: 47
Merit: 0
I installed Bfgminer 3.1.4 and everything was running fine.
I was tinkering around trying to build bitcoin-qt from source and changed a few things, now I get a bus error: 10 when I try to run Bfgminer 3.1.4 @ command prompt  (terminal) in Mac OS X 10.8.4

How do I fix it? I tried restarting, reinstalling and NOTHING seems to work... I am stuck using Mac Miner for now...


Seems to be an issue with Bfgminer, ran it once on a separate system (10.7 instead of 10.Cool and after shutting it down and restarting it, I get the same bus error and NOTHNG seems to fix it...
What gives?
hero member
Activity: 910
Merit: 1002
Yes, its working. And will need to disable BFL in the second instance now Smiley

Thank you
legendary
Activity: 2576
Merit: 1186
Hi Luke,
I cant disable my eruptors with --disable-icarus in my .bat. They working together with my BFL LS, but diff 32 is too high for them. I wanna run them with other worker with diff 1
--disable-icarus is a compile-time option.
-S erupter:noauto should do it
hero member
Activity: 910
Merit: 1002
Hi Luke,
I cant disable my eruptors with --disable-icarus in my .bat. They working together with my BFL LS, but diff 32 is too high for them. I wanna run them with other worker with diff 1
sr. member
Activity: 388
Merit: 250
Save A Life, Adopt a Pet Today!
Yeah, for more than 5 Gh/s or so you definitely want to use GBT or stratum with a difficulty much higher than 1 Smiley

Wow.. slap me in the head and call me stupid.. can't believe i missed that.

i find 32 diff on 50btc works real well for me on the us servers..
legendary
Activity: 2576
Merit: 1186
Yeah, for more than 5 Gh/s or so you definitely want to use GBT or stratum with a difficulty much higher than 1 Smiley
legendary
Activity: 2702
Merit: 1468
I started using BFGMiner with two BFL SC Singles. The actual hashrate just doesn't seem to add up:



49 GH/s literally going nowhere.  Huh

Its not the singles.  Its 50BTC.  See the AS number around 4500...  it is having trouble submitting to 50btc.

I have had similar problems -  high latency to the stratum server especially if you are in the US.

I have had MUCH better success mining it at:  pool-us.50btc.com:3333


Try that!

Rob

+1

Try eclipsemc.com or eligius.st, both work well with BFLs. 
sr. member
Activity: 388
Merit: 250
Save A Life, Adopt a Pet Today!
I started using BFGMiner with two BFL SC Singles. The actual hashrate just doesn't seem to add up:



49 GH/s literally going nowhere.  Huh

Its not the singles.  Its 50BTC.  See the AS number around 4500...  it is having trouble submitting to 50btc.

I have had similar problems -  high latency to the stratum server especially if you are in the US.

I have had MUCH better success mining it at:  pool-us.50btc.com:3333


Try that!

Rob
newbie
Activity: 9
Merit: 0
I started using BFGMiner with two BFL SC Singles. The actual hashrate just doesn't seem to add up:

http://i.imgur.com/uTIMDYp.jpg

49 GH/s literally going nowhere.  Huh
full member
Activity: 138
Merit: 100
Luke-Jr is standing for election to the board of the Bitcoin Foundation. If you like what he's contributed to Bitcoin so far and agree with his vision for Bitcoin "as a legal and widely utilized, decentralized replacement for fiat currencies", then:

Join the Bitcoin Foundation: https://bitcoinfoundation.org/support

Read Luke-Jr's full statement: http://eligius.st/~gateway/news/founder-stands-bitcoin-foundation-election
newbie
Activity: 47
Merit: 0
I installed Bfgminer 3.1.4 and everything was running fine.
I was tinkering around trying to build bitcoin-qt from source and changed a few things, now I get a bus error: 10 when I try to run Bfgminer 3.1.4 @ command prompt  (terminal) in Mac OS X 10.8.4

How do I fix it? I tried restarting, reinstalling and NOTHING seems to work... I am stuck using Mac Miner for now...
legendary
Activity: 2702
Merit: 1468
when the temperature reached 86 C on one BFL device, that device was not disabled.  Do I have to setup any other "auto" parameters for temp-cutoff to work?
After a careful review of the code in question:
  • --temp-cutoff acts when the temperature exceeds the argument. This is how BFGMiner/cgminer have always interpreted the value, so this is a documentation error.
  • While a device is resting, the hardware error counter continually increments. This is a regression in 3.1.4 (older versions worked correctly).
  • It works for me, with the above in mind.

Thanks Luke.  I noticed it is working when it hits around 89...with parameter set to 86.
member
Activity: 106
Merit: 10
These are bugs in your compiler and libcurl, fixed in newer versions of such, and harmless in any case. Smiley

Cool, thanks!
Josh
legendary
Activity: 2576
Merit: 1186
The program runs perfectly, hash rate is good, but should I be concerned about these compilation warnings?
Code:
util.c: In function ‘notifier_read’:
util.c:2564:2: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
util.c: In function ‘notifier_wake’:
util.c:2554:2: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
util.c: In function ‘json_rpc_call_completed’:
util.c:504:6: warning: call to ‘_curl_easy_getinfo_err_string’ declared with attribute warning: curl_easy_getinfo expects a pointer to char * for this info [enabled by default]
These are bugs in your compiler and libcurl, fixed in newer versions of such, and harmless in any case. Smiley
member
Activity: 106
Merit: 10
I just upgraded to bfgminer 3.1.4, rather impressed by the new display layout, I like the summary line and blue highlight at top!

The program runs perfectly, hash rate is good, but should I be concerned about these compilation warnings?

Quote
util.c: In function ‘notifier_read’:
util.c:2564:2: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
util.c: In function ‘notifier_wake’:
util.c:2554:2: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
util.c: In function ‘json_rpc_call_completed’:
util.c:504:6: warning: call to ‘_curl_easy_getinfo_err_string’ declared with attribute warning: curl_easy_getinfo expects a pointer to char * for this info [enabled by default]

Josh
legendary
Activity: 2576
Merit: 1186
when the temperature reached 86 C on one BFL device, that device was not disabled.  Do I have to setup any other "auto" parameters for temp-cutoff to work?
After a careful review of the code in question:
  • --temp-cutoff acts when the temperature exceeds the argument. This is how BFGMiner/cgminer have always interpreted the value, so this is a documentation error.
  • While a device is resting, the hardware error counter continually increments. This is a regression in 3.1.4 (older versions worked correctly).
  • It works for me, with the above in mind.
Jump to: