|
I don't believe these need to be faster or cheaper than GPU's
Simply need to use less electricity.
Even if they are more expensive they'd have the advantage of chaining many together without needing to build new pc's to house them in.
Of course they'd still need to be in the same ballpark price, if they're grossly expensive nobody would go for it.
It seems a difficult feat to make an inexpensive Scrypt miner
|
|
|
|
claims to do 59.6 KH/s while using 0.44 W that would be good, but first get the current boards sorted.
Barntech sent ya a pm
Yeah, but you gonna need 16chips to mimic say an R9 290 gpu, and I bet a 16 chip board wont be cheap! No but it would be a lot more energy efficient. Yeah, but nobody is going to run them in LTC only mode are they, they will run them in mixed mining mode which pulls close to 5watts per chip, a lot less efficient than the current Drillbit boards. i am sure once barntech & co finished this batch they'll look into things like these. one problem at a time...... I have plenty of SHA ASICs, I would be running them Scrypt/Litecoin full-time, no need for hybrid, what good does a few extra gigs do me compared to alt coining? no contest. |
|
|
|
claims to do 59.6 KH/s while using 0.44 W that would be good, but first get the current boards sorted.
Barntech sent ya a pm
Yeah, but you gonna need 16chips to mimic say an R9 290 gpu, and I bet a 16 chip board wont be cheap! No but it would be a lot more energy efficient. And expandable. There are only so many gpu's per PC you can hook-up. Whereas external ASIC's can just keep being stacked up on the one host pc |
|
|
|
|
Ok so it seems I'm a bit behind on the latest news. I read the e-mail update
Am I to understand that.. every single board has a hardware fault?
And because I don't wish to tinker with it myself (haven't even opened them), I should return to sender?
Any forms to fill out or emails to send?
|
|
|
|
|
I believe Hermes is the god we need to show our love to for this matter
|
|
|
|
Hmm... is the "Got spurious work results for idle ASIC 0" anything to be concerned about?
Nah that only happens when you restart cgminer Here's a new screenshot now that it's run overnight, passive cooling. (very low error rate as you can see)  |
|
|
|
Oh sorry, how selfish of me not to post cgminer pr0n. I've been fiddling with the clock. Still tinkering I can get it up to almost 3Gh/s without error when cooled by a fan - though it fluctuates a fair bit 2.7~3 I don't really want to push too hard because I plan on sticking to passive cooling and don't want it to explode  Seem to get a stable 2.6~2.7 without a fan. Pushing it...  Letting it chill n do its thang  |
|
|
|
Hey guys. Good news this time! Today i shipped out the first thumbs.  I has thumbs! And let me just say.. these are much much sexier, easier, and faster than the bluefury's Well done to the Barntech team! Damn, let us see some hardware porn!! How'd you get them so quick?!?! Me and the local postie are cool, he looks after me. Also, I have been having terrific luck this week!! Barntech even put a little smilie on the side of the cute little green box. hoorah! #daycantberuined Here is some p0rn! click to enlarge!   here it is next to BlueFury and Block Eruptors, putting them to shame   happy-super-fun-time-packaging!  |
|
|
|
Hey guys. Good news this time! Today i shipped out the first thumbs. I has thumbs! And let me just say.. these are much much sexier, easier, and faster than the bluefury's Well done to the Barntech team! |
|
|
|
Ok, so this is getting frustrating...
I've downloaded the bfgminer build which has the bf1.inf in it, which i've installed for my device successfully getting a COM port assigned to it.. yet no miner will work with it
The latest cgminer doesn't work at all (not even for block erupters, and yes, tried without them plugged in also) it just says "failed to initialise" / "you need to install a WinUSB driver for - BF1"
I have tried versions 3.7, 3.6.6, 3.5 and 3.4.3, to no avail
bfgminer simply won't detect anything... at all... just says no devices.. have tried the -S bigpic:all as well as \\.\COMn aswell as bigpic:\\.\COMn
it fails to work with either block erupter or bluefury
I have tried the version with the .inf, as well as version 3.4.0
bitminter beta detects all devices... but the bluefury gets the error "Probe of port COM43 failed: timeout"
I really don't care what miner I have to use, and whether or not it can run both varieties of miners at the same time or not.. I just want them hashing...
FYI, I am working with the infamous Windows Vista
P.S: Despite not hashing, the device gets hot, wtf?
This made me think it was DOA - but I have now tried 2 different devices, and they both behaved the same way.
So, can anybody please tell me what they're using, and how they got it to work? or point out anything I've clearly missed?
Thanks in advance
I did not try it on Vista. On Win7 I am using the bfgminer32 per the instructions earlier in this thread. I use the sample #MINE.bat file edited to suit my pool. bfgminer.exe -S "BF1:all" -o (not bigpic:all). My single BF1 device gets about 2.26 GH/sec (I think that the number that matters is the second number in the bfgminer display, which is the all time average, while the first is a short term exponentially decaying average and the last number looks like a short time actually submitted shares average. The long term average should be taken after things stabilize (quoting any numbers in the first few minutes is misleading and not representative of the long term performance). Good luck Yes!! the BF1:all worked! and getting a steady 2.33 Thank you so much. I'm glad it was something stupidly simple I was doing wrong, I was getting worried. I'd like to tip you, have an address? |
|
|
|
Nice work Doc, But where do we get drivers for the BlueFury?EDIT: Ok, so I used the bf1.inf found in the bfgminer build. Now BitMinter detects my device but has the following error Probe of port COM43 failed: timeout
And then the probing appears to just stop (only a few devices show up) I am using both BE's and BF's, I have heard other miners have an issue with that, is that also the case with BitMinter? If so, what is the solution? surely I am not forced to run 2 machines? EDIT EDIT: I have tried with just the BlueFury plugged in, it still has the timeout error Try having just the blue fury plugged in. Before you start the program press the rst button near the USB port. Wait for it to go dark red and then press start on bitminter. Ok, I tried this a few times, but unfortunately it doesn't seem to make any difference. |
|
|
|
|
Ok, so this is getting frustrating...
I've downloaded the bfgminer build which has the bf1.inf in it, which i've installed for my device successfully getting a COM port assigned to it.. yet no miner will work with it
The latest cgminer doesn't work at all (not even for block erupters, and yes, tried without them plugged in also) it just says "failed to initialise" / "you need to install a WinUSB driver for - BF1"
I have tried versions 3.7, 3.6.6, 3.5 and 3.4.3, to no avail
bfgminer simply won't detect anything... at all... just says no devices.. have tried the -S bigpic:all as well as \\.\COMn aswell as bigpic:\\.\COMn
it fails to work with either block erupter or bluefury
I have tried the version with the .inf, as well as version 3.4.0
bitminter beta detects all devices... but the bluefury gets the error "Probe of port COM43 failed: timeout"
I really don't care what miner I have to use, and whether or not it can run both varieties of miners at the same time or not.. I just want them hashing...
FYI, I am working with the infamous Windows Vista
P.S: Despite not hashing, the device gets hot, wtf?
This made me think it was DOA - but I have now tried 2 different devices, and they both behaved the same way.
So, can anybody please tell me what they're using, and how they got it to work? or point out anything I've clearly missed?
Thanks in advance
|
|
|
|
Nice work Doc, But where do we get drivers for the BlueFury?EDIT: Ok, so I used the bf1.inf found in the bfgminer build. Now BitMinter detects my device but has the following error Probe of port COM43 failed: timeout
And then the probing appears to just stop (only a few devices show up) I am using both BE's and BF's, I have heard other miners have an issue with that, is that also the case with BitMinter? If so, what is the solution? surely I am not forced to run 2 machines? EDIT EDIT: I have tried with just the BlueFury plugged in, it still has the timeout error |
|
|
|
|
I have a package from julz, exciting!
|
|
|
|
4th week of October. What's the latest excuse? link anyone?
Units are being produced right now. Shipping will start late this week. Thank you |
|
|
|
|
4th week of October. What's the latest excuse? link anyone?
|
|
|
|
|
Ok.. so it's now 3rd week of October.. given the 2nd week of October deadline + 1 week delay.. We'd expect you to have units on the way to your door right now.. And if not that, an actual ETA date.
|
|
|
|
|
If anyone here is still wanting these shares.
I offer my 2 shares up for BTC2
PM if interested
|
|
|
|
|
Some good answers here, something else I'd like to put out there to you all
In one-off dice games, where there is a single bitcoin transaction used per game.
Would the transaction ID be an acceptable seed for generating a winning number?
Or are transaction id's predictable/manipulatable ?
Thanks!
|
|
|
|
I've been getting from .04-.05 per block with my 70gh/s, the last few blocks i've got .02 ish, what am I missing? live stats are showing my correst hash rate...?
The pool size has been growing rapidly. as more power is added to the pool, your share per block decreases. But this should mean blocks are mined faster, which theoretically balances it out (smaller payments, more often) |
|
|
|
|
Show Posts
