|
The web site has been updated. Most downloads moved to GitHub, so Google gets happy in their way finally. They flag my mining software as malware and ban the whole domain name with its subdomains. You can appeal, but they don't even read what you say.
UPD: I've got an email from Google. They have removed phoenixcoin.org from their list of malware sites.
|
|
|
|
It's very silent in here.
No one seems to care to donate anything. That's alright, I haven't put high expectations on it anyway. I have a few other unrelated projects in the works and they pay well, some even in advance. I may revisit this miner later and push it a bit further if I have some time to spare. I'm interested, but I think you'd better off trying with a thread on your own. Any chance you know the hashrate of a GTX 970 with your miner? I expect about the same performance improvement give or take a couple of percent. |
|
|
|
It's very silent in here.
No one seems to care to donate anything. That's alright, I haven't put high expectations on it anyway. I have a few other unrelated projects in the works and they pay well, some even in advance. I may revisit this miner later and push it a bit further if I have some time to spare. |
|
|
|
I'm optimising my server infrastructure, so all current and most historical wallet releases are on GitHub now. https://github.com/ghostlander/Orbitcoin/releasesAll wallet releases hosted by download.orbitcoin.org will be available until the next wallet release which is a work in progress. |
|
|
|
You're right, if I added "# define VLIW 1" into `neoscrypt.cl', just after :
/* NeoScrypt(128, 2, 1) with Salsa20/20 and ChaCha20/20
* Optimised for the AMD GCN, VLIW4 and VLIW5 architectures
* v7, 20-Feb-2016 */
#define VLIW 1
I got this error : [20:37:42] Probing for an alive pool
[20:37:43] The network difficulty has been set to 8307
[20:37:43] Stratum from pool 0 detected new block
[20:37:43] Error -11: Building Program (clBuildProgram)
[20:37:43] input.cl:100:26: warning: unknown OpenCL extension 'cl_amd_media_ops' - ignoring
input.cl:126:14: warning: implicit declaration of function 'amd_bitalign' is invalid in C99
unsupported call to function amd_bitalign in search
[20:37:43] Failed to init GPU thread 0, disabling device 0
[20:37:43] Restarting the GPU from the menu will not fix this.
[20:37:43] Try to restart the miner.
If I changed it on the same place to "#define OLD_VLIW 1", it's core dumped again : [20:40:07] Probing for an alive pool
[20:40:07] The network difficulty has been set to 8307
[20:40:07] Stratum from pool 0 detected new block
[20:40:07] Pool 0 is sending mismatched block contents to us (0 is not 1-1)./nsgminer.sh: line 24: 23981 Segmentation fault (core dumped) /usr/local/bin/nsgminer --neoscrypt -o stratum+tcp://....
Would be a problem with (enough of free) memory (HD7660D can allocate 256MB at maximum, if I'm not fallen), for example ? Yes, it doesn't seem to support bitalign. You can allocate more memory for your APU in the BIOS, 512Mb or 1Gb. It should work with -I 12 for 256Mb. |
|
|
|
cl_amd_media_ops is for bitalign/bytealign mostly which are not used in v6 directly. The compiler is supposed to take care of this, but it doesn't do well in the drivers newer than 14.7. It won't be an issue in the next release.
Hi ghostlander, thanks for amazing job! You're right, that isn't an issue in new 0.9.2 version anymore. And also, I removed "static" from `neoscrypt.cl' source file (this string is three times there), and now the error "OpenCL does not support the 'static' storage class specifier" is gone. Great! But with --neoscrypt option, nsgminer exits very quickly - sometimes it lists current config and then "Segmentation fault (core dumped)", sometimes it gets this fault immediately. Unfortunately there is no dump file (even if I added --verbose option) for further analysis. The same nsgminer, with option --scrypt, or without algo-option (it means sha256 algo) runs fine. Well, the hash-power is really ridiculous, but it's not just related to OSS drivers, it's also because I'm testing it on very weak IGP/APU (Radeon HD 7660D). If everything will be fine with --neoscrypt there, I'll try on more powerful/faster discrete AMD cards too... Finally, within compilation of nsgminer from git repo, I didn't add AMD APP SDK; I guess it doesn't make a sense with OSS radeon.ko driver ... or would be there some performance impact also in this "specific OSS case" ? Thanks for your help and your work on nsgminer again! HD7660D is a VLIW4 design which should be capable of some 60KH/s @ 800MHz. I'm almost sure the OSS driver doesn't expose any GPU specific data to an OpenCL compiler, so you have to set it up manually. Add "#define VLIW 1" somewhere in the kernel beginning. If there is no support for cl_amd_media_ops, change it to "#define OLD_VLIW 1" |
|
|
|
10MH/s is much better, but still not enough to compete with these ASICs. There may be even faster ASICs by the time Pascal comes into production.
The (28nm) R9 Nano is already 1/2 the speed of the announced unreleased ASIC if you messure hash/Watt. With a modded kernal you can reach 20MHASH per card. for $2000 you can buy many cards.. Pascal is rumoured to be 12 times faster, and will be released in 2016. (16nm) The announced asic is slow. It should be 2.3 GHASH / 700Watt. to beat the competition. I'm sure this ASIC is of a very inexpensive design and production. Something like 150nm and multiproject wafers. Indeed it's overpriced. Any subsequent designs should be much more impressive. |
|
|
|
iBeLink DM384M Dash MinerIf what they advertise is true, 384MH/s for 715W and $2098 in cash, say good-bye to X11 GPU mining. A reference R9 280X outputs 2MH/s for maybe 150W. If they produce enough of these ASICs for themselves, they can do a 51% attack on any X11 coin including Dash. The latest bins does 10MHASH on the reference 280x (nicehashminer) DM384M Dash Miner: 0,537 Mhash /Watt r9 280x: 0.066 Mhash /Watt (1/8 of the asic) (tahiti 2012) 750ti Maxwell: 0.075 Mhash /watt (1/7 of the asic) (maxwell 2014) r9 NANO 0,141 MHASH /watt (1/4 of the asic)(fury 2015) NVIDIA pascal(16nm) ... (1/2? of the asic, or perhaps the same speed.) (2016?) 10MH/s is much better, but still not enough to compete with these ASICs. There may be even faster ASICs by the time Pascal comes into production. |
|
|
|
iBeLink DM384M Dash MinerIf what they advertise is true, 384MH/s for 715W and $2098 in cash, say good-bye to X11 GPU mining. A reference R9 280X outputs 2MH/s for maybe 150W. If they produce enough of these ASICs for themselves, they can do a 51% attack on any X11 coin including Dash.
|
|
|
|
At this point, I would say a whole lot of nothing, since Myriad doesn't use X11. Myriad uses Qubit (Luffa, CubeHash, Shavite, SIMD, Echo) which is a subset of X11. Skein is also a part of X11. Myriad's Groestl is Groestl-512 + SHA-256 which is a bit different. The question if the ASIC manufacturer allows use of these 11 algos separately or chained differently. Even if this model doesn't, not a big deal to produce another one which does. Reference R9 280X offers 2MH/s. Not sure about power consumption, maybe 150W. What they offer 384MH/s for 715W blows GPUs away by a HUGE margin. |
|
|
|
Hey ghostlander, any idea's why FTC is so prone to orphans? It the only coin on my pool that makes more orphans then valid blocks. www.zpool.ca/site/block?id=308Maybe you're low on connections? If you add a few permanent ones to other big pools, it should help. I've tried that already. Tried having 64 connections and still no improvements. What version do you use? 0.9.3.0 Could you try v0.8.7? sure, I'll give it a try... 0.8.7.2? Yes, this one. Older version is working much better. Thanks. Do you have an idea why that would be? www.zpool.ca/site/block?id=308These branches were done by different developers mostly. Something got lost in translation apparently. |
|
|
|
Up to 100% holy cow, where that came from? Have you found the way to tap into black matter?  No, worked around bad drivers  |
|
|
|
I don't say this often, but Ghostlander - really well done on the improvements to FastKDF and everything it calls. I know I gave the idea for the aligned copies/XORs, but your implementation is quite nice. I do wish you would use loops with #pragma unroll just a little more often, but your code is decently readable regardless. Extremely well done implementation on that. In fact, I wouldn't be surprised if, comparing only FastKDF, your implementation surpasses my own.
However, I must say, you still haven't optimized quite an important bit here... the main loop.
FastKDF was a major bottleneck in v6, so I had to fix it first. Catalysts above 14.7 lost ability to align reads and writes properly on their own, so bitalign was the way to go. I know there are other places which need optimisations. That's for the next release. Thanks for all your work Ghost, but just a heads up R9 Nano gets hardware errors with same settings from 0.9.0. BIG jumps on my other GPUs.
I wish I had a Nano or Fury for testing. I have added their ID as well as the Carrizo ID (the last AMD APU) to the kernel. Hope they work well with the default GCN settings. The ISA code looks good at least. Pull it from my GitHub and let me know. nice work @Ghostlander
thanks
does this miner work solo ??
Of course it does. That's how I use it most of the time. |
|
|
|
Hey ghostlander, any idea's why FTC is so prone to orphans? It the only coin on my pool that makes more orphans then valid blocks. www.zpool.ca/site/block?id=308Maybe you're low on connections? If you add a few permanent ones to other big pools, it should help. I've tried that already. Tried having 64 connections and still no improvements. What version do you use? 0.9.3.0 Could you try v0.8.7? sure, I'll give it a try... 0.8.7.2? Yes, this one. |
|
|
|
Is there any exchanges where Halcyon can be traded right now? Also if not has anyone looked into getting it listed onto an exchange?
Well, it's listed for voting at Cryptopia and getting some votes daily. However it seems to be a slow process. |
|
|
|
I have released NSGminer v0.9.2 with performance improvements up to 100%.Thanks for your support.
|
|
|
|
Hey ghostlander, any idea's why FTC is so prone to orphans? It the only coin on my pool that makes more orphans then valid blocks. www.zpool.ca/site/block?id=308Maybe you're low on connections? If you add a few permanent ones to other big pools, it should help. I've tried that already. Tried having 64 connections and still no improvements. What version do you use? 0.9.3.0 Could you try v0.8.7? |
|
|
|
|
Show Posts
