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

[kerney666]

Hi all

Is it mean that ETC on 4gb cards is over?


rig (4x570 4gb)
internal graphic card is used (no monitor emulation)
4gb RAM
pagefile 50gb
win10

p.s. if i start to ETH - it's generating dag file correctly

Hi, see the post above, 0.7.3 will handle a few more epochs, then we'll release 0.7.4 with a better fix.

[ZombieWorm]

Are you running a monitor on that gpu? Currently that means you'll have to tune down the config manually, but we're about to add code for detecting and adjusting that automatically. The Windows TDR timeout can also still be bitchy at times, I'm about to run more tests on that today and add automatic behavior for that too.

Yes monitor running off GPU. Its not aggressive as I like low temps - vega56, under clock, under volt. Let me know if you want details. On default settings it crashes and screen reset (went black for ~ 20secs) so its likely the new drivers not quite perfect?

[ALEX_RAA]

Hi all

Is it mean that ETC on 4gb cards is over?
https://ibb.co/CPGR0qj

rig (4x570 4gb)
internal graphic card is used (no monitor emulation)
4gb RAM
pagefile 50gb
win10

p.s. if i start to ETH - it's generating dag file correctly

Hi, see the post above, 0.7.3 will handle a few more epochs, then we'll release 0.7.4 with a better fix.

thnx for so fast reaction! it works!

[kerney666]

Are you running a monitor on that gpu? Currently that means you'll have to tune down the config manually, but we're about to add code for detecting and adjusting that automatically. The Windows TDR timeout can also still be bitchy at times, I'm about to run more tests on that today and add automatic behavior for that too.

Yes monitor running off GPU. Its not aggressive as I like low temps - vega56, under clock, under volt. Let me know if you want details. On default settings it crashes and screen reset (went black for ~ 20secs) so its likely the new drivers not quite perfect?

Hi, sorry for the late reply, had this written in a Chrome tab for a while it seems  .

There are two things in play here, the Windows TDR mechanism and the way we run the kernels. We're working on proper monitor detection in the next release, and will throttle our execution somewhat to allow for rendering tasks to run better in parallel with mining. That way we shouldn't piss off the Windows TDR (Timeout Detection and Recovery).

[ZombieWorm]

Are you running a monitor on that gpu? Currently that means you'll have to tune down the config manually, but we're about to add code for detecting and adjusting that automatically. The Windows TDR timeout can also still be bitchy at times, I'm about to run more tests on that today and add automatic behavior for that too.

Yes monitor running off GPU. Its not aggressive as I like low temps - vega56, under clock, under volt. Let me know if you want details. On default settings it crashes and screen reset (went black for ~ 20secs) so its likely the new drivers not quite perfect?

Hi, sorry for the late reply, had this written in a Chrome tab for a while it seems  .

There are two things in play here, the Windows TDR mechanism and the way we run the kernels. We're working on proper monitor detection in the next release, and will throttle our execution somewhat to allow for rendering tasks to run better in parallel with mining. That way we shouldn't piss off the Windows TDR (Timeout Detection and Recovery).

Sounds great!

[todxx]

Team Red Miner v0.7.4 released

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

Changes in v0.7.4

• Increased ethash support on 4GB GPUs up to epoch 380-383
• Implemented split ethash dag buffers for 8GB GPUs to support DAGs over 4GB
• Kawpow optimizations (Navi +2.25%, Vega +1.25%, Polaris +0.25%)
• Added gpu enable/disable API support.
• Windows TDR detection/handling/warning.
• Monitor detection on Windows/Linux with intensity adjustment.
• Fix for ethash pool hashrate reporting stopping after network outage.

The big push in this release is extending ethash support for 4GB GPUs on higher epochs.  Version 0.7.3 stopped working at epoch 351 which ETC has now crossed.
Anyone running 4GB GPUs on ETC or Nicehash should update to this version as soon as possible.

We also managed to squeeze in some optimizations for Kawpow.  As you can see above Navi and Vega benefit the most from these optimizations.

[souvenir12]

Team Red Miner v0.7.4 released

Great news mate! 383 epoch is for linux? how about windows? How can i test on my own?

[tale01]

Thanks for solved TDR detection. 

[ZombieWorm]

Team Red Miner v0.7.4 released

Initial test looks good. Well done guys!!

[justoiurii]

Hello, masters) Could someone point me for my RX480 8G best variants of cloking, driver etc. to mine ETH and gain better then Claymore. Thanks for advise)

[dastardlyman12]

I dont post very often.
last time was to say very well done to claymore for the straps and rxboost stuff.
just here to say VERY impressed with teamredminer on kawpow
ive got radeon VII and a couple of bios hacked rx 5700 blower cards.
they are getting WAY better than NBminer and nanominer on kawpow.
way better.
seem to be getting 25 on the rx5700s and 40 on the radeon Vii.

windows 10 version 2004 and amd driver 20.3.1
radeon Vii is at 1450 ish and the rx 5700s are at 1600 ish
memory at minimum speed

used amd driver to set clocks

the only thing i would like is to be able to set clocks in the config file of teamredminer.
best wishes to the devs.

ps - everyone put a limit on the clocks in the amd settings or you will melt your cards and psu
thats not a comment on teamredminer - i nearly blew my radeon VII doing kawpow on nanominer a few weeks back
pps get a killawatt

[todxx]

Team Red Miner v0.7.5 released

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

Changes in v0.7.5

• Fixed broken optimizations for kawpow in 0.7.4.

We had a kawpow bug slip into the previous released version.
This bug caused Vegas to run slower than necessary and caused occasional hw errors in the miner for Navi and Polaris GPUs.
The bug is fixed in this release.

[iDisturbia]

Due to the fact that unlike many respectable and honest developers who allow users to see when devfee process begins and ends, I suggest the following:

Block “dev2.teamredminer.com” within your router and then launch this software.

Check your router’s documentation to see if this feature is available. If not, you can always get a cheap Pi and install Pi-hole to block it.

Sure, you will be mining at a little slower rate but it’s worth it because you might have been losing a lot more!

FWIW, I am aware of at least 2 groups on github who have expressed their interest to investigate this software and make it much cheaper to use.

[ZombieWorm]

OK. So spill the tea..  what nefarious actions are these guys doing - is it the length of time the dev miner kicks in for? 

[kerney666]

OK. So spill the tea..  what nefarious actions are these guys doing - is it the length of time the dev miner kicks in for? 

None. He's a troll with some unknown agenda, and I've gladly made him a bet for 1 BTC whenever he can come back with anything backing the FUD and bs he's dumping wherever he goes. He's a nuisance in multiple miner threads. Naturally he'll never get 1 BTC, since spreading dirt is the only thing he's good for. You're free to read back a few pages when he was last around.

[todxx]

Due to the fact that unlike many respectable and honest developers who allow users to see when devfee process begins and ends, I suggest the following:

Block “dev2.teamredminer.com” within your router and then launch this software.

Check your router’s documentation to see if this feature is available. If not, you can always get a cheap Pi and install Pi-hole to block it.

Sure, you will be mining at a little slower rate but it’s worth it because you might have been losing a lot more!

FWIW, I am aware of at least 2 groups on github who have expressed their interest to investigate this software and make it much cheaper to use.

There is a penalty for blocking the dev fee in our miner, as I'm sure you've seen since the miner will constantly print error messages saying so when it can't connect to the dev pool.
If you are not comfortable paying a dev fee while using this software (or any other software), I suggest using open source miner software instead.  There are many projects out there and I would be happy to point you to some if you can't find any yourself.

Looking through your post history I see you've been a proponent of removing the dev fee from Claymore's miner using various proxy hacks.
So it seems like you're being dishonest about your intentions, and disrespectful to miner developers by trying to cheat their dev fee.

In fact you have yourself clearly stated that you feel "entitled" to use other's hard work for free:

...

As for competition discussion, I am actually a lot more acquainted in human nature who loves things with a shiny sticker that reads: FREE!

So, no matter how low CM and or any other mining software developer - including your upcoming software ask for, there will be always a huge percentage of us in this very forum complaining “how dare you ....” and ask for links to their FREE version - because humans are entitled to everything-free and or open-sourced so I can easily replace your wallet address with my own!

[souvenir12]

There is an issue with 0.7.5 version:
random polaris video card in the system stops mining (showing 0 hashes) and starts to warm up until the thermal protection is triggered, driver 19.12.2. On version 0.7.1 everything is stable.
test system: RX580+RX580+Vega56
algo: daggerhashimoto

[kerney666]

There is an issue with 0.7.5 version:
random polaris video card in the system stops mining (showing 0 hashes) and starts to warm up until the thermal protection is triggered, driver 19.12.2. On version 0.7.1 everything is stable.
test system: RX580+RX580+Vega56
algo: daggerhashimoto

Hi! Would this be immediately from the start or after mining a while? It’s hard to see what the miner could do to increase pressure on the card as you describe without the driver comm with card being busted. If it happens immediately, can you run with —debug and pm me the output? If not immediately, any other clues about what is happening when you run into these situations? Also, does the miner detect the gpu as DEAD or not?

Edit: last, are these 4GB or 8GB 580s, or a mix even?

[souvenir12]

There is an issue with 0.7.5 version:
random polaris video card in the system stops mining (showing 0 hashes) and starts to warm up until the thermal protection is triggered, driver 19.12.2. On version 0.7.1 everything is stable.
test system: RX580+RX580+Vega56
algo: daggerhashimoto

Hi! Would this be immediately from the start or after mining a while? It’s hard to see what the miner could do to increase pressure on the card as you describe without the driver comm with card being busted. If it happens immediately, can you run with —debug and pm me the output? If not immediately, any other clues about what is happening when you run into these situations? Also, does the miner detect the gpu as DEAD or not?

Edit: last, are these 4GB or 8GB 580s, or a mix even?

Hi, it happens randomly from few minutes to few hours.
test system: rx 580 8g, rx 580 4g, vega 56.

As I understand it, because the dag file is now divided, the overclocking potential of the memory has decreased (a person from the local forum also complained about an increase in the number of hw errors). This can explain the fact that mining stops on one of the video cards. But in 0.7.5 version the miner does not report that vc is dead, it reports 0 mh/s, driver does not reset card settings, fan stops spinning (the miner shows that the fan is spinning), and vc goes overheating. Zero RPM function is disabled.
https://piccy.info/view3/13844295/222c1a02ca89fb8cac69eb20dababbe7/orig/

[kerney666]

There is an issue with 0.7.5 version:
random polaris video card in the system stops mining (showing 0 hashes) and starts to warm up until the thermal protection is triggered, driver 19.12.2. On version 0.7.1 everything is stable.
test system: RX580+RX580+Vega56
algo: daggerhashimoto

Hi! Would this be immediately from the start or after mining a while? It’s hard to see what the miner could do to increase pressure on the card as you describe without the driver comm with card being busted. If it happens immediately, can you run with —debug and pm me the output? If not immediately, any other clues about what is happening when you run into these situations? Also, does the miner detect the gpu as DEAD or not?

Edit: last, are these 4GB or 8GB 580s, or a mix even?

Hi, it happens randomly from few minutes to few hours.
test system: rx 580 8g, rx 580 4g, vega 56.

As I understand it, because the dag file is now divided, the overclocking potential of the memory has decreased (a person from the local forum also complained about an increase in the number of hw errors). This can explain the fact that mining stops on one of the video cards. But in 0.7.5 version the miner does not report that vc is dead, it reports 0 mh/s, driver does not reset card settings, fan stops spinning (the miner shows that the fan is spinning), and vc goes overheating. Zero RPM function is disabled.

Correct, all kernels on all cards are now prepared for a > 4GB dag. This means split allocation into two buffers. I don’t believe this should affect oc capabilities in itself, but compute has increased somewhat because the address calculations are now more complex with the split dag. No choice there though, Windows and amdgpu-pro don’t support the bulky allocations .

Your issue is quite confusing though. We don’t make progress hashing but we’re not stuck in a kernel enqueue, or else the card would be detected dead. I wonder if it crashes calling the Windows ADL library, reading clocks and temps, we’ve done a lot of changes there lately (released in 0.7.2). Just makes no sense that your fan stops spinning etc, we don’t do any clock or fan control, only read-only calls.

Can you run with —no_gpu_monitor to check? And thank you for testing and reporting in general, always grateful!

— K