great almost 6mhs on rx 580 and 12 on vega 64
How do yue get that speed??
I have only 4.9 Mh on sapphire 580 nitro with patched timings CC 1250 MC 2070, so what i do wrong ?
What timings are you using?
Topic: [ANN] TeamRedMiner - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2 - page 38. (Read 85791 times)
October 02, 2018, 07:43:15 PM
How do yue get that speed??
I have only 4.9 Mh on sapphire 580 nitro with patched timings CC 1250 MC 2070, so what i do wrong ?
What timings are you using?
October 02, 2018, 07:17:55 PM
great almost 6mhs on rx 580 and 12 on vega 64
How do yue get that speed??
I have only 4.9 Mh on sapphire 580 nitro with patched timings CC 1250 MC 2070, so what i do wrong ?
October 02, 2018, 07:01:20 PM
great almost 6mhs on rx 580 and 12 on vega 64
How do you get that speed??
October 02, 2018, 04:06:26 PM
@hizzy2023
Basically, this is tdxminer, but it has been renamed and we're now two devs working on it. There is no change in performance nor dev fee for lyra2z. There are a few outlier bugs fixed though, so it's never a bad idea to upgrade. It is 100% command line compatible with tdxminer, so it should be a 1 min thing for you
.
Basically, this is tdxminer, but it has been renamed and we're now two devs working on it. There is no change in performance nor dev fee for lyra2z. There are a few outlier bugs fixed though, so it's never a bad idea to upgrade. It is 100% command line compatible with tdxminer, so it should be a 1 min thing for you
.Thanks for clarification. I would like to upgrade but i am noob on linux. Can you write me few steps how can i do it so fast?
October 02, 2018, 02:27:41 PM
that's it.. having HBCC enabled will give gfx901, while having HBCC disabled will give you gfx900.
with HBCC disabled, it runs.
would love a version with HBCC enabled.
with HBCC disabled, it runs.
would love a version with HBCC enabled.
Yep, we're working on the next release, addressing the quirks found so far, this being one of them. Should be out within a week, probably before that.
October 02, 2018, 02:25:47 PM
great almost 6mhs on rx 580 and 12 on vega 64
October 01, 2018, 11:41:22 PM
that's it.. having HBCC enabled will give gfx901, while having HBCC disabled will give you gfx900.
with HBCC disabled, it runs.
would love a version with HBCC enabled.
with HBCC disabled, it runs.
would love a version with HBCC enabled.
Yep, we're working on the next release, addressing the quirks found so far, this being one of them. Should be out within a week, probably before that.
October 01, 2018, 11:01:32 PM
@alucard20724
Don't think we've tested on that driver version. Can you run "clinfo" from a command prompt, it will dump all opencl platforms and devices on your box. Then, scroll up and locate the section for a Vega 56 that looks like this (might be one at the very bottom of the output):
Before asking you to dump the whole thing here, can you tell me if you see the string "gfx900" or something else for the name?
Don't think we've tested on that driver version. Can you run "clinfo" from a command prompt, it will dump all opencl platforms and devices on your box. Then, scroll up and locate the section for a Vega 56 that looks like this (might be one at the very bottom of the output):
Quote
Platform ID: 00007FF8044C4AB0
Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2527.10 (PAL,HSAIL)
Profile: FULL_PROFILE
Version: OpenCL 2.0 AMD-APP (2527.10)
Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2527.10 (PAL,HSAIL)
Profile: FULL_PROFILE
Version: OpenCL 2.0 AMD-APP (2527.10)
Before asking you to dump the whole thing here, can you tell me if you see the string "gfx900" or something else for the name?
I normally have gfx901, not a gfx900. I've had that same issue before. I normally rename the gfx900.bin to gfx901.bin in the miners that require a .bin file
just verified clinfo, it's "gfx901"
oh.. and how about api support?
We will address the gfx901 issue in the next release, but for the time being you can try disabling HBCC on the cards while mining.
Adding API support is on our todo list, but we don't have an estimate on when we'll get it released yet.
that's it.. having HBCC enabled will give gfx901, while having HBCC disabled will give you gfx900.
with HBCC disabled, it runs.
would love a version with HBCC enabled.
October 01, 2018, 06:45:34 PM
@hizzy2023
Basically, this is tdxminer, but it has been renamed and we're now two devs working on it. There is no change in performance nor dev fee for lyra2z. There are a few outlier bugs fixed though, so it's never a bad idea to upgrade. It is 100% command line compatible with tdxminer, so it should be a 1 min thing for you.
Basically, this is tdxminer, but it has been renamed and we're now two devs working on it. There is no change in performance nor dev fee for lyra2z. There are a few outlier bugs fixed though, so it's never a bad idea to upgrade. It is 100% command line compatible with tdxminer, so it should be a 1 min thing for you
. October 01, 2018, 05:57:03 PM
I am using tdxx miner with RX 580 - 8gb cards and getting from 3.25 to 3.45Mhz on lyra2z. It works like clock on 1250 core and 1400 memory. Should i upgrade to this miner instead? Will performance be better or lower power draw? Thanks. I am using Linux version. Also is it different dev fee from tdx miner and how much is it?
October 01, 2018, 04:46:10 PM
@alucard20724
Don't think we've tested on that driver version. Can you run "clinfo" from a command prompt, it will dump all opencl platforms and devices on your box. Then, scroll up and locate the section for a Vega 56 that looks like this (might be one at the very bottom of the output):
Before asking you to dump the whole thing here, can you tell me if you see the string "gfx900" or something else for the name?
Don't think we've tested on that driver version. Can you run "clinfo" from a command prompt, it will dump all opencl platforms and devices on your box. Then, scroll up and locate the section for a Vega 56 that looks like this (might be one at the very bottom of the output):
Quote
Platform ID: 00007FF8044C4AB0
Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2527.10 (PAL,HSAIL)
Profile: FULL_PROFILE
Version: OpenCL 2.0 AMD-APP (2527.10)
Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2527.10 (PAL,HSAIL)
Profile: FULL_PROFILE
Version: OpenCL 2.0 AMD-APP (2527.10)
Before asking you to dump the whole thing here, can you tell me if you see the string "gfx900" or something else for the name?
I normally have gfx901, not a gfx900. I've had that same issue before. I normally rename the gfx900.bin to gfx901.bin in the miners that require a .bin file
just verified clinfo, it's "gfx901"
oh.. and how about api support?
We will address the gfx901 issue in the next release, but for the time being you can try disabling HBCC on the cards while mining.
Adding API support is on our todo list, but we don't have an estimate on when we'll get it released yet.
October 01, 2018, 02:47:26 PM
@alucard20724
Don't think we've tested on that driver version. Can you run "clinfo" from a command prompt, it will dump all opencl platforms and devices on your box. Then, scroll up and locate the section for a Vega 56 that looks like this (might be one at the very bottom of the output):
Before asking you to dump the whole thing here, can you tell me if you see the string "gfx900" or something else for the name?
Don't think we've tested on that driver version. Can you run "clinfo" from a command prompt, it will dump all opencl platforms and devices on your box. Then, scroll up and locate the section for a Vega 56 that looks like this (might be one at the very bottom of the output):
Quote
Platform ID: 00007FF8044C4AB0
Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2527.10 (PAL,HSAIL)
Profile: FULL_PROFILE
Version: OpenCL 2.0 AMD-APP (2527.10)
Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2527.10 (PAL,HSAIL)
Profile: FULL_PROFILE
Version: OpenCL 2.0 AMD-APP (2527.10)
Before asking you to dump the whole thing here, can you tell me if you see the string "gfx900" or something else for the name?
I normally have gfx901, not a gfx900. I've had that same issue before. I normally rename the gfx900.bin to gfx901.bin in the miners that require a .bin file
just verified clinfo, it's "gfx901"
oh.. and how about api support?
October 01, 2018, 12:29:33 PM
@pnixx
Do you have an integrated graphics on the host? If so, you might have multiple opencl platforms available and your AMD GPUs are rather on platform 1. The nr of platforms is shown at the beginning of the opencl output. You can also check Makreliak's post a few posts above this for the best solution, i.e. specifying the platform and device(s) manually.
We need to add a better device scan to the miner, right now it naively tries all devices on platform 0.
EDIT: sry, was a bit quick there, I thought you were on windows as well. We need to check the 18.30 amdgpu-pro release. Looks to me it's using rocm kernels rather than amdcl2 (the format for windows and earlier amdgpu-pro releases). I'm guessing they have merged in the rocm stack for vegas from the point where they relaxed the PCIe atomics requirements. We dropped rocm support in this release but should get it back in again shortly. This should hopefully solve your issue.
Do you have an integrated graphics on the host? If so, you might have multiple opencl platforms available and your AMD GPUs are rather on platform 1. The nr of platforms is shown at the beginning of the opencl output. You can also check Makreliak's post a few posts above this for the best solution, i.e. specifying the platform and device(s) manually.
We need to add a better device scan to the miner, right now it naively tries all devices on platform 0.
EDIT: sry, was a bit quick there, I thought you were on windows as well. We need to check the 18.30 amdgpu-pro release. Looks to me it's using rocm kernels rather than amdcl2 (the format for windows and earlier amdgpu-pro releases). I'm guessing they have merged in the rocm stack for vegas from the point where they relaxed the PCIe atomics requirements. We dropped rocm support in this release but should get it back in again shortly. This should hopefully solve your issue.
October 01, 2018, 12:20:47 PM
@alucard20724
Don't think we've tested on that driver version. Can you run "clinfo" from a command prompt, it will dump all opencl platforms and devices on your box. Then, scroll up and locate the section for a Vega 56 that looks like this (might be one at the very bottom of the output):
Before asking you to dump the whole thing here, can you tell me if you see the string "gfx900" or something else for the name?
Don't think we've tested on that driver version. Can you run "clinfo" from a command prompt, it will dump all opencl platforms and devices on your box. Then, scroll up and locate the section for a Vega 56 that looks like this (might be one at the very bottom of the output):
Quote
Platform ID: 00007FF8044C4AB0
Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2527.10 (PAL,HSAIL)
Profile: FULL_PROFILE
Version: OpenCL 2.0 AMD-APP (2527.10)
Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2527.10 (PAL,HSAIL)
Profile: FULL_PROFILE
Version: OpenCL 2.0 AMD-APP (2527.10)
Before asking you to dump the whole thing here, can you tell me if you see the string "gfx900" or something else for the name?
I see (for amdgpu-pro-18.30-641594):
Quote
Platform ID: 0x7ffae6972df0
Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2679.0 (HSA1.1,LC)
Profile: FULL_PROFILE
Version: OpenCL 1.2
But I see same error:Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2679.0 (HSA1.1,LC)
Profile: FULL_PROFILE
Version: OpenCL 1.2
Team Red Miner version 0.3.2
failed to build program.
[2018-10-01 19:57:47] Failed to initialize device number 0.
October 01, 2018, 08:04:43 AM
@alucard20724
Don't think we've tested on that driver version. Can you run "clinfo" from a command prompt, it will dump all opencl platforms and devices on your box. Then, scroll up and locate the section for a Vega 56 that looks like this (might be one at the very bottom of the output):
Before asking you to dump the whole thing here, can you tell me if you see the string "gfx900" or something else for the name?
Don't think we've tested on that driver version. Can you run "clinfo" from a command prompt, it will dump all opencl platforms and devices on your box. Then, scroll up and locate the section for a Vega 56 that looks like this (might be one at the very bottom of the output):
Quote
Platform ID: 00007FF8044C4AB0
Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2527.10 (PAL,HSAIL)
Profile: FULL_PROFILE
Version: OpenCL 2.0 AMD-APP (2527.10)
Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2527.10 (PAL,HSAIL)
Profile: FULL_PROFILE
Version: OpenCL 2.0 AMD-APP (2527.10)
Before asking you to dump the whole thing here, can you tell me if you see the string "gfx900" or something else for the name?
October 01, 2018, 06:57:35 AM
i get a failed to initialize device number
> Team Red Miner version 0.3.2
> [2018-10-01 06:43:39] Failed to initialize device number 0.
> [2018-10-01 06:43:39] Failed to initialize device number 1.
> [2018-10-01 06:43:39] Failed to initialize device number 2.
running adrenaline 18.9.2/ windows 10
three vega56
parameters:
teamredminer.exe -a lyra2z -o stratum+tcp://lyra2z.usa.nicehash.com:3365 -u myaddressxxxx --platform=0 -d 0,1,2
and even:
teamredminer.exe -a phi2 -o stratum+tcp://phi2.mine.zergpool.com:8332 -u yetanotheraddress
i get the same result with both
> Team Red Miner version 0.3.2
> [2018-10-01 06:43:39] Failed to initialize device number 0.
> [2018-10-01 06:43:39] Failed to initialize device number 1.
> [2018-10-01 06:43:39] Failed to initialize device number 2.
running adrenaline 18.9.2/ windows 10
three vega56
parameters:
teamredminer.exe -a lyra2z -o stratum+tcp://lyra2z.usa.nicehash.com:3365 -u myaddressxxxx --platform=0 -d 0,1,2
and even:
teamredminer.exe -a phi2 -o stratum+tcp://phi2.mine.zergpool.com:8332 -u yetanotheraddress
i get the same result with both
October 01, 2018, 02:45:29 AM
And I was wondering what killed Lyra2z profitability lately...
So it was this release all along. Now all the ETH miners are getting in. Time to sell the rigs.
If only you were never to release for Windows.
Thanks for nothing, I guess.
Oh anyway...
So it was this release all along. Now all the ETH miners are getting in. Time to sell the rigs.
If only you were never to release for Windows.
Thanks for nothing, I guess.
Oh anyway...
Oh anyway... this miner is not the reason you are seeing reduced profits. Blame private FPGAs ... oh and anway, public ones are almost in hand too
This has nothing to do with the windows release as its barely a few hours old
@teamred devs
thanks alot for this, very excited to see what other alogs you are working on? mind giving us a hint? possibly X16r and X17?
once again, thank you for bringing some agility to our AMD cards!
October 01, 2018, 02:23:58 AM
And I was wondering what killed Lyra2z profitability lately...
tdxminer was available for few months at least, it used to be very profitable to mine it with GPUs, but the algo is now ridden with FPGAs.He meant a release for Windows. Noobies could not use it while it was Linux only
But profitability was destroyed a while ago and I doubt it was FPGA, although they are on the networks.
But they were on a long time ago. The market killed it and slow adoption by the users.
October 01, 2018, 02:18:00 AM
And I was wondering what killed Lyra2z profitability lately...
tdxminer was available for few months at least, it used to be very profitable to mine it with GPUs, but the algo is now ridden with FPGAs. October 01, 2018, 01:34:27 AM
And I was wondering what killed Lyra2z profitability lately...
So it was this release all along. Now all the ETH miners are getting in. Time to sell the rigs.
If only you were never to release for Windows.
Thanks for nothing, I guess.
Oh anyway...
So it was this release all along. Now all the ETH miners are getting in. Time to sell the rigs.
If only you were never to release for Windows.
Thanks for nothing, I guess.
Oh anyway...
Jump to: