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

wyzdic

newbie

Activity: 46

Merit: 0

Quote from: vmozara on October 31, 2018, 03:29:44 AM

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.

kerney666

member

Activity: 658

Merit: 86

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

heavyarms1912

full member

Activity: 729

Merit: 114

Quote from: todxx on October 31, 2018, 02:13:42 AM

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

member

Activity: 658

Merit: 86

Quote from: dickmo on October 31, 2018, 07:55:03 AM

Quote from: kerney666 on October 30, 2018, 11:48:36 AM

Quote from: dickmo on October 30, 2018, 10:34:13 AM

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.

dickmo

newbie

Activity: 6

Merit: 0

Quote from: kerney666 on October 30, 2018, 11:48:36 AM

Quote from: dickmo on October 30, 2018, 10:34:13 AM

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!!

Triforcebg

newbie

Activity: 12

Merit: 0

Quote from: kerney666 on October 31, 2018, 06:55:46 AM

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.

kerney666

member

Activity: 658

Merit: 86

Quote from: Triforcebg on October 31, 2018, 06:48:05 AM

It does not start without any extra config too Sad

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?

bigassboy

sr. member

Activity: 373

Merit: 254

Quote from: Triforcebg on October 31, 2018, 06:48:05 AM

It does not start without any extra config too Sad

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.

Triforcebg

newbie

Activity: 12

Merit: 0

It does not start without any extra config too Sad

So I am asking here for help!

bigassboy

sr. member

Activity: 373

Merit: 254

Quote from: Triforcebg on October 31, 2018, 06:41:44 AM

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

newbie

Activity: 12

Merit: 0

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!

flashsam

newbie

Activity: 13

Merit: 0

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!!!!

vmozara

member

Activity: 190

Merit: 59

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

plox99

newbie

Activity: 9

Merit: 0

Quote from: todxx on October 31, 2018, 02:15:46 AM

Quote from: plox99 on October 31, 2018, 01:30:04 AM

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

Bepson

newbie

Activity: 5

Merit: 0

Quote from: kerney666 on October 30, 2018, 07:45:49 PM

Quote from: Bepson on October 30, 2018, 03:28:54 PM

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.

Sx5000

jr. member

Activity: 31

Merit: 5

Quote from: todxx on October 31, 2018, 02:13:42 AM

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

geck

member

Activity: 145

Merit: 10

todxx

member

Activity: 176

Merit: 76

Quote from: plox99 on October 31, 2018, 01:30:04 AM

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.

todxx

member

Activity: 176

Merit: 76

Quote from: Sx5000 on October 31, 2018, 01:14:37 AM

Quote from: wyzdic on October 31, 2018, 12:51:04 AM

Quote from: Sx5000 on October 31, 2018, 12:31:33 AM

Dear, please add the option --bus-order, as in JCE, SRB. Very useful for simply identifying problem cards in rigs with a large number of video cards.

When the miner starts, you can see the PCIE ID, open your device manager, find the VEGA card, and you can see the same PCIE ID.

I know that this can be done. But this is not convenient, especially when the card falls off after a while. Sorting by bus number is convenient because it has such an OverdriveNTtool. http://prntscr.com/lcjc3t

Ideally, there should be a sorting by bus number based on the value of the --pcie_fmt parameter. That is, for Linux, 'hex' is more preferable, for Windows - 'dec'

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.

joseph32

member

Activity: 418

Merit: 21

Some more tests:

1150/960 seems to be stable too on Vega 64 LC with insane 2410-2420 MH/s and still less power than SRB. SRB was crashing with 1150.

Tested also some more options, but --cn_config 16+14 is the fastest so far. 13 gets the same speed as SRB ~2100, 15 and 16 crash the cards randomly.

Topic: [ANN] TeamRedMiner v0.10.10 - Ironfish/Kaspa/ZIL/Kawpow/Etchash and More - page 146. (Read 211959 times)