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

kerney666

member

Activity: 658

Merit: 86

Quote from: golya87 on November 06, 2018, 09:10:59 AM

Quote from: kerney666 on November 05, 2018, 11:40:37 PM

Quote from: golya87 on November 05, 2018, 08:43:16 PM

This is my starting command:

Code:

teamredminer.exe --algo=cnv8 --url=stratum+tcp://gulf.moneroocean.stream:10128 --user=45n...aBx --pass=Moria:x --devices=0,1,2,3,4 --cn_config 14+14,14+14,14+14,14+14,14+14

What did I wrong?

Thank you in advance!

Hmm, hashing looks fine, it would rather be something in the rpc communication with Monero Ocean, although we haven't gotten any other reports for this pool. We're working on fixing some small rpc bugs, we'll make sure to test against Monero Ocean as well.

I've get the same error with monero.miningpoolhub.com and wownero.ingest.cryptoknight.cc also.
I've enabled the miner sw in the windows firewall rules also, so it shouldn't be a FW issue.

I've tried running the latest public release (0.3.6) against all three pools now, I don't have any problems mining at gulf.moneroocean.stream:10128, us-east.cryptonight-hub.miningpoolhub.com:20580, wownero.ingest.cryptoknight.cc:50901.

With the same error on all three pools, I'm guessing the issue is something specific about your setup. Have you found any pool that works? Are other CN miners working fine against the pools above on your machine?

peterboy1

newbie

Activity: 168

Merit: 0

btw, sometimes, random of my rx570 is hashing below 1kh/s be it at start or at the middle of mining.

my temporary fix is just disabling and enabling my lan til it hashes back to its max.

hope you can reproduce it. it mostly happen on a rig with a different brand of cards.

kerney666

member

Activity: 658

Merit: 86

Quote from: golya87 on November 06, 2018, 09:10:59 AM

Quote from: kerney666 on November 05, 2018, 11:40:37 PM

Quote from: golya87 on November 05, 2018, 08:43:16 PM

Hello

After I start the miner, I've got the following error.

Code:

Team Red Miner version 0.3.6
[2018-11-06 02:26:05] Auto-detected AMD OpenCL platform 1
[2018-11-06 02:26:05] Initializing GPU 0.
[2018-11-06 02:26:06] Pool gulf.moneroocean.stream login succeeded.
[2018-11-06 02:26:06] Pool gulf.moneroocean.stream received new job. (job_id: BnhOxLVdmQh7rdyK3iFIaRD8iinZ)
[2018-11-06 02:26:06] Pool gulf.moneroocean.stream set difficulty to 128001
[2018-11-06 02:26:07] Initializing GPU 1.
[2018-11-06 02:26:07] Dev pool connected and ready.
[2018-11-06 02:26:08] Initializing GPU 2.
[2018-11-06 02:26:10] Initializing GPU 3.
[2018-11-06 02:26:11] Initializing GPU 4.
[2018-11-06 02:26:13] Successfully initialized GPU 0: Vega with 56 CU (PCIe 10:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 1: Vega with 56 CU (PCIe 03:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 2: Vega with 56 CU (PCIe 06:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 3: Vega with 56 CU (PCIe 13:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 4: Vega with 56 CU (PCIe 16:00.0) (CN 14+14)
[2018-11-06 02:26:15] Pool gulf.moneroocean.stream received new job. (job_id: vCLrCaDLBkR++jmkZht+CinbJF4f)
[2018-11-06 02:26:36] Stats GPU 0 - cnv8: 1.432kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 1 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 2 - cnv8: 1.419kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 3 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 4 - cnv8: 1.427kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats Total - cnv8: 7.122kh/s, avg 8.746kh/s, pool 0.0 h/s
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream connection was closed due to an error.
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream login succeeded.
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream received new job. (job_id: urc+A/g/16ZnWkFNtJIAmMZFqX0r)
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream set difficulty to 128001

This is my starting command:

Code:

teamredminer.exe --algo=cnv8 --url=stratum+tcp://gulf.moneroocean.stream:10128 --user=45n...aBx --pass=Moria:x --devices=0,1,2,3,4 --cn_config 14+14,14+14,14+14,14+14,14+14

What did I wrong?

Thank you in advance!

Hmm, hashing looks fine, it would rather be something in the rpc communication with Monero Ocean, although we haven't gotten any other reports for this pool. We're working on fixing some small rpc bugs, we'll make sure to test against Monero Ocean as well.

I've get the same error with monero.miningpoolhub.com and wownero.ingest.cryptoknight.cc also.
I've enabled the miner sw in the windows firewall rules also, so it shouldn't be a FW issue.

Will take a look at both today!

golya87

newbie

Activity: 10

Merit: 0

Quote from: kerney666 on November 05, 2018, 11:40:37 PM

Quote from: golya87 on November 05, 2018, 08:43:16 PM

Hello

After I start the miner, I've got the following error.

Code:

Team Red Miner version 0.3.6
[2018-11-06 02:26:05] Auto-detected AMD OpenCL platform 1
[2018-11-06 02:26:05] Initializing GPU 0.
[2018-11-06 02:26:06] Pool gulf.moneroocean.stream login succeeded.
[2018-11-06 02:26:06] Pool gulf.moneroocean.stream received new job. (job_id: BnhOxLVdmQh7rdyK3iFIaRD8iinZ)
[2018-11-06 02:26:06] Pool gulf.moneroocean.stream set difficulty to 128001
[2018-11-06 02:26:07] Initializing GPU 1.
[2018-11-06 02:26:07] Dev pool connected and ready.
[2018-11-06 02:26:08] Initializing GPU 2.
[2018-11-06 02:26:10] Initializing GPU 3.
[2018-11-06 02:26:11] Initializing GPU 4.
[2018-11-06 02:26:13] Successfully initialized GPU 0: Vega with 56 CU (PCIe 10:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 1: Vega with 56 CU (PCIe 03:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 2: Vega with 56 CU (PCIe 06:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 3: Vega with 56 CU (PCIe 13:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 4: Vega with 56 CU (PCIe 16:00.0) (CN 14+14)
[2018-11-06 02:26:15] Pool gulf.moneroocean.stream received new job. (job_id: vCLrCaDLBkR++jmkZht+CinbJF4f)
[2018-11-06 02:26:36] Stats GPU 0 - cnv8: 1.432kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 1 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 2 - cnv8: 1.419kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 3 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 4 - cnv8: 1.427kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats Total - cnv8: 7.122kh/s, avg 8.746kh/s, pool 0.0 h/s
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream connection was closed due to an error.
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream login succeeded.
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream received new job. (job_id: urc+A/g/16ZnWkFNtJIAmMZFqX0r)
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream set difficulty to 128001

This is my starting command:

Code:

teamredminer.exe --algo=cnv8 --url=stratum+tcp://gulf.moneroocean.stream:10128 --user=45n...aBx --pass=Moria:x --devices=0,1,2,3,4 --cn_config 14+14,14+14,14+14,14+14,14+14

What did I wrong?

Thank you in advance!

Hmm, hashing looks fine, it would rather be something in the rpc communication with Monero Ocean, although we haven't gotten any other reports for this pool. We're working on fixing some small rpc bugs, we'll make sure to test against Monero Ocean as well.

I've get the same error with monero.miningpoolhub.com and wownero.ingest.cryptoknight.cc also.
I've enabled the miner sw in the windows firewall rules also, so it shouldn't be a FW issue.

Mashy81

jr. member

Activity: 225

Merit: 1

Quote from: keksik on November 06, 2018, 05:30:02 AM

Quote from: Mashy81 on November 06, 2018, 04:46:20 AM

Quote from: keksik on November 06, 2018, 04:42:24 AM

hello, i run it for many hours thru the day, and i am getting soo many rejected shares on one gpu
is hashing 940h/s but getting like 6/345 shares, this is caused by what? also it wrote low difficulty share, rejected

What are your settings. Core,memory and voltages. To high clocks and or too low voltage some times

i tried to lower 25mhz memory, lets see..i havent seen any drops in core and voltage in hwinfo, just few memory errors(like 200 or so only)

Ideally you want zero memory errors. Keep dropping little by little until no errors.
Sometimes it appears as thought your hashrate is lower but it will be higher accepted buy the pool. Better effective hashrate is what you want

keksik

jr. member

Activity: 169

Merit: 1

Quote from: Mashy81 on November 06, 2018, 04:46:20 AM

Quote from: keksik on November 06, 2018, 04:42:24 AM

hello, i run it for many hours thru the day, and i am getting soo many rejected shares on one gpu
is hashing 940h/s but getting like 6/345 shares, this is caused by what? also it wrote low difficulty share, rejected

What are your settings. Core,memory and voltages. To high clocks and or too low voltage some times

i tried to lower 25mhz memory, lets see..i havent seen any drops in core and voltage in hwinfo, just few memory errors(like 200 or so only)

vrottenberg

jr. member

Activity: 31

Merit: 2

Dear dev,
I really look forward to the function of the failover pool in pools.txt file!

Mashy81

jr. member

Activity: 225

Merit: 1

Changed to static difficulty and it smoothed out the pool hash rate variance.
Miner reports 10.2khs pool reports 10khs ave after 12hrs

Mashy81

jr. member

Activity: 225

Merit: 1

Quote from: keksik on November 06, 2018, 04:42:24 AM

hello, i run it for many hours thru the day, and i am getting soo many rejected shares on one gpu
is hashing 940h/s but getting like 6/345 shares, this is caused by what? also it wrote low difficulty share, rejected

What are your settings. Core,memory and voltages. To high clocks and or too low voltage some times

keksik

jr. member

Activity: 169

Merit: 1

hello, i run it for many hours thru the day, and i am getting soo many rejected shares on one gpu
is hashing 940h/s but getting like 6/345 shares, this is caused by what? also it wrote low difficulty share, rejected

icebody

newbie

Activity: 1

Merit: 0

Just noted that Vega Frontier Edition is performing bad with different settings..... around 1980-2000 h/s
any advice? Huh

kerney666

member

Activity: 658

Merit: 86

Quote from: golya87 on November 05, 2018, 08:43:16 PM

Hello

After I start the miner, I've got the following error.

Code:

Team Red Miner version 0.3.6
[2018-11-06 02:26:05] Auto-detected AMD OpenCL platform 1
[2018-11-06 02:26:05] Initializing GPU 0.
[2018-11-06 02:26:06] Pool gulf.moneroocean.stream login succeeded.
[2018-11-06 02:26:06] Pool gulf.moneroocean.stream received new job. (job_id: BnhOxLVdmQh7rdyK3iFIaRD8iinZ)
[2018-11-06 02:26:06] Pool gulf.moneroocean.stream set difficulty to 128001
[2018-11-06 02:26:07] Initializing GPU 1.
[2018-11-06 02:26:07] Dev pool connected and ready.
[2018-11-06 02:26:08] Initializing GPU 2.
[2018-11-06 02:26:10] Initializing GPU 3.
[2018-11-06 02:26:11] Initializing GPU 4.
[2018-11-06 02:26:13] Successfully initialized GPU 0: Vega with 56 CU (PCIe 10:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 1: Vega with 56 CU (PCIe 03:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 2: Vega with 56 CU (PCIe 06:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 3: Vega with 56 CU (PCIe 13:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 4: Vega with 56 CU (PCIe 16:00.0) (CN 14+14)
[2018-11-06 02:26:15] Pool gulf.moneroocean.stream received new job. (job_id: vCLrCaDLBkR++jmkZht+CinbJF4f)
[2018-11-06 02:26:36] Stats GPU 0 - cnv8: 1.432kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 1 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 2 - cnv8: 1.419kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 3 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 4 - cnv8: 1.427kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats Total - cnv8: 7.122kh/s, avg 8.746kh/s, pool 0.0 h/s
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream connection was closed due to an error.
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream login succeeded.
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream received new job. (job_id: urc+A/g/16ZnWkFNtJIAmMZFqX0r)
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream set difficulty to 128001

This is my starting command:

Code:

teamredminer.exe --algo=cnv8 --url=stratum+tcp://gulf.moneroocean.stream:10128 --user=45n...aBx --pass=Moria:x --devices=0,1,2,3,4 --cn_config 14+14,14+14,14+14,14+14,14+14

What did I wrong?

Thank you in advance!

Hmm, hashing looks fine, it would rather be something in the rpc communication with Monero Ocean, although we haven't gotten any other reports for this pool. We're working on fixing some small rpc bugs, we'll make sure to test against Monero Ocean as well.

kerney666

member

Activity: 658

Merit: 86

Quote from: Bael on November 05, 2018, 07:52:02 PM

Hello

I want to tune the cards, but there is something I do not understand.

[Polaris cards (470-580)]
The standard configuration is 8 + 8 for all of these cards. 7 + 7 might give the same optimal hash, and 9 + 9 can, especially under linux, give a better result for 480/580. For some cards, 16 + 14 is the best choice but also increases the probability of stale shares.

My default cards are like this:

If I put 8 + 8 what does it mean? or if I put for example 7 + 7?

When doing so, do I raise or lower the intensity of the gpu?

Excuse me because it seems that it's obvious to everyone but I do not know what it means, basically I've mined eth always, I think I'm missing something xDD

Great job TeamRedMiner!

regards

Hi Bael!

Thanks for the kind words. It is an intensity setting, like you suggest yourself. The sum of the two numbers will control your total memory consumption on the gpu and how it is spread out over the two threads per gpu. A 4GB card only do 7+7, maybe 8+7. 8 GB can do up to 15+15 or 16+14, but that's rarely worth it for Polaris cards, only Vegas.

golya87

newbie

Activity: 10

Merit: 0

Hello

After I start the miner, I've got the following error.

Code:

Team Red Miner version 0.3.6
[2018-11-06 02:26:05] Auto-detected AMD OpenCL platform 1
[2018-11-06 02:26:05] Initializing GPU 0.
[2018-11-06 02:26:06] Pool gulf.moneroocean.stream login succeeded.
[2018-11-06 02:26:06] Pool gulf.moneroocean.stream received new job. (job_id: BnhOxLVdmQh7rdyK3iFIaRD8iinZ)
[2018-11-06 02:26:06] Pool gulf.moneroocean.stream set difficulty to 128001
[2018-11-06 02:26:07] Initializing GPU 1.
[2018-11-06 02:26:07] Dev pool connected and ready.
[2018-11-06 02:26:08] Initializing GPU 2.
[2018-11-06 02:26:10] Initializing GPU 3.
[2018-11-06 02:26:11] Initializing GPU 4.
[2018-11-06 02:26:13] Successfully initialized GPU 0: Vega with 56 CU (PCIe 10:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 1: Vega with 56 CU (PCIe 03:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 2: Vega with 56 CU (PCIe 06:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 3: Vega with 56 CU (PCIe 13:00.0) (CN 14+14)
[2018-11-06 02:26:13] Successfully initialized GPU 4: Vega with 56 CU (PCIe 16:00.0) (CN 14+14)
[2018-11-06 02:26:15] Pool gulf.moneroocean.stream received new job. (job_id: vCLrCaDLBkR++jmkZht+CinbJF4f)
[2018-11-06 02:26:36] Stats GPU 0 - cnv8: 1.432kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 1 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 2 - cnv8: 1.419kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 3 - cnv8: 1.422kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats GPU 4 - cnv8: 1.427kh/s, avg 1.749kh/s, pool 0.0 h/s 0/0
[2018-11-06 02:26:36] Stats Total - cnv8: 7.122kh/s, avg 8.746kh/s, pool 0.0 h/s
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream connection was closed due to an error.
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream login succeeded.
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream received new job. (job_id: urc+A/g/16ZnWkFNtJIAmMZFqX0r)
[2018-11-06 02:26:44] Pool gulf.moneroocean.stream set difficulty to 128001

This is my starting command:

Code:

teamredminer.exe --algo=cnv8 --url=stratum+tcp://gulf.moneroocean.stream:10128 --user=45n...aBx --pass=Moria:x --devices=0,1,2,3,4 --cn_config 14+14,14+14,14+14,14+14,14+14

What did I wrong?

Thank you in advance!

Bael

jr. member

Activity: 87

Merit: 2

Hello

I want to tune the cards, but there is something I do not understand.

[Polaris cards (470-580)]
The standard configuration is 8 + 8 for all of these cards. 7 + 7 might give the same optimal hash, and 9 + 9 can, especially under linux, give a better result for 480/580. For some cards, 16 + 14 is the best choice but also increases the probability of stale shares.

My default cards are like this:

If I put 8 + 8 what does it mean? or if I put for example 7 + 7?

When doing so, do I raise or lower the intensity of the gpu?

Excuse me because it seems that it's obvious to everyone but I do not know what it means, basically I've mined eth always, I think I'm missing something xDD

Great job TeamRedMiner!

regards

ivomm

legendary

Activity: 1891

Merit: 3096

All good things to those who wait

I just tested this miner. So far stable with 1.8% increase of the profit. However it is liqudated by the same difference between the dev fee with the competitor miner. So, I will run it for a day to support the team, but I hope the fee will be reduced to have some advantage to chose this miner.

heavyarms1912

full member

Activity: 729

Merit: 114

Some dirty oc results. RX570 8gb . 1396 core / 2275 memory. 1133 H/s.

deadsix

hero member

Activity: 751

Merit: 517

Fail to plan, and you plan to fail.

Hitting ~1000h/s on my RX 470's across memory types. Great job guys, repped++. Currently testing for stability and poolside reporting consistency.

pbfarmer

member

Activity: 340

Merit: 29

Quote from: kerney666 on November 05, 2018, 08:17:58 AM

Quote from: netmebtc on November 05, 2018, 07:35:44 AM

Hello,dev. When the pool restart , My vega rigs runing teamredminer0.3.6 will crash and down, Waht is the problem?

Hi! What pool is this? And, why does the pool restart, is it connection down, block due to bad shares, anything else? Will try to reproduce and fix if you provide more info.

Ran into same issue when connection to supportxmr got interrupted. One machine came back fine, but on another, one of two cards crashed almost immediately after reconnect. While I’m certain this can likely be resolved with a clock/voltage adjustment, the miner had been running for 4 hours or so w/o issues, so it seems the restart after reconnect is causing extra stress for some reason. Would be nice not to have to adjust voltages just for this scenario...

peterboy1

newbie

Activity: 168

Merit: 0

Quote from: kerney666 on November 05, 2018, 10:38:23 AM

Quote from: peterboy1 on November 05, 2018, 09:59:09 AM

ok, im about 2 days non stop now. so far so good. here are my statistics on one of my 13gpu rx570 4gb rig:

7331/7315/5

so i have 11 shares missing (as you discussed that the pool might not have responded)

5 rejects, 2 rejects in one card and 1 each random cards.

should i worry about the reject? on pool side, it didnt report any invalid shares. is my internet connection one of the factor? my internet is sometimes erratic.

edit:

i browsed the console, i found that all rejects happened all at once:
(gpu 7) error code: -1 invalid job id
(gpu 2) same
(gpu 9) same
(gpu 2) same
(gpu 5) same

Sounds like a network or pool hickup, and we tried to send old shares after reconnecting. Personally, I think 0.07% rejected shares is very much acceptable. So many things that can and will go wrong over a longer period of time. A pool restart there, some ddos attack there, a little internet glitch for the miner.

Do you see any other indications of pool reconnect etc before those errors?

i noticed nothing. anyway, the more serious reject is low difficulty share, right?

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