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

That's nothing to worry about though, but you're still not seeing any reported hashrates? Please confirm and I'll look into it.

Nopes, it says "Pool eth-eu1.nanopool rpc method "eth_getWork" timed out after 69 seconds. Discarding."

I believe nanopool only can do reported hashrate with the ethproxy protocol. We typically default to one of the other possible protocols. Try adding "--eth_stratum_mode=ethproxy", I think it will solve it for you. Otherwise, let us know and we'll look into it more closely.

using amdmemtweak cli
created a bat file to apply ref 30 in 6 gpus starting from gpu 0 to gpu 5 index
but after running it
it makes no difference
any way to do it in gui?

ref 30

Thanks. Great, great work. Now I can use TRM only.

As as you said, other miners do not report real hashrate. Using it for >12h, despite reporting -2 Mh/s than the miner I was using, calculated hashrate @ the pool went up 4 Mh/s...

That said, I'm not getting miner reported hashrate to eth.nanopool.org. How can I turn that on?

No that would rather be for Vegas . For Polaris, it’s just “--REF 30”. You can always inspect the current values to get a feeling for the right scale.
 

Thanks alot! Free +1 Mh/s on each card. 

I have memory strips made with polaris bios editor some 2 years ago, but REF was 5 on all cards.

To set it on command line, the argument should be --REF 30000, right?

ref 30

Very cool, I just left it running on a 4 polaris machine.

Anyone knows of good mem timings to use with AMDmemtweak with Elpida and Hynix 4 Gb cards?

Wallet argument should be -u, not -wal. That’s the only thing I see, hope it works!

Please help!  I dont understand why miner doesnt start. This is my bat file

set GPU_MAX_ALLOC_PERCENT=100
set GPU_SINGLE_ALLOC_PERCENT=100
set GPU_MAX_HEAP_SIZE=100
set GPU_USE_SYNC_OBJECTS=1
teamredminer.exe -a ethash -o stratum+tcp://eu1-etc.ethermine.org:4444 -wal 0xc614703e0090a58a26b8c301b7662614019f0fbe.rig1 -p x --temp_limit=65 --temp_resume=50

Hi Apprentice,

Apologies that we didn't get this done in this release.  We recognize that pool failover is an important feature, and we will be adding it in the next release.
To help us get it right, could you describe the failover and/or load balancing features you would like to see added?

8:41 AM] todxx: On polaris we've seen varying results depending on clocks/voltages/timings, typically results are in the +0-2% improvment range, with typical values in the +0.5-1% range
[8:42 AM] todxx: We haven't done extensive tune testing, but so far we've seen that TRM will run the same or slightly better in terms of stability for a given hardware configuration.
[8:42 AM] todxx: Some of our early testers reported being able to lower voltage slightly more than with CM/PM
[8:44 AM] todxx: Also you'll need to keep in mind that I'm referring to poolside hashrate here (I.E. real effective hashrate).  We've noticed that CM/PM are often optimistic about reporting their hashrate compared to actual effective hashrate.
[8:45 AM] todxx: You can see this in PM directly as it prints the effective/pool hashrate in the miner, and it is typically less than the hashrate it reports for GPUs
[8:50 AM] todxx: As for vega, we do see a consistent +1.5-2% over other miners for Vegas with samsung mem.  Vega 56s with hynix mem do much much better with trm and the right tuning, easily hitting 50Mh/s with very low power usage.
[8:51 AM] todxx: For the VII we are seeing +5-7% increase in hashrate compared to other miners.
[8:55 AM] todxx: To get good performance on the VIIs you'll need to make sure you're running the v106 bios, hence the pinned message above with the v106 bios installer.

please include the pool fail-over in the next release. This is a very important option.
Thanks.

Just to note that I do use this mine for all of my AMD GPUs

If a thread dies, the hash should drop.
but Hash does not decrease‧