[ANN] TeamRedMiner v0.10.10 - Ironfish/Kaspa/ZIL/Kawpow/Etchash and More

[todxx]

Hi guys! I have a problem with connect to pool.minexmr.com in this miner.
I mine to long XMR wallet address on Exchange (without payment ID).
In another miner (srb, jce and etc.) everything ok with connection to pool, but only in teamredminer i have a fail.

Does someone have the same problem?

Hey plox99, I just tested one of my rigs running against pool.minexmr.com and it worked fine.
Can you post what your batch file or command line is for running the miner?  Feel free to PM me if you don't want to post it publicly.

[geck]

hi,

im not able to get it to work with my vega64 or 8x vega56.
on both rigs i get the same error message “Failed to initialize device number 0.”

ive tried using -d 1, but then the error becomes device 1 is out of range.

any ideas on what to try next?

edit forgot to mention im on win 10 and 18.6.1 drivers

Have you tried this ?

--platform=1

hi,
yes, i have tried that. Did not work either.

turn off hbcc... it's probably recognizing it has gfx901.

Just checked that, hbcc is turned off. SRBminer detects it as gfx900.

same problem here

Can you post the output from the command “clinfo”? You can run it from the command prompt, it’ll be a long text dump. Also, include your command line and the output from the miner when you run it. Think we’ll be able to nail down this one. Everything points to a platform with a single device being tried, doesn’t match your rig description.

And, we desperately need to add automatic platform id detection...

Code:

  Platform Name:                                 AMD Accelerated Parallel Processing
Number of devices:                               2
  Device Type:                                   CL_DEVICE_TYPE_GPU
  Vendor ID:                                     1002h
  Board name:                                    Radeon RX Vega
  Device Topology:                               PCI[ B#3, D#0, F#0 ]
  Max compute units:                             64
  Max work items dimensions:                     3
    Max work items[0]:                           1024
    Max work items[1]:                           1024
    Max work items[2]:                           1024
  Max work group size:                           256
  Preferred vector width char:                   4
  Preferred vector width short:                  2
  Preferred vector width int:                    1
  Preferred vector width long:                   1
  Preferred vector width float:                  1
  Preferred vector width double:                 1
  Native vector width char:                      4
  Native vector width short:                     2
  Native vector width int:                       1
  Native vector width long:                      1
  Native vector width float:                     1
  Native vector width double:                    1
  Max clock frequency:                           1750Mhz
  Address bits:                                  64
  Max memory allocation:                         4244635648
  Image support:                                 Yes
  Max number of images read arguments:           128
  Max number of images write arguments:          64
  Max image 2D width:                            16384
  Max image 2D height:                           16384
  Max image 3D width:                            2048
  Max image 3D height:                           2048
  Max image 3D depth:                            2048
  Max samplers within kernel:                    16
  Max size of kernel argument:                   1024
  Alignment (bits) of base address:              2048
  Minimum alignment (bytes) for any datatype:    128
  Single precision floating point capability
    Denorms:                                     No
    Quiet NaNs:                                  Yes
    Round to nearest even:                       Yes
    Round to zero:                               Yes
    Round to +ve and infinity:                   Yes
    IEEE754-2008 fused multiply-add:             Yes
  Cache type:                                    Read/Write
  Cache line size:                               64
  Cache size:                                    16384
  Global memory size:                            8573157376
  Constant buffer size:                          4244635648
  Max number of constant args:                   8
  Local memory type:                             Scratchpad
  Local memory size:                             32768
  Max pipe arguments:                            16
  Max pipe active reservations:                  16
  Max pipe packet size:                          4244635648
  Max global variable size:                      3820172032
  Max global variable preferred total size:      8573157376
  Max read/write image args:                     64
  Max on device events:                          1024
  Queue on device max size:                      8388608
  Max on device queues:                          1
  Queue on device preferred size:                262144
  SVM capabilities:
    Coarse grain buffer:                         Yes
    Fine grain buffer:                           Yes
    Fine grain system:                           No
    Atomics:                                     No
  Preferred platform atomic alignment:           0
  Preferred global atomic alignment:             0
  Preferred local atomic alignment:              0
  Kernel Preferred work group size multiple:     64
  Error correction support:                      0
  Unified memory for Host and Device:            0
  Profiling timer resolution:                    1
  Device endianess:                              Little
  Available:                                     Yes
  Compiler available:                            Yes
  Execution capabilities:
    Execute OpenCL kernels:                      Yes
    Execute native function:                     No
  Queue on Host properties:
    Out-of-Order:                                No
    Profiling :                                  Yes
  Queue on Device properties:
    Out-of-Order:                                Yes
    Profiling :                                  Yes
  Platform ID:                                   00007FFB858EFFD0
  Name:                                          gfx900
  Vendor:                                        Advanced Micro Devices, Inc.
  Device OpenCL C version:                       OpenCL C 2.0
  Driver version:                                2580.6 (PAL,HSAIL)
  Profile:                                       FULL_PROFILE
  Version:                                       OpenCL 2.0 AMD-APP (2580.6)
  Extensions:                                    cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_gl_sharing cl_khr_gl_depth_images cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_khr_image2d_from_buffer cl_khr_spir cl_khr_subgroups cl_khr_gl_event cl_khr_depth_images cl_khr_mipmap_image cl_khr_mipmap_image_writes cl_amd_liquid_flash

My command line is teamredminer.exe  -a cnv8 -o stratum+tcp://cryptonightv8.eu.nicehash.com:3367 -u xxx -p x --api_listen=0.0.0.0:4028

and the output is
Mining Engine Process started, PID: 18540
>           Team Red Miner version 0.3.4
> [2018-10-31 01:33:17] Failed to initialize device number 0.

Hope it helps.

does your system have integrated graphics?

if so, you might need --platform=0 or --platform=1, i see that you already tried platform=1, so try the other.

Yes it has integrated graphics and an nvidia card. Tried platforms 0 and 2 but it didn't work.

0.35 works though! thanks.

[Sx5000]

We will look into this as an option in the future.
What you can do for the time being is manually reorder the cards using the -d option.
If you use the option "-d 2,3,0,1", this will result in the GPUs in the miner being reordered so that GPU0 is actually device 2, GPU1 is device 3, GPU2 is device 0, and GPU3 is device 1.
It's a bit annoying to setup, but it will work with the current version we have today until we can add an option to do it automatically.

Thank you, your advice will greatly help. I did not think about this method

[Bepson]

On win7x64 rx550-2 could not start. Always crash driver. Does the miner work in win 7?

Sorry Bepson, missed this earlier today. We have not tested the miner on Win 7 unfortunately. I have an Rx550-2GB waiting for me, I’ll start playing around with it tomorrow.

It might be that the miner tries to push the intensities too hard. Can you try using —cn_config=2+2 as a very conservative test setting?

Thanks for answering!
I tried several different configurations, 4 + 3, 3 + 3, 2 + 2, 1 + 1. With overclocking the video card and without overclocking In all cases, the driver crashes. I tried to use drivers 18.6.1 and 17.7.2.

[plox99]

Hi guys! I have a problem with connect to pool.minexmr.com in this miner.
I mine to long XMR wallet address on Exchange (without payment ID).
In another miner (srb, jce and etc.) everything ok with connection to pool, but only in teamredminer i have a fail.

Does someone have the same problem?

Hey plox99, I just tested one of my rigs running against pool.minexmr.com and it worked fine.
Can you post what your batch file or command line is for running the miner?  Feel free to PM me if you don't want to post it publicly.

toddx i cannot write you more than 1 private message in 1 hour, so i write here

http://i66.tinypic.com/5phfdy.png

[vmozara]

I just wanted to confirm that version 0.3.5 works for initialization of all cards, even with my turbo-disabled super slow celeron 3885U.

The performance gain is huge, however during the night half of my rigs hanged or crashed, even if I use lower settings than JCE or SRBminer. This miner taps into parts of Vega that are normaly not touched by slower miners, so it will take some time to tune the rigs properly.

keep up with development, thanks

[flashsam]

for statistics:
VEGA64 ref. default settings & bios, OS Ubuntu server 16.04.5, drivers AMDGPU 18.30, Control powerlimit ROCm - level 5 (1408 core, 945 mem). ~1950H/s ~ 190W

Good work!!!!

[Triforcebg]

Hello!
How can I start miner in Hive OS?
I have these settings:
Installation URL:
https://github.com/todxx/teamredminer/releases/download/v0.3.5/teamredminer-v0.3.5-linux.tgz
Name - automaticly changed
Hash algo - cryptonight_v8
Wallet and worker: %WAL%.%WORKER_NAME%
Pool URL: eu-xmr.hiveon.net:12000
Extra arguments :
--platform=0,1,2,3,4,5          
--cn_config=8+8

I have 6xRX580 Sapphire Pulse.
Where I get wrong? I am new in HIVE, but that is not so hard to understand.
Thank you!

[bigassboy]

Hello!
How can I start miner in Hive OS?
I have these settings:
Installation URL:
https://github.com/todxx/teamredminer/releases/download/v0.3.5/teamredminer-v0.3.5-linux.tgz
Name - automaticly changed
Hash algo - cryptonight_v8
Wallet and worker: %WAL%.%WORKER_NAME%
Pool URL: eu-xmr.hiveon.net:12000
Extra arguments :
--platform=0,1,2,3,4,5          
--cn_config=8+8

I have 6xRX580 Sapphire Pulse.
Where I get wrong? I am new in HIVE, but that is not so hard to understand.
Thank you!

try --cn_config=8+7 or 7+7, it works for me..

[Triforcebg]

It does not start without any extra config too
So I am asking here for help!

[bigassboy]

It does not start without any extra config too
So I am asking here for help!

is your onboard display enabled? if yes then use --platform=1 if not then just omit it. RX580 4gb = 1049h/sols for me.

[kerney666]

It does not start without any extra config too
So I am asking here for help!

Hmm it should work without the extra args. We had one user report a crash on startup in Hive yesterday though. May I ask the following:

1) what’s your HiveOS version?
2) 4GB or 8GB cards?
3) can you start the miner directly in a shell, ie command line, and post the output here?

[Triforcebg]

Hmm it should work without the extra args. We had one user report a crash on startup in Hive yesterday though. May I ask the following:

1) what’s your HiveOS version?
2) 4GB or 8GB cards?
3) can you start the miner directly in a shell, ie command line, and post the output here?

1)0.5-82
2)8GB
3)Don't know how.

AMD drivers - 18.10.

[dickmo]

          Team Red Miner version 0.3.4
[2018-10-30 15:25:55] Pool gin.f2pool.com successfully subscribed.
[2018-10-30 15:25:55] Pool gin.f2pool.com authorization succeeded.
[2018-10-30 15:25:55] Pool gin.f2pool.com set difficulty to 15.999756
[2018-10-30 15:25:55] Pool gin.f2pool.com received new job. (job_id: aKXuutTIJS)
[2018-10-30 15:25:55] Successfully initialized GPU 0: Vega with 56 CU (PCIe 10:00.0)
[2018-10-30 15:25:55] Successfully initialized GPU 1: Vega with 56 CU (PCIe 0d:00.0)
[2018-10-30 15:25:55] Dev pool connected and ready.
[2018-10-30 15:25:55] Successfully initialized GPU 2: Vega with 56 CU (PCIe 09:00.0)
Segmentation fault


i just upgrade amd-gpupro driver from 18.10 to 18.30 on hiveos(ubuntu 16.04.5),then start like above

Well, that is annoying, hmm. Would it be possible for you to check if this is a regression bug in this new version, i.e. since you run lyra2z, if you download and run an older version of the miner on the 18.30 driver, do you still get the same seg fault?

after reinstall 18.10,everything is fine.   great work guys!!

[kerney666]

          Team Red Miner version 0.3.4
[2018-10-30 15:25:55] Pool gin.f2pool.com successfully subscribed.
[2018-10-30 15:25:55] Pool gin.f2pool.com authorization succeeded.
[2018-10-30 15:25:55] Pool gin.f2pool.com set difficulty to 15.999756
[2018-10-30 15:25:55] Pool gin.f2pool.com received new job. (job_id: aKXuutTIJS)
[2018-10-30 15:25:55] Successfully initialized GPU 0: Vega with 56 CU (PCIe 10:00.0)
[2018-10-30 15:25:55] Successfully initialized GPU 1: Vega with 56 CU (PCIe 0d:00.0)
[2018-10-30 15:25:55] Dev pool connected and ready.
[2018-10-30 15:25:55] Successfully initialized GPU 2: Vega with 56 CU (PCIe 09:00.0)
Segmentation fault


i just upgrade amd-gpupro driver from 18.10 to 18.30 on hiveos(ubuntu 16.04.5),then start like above

Well, that is annoying, hmm. Would it be possible for you to check if this is a regression bug in this new version, i.e. since you run lyra2z, if you download and run an older version of the miner on the 18.30 driver, do you still get the same seg fault?

after reinstall 18.10,everything is fine.   great work guys!!

Glad to hear it dickmo! But, I'm a little concerned you won't be getting the max possible Vega hashrates with 18.10.

I have a hunch your issue is what Triforcebg (above) is hitting as well. I will try to get HiveOS 0.5-82 going today or tomorrow on 18.30 to see if I get the same error.

[heavyarms1912]

We will look into this as an option in the future.
What you can do for the time being is manually reorder the cards using the -d option.
If you use the option "-d 2,3,0,1", this will result in the GPUs in the miner being reordered so that GPU0 is actually device 2, GPU1 is device 3, GPU2 is device 0, and GPU3 is device 1.
It's a bit annoying to setup, but it will work with the current version we have today until we can add an option to do it automatically.

Aah this is nice if -d helps to maintain the order.

[kerney666]

Rx550 update

Finally got time to play around with an Rx550 2GB. We were missing a device string, so the miner didn't recognize the gpu and failed in the early initialization. It's now fixed, I managed to squeeze out ~428 h/s using 2+2 with 1150/900 cclk, 1875/900 mclk as shown below. Please note that I have zero experience with the Rx550, so I just went with some values.

We will be releasing an updated version tonight with support for Rx550.

Code:

C:\miner>teamredminer.exe -a cnv8 -o stratum+tcp://pool.supportxmr.com:7777 -u xxx+10000 -p x -d 1
          Team Red Miner version 0.3.5
[2018-10-31 14:41:37] Auto-detected AMD OpenCL platform 0
[2018-10-31 14:41:38] Initializing GPU 0.
[2018-10-31 14:41:38] Pool pool.supportxmr.com login succeeded.
[2018-10-31 14:41:38] Pool pool.supportxmr.com received new job. (job_id: qLzw6pc0GxZqslZBlOyKg/VrvvS0)
[2018-10-31 14:41:38] Pool pool.supportxmr.com set difficulty to 10000
[2018-10-31 14:41:38] Dev pool connected and ready.
[2018-10-31 14:41:39] Successfully initialized GPU 0: Polaris with 8 CU (PCIe 04:00.0) (CN 2+2)
[2018-10-31 14:41:47] Pool pool.supportxmr.com share accepted. (GPU0) (1/1/0)
[2018-10-31 14:42:03] Pool pool.supportxmr.com share accepted. (GPU0) (2/2/0)
[2018-10-31 14:42:08] Stats GPU 0 - cnv8: 406.3 h/s, avg 420.7 h/s, pool 699.3 h/s 2/0
[2018-10-31 14:42:18] Pool pool.supportxmr.com share accepted. (GPU0) (3/3/0)
[2018-10-31 14:42:21] Pool pool.supportxmr.com share accepted. (GPU0) (4/4/0)
[2018-10-31 14:42:38] Stats GPU 0 - cnv8: 427.2 h/s, avg 423.7 h/s, pool 682.6 h/s 4/0
[2018-10-31 14:42:55] Pool pool.supportxmr.com share accepted. (GPU0) (5/5/0)
[2018-10-31 14:43:02] Pool pool.supportxmr.com share accepted. (GPU0) (6/6/0)
[2018-10-31 14:43:08] Stats GPU 0 - cnv8: 429.2 h/s, avg 424.7 h/s, pool 677.2 h/s 6/0
^C

[wyzdic]

I just wanted to confirm that version 0.3.5 works for initialization of all cards, even with my turbo-disabled super slow celeron 3885U.

The performance gain is huge, however during the night half of my rigs hanged or crashed, even if I use lower settings than JCE or SRBminer. This miner taps into parts of Vega that are normaly not touched by slower miners, so it will take some time to tune the rigs properly.

keep up with development, thanks

Me too.
I increase the voltage and reduce the memory frequency, but the mine crash will still crash in about 2 hours. This happens on my Vega56 mine and the vega64 mine is running normally.

[LordPower]

I just wanted to confirm that version 0.3.5 works for initialization of all cards, even with my turbo-disabled super slow celeron 3885U.

The performance gain is huge, however during the night half of my rigs hanged or crashed, even if I use lower settings than JCE or SRBminer. This miner taps into parts of Vega that are normaly not touched by slower miners, so it will take some time to tune the rigs properly.

keep up with development, thanks

Me too.
I increase the voltage and reduce the memory frequency, but the mine crash will still crash in about 2 hours. This happens on my Vega56 mine and the vega64 mine is running normally.

I have the same problem, works for a few hours then crash's and reboots the machine, was able to capture it doing it, it appears to be when the miner switches from mining to the dev fee, the driver pukes with OPENCL_INITIALIZATION error on windows 10,

rebooting the machine and starting over works and then issue repeats itself when dev fee kicks in.

[vmozara]

I have reverted to srbminer on 3 of my 7 rigs. I have no idea what is going on. Even with super safe voltages and frequencies, the miner immediately crashes the rig, after running without issues for 12 hours on much more agressive settings. Now, One rig is so screwed up that I am unable to DDU the driver, rig crashes during DDU so i will have to go to the rigs and see what is going on.

Other 4 rigs (all same rigs, octominer board + 7 reference vegas) seems to work fine and hash very nice.

Please, can you implement some stuff in next version for miner tuning purposes. They don't need to be a default, but can be enabled for miner tuning.

1. A logfile
2. Remove all parallelization and do things one by one
3. If devfee is at the very start of the miner, push it back or put it at random time. I have restarted my miners 400 times during last day for tuning

i will give up temporarily as i already have massive downtime, and check experiences of others. Whoever has the miner runing stable and efficient for multi vega rig, please share your setups and configs here.