You running it off 2.0 or 3.0 port? The device negotiates as USB 1.1, plugged into my USB 2.0 hub. Without an adapter, you cannot plug USB 1.1/2.0 devices into USB 3.0 ports.Excuse me?  Yeah, nevermind that... I was looking at some other kind of port the whole time. My USB 3.0 ports are occupied by keyboard/mouse so I didn't see them >_< Now I'm curious what these other ports are  Edit: Apparently my motherboard has 2 eSATA ports I wasn't aware of  |
|
|
|
Can you measure the thickness of the board+sink?
Also, how wide is the board? | ________________Measurement | Tonal | Imperial | SI | | Thickness: | 9 Mˢ | 0.23in | 6mm | | Width: | 29 Mˢ | 1in | 25mm | | Length: | 68 Mˢ | 2.4in | 60mm | | Length protruding from USB port: | 5 Mˢ | 2.1in | 53mm | | Length of PCB: | 4 Mˢ | 1.8in | 45mm |
You running it off 2.0 or 3.0 port? The device negotiates as USB 1.1, plugged into my USB 2.0 hub. |
|
|
|
Eloipool modified for scrypt isn't that difficult and it has vardiff and stratum. Likewise, it's also not hard to modify pushpool to support stratum and vardiff. To my knowledge, there is no out of the box, open source on github pushpool with vardiff and stratum. The pool operators either modified it and didn't release it or use a different poolserver. I have only granted AGPL licensing for Eloipool, so if someone is running a poolserver based on it without exposing the source code, they are infringing. Feel free to let me know who, if anyone, is doing this, and I will have a chat with them (and throw the book if necessary). But first, be sure they're actually infringing: grab a HTTP header from the poolserver and check out the path in the X-Source-Code header.  |
|
|
|
You make it sound like BFGMiner is some sort of original product? Didn't you just fork his code and then now you are bashing the original devs? BFGMiner is based on cgminer-the-GPU-miner which is based on cpuminer. Present day cgminer is a fork of BFGMiner, created by trolls for trolling. |
|
|
|
Please be wary of other software where they don't tell you these required options or don't have a release that works with it yet. BFGMiner doesn't require those options, just -S all (or specify the specific COM port). The only reason there isn't a BFGMiner 3.1.0 release yet is actually because of a cgminer screwup that you probably don't even know exists. The next release of cgminer will automatically handle it without any options required and it will also handle you being able to just plug it in while cgminer is already running.
You can also start cgminer with no devices and then plug it in and it will start mining with it. But all this.. only if you manually install a non-standard driver for it. cgminer, the original USB miner and the best. More outright lies. No surprise coming from Kano. |
|
|
|
Hello, I'm a newbie and I have a question: which of cgminer and bfgminer is better to use with Block Erupter USB? BFGMiner is much better in general - it supports nearly everything cgminer does, plus more bugfixes and enhancements. |
|
|
|
Now we're looking at the code.
This wasn't the exact file I had but maybe something has changed I don't know, it's close enough in the places that matter anyways.
Anyways for the crux of my argument, take lines 124 through 142 which consist of the bulk of the random number generator.
These are currently implemented as defines.
That isn't a random number generator. You're looking at macros for the SHA256 rounds. Just stop, and go read the scrypt whitepaper. Immediately, if not sooner.. I'm not trying to be rude, it's just that an immediate read of the scrypt whitepaper will be better use of your time at this point. Well, strictly speaking scrypt is using SHA256 as a random number generator... |
|
|
|
Greetings to all.
just bought a pair of boards, working with BFGMiner fine, but a I have lot of HW errors. It is normal or something to be done?
Can you post the stat line? Does it report adjusting the clock speed down? to Luke-Jr  Hw error rate here doesn't look too bad - if it's with a dynamic clocking firmware, I'd expect it would have downclocked a bit. |
|
|
|
|
The only cases I am aware of people having trouble "upgrading" wallets, is really because their wallet got corrupted somewhere along the lines.
If Bitcoin-Qt (or any other Satoshi-based client) does not cleanly exit, your wallet.dat is not intact!
It will depend on the database/ subdirectory until you resolve it with a clean shutdown.
If that directory disappears on it (or is replaced, etc), you may be losing money.
|
|
|
|
So to summarize things a bit ... if anyone were to donate a device, there's two people interested: - a guy who refuses to do anything for the device until it's been given to him, and threatens to remove support at all unless people help him because he's rewriting the code using an inferior interface for no reason (Kano)
- a guy who's actually put effort and hours of time into providing full support for a device he doesn't have, and uses standard interfaces to ensure maximum compatibility (myself)
You left out the part where you also intimidate and coerce people into paying you BTC in IRC ... Or that more than half the Icarus code was written by me and you copied it and claimed it was yours. Edit: though I should also point out the TYPICAL Luke-Jr lie there. I wrote the code for the first support for Cairnsmore1 ... yet I still don't have one. (Yohan had a version of cgminer before me where they only changed the baud but nothing else) Yeah, you can go ahead and keep on making up lies... sigh I offered you Cairnsmore1 access, I can give you ssh or something to debug - you refuse I gave you 3 patches: 0003-driver-icarus-add-re-open-device-after-com-errors.patch
0002-api-for-icarus-return-com-port-as-device-ID.patch
0001-driver-icarus-display-com-port-in-statusline.patch You said not possible to add them, because they not compatible or something - so why they are working for me with cgminer for months? And finally you didn't even bother to reply to my last two messages If you'd like to submit them to BFGMiner (preferrably via a pull request on github), I'd be glad to take a look. |
|
|
|
So to summarize things a bit ... if anyone were to donate a device, there's two people interested: - a guy who refuses to do anything for the device until it's been given to him, and threatens to remove support at all unless people help him because he's rewriting the code using an inferior interface for no reason (Kano)
- a guy who's actually put effort and hours of time into providing full support for a device he doesn't have, and uses standard interfaces to ensure maximum compatibility (myself)
|
|
|
|
Any ideas how to run in mac? Thanks.
BFGMiner can be compiled for Mac if you disable GPU mining, at least. I think it's part of Homebrew now. Do you mean without CPU mining? I compiled a very custom linked version today and it didn't compile with CPU mining but everything else (that's supported on Mac) worked fine. Which driver does the block erupter use? CPU mining is disabled by default. I wasn't sure what the state of GPU mining was. Block Erupter uses the Icarus driver, but you need the latest git for it to autodetect the configuration properly. |
|
|
|
Any ideas how to run in mac? Thanks.
BFGMiner can be compiled for Mac if you disable GPU mining, at least. I think it's part of Homebrew now. |
|
|
|
blah blah blah I am God, my code doesn't need to be any good to say it's the best cos I say so
Luke - go away. <snip trolling and lies> Here - read my lips - fuck off and die please. As I've offered before, I will gladly ignore this thread entirely if you will stop trolling and spreading lies about BFGMiner and myself. Yet again another lie by you. You posted your bullshit lies in here and I simply responded to the lies you posted. You have now even removed (or had removed) your post ... coz it was lies. CAN YOU PLEASE STOP STALKING CGMINER? IS THAT POSSIBLE? Prove one thing I said in that post was a lie. One thing. No - of course not - because it was true. Luke-Jr - never proves his accusations coz he can't coz they are indeed lies. LOL, I'm stalking? Who is it following me around to troll everywhere I post? ...oh, that's Kano! What a surprise. Hypocrite. |
|
|
|
blah blah blah I am God, my code doesn't need to be any good to say it's the best cos I say so
Luke - go away. <snip trolling and lies> Here - read my lips - fuck off and die please. As I've offered before, I will gladly ignore this thread entirely if you will stop trolling and spreading lies about BFGMiner and myself. |
|
|
|
Do these little guys have a temp sensor on them? Anyone know offhand? Not accessible by software, at least. |
|
|
|
Here's the build arklan ended up using: Win64 | Win32 |
|
|
|
Here's the build arklan ended up using: Win64 | Win32 |
|
|
|
|
Show Posts
