Unless you got one of the very few Block Erupter Emerald sample devices (never sold), you shouldn't be seeing BEE... just BES.
All of the Erupters were the ones sold by BTC Guild. BFGminer sees them as just about everyone ASIC out there. I've seen them detected as: ICA, BEE, BES, ECM, and even AMU a few times. And it's never all of them, usually 1 to 4 for each with no more than 4 ASIC 'types' at a time. Probably an issue with the Linux USB driver, that confuses BFGminer as to what's actually attached. I've never had a problem, though mine are all properly branded (and don't require the -S options) |
|
|
|
|
Unless you got one of the very few Block Erupter Emerald sample devices (never sold), you shouldn't be seeing BEE... just BES.
|
|
|
|
i will install the bfgminer on raspberry. But its dont work. What i do: cd /home/pi/
wget http://luke.dashjr.org/programs/bitcoin/files/bfgminer/3.10.x/bfgminer-3.10.0.zip
unzip bfgminer-3.10.0.zip
cd bfgminer-3.10.0
sudo ./configure && sudo make
But now i become bfgminer version 3.2.90 with no support on antminers No idea what you're doing wrong here, but you need to get 3.10.0 as you suspect. |
|
|
|
Pulled a new clone this evening and now seeing:
[2014-02-07 02:36:31] AMU: Applying rule antminer:clock=x0981: Unknown option: clock
... when bfgminer launches.
Suggestions?
This is during probe, before the "clock" option exists. It should still be set successfully when initialising the device. I'll reduce the message to debug loglevel so as to avoid confusing people... |
|
|
|
I think you have typo on shipping 'January 10' instead of feb Yep, thanks. Fixed. |
|
|
|
Using Windows 7 x64, Catalyst 14.1, Multiminer (recent), R9-290, and most recent version of BFG miner I now get screen corruption as well as 1/3 the normal hash rate.
Apparently AMD changed something in 14.1 with the drivers and OpenCL optimizations. Not sure where to report this or to who. I'm told this was a problem with the beta 14.1 driver, fixed in the final release. Can you try fully uninstalling your driver, then redownload and install the final 14.1 release? |
|
|
|
|
Rumour has it the Chinese pools can't get a decent internet connection in China and are too cheap to bother setting up a remote block-making node, so they just make tiny blocks and push the workload onto the other miners.
I don't have first-hand knowledge if this is true or not, so research it before acting on it...
Feel free to suggest they get in touch with me if it turns out to just be a technical problem of some sort (these pools aren't participating in the regular pool-operator communciations networks, so I'm not sure how to reach them off-hand).
|
|
|
|
Note: the equivalent Ltc transfer took less than 4 minutes. (I know it's meant to be faster, but still...)
Obviously an unused network is going to find room for your transaction with lower fees (although is it really "equivalent" in that case?). Reality is that all things equal, Litecoin is not any faster, though! |
|
|
|
I just tried to send BTC6.5 with a 0.0001 fee (per software recommendation) and it took 2.5 hours! Yes, this issue is impacting users like me now.
Sends are almost always instant with Bitcoin. Confirmation may have taken 2.5 hours, but that's still relatively fast. Outside of Bitcoin, it's typically 6+ months with expensive credit card fees or at best half a day with even more expensive wiring fees. |
|
|
|
That's just a fraudulent scamcoin. There's no pizza used in it at all!  |
|
|
|
Perhaps naming the thread [16% world's hashpower] would be more informative than 3100TH ?
20% would be more accurate. |
|
|
|
Totally unrelated side note: Doom's BFG actually means Bio-Force Gun. * Luke-Jr ducks. That was the weapons name in the Doom movie. In the game itself, it was the Big F******g Gun. I didn't think the game ever defined it? |
|
|
|
Totally unrelated side note: Doom's BFG actually means Bio-Force Gun. * Luke-Jr ducks. |
|
|
|
Noticed these messages after I recently restarted. Have they always been there, or have I goofed up some library somewhere? (A real possibility since I've been reworking my miners trying to standardize them. If so, just need a hint as too which library I've accidentally downgraded) Latest git has a lot of new untested code. I believe I fixed this issue in the last 48 hours. Thanks. Figured it would be 3.10.1 if it had changed, but I'm new to the git world. 3.10.1 will be from the bfgminer-3.10.x branch. |
|
|
|
I tried your version when mining on windows and my antivirus (Bitdefender) wanted no part of it. Oh well, nothing I can do about malware "antivirus software". So I have no opinion whether or not it works. I settled on CGminer till I got the raspberry going. Then the instructions for the Raspberry were provided for CGminer. So here I am in the CGminer thread. If it works and you're perfectly happy with it, great. If it's lacking for you in any way, you might try BFGMiner to see if it already has your needs addressed. If neither do, it never hurts to post a feature request to both. My unmentionable "alt coins" are also chugging along on 3.7.2 without complaints. I always advise against running unmaintained software. Whether you go with cgminer, BFGMiner, Linux, Windows, or whatever, always use something receiving developer attention for security patches. |
|
|
|
|
KDE is far more user-friendly than Mac/Windows.
|
|
|
|
Not centralized way of looking at anything (ignoring your typo). There was a project named cgminer. It existed yours as bfgminer didn't. BFGMiner is merely a continuation of the same project under a new name. The credit as such goes not to just you but the whole team that worked on cgminer at the time. Yes con and kano and lJr get credit in my mind. Great, sounds like you're the exception here who understands that. That being said the split off is where bfgminer started. No, the split off was Con/Kano deciding they would no longer collaborate. If any project started forking off at this point, it was the new cgminer. One could argue it was simply a two-way split of the same project, but to say new-cgminer is a continuation and BFGMiner "merely" a fork is unreasonable since BFGMiner just continued on as things were prior to the split. In any case, how one prefers to label these things is much less relevant than what works best, which is ultimately the proper metric to be using when you choose your mining software. For some people, cgminer works better (hot unplug and Avalon dynamic clocking come to mind as cgminer advantages at the moment). For many others, BFGMiner is the clear winner... and we strive to make it better all the time. |
|
|
|
Noticed these messages after I recently restarted. Have they always been there, or have I goofed up some library somewhere? (A real possibility since I've been reworking my miners trying to standardize them. If so, just need a hint as too which library I've accidentally downgraded) Latest git has a lot of new untested code. I believe I fixed this issue in the last 48 hours. |
|
|
|
|
Show Posts
