Bitcoin Forum
June 22, 2024, 06:15:49 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 [95] 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 ... 155 »
1881  Bitcoin / Mining software (miners) / Re: BitMinter.com * Optional Custom Miner, PPLNS, Merged mining, Newbie-Friendly! * on: March 01, 2013, 10:13:15 PM
Here's an exempt of the error log I get:
[...]

That's the Java virtual machine crashing, most likely inside the AMD drivers. If you look a little further down it probably says it crashed in amdocl.dll (AMDs OpenCL drivers on Windows).

If you uninstall the AMD drivers, run driver sweeper to clean up, and then reinstall an older version, you should be ok.
1882  Bitcoin / Mining software (miners) / Re: BitMinter.com * Optional Custom Miner, PPLNS, Merged mining, Newbie-Friendly! * on: March 01, 2013, 12:36:01 PM
Newbie here, hope to get started using this..

Welcome Smiley Let us know if you have any problems.
1883  Bitcoin / Mining software (miners) / Re: BitMinter.com * Optional Custom Miner, PPLNS, Merged mining, Newbie-Friendly! * on: March 01, 2013, 12:05:32 PM
AMD uninstall never uninstalls properly.

You may want to try driver sweeper: http://www.guru3d.com/content_page/guru3d_driver_sweeper.html
I haven't had to do this in a long time, if there's a better tool for this now, someone speak up.

So you uninstall, run driver sweeper, then re-install Catalyst 13.1.
1884  Bitcoin / Mining software (miners) / Re: BitMinter.com * Optional Custom Miner, PPLNS, Merged mining, Newbie-Friendly! * on: March 01, 2013, 11:41:54 AM
I was using GUIminer for some time without any problems on Slush's pool .
After upgrading to latest ati drivers (13.2 beta 7) I get ' Verification failed, check hardware! (0:0:Juniper, dc83aea6)'
Tried poclbm = crash
Tried cgminer= crash
The only working miner is bitminter but I get a error 'BFI patch failed'

If you turn off BFI (click the little green arrows to expand the display then click the wrench for settings), then it will perhaps work, but it will run rather slowly without BFI.

Have you tried Catalyst 13.1, which is the latest stable release? 13.2 is still just a beta.
1885  Bitcoin / Pools / Re: [2000 GH/s] BitMinter.com [ASIC support: var diff, Stratum, GBT, rolllntime] on: February 28, 2013, 09:51:58 PM
Is this a temporary issue or shutdown permanently?

If you go to myid.net it redirects you to another site which displays a message in korean. It's an image so you can't paste it into google translate. But one miner told me that myid.net have shut down permanently.
1886  Bitcoin / Pools / Re: [2000 GH/s] BitMinter.com [ASIC support: var diff, Stratum, GBT, rolllntime] on: February 28, 2013, 06:17:08 PM
The OpenID identity provider myid.net appears to have shut down. If you can't get into your BitMinter account because of this, contact me at operator@bitminter.com

question about walletbit.com

Haven't seen that one. An online wallet? I hope it's temporary.
1887  Bitcoin / Pools / Re: [2000 GH/s] BitMinter.com [ASIC support: var diff, Stratum, GBT, rolllntime] on: February 25, 2013, 06:35:30 PM
How does the pool take into account the miner's higher difficulty set point that would correlate to a lower submitted hash rate and the payout share?

It pretends like one proof of work mined at difficulty 32 is 32 proofs of work at difficulty 1. So the payout is fair, but there is a little more variance at higher difficulty. As far as I know this is how all the pools handle variable difficulty.

If you want to know more about that I'd suggest you check out organofcorti's blogpost about it: http://organofcorti.blogspot.com/2012/10/71-variable-pool-difficulty.html
1888  Bitcoin / Pools / Re: [2000 GH/s] BitMinter.com [ASIC support: var diff, Stratum, GBT, rolllntime] on: February 25, 2013, 05:20:01 PM
My apologies if you have already covered the subject, but ... what are your commits on the use of mining_proxy with the new ASIC boxes coming online?

And does anyone know if bfgminer supports the variable difficulty being talked about here?

My recommendation is to not use proxies unless you actually need them. Bfgminer has Stratum and vardiff support built in, so you'd be better off connecting it directly to the pool. But  if you have multiple mining computers on a local network, you may save a little bandwidth by using a Stratum proxy instead of having each connect to the pool directly.
1889  Bitcoin / Pools / Re: [ANN] Stratum mining protocol - ASIC ready on: February 25, 2013, 07:14:52 AM
This looks good. Thanks for including the user-agent in there as well.

Note the session ID has changed between the initial subscription and the resume, BUT the extranonce1 has remained the same. This tells the miner it can (re)submit shares before the disconnection.

If the resume fails, how should the server respond? Give an error, or just a new extranonce1?

If the old connection is still there, I guess the server could disconnect it. That means the session ID must be hard to guess so you can't disconnect other people. You must also be very sure that you don't give out the same session ID twice, or you'll have two workers disconnecting each other all day.

It's safer to never resume a connection that still appears up to the server. But I wonder how often it will happen that a client tries to resume before the server discovers that the old connection is dead.

Letting both connections stay seems like a bad idea. They'd both be doing the same hashes in the unlikely event that they both keep hashing.
1890  Bitcoin / Pools / Re: [2000 GH/s] BitMinter.com [ASIC support: var diff, Stratum, GBT, rolllntime] on: February 23, 2013, 09:45:12 PM
Back up again. Sorry for the downtime.

bitcoind went haywire with disk accesses, but a restart cleared it up.
1891  Bitcoin / Pools / Re: [2000 GH/s] BitMinter.com [ASIC support: var diff, Stratum, GBT, rolllntime] on: February 23, 2013, 09:32:29 PM
Having an issue with the server. Looking into it now.
1892  Bitcoin / Pools / Re: [2000 GH/s] BitMinter.com [ASIC support: var diff, Stratum, GBT, rolllntime] on: February 22, 2013, 09:29:04 PM
Var diff can slow things down a bit. Do you have plans to implement preconfigurable diff per worker in near feature? For 64300-64500 MHash/s diff about 64 shall be just right in order to have about 20 submited shares per minute and not to "flood" the pool right?

Bitminter adjusts the diff quite quickly. Asicminer tested the pool with much more hashrate than one Avalon and the pool adjusted (it maxed out at 64 at the time, but I have set a higher max now). That said, there are plans to allow setting a minimum diff.

PS: As long some instability issues are reported from avalon users a nice feature available via perks will be inactivity mail notification - per worker. What about it?

Yep, that's also on the TODO list.
1893  Bitcoin / Pools / Re: [ANN] Stratum mining protocol - ASIC ready on: February 22, 2013, 06:26:04 PM
There's mining.reconnect(). It should work in proxy, poclbm and cgminer too.

Is this an extension? Where are those documented?
1894  Bitcoin / Pools / Re: [2000 GH/s] BitMinter.com [ASIC support: var diff, Stratum, GBT, rolllntime] on: February 22, 2013, 03:40:44 PM
Can i share this with Kon after i check it?

Of course. Anonymize out your IP address if you want. I didn't do that as I was sending it only to your email address and it could be helpful to you.
1895  Bitcoin / Pools / Re: [2000 GH/s] BitMinter.com [ASIC support: var diff, Stratum, GBT, rolllntime] on: February 22, 2013, 03:20:30 PM
1.when i mine with getwork with diff 1 given by the pool i submit every share
2. When i mine with stratum and diff 8 given by the pool i submit one of eight at average - there is variation of course
3. Is it possible in theory that those 8 shares skipped to be able to solve the block? Because if i was using getwork with diff 1 given by the pool they shall be ok and submitted to the pool right?

If your proof of work hash is above difficulty 1.6 million then it is also above difficulty 8, so there won't be any problems. Any proof of work that can create a valid block will be submitted by the client.

Edit: I emailed the data that was logged about your proof of work to the email address registered with your Bitminter account.
1896  Bitcoin / Pools / Re: [2000 GH/s] BitMinter.com [ASIC support: var diff, Stratum, GBT, rolllntime] on: February 22, 2013, 02:30:28 PM
Recently i found a block but cgminer did not report it. I have found blocks before with getwork and i was able to see Found block count > 0 matching the actual found blocks reported buy bitminter

Maybe this is a bug in cgminer. Or if you have multiple workers, did you check them all?

1. Mining software knows that it shall shall submit work only if its matching difficulty (let say 4).
2. Mining software shall check if valid shares which are less that required difficulty solve the block

You mean above the required difficulty to solve the block. Above difficulty = below target.

3. If yes they shall be submitted to the pool even though they are not matching pool difficulty

The difficulty given by the pool (1-4096 currently) will always be lower than the difficulty for creating a block (currently 3.6 million).

Even if the mining difficulty was not capped (currently at 4096) you would still need a worker with a hashrate that would produce 20 bitcoin blocks per minute on average, for the server to give you a mining difficulty that is higher than the difficulty to create a block. If you receive enough ASICs for that then I recommend splitting them up over multiple worker accounts, at least until the network difficulty goes up.

What i am asking is are any potential issues from both miner and pool if a share solving the block can be rejected by the pool or not sent by software?

It could be a potential problem if you added a new worker that had 200 times the hashpower of the rest of the network. So if the current network hashrate is 30 TH/s and you add hardware doing 6000 TH/s on a single worker account, then we need to look into it. In that case, please let me know in advance. Wink
1897  Bitcoin / Mining software (miners) / Re: Will 50 BTC and Deepbit move to Version 2 blocks? on: February 21, 2013, 12:19:34 PM
Ask your pool operator to upgrade or switch to a different pool.
1898  Bitcoin / Pools / Re: [ANN] Stratum mining protocol - ASIC ready on: February 21, 2013, 06:43:02 AM
Is it possible to use the existing unique subscription ID as the session ID with mining.resume instead?

Sounds good to me, mine is just hardcoded to "1" at the moment. I'll make it unique when it is actually used for something. Wink

Pool should not close the connection on unknown message.

Can this go in the docs?

As well as mining.resume and mining.identify or whatever the "which client version are you" message is called.
1899  Bitcoin / Pools / Re: [ANN] Stratum mining protocol - ASIC ready on: February 20, 2013, 05:26:30 PM
I do see reasons to implement a difficulty setting in the miner

What are those reasons?

How would it work? Would it be a suggestion that the server can take under advisement and choose to ignore?
1900  Bitcoin / Pools / Re: [2000 GH/s] BitMinter.com [ASIC support: var diff, Stratum, GBT, rolllntime] on: February 19, 2013, 09:46:17 PM
Hmm.. I had cgminer 2.10.2 and upgraded to 2.10.5 and still get a lot of rejects (about 9%), although not from 'below difficulty' as an error, just 'rejects'. Running for a day with just the regular getwork server via the nginx/PHP proxy I use and I get nearly zero rejects. I will try again with direct from miner to the stratum proxy and see if it's my nginx/PHP proxy getting in the way. Pity it if is since it's SO useful for pool failovers and configurations and monitoring all miners at once.

Yeah, 9% is ridiculous. Something is wrong there. I guess somewhere in your dual proxy setup things get slowed down a lot. Try connecting cgminer directly to the pool and see how that works.

Poolwide rejects for the current round is 0.16% as I write this. I'd expect some getwork users are above and most Stratum users are below that.
Pages: « 1 ... 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 [95] 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 ... 155 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!