Where is the version of bfgminer for android (not the bfl version)
You get to compile it yourself... 
Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 140. (Read 1193368 times)
August 14, 2013, 04:19:38 PM
August 14, 2013, 02:32:07 PM
Where is the version of bfgminer for android (not the bfl version)
August 14, 2013, 10:47:50 AM
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...
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.
and after shutting it down and restarting it, I get the same bus error and NOTHNG seems to fix it... What gives?
August 14, 2013, 05:32:22 AM
Yes, its working. And will need to disable BFL in the second instance now 
Thank you
Thank you
August 14, 2013, 04:48:55 AM
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.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
-S erupter:noauto should do it
August 14, 2013, 03:46:51 AM
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
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
August 13, 2013, 10:29:41 PM
Yeah, for more than 5 Gh/s or so you definitely want to use GBT or stratum with a difficulty much higher than 1
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..
August 13, 2013, 10:24:14 PM
Yeah, for more than 5 Gh/s or so you definitely want to use GBT or stratum with a difficulty much higher than 1
August 13, 2013, 10:01:36 PM
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.
49 GH/s literally going nowhere.
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
August 13, 2013, 09:52:32 PM
I started using BFGMiner with two BFL SC Singles. The actual hashrate just doesn't seem to add up:
https://i.imgur.com/uTIMDYp.jpg
49 GH/s literally going nowhere.
https://i.imgur.com/uTIMDYp.jpg
49 GH/s literally going nowhere.
August 13, 2013, 06:21:11 PM
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
Join the Bitcoin Foundation: https://bitcoinfoundation.org/support
Read Luke-Jr's full statement: http://eligius.st/~gateway/news/founder-stands-bitcoin-foundation-election
August 13, 2013, 11:02:32 AM
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...
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...
August 13, 2013, 02:42:03 AM
These are bugs in your compiler and libcurl, fixed in newer versions of such, and harmless in any case.
Cool, thanks!
Josh
Cool, thanks!
Josh
August 13, 2013, 02:17:33 AM
The program runs perfectly, hash rate is good, but should I be concerned about these compilation warnings?
These are bugs in your compiler and libcurl, fixed in newer versions of such, and harmless in any case. 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]
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]
August 13, 2013, 01:37:13 AM
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?
Josh
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]
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
August 13, 2013, 01:33:48 AM
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.
August 11, 2013, 06:11:08 PM
Quote
Anyone else all of a sudden start having their ESET or other virus program start flagging BFG? Was alwasy good, never had a problem before (but cgminer would get picked up). Now here within the last week or so ESET is flagging BFG.
IMO, "antivirus" software that takes the easy way out by flagging commonly abused software as more than merely a warning, is itself malware.
They should be looking for the virus/trojan itself, not the common software they use.
IMO, "antivirus" software that takes the easy way out by flagging commonly abused software as more than merely a warning, is itself malware.
They should be looking for the virus/trojan itself, not the common software they use.
Sadly i found many other private clients from being infected by a bfgminer/cgminer/minerd instance
Hidden in a self starting proces called adobe, so it looks some botnet builders are using the miner to run them illegal
These unknowing customers have no clue that its not normal that their gpu is blazing like mad so they complain and ofcourse some specialist find that its caused by the secretly installed miners.
If this is done by people they know or by botnet owners or usage of illegal software i do not know.
Ofcourse some of them report their findings to the av companies, and to be honest even though its annoying they are right
But fact is that this causes all anti virus makers to flag the miners as nasty software.
Flag that, not the legit software it's abusing.
August 11, 2013, 12:19:36 PM
Thanks I thought I had some phantom block erupter problem.
I thought I had some phantom block erupter problem. August 11, 2013, 12:11:35 PM
Hey there, I`m having a little issue with my block erupters on BFG 3.1.4. I appears like BFG might be adding a phantom erupter, and so I have two number 9`s. 
Any ideas?
The only way i`ve managed to get rid of this is to restart bfg, but I`d like to keep it going.
Thanks.
It's just a rendering glitch if they have the same id. Any ideas?
The only way i`ve managed to get rid of this is to restart bfg, but I`d like to keep it going.
Thanks.
August 11, 2013, 12:04:08 PM
Hey there, I`m having a little issue with my block erupters on BFG 3.1.4. I appears like BFG might be adding a phantom erupter, and so I have two number 9`s.
Any ideas?
The only way i`ve managed to get rid of this is to restart bfg, but I`d like to keep it going.
Thanks.
Any ideas?
The only way i`ve managed to get rid of this is to restart bfg, but I`d like to keep it going.
Thanks.
Jump to: