Topic: OLD: BFGMiner 4.10.0: GBT+Stratum, RPC, Mac/Linux/Win64, Spondoolies SP30 - page 30. (Read 308577 times)
June 26, 2014, 04:33:35 AM
Anyone running git should note that when updating, they will need to re-run autogen.sh to pull in the latest ccan from upstream.
June 25, 2014, 01:15:43 PM
The Si Labs drivers sometimes don't like to install on Win64. The Si Labs Cp210x FREE Tool includes the driver package and if you download and install the free tool, then the drivers will usually work.
I wonder if I'm having a driver problem because of this. I'm not sure what the "free tool" is, could you please provide a link? Thanks! 
http://www.silabs.com/products/mcu/Pages/USBXpress.aspx
This is for people having issues installing the USB to UART VCP 210x drivers, I have used this to install to Silabs 210x driver packed on 5 different computers that would not install the driver package on Windows 64 bit OS's. Bitmain Antminer U1 & U2 were the first that I personally needed these drivers but since then I believe a few other brands use these with BFGMiner.
It is a complete development tool so if you want to dig in and learn more its in there.
June 25, 2014, 12:46:51 PM
Use this to find the correct package:
sudo aptitude search uthash
A list of programs will come up. Just pick the -dev version that's at least 1.9.2. Then run apt-get update and apt-get upgrade to make sure you're up to snuff...
The search will only have 1 hit so use this:
sudo apt-get install uthash-dev
The other thing I did when I first started mining was to go to google and type in Linux BTCGuild and found the steps necessary to install a miner. Just get all the required programs first, then try installing BFGMiner
sudo aptitude search uthash
A list of programs will come up. Just pick the -dev version that's at least 1.9.2. Then run apt-get update and apt-get upgrade to make sure you're up to snuff...
The search will only have 1 hit so use this:
sudo apt-get install uthash-dev
The other thing I did when I first started mining was to go to google and type in Linux BTCGuild and found the steps necessary to install a miner. Just get all the required programs first, then try installing BFGMiner
Thanks for your hint, but it's always the same:
Quote
checking whether HASH_ITER is declared... no
configure: error: Could not find HASH_ITER - please install uthash-dev 1.9.4+
root@sunwatch:/usr/src/bfgminer# sudo aptitude search uthash
i uthash-dev - A hash table and linked list for C structures
root@sunwatch:/usr/src/bfgminer# sudo apt-get install uthash-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
uthash-dev is already the newest version.
The following packages were automatically installed and are no longer required:
libssh2-1-dev libssl-dev
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@sunwatch:/usr/src/bfgminer#
configure: error: Could not find HASH_ITER - please install uthash-dev 1.9.4+
root@sunwatch:/usr/src/bfgminer# sudo aptitude search uthash
i uthash-dev - A hash table and linked list for C structures
root@sunwatch:/usr/src/bfgminer# sudo apt-get install uthash-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
uthash-dev is already the newest version.
The following packages were automatically installed and are no longer required:
libssh2-1-dev libssl-dev
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@sunwatch:/usr/src/bfgminer#
regards
June 25, 2014, 10:09:42 AM
The Si Labs drivers sometimes don't like to install on Win64. The Si Labs Cp210x FREE Tool includes the driver package and if you download and install the free tool, then the drivers will usually work.
I wonder if I'm having a driver problem because of this. I'm not sure what the "free tool" is, could you please provide a link? Thanks! June 25, 2014, 10:08:50 AM
I'm still having issues with BFGminer and my Scrypt ASICs (GAWminer Fury and Gridseed Orbs). BFGminer will accept shares from my pool for about 5 minutes and then it hangs and does not receive any further shares. The hashrate will decline until I restart it. I've tried playing with my config file, changing FIFO buffers, different versions of BFGminer but the result is still the same. It runs and then proceeds to stop receiving shares shortly after it starts. CPUminer and CGminer both work without any issues, so I'm having trouble rooting out the issue with BFGminer. Does anyone have any ideas? Thanks!
June 25, 2014, 08:13:57 AM
June 25, 2014, 01:00:03 AM
June 24, 2014, 06:38:33 AM
Use this to find the correct package:
sudo aptitude search uthash
A list of programs will come up. Just pick the -dev version that's at least 1.9.2. Then run apt-get update and apt-get upgrade to make sure you're up to snuff...
The search will only have 1 hit so use this:
sudo apt-get install uthash-dev
The other thing I did when I first started mining was to go to google and type in Linux BTCGuild and found the steps necessary to install a miner. Just get all the required programs first, then try installing BFGMiner
sudo aptitude search uthash
A list of programs will come up. Just pick the -dev version that's at least 1.9.2. Then run apt-get update and apt-get upgrade to make sure you're up to snuff...
The search will only have 1 hit so use this:
sudo apt-get install uthash-dev
The other thing I did when I first started mining was to go to google and type in Linux BTCGuild and found the steps necessary to install a miner. Just get all the required programs first, then try installing BFGMiner
June 23, 2014, 11:51:49 PM
Thanks Luke.
That go me a step farther.
Now I got
configure: error: Could not find HASH_ITER - please install uthash-dev 1.9.2+
tried
install uthash-dev 1.9.2+
but, of course, that didn't work.
Don'cha just hate newbies
That go me a step farther.
Now I got
configure: error: Could not find HASH_ITER - please install uthash-dev 1.9.2+
tried
install uthash-dev 1.9.2+
but, of course, that didn't work.
Don'cha just hate newbies
but
Quote
root@sunwatch:~# sudo aptitude install uthash-dev
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
and than
Quote
cd /usr/src
wget http://luke.dashjr.org/programs/bitcoin/files/bfgminer/4.2.0/bfgminer-4.2.0.zip
unzip bfgminer-4.2.0.zip && mv bfgminer-4.2.0 bfgminer
cd bfgminer
sudo ./configure
sudo make
wget http://luke.dashjr.org/programs/bitcoin/files/bfgminer/4.2.0/bfgminer-4.2.0.zip
unzip bfgminer-4.2.0.zip && mv bfgminer-4.2.0 bfgminer
cd bfgminer
sudo ./configure
sudo make
always the same and I don't know?
Code:
checking whether HASH_ITER is declared... no
configure: error: Could not find HASH_ITER - please install uthash-dev 1.9.4+
On my Pi is the newest Kernel!?
greets
Can anyone help me, i don't know why i can't install bfgminer?
Regards
June 23, 2014, 04:48:52 PM
Is there any way bfgminer can be configured to 'reset' if it detects some of my gridseed miners have a low effective hashrate and/or are accepting few or zero shares (after say a given amount of time), rather than having to do this manually? I commonly have this issue with random gridseeds using multiminer despite having 'restart suspect/orphaned miners' checked in the program 
Other times its fine, but its entirely random
Other times its fine, but its entirely random
As quoted above, this software still isn't optimised to work with Gridseed blades.
I still find I have to manually restart the program until both blades hit the 2.5-2.7mh/s their capable of - often 1 of the blades will briefly go to anything up to 1mh/s or so in speed then completely drop off to 71kh/s (not sure why this speed but its common).
Also, an earlier modified version of bfgminer works better at getting all of the 5-chip miners working than this latest version does, which often fails to kick off several miners. cpu miner is better. It takes 10 minutes or so to bring all miners up to full speed but once its there its stable.
June 23, 2014, 04:09:23 PM
Is there a nice GUI for bfg other than Multiminer? Multiminer is not working on Ubuntu 12.04 LTS 64bit
June 23, 2014, 12:26:08 PM
Use MultiMiner.
It can seamlessly restart suspect and stuck miners. There is a check box for it.
I am using it to run 4 of them on two different coins.
https://bitcointalksearch.org/topic/multiminer-any-miner-any-where-on-any-device-free-open-source-cross-platform-248173
It uses BFGMiner to run them
The best software progs to use with these are MM with BFG and CrazyGuys custom cgminer.
I prefer MM and BFG as I get fewer errors and it is more stable.
It can seamlessly restart suspect and stuck miners. There is a check box for it.
I am using it to run 4 of them on two different coins.
https://bitcointalksearch.org/topic/multiminer-any-miner-any-where-on-any-device-free-open-source-cross-platform-248173
It uses BFGMiner to run them
The best software progs to use with these are MM with BFG and CrazyGuys custom cgminer.
I prefer MM and BFG as I get fewer errors and it is more stable.
Ok
i testet the latest version from BFG, i get alot of errors ( with RBOX Miner ) and shut down randomly ( 5 - 10 hours uptime )
u can see now, iam running only 22 minutes, and i get alot off errors
i tested the latest version from cgminer 4.1, no problems uptime 48+ hours
i testet the latest version from BFG, i get alot of errors ( with RBOX Miner ) and shut down randomly ( 5 - 10 hours uptime )
u can see now, iam running only 22 minutes, and i get alot off errors
i tested the latest version from cgminer 4.1, no problems uptime 48+ hours
June 23, 2014, 03:21:49 AM
and the shutdown randomly ( 4 - 10 hours uptime ) i get a sick ?
That's what I mean by "hang". 
June 23, 2014, 03:17:31 AM
and the shutdown randomly ( 4 - 10 hours uptime ) i get a sick ?
June 23, 2014, 03:11:15 AM
i testet the latest version from BFG, i get alot of errors ( with RBOX Miner ) and shut down randomly ( 5 - 10 hours uptime )
u can see now, iam running only 22 minutes, and i get alot off errors
i tested the latest version from cgminer 4.1, no problems uptime 48+ hours
Those errors are "normal" with current R-Boxen.u can see now, iam running only 22 minutes, and i get alot off errors
i tested the latest version from cgminer 4.1, no problems uptime 48+ hours
cgminer just doesn't report them.
The hangs are fixed in git (to-be 4.3).
June 23, 2014, 03:09:37 AM
Ok
i testet the latest version from BFG, i get alot of errors ( with RBOX Miner ) and shut down randomly ( 5 - 10 hours uptime )
u can see now, iam running only 22 minutes, and i get alot off errors
i tested the latest version from cgminer 4.1, no problems uptime 48+ hours
i testet the latest version from BFG, i get alot of errors ( with RBOX Miner ) and shut down randomly ( 5 - 10 hours uptime )
u can see now, iam running only 22 minutes, and i get alot off errors
i tested the latest version from cgminer 4.1, no problems uptime 48+ hours
June 22, 2014, 10:42:30 PM
Update: Managed to get the RBox working using MultiMiner. Long thread https://bitcointalksearch.org/topic/multiminer-any-miner-any-where-on-any-device-free-open-source-cross-platform-248173. Last page has the help I got with the drivers. The same driver may help with native BFG as well.
June 22, 2014, 09:40:55 PM
Quick FYI: On Linux, I strongly advise NOT trying to use -S bitforce:all
I just noticed this attempts to open and talk to every single PCI device.
That could be very bad...
Will fix in next release.
I just noticed this attempts to open and talk to every single PCI device.
That could be very bad...
Will fix in next release.
June 22, 2014, 06:46:33 PM
Hey folks!
I'm bumping this because it's still a problem. Can someone please give me a hand in fixing this? Thanks!
I'm having a problem with bfgminer (both the new 4.2.0 version and the 4.1.99 jstefanop fork) with failover for both gridseed and zeus (GAWMiner fury) rigs. Because it's happening with both versions I'm sure it's something dumb. so I thought I'd seek help here.
What's happening is that failover works going from pool 1 to pool 0 when pool 0 becomes active, but it doesn't work when pool 0 goes dead. Bfgminer reports that it has switched back to pool 1 but the pool doesn't show any hashrate. As well, my external monitor (CgminerMonitor version 0.7.0) shows the rig as still connected to pool 0. Finally, I'm getting the following messages displayed in bfgminer:
When it's doing this, it sometimes changes the network difficulty several times, then give the "pool 0 slow/down" message again, but it's not accepting shares.
Here's how I'm running bfgminer for the furys:
/root/bfgminer/bfgminer --scrypt -S zeus:/dev/ttyUSB0 --nocheck-golden --chips-count 6 --ltc-clk 328 --config=/opt/cgminer/cgminer_conf/cgminer-ttyUSB0.conf
and here's the config file:
Can anyone see any errors in this or offer any suggestions on how to fix this problem?
Thanks!
Regards,
Chris
I'm bumping this because it's still a problem. Can someone please give me a hand in fixing this? Thanks!
I'm having a problem with bfgminer (both the new 4.2.0 version and the 4.1.99 jstefanop fork) with failover for both gridseed and zeus (GAWMiner fury) rigs. Because it's happening with both versions I'm sure it's something dumb. so I thought I'd seek help here.
What's happening is that failover works going from pool 1 to pool 0 when pool 0 becomes active, but it doesn't work when pool 0 goes dead. Bfgminer reports that it has switched back to pool 1 but the pool doesn't show any hashrate. As well, my external monitor (CgminerMonitor version 0.7.0) shows the rig as still connected to pool 0. Finally, I'm getting the following messages displayed in bfgminer:
Code:
[2014-06-16 19:26:49] Pool 0 slow/down or URL or credentials invalid
[2014-06-16 19:27:02] Network difficulty changed to 792 ( 5.68G)
When it's doing this, it sometimes changes the network difficulty several times, then give the "pool 0 slow/down" message again, but it's not accepting shares.
Here's how I'm running bfgminer for the furys:
/root/bfgminer/bfgminer --scrypt -S zeus:/dev/ttyUSB0 --nocheck-golden --chips-count 6 --ltc-clk 328 --config=/opt/cgminer/cgminer_conf/cgminer-ttyUSB0.conf
and here's the config file:
Code:
{
"pools" : [
{
"url" : "stratum+tcp://r6284.g21.rigs.eu.betarigs.com:9116",
"user" : "chrison999-6284",
"pass" : "x"
},
{
"url" : "stratum+tcp://pool.ipominer.com:3333",
"user" : "corion49.USB0",
"pass" : "x"
}
]
,
"failover-only" : true,
"failover-switch-delay" : "240",
"api-listen" : true,
"api-mcast-port" : "4035",
"api-port" : "4035",
"expiry" : "120",
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "30",
"scrypt" : true,
"shares" : "0",
"kernel-path" : "/usr/local/bin",
"api-allow" : "W:127.0.0.1",
"usb" : ":1",
"request-diff" : "512",
"cmd-sick" : "pkill -9 bfgminer0",
"cmd-dead" : "pkill -9 bfgminer0",
"gridseed-options" : "baud=115200,freq=838,chips=40,modules=1,usefifo=0"
}
Can anyone see any errors in this or offer any suggestions on how to fix this problem?
Thanks!
Regards,
Chris
June 22, 2014, 05:29:56 AM
Finally upgraded one of my random thumb miner rigs (mix of Antminer U1's, U2's, RedFury, Bi*Fury, Drillbit Thumbs and a few Block Erupters) from old BFGminer 3.10.0 to 4.2.0.
Seeing two odd behaviors when starting updated bfgminer with this particular rig:
1. It starts up with the third pool in my priority list for half a minute before switching to the primary pool (third pool is BTCGuild while first and second are P2Pool nodes). Not a big deal, but just wondering the reason why it thinks P2Pool nodes are dead at first before recognizing them as alive after half a minute. The old 3.x.x versions didn't do this. They immediately startup and connect to the p2pool nodes.
2. Only 1 of my 3 Drillbit Thumbs start hashing immediately after I startup bfgminer. The other two show 0.00/0.00/0.00 until I manually pull them and reseat them in the USB socket (hot plugging) and then automagically bfgminer pick them up and starts hashing away. This is also not a big deal, but if I have to restart BFGMiner, I have to hot plug those two Drillbit Thumbs again, which won't be convenient if I'm doing it from remote. The weird thing is, that it only occurs for 2 of the 3 Drillbits, with the "middle one" having no problem starting up. All three are defined in my conf file with direct USB assignments.
Seeing two odd behaviors when starting updated bfgminer with this particular rig:
1. It starts up with the third pool in my priority list for half a minute before switching to the primary pool (third pool is BTCGuild while first and second are P2Pool nodes). Not a big deal, but just wondering the reason why it thinks P2Pool nodes are dead at first before recognizing them as alive after half a minute. The old 3.x.x versions didn't do this. They immediately startup and connect to the p2pool nodes.
2. Only 1 of my 3 Drillbit Thumbs start hashing immediately after I startup bfgminer. The other two show 0.00/0.00/0.00 until I manually pull them and reseat them in the USB socket (hot plugging) and then automagically bfgminer pick them up and starts hashing away. This is also not a big deal, but if I have to restart BFGMiner, I have to hot plug those two Drillbit Thumbs again, which won't be convenient if I'm doing it from remote. The weird thing is, that it only occurs for 2 of the 3 Drillbits, with the "middle one" having no problem starting up. All three are defined in my conf file with direct USB assignments.
Jump to: