Just use p2pool, pool problem solved
So far, there's little incentive to use BFL gear on p2pool. That's why I haven't even taken a moment to look into the advantages I've heard about with p2pool. I'll mine where I get the most out of my equipment. |
|
|
|
I have BitMinter set to start a new device every time it connects, so I'm not sure why they don't start up every time they get re-detected.
I guess they reconnect as the same USB device and are not seen as "new" devices. May not be the best behavior. You could try in settings choosing on startup to start automated devices, and under automated devices put a tickmark on all the FPGAs. Also a dirty hack would be to set up a scheduled action to start automated devices every 5 minutes. It's not meant to be necessary though. I should look at always doing the "new device" thing even if the device has been seen before. Thank you for the reply Doc. This issue was occurring with the Singles hooked up to a lightly used server with dual quad-core Xeon CPUs and 8GB RAM. The problem went away when I moved it to an idle Acer Iconia Tab tablet with a 1GHz dual-core AMD C-50 and 2GB RAM. Weird. |
|
|
|
|
Hi Doc,
Would it be possible to add a re-scan interval to the BitMinter client that checks for devices that are sitting idle and to start them if it finds any?
I have a PC that's hashing with 5 BFL Singles. Two of them occasionally get dropped from the list and then re-added by the re-scan interval, but for some reason, every time I remote into that computer to check why the hash speed is has dropped, it's due to one or two Singles sitting idle. If I hit the start button next to the ones that aren't hashing, they start up like nothing is wrong.
I have BitMinter set to start a new device every time it connects, so I'm not sure why they don't start up every time they get re-detected.
Thanks,
WP
|
|
|
|
That press release also states: 1) BitForce SC Jalapeno: a USB powered coffee warmer providing 3.5 GH/s, priced at under $149I don't know if you noticed that the pre-order price is: $149So not everything in that press release is true...  Inflation since the press release makes $149 worth less now than it was then... Kidding.  |
|
|
|
|
I've also been watching the BFL threads since late last year and I'm a happy customer with two BFL mini-rigs.
Of course there's no harm in asking, but I also believe the odds that they'll respond at all to this sort of question are near zero and the odds that they'll respond with any information that satisfies the nature of your question are exactly zero.
|
|
|
|
ours is probably very similar :-) No nickname there. Anybody could have made that. Not believable. I don't see what's so hard to believe. What's even stranger is that I care. *shrug* I've uploaded the following pic to my album on imgur for you. (I'll be glad to delete it again, if you wish).  Here's the link again to my album: http://imgur.com/a/UanjrI use a different name on YouTube, but note that the mini-rig in the video is in the same spot as where I took the pictures. http://www.youtube.com/watch?v=66KHMmbnQ_Y |
|
|
|
I'm still waiting for someone with proper reputation on the forums to actually show me a photo of a rig he received.
Other that that, OK.
Here's the post I put up after I received mine. It was a while after giga's. https://bitcointalk.org/index.php?topic=60586.msg1050427#msg1050427P.S. The video I took was the first time I'd ever used my new camera...Didn't realize I have to manually focus it in video mode. |
|
|
|
Maybe I should close this thread down then? Is it really that important to know when the last guy receives his mini-rig?
Well, it's important to me. Mine should ship next week! Grats! I know what that excitement feels like. I asked BFL for the name of the freight company. After Googling their contact info, I was able to go pick up my mini-rigs at the freight facility about 5 hours before they would have been delivered. |
|
|
|
i dont want any rage or something, i just noticed all his messages after each other, on most forums you are warned to use the edit button....
Personally, I appreciate a new message, as it gives me an E-Mail to say there's been a new post. I don't believe editing a message does that. Let's kill this 99.99% CDF monster! |
|
|
|
|
Ordered: 06/26/2012
Quantity: 4
Received: 08/20/2012
|
|
|
|
|
Hi Doc,
I noticed on the beta miner that I can turn on a re-scan interval for added/removed FPGAs. Is that safe to use now?
Thanks!
|
|
|
|
one question: if CDF reaches 100%, we will solve the block?
"There's no such thing as being 1% towards solving a block. You don't make progress towards solving it. After working on it for 24 hours, your chances of solving it are equal to what your chances were at the start or at any moment. Believing otherwise is what's known as the Gambler's fallacy [1]. It's like trying to flip 53 coins at once and have them all come up heads. Each time you try, your chances of success are the same." from https://en.bitcoin.it/wiki/Blocks Then CDF looks useless for predicting the end of a block Nothing is useful for predicting the end of a block. Sorry. To put it another way, if the block we're working on right now shows a CDF of 75%, it simply means that, on average, we should generate a block prior to this point 75% of the time. |
|
|
|
Well - to state the obvious, related to my post on the previous page - BFL can't send out a device with no software ... You're right. They need someone to do the free software development (that they wont pay for in any way) so they can keep the, at least, many hundreds of thousands (or more likely millions) of dollars people have already given them ... Now you're wrong! .500 average, not bad. Well, since a 1TH rig costs $30,000 (or $15,000 with a MR trade in) I can't see how I can possibly be wrong with my money guestimate ... I think he's saying that you're wrong about them needing someone to do the free software development. |
|
|
|
Their 1/3, 1/3, 1/3 policy was decided what, 1.5 or 2 months ago? Why is this just now being debated?
I was wondering the same...lol |
|
|
|
|
Ordered: 06/12/2012
Quantity: 1
Received: 08/16/2012
Ordered: 06/18/2012
Quantity: 1
Received: 08/16/2012
I asked them to combine the orders since they were pretty close together to avoid the extra $33 shipping, so I assume the 06/12 order date was changed to 06/18.
|
|
|
|
WhitePhantom or anyone, Got some questions, but first an update after two hours of crunching... I think I got lucky and all are working. Starts at COM3 for me and goes to COM21 without skipping a number. That adds up to 19 but the CPU should be disabled from crunching. Running this on a shitty 1st gen intel atom laptop...lol When I reduced the CPU affinity from 2 to 1 on the java app, I dropped from 11.6 BTC average to 10.5 or so. I don't think an atom core could crunch .9 per day so something else is going on there. Apparently I should be running on better hardware if that is the case... Didn't really think the computer had much to do with it. Running diagnostics with easyminer does show that one of the cards in there does fail occasionally. On the light test...I will fail between 3 & 6, umm units?, out of 100 Is there anything worth checking out in the Tune & Tweak buttons? Anything else a person should be aware of with this java app? There is an auto-tune package here... http://www.butterflylabs.com/drivers/ Not really sure what it does. I don't wanna disturb anything, it's all running fine so far. Does this thing throttle itself down to 25.2 Gh/s? I ask because it feels that way. A few of the bitforce's are running at 1,450Mh but most are in the 1200 range. Yet I still add up to the 25.2 as promised. Does the bitminter pool update the balance once per day or once per hour? I still show "0" after two hours... But I am #6 on the fastest users now so it is apparently working... I'd suggest turning on affinity for all your CPU cores. To keep them from mining, just hit the red X to remove the CPU from the list of mining hardware. I've never changed a setting in the Tune & Tweak area for an FPGA. Based on my experience, the auto-tune package is a waste of time. It's better to try tweaking them yourself. See my comments here: https://bitcointalk.org/index.php?topic=76916.msg1099628#msg1099628The cards in the mini-rig do not throttle. Every FPGA is unique and those used in the mini-rig are able to run at either 1500 or 1320 MH/s, similar to the +/- 10% specification on the Singles. It looks like you got an excessive number of units that run at 1320, but to make up for it, BFL put an extra FPGA in your box; each of my mini-rigs only have 18. Your balance on BitMinter updates when we find a block. If you go to My Account >> Donations & Perks and set it to 1% or higher, you can opt to get paid immediately, even if our block is orphaned. Otherwise you have to wait 120 confirmations to get paid. You get paid based on your proofs of work over the last 10 shifts. http://bitminter.com/shiftsIf you look at your Account Details under the "Expected per block" column, that is how much you will receive if we find a block in the current shift. If you go to Statistics >> Blocks (coins minted) or if you click the Live Stats button and go to the "Round" tab, you'll see that the last block we found was 4 hours 21 minutes ago at 7:45pm UTC. The CDF (Cumulative Distribution Function) of 74% means that, on average, we would find a block more quickly than this one 74% of the time. If you mine 24/7, it all averages out. Are you doing 1%? I'm too much of a miser...lol Does a block getting "orphaned" happen a lot? Orphaned means that multiple pools were crunching on the same block or something? How long do 120 confirmations take? 24 hours I assume? Thanks again man, you've been a great help. You running a fan on your miners? Many of these are getting to 120-130 degrees F on my end even though that is still considered "in the green" for bitminter. I do 1%. I may be mistaken, but I believe an orphaned block occurs when two miners find a block at the same height at roughly the same time. The network confirms one of the blocks and orphans the other. I've heard that an orphaned block is created roughly 2.5% of the time, but I don't recall who said that. I have a portable A/C blowing directly on both of my mini-rigs. The small room they're in is like 85F, but the mini-rigs stay cool since the A/C is ducted straight to them. Sonny tells me that you're only running too hot if you get an unacceptable number of errors. He also suggested that 59C (138F) is getting on the very warm side for some of the MR's FPGAs, but that others can run much hotter than that reliably; just depends on the particular unit. |
|
|
|
- there are 19 devices  This is because one MiniRig is actually 20 (+/- 1) Next generation Singles (which probably won't ever be sold individually). Both of mine have 18, but each one hashes at the advertised speed. |
|
|
|
WhitePhantom or anyone, Got some questions, but first an update after two hours of crunching... I think I got lucky and all are working. Starts at COM3 for me and goes to COM21 without skipping a number. That adds up to 19 but the CPU should be disabled from crunching. Running this on a shitty 1st gen intel atom laptop...lol When I reduced the CPU affinity from 2 to 1 on the java app, I dropped from 11.6 BTC average to 10.5 or so. I don't think an atom core could crunch .9 per day so something else is going on there. Apparently I should be running on better hardware if that is the case... Didn't really think the computer had much to do with it. Running diagnostics with easyminer does show that one of the cards in there does fail occasionally. On the light test...I will fail between 3 & 6, umm units?, out of 100 Is there anything worth checking out in the Tune & Tweak buttons? Anything else a person should be aware of with this java app? There is an auto-tune package here... http://www.butterflylabs.com/drivers/ Not really sure what it does. I don't wanna disturb anything, it's all running fine so far. Does this thing throttle itself down to 25.2 Gh/s? I ask because it feels that way. A few of the bitforce's are running at 1,450Mh but most are in the 1200 range. Yet I still add up to the 25.2 as promised. Does the bitminter pool update the balance once per day or once per hour? I still show "0" after two hours... But I am #6 on the fastest users now so it is apparently working... I'd suggest turning on affinity for all your CPU cores. To keep them from mining, just hit the red X to remove the CPU from the list of mining hardware. I've never changed a setting in the Tune & Tweak area for an FPGA. Based on my experience, the auto-tune package is a waste of time. It's better to try tweaking them yourself. See my comments here: https://bitcointalk.org/index.php?topic=76916.msg1099628#msg1099628The cards in the mini-rig do not throttle. Every FPGA is unique and those used in the mini-rig are able to run at either 1500 or 1320 MH/s, similar to the +/- 10% specification on the Singles. It looks like you got an excessive number of units that run at 1320, but to make up for it, BFL put an extra FPGA in your box; each of my mini-rigs only have 18. Your balance on BitMinter updates when we find a block. If you go to My Account >> Donations & Perks and set it to 1% or higher, you can opt to get paid immediately, even if our block is orphaned. Otherwise you have to wait 120 confirmations to get paid. You get paid based on your proofs of work over the last 10 shifts. http://bitminter.com/shiftsIf you look at your Account Details under the "Expected per block" column, that is how much you will receive if we find a block in the current shift. If you go to Statistics >> Blocks (coins minted) or if you click the Live Stats button and go to the "Round" tab, you'll see that the last block we found was 4 hours 21 minutes ago at 7:45pm UTC. The CDF (Cumulative Distribution Function) of 74% means that, on average, we would find a block more quickly than this one 74% of the time. If you mine 24/7, it all averages out. |
|
|
|
|
I've always used the BitMinter client and love it. When I start up the beta miner, it auto-detects all my Mini-Rigs' FPGAs. Some tend to fall off the list while the rest are still being detected, but I just re-add them using Devices >> "Probe specific port for FPGA" and then type in the COM port, such as COM12. It's easy enough to tell which ones are missing, as they're sequentially numbered. This puts the missing devices back in the list and mines away like a champ.
|
|
|
|
Thanks, running. I had to add -S for all devices by hand though (debian). Did anybody try to tune the speed with the bfl driver: "Auto-Tune Package – For speed tuning Mini Rigs" ?
Three weeks ago (there may be an updated version out now?), the auto-tune package hosed about 10 of the FPGAs in my two rigs. Sonny sent me two firmware packages to load manually, which fixed the issue. I also found that updating the firmware on one FPGA while the rest are mining almost always resulted in a bad firmware update, requiring me to do it over several times until I realized what was wrong. Here are the two firmware packages Sonny sent to me. https://www.box.com/s/e8cd6a2e651cc87b604cWhat I did in the end was to use EasyMiner to view the properties of each FPGA and identify which ones were using the 1320 MH/s firmware. I updated each of them to use the 1500 MH/s firmware and then mined with them for a while to see if errors showed up. All but one had a 20%+ error rate, so I flashed them back to the 1320 MH/s firmware. The Mini-Rig FPGAs don't throttle when there are errors, so I guess it was worthwhile since I got one running at 1500 MH/s with only a 2% error rate in exchange for a 13% speed increase. |
|
|
|
|
Show Posts
