Hi guys,
I'm new here. I was using CGminer on ubuntu and decided to change to BFGminer. I installed through the PPA. BFGMiner doesn't recognize my BFL's and recognize just one of my usb asicminers, I have 11 of them.
Anything I need to do extra? Do I need to install drivers for them or BFL like in Windows?!
Any ideas?
Thank you,
Igor
From README: Q: I ran cgminer, and now BFGMiner doesn't work!
A: cgminer has its own non-standard implementations of the drivers for most USB devices, and disables the official drivers (on Windows, you did this manually using Zadig). Before you can use BFGMiner, you will need to restore the original driver. With Linux, usually rebooting or re-plugging the device is sufficient. |
|
|
|
How would that work with pools that have public stats? Especially Eligius, actually.
Perhaps show hash(BIP32 seed)? Otherwise, public seeds would not result in any more privacy.
Actually, I was thinking we should use hash(recurring invoice id) for the stats page, and not publish a list of those at all. wizkid057 disagrees at the moment, though, so I'm not sure how it will turn out. |
|
|
|
Is the Klondike K16 supported now in BFG? I can't be sure looking at the readmes.
The driver is pretty poor code (almost verbatim import from cgminer), so I'll probably rewrite it when/if they get back to me with protocol specs (or maybe reverse engineer it from this code), but it should work as of 3.6.0... |
|
|
|
|
It's a mining pool, not a bank...
|
|
|
|
Doesn't matter, there's a pseudonym visible. Anonymity means you cannot name them at all. Bitcoin is at best pseudonymous. Practical difference: a pseudonym can be named/identified and theoretically be found, whereas someone anonymous cannot be identified at all distinct from any other actor. |
|
|
|
Hopefully it won't be forced until Bitcoin-qt supports it. I don't expect it to ever be forced at the blockchain level. |
|
|
|
Does not look like the official client supports that. There is no official client, or official anything. Official implies centralisation. However, I believe that everyone should decide that for themselves Address reuse takes away that choice from other users. Using a unique address per transaction, as Bitcoin was always intended to be used, allows each user to choose for themselves whether they want their transaction record public or not. However, this affects not only the destination but also source addresses as I understand it. There are no source addresses. Addresses are only ever used to receive. So, if I have mined a lot of coins (and on Eligius, all coins go to a single address, can't really change it, can I?) I have to wait longer if I want to make a few smaller purchases? Actually, same applies to coins bought in an exchange - unless I want to spend time manually withdrawing to different addresses. Yes, if you use Bitcoin wrong, this will make your transactions take slightly longer to confirm. That's intentional. I will continue to work closely with wizkid057 to ensure Eligius gets support for BIP32 as soon as possible. I like the current system where I can keep coins received by mining in one address (so if I see the notification that 1P5p... received coins I know it is from mining, 175... means LabRat paid dividends etc). Future software versions implementing BIP32 should be able to notify you based on the recurring invoice id used. |
|
|
|
|
Using bitcoin correctly won't stop your government from tracking you, and isn't intended to.
What it can do, is stop everyone else from tracking you.
|
|
|
|
Hi wizkid,
I was thinking about changing my deposit address. But since my "Share Rewarded" is about 91% right now, I wanted to check if changing addresses and abandoning my old account makes it less likely that those stored shares might be paid someday. Based on my understanding of the reward system I didn't think it would matter, but I wanted to run it by you first. Thanks!
Won't matter. |
|
|
|
My unpaid balance is above my payout threshold, but there is nothing showing in the payout queue (totally blank)
What's going on???
Anyone else seeing the same thing?
I was a few seconds away and jumped to 8 blocks til payout. It does all arrive eventually it seems. Is the preferred payout to new addresses in effect? I see on bitcointax.info that there are choices like on spending Bitcoin, last in first out; or first in first out or averaging. It says if Bitcoins are mixed in an address they can't be separated out. There is suppose to be a tax advantage to one or another scheme. So, wanting us to use new addresses might be to our advantage eventually aside from the reduced ripoff potential. bitcointax.info is wrong; I would have to say whoever wrote it doesn't understand how bitcoin works. |
|
|
|
Is Bi•Fury gonna be supported in the next version? I know it's in the pipeline, just curious.
In fact, you can try the "bifury" branch I pushed to git... It won't report hashrates, but it should mine...  I'll do that this weekend though I won't be able to actually 'try' it until Monday night.  Did you have any heat issues with it? (I'm assuming, of course, that you received an engineering sample.) Plan on using oven gloves to unplug it... |
|
|
|
|
For CPU or scrypt problems, especially on Mac: patches welcome.
|
|
|
|
how would one hot plug a nanofury NF1 through device manager on a windows 7 x32 machine. or can it only be located at startup with hidapi?
Plug it in, hit D M and type in nanofury:auto |
|
|
|
How far off until BFGMiner supports the Drillbit thumbs? Just got mine today and want to start running them on my Pi with BFGMiner as soon as possible to keep power consumption down, as CGMiner is too unstable on the Pi at the moment.
I've not heard anything from Drillbit in a while... |
|
|
|
I've noticed a number of things in README have fallen out of date. If you see any of these and feel like helping out, please just pastebin your modified version and PM me a link to it. Please include in your PM a name and email address for attribution. Thanks, Luke |
|
|
|
How can I get crash logs to you from windows? Ideally, use --debuglog --log-file someuniquefilenameyouwillremember.logPaste the backtrace here (the very bottom of the log); if I need the full file, I will ask for it. |
|
|
|
Is Bi•Fury gonna be supported in the next version? I know it's in the pipeline, just curious.
In fact, you can try the "bifury" branch I pushed to git... It won't report hashrates, but it should mine... |
|
|
|
Maybe you should try to connect to stratum+tcp://stratum.btcguild.com:3333 instead of bitcoin.cz......... bfgminer -o stratum+tcp://stratum.btcguild.com:3333 -x http://proxy.com:8080 -u xxx -p 111 oops. I made a mistake in my post. Yes, I was using stratum.btcguild.com:3333. These are the commands that don't work. bfgminer -o stratum.btcguild.com:3333 -x http://proxy.com:8080 -u xxx -p 111 bfgminer -o stratum+tcp://stratum.btcguild.com:3333 -x http://proxy.com:8080 -u xxx -p 111 bfgminer -o http://stratum.btcguild.com:3333 -x http://proxy.com:8080 -u xxx -p 111 These are the commands that work. bfgminer -o http://api.bitcoin.cz:8332 -x http://proxy.com:8080 -u xxx -p 111 cgminer -o "http:proxy.com:8080|stratum.btcguild.com:3333" -u xxx -p 111 At least I know that I can do it behind my firewall, it's just that I don't now the correct command or bfgminer does not allow connection to stratum via proxy? This is a bug in libcurl for HTTP proxies when combined with CURLOPT_CONNECT_ONLY (needed for stratum). I've found a workaround, and will put it in the next release. Is Bi•Fury gonna be supported in the next version? I know it's in the pipeline, just curious.
Yes. |
|
|
|
The log would look like this: Sorry, the >>>tx/rx was a temporary hack for debugging  If I have time, I'll try to add some equivalent I guess... |
|
|
|
|
Show Posts
