running 16 hours so far without any issues.
rx480 1106/1750 ~ 3 Mh/s
rx470 1095/1650 ~ 2.6Mh/s
rx580 1300/1000 ~ 3.5 Mh/s
Funny thing is when i overclock hashrate would decrease, ie rx480@1280/1900 would run 2.6 Mh/s, rx580@1380/2000 ~ 3.1 Mh/s. So i let it run on default clock, in auto DPM state. Not so easy to OC under linux.
Just got this error reported by miner over and over, and mining stopped: [2018-03-15 11:01:20] Pool xzc.f2pool.com failed to parse server rpc: {"id":1,"result":[[["mining.set_difficulty","deadbeefcafebabe21b9070000000000"],["mining.notify","deadbeefcafebabe21b9070000000000"]],"00007ce5",4],"error":null} restarted miner, seems OK again.... Thank you very much for posting this. This problem appears to be caused by invalid data being received by the miner from the pool connection and not being processed correctly (this was most likely due to a network error of some sort). In this case, the miner should treat this as a network error, causing it to close the connection to the pool and attempt to reconnect. However, after examining the code, there is a bug that prevents the miner from properly clearing it's receiving network buffer in this case. This bug causes the miner to repeatedly see the invalid data in every future reconnect attempt. I will have a fix for this bug out as soon as I can. I advise anyone using version 0.2.0.0 or earlier to monitor their rigs closely in case of this error occurring. If your pool supports alert/monitoring emails, please use them.Network errors like this are usually not common, but can occur more frequently on unstable/unreliable network connections. Edit: New version with potential fix posted. |
|
|
|
Tested on Linux today (fresh install).
- RX 580: 3.2 MH/s
- RX 470: 2.5 MH/s
I am sure I could do better but I have no experience with overclocking under Linux. My rigs are Win 10, so eagerly awaiting the Windows version.
The miner worked without flaws, but I did not test for extended periods of time.
Thanks for posting your results. It's nice to have some confirmation that the kernels scale well on RX 470 GPUs. The GPU kernels should scale relatively linearly with the number of CU and core clock speed. They should not be affected very much by memory speed. Sounds like great news for ADM owners.
I have question about rx580. Is there any performance difference between 4Gb and 8Gb versions or hashrate is the same for both?
The hash rates should be the same for both. The GPU kernels do not use very much memory, and they only use it for intermediate state, so memory capacity and clock should have little impact. I will try with 4 or 5 rx580 this week. I will let you know.
Thanks for your job
Thanks principino! It will be nice to have some feedback on how the miner runs with more than a couple GPUs at a time. I look forward to your results! Tested on Linux today (fresh install).
- RX 580: 3.2 MH/s
- RX 470: 2.5 MH/s
I am sure I could do better but I have no experience with overclocking under Linux. My rigs are Win 10, so eagerly awaiting the Windows version.
The miner worked without flaws, but I did not test for extended periods of time.
Out of interest, what are these cards achieving with SGminer? I haven't tried myself, I'm usually quite reluctant to experiment with my AMD rigs are they are my very stable cash cows mining ETH... around 0.5 mhs
The 0.5Mh/s number is about what I remember getting on sgminer the last time I ran it. I think with some tuning you can get to around 1.5 Mh/s on a Vega 64. As for switching over your stable rigs to this miner, please keep in mind that this is still a beta release. I do not promise that it will be stable on all hardware. I've done my best to test it for stability on the hardware I have and so far I have not received any reports of instability, but I've only received feedback from a handful of people. I would suggest slowly switching your rigs over one at a time, making sure that they are stable along the way. I don't want to ruin anybody's profits because of potential bugs in the miner. Also remember to check your GPU temperatures as the miner does not check them, and will continue mining even if they exceed safe limits. |
|
|
|
I didn't even know that setting existed. Setting changed, fire away  . |
|
|
|
Is there restrictions to mining cards per rig? I thought I heard it is for 1 or max 2 gpu's?
And one more vote for windows miner.
The code is written to support up to 16 GPUs, though I don't think most motherboards/BIOS's/operating systems can handle that many. I have only tested it with up to 2 GPUs. If anyone is having issues running with more GPUs, I'd like to hear about it. If there are bugs in the miner preventing running with more GPUs I'd love to squash them. I'm working on a windows version, but it will probably be a week or two before I have something to release. |
|
|
|
Reading through this thread for the first time, I only saw your announcement on the ZCoin subreddit earlier. A polite request though, with all due respect please stop the bs hints about ripping your kernels, I haven't even downloaded your miner, even less so tried to dump your kernels. I was just as surprised as you were about the weird coincidence that two very similar AMD lyra2z-related announcements were made within a friggin' day after months of silence. Furthermore, I don't know when you published on github, but otherwise all your announcements that I've seen were written after(!) my post here. It's a bit of a stretch that I somehow would have found your miner before your first announcement, ripped the kernels, massaged them into a Windows sgminer and made a wild announcement myself, like you wouldn't be able to release the same packaging yourself at some point  . As stated, my implementation was written bottom up in pure GCN ASM (well, not the Blake part) and has been running on Windows rigs for a number of months. No ROCm dependencies. We probably made the same analysis, that lyra2z was very far from well understood and a very good fit for what an AMD GCN CU can do with DPP ops. Your miner def has had me become less interested in releasing it public though, I'd rather keep the extra ~15% edge I seem to have for now. Cheers, K Hey kerney, thanks for clearing the air on this. I admittedly over-reacted a bit by insinuating that you may have taken the kernels from my miner. Right after my initial release on github I had ask a couple people if they could test it out, before my reddit announcement. One of them directly told me that he was trying to reverse engineer the kernels. When I saw that your post went up half a day after this interaction, I jumped to conclusions. My apologies. Also kudos to you for writing a lyra2 implementation entirely in assembly. I know how much of a pain it was for me to do it in opencl c with inline assembly, so I imagine it was doubly so doing it entirely in assembly. I don't understand why this release discouraged you from releasing your own miner. Wouldn't releasing a miner with a dev fee would be more profitable than having a 15% advantage just on your own rigs? In either case, I think the community would appreciate and benefit from having two competing AMD miners for lyra2z, and I personally welcome the competition. |
|
|
|
Impressive! 70Mh/s on Lyra2Rev2 would beat out mkxminer... I've gotten it up to 67 on a V64 with high overclock, but 70 @ stock settings? Niceee.
As mentioned above, 3% is quite reasonable. People will pay for good miners, especially new ones where there is no real competition.
As for ripping kernels... don't know much about that, although I do recall Claymore calling out Phoenix's ETH kernels fairly recently. I think you're focused on the right thing, as far as developing goes. There is/will be (at least from my perspective) high demand for more algo flexibility on the AMD side. And the gpus are quite capable if you can fine-tune your kernels to exploit the hardware, particularly the Vegas.
I've got a fair amount of AMD cards, not sure what your hardware constraints are, and am I'm happy to test/run anything you throw my way. Got RX 480s, RX 580s, Vega 56s, Vega 64s, and Vega FEs.
Thanks, I actually started working on lyra2rev2 first, but then quickly realized that lyra2z had much more low hanging fruit for performance improvements. Here is my reasoning for the 3% fee. While it is higher than the more common ~2% range for competitive miners, this miner is (to my knowledge) one of the most profitable for AMD hardware currently available. If you look at whattomine's XZC estimates for revenue based on the hash rates posted in the description, at the time of this post it estimates: RX 580 - $2.14/day RX Vega 64 - $4.37/day These are significantly more profitable than the most profitable coin currently on their front page (currently XMR, with Vega 64 bringing in ~$2.90/day). And again, the hash rates I've posted are from stock GPUs with no tuning. Others have reported their rates are higher. If and when this miner becomes less relatively profitable, either due to competing miners or difficulty increase, I will lower the fee to stay competitive. I'm not trying to price gouge here. On the other hand I wouldn't mind getting some return on the several hundred hours of work I've put into this miner. Edit: I forgot to mention, the miner code is structured to support different fee per algo. For lyra2rev2 I would go around 2% since I don't believe it would be profitable enough to command the higher fee. If I can't get it to go significantly faster than a 1080ti, I don't think that justifies much over a 2% fee. I very much agree with you regarding AMD gpus just not having good software available, and especially for Vega. Vega has some nice ISA improvements that can yield pretty noticeable perf improvements. Many of these ISA improvements are not currently supported by OpenCL toolchains, so some hand tuning is required to use them. For the algos I've looked at so far I can usually get a Vega 64 to perform similarly to, or better than a 1080ti. Last, but not least, the GPUs you listed are almost exactly all the GPUs the miner currently supports  What OS are you currently running your GPUs under? If any are under linux, I would be very curious to see how the miner runs with them. Especially the RX 480 and Vega 56 gpus, as I don't currently have access to any of those. |
|
|
|
|
New version released! Now with support for amdgpu-pro Linux drivers.
I've only been able to do minimal testing of the amdgpu-pro support, so some testers here would be much appreciated.
Also if you have successfully tested out the release, please post your results!
I have limited hardware available for testing and am very curious to see what hash rates people get with different setups.
|
|
|
|
Turns out converting my kernels from ROCm to amdgpu-pro/windows is a lot simpler than I expected.
Unfortunately, I first need to waste some time hardening them so we don't have another "coincidental" announcement.
I should have a new version that supports amdgpu-pro drivers on linux in a day or two. This should make the miner compatible with the typical linux rigs running RX 580s/570s, such as HiveOS and the like. Windows will take a week or two longer, since I don't even have a windows environment to build/test in right now.
Nice! yeah I'll definitely be waiting for windows as well, since the undervolting/overclocking with Vegas is much easier in windows. Windows 10 is free, and you can do pretty much everything without activating it... not sure what's holding you back but definitely looking forward to this version! Edit: Also, that's very interesting/coincidental about the other thread for sure... If true, I'd definitely use yours... and that would make his whole rant quite hypocritical. If it is yours, sweet! That means the numbers for this miner are great  but that would also mean your devfee is quite high  Hopefully, if it really is as simple as dropping your kernel into something like SGMiner, we won't have to wait too long for a windows version. Very excited about this, been in XZC for a while but never had a good reason to mine it. Yeah, tuning support for Vega on linux is not great. I believe in kernel 4.17 they will add support for wattman like profiles for overclocking/tuning, but that's a ways out. I've mostly been running my cards stock, but I also use them mostly for development/testing. Regarding the other thread, thanks for seeing my side. Obviously I can't say for sure if it was coincidence or malice, but I guess we'll have to wait and see if he releases anything. Or even posts again for that matter. The perf on the current release is already pretty good. I think people might be getting the wrong impression by the modest hardware settings I used for the hash rates I posted. I'll see if I can get some numbers from my Vega 64 LC at max powerstate. I'm sure they'll be impressive and totally useless since that thing burns stupid amounts of power at full throttle. As for the dev fee, I'm not planning on having a egregiously high dev fee. I'm currently thinking 3% for the next release. Even the current relatively high fee in the miner is nowhere near the 25% that guy was talking about. Unlike what he was saying, I don't need to make quick cash on this algo before XZC switches over to MTP. I've done work on other algos like lyra2rev2, nist5, skunk, neoscrypt and some others. I chose to release lyra2z first since my implementation of it has the best perf improvement out of the algos I've worked on (also some like skunk and nist5 are basically dead for GPU mining now, and Claymore beat me to the punch for neoscrypt ). The next algo I plan to support is lyra2rev2 which should be able to get around ~70Mh/s on a modestly clocked Vega 64. But first I need to get that windows build out About the kernels, they are not drop in compatible with sgminer. Some reverse engineering work and modifications would have to be done. Before the alpha release, I thought I was being paranoid thinking that someone would go through the effort required to rip them, so I did not spend effort trying to make them hard to rip. I also think it's a bit of a waste having to spend the time/effort and adding useless junk to the kernels just so they are harder to steal. Oh well, the next release will have kernels that will have better performance and be much more difficult to rip. |
|
|
|
|
Turns out converting my kernels from ROCm to amdgpu-pro/windows is a lot simpler than I expected.
Unfortunately, I first need to waste some time hardening them so we don't have another "coincidental" announcement.
I should have a new version that supports amdgpu-pro drivers on linux in a day or two. This should make the miner compatible with the typical linux rigs running RX 580s/570s, such as HiveOS and the like. Windows will take a week or two longer, since I don't even have a windows environment to build/test in right now.
|
|
|
|
Definitely interested, but worried about the PCIE Gen 3 requirement. My larger rigs definitely require Gen 2 settings in the bios due to the number of cards, so don't know how feasible it will be to run this miner except on a couple one or two card computers.
Btw todxx, have you checked out the other thread on potential release of Vega XZC miner? Guy seemed like he was doing it in GCN ASM instead of OpenCL or ROCm... maybe you could pick something up from that thread to optimize your miner/make it compatible with Windows. Assuming he wasn't bs'ing, but the numbers he was throwing around were phenomenal.
Yeah, ROCm is a bit of a double edged sword right now. Their toolchain is good, but their run-time has some overbearing requirements that other drivers don't. I can see how they ended up there as ROCm was initially targeted for data-center cards, but now that they are starting to use it as the default driver for desktop cards, it's causing some headaches. Regarding the other thread, I don't know what to tell you man. I'm pretty sure you could get pretty close to those numbers with my miner if you properly tuned/OC'd your GPUs. The numbers I posted are for bone-stock GPUs (stock bios, voltages, clocks, etc). The only thing I did was set a fixed power-state so I can get reliable performance measurements. Given all of this, and the fact that he posted his rant about half a day after I released my alpha release on github makes me feel like it's someone who just ripped my kernels and ran them on some very OC'd cards. I even have an idea of who it might have been, as I had asked this person if he could test out my miner right after posting the release. Maybe I'm just being paranoid. But I can't get over the fact that I've been working on this for 4+ months, and the day I post a release, coincidentally someone else figured out how to do the exact same thing later that day. I guess we'll find out if his kernels are the same if he ever releases anything. Ugh, sorry for the rant. Since the request for supporting windows/amdgpu-pro drivers is the most common feedback I get, I will focus on figuring this out. |
|
|
|
What speeds were indicated before? It's the first time I have seen this miner and it is damn quick, best think since sliced bread. Well done dev and alpha release is very stable for me. I'm actually getting better results than indicated here.
Thanks Arctic! I'm glad it's working well for you. I have done my best to test this release on my hardware for stability and have run it for several hundred hours on my rigs. But I can't really call it more than an alpha release until I get some feedback on how it runs on other hardware. I've already had a couple reports of it not being able to find/load GPUs on certain hardware, so hopefully I can get to the bottom of those problems soon and get a new release out. |
|
|
|
|
To answer this upfront since it's been asked a few times:
There is no windows version available.
|
|
|
|
tdxminer has become teamredminerPlease see the teamredminer thread for newer releases. tdxminer v0.2.2.2 Beta ReleaseThis is an optimized miner for AMD GPUs running on the Linux. This is a BETA release and may be unstable on some hardware. Algorithms: lyra2z GPUs Supported: - RX 580/570/480/470 with amdgpu-pro or ROCm 1.8 drivers
- RX Vega 64/56, Vega FE with ROCm 1.8 driver
Download available here: https://github.com/todxx/tdxminer/releases/download/v0.2.2.2/tdxminer-v0.2.2.2.tgzBrief readme available here: https://github.com/todxx/tdxminerNOTE: This miner does NOT monitor GPU temperatures. It is up to the user to ensure that GPU(s) are functioning within safe power and temperature limits. Software Requirements: - Linux (preferably Ubuntu 16.04 as that is supported by ROCm and amdgpu-pro)
- Supported GPU driver (see GPUs Supported above)
- libjansson4
This miner includes a 3% dev fee. Rough lyra2z user hash rates on stock GPUs: | GPU | SCLK (MHz) | MCLK (MHz) | Hash Rate (Mh/s) | | RX 580 | 1167 | 2000 | 3.27 | | RX Vega 64 | 1401 | 945 | 6.66 | | RX Vega 64 LC | 1408 | 945 | 7.07 |
If you are considering installing ROCm, please check that it supports your hardware first. Note that ROCm versions prior to 1.8 do not support typical riser setups. For reporting bugs and/or for features requests please open an issue in the github issue tracker, or make a post here and I'll do my best to respond. Any feedback would be appreciated. ------------------------------------ Changes in v0.2.2.2 - Changed output to be line buffered for easier use with piping. - Fixed month off-by-one bug in printing the date. - Fixed hang that could occur when pool connection is lost. Changes in v0.2.2.1 - Added better/faster handling of non-responding pool connections. - More network bug fixes. Changes in v0.2.2.0 - More network bug fixes for pool connection. Changes in v0.2.1.1 - Fixed bug with handling network errors in dev pool connection. Changes in v0.2.1.0 - Fixed bug with handling network errors in pool connection. Changes in v0.2.0.0 - Improved lyra2z performance - Support for Ellesmere GPUs under amdgpu-pro drivers - Dev fee set to 3%
|
|
|
|
I was really hoping to get at least a beta build ready before setting this forum loose on it. Also to get some feedback about any bugs, like the one you mention. The github repo has an issue tracker that would be a great place to report problems like not finding devices. Any feedback would be appreciated. Edit: Now that I look at it, I find it strange that this was posted here half a day after I posted my alpha release. That's a hell of a coincidence. Just a coincidence)) To make a topic - better choice, i think. You can get more feedback. Yep, definitely a coincidence. I'll make sure future releases are less coincidence prone. And yes, a topic is what I should have said. I'm new to posting here, as I'm sure you guys have noticed Edit: topic is here: https://bitcointalk.org/index.php?topic=3299496.0 |
|
|
|
I was really hoping to get at least a beta build ready before setting this forum loose on it. Also to get some feedback about any bugs, like the one you mention. The github repo has an issue tracker that would be a great place to report problems like not finding devices. Any feedback would be appreciated. Edit: Now that I look at it, I find it strange that this was posted here half a day after I posted my alpha release. That's a hell of a coincidence. Lol! This is like Bitmain rushing their Cryptonight ASIC to the market after Baikal announced theirs (or was it other way around). Edit: Hey can you start your own thread for feedback? Would love to test it. Looks like the cat's out of the bag, so I guess I should. I'll try to get a post up tonight. I'm trying to get my taxes done right now  . Until then, you can find it at the link that was posted. Feel free to post issues in the github repo for bugs, requests, etc. |
|
|
|
I was really hoping to get at least a beta build ready before setting this forum loose on it. Also to get some feedback about any bugs, like the one you mention. The github repo has an issue tracker that would be a great place to report problems like not finding devices. Any feedback would be appreciated. Edit: Now that I look at it, I find it strange that this was posted here half a day after I posted my alpha release. That's a hell of a coincidence. |
|
|
|
|
Show Posts
