|
For starters you're in the wrong place and time. No one mines bitcoin with GPUs any more.
|
|
|
|
OOOOOOOOOOH. That makes sense. Which version of CGMiner was that added to Icarus?
You can always check the extensively documented NEWS file to see when U1 support was added if you want to use an old version.
|
|
|
|
You're entirely right - I had this feeling like I was saying something but seeing something else, but I wasn't quite sure what it was - but apparently that "--enable-ants1" does do something for the U1's in CGMiner as well. Like I said in a post above, enabling the ants1 configuration with icarus allows the U1's to hash at or just under 1.6ghz each, which is better than the 500mhz block erupter speeds I was getting before with just the icarus configured. Also, the section below has "anu-freq" which affects U1 hashing speeds, so I think I was probably mixing those two up as far as S1/U1 stuff goes.
Also, since both miners use the same chips, I'm guessing they both communicate the same way - so maybe that's part of why the ants1 configuration is fixing the hashing issue.
If the ants1 configuration has nothing to do with the U1's, then why would the U1's be working differently with that enabled than without it?
No no no you're confusing support for the U1 being in the newer cgminer with you enabling S1 support which has nothing to do with it. Support for the U1 is in newer cgminer code with the icarus driver. |
|
|
|
There's no such command as --enable-ants1 I have no idea where you got that. Ancient versions did not support the U1s so the icarus driver randomly ran them not much better than a block erupter. You can always check the extensively documented NEWS file to see when U1 support was added if you want to use an old version.
https://www.dropbox.com/s/fvjes67wygg0ytd/CaptureCGMinerReadMe.PNG - from the ReadMe under "Building CGMiner For Yourself". I included the URL so you could see it's kinda on the webpage with your name on it. --enable-ants1 Compile support for Antminer S1 Bitmain (default disabled) Indeed even I forgot that sorry, since it was code added by Kano, but that says to build for Antminer S1 and you have U1. |
|
|
|
How about one of the older versions before the screen layout change? Do any support Antminer U1 configuration? I know I had to --enable-icarus and --enable-ants1 in order for 4.2.1 to recognize the U1, so I probably will try enabling all support for 3.8.4 (maybe one of the 3.9.x's) to see if I can get the U1's hash speed up - that would also be an acceptable solution. With just --enable-ants1, 4.2.1 didn't notice they were there. Any maybe this makes perfect sense to people here who have a greater understanding of hardware/software interaction and communication. It has been an adventure getting this far off that tutorial and some old forum posts.
There's no such command as --enable-ants1 I have no idea where you got that. Ancient versions did not support the U1s so the icarus driver randomly ran them not much better than a block erupter. You can always check the extensively documented NEWS file to see when U1 support was added if you want to use an old version. |
|
|
|
Scrypt pretty much just skipped FPGAs and went directly to ASICs as FPGAs give horrible Scrypt hashing performance. Though, this is exactly why Scrypt was implemented to make FPGAs and ASICs much less effective.
Not really. It was developed to make GPUs less effective, yet it failed on that front and then everything else followed too. |
|
|
|
You can pretty much assume that mod = scamlover.
There are an awful lot of mods, and that's an awfully unfair generalisation. Given that an awful lot of them act anonymously, I can't say. Maybe some of them are honest. Why do they stay, though? Especially after theymos' repeated failures. Because this is still the prime (and only meaningful) communication forum for bitcoin and those of us who believe in bitcoin try to keep it as useful as possible. |
|
|
|
You can pretty much assume that mod = scamlover.
There are an awful lot of mods, and that's an awfully unfair generalisation. |
|
|
|
Difficulty and nBits (target) are interconvertible; note that pools often use 256-bit expanded form: 0x00000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF being diff 1.
This was only true of the getwork mining era. All stratum pools (should) use true diff 1 as their base now. |
|
|
|
|
Yep, I never said it was impossible, just a lousy idea. Some pools work on zero transaction blocks temporarily on a block change due to some theoretical chance of wining an orphan race but that's likely a bullshit optimisation. Some solo mining "entities" do not include the standard bitcoind recommended transactions and minimise them as an (assumed) optimisation and most pools include a lot of their own stuff. Most pools likely just include all the standard bitcoind transactions as well though, and cgminer's solo mining code definitely does.
|
|
|
|
If difficulty grows by 20% do my earnings tank by 20%? Any reputable site that predicts difficulty? There are a few but they estimate different values.
Yes and no respectively. |
|
|
|
aha! It's the nonce I haven't discovered yet. That isn't in the stratum protocol, which is why I missed it.
So that means the proxy tells the worker you have a pool minus 2 byte counter to work with, and then the miner uses that and the normal 8-byte nonce. That's plenty of space.
Normal 4 byte nonce. thank you. I take modern miners are aware if they reach the end of the space for the nonce and then increment something else, like ntime? M No need, as 8 bytes total is already a ridiculous amount of hashes. |
|
|
|
aha! It's the nonce I haven't discovered yet. That isn't in the stratum protocol, which is why I missed it.
So that means the proxy tells the worker you have a pool minus 2 byte counter to work with, and then the miner uses that and the normal 8-byte nonce. That's plenty of space.
Normal 4 byte nonce. |
|
|
|
|
You are mining bitcoins with GPUs which no one informed today would be doing due to the massive difficulty in the current bitcoin network which is why no one's around to help any more. If you want to get back into bitcoin mining affordably, buy yourself a USB stick like the AntminerU2 instead which does 2GH for much less cost than your GPU and use your GPU for graphics the way it was intended.
|
|
|
|
|
It's virtually impossible to mine blocks with a CPU full stop, and it is no easier to mine blocks without transactions.
But yes, it is possible to mine blocks with zero transactions, but then that would defeat the purpose of mining, which is actually to proliferate transactions and secure the network, and the block reward is a reward for their work, though miners seem to forget that... If enough people/pools mined blocks with zero transactions it would make bitcoin suffer and the value drop as a result of lost confidence in its reliability and whoever was mining them would lose indirectly due to the drop in value.
|
|
|
|
|
The question was rhetorical. Only altcoin miners and botnets are cpu mining these days, neither of which is relevant here.
|
|
|
|
|
Share diff is chosen by the pool to find an optimal spread between bandwidth to the pool and variance to the miner. The choice of value chosen by the pool is arbitrary but most target diff to work out to somewhere around 20 shares submitted by the miner per minute. Difficulty of the share submitted is paid only based on the share difficulty asked for by the pool, though it can be much much higher (and ideally higher than the network difficulty in order to solve a block for the pool). Difficulty is internally determined in cgminer by checking the ratio of the share hash to diff1 where diff 1 is 26959535291011309493156476344723991336010898738574164086137773096960. Imagine every share's hash is just one massive number.
The 65536 constant mentioned earlier has nothing to do with bitcoin. Ignore it.
|
|
|
|
I do recall a push by the bfgminer author to put longpoll into the bitcoind client to inform mining software of block changes but no such thing exists, so perhaps he does nothing special to make sure you're working on a new block. Cgminer checks every 0.5 second when mining solo to bitcoind.
Can cgminer be set up to mine with a network device? (I have ASICminer Block Erupter Cubes) I wanted to try it but I think I would need a miner that I could connect directly by USB to my computer running cgminer. I don't see an option to specify a network port where it should listen to my miners... Or is there a way to use it with BE Cubes? Nope, cgminer doesn't act as a proxy to other mining software (and the cubes have their own primitive mining software). |
|
|
|
|
Show Posts
