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

kerney666

member

Activity: 658

Merit: 86

Quote from: angelbbs on March 11, 2019, 11:45:08 AM

Quote

Ok, nice with a workaround! Annoying that these fixes weren't enough though. I might have to try to find some older Win10 installation somewhere so I can test properly.

And Win7 too, please

Yep, the fixes for old Win10 means it should work in any legacy terminal. I managed to reproduce it and have it fixed now (for real this time, I hope). Todxx is out cold for > 8h though, and he's the build master.

Meanwhile, this should work:

For anyone with Windows terminal output isses, use TRM 0.4.1 and add --disable_colors to your command line.

angelbbs

full member

Activity: 1179

Merit: 209

Quote

Ok, nice with a workaround! Annoying that these fixes weren't enough though. I might have to try to find some older Win10 installation somewhere so I can test properly.

And Win7 too, please

kerney666

member

Activity: 658

Merit: 86

Quote from: kryx on March 11, 2019, 10:22:34 AM

Quote from: kerney666 on March 10, 2019, 08:01:00 AM

Quote from: oxzhor on March 10, 2019, 05:49:58 AM

@kerney666 any idea when cryptonight-heavyx ( x-cash ) will implemented into TeamRedMiner? Thx Cool

We will start chewing away at variants shortly. I just finished adding the most low hanging fruit one of them all, cn/half for MSR and XTL, will continue with others the next few days. We will add heavy and derived variants in a not too distant future, but it's a little more work getting the base heavy kernels going first.

Edit: I've added heavyx for x-cash as well now, I thought it was a Heavy-derived algo, not CNv8 with 2x iterations. What a stupid choice of name

.

If anyone has any specific ideas about your favorite CN variants you'd like to see added, give us a holler here. No promises for any specific order though .

Is x-cash algo working now in 0.4.1 ?? Which flag to use?

Graft planned also?

Nice Work !!

Half+double CNv8 variants are done already for MSR/XTL/x-cash, I'm going to to the waltz now for Graft. We have a few more things host-side we need to add, then we'll release, shouldn't be more than 2 days away from now.

kerney666

member

Activity: 658

Merit: 86

Quote from: wei0339 on March 11, 2019, 10:08:45 AM

Quote from: kerney666 on March 10, 2019, 04:30:22 PM

Quote from: wei0339 on March 10, 2019, 04:18:09 PM

Quote from: kerney666 on March 10, 2019, 03:33:25 PM

Quote from: wei0339 on March 10, 2019, 02:08:55 PM

i have vega *9 , but --list_devices can't find.

Unexpected, what’s the OS and driver? Other miners working on?

win10 ver.1607
drive:18.6.1
swap space: 128GB

teamredminer-v0.3.8 v8 OK
gminer 1.32 equihash150_5 OK

add --platform=1 or 0 ,both are not normal.
only message "Team Red Miner veersion 0.4.0"

Team Red Miner 0.4.0 mineing, also show "Team Red Miner veersion 0.4.0".
But the temperature of the graphics card will rise

I’m guessing it’s the old win 10 version not liking a terminal command we run to enable colors. Will check later tonight.

Using Team Red Miner 0.4.1 is also not possible.
But the phrase "old win 10 version" reminds me of one thing.
cmd.exe option, ticked the "old console mode".
After canceling, it is normal.

Ok, nice with a workaround! Annoying that these fixes weren't enough though. I might have to try to find some older Win10 installation somewhere so I can test properly.

kryx

newbie

Activity: 91

Merit: 0

Quote from: kerney666 on March 10, 2019, 08:01:00 AM

Quote from: oxzhor on March 10, 2019, 05:49:58 AM

@kerney666 any idea when cryptonight-heavyx ( x-cash ) will implemented into TeamRedMiner? Thx Cool

We will start chewing away at variants shortly. I just finished adding the most low hanging fruit one of them all, cn/half for MSR and XTL, will continue with others the next few days. We will add heavy and derived variants in a not too distant future, but it's a little more work getting the base heavy kernels going first.

Edit: I've added heavyx for x-cash as well now, I thought it was a Heavy-derived algo, not CNv8 with 2x iterations. What a stupid choice of name

.

If anyone has any specific ideas about your favorite CN variants you'd like to see added, give us a holler here. No promises for any specific order though .

Is x-cash algo working now in 0.4.1 ?? Which flag to use?

Graft planned also?

Nice Work !!

wei0339

newbie

Activity: 12

Merit: 1

Quote from: kerney666 on March 10, 2019, 04:30:22 PM

Quote from: wei0339 on March 10, 2019, 04:18:09 PM

Quote from: kerney666 on March 10, 2019, 03:33:25 PM

Quote from: wei0339 on March 10, 2019, 02:08:55 PM

i have vega *9 , but --list_devices can't find.

Unexpected, what’s the OS and driver? Other miners working on?

win10 ver.1607
drive:18.6.1
swap space: 128GB

teamredminer-v0.3.8 v8 OK
gminer 1.32 equihash150_5 OK

add --platform=1 or 0 ,both are not normal.
only message "Team Red Miner veersion 0.4.0"

Team Red Miner 0.4.0 mineing, also show "Team Red Miner veersion 0.4.0".
But the temperature of the graphics card will rise

I’m guessing it’s the old win 10 version not liking a terminal command we run to enable colors. Will check later tonight.

Using Team Red Miner 0.4.1 is also not possible.
But the phrase "old win 10 version" reminds me of one thing.
cmd.exe option, ticked the "old console mode".
After canceling, it is normal.

rubine2323

member

Activity: 84

Merit: 10

Very nice! Have done a quick test on my rigs

Vega 56 6 GPU
11890h/s 1120W (1981h/s)

RX 580 6 GPU
6530h/s 800W (1090h/s)

Pretty solid very nice work!
The power draw on polaris cards is amazing Grin

Miguelgreen

newbie

Activity: 95

Merit: 0

Any news regarding hading xcash algo?
Thank you.

todxx

member

Activity: 176

Merit: 76

Team Red Miner v0.4.1 released

https://github.com/todxx/teamredminer/releases

Changes in v0.4.1

Removed server name verification for SSL connections. (Pools like supportxmr now work with SSL)
Fixed bug causing GPUs to fail to initialize on some systems.
Fixed bug causing GPUs to only run one thread (but display 2x hashrate)
Fixed bug where having GPU_MAX_WORKGROUP_SIZE set too high would cause GPUs to crash.
Fixed bug where older windows versions would get no console output.
Added work-around for driver bug in linux amdgpu-pro drivers resulting in low pool-side hash for polaris cards in rare cases.
Added some cpu verification optimizations. CN/R cpu usage should decrease about 15%.

The changes in this version are mostly addressing issues people have been reporting with the v0.4.0 release.
If v0.4.0 is working for you without issue, updating to v0.4.1 isn't urgent, but probably a good idea when you get the chance.

heavyarms1912

full member

Activity: 729

Merit: 114

Quote from: kristikun on March 11, 2019, 08:42:47 AM

Hello after discovery of team red miner and its insane hashrates , i started to look for cheap amd cards i found a guy whos selling his rigs and has really nice price on Sapphire Nitro OC RX470 8gb.
Anybody here whos using Sapphire Nitro OC RX470 8gb i would like to know - + max hashrates of Cryptonight and Lyra2rev3 which can Sapphire Nitro OC RX470 8gb pull on this miner , thank for any reply

polaris cards rx470/rx480/rx570/rx580 series 4gb or 8gb, all have same hashrate on monero. Only difference is in type of memory straps mod

kristikun

newbie

Activity: 62

Merit: 0

Hello after discovery of team red miner and its insane hashrates , i started to look for cheap amd cards i found a guy whos selling his rigs and has really nice price on Sapphire Nitro OC RX470 8gb.
Anybody here whos using Sapphire Nitro OC RX470 8gb i would like to know - + max hashrates of Cryptonight and Lyra2rev3 which can Sapphire Nitro OC RX470 8gb pull on this miner , thank for any reply

furious_gman

newbie

Activity: 5

Merit: 0

I'm struggling with a weird issue on one of my rigs - the miner keeps crashing with a "POSIX Window...." message. It only happens on 1 of 16 rigs... Tried lowering the clock, even to 1260/925, didn't help Sad

. Did anyone encounter this?

OK, quick edit: turning off CPU share verification seems to have solved it. Don't ask my why...

kerney666

member

Activity: 658

Merit: 86

Quote from: nbvqq on March 11, 2019, 06:48:43 AM

teamredminer.exe -a cnr -o stratum+tcp://xmr-eu1.nanopool.org:14444 -u 49zV3AGkebZRqUBnwatyYagyLrd7QfvG74gLFjcksqqFb737etUHmj4GduyvGtaGsTLL1N4acCgNuYY XmX5pyh9FJAjyB -p x -d 0
--cn_config L3+3

.bat starts, but nothing happens except this inscription, although the hashes go to the pool. How to watch hashes and other info in miner?

There's a bug in the terminal init code for windows - for older win10 and win7 setups that don't support enabling "virtual terminal support" for colors, we abort a function call too early and don't initialize the logging properly. It's fixed and will be included in the next release coming out very soon. Very annoying bug, sorry about that. The API is the one place where you can extract runtime information right now.

nbvqq

newbie

Activity: 1

Merit: 0

teamredminer.exe -a cnr -o stratum+tcp://xmr-eu1.nanopool.org:14444 -u 49zV3AGkebZRqUBnwatyYagyLrd7QfvG74gLFjcksqqFb737etUHmj4GduyvGtaGsTLL1N4acCgNuYY XmX5pyh9FJAjyB -p x -d 0
--cn_config L3+3

.bat starts, but nothing happens except this inscription, although the hashes go to the pool. How to watch hashes and other info in miner?

kerney666

member

Activity: 658

Merit: 86

Quote from: pbfarmer on March 11, 2019, 05:28:08 AM

@kerney666 @todxx

Not sure if this is by design, but just noticed, 16+14 is very different from 14+16 - at least on linux/cnr. On a 2 vega (56 + 64) rig I'm benching w/ 1350(actual)/1107 clocks, running 14+16 produces a pretty stable ~1970 h/s each, but 16+14 produced very strange behavior, where the first vega (64) was running ~750 h/s, while the second (56) was bouncing around between 1100-1500 h/s.

That is odd behavior. The only thing that would/should be affected is the order in which large gpu mem allocations are done at init time. What happens with 15+15 for the V64 and 14+14 for the V56 in the same setup?

pbfarmer

member

Activity: 340

Merit: 29

@kerney666 @todxx

Not sure if this is by design, but just noticed, 16+14 is very different from 14+16 - at least on linux/cnr. On a 2 vega (56 + 64) rig I'm benching w/ 1350(actual)/1107 clocks, running 14+16 produces a pretty stable ~1970 h/s each, but 16+14 produced very strange behavior, where the first vega (64) was running ~750 h/s, while the second (56) was bouncing around between 1100-1500 h/s.

angelbbs

full member

Activity: 1179

Merit: 209

Quote from: kerney666 on March 10, 2019, 04:30:22 PM

Quote from: wei0339 on March 10, 2019, 04:18:09 PM

Quote from: kerney666 on March 10, 2019, 03:33:25 PM

Quote from: wei0339 on March 10, 2019, 02:08:55 PM

i have vega *9 , but --list_devices can't find.

Unexpected, what’s the OS and driver? Other miners working on?

win10 ver.1607
drive:18.6.1
swap space: 128GB

teamredminer-v0.3.8 v8 OK
gminer 1.32 equihash150_5 OK

add --platform=1 or 0 ,both are not normal.
only message "Team Red Miner veersion 0.4.0"

Team Red Miner 0.4.0 mineing, also show "Team Red Miner veersion 0.4.0".
But the temperature of the graphics card will rise

I’m guessing it’s the old win 10 version not liking a terminal command we run to enable colors. Will check later tonight.

Same problem with Microsoft Windows [Version 10.0.17134.590] and Windows 7 (Microsoft Windows [Version 6.1.7601])

adaseb

legendary

Activity: 3808

Merit: 1723

Up to 300% + 200 FS deposit bonuses

So I just noticed that XMR switched to a new algo called CN R. Wondering what speeds people are getting with their RX 470 4GB.

My rigs have been long shut off due to the high power costs and wondering if its beneficial to get them up and running again.

I am assuming the difficulty will stay low for a week or so and then all the miners will make the switch and profits will be equal to ETH profitability, as was last time with the CN V8 fork.

tvukoman

jr. member

Activity: 69

Merit: 5

Miner failed to start over after crash:

log:
[2019-03-10 23:17:44] GPU 3: detected DEAD (03:00.0), will execute restart script start_reset_skript.bat
[2019-03-10 23:17:44] Watchdog triggering miner shutdown after restart script execution.
[2019-03-10 23:17:44] Shutting down...
[2019-03-10 23:17:44] GPU 1 CN thread 1 exiting.
[2019-03-10 23:17:44] GPU 2 CN thread 0 exiting.
[2019-03-10 23:17:44] GPU 0 CN thread 0 exiting.
[2019-03-10 23:17:45] GPU 0 CN thread 1 exiting.
[2019-03-10 23:17:45] GPU 2 CN thread 1 exiting.
[2019-03-10 23:17:45] GPU 1 CN thread 0 exiting.
[2019-03-10 23:17:54] GPU 3 thread 0 shutdown timed out.
[2019-03-10 23:17:54] GPU 3 thread 1 shutdown timed out.

Miner program is open "freezed" with this last note:
Team Red Miner version 0.4.0
[2019-03-10 23:18:22] Auto-detected AMD OpenCL platform 1

I have reset script that work just fine with Vertcoin in 0.3.10 version (disable / enable vegas with devcon, apply overdriveNtool profiles, start miner again)

Any help?

GordoLui

jr. member

Activity: 73

Merit: 2

Quote from: kerney666 on March 10, 2019, 04:30:22 PM

Quote from: wei0339 on March 10, 2019, 04:18:09 PM

Quote from: kerney666 on March 10, 2019, 03:33:25 PM

Quote from: wei0339 on March 10, 2019, 02:08:55 PM

i have vega *9 , but --list_devices can't find.

Unexpected, what’s the OS and driver? Other miners working on?

win10 ver.1607
drive:18.6.1
swap space: 128GB

teamredminer-v0.3.8 v8 OK
gminer 1.32 equihash150_5 OK

add --platform=1 or 0 ,both are not normal.
only message "Team Red Miner veersion 0.4.0"

Team Red Miner 0.4.0 mineing, also show "Team Red Miner veersion 0.4.0".
But the temperature of the graphics card will rise

I’m guessing it’s the old win 10 version not liking a terminal command we run to enable colors. Will check later tonight.

I'm running the exact same version of windows and everything is working fine. Might be worth try this update, second one from the top.

http://www.catalog.update.microsoft.com/Search.aspx?q=KB4103723

I don't know why but it help me run this miner on 1607.

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