Phoenix, when will be miner update for support new AMD 19.12 drivers?

AMD released new Adrenalin 2020 edition drivers. What about PM support?

Yeah, we can add manual tuning mode if people want to play around. The auto-tuning should find the best value though, it doesn't matter that it's running as speed appears to increase, that's just an effect of the DAG rebuild. The auto-tune looks much more closely at the runtime for every separate run that we do on the gpu and not those increasing values.

Team Red Miner v0.6.1 released

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

Changes in v0.6.1

• Added pool failover and load balancing.
• Added better error messages when failing to allocate eth DAG buffers.
• Added server name for TLS SNI.
• Added automatic setting for environment variables for 4GB GPUs.
• Extended maximum length of usernames and passwords (for some merged mining setups).
• Added report of pool stats.
• Changed initial pool auto detect mode to eth proxy.
• Various fixes for submitting hashrate to pools.

It's been a long time coming, but we finally did it; we added pool failover support
We also added pool hashrate stats to help with tracking multi-pool use.
For the more advanced users, we also support load balancing pool strategies.  (See the --help output for more info)
If you want to try it out, there is an example start_multipool.sh/bat file included in the miner packages.

Hi UnclWish!

I truly believe you only mean well, and I _really_ believe you want to run the miner most optimal for yourself, and you (like all miners) would like to be able to test and verify miners to compare for yourselves. Like todxx mentioned, Phoenix miner has been underperforming its displayed hash rates with an avg of -2.9% right now across all our runs. That has now been verified in tests done outside of our control as well, but still mostly with people that we know, and I'd love if people like you, that we only really interact with here in this forum, would run some tests as well.

Therefore, I would like to offer you compensation in XMR for mining air for a few days so you can test for yourself using our released ethash miner testing tool. I've tried to present the math and statistics in the documentation for the tool, and show that 24h poolside tests using a single gpu or even full rig are just way too random to trust. We need a much much larger sample size, and that's why we built and released the tool in the first place.

It is indeed difficult on a single 580 though, it will take maybe 5 days to do a single test, and naturally, it must run 100% stable during that time, no crashes or internet outages etc. Maybe you have more than one 580 to test with? If you're interested, try to get started yourself, then we'll answer any questions you might have here in public to you get going. Then you report back when the test is done.

For people thinking that running a 5+ days long test with a much lower diff than normal pools sounds ridiculous, unfortunately it's what you need if you only do a single gpu. The test is just a very controlled way of keeping track of your mining over a longer period of time, where pools normally only present a sliding window of the last N hours.

Again, the tool and documentation is available here:

https://github.com/Kerney666/trm-ethash-miner-tester/

Cheers, Kerney

You can specify configs for the cards like with the cn_config, but it's eth_config instead.  To make all cards run A mode, you can use --eth_config=A
You can set a specific mode and intensity with something like so: --eth_config=A300
You can also provide a list with one entry per card, like so: --eth_config=A300,B400,A,B


I'm guessing you haven't read any of the last ~20 posts in this thread.  You might want to go back and look through them a bit.
TL;DR: Phoenix miner reports hashrate ~2.9% higher than it actually gets.  So by your measurement, we're getting about 0.9% better actual hashrate (I.E. your pool hashrate will go up 0.9%).

You can enable logging by adding the following option to the command line:
--log_file=trm_log.txt

Where trm_log.txt is the name of the log file to write out.

Hi UnclWish,

We've seen things like this happen in the past when a pool has banned an IP, but that usually only happens if the miner does something like submit a lot of invalid shares.
Do you have a log of when this happened?
I'd be interested to see the part of the log when it stopped mining and started having this problem.

Gaaah, it's actually messier than you'd think, especially since we're a cross platform miner. Need to do both the full OverdriveN API on windows, then messing around with sysfs on linux. Not impossible, but it's one of those things you just love to rely on e.g. mining OSs for, handle all linux quirks etc.

If things quiet down somewhat I'll take a more proper look though.

18.6.1 driver is the best for mining for RX cards if you compare hashrate and stability with latest ones. 4.8c is buggy and there is nothing significant for mining.