Using ASICS miners etc on Bitcoin
- robmacagain
- Boinc Warrant Officer Class 2
- Posts: 322
- Joined: Tue Apr 12, 2011 3:53 pm
- Location: Sassenachshire
#131 Re: Using ASICS miners etc on Bitcoin
ha ha keck me, < that was it, why couldn't I see that, have added it and restarted it and now its doing only 1, nice one mate .
And no it loaded it and ran it, it was that less than symbol DOH!!!
And no it loaded it and ran it, it was that less than symbol DOH!!!
#132 Re: Using ASICS miners etc on Bitcoin
Tis a picky wee booger at times
The best form of help from above is a sniper on the rooftop....
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#133 Re: Using ASICS miners etc on Bitcoin
BU changed their cgminer command line default to use the option --usb :1, which tells cgminer to use only 1 ASIC. Not a huge problem if you only have one ASIC or are running a version of BOINC that supports the cc_config.xml and and app_config.xml options which use the miner_asic value, but my raspberry pi's only have BOINC 7.0.27 so I'm stuck running a 1 r3 blade instead of 4 on one rpi and a 1 box instead of 6 on the other until I can install a version that supports it. I don't think there's a good install process for the latest version where you don't have to manually update the scripts to control the BOINC client. I'm not a linux admin, so I feel like I'm crawling around in the dark doing that.
#134 Re: Using ASICS miners etc on Bitcoin
can you not set the count option in cc_config to the number of miners you have ?
and for the r4 set count to 4 not 1.
Of course you can't do that without 7.4.22 + doooh.
Have you tried changing max concurrent to 4 on the r4 and see if it works that way ? otherwise I guess it's stick them back on a windows box for now or get the new version of Boinc. Is the version specific for the pi or can you run the linux version of Boinc ?
and for the r4 set count to 4 not 1.
Of course you can't do that without 7.4.22 + doooh.
Have you tried changing max concurrent to 4 on the r4 and see if it works that way ? otherwise I guess it's stick them back on a windows box for now or get the new version of Boinc. Is the version specific for the pi or can you run the linux version of Boinc ?
The best form of help from above is a sniper on the rooftop....
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#135 Re: Using ASICS miners etc on Bitcoin
I assume it requires a version built to run on a pi. Doesn't every linux install require a processor specific build?Alez wrote:Is the version specific for the pi or can you run the linux version of Boinc ?
I can get 7.4.22 installed, but how to do you set it up to as a daemon and stop it?
#136 Re: Using ASICS miners etc on Bitcoin
linux is pretty generic though I guess the pi is arm based ?
I would also guess that what you are running is basically ubuntu / debian based linux ?
if so I guess you have been running boinc using
/etc/init.d/boinc-client start to start the service and
/etc/init.d/boinc-client stop to stop the service from root ( sudo ) ?
if so to make it run as a deamon issue this command from shell ( can't remember if you need sudo or not, to be honest I normally just do everything from root, saves messing with permissions all the time )
sudo update-rc.d -f boinc-client remove ( just incase it is there already )
sudo update-rc.d boinc-client defaults 99
this should load boinc as the 99 or hopefully last item in the deamon start up service list
That should be it, unless you run into permission problems in which case you will need to add yourself to the boinc group.
I would also guess that what you are running is basically ubuntu / debian based linux ?
if so I guess you have been running boinc using
/etc/init.d/boinc-client start to start the service and
/etc/init.d/boinc-client stop to stop the service from root ( sudo ) ?
if so to make it run as a deamon issue this command from shell ( can't remember if you need sudo or not, to be honest I normally just do everything from root, saves messing with permissions all the time )
sudo update-rc.d -f boinc-client remove ( just incase it is there already )
sudo update-rc.d boinc-client defaults 99
this should load boinc as the 99 or hopefully last item in the deamon start up service list
That should be it, unless you run into permission problems in which case you will need to add yourself to the boinc group.
The best form of help from above is a sniper on the rooftop....
#137 Re: Using ASICS miners etc on Bitcoin
Judging by the points racking up again you managed to crack it ? Want to share some of the knowledge on the linux forum http://www.dunadd.co.uk/seti/forum/viewforum.php?f=139 or update my post on the bitcoin subforum http://www.dunadd.co.uk/seti/forum/view ... 113&t=2432
inquiring minds want to know as I'm going to be setting up Ubuntu 14 when / if I ever get out of this place
inquiring minds want to know as I'm going to be setting up Ubuntu 14 when / if I ever get out of this place
The best form of help from above is a sniper on the rooftop....
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#138 Re: Using ASICS miners etc on Bitcoin
I should have added this info before, so here it is...
A recent change in the BU app now uses a default command line option --usb:1 which causes the cgminer program to only use 1 ASIC. That also means only 1 ASIC will be used by the WU. Here is how you can control how many concurrent WUs you run and how many ASICs to use per WU.
If you want to run multiple WUs using only 1 ASIC per WU, then...
1) Make sure you are running the latest stable version of BOINC
2) Make sure you have you have this section in your cc_config.xml file with the count set to the correct number of ASICs...
<coproc>
<type>miner_asic</type>
<count>6</count>
</coproc>
3) Make sure your app_config.xml is not limiting the max_concurrent for the project or app
If you want to run multiple ASICs per WU
(This example will run 3 concurrent WU with 2 ASICs per WU)...
1) Make sure your app_config.xml limits the max_concurrent WU for the project or app
<project_max_concurrent>3</project_max_concurrent>
<app>
<name>cgminer</name>
<max_concurrent>3</max_concurrent>
</app>
2) Make sure your app_config.xml has the correct <cmdline> option, for each BU app, to use the desired number of ASICs per WU.
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>C-cgminer</app_name>
<cmdline>--usb :2</cmdline>
</app_version>
I'll do another post about how I got the latest version of BOINC running on the Rpi.
Also, running multiple WU with 1 ASIC per WU has really helped with the rockminer r3/rbox stability. When running 4 r3 blades per WU, I'd have a blade lock up at least every few hours, sometimes sooner. Now maybe 1 blade per day needs to be reset.
A recent change in the BU app now uses a default command line option --usb:1 which causes the cgminer program to only use 1 ASIC. That also means only 1 ASIC will be used by the WU. Here is how you can control how many concurrent WUs you run and how many ASICs to use per WU.
If you want to run multiple WUs using only 1 ASIC per WU, then...
1) Make sure you are running the latest stable version of BOINC
2) Make sure you have you have this section in your cc_config.xml file with the count set to the correct number of ASICs...
<coproc>
<type>miner_asic</type>
<count>6</count>
</coproc>
3) Make sure your app_config.xml is not limiting the max_concurrent for the project or app
If you want to run multiple ASICs per WU
(This example will run 3 concurrent WU with 2 ASICs per WU)...
1) Make sure your app_config.xml limits the max_concurrent WU for the project or app
<project_max_concurrent>3</project_max_concurrent>
<app>
<name>cgminer</name>
<max_concurrent>3</max_concurrent>
</app>
2) Make sure your app_config.xml has the correct <cmdline> option, for each BU app, to use the desired number of ASICs per WU.
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>C-cgminer</app_name>
<cmdline>--usb :2</cmdline>
</app_version>
I'll do another post about how I got the latest version of BOINC running on the Rpi.
Also, running multiple WU with 1 ASIC per WU has really helped with the rockminer r3/rbox stability. When running 4 r3 blades per WU, I'd have a blade lock up at least every few hours, sometimes sooner. Now maybe 1 blade per day needs to be reset.
- robmacagain
- Boinc Warrant Officer Class 2
- Posts: 322
- Joined: Tue Apr 12, 2011 3:53 pm
- Location: Sassenachshire
#139 Re: Using ASICS miners etc on Bitcoin
FFS, I have been doing my nut in wondering why (reset them humpteen times swapped usb ports ding fekkin dong and gave the smeg up) i was only doing work on 1 box .
- robmacagain
- Boinc Warrant Officer Class 2
- Posts: 322
- Joined: Tue Apr 12, 2011 3:53 pm
- Location: Sassenachshire
#140 Re: Using ASICS miners etc on Bitcoin
I am so rubbish at this config lark .
Please can some kind soul write and post me the app_config to run all current units 3,4,5,6 and 8 using 4 devices to do 1 unit.
I just cannot get my head around it at all .
Please can some kind soul write and post me the app_config to run all current units 3,4,5,6 and 8 using 4 devices to do 1 unit.
I just cannot get my head around it at all .
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#141 Re: Using ASICS miners etc on Bitcoin
Will you participate in the team challenges?
BTW, very few projects carry no pending. I have over 1,100 pending just 3 days into the SIMAP challenge. It will all count. Still have 50 PrimeGrid WUs pending after the challenge. Einstein down to 10. It will all get counted eventually.
<app_config>
<project_max_concurrent>1</project_max_concurrent>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>C-cgminer-rbox</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_4</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_5</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_6</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_8</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
</app_config>
BTW, very few projects carry no pending. I have over 1,100 pending just 3 days into the SIMAP challenge. It will all count. Still have 50 PrimeGrid WUs pending after the challenge. Einstein down to 10. It will all get counted eventually.
<app_config>
<project_max_concurrent>1</project_max_concurrent>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>C-cgminer-rbox</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_4</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_5</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_6</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_8</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
</app_config>
- robmacagain
- Boinc Warrant Officer Class 2
- Posts: 322
- Joined: Tue Apr 12, 2011 3:53 pm
- Location: Sassenachshire
#142 Re: Using ASICS miners etc on Bitcoin
Thanks Steve, all present and correct.
Team what's???? .
Team what's???? .
- Buster Gunn
- Boinc Second Lieutenant
- Posts: 513
- Joined: Sun Aug 13, 2006 7:20 am
- Location: Wilmington Delaware USA
#143 Re: Using ASICS miners etc on Bitcoin
My grandson has decided that I need an Antminer U2. What can I expect from this device.
Ain't kids great. He controls the normal cores on my machines and I get the GPU's (for now).
He felt sorry for me.
Ain't kids great. He controls the normal cores on my machines and I get the GPU's (for now).
He felt sorry for me.
Buster is my dog. Sadly, Buster is gone.
Buster is the Malamute, Obi is the Golden.
Obi is the dog of the house now.
Buster is the Malamute, Obi is the Golden.
Obi is the dog of the house now.
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#144 Re: Using ASICS miners etc on Bitcoin
I think I'm averaging about 1.5 million per day per U2 but they are overclocked to 2.0 Gh/s. The default rate is 1.6 Gh/s. Each WU only uses .05 of a CPU core, not much.
After re-thinking, if you only have one U2 and don't want to overclock, you might not need all the stuff below. If you do, I think you also have to upgrade BOINC to 7.4.22 or higher.
Add this to your cc_config.xml file, where the count is the number of U2s you have. Be sure to restart the BOINC Client...
<coproc>
<type>miner_asic</type>
<count>1</count>
</coproc>
If you want to overclock your U2, add this to your BU app_config.xml. There's a section for each of the campaign 1.6 Gh/s apps. If you do overclock, I'd recommend using a powered USB hub and put a fan on the U2 to keep it cool...
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>C-cgminer</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_2</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_4</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_5</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_6</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_7</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_8</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_9</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_10</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_11</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_12</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_13</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_14</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
Then go to the your BU account and under the preferences, select the 1.6 Gh/s apps for the campaigns you want to support. You can select as many as you want.
Then go back and update BU in Boinc Manager. You should see the 1.6 Gh/s ASIC WUs download.
After re-thinking, if you only have one U2 and don't want to overclock, you might not need all the stuff below. If you do, I think you also have to upgrade BOINC to 7.4.22 or higher.
Add this to your cc_config.xml file, where the count is the number of U2s you have. Be sure to restart the BOINC Client...
<coproc>
<type>miner_asic</type>
<count>1</count>
</coproc>
If you want to overclock your U2, add this to your BU app_config.xml. There's a section for each of the campaign 1.6 Gh/s apps. If you do overclock, I'd recommend using a powered USB hub and put a fan on the U2 to keep it cool...
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>C-cgminer</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_2</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_4</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_5</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_6</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_7</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_8</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_9</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_10</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_11</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_12</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_13</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer_14</app_name>
<cmdline>--usb :1 --anu-freq 250</cmdline>
</app_version>
Then go to the your BU account and under the preferences, select the 1.6 Gh/s apps for the campaigns you want to support. You can select as many as you want.
Then go back and update BU in Boinc Manager. You should see the 1.6 Gh/s ASIC WUs download.
- Buster Gunn
- Boinc Second Lieutenant
- Posts: 513
- Joined: Sun Aug 13, 2006 7:20 am
- Location: Wilmington Delaware USA
#145 Re: Using ASICS miners etc on Bitcoin
Thanks for the help.
Buster is my dog. Sadly, Buster is gone.
Buster is the Malamute, Obi is the Golden.
Obi is the dog of the house now.
Buster is the Malamute, Obi is the Golden.
Obi is the dog of the house now.
#146 Re: Using ASICS miners etc on Bitcoin
If you are running a single antminer I wouldn't bother overclocking ( or you will have to add every new campaign to your config file as you want to run them ) and as the difficulty is getting higher you may have to run the 333 Mh/s units if you find you can't finish in time.
For almost the same price you can get 32GH/s R boxes which are far better, develop far more points and are more future proof.
For almost the same price you can get 32GH/s R boxes which are far better, develop far more points and are more future proof.
The best form of help from above is a sniper on the rooftop....
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#147 Re: Using ASICS miners etc on Bitcoin
Yeah, on eBay a 32 Gh/s r-box can be bought for $20-$30. Antminer U2s appear to still be selling for up to $20. Go figure? Need to sell mine.
- Buster Gunn
- Boinc Second Lieutenant
- Posts: 513
- Joined: Sun Aug 13, 2006 7:20 am
- Location: Wilmington Delaware USA
#148 Re: Using ASICS miners etc on Bitcoin
I shall see what my grandson comes up with. It's his dime.
Buster is my dog. Sadly, Buster is gone.
Buster is the Malamute, Obi is the Golden.
Obi is the dog of the house now.
Buster is the Malamute, Obi is the Golden.
Obi is the dog of the house now.
- Buster Gunn
- Boinc Second Lieutenant
- Posts: 513
- Joined: Sun Aug 13, 2006 7:20 am
- Location: Wilmington Delaware USA
#149 Re: Using ASICS miners etc on Bitcoin
So there I was sitting having breakfast with a neighbor/friend of mine about a month ago, and the conversation turned to
crypto-mining. He told me his son bought an AntMiner U3 (the silver domed one) and couldn't get it working. His son
discarded it in my friends garage. My friend isn't technically inclined and asked me if I wanted it. It said sure. What's the price? He said, "pay for breakfast", which I did.
I futzed with it for a few days and finally got it running on BU but only at 40% (about 18M/day). It's a 60ghz miner. I needed cgminer 4.9.0 and had to zip add it to the app zip files. I couldn't adjust the freq and voltage with the normal app-info or config files.
Finally about 2 days ago I found that you can do those adjustments using a cgminer.conf file, adjusting au3-freq and au3-volt. I'm now up to about 90% and churning out about 40M/day. The only problem I have is if BOINC stops or gets reset or BU decides to upgrade apps, then I will have to zip-add cgminer 4.9.0 and the conf file again.
For about 8 hours last night I was running at 100%. Not a clue why.
crypto-mining. He told me his son bought an AntMiner U3 (the silver domed one) and couldn't get it working. His son
discarded it in my friends garage. My friend isn't technically inclined and asked me if I wanted it. It said sure. What's the price? He said, "pay for breakfast", which I did.
I futzed with it for a few days and finally got it running on BU but only at 40% (about 18M/day). It's a 60ghz miner. I needed cgminer 4.9.0 and had to zip add it to the app zip files. I couldn't adjust the freq and voltage with the normal app-info or config files.
Finally about 2 days ago I found that you can do those adjustments using a cgminer.conf file, adjusting au3-freq and au3-volt. I'm now up to about 90% and churning out about 40M/day. The only problem I have is if BOINC stops or gets reset or BU decides to upgrade apps, then I will have to zip-add cgminer 4.9.0 and the conf file again.
For about 8 hours last night I was running at 100%. Not a clue why.
Buster is my dog. Sadly, Buster is gone.
Buster is the Malamute, Obi is the Golden.
Obi is the dog of the house now.
Buster is the Malamute, Obi is the Golden.
Obi is the dog of the house now.
#150 Re: Using ASICS miners etc on Bitcoin
That's a great breakfast bargain there Buster!
And well done getting it working, I thought there were issues with the U3's on bitcoin but looks like you/they've got it sorted.
And well done getting it working, I thought there were issues with the U3's on bitcoin but looks like you/they've got it sorted.
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#151 Re: Using ASICS miners etc on Bitcoin
I need to find me some friends like that...
But excellent job working through it and getting it running on BU.
But excellent job working through it and getting it running on BU.
- robmacagain
- Boinc Warrant Officer Class 2
- Posts: 322
- Joined: Tue Apr 12, 2011 3:53 pm
- Location: Sassenachshire
#152 Re: Using ASICS miners etc on Bitcoin
Can anyone see anything wrong with this for me please, Can't get it to run milkyway #3 .
<app_config>
<project_max_concurrent>1</project_max_concurrent>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>C-cgminer-rbox</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer-rbox_3</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer-rbox_4</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer-rbox_5</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer-rbox_6</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer-rbox_8</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer-rbox_9</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
</app_config>
Thank You.
<app_config>
<project_max_concurrent>1</project_max_concurrent>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>C-cgminer-rbox</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer-rbox_3</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer-rbox_4</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer-rbox_5</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer-rbox_6</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer-rbox_8</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
<plan_class>miner_asic</plan_class>
<app_name>cgminer-rbox_9</app_name>
<cmdline>--usb :4</cmdline>
</app_version>
</app_config>
Thank You.
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#153 Re: Using ASICS miners etc on Bitcoin
What's your cc_config.xml look like? Also, campaign #3 was removed then added back. Is that option selected in the BU preferences for your system?
- robmacagain
- Boinc Warrant Officer Class 2
- Posts: 322
- Joined: Tue Apr 12, 2011 3:53 pm
- Location: Sassenachshire
#154 Re: Using ASICS miners etc on Bitcoin
Thanks.
Yes it is in the preferences.
This >
<cc_config>
<options>
<coproc>
<type>miner_asic</type>
<count>1</count>
</coproc>
</options>
</cc_config>
Have just upgraded BOINC at it's request and now i'm getting this as well
Bitcoin Utopia: Notice from BOINC
Your app_config.xml file refers to an unknown application 'cgminer-rbox_6'. Known applications: 'cgminer-rbox_4', 'C-cgminer-rbox', 'cgminer-rbox_5', 'cgminer-rbox_3'
21/04/2015 16:04:37
--------------------------------------------------------------------------------
Bitcoin Utopia: Notice from BOINC
Unknown tag in app_config.xml: /app_version
21/04/2015 16:04:37
--------------------------------------------------------------------------------
Bitcoin Utopia: Notice from BOINC
Unknown tag in app_config.xml: cmdline
21/04/2015 16:04:37
--------------------------------------------------------------------------------
Bitcoin Utopia: Notice from BOINC
Unknown tag in app_config.xml: app_name
21/04/2015 16:04:37
--------------------------------------------------------------------------------
Bitcoin Utopia: Notice from BOINC
Unknown tag in app_config.xml: plan_class
21/04/2015 16:04:37
--------------------------------------------------------------------------------
Bitcoin Utopia: Campaign #3 reopened, campaign #12 (Free-DC) online
There are two new active campaigns:
- Campaign #3 - Milkyway@home - Part 3
- Campaign #12 - Free-DC
....................................................................................................................
There should be some work available. Enjoy!
Henri.
20/04/2015 21:16:11 · more...
BUT its still running and crunching???
It is trying to download this cgminer-rbox_3_win32_00003.zip file, maybe that is why it will not run milkyway until it gets it, but its on project backoff saying retry in 2 hrs 47 minutes GRRRR.
Yes it is in the preferences.
This >
<cc_config>
<options>
<coproc>
<type>miner_asic</type>
<count>1</count>
</coproc>
</options>
</cc_config>
Have just upgraded BOINC at it's request and now i'm getting this as well
Bitcoin Utopia: Notice from BOINC
Your app_config.xml file refers to an unknown application 'cgminer-rbox_6'. Known applications: 'cgminer-rbox_4', 'C-cgminer-rbox', 'cgminer-rbox_5', 'cgminer-rbox_3'
21/04/2015 16:04:37
--------------------------------------------------------------------------------
Bitcoin Utopia: Notice from BOINC
Unknown tag in app_config.xml: /app_version
21/04/2015 16:04:37
--------------------------------------------------------------------------------
Bitcoin Utopia: Notice from BOINC
Unknown tag in app_config.xml: cmdline
21/04/2015 16:04:37
--------------------------------------------------------------------------------
Bitcoin Utopia: Notice from BOINC
Unknown tag in app_config.xml: app_name
21/04/2015 16:04:37
--------------------------------------------------------------------------------
Bitcoin Utopia: Notice from BOINC
Unknown tag in app_config.xml: plan_class
21/04/2015 16:04:37
--------------------------------------------------------------------------------
Bitcoin Utopia: Campaign #3 reopened, campaign #12 (Free-DC) online
There are two new active campaigns:
- Campaign #3 - Milkyway@home - Part 3
- Campaign #12 - Free-DC
....................................................................................................................
There should be some work available. Enjoy!
Henri.
20/04/2015 21:16:11 · more...
BUT its still running and crunching???
It is trying to download this cgminer-rbox_3_win32_00003.zip file, maybe that is why it will not run milkyway until it gets it, but its on project backoff saying retry in 2 hrs 47 minutes GRRRR.
- robmacagain
- Boinc Warrant Officer Class 2
- Posts: 322
- Joined: Tue Apr 12, 2011 3:53 pm
- Location: Sassenachshire
#155 Re: Using ASICS miners etc on Bitcoin
There seems to be no work coming from them at all now, the server page says it's running???
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#156 Re: Using ASICS miners etc on Bitcoin
I'm getting #3 WUs but don't use an app_config.xml.
I think the issue may be app_name should be C-cgminer-rbox, not C-cgminer_rbox. It's close but computers are so darn picky.
I think the issue may be app_name should be C-cgminer-rbox, not C-cgminer_rbox. It's close but computers are so darn picky.
- robmacagain
- Boinc Warrant Officer Class 2
- Posts: 322
- Joined: Tue Apr 12, 2011 3:53 pm
- Location: Sassenachshire
#157 Re: Using ASICS miners etc on Bitcoin
It says C-cgminer-rbox already??
Anyway it has started working now, it was that .zip file that was the problem, it's downloaded it the noo and it's working :wav:
Anyway it has started working now, it was that .zip file that was the problem, it's downloaded it the noo and it's working :wav:
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#158 Re: Using ASICS miners etc on Bitcoin
Then what the heck was I looking at!
Dunno what the issue is. Did you say the issue is it won't download a #3 WU or it downloads but won't launch it active?
Dunno what the issue is. Did you say the issue is it won't download a #3 WU or it downloads but won't launch it active?
- robmacagain
- Boinc Warrant Officer Class 2
- Posts: 322
- Joined: Tue Apr 12, 2011 3:53 pm
- Location: Sassenachshire
#159 Re: Using ASICS miners etc on Bitcoin
I think you need to grind a fresh jug .
What it was it wouldn't get me any campaign #3, and it was stuck downloading a .zip file that said cgminer-rbox_3_win32_00003.zip that was after I inserted the new parameter in the cc config to start campaign 3 again.
I have #3 now and #4 all banging away, so I is happy .
What it was it wouldn't get me any campaign #3, and it was stuck downloading a .zip file that said cgminer-rbox_3_win32_00003.zip that was after I inserted the new parameter in the cc config to start campaign 3 again.
I have #3 now and #4 all banging away, so I is happy .
- Dirk Broer
- Corsair
- Posts: 1964
- Joined: Thu Feb 20, 2014 11:24 pm
- Location: Leiden, South Holland, Netherlands
- Contact:
#160 Re: Using ASICS miners etc on Bitcoin
I have one 333 Mh/s block erupter (device 5, for all practical purposes an U1 Antminer) and two 1.6 Gh/s U2 antminers (devices 3 and 4), all on USB bus 1 (oh, the joy of an USB 3.0 hub).
How can I get the 333 Mh/s block erupter to crunch only campaign #7, while the heavy cavalry charges only at campaign#6?
How can I get the 333 Mh/s block erupter to crunch only campaign #7, while the heavy cavalry charges only at campaign#6?
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#161 Re: Using ASICS miners etc on Bitcoin
This used to work. Don't know if BU has changed though. Use the correct app names also.
Make sure cc_config.xml has correct number of miners in it...
<coproc>
<type>miner_asic</type>
<count>3</count>
</coproc>
Modify your BU app cmdline parameter with the --usb option, where..
--usb <bus>:<device>,<bus>:<device>,<bus>:<device>
app_config.xml looks like this...
<app_config>
<app>
<name>C-cgminer</name>
<max_concurrent>1</max_concurrent>
</app>
<app>
<name>cgminer_4</name>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<plan_class>asic</plan_class>
<app_name>C-cgminer</app_name>
<cmdline>--usb 4:14,4:16,4:17 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>asic</plan_class>
<app_name>cgminer_4</app_name>
<cmdline>--usb 4:10,4:11,4:13 --anu-freq 250</cmdline>
</app_version>
</app_config>
To determine the bus and device number of each miner, unzip the contents of one of the BU cgminer app files into a work folder, then from a command prompt, go to that folder and run...
cgminer -ndevs
It will give you output like this...
[2014-09-24 17:42:42] USB all: found 28 devices - listing known devices
.USB dev 0: Bus 4 Device 10 ID: 10c4:ea60
Manufacturer: 'Silicon Labs'
Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 1: Bus 4 Device 11 ID: 10c4:ea60
Manufacturer: 'Silicon Labs'
Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 2: Bus 4 Device 17 ID: 10c4:ea60
Manufacturer: 'Silicon Labs'
Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 3: Bus 4 Device 13 ID: 10c4:ea60
Manufacturer: 'Silicon Labs'
Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 4: Bus 4 Device 16 ID: 10c4:ea60
Manufacturer: 'Silicon Labs'
Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 5: Bus 4 Device 14 ID: 10c4:ea60
Manufacturer: 'Silicon Labs'
Product: 'CP2102 USB to UART Bridge Controller'
[2014-09-24 17:42:42] 6 known USB devices
Make sure cc_config.xml has correct number of miners in it...
<coproc>
<type>miner_asic</type>
<count>3</count>
</coproc>
Modify your BU app cmdline parameter with the --usb option, where..
--usb <bus>:<device>,<bus>:<device>,<bus>:<device>
app_config.xml looks like this...
<app_config>
<app>
<name>C-cgminer</name>
<max_concurrent>1</max_concurrent>
</app>
<app>
<name>cgminer_4</name>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<plan_class>asic</plan_class>
<app_name>C-cgminer</app_name>
<cmdline>--usb 4:14,4:16,4:17 --anu-freq 250</cmdline>
</app_version>
<app_version>
<plan_class>asic</plan_class>
<app_name>cgminer_4</app_name>
<cmdline>--usb 4:10,4:11,4:13 --anu-freq 250</cmdline>
</app_version>
</app_config>
To determine the bus and device number of each miner, unzip the contents of one of the BU cgminer app files into a work folder, then from a command prompt, go to that folder and run...
cgminer -ndevs
It will give you output like this...
[2014-09-24 17:42:42] USB all: found 28 devices - listing known devices
.USB dev 0: Bus 4 Device 10 ID: 10c4:ea60
Manufacturer: 'Silicon Labs'
Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 1: Bus 4 Device 11 ID: 10c4:ea60
Manufacturer: 'Silicon Labs'
Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 2: Bus 4 Device 17 ID: 10c4:ea60
Manufacturer: 'Silicon Labs'
Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 3: Bus 4 Device 13 ID: 10c4:ea60
Manufacturer: 'Silicon Labs'
Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 4: Bus 4 Device 16 ID: 10c4:ea60
Manufacturer: 'Silicon Labs'
Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 5: Bus 4 Device 14 ID: 10c4:ea60
Manufacturer: 'Silicon Labs'
Product: 'CP2102 USB to UART Bridge Controller'
[2014-09-24 17:42:42] 6 known USB devices
- Dirk Broer
- Corsair
- Posts: 1964
- Joined: Thu Feb 20, 2014 11:24 pm
- Location: Leiden, South Holland, Netherlands
- Contact:
#162 Re: Using ASICS miners etc on Bitcoin
I'm not having trouble running 3 WUs at a time, I am having trouble keeping the block erupter at campaign #7 333Mh/s WUs, while the antminers do campaign #6 WUs at 1.6 Gh/s.
At the moment my system is treating the three USB sticks as equal and randomly assigns 333Mh/s or 1.6Mh/s Wu to them for both campaigns, despite my settings in the app_config.xml. In fact the only thing that changed when I tried to run with an app_config.xml -I did without previously- is that the error rate for the 1.6 WUs has risen sharply.
Is it right to have --anu-freq 250 for both the 333Mh/s block erupter and the 1.6Mh/s U2 Antminers?
At the moment my system is treating the three USB sticks as equal and randomly assigns 333Mh/s or 1.6Mh/s Wu to them for both campaigns, despite my settings in the app_config.xml. In fact the only thing that changed when I tried to run with an app_config.xml -I did without previously- is that the error rate for the 1.6 WUs has risen sharply.
Is it right to have --anu-freq 250 for both the 333Mh/s block erupter and the 1.6Mh/s U2 Antminers?
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#163 Re: Using ASICS miners etc on Bitcoin
Look closer at the example. It shows you how to assign devices on specific USB ports to specific apps.
Not sure cgminer will pass the cmdline arg --anu-freq 250 to the block erupters. That's an option specifically for antminers. If it did though, I would say, no don't set the freq the same for different types of ASICs.
Not sure cgminer will pass the cmdline arg --anu-freq 250 to the block erupters. That's an option specifically for antminers. If it did though, I would say, no don't set the freq the same for different types of ASICs.
- Dirk Broer
- Corsair
- Posts: 1964
- Joined: Thu Feb 20, 2014 11:24 pm
- Location: Leiden, South Holland, Netherlands
- Contact:
#164 Re: Using ASICS miners etc on Bitcoin
What am I doing wrong here? Only device 4 runs, and it is doing Campaign#6...
<app_config>
<app>
<name>cgminer-be_7</name>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<app_name>cgminer-be_7</app_name>
<plan_class>miner_asic</plan_class>
<cmdline>--usb 1:5</cmdline>
</app_version>
<app>
<name>cgminer_6</name>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<app_name>cgminer_6</app_name>
<plan_class>miner_asic</plan_class>
<cmdline>--usb 1:3</cmdline>
</app_version>
<app>
<name>cgminer_7</name>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<app_name>cgminer_7</app_name>
<plan_class>miner_asic</plan_class>
<cmdline>--usb 1:4</cmdline>
</app_version>
</app_config>
<app_config>
<app>
<name>cgminer-be_7</name>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<app_name>cgminer-be_7</app_name>
<plan_class>miner_asic</plan_class>
<cmdline>--usb 1:5</cmdline>
</app_version>
<app>
<name>cgminer_6</name>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<app_name>cgminer_6</app_name>
<plan_class>miner_asic</plan_class>
<cmdline>--usb 1:3</cmdline>
</app_version>
<app>
<name>cgminer_7</name>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<app_name>cgminer_7</app_name>
<plan_class>miner_asic</plan_class>
<cmdline>--usb 1:4</cmdline>
</app_version>
</app_config>
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#165 Re: Using ASICS miners etc on Bitcoin
what does your cc_config.xml look like and what version boinc?
- Dirk Broer
- Corsair
- Posts: 1964
- Joined: Thu Feb 20, 2014 11:24 pm
- Location: Leiden, South Holland, Netherlands
- Contact:
#166 Re: Using ASICS miners etc on Bitcoin
I have it back at three running WUs, but still ignoring these settings (placed USB WiFi stick in the hub so the device numbers changed):
<app_config>
<app>
<name>cgminer-be_7</name>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<app_name>cgminer-be_7</app_name>
<plan_class>miner_asic</plan_class>
<cmdline>--usb 1:5</cmdline>
</app_version>
<app>
<name>cgminer_6</name>
<max_concurrent>2</max_concurrent>
</app>
<app_version>
<app_name>cgminer_6</app_name>
<plan_class>miner_asic</plan_class>
<cmdline>--usb 1:2,1:4 --anu-freq 250</cmdline>
</app_version>
</app_config>
Ignoring in the sense that the block erupter (1:5) still gets 1.6 Gh/s tasks for both campaigns,
and the U2 antminers (1:2 & 1:4) still get 333 Mh/s tasks for campaign#7 too
<app_config>
<app>
<name>cgminer-be_7</name>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<app_name>cgminer-be_7</app_name>
<plan_class>miner_asic</plan_class>
<cmdline>--usb 1:5</cmdline>
</app_version>
<app>
<name>cgminer_6</name>
<max_concurrent>2</max_concurrent>
</app>
<app_version>
<app_name>cgminer_6</app_name>
<plan_class>miner_asic</plan_class>
<cmdline>--usb 1:2,1:4 --anu-freq 250</cmdline>
</app_version>
</app_config>
Ignoring in the sense that the block erupter (1:5) still gets 1.6 Gh/s tasks for both campaigns,
and the U2 antminers (1:2 & 1:4) still get 333 Mh/s tasks for campaign#7 too
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#167 Re: Using ASICS miners etc on Bitcoin
What does your cc_config.xml look like?
- Dirk Broer
- Corsair
- Posts: 1964
- Joined: Thu Feb 20, 2014 11:24 pm
- Location: Leiden, South Holland, Netherlands
- Contact:
#168 Re: Using ASICS miners etc on Bitcoin
<coproc>scole250 wrote:What does your cc_config.xml look like?
<type>miner_asic</type>
<count>3</count>
<peak_flops>0.000000</peak_flops>
<device_nums>2 4 5</device_nums>
</coproc>
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#169 Re: Using ASICS miners etc on Bitcoin
What does this line do?
<device_nums>2 4 5</device_nums>
Try taking that out.
<device_nums>2 4 5</device_nums>
Try taking that out.
- Dirk Broer
- Corsair
- Posts: 1964
- Joined: Thu Feb 20, 2014 11:24 pm
- Location: Leiden, South Holland, Netherlands
- Contact:
#170 Re: Using ASICS miners etc on Bitcoin
From http://boinc.berkeley.edu/wiki/Client_configuration
<coproc>
specify a coprocessor. Used in combination with the Anonymous platform mechanism. The element has the form
<coproc>
<type>some_name</type>
<count>1</count>
<device_nums>0 2</device_nums>
[ <peak_flops>1e10</peak_flops> ]
[ <non_gpu/> ]
</coproc>
The name given in <type> must match that in the <coproc> element in app_info.xml. <count> in the number of GPU instances, and
<device_nums> is their device numbers. <peak_flops> is the GPU peak FLOPS; it can be omitted if your app_info.xml specifies estimated application FLOPS. If <non_gpu/> is specified, the coprocessor is not treated as a GPU; i.e. "Suspend GPU" does not affect it. This mechanism has two purposes: to provide fine-grained control of the coprocessors recognized by BOINC (NVIDIA, AMD, and Intel GPUs), and to let you use coprocessors not recognized by BOINC.
removal of the line resulted in having devices 0, 1 and 2 -the whole shebang banging away on campaign#7, or #6, or both, regardless of the app_config.xml- instead of having 2 and 4 go at #6 and 5 at #7.....
<coproc>
specify a coprocessor. Used in combination with the Anonymous platform mechanism. The element has the form
<coproc>
<type>some_name</type>
<count>1</count>
<device_nums>0 2</device_nums>
[ <peak_flops>1e10</peak_flops> ]
[ <non_gpu/> ]
</coproc>
The name given in <type> must match that in the <coproc> element in app_info.xml. <count> in the number of GPU instances, and
<device_nums> is their device numbers. <peak_flops> is the GPU peak FLOPS; it can be omitted if your app_info.xml specifies estimated application FLOPS. If <non_gpu/> is specified, the coprocessor is not treated as a GPU; i.e. "Suspend GPU" does not affect it. This mechanism has two purposes: to provide fine-grained control of the coprocessors recognized by BOINC (NVIDIA, AMD, and Intel GPUs), and to let you use coprocessors not recognized by BOINC.
removal of the line resulted in having devices 0, 1 and 2 -the whole shebang banging away on campaign#7, or #6, or both, regardless of the app_config.xml- instead of having 2 and 4 go at #6 and 5 at #7.....
- Dirk Broer
- Corsair
- Posts: 1964
- Joined: Thu Feb 20, 2014 11:24 pm
- Location: Leiden, South Holland, Netherlands
- Contact:
#171 Re: Using ASICS miners etc on Bitcoin
The only thing that seems to work is the --anu-freq 250 line.
BOINC manager still gives tasks at random to my three USB sticks, even though I specified campaign#7 for the 333 Mh/s block erupter and #6 for the 1.6 Gh/s U2 antminers.
BOINC manager still gives tasks at random to my three USB sticks, even though I specified campaign#7 for the 333 Mh/s block erupter and #6 for the 1.6 Gh/s U2 antminers.
- Dirk Broer
- Corsair
- Posts: 1964
- Joined: Thu Feb 20, 2014 11:24 pm
- Location: Leiden, South Holland, Netherlands
- Contact:
#172 Re: Using ASICS miners etc on Bitcoin
BU is not reading my app_config.xml at all! I enabled campaign #13 again, did nothing for the app_config.xml (that does not mention #13) and voila: campaign #13 runs on my machine :drunken:
#173 Re: Using ASICS miners etc on Bitcoin
Dirk, on start up does boinc mention finding an app_config to use ? or does it mention app_config refers to missing apps etc. Post up your new app_config and I'll see if I can spot anything untoward. Which version of BOINC manager ?
The best form of help from above is a sniper on the rooftop....
- Dirk Broer
- Corsair
- Posts: 1964
- Joined: Thu Feb 20, 2014 11:24 pm
- Location: Leiden, South Holland, Netherlands
- Contact:
#174 Re: Using ASICS miners etc on Bitcoin
Yes, it finds the app_config.xml
Nope, no missing apps
Latest Boinc manager
but this post says it all:
With the new --usb :1 option and running more than 1 miner of the same kind you must change the
<count>x</count>
line in cc_config to the amount of your running miners. No app_config is needed anymore. For different apps see above.
This will overwrite the --usb :1 option.
and other USB options as well, I fear...
Nope, no missing apps
Latest Boinc manager
but this post says it all:
With the new --usb :1 option and running more than 1 miner of the same kind you must change the
<count>x</count>
line in cc_config to the amount of your running miners. No app_config is needed anymore. For different apps see above.
This will overwrite the --usb :1 option.
and other USB options as well, I fear...
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#175 Re: Using ASICS miners etc on Bitcoin
Post your cc_config.xml and app_config,xml
- Dirk Broer
- Corsair
- Posts: 1964
- Joined: Thu Feb 20, 2014 11:24 pm
- Location: Leiden, South Holland, Netherlands
- Contact:
#176 Re: Using ASICS miners etc on Bitcoin
Read above or below, depending on the way you sort the messages.scole250 wrote:Post your cc_config.xml and app_config,xml
#177 Re: Using ASICS miners etc on Bitcoin
It certainly sounds like it over rules what you wish to do. One way round it would be to run your miners on different computers and use the home / work / school setting in your account to specify which project runs on which computer / miner combination. Only way I can think of without being able to use the USB options.Dirk Broer wrote:Yes, it finds the app_config.xml
Nope, no missing apps
Latest Boinc manager
but this post says it all:
With the new --usb :1 option and running more than 1 miner of the same kind you must change the
<count>x</count>
line in cc_config to the amount of your running miners. No app_config is needed anymore. For different apps see above.
This will overwrite the --usb :1 option.
and other USB options as well, I fear...
The best form of help from above is a sniper on the rooftop....
- scole of TSBT
- Boinc Major General
- Posts: 5982
- Joined: Mon Feb 03, 2014 2:38 pm
- Location: Goldsboro, (Eastern) North Carolina, USA
#178 Re: Using ASICS miners etc on Bitcoin
I recall having similar issues while I ran it. I used raspberry pi's to run them. BU and WUProp where the only projects on them.
- Dirk Broer
- Corsair
- Posts: 1964
- Joined: Thu Feb 20, 2014 11:24 pm
- Location: Leiden, South Holland, Netherlands
- Contact:
#179 Re: Using ASICS miners etc on Bitcoin
I've set BU to 10,000% resources in order to get WUs on the systems that run BU.
I mostly run 40+ projects per box (that's x86 boxes, try to run 40+ projects on your ARM boxes...)
I mostly run 40+ projects per box (that's x86 boxes, try to run 40+ projects on your ARM boxes...)