Latest posts of: JRyoku

Show Posts
Pages: [1]

on: August 02, 2014, 02:55:44 PM

If you devs want to make some money off your miners, you need to get more serious. Design a GUI for your miner with auto loading ads on the bottom of it. Include a way to pay a small BTC fee to remove ads from the GUI. In my perfect world, the miner would be a stand alone program that doesn't have to be updated and all the algos are loaded into .dll files. That would be something worth paying for.

on: July 24, 2014, 04:49:21 AM

POS is going crazy! I am having a hard time getting yay!!! in pool mining right now. Glad we are back in business though!

on: July 19, 2014, 12:54:24 AM

Proof of stake stopped working about 5 hours ago. Judging by the pool size of Dwarfpool, I'm not surprised it forked. So why did PoS stop?

on: July 10, 2014, 12:53:22 PM

Quote from: kebabman on July 10, 2014, 04:05:29 AM But the PoS and PoW chains don't affect each other like that, a PoS block being found doesn't invalidate current PoW work, only a PoW block being found does that. You can see this by the fact that PoS and PoW have different block target times (20s Pos 120s Pow, PoW/PoS indepentant, see the OP), and if you check the block explorer you will see that they are not evenly spread out. I must be mining on the PoS chain then.... look at those block times. This is mining on Hash@me.

on: July 10, 2014, 03:19:06 AM

The only problem with a high vardiff is this, on average, there is a new block about every 20 seconds because of the proof of stake constantly taking the work. On most pools my whole miner screen only shows stratum detected new block and pre-submitted work about 25% of the time.

on: May 04, 2014, 12:38:23 AM

Quote from: cayars on May 04, 2014, 12:29:25 AM Quote from: bigjme on May 04, 2014, 12:24:58 AM That was put jn after the tutorial. What card is it for? 750ti you set the variable to 1 660 to 780 you set it to 0 Ccminer30 is compute 3.0 660 to 770 Ccminer35 is compute 3.5 780, 780ti, titan Ccminer50 is compute 3.5 750, 750Ti Somoone correct me if im wrong, its almost 2am so im talking off the top of my head Got that and it covers ccminer50.exe below: ccminer50.exe was compiled for Compute 3.5 with #define MAXWELL_OR_FERMI set to 1 in three .cu modules However what else is set differently to build ccminer30.exe and ccminer35.exe as they both have #define MAXWELL_OR_FERMI set to 0: ccminer35.exe was compiled for Compute 3.5 with #define MAXWELL_OR_FERMI set to 0 in three .cu modules ccminer30.exe was compiled for Compute 3.0 with #define MAXWELL_OR_FERMI set to 0 in three .cu modules That what I'm asking. In Visual Studio 2010 select ccminer in the left menu, press alt + f7, in the left column click Configuration Properties, Cuda C/C++, Device. In the right window under Code Generation it should list "compute_35,sm_35" by default. That value is for compute 3.5 and 5.0. If you click the drop down arrow on the right hand side of it, you can edit it. Change it to "compute_30,sm_30" to build under compute 3.0

on: May 04, 2014, 12:12:32 AM

Quote from: Chris84 on May 03, 2014, 11:06:25 PM Quote from: djm34 on May 03, 2014, 11:01:19 PM Quote from: cayars on May 03, 2014, 10:57:25 PM Quote from: JRyoku on May 03, 2014, 09:30:08 PM Compiled three versions for 3.0, 3.5, and 5.0 following the #define MAXWELL_OR_FERMI. Did I do this right? Works on my PC. https://mega.co.nz/#!adBy1YiY!bwix_AfHUKGPmLzm2BvxmX1zcMcRvUQq0SscyZhVMh0 edit: re-uploaded the zip, 5.0 was compiled before the stratum update. I just tried your compiled version and ran it against HVC with drastic drop off in hash rate. Went from 24MH to 16MH with 2 750tis. have the same problem (with my own compilation), it is due to the fact that gpu usage stays at 50%, you need to open 2 separate instances to run at full gpu usage. We did a little mistake with the Timing. Plz do the follow (if you compiled the code a your own): Code: open the file: "Heavy/heavy.cu" goto line 329: "MyStreamSynchronize(NULL, 0, thr_id);" Change it to: "MyStreamSynchronize(NULL, 1, thr_id);" This should help, we implemented a Counter, so I didn't tested this exact way. Next release will be fine Christian Made the code change, works correct on my 780. Here is the new zip. https://mega.co.nz/#!CV5nGLaZ!WXL66wxvN5ifnqn2wEh4fk-e5WoCB7cBqmmQpsRUIh8

on: May 03, 2014, 09:30:08 PM

Compiled three versions for 3.0, 3.5, and 5.0 following the #define MAXWELL_OR_FERMI. Did I do this right? Works on my PC. https://mega.co.nz/#!CV5nGLaZ!WXL66wxvN5ifnqn2wEh4fk-e5WoCB7cBqmmQpsRUIh8 edit: re-uploaded the zip, 5.0 was compiled before the stratum update.

on: May 03, 2014, 08:52:41 PM

Quote from: djm34 on May 03, 2014, 08:46:57 PM getting around 7600khash with the 750ti (original bios) for the 780ti, I have some strange issues, it uses only 50% GPU usage, I need to run 2 instance to get it to work at 93% so with two instances, I am getting around 28~29MHash/s on old mjollnir wallet... (didn't see any block yet though...) Just noticed I'm having the same issue on my 780, got up to 22.3MHash/s with 2 instances. Third block found so far while I was typing this. @zelante addnode=94.102.50.39

on: May 03, 2014, 08:36:29 PM

Got a block on the old chain with ccminer 0.8 compiled on windows mining with a gtx 780.

Pages: [1]