Bitcoin Forum
December 14, 2017, 09:55:26 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
  Home Help Search Donate Login Register  
  Show Posts
Pages: « 1 ... 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 »
1901  Bitcoin / Pools / Re: [350 GH/s] "Eligius" (experimental) pool: almost feeless PPS, hoppers welcome on: June 28, 2011, 07:44:16 PM
Stickied.
1902  Bitcoin / Mining / Re: Missing threads, blame Theymos on: June 28, 2011, 06:51:55 PM
Roll Eyes


Small problem is I deleted a couple posts. So, I'm thinking I accidentally tripped on database corruption.

Especially since people are reporting missing threads in forum sections that I don't have mod powers on.
1903  Bitcoin / Mining / Missing threads, blame Theymos on: June 28, 2011, 05:32:03 PM
Apparently the board has decided to eat a bunch of threads because its PHP and MySQL.

Goddamnit Theymos.
1904  Other / CPU/GPU Bitcoin mining hardware / Re: DiabloMiner GPU Miner (Long Poll, BFI_INT, and never fail async networking) on: June 28, 2011, 12:54:06 AM
In the part where you enqueue the work to the gpu and then read the output buffer , why do you alternate two buffers? ( buffer and output are two arrays of two buffers)

Because its faster on some setups.
1905  Other / CPU/GPU Bitcoin mining hardware / Re: DiabloMiner GPU Miner (Long Poll, BFI_INT, and never fail async networking) on: June 27, 2011, 06:01:24 AM
Update: Added bitless's hack.

My 5850@918 on 2.1 went from 369 to 378, so a 2.4% increase.
1906  Other / CPU/GPU Bitcoin mining hardware / Re: DiabloMiner GPU Miner (Long Poll, BFI_INT, and never fail async networking) on: June 27, 2011, 05:56:48 AM
Slush pool says to avoid new Diablominer. Luckily i had a backup of old diablominer & using it now.

http://forum.bitcoin.org/index.php?topic=1976.msg285661#msg285661
I even started a thread on this subject weeks ago and just got a lot of BS replies from people that couldn't believe it. The effective hash rate on my pool which = my payut didn't lie. It was actually slower..

I can't comment on later versions of phoenix, but I log all my shares with phatk+phoenix svn r64 (which is what I'm mostly running) and the hash meter expected shares agrees quite closely with the actual ones. ::shrugs::


Slush pool says to avoid new Diablominer. Luckily i had a backup of old diablominer & using it now.

http://forum.bitcoin.org/index.php?topic=1976.msg285661#msg285661

This is a very good point, I haven't tried the new build yet since  the build I pulled down 2 weeks ago is working so well for  my 6 GPU system but this is a concern, the async work is great so hopefully it can be sorted.

IIRC, the async work is what is incompatible with slush. It has nothing to do with the new kernel at all.  Basically when the miner would otherwise be idle it increments the ntime anyways, hoping that the pool will still accept those shares.  On slush, it won't so that work is wasted, but it would have been wasted regardless.  The solution to that is to use a better pool, IMO.

It's also broken with flexible mining proxy. Does anyone know how to get back to pre async?

Perhaps an option to specify no ntime increments.

Pools and proxies that can't handle ntime being incremented by one or two need to be fixed.
1907  Other / CPU/GPU Bitcoin mining hardware / Re: DiabloMiner GPU Miner (Long Poll, BFI_INT, and never fail async networking) on: June 26, 2011, 04:52:48 AM
lol pool went down at time of update, what a coincedence...

Cant be me.. 90% shares arent being submitted?

Bug?

Miner 1
mhash 177.7/178.9 | a/r/hwe: 1/0/0 | ghash: 110.2 | fps: 30.0

Miner 2
mhash 819.5/826.6 | a/r/hwe: 0/3/0 | ghash: 114.0 113.3 112.3 | fps: 30.2

Quote
[24/06/11 8:49:58 PM] DEBUG: Attempt 77 found on Cypress (#3)
[24/06/11 8:50:02 PM] DEBUG: Attempt 78 found on Cypress (#2)
[24/06/11 8:50:07 PM] DEBUG: Attempt 79 found on Cypress (#2)
[24/06/11 8:50:12 PM] DEBUG: Attempt 80 found on Cypress (#3)
[24/06/11 8:50:13 PM] DEBUG: Attempt 81 found on Cypress (#2)
[24/06/11 8:50:14 PM] DEBUG: Attempt 82 found on Cypress (#3)
[24/06/11 8:50:15 PM] DEBUG: Attempt 83 found on Cypress (#2)
[24/06/11 8:50:18 PM] DEBUG: Attempt 84 found on Cypress (#3)
[24/06/11 8:50:21 PM] DEBUG: Attempt 85 found on Cypress (#1)
[24/06/11 8:50:23 PM] DEBUG: Attempt 86 found on Cypress (#2)
[24/06/11 8:50:33 PM] DEBUG: Attempt 87 found on Cypress (#2)

both updated to latest git

Just updated windows machine

Quote
[24/06/11 8:56:17 PM] DEBUG: Attempt 3 found on Cayman (#2)
[24/06/11 8:56:18 PM] DEBUG: Attempt 4 found on Cayman (#2)
[24/06/11 8:56:20 PM] DEBUG: Attempt 5 found on Cayman (#2)
[24/06/11 8:56:26 PM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 8:56:31 PM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 8:56:32 PM] DEBUG: Attempt 6 found on Cayman (#2)
[24/06/11 8:56:32 PM] DEBUG: Attempt 7 found on Cayman (#2)
[24/06/11 8:56:34 PM] DEBUG: Attempt 8 found on Cayman (#2)
[24/06/11 8:56:38 PM] DEBUG: Attempt 9 found on Cayman (#2)

mhash 364.5/362.8 | a/r/hwe: 0/1/0 | ghash: 30.1 | fps: 30.4

Nothing is being submitted?

EDIT: now how do i go back to the old version?

Nope, it's Diablominer and/or flexible proxy (though i never touched the proxy). It will find a few results, submit one or two and say accepted. After that "Attempt found" but never submit it?

Phoenix works 100% rock solid

The proxy probably does not correctly support things DiabloMiner does, such as time incrementing and returning multiple nonces for the same getwork over short periods. It looks like the sendwork thread is being choked by the proxy.

So, clearly, its a proxy bug.
1908  Other / CPU/GPU Bitcoin mining hardware / Re: DiabloMiner GPU Miner (Long Poll, BFI_INT, and never fail async networking) on: June 26, 2011, 04:47:35 AM
The new frankenkernel seems to have lost me about 10 mhash/s. I'm on a 6990@910 (mem 625). Using -v 2 -w 128 (increasing -w made things worse, as did fiddling with -v).

-v 2 -w 128 should be as fast as phatk VECTORS WORKSIZE=128 on your machine. If it isn't, then its just more proof Phoenix has a broken hash meter.
1909  Other / CPU/GPU Bitcoin mining hardware / Re: DiabloMiner GPU Miner (Long Poll, BFI_INT, and never fail async networking) on: June 26, 2011, 04:46:00 AM
Uodate: Behold, the frankenkernel. A mix of DiabloKernel and phatk.

Before this, I got 369 mhash on my 5850@918 on SDK 2.1, and 352 on 2.4 post-11.4 (thanks AMD!)

Now I get 369 on 2.1 AND 2.4.

AMD, you can't hide. I am coming for you.
oh hey it started working for me now
not as fast as poclbm, though

Use -v 2 with either -w 128 or 256. -v 3/19 settings don't seem to be optimum anymore.
1910  Other / CPU/GPU Bitcoin mining hardware / Re: DiabloMiner GPU Miner (Long Poll, BFI_INT, and never fail async networking) on: June 26, 2011, 04:41:40 AM
Uodate: Behold, the frankenkernel. A mix of DiabloKernel and phatk.
Before this, I got 369 mhash on my 5850@918 on SDK 2.1, and 352 on 2.4 post-11.4 (thanks AMD!)
Now I get 369 on 2.1 AND 2.4.
AMD, you can't hide. I am coming for you.

Congrats, you're finally as fast as phoenix / phatk for meó actually about 0.4% faster it looks like.  (Only tested it on the 5850s with SDK 2.4 so far)

I seemed to be getting high stales with -f0, -f1 was fine but it could have just been bad luck. There didn't appear to be much if any hashrate difference, so I just left it at 1%.

Still need the ability to loadshare (ideally) or fail over between multiple pools.   But it's looking pretty good.  Good work.


Don't use -f 0. I need to add an error message for that, as far as I can tell, instead of dividing by zero, it just steadily increases the worksize to maximum of 2^32 (or about 0.1 fps give or take).

Loadshare might be halfway easily to implement. Not sure.
1911  Other / CPU/GPU Bitcoin mining hardware / Re: DiabloMiner GPU Miner (Long Poll, BFI_INT, and never fail async networking) on: June 25, 2011, 03:03:26 PM
Uodate: Behold, the frankenkernel. A mix of DiabloKernel and phatk.

Before this, I got 369 mhash on my 5850@918 on SDK 2.1, and 352 on 2.4 post-11.4 (thanks AMD!)

Now I get 369 on 2.1 AND 2.4.

AMD, you can't hide. I am coming for you.
1912  Other / CPU/GPU Bitcoin mining hardware / Re: DiabloMiner GPU Miner (Long Poll, BFI_INT, and never fail async networking) on: June 24, 2011, 11:47:38 PM
Random question: Does DiabloMiner support MMP?

No.
1913  Other / CPU/GPU Bitcoin mining hardware / Re: DiabloMiner GPU Miner (Long Poll, BFI_INT, and never fail async networking) on: June 24, 2011, 05:30:49 AM
Update: Change execution thread count from 3 to 2. More efficient, no longer need 3 because of fully async getwork.
1914  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner GPU Miner Thread (now with Long Poll and BFI_INT support) on: June 24, 2011, 05:11:19 AM
Update: Finish async networking, now everything is async. getwork, sendwork, and LP now use 1 thread per miner instance instead of 3 per GPU.

So, no matter how much Eligius lags out, it can't stop mining.
1915  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner GPU Miner Thread (now with Long Poll and BFI_INT support) on: June 24, 2011, 02:10:57 AM
xorg wierdness, restarted x and all is well.

Now with all 3 i get alot of force getworks?

Quote
[24/06/11 9:38:27 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:30 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:31 AM] DEBUG: Attempt 120 found on Cypress (#1)
[24/06/11 9:38:31 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:31 AM] DEBUG: Attempt 121 found on Cypress (#3)
[24/06/11 9:38:31 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:32 AM] Accepted block 115 found on Cypress (#1)
[24/06/11 9:38:32 AM] Accepted block 116 found on Cypress (#3)
[24/06/11 9:38:33 AM] DEBUG: Attempt 122 found on Cypress (#2)
[24/06/11 9:38:33 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:33 AM] Accepted block 117 found on Cypress (#2)
[24/06/11 9:38:34 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:36 AM] DEBUG: Attempt 123 found on Cypress (#2)
[24/06/11 9:38:37 AM] Accepted block 118 found on Cypress (#2)
[24/06/11 9:38:39 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:40 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:52 AM] DEBUG: Attempt 124 found on Cypress (#2)
[24/06/11 9:38:53 AM] Accepted block 119 found on Cypress (#2)
[24/06/11 9:38:58 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:39:04 AM] DEBUG: Attempt 125 found on Cypress (#2)
[24/06/11 9:39:05 AM] Accepted block 120 found on Cypress (#2)

Thats normal. At 300 mhash, you can see 3 nonce saturations happen every 45 seconds.
1916  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner GPU Miner Thread (now with Long Poll and BFI_INT support) on: June 23, 2011, 12:13:49 PM
using aticonfig to list the adaptors i see all 3, diablo only uses 2 to mine?

If your setup is configured correctly, it will use all 3.
1917  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner GPU Miner Thread (now with Long Poll and BFI_INT support) on: June 22, 2011, 06:01:15 PM
I'm having a look at your code because i would like to understand how a miner works.
I have a few questions.
Where i can find how is stored the data contained in the work sent to the miner from the server ?
Also could you explain a little bit in few words what happens in lines of code between 888 and 944?
Here:
Code:
bufferIndex = (bufferIndex == 0) ? 1 : 0;

          workSizeTemp.put(0, workSize);
          currentWork.update(workSizeTemp.get(0) * loops * vectors);

          System.arraycopy(currentWork.midstate, 0, midstate2, 0, 8);

          sharound(midstate2, 0, 1, 2, 3, 4, 5, 6, 7, currentWork.data[16], 0x428A2F98);
          sharound(midstate2, 7, 0, 1, 2, 3, 4, 5, 6, currentWork.data[17], 0x71374491);
          sharound(midstate2, 6, 7, 0, 1, 2, 3, 4, 5, currentWork.data[18], 0xB5C0FBCF);

          int fW0 = currentWork.data[16] + (rot(currentWork.data[17], 7) ^ rot(currentWork.data[17], 18) ^
                    (currentWork.data[17] >>> 3));
          int fW1 = currentWork.data[17] + (rot(currentWork.data[18], 7) ^ rot(currentWork.data[18], 18) ^
                    (currentWork.data[18] >>> 3)) + 0x01100000;
          int fW2 = currentWork.data[18] + (rot(fW0, 17) ^ rot(fW0, 19) ^ (fW0 >>> 10));
          int fW3 = 0x11002000 + (rot(fW1, 17) ^ rot(fW1, 19) ^ (fW1 >>> 10));
          int fW15 = 0x00000280 + (rot(fW0, 7) ^ rot(fW0, 18) ^ (fW0 >>> 3));
          int fW01r = fW0 + (rot(fW1, 7) ^ rot(fW1, 18) ^ (fW1 >>> 3));

          int fcty_e = currentWork.midstate[4] + (rot(midstate2[1], 6) ^ rot(midstate2[1], 11) ^ rot(midstate2[1], 25)) +
                       (midstate2[3] ^ (midstate2[1] & (midstate2[2] ^ midstate2[3]))) + 0xe9b5dba5;
          int fcty_e2 = (rot(midstate2[5], 2) ^ rot(midstate2[5], 13) ^ rot(midstate2[5], 22)) + ((midstate2[5] & midstate2[6]) |
                        (midstate2[7] & (midstate2[5] | midstate2[6])));

          int fcty_e_plus_e2 = fcty_e + fcty_e2;
          int fcty_e_plus_state0 = fcty_e + currentWork.midstate[0];
I also noticed that i get 'Spurious CL_INVALID_KERNEL_ARGS error, ignoring' when running with -d enabled, what could it be ?
Thanks for the patience Cheesy

884 through 903 use shortcuts to do less math in the OpenCL kernel (because the math is the same for all the runs). The rest of 903 through 944 just executes the kernel, checks for errors, and then sets up a blocking buffer read.

As for that warning, it indicates a driver bug. As long as it happens only once in awhile, you're fine.
1918  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner GPU Miner Thread (now with Long Poll and BFI_INT support) on: June 22, 2011, 12:24:03 AM
I run 2 6990s and 1 hour ago i was getting about .5 hw errors per second and full speed on the newest version.

Then there was a power brownout and all my equipment froze and restarted. When I restarted, the newest version gave me 75-85% of speed under the same settings and 1000 hw errors per second. However on the old version which I switched back to now, I get 100% speed still.  I had this problem before, and what might have fixed it is reseating the cards. But if thats the problem why does the old version work fine?

If you're getting a lot of HW errors, the miner is probably slowing down.
1919  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner GPU Miner Thread (now with Long Poll and BFI_INT support) on: June 22, 2011, 12:02:27 AM
ups sorry, im sleepy Smiley

There is no rest ... thats all
I forgot to tell you that i connect to proxy ( http://forum.bitcoin.org/index.php?topic=5506 ) and than to slush, deepbit or btcguild.

Im just wondering that it runs about 30h-40h very smoth and than i have this endless loop ... stoping ... waiting 5 seconds .... restart and every thing is smoth for the next day Smiley

Thanks for your time and support.

cheers


Sounds like the proxy is trying to report an error message, I wish I knew what it was saying.
1920  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner GPU Miner Thread (now with Long Poll and BFI_INT support) on: June 21, 2011, 11:48:21 PM
Hello,

first thanks for your great Miner and thanks to all who help with those projects.

There is a little problem, sometimes the miner runs in an endless loop:
Code:
ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: <?xml version="1.0" encoding

There is no way that it stops.

If i stop the miner from requesting work, wait some second than restart it, everytihing is fine.
Maybe there is a parameter that i dont see to tell the miner just wait 10 seconds if this happens and than start asking for work again.

cheers
carlo

I wish I knew what the rest of that is. What are you connecting it to?
Pages: « 1 ... 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 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!