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

I get this error on a linux box with no GUI.

You are probably getting that error because your browser(s) are using the GPU? Try turning off "hardware acceleration" in chrome/brave.

I have the same issue on all CN algos except turtlecoin when I launch TRM while any web browser is opened (be Firefox, brave, Edge).

I saw in the release notes that Tonga support has been added, so I tried the latest version (0.5.2) with a Tonga card (r9 380 4GB) but get the following error on startup:


Failed to initialise device idx 3 (-13)


Is this card supported? Or is extra config required for Tonga?



08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] (rev f1)

Much love to Kerney666, too!

Glad to hear it's running smoother
You should send your praise in Kerney666's direction though, he's been the one fighting these issues over the last few days.

Ah interesting! You see, I didn’t make the same small stabilizing adjustments in the main 4MB variant kernels. Obviously I should have, my mistake, I simply forgot. Will try fix them as well very soon and will let you know when a release is available.

Apparently the new release didnot fix the issue.. still have the same error

https://imgur.com/a/GraVN7H?desktop=1

I have 1 Vega 56 that was previously crashing 2-3x per day while my other Vegas chugged along. Since flipping to 0.5.2 yesterday I have not had a single crash.
No changes to OC or mem timings.
Cheers toddxx!!

Still running!
https://i.ibb.co/FgjLTWJ/Untitled.png

edit: 1d 4hours on 5.2 and still no dead GPU. I guess we can call it fixed! (?)

Hmm, the intention is that the miner should use the same ramp-up logic as we use at start-up when a pool has been disconnected, this in order to not kill the PSU by going from 0-100% load on all GPUs at the same time. I can't say I have tested it lately though, and I can't say for sure that this is the issue here. It's a good guess though, no real reason why the rig would croak otherwise. I will do some tests.

Thanks for the kind words, much appreciated!

Hi! Just curious, did you have time to test 0.5.2 yet? It has a first wave of changes that only aim to stabilize the miner. No real guarantees, only some changes that theoretically should be nicer to the hardware. Otherwise, I agree, we’re dealing with some very delicate issues, and the software/driver/hardware interaction here is not all hunky dory.

The best, the fastest and most stable AMD miner ever.
It works perfect on all supported algos.

I am using all 1x slots and am having the same behavior. I am seriously thinking that this is a driver compatibility issue with Win10 for a couple of reasons:

1) It is always (in my case) the first card enumerated on the PCIe bus
2) It doesn't matter what motherboard I'm using (have tried on 7 different)
3) Starting ANY other applications on the same system slows down ONLY the affected GPU, and it shouldn't affect anything, historically.
4) In digging through logs and in the rare cases of a BSOD, there are consistently "stuck thread" issues
5) This phenomenon is not isolated to TRM - I am having the same issue with SRB, Phoenix, Claymore and others

I did not have this problem with earlier builds, but since the latest Windows and AMD updates, I can't get rid of it. I have tried rolling back through every iteration all the way back to Blockchain drivers without success.

I should mention that I am using a mix of V64 and V56 cards in my rigs, but all have Samsung memory.

Hi Kerney,

I already PM you, please check your message.

Thanks.

hi, Dev, the network connection problem always cause the rig crash,

[2019-06-13 21:52:22] Pool asia.cryptonight-hub.miningpoolhub.com connecting to address 172.105.205.58.
[2019-06-13 21:52:30] Stats Uptime: 0 days, 05:58:08
[2019-06-13 21:52:30] GPU 0 [48C, fan 49%] cnr: 533.0 h/s, avg 530.7 h/s, pool 504.0 h/s a:203 r:0 hw:0
[2019-06-13 21:52:30] GPU 1 [49C, fan 39%] cnr: 539.2 h/s, avg 536.6 h/s, pool 525.9 h/s a:216 r:0 hw:0
[2019-06-13 21:52:30] GPU 2 [47C, fan 39%] cnr: 538.3 h/s, avg 533.8 h/s, pool 527.7 h/s a:212 r:0 hw:0
[2019-06-13 21:52:30] GPU 3 [52C, fan 39%] cnr: 543.6 h/s, avg 540.3 h/s, pool 551.6 h/s a:225 r:0 hw:0
[2019-06-13 21:52:30] GPU 4 [53C, fan 49%] cnr: 516.1 h/s, avg 513.2 h/s, pool 456.6 h/s a:182 r:0 hw:0
[2019-06-13 21:52:30] GPU 5 [45C, fan  0%] cnr: 520.5 h/s, avg 517.9 h/s, pool 542.8 h/s a:215 r:0 hw:0
[2019-06-13 21:52:30] Total                cnr: 3.191kh/s, avg 3.173kh/s, pool 3.109kh/s a:1253 r:0 hw:0
[2019-06-13 21:52:32] Pool asia.cryptonight-hub.miningpoolhub.com connect timed-out to address 172.105.205.58.
[2019-06-13 21:52:32] Pool asia.cryptonight-hub.miningpoolhub.com connecting to address 172.105.210.117.
[2019-06-13 21:52:42] Pool asia.cryptonight-hub.miningpoolhub.com connect timed-out to address 172.105.210.117.
[2019-06-13 21:52:42] Pool asia.cryptonight-hub.miningpoolhub.com connecting to address 139.162.46.14.
[2019-06-13 21:52:52] Pool asia.cryptonight-hub.miningpoolhub.com connect timed-out to address 139.162.46.14.

after several retries, success connect to the pool again

[2019-06-13 21:52:52] Pool asia.cryptonight-hub.miningpoolhub.com connecting to address 172.105.197.212.
[2019-06-13 21:52:52] Pool asia.cryptonight-hub.miningpoolhub.com successfully connected to address 172.105.197.212.
[2019-06-13 21:52:53] Pool asia.cryptonight-hub.miningpoolhub.com login succeeded.(1106 ms)
[2019-06-13 21:52:53] Pool asia.cryptonight-hub.miningpoolhub.com received new job. (job_id: 212828560336492)
[2019-06-13 21:52:53] Pool asia.cryptonight-hub.miningpoolhub.com set difficulty to 54564

but this make the rig crash, and restart,  is there any way to prevent this, thanks

[2019-06-13 21:55:44] Initializing GPU 0.
[2019-06-13 21:55:44] Watchdog thread starting.
[2019-06-13 21:55:44] API initialized on 0.0.0.0:522
[2019-06-13 21:55:44] Runtime Command Keys: h - help, s - stats, e - enable gpu, d - disable gpu, q - quit
[2019-06-13 21:55:44] Pool asia.cryptonight-hub.miningpoolhub.com connecting to address 172.105.210.117.
[2019-06-13 21:55:44] Dev pool connected and ready.
[2019-06-13 21:55:44] Initializing GPU 1.
[2019-06-13 21:55:45] Initializing GPU 2.
[2019-06-13 21:55:46] Initializing GPU 3.
[2019-06-13 21:55:47] Miner load at 0%, hashrates are not at max speed yet.
[2019-06-13 21:55:47] Initializing GPU 4.
[2019-06-13 21:55:48] Initializing GPU 5.

All primary x16 slots on any motherboard always are uplink.
What hardware do you guys have? (only for the vega rigs)
H110 3da with latest bios (F25), Celeron G3900 (Skylake) all (2) cores enabled. igfx enabled as primary. and a vega 56 in every pcie slot (stock bios, but we've already established bios, settings and algo don't matter). Single channel & single bank 4Gb memstick Crucial.

For most of us TRM 4.4 seems to work normally although a teeny tiny bit slower, but it's still better than a whole card not running . 5.2 only just released, so can't say yet.

people start autotune, notice they didn't set their own wallet and stop the miner? Just a thought.
There's an easy way to test if this is the case. set a minername in the batchfiles that come with the miner.
If they forgot to change the wallet, likely they didn't change the miner id either.

Well, it should really only happen when we restart our servers, which isn't often at all. So, there's something else cutting the connection for you. In some cases there are home routers that cut connections, in other cases many countries/jurisdictions don't like neither SSL traffic nor mining traffic. May I ask where you're located? You can PM me if you want to. Also, I'd love to know what version of TRM you're running? We have noticed a higher degree of short-lived inbound connections lately, but can't explain why.

Hi Dev,

Why I often got this message :

but after sometime it will connect to dev pool :

is there any solution for this message?



Thanks.