Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 107. (Read 1193231 times)
October 22, 2013, 10:15:33 PM
Is there an easy way to increase the number of lines for the messages at the bottom of bfgminer? It's not enough lines to see the menu's. If not, could someone point me to the right location in the code and I'll just recompile it.
October 22, 2013, 09:26:33 PM
how to get bfgminer to work on v2 blades?
compile it with the network server, set the ports with --http-port.
set the blades server ip to bfgminer ip and each blade must have a unique username and password; doesnt matter what it is.
October 22, 2013, 07:28:19 PM
how to get bfgminer to work on v2 blades?
October 22, 2013, 07:19:48 PM
On BFGminer start-up im getting 20 or more (duped/stale) not sure which. Only get them when I first start the miner.
Looks like this...BFL 0: 64C | 61.45/61.11/60.52Gh's | A:10153 R:46+20(.45%) HW:1910/.58%
^^
Anybody know whats causing these?
Edit: Figured it out. I think...lol
Looks like this...BFL 0: 64C | 61.45/61.11/60.52Gh's | A:10153 R:46+20(.45%) HW:1910/.58%
^^
Anybody know whats causing these?
Edit: Figured it out. I think...lol
October 22, 2013, 12:41:23 PM
That's not what you asked, though, is it?
You asked if it was no longer available in 13.10, insinuating that it was available in 13.10 and no longer is.
October 22, 2013, 11:29:03 AM
When overclocking individual chips, it would be useful if I could calculate the average valid hashrate from work utility. Unfortunately, the procs API response only lists utility, not work utility. Adding either time elapsed (which could be used in the calculations with Diff1 Work) or work utility to the procs response would be helpful.
And before you say "just use average hashrate * 1-HW%", I'll note that at least broken bitfury chips sometimes report inflated hashrates. For example, a chip @ 2.2 GH/s doing 33% errors never manages to do even 50% of the diff1 work that normally functioning chips do @ 2.2 GH/s. These kind of problems are why it would be useful to have the ability to derive a hashrate from actual work done, for individual chips. This is easy to do for the whole instance from the summary response, by just calculating (Work Utility)/60*2^32.
Work Utility is Diff1 Work / ElapsedAnd before you say "just use average hashrate * 1-HW%", I'll note that at least broken bitfury chips sometimes report inflated hashrates. For example, a chip @ 2.2 GH/s doing 33% errors never manages to do even 50% of the diff1 work that normally functioning chips do @ 2.2 GH/s. These kind of problems are why it would be useful to have the ability to derive a hashrate from actual work done, for individual chips. This is easy to do for the whole instance from the summary response, by just calculating (Work Utility)/60*2^32.
Yes, but there is no elapsed stat either on the procs response, so it's hard to implement this in miner.php. Maybe I should use DEVS instead of PGA, then I could combine DEVS & SUMMARY and get elapsed from $alldata.
EDIT: This worked fine. I still see no reason not to list the work utility for devs, though. Except that adding it would take some work
October 22, 2013, 11:20:46 AM
When overclocking individual chips, it would be useful if I could calculate the average valid hashrate from work utility. Unfortunately, the procs API response only lists utility, not work utility. Adding either time elapsed (which could be used in the calculations with Diff1 Work) or work utility to the procs response would be helpful.
And before you say "just use average hashrate * 1-HW%", I'll note that at least broken bitfury chips sometimes report inflated hashrates. For example, a chip @ 2.2 GH/s doing 33% errorsnever barely manages to do even 50% of the diff1 work that normally functioning chips do @ 2.2 GH/s. These kind of problems are why it would be useful to have the ability to derive a hashrate from actual work done, for individual chips. This is easy to do for the whole instance from the summary response, by just calculating (Work Utility)/60*2^32.
Work Utility is Diff1 Work / ElapsedAnd before you say "just use average hashrate * 1-HW%", I'll note that at least broken bitfury chips sometimes report inflated hashrates. For example, a chip @ 2.2 GH/s doing 33% errors
Yes, but there is no elapsed stat either on the procs response, so it's hard to implement this in miner.php. Maybe I should use DEVS instead of PGA, then I could combine DEVS & SUMMARY and get elapsed from $alldata.
EDIT: This worked fine. I still see no reason not to list the work utility for devs, though. Except that adding it would take some work
EDIT2: Here's a screenshot of my (heavily modded) miner.php:
As you can see, the chip doing 33% errors only barely has a 50% noncerate ((Diff1 Work) / Elapse * 2^32) compared to it's avg hashrate. I wonder what happens to that missing 17%, it's consistently missing and not just random variance.
October 22, 2013, 11:12:04 AM
Was it ever?
yes in 13.04 via synaptic... October 22, 2013, 11:06:44 AM
When overclocking individual chips, it would be useful if I could calculate the average valid hashrate from work utility. Unfortunately, the procs API response only lists utility, not work utility. Adding either time elapsed (which could be used in the calculations with Diff1 Work) or work utility to the procs response would be helpful.
And before you say "just use average hashrate * 1-HW%", I'll note that at least broken bitfury chips sometimes report inflated hashrates. For example, a chip @ 2.2 GH/s doing 33% errors never manages to do even 50% of the diff1 work that normally functioning chips do @ 2.2 GH/s. These kind of problems are why it would be useful to have the ability to derive a hashrate from actual work done, for individual chips. This is easy to do for the whole instance from the summary response, by just calculating (Work Utility)/60*2^32.
Work Utility is Diff1 Work / Elapsed And before you say "just use average hashrate * 1-HW%", I'll note that at least broken bitfury chips sometimes report inflated hashrates. For example, a chip @ 2.2 GH/s doing 33% errors never manages to do even 50% of the diff1 work that normally functioning chips do @ 2.2 GH/s. These kind of problems are why it would be useful to have the ability to derive a hashrate from actual work done, for individual chips. This is easy to do for the whole instance from the summary response, by just calculating (Work Utility)/60*2^32.
October 22, 2013, 10:20:01 AM
When overclocking individual chips, it would be useful if I could calculate the average valid hashrate from work utility. Unfortunately, the procs API response only lists utility, not work utility. Adding either time elapsed (which could be used in the calculations with Diff1 Work) or work utility to the procs response would be helpful.
And before you say "just use average hashrate * 1-HW%", I'll note that at least broken bitfury chips sometimes report inflated hashrates. For example, a chip @ 2.2 GH/s doing 33% errors never manages to do even 50% of the diff1 work that normally functioning chips do @ 2.2 GH/s. These kind of problems are why it would be useful to have the ability to derive a hashrate from actual work done, for individual chips. This is easy to do for the whole instance from the summary response, by just calculating (Work Utility)/60*2^32.
And before you say "just use average hashrate * 1-HW%", I'll note that at least broken bitfury chips sometimes report inflated hashrates. For example, a chip @ 2.2 GH/s doing 33% errors never manages to do even 50% of the diff1 work that normally functioning chips do @ 2.2 GH/s. These kind of problems are why it would be useful to have the ability to derive a hashrate from actual work done, for individual chips. This is easy to do for the whole instance from the summary response, by just calculating (Work Utility)/60*2^32.
October 22, 2013, 09:38:32 AM
Code:
apt-cache search bfgminer
bfgminer no more availlable in Ubuntu 13.10?Was it ever?
October 22, 2013, 09:32:40 AM
Code:
apt-cache search bfgminer
bfgminer no more availlable in Ubuntu 13.10? 
October 22, 2013, 07:53:15 AM
Hi Luke,
I think that the KnCMiner is in your plans.
Do you have an estimation when you release the KncMiner version?
Thank you very much for your contribution to Cryptocoin Mining!!!
The next major version will support KnC units.I think that the KnCMiner is in your plans.
Do you have an estimation when you release the KncMiner version?
Thank you very much for your contribution to Cryptocoin Mining!!!
You can see the (working) code-in-progress in the git "knc" branch.
Thank you very much for your answer!!!
October 22, 2013, 05:47:32 AM
guess: the built in temp sensor on chip 1 in your bfl is non functional and it may be overheating or comm errors. have you flashed your unit?
no I have not flashed it October 21, 2013, 03:48:58 PM
anyone have a link to a table of bit fury osc6 bit stats like bits gnash/sec wattage. been trawliing trying to find it for some ideas.
edit: found one in nano fury dev thread. still open to more though
edit: found one in nano fury dev thread. still open to more though
October 21, 2013, 03:33:29 PM
anyone know whats wrong?
guess: the built in temp sensor on chip 1 in your bfl is non functional and it may be overheating or comm errors. have you flashed your unit?
October 21, 2013, 02:36:19 PM
anyone know whats wrong?
October 21, 2013, 01:42:24 PM
Hi Luke,
I think that the KnCMiner is in your plans.
Do you have an estimation when you release the KncMiner version?
Thank you very much for your contribution to Cryptocoin Mining!!!
The next major version will support KnC units.I think that the KnCMiner is in your plans.
Do you have an estimation when you release the KncMiner version?
Thank you very much for your contribution to Cryptocoin Mining!!!
You can see the (working) code-in-progress in the git "knc" branch.
October 21, 2013, 01:32:02 PM
Hi Luke,
I think that the KnCMiner is in your plans.
Do you have an estimation when you release the KncMiner version?
Thank you very much for your contribution to Cryptocoin Mining!!!
I think that the KnCMiner is in your plans.
Do you have an estimation when you release the KncMiner version?
Thank you very much for your contribution to Cryptocoin Mining!!!
October 21, 2013, 12:32:07 PM
Ah dude, every time I go out my miner stops working. It's a bfl 60gh. Usually it says something like this
Bugs don't get fixed unless they're reported 
Can you run BFGMiner in valgrind? It'll use a lot more CPU time, but it will also give a lot more info.
Code:
valgrind --leak-check=full --track-origins=yes bfgminer YOUR OPTIONS --debuglog 2>valgrind.log
Thank you, I will do when I return. Hope my 1gig of ram pc from year 2000 can handle it.
Jump to: