Can you use all of the same commands as cgminer?
Yup. It's based on cgminer with minimal changes to support Yacoin. |
|
|
|
Thank you for the update.
Sorry about nagging, but I am still interested in a Ybcoin version of the Yacminer.
Would a small YAC donation and promise of 5% of all mined Ybcoins spark your interest?
Tried and failed at updating the source myself, yes, that is how dumb I am.
Fine, I might make one since there's popular demand. Easy enough to change 4 lines... |
|
|
|
|
New version is up. -yac2 fixes a problem which has annoyed me greatly. I noticed that the miner always starts experiencing lots of network failures when mining on a pool for a while. I investigated the issue and I think the cause is that the miner does not close long polling connections. -yac2 fixes that by telling the cURL library to limit the number of long polling connections. It's not a perfect fix because the miner is still keeping more than one connection open but at least it shouldn't stall anymore.
|
|
|
|
Hey mikaelh, are you looking into the ways around keeping GPU's usable after the Aug N++? Or is that something hanzac might be doing? Or neither?  Well, let's re-iterate this once more. GPU mining is not going to magically stop at N = 8192. My miner should survive it just fine. I'm not going to benchmark it because people always keep finding new settings after N changes. Some people will use a higher lookup gap and others will find ways to use lower values. I might come up with some new tricks but at the moment I'm pretty happy how the code scales with the lookup gap. My apologies, I thought I understood the way it works but obviously not. I thought that the RAM on the GPU was the limitation and this couldn't be overcome. I'm not sure I understand the lookup gap / TC correlation and the use of GPU RAM vs system RAM. It's pretty hard to discuss the details of lookup gap without explaining the entire scrypt algorithm first. I did write a bit about lookup gap on the other forum: http://yacointalk.com/index.php/topic,350.msg1511.html#msg1511The miner allocates the scratchpad from GPU memory. You may need enough system RAM to support that, but that's a driver issue. |
|
|
|
Hm, how does that work? GPUs are around the 100Kh/s zone at current N for YaCoin, how will they get to 1Mh/s at the highest N?
N = 32 is the smallest N for Yacoin, not the highest. N = 32 corresponds to Nfactor = 4. |
|
|
|
orders of magnitude
I don't think there's any GPU able to get two orders of magnitude more hashes than a desktop CPU. My 6850 barely reaches one order of magnitude above my i5 2500k with the latest optimized kernel. Well, it depends on the value of N. If you set N to 32, my latest kernel will do over 1 million hashes per second quite easily. That's what's happening at the Ybcoin camp. They launched with N = 32 a few days ago and their network hashrate seems to have reached 87 Mhash/s already. Most of the coins are probably going into the pockets of a few GPU miners. |
|
|
|
Hey mikaelh, are you looking into the ways around keeping GPU's usable after the Aug N++? Or is that something hanzac might be doing? Or neither? Well, let's re-iterate this once more. GPU mining is not going to magically stop at N = 8192. My miner should survive it just fine. I'm not going to benchmark it because people always keep finding new settings after N changes. Some people will use a higher lookup gap and others will find ways to use lower values. I might come up with some new tricks but at the moment I'm pretty happy how the code scales with the lookup gap. |
|
|
|
Links for x86 and x64 versions from mega are the same?
Oops, fixed. Thanks for pointing it out! |
|
|
|
I have no interest in Ybcoin since it's simply a clone of Yacoin for the Chinese market. Looks like the only thing one would have to change is the calculation of the Nfactor. No doubt someone has already figured that out and is happily mining at 10 Mh/s. Someone else can release a miner for Ybcoin if they want. |
|
|
|
Can anyone provide a list of peers that accept inbound connections?
Here's a list of peers I grabbed from my yacoind: 37.59.119.242
199.204.38.210
184.175.53.111
88.198.92.150
109.80.94.251
198.199.80.210
106.187.96.135
50.56.186.88
54.244.109.130
140.112.183.10
95.138.185.176
72.46.155.34
95.90.147.164
174.56.58.238
110.211.43.56
95.178.181.163 I've also been having a number of issues with pools, so I'm solo-mining at the moment. Let's hope feeleep gets stratum working. |
|
|
|
Guys, I set up experimental stratum support on http://yac.coinmine.pl on port 9088, however when I tried to setup yacminer it cannot connect. I suppose it doesn't support stratum in this version but I may be wrong. It would be beneficial if someone who has enough programming skills could check the source code of yacminer and say if stratum should work or not... Anyway you are invited to test stratum if you can feeleep Your stratum pool is rejecting shares. yacminer version 3.2.1 - Started: [2013-07-01 15:48:41]
--------------------------------------------------------------------------------
(5s):111.3K (avg):114.6Kh/s | A:0 R:8 HW:0 U:0.0/m WU:84.5/m
ST: 2 SS: 0 NB: 8 LW: 134 GF: 0 RF: 0
Connected to yac.coinmine.pl diff 31 with stratum as user mikaelh.x
Block: 5cc54263730eb5fe... Diff:52.5K Started: [15:52:43] Best share: 338
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: | 114.9K/116.3Kh/s | A:0 R:8 HW:0 U:0.00/m I:17
--------------------------------------------------------------------------------
rypt' is n
[2013-07-01 15:51:36] Network diff set to 52.5K
[2013-07-01 15:51:36] Stratum from pool 0 detected new block
[2013-07-01 15:51:40] Rejected a4a838e1 Diff 286/31 GPU 0 (global name 'ltc_sc
rypt' is n
[2013-07-01 15:51:46] Rejected f04a3094 Diff 111/31 GPU 0 (global name 'ltc_sc
rypt' is n
[2013-07-01 15:51:51] Network diff set to 52.5K
[2013-07-01 15:51:51] Stratum from pool 0 detected new block
[2013-07-01 15:52:41] Rejected 93af4b8a Diff 63/31 GPU 0 (global name 'ltc_scr
ypt' is n
[2013-07-01 15:52:43] Network diff set to 52.5K
[2013-07-01 15:52:43] Stratum from pool 0 detected new block This is my own version compiled from hanzac's source with a few fixes. Nothing that should affect stratum support though. EDIT: Same thing with hanzac's original version. Pool is rejecting all shares with the same message. |
|
|
|
This version is my attempt to optimize the Keccak code as much as possible. 128-bit vector operations are used where possible. Unfortunately the core operations of Keccak are still 64-bit because Keccak is annoying. Speedup is pretty minor. My 7790 goes from 108 khash/s to 112 khash/s. This version doesn't use the vstore* functions and should work with very old compilers (not tested though). scrypt-chacha-v7.clhttps://mega.co.nz/#!RldG2YpD!DVbjR1A8tAFBPDBHTz7_WVN0S6o3hRQwWjOFrEBD0RU |
|
|
|
C:\DOCUME~1\GHO~1.TH~\LOCALS~1\Temp\OCL34E.tmp.cl(135): error: bad argument
type to opencl vload/vstore: expected pointer to scalar with
addrSpace global/local/private/constant(vloa [2013-06-26 09:42:44] Failed to init GPU thread 0, disabling device 0
[2013-06-26 09:42:44] Restarting the GPU from the menu will not fix this.
[2013-06-26 09:42:44] Try restarting cgminer. What's your driver version? I think your OpenCL compiler may be too old. It's also possible to get rid of vstore but I'm not sure how that would affect performance. That's HD4870 on Windows XP, so the drivers and APP SDK are pretty old. This OpenCL 1.0 HW delivers ~100MH/s SHA-256 at 800MHz engine and maybe 120W power consumption. Not worth mining anymore unless you have free electricity. I think it can be used very well for scrypt-jane mining as it offers over 100GB/s of memory bandwidth. Here's a quick version that doesn't use vstore. Only recommended for people who cannot compile v6. scrypt-chacha-v6-no-vstorehttps://mega.co.nz/#!p9l20QLa!YbT2A0i0WqJS1moB6hGGaU4vRgJ7nChIKgs-2o1jB8k |
|
|
|
7790 users! Please post here new N=10 settings. I try many setups, always hw error. MY N9 settings:hashing avg.: 126.3kh/s Parameters: --device 0 --scrypt --worksize 256 --lookup-gap 2 -I 11 --thread-concurrency 8192 -o adress -u name -p pass My current settings for a 7790 are: --scrypt -w 128 --lookup-gap 2 -I 17 --thread-concurrency 12000 This produces about 109 kH/s after the latest N change. |
|
|
|
C:\DOCUME~1\GHO~1.TH~\LOCALS~1\Temp\OCL34E.tmp.cl(135): error: bad argument
type to opencl vload/vstore: expected pointer to scalar with
addrSpace global/local/private/constant(vloa [2013-06-26 09:42:44] Failed to init GPU thread 0, disabling device 0
[2013-06-26 09:42:44] Restarting the GPU from the menu will not fix this.
[2013-06-26 09:42:44] Try restarting cgminer. What's your driver version? I think your OpenCL compiler may be too old. It's also possible to get rid of vstore but I'm not sure how that would affect performance. |
|
|
|
Trying it now...seems like yac either killed my card or my win 7 install got borked with your v5 kernel somehow (?) I can't mine other coins either, getting tons of hw atm.  (this is when trying to mine ltc) You will probably need to restart that computer. |
|
|
|
|
Yeah, it's probably a good idea to hold off mining for a while. Difficulty should actually adjust faster that way. There's a bug in v5 causing the HW errors. I'll release a new kernel soon.
|
|
|
|
|
Show Posts
