Got 4.2.0 compiled and working on Rasberry Pi (Arch/Minepeon)
it wasn't able to detect the R-BOX's though. Is this a thing where I have to program the chips on the miners to identify themselves properly?
Topic: OLD: BFGMiner 4.10.0: GBT+Stratum, RPC, Mac/Linux/Win64, Spondoolies SP30 - page 37. (Read 308577 times)
June 11, 2014, 11:11:52 AM
June 11, 2014, 10:36:48 AM
Is there a way to set the clocking for each antminer (u1's) separately?
I am currently running two instances of BFGminer to run my mix of antminers, Bifury's and 1 Nanofury. I would like to be able to consolidate and only run one instance in one command window if possible. The reason I need to run separate clocking is that 2 of the ants will not run stable at more than 1.8 Gh/s or the 0881 so I run them on one instance along with my nanofury and bifury and run the other 7 ants 2.0 in a second instance.
Please let me know if this is possible and if so how to structure the command line to do so.
Thanks
I am currently running two instances of BFGminer to run my mix of antminers, Bifury's and 1 Nanofury. I would like to be able to consolidate and only run one instance in one command window if possible. The reason I need to run separate clocking is that 2 of the ants will not run stable at more than 1.8 Gh/s or the 0881 so I run them on one instance along with my nanofury and bifury and run the other 7 ants 2.0 in a second instance.
Please let me know if this is possible and if so how to structure the command line to do so.
Thanks
For each device:
--set ant@
I believe or something similar
I'd love to see someones working conf file that does work so we can figure it out once and for all.
I settled on 2 instances and dealing with it. It took less time in the end to configure it that way. PITA with all the files now.
I think I have it working for now. I have the two that can not run more than 180 running 180 and the others running 200 on one instance of BFGminer . Now to see if they will do so while on the same hub. I will try that perhaps tomorrow and let you know. Currently I am using the following command line to start my rig loaded with 9 ants, 7 bifurys, and one nanofury twin.
bfgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u user -p x -S antminer:all -d antminer@\\.\COM3 --set antminer@\\.\COM3:clock=x0881 -d antminer@\\.\COM4 --set antminer@\\.\COM4:clock=x0881 -d antminer@\\.\COM5 --set antminer@\\.\COM5:clock=x0981 -d antminer@\\.\COM6 --set antminer@\\.\COM6:clock=x0981 -d antminer@\\.\COM7 --set antminer@\\.\COM7:clock=x0981 -d antminer@\\.\COM8 --set antminer@\\.\COM8:clock=x0981 -d antminer@\\.\COM9 --set antminer@\\.\COM9:clock=x0981 -d antminer@\\.\COM10 --set antminer@\\.\COM10:clock=x0981 -d antminer@\\.\COM11 --set antminer@\\.\COM11:clock=x0981 -S bfx:all --set bfx:osc6_bits=54
So I was going to send a buck for the example. but since I've been out of the scene for a long time I see the new qt client won't send without
adding a fee regardless. So I need to figure out the rawtransaction command.. Otherwise the fee is a joke for such a small amount.
June 11, 2014, 10:17:11 AM
Any chance that the GAWMiner products will be supported? I'm thinking about getting a Fury or 10 (mostly because I don't want to have to buy a PSU and cables and try to splice S*** together). I know that there is a CGminer fork, which I use for my gridseeds because there were problems running BFGminer where the 3 miners would hash but one stopped submitting shares using windows 7, and the version I put on my Pi would stop seeing them altogether after a few minutes.
I would just rather use BFGMiner because I'm more familiar with it, plus you guys keep pumping out upgrades...
I would just rather use BFGMiner because I'm more familiar with it, plus you guys keep pumping out upgrades...
We should have both a GAW branded Zeusminer and a stock Zeusminer coming. They will be supported in BFGMiner once we receive them and proper documentation.
YAY!!!
/bow to N.Wools!
June 11, 2014, 10:12:25 AM
Any chance that the GAWMiner products will be supported? I'm thinking about getting a Fury or 10 (mostly because I don't want to have to buy a PSU and cables and try to splice S*** together). I know that there is a CGminer fork, which I use for my gridseeds because there were problems running BFGminer where the 3 miners would hash but one stopped submitting shares using windows 7, and the version I put on my Pi would stop seeing them altogether after a few minutes.
I would just rather use BFGMiner because I'm more familiar with it, plus you guys keep pumping out upgrades...
I would just rather use BFGMiner because I'm more familiar with it, plus you guys keep pumping out upgrades...
We should have both a GAW branded Zeusminer and a stock Zeusminer coming. They will be supported in BFGMiner once we receive them and proper documentation.
June 11, 2014, 09:45:36 AM
Any chance that the GAWMiner products will be supported? I'm thinking about getting a Fury or 10 (mostly because I don't want to have to buy a PSU and cables and try to splice S*** together). I know that there is a CGminer fork, which I use for my gridseeds because there were problems running BFGminer where the 3 miners would hash but one stopped submitting shares using windows 7, and the version I put on my Pi would stop seeing them altogether after a few minutes.
I would just rather use BFGMiner because I'm more familiar with it, plus you guys keep pumping out upgrades...
I would just rather use BFGMiner because I'm more familiar with it, plus you guys keep pumping out upgrades...
June 11, 2014, 09:33:56 AM
NEW VERSION 4.2.0, JUNE 11 2014
Human readable changelog:
Full changelog:
Human readable changelog:
- rockminer: New driver for ROCKMINER R-BOX.
Full changelog:
- Upgraded Windows libmicrohttpd from 0.9.35 to 0.9.38_pre33603
- SGW: Workaround BE Cube bugs with new libmicrohttpd by forcing HTTP 1.0 response
- rockminer: Increase hw error count for problems
- rockminer: Autodetect with "R-BOX miner" or "RX-BOX miner" product strings
- rockminer: Support for seeing and setting clock frequency in Manage TUI
- rockminer: Include clock frequency in RPC processor status
- rockminer: Support for setting clock frequency
- rockminer: Workaround lost tasks by resending them
- rockminer: Support for temperature sensors
- rockminer: Debug messages
- Bugfix: rockminer: Initialise rockminer_chip_data
- Bugfix: rockminer: Ensure work actually exists before testing against it
- rockminer: Mine at 270 MHz
- rockminer: Implement mining (at 200 MHz)
- DevAPI: Move device_proc_by_id out of bifury driver, since it is generically useful
- rockminer: Detection code for new driver
- bfg_socket wrapper to ensure sockets are close-on-exec
- set_cloexec_socket: Explicitly cast SOCKET to HANDLE
Thank you Luke, you are my favorite person today. High Five.
June 11, 2014, 04:25:11 AM
Very cool.
Thanks for the great work as always Luke.
Thanks for the great work as always Luke.
NEW VERSION 4.2.0, JUNE 11 2014
Human readable changelog:
Full changelog:
Human readable changelog:
- rockminer: New driver for ROCKMINER R-BOX.
Full changelog:
- Upgraded Windows libmicrohttpd from 0.9.35 to 0.9.38_pre33603
- SGW: Workaround BE Cube bugs with new libmicrohttpd by forcing HTTP 1.0 response
- rockminer: Increase hw error count for problems
- rockminer: Autodetect with "R-BOX miner" or "RX-BOX miner" product strings
- rockminer: Support for seeing and setting clock frequency in Manage TUI
- rockminer: Include clock frequency in RPC processor status
- rockminer: Support for setting clock frequency
- rockminer: Workaround lost tasks by resending them
- rockminer: Support for temperature sensors
- rockminer: Debug messages
- Bugfix: rockminer: Initialise rockminer_chip_data
- Bugfix: rockminer: Ensure work actually exists before testing against it
- rockminer: Mine at 270 MHz
- rockminer: Implement mining (at 200 MHz)
- DevAPI: Move device_proc_by_id out of bifury driver, since it is generically useful
- rockminer: Detection code for new driver
- bfg_socket wrapper to ensure sockets are close-on-exec
- set_cloexec_socket: Explicitly cast SOCKET to HANDLE
June 11, 2014, 02:58:52 AM
I'm glad to see people are actually verifying the PGP signatures, but before you report that my key expired, please update your copy from the keyserver, as I updated the expiration date already 
June 11, 2014, 01:56:49 AM
NEW VERSION 4.2.0, JUNE 11 2014
Human readable changelog:
Full changelog:
Human readable changelog:
- rockminer: New driver for ROCKMINER R-BOX.
Full changelog:
- Upgraded Windows libmicrohttpd from 0.9.35 to 0.9.38_pre33603
- SGW: Workaround BE Cube bugs with new libmicrohttpd by forcing HTTP 1.0 response
- rockminer: Increase hw error count for problems
- rockminer: Autodetect with "R-BOX miner" or "RX-BOX miner" product strings
- rockminer: Support for seeing and setting clock frequency in Manage TUI
- rockminer: Include clock frequency in RPC processor status
- rockminer: Support for setting clock frequency
- rockminer: Workaround lost tasks by resending them
- rockminer: Support for temperature sensors
- rockminer: Debug messages
- Bugfix: rockminer: Initialise rockminer_chip_data
- Bugfix: rockminer: Ensure work actually exists before testing against it
- rockminer: Mine at 270 MHz
- rockminer: Implement mining (at 200 MHz)
- DevAPI: Move device_proc_by_id out of bifury driver, since it is generically useful
- rockminer: Detection code for new driver
- bfg_socket wrapper to ensure sockets are close-on-exec
- set_cloexec_socket: Explicitly cast SOCKET to HANDLE
June 11, 2014, 12:59:45 AM
Is there a way to set the clocking for each antminer (u1's) separately?
I am currently running two instances of BFGminer to run my mix of antminers, Bifury's and 1 Nanofury. I would like to be able to consolidate and only run one instance in one command window if possible. The reason I need to run separate clocking is that 2 of the ants will not run stable at more than 1.8 Gh/s or the 0881 so I run them on one instance along with my nanofury and bifury and run the other 7 ants 2.0 in a second instance.
Please let me know if this is possible and if so how to structure the command line to do so.
Thanks
I am currently running two instances of BFGminer to run my mix of antminers, Bifury's and 1 Nanofury. I would like to be able to consolidate and only run one instance in one command window if possible. The reason I need to run separate clocking is that 2 of the ants will not run stable at more than 1.8 Gh/s or the 0881 so I run them on one instance along with my nanofury and bifury and run the other 7 ants 2.0 in a second instance.
Please let me know if this is possible and if so how to structure the command line to do so.
Thanks
For each device:
--set ant@
I believe or something similar
I'd love to see someones working conf file that does work so we can figure it out once and for all.
I settled on 2 instances and dealing with it. It took less time in the end to configure it that way. PITA with all the files now.
I think I have it working for now. I have the two that can not run more than 180 running 180 and the others running 200 on one instance of BFGminer . Now to see if they will do so while on the same hub. I will try that perhaps tomorrow and let you know. Currently I am using the following command line to start my rig loaded with 9 ants, 7 bifurys, and one nanofury twin.
bfgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u user -p x -S antminer:all -d antminer@\\.\COM3 --set antminer@\\.\COM3:clock=x0881 -d antminer@\\.\COM4 --set antminer@\\.\COM4:clock=x0881 -d antminer@\\.\COM5 --set antminer@\\.\COM5:clock=x0981 -d antminer@\\.\COM6 --set antminer@\\.\COM6:clock=x0981 -d antminer@\\.\COM7 --set antminer@\\.\COM7:clock=x0981 -d antminer@\\.\COM8 --set antminer@\\.\COM8:clock=x0981 -d antminer@\\.\COM9 --set antminer@\\.\COM9:clock=x0981 -d antminer@\\.\COM10 --set antminer@\\.\COM10:clock=x0981 -d antminer@\\.\COM11 --set antminer@\\.\COM11:clock=x0981 -S bfx:all --set bfx:osc6_bits=54
June 10, 2014, 11:09:14 PM
Does anybody have BFGMiner working as a scrypt proxy?
June 10, 2014, 07:01:39 PM
It's occured for me first under win 7 & now under win 8, on 2 different PC's using both G-Blade & Orbs. I've looked at power supplies, Com Port settings, cabling..you name it. IMO its some sort of 'initilization issue' as either the miner/s will kick off and start accepting shares or they wont (until next time bfgminer is restarted & the device/s are reinitialized), though I have seen cases where a miner will accept a couple of shares then nothing.
If you are using MultiMiner and have it set to restart "suspect" miners it should pick up on miners that have a low effective hashrate.
Also note that, depending on the pool difficulty and luck, it may take a bit for things to play out.
Yea it is set to restart and I've let the miners run for quite some time with no shares. I'm wondering if this is just erroneous reporting in MM? I'll try running the miners from bfgminer directly and see if I still get zero shares accepted. If I dont, I'm going to somehow have to try and do a compare between shares reported in MM versus actual shares accepted on a pool.
June 10, 2014, 06:18:32 PM
It's occured for me first under win 7 & now under win 8, on 2 different PC's using both G-Blade & Orbs. I've looked at power supplies, Com Port settings, cabling..you name it. IMO its some sort of 'initilization issue' as either the miner/s will kick off and start accepting shares or they wont (until next time bfgminer is restarted & the device/s are reinitialized), though I have seen cases where a miner will accept a couple of shares then nothing.
If you are using MultiMiner and have it set to restart "suspect" miners it should pick up on miners that have a low effective hashrate.
Also note that, depending on the pool difficulty and luck, it may take a bit for things to play out.
June 10, 2014, 04:35:53 PM
Thanks, Nate. That worked, I thought I had to replace the INF in another driver package in order to get it to work.
However, I have the same problem that Oldminer mentioned above: BFGminer find the Gridseed Orbs and mines fine for the first while. After about 30 or so minutes, the speed drops and they eventually stop accepting shares. I have read about the FIFO buffers and tried messing with those, but it seems to behave the same with them enabled or disabled. Any ideas? I'm using BFGminer 4.1 on Windows 7.
However, I have the same problem that Oldminer mentioned above: BFGminer find the Gridseed Orbs and mines fine for the first while. After about 30 or so minutes, the speed drops and they eventually stop accepting shares. I have read about the FIFO buffers and tried messing with those, but it seems to behave the same with them enabled or disabled. Any ideas? I'm using BFGminer 4.1 on Windows 7.
I've unfortunately never seen such an issue with any Orbs, Blades, or DMUs on any of the OSs I have setup for testing and dev.
It's occured for me first under win 7 & now under win 8, on 2 different PC's using both G-Blade & Orbs. I've looked at power supplies, Com Port settings, cabling..you name it. IMO its some sort of 'initilization issue' as either the miner/s will kick off and start accepting shares or they wont (until next time bfgminer is restarted & the device/s are reinitialized), though I have seen cases where a miner will accept a couple of shares then nothing.
June 10, 2014, 01:33:25 PM
SHA2 is not supported for these, only scrypt.
dude do you know of a bfgminer Fork that will let me mine sha with a gridseed?
I can't stand the cgminer for gridseed
it sux!!!
I don't get why you would not add sha for gridseed???
your the guy who was like I don't really care about scrypt & yet you add scrypt for gridseed
that's a big Assumption
how do you know I have not giving him a donation before.
as for adding the support
the work has been done for the most part, he just has to add it to bfgminer.
June 10, 2014, 11:44:34 AM
SHA2 is not supported for these, only scrypt.
dude do you know of a bfgminer Fork that will let me mine sha with a gridseed?
I can't stand the cgminer for gridseed
it sux!!!
I don't get why you would not add sha for gridseed???
your the guy who was like I don't really care about scrypt & yet you add scrypt for gridseed
that's a big Assumption
how do you know I have not giving him a donation before.
as for adding the support
the work has been done for the most part, he just has to add it to bfgminer.
June 10, 2014, 10:41:56 AM
SHA2 is not supported for these, only scrypt.
dude do you know of a bfgminer Fork that will let me mine sha with a gridseed?
I can't stand the cgminer for gridseed
it sux!!!
I don't get why you would not add sha for gridseed???
your the guy who was like I don't really care about scrypt & yet you add scrypt for gridseed
June 10, 2014, 10:22:29 AM
Thanks, Nate. That worked, I thought I had to replace the INF in another driver package in order to get it to work.
However, I have the same problem that Oldminer mentioned above: BFGminer find the Gridseed Orbs and mines fine for the first while. After about 30 or so minutes, the speed drops and they eventually stop accepting shares. I have read about the FIFO buffers and tried messing with those, but it seems to behave the same with them enabled or disabled. Any ideas? I'm using BFGminer 4.1 on Windows 7.
However, I have the same problem that Oldminer mentioned above: BFGminer find the Gridseed Orbs and mines fine for the first while. After about 30 or so minutes, the speed drops and they eventually stop accepting shares. I have read about the FIFO buffers and tried messing with those, but it seems to behave the same with them enabled or disabled. Any ideas? I'm using BFGminer 4.1 on Windows 7.
I've unfortunately never seen such an issue with any Orbs, Blades, or DMUs on any of the OSs I have setup for testing and dev.
June 10, 2014, 10:20:46 AM
Could you provide a little more detail, please? I'm uncertain what to do with this INF file, as I'm assuming from your post I actually need the drivers from elsewhere but am not sure where to obtain them. I presume I need the INF file to install the drivers. I have the official (non-zadig) drivers installed (noted above) but you remarked they are not the same. Any clarification you could offer would be much appreciated
When Windows prompts you to install a driver, one of the options is to browse for an INF file. In this case browse to the GridSeed INF file found in the link I provided.
In the case of Windows 7 and 8 and 8.1 you will need to take extra steps (different for each) to install unsigned drivers.
However, I have the same problem that Oldminer mentioned above: BFGminer find the Gridseed Orbs and mines fine for the first while. After about 30 or so minutes, the speed drops and they eventually stop accepting shares. I have read about the FIFO buffers and tried messing with those, but it seems to behave the same with them enabled or disabled. Any ideas? I'm using BFGminer 4.1 on Windows 7.
June 10, 2014, 09:57:40 AM
SHA2 is not supported for these, only scrypt.
dude do you know of a bfgminer Fork that will let me mine sha with a gridseed?
I can't stand the cgminer for gridseed
it sux!!!
I don't get why you would not add sha for gridseed???
your the guy who was like I don't really care about scrypt & yet you add scrypt for gridseed
Jump to: