yes im the same in terms of once hashing trm is super stable with the rx580 cards setup correctly. I’m 100% share’s accepted since last boot which is sometime now. Obviously i started TRM with hiveos having no overclocks applied to cards at all and then once running i applied the overclock profile. I have the TRM watchdog enabled and no dead gpu message since getting all the card overclocks super stable. Before when using simply the hive community shared configs the rig was unstable and maybe a dead gpu from watchdog every 6 hours or so. But like i say since cards setup properly i’m no longer having that issue and gpu’s temps sitting nice around 50-54c with fans on auto only at most 30%. TRM doing a nice job in that respect.
Also do you have any idea why when i set my voltage to 850mv in hiveos overclock section TRM reports in console card voltage to be 950mv ? Seemed strange being that I had set the undervolt along with the clock settings etc and clock settings all worked by reflection of increased hash rate yet the undervolt seemed to have not got through to TRM. Any clues appreciated.
& yes i have read all the TRM documentation and some options need better explaiing such as the --eth config
-eth_config=CONFIG Manual ethash configuration for the miner. CONFIG must be in the form [M][L].
The [M] value selects the mode which can be ‘A’,‘B’, or ‘C’.
The ‘B’ mode uses additional memory and will only work on 8+GB cards.
The ‘C’ mode uses additional memory and will only work on 16+GB cards, such as the VII, with
a correctly configured system. See the ETHASH_TUNING_GUIDE.txt for more details.
The [L] value selects the intensity and it’s range will depend on the GPU architecture.
Both values are optional, but if [L] is specified, [M] must also be specified.
Example configs: --eth_config=A
–eth_config=B750
CONFIG can also be a comma separated list of config values where each is
applied to each GPU. For example: --eth_config=A,B750,A288
Any gpu that does not have a specific config in the list will use the first
config in the list.
I thought maybe setting manual tune on all the cards from configs would stop the autotune from happening and thus causing TRM to fail startup when an overclock profile is active in hive. It is how to write the syntax for say a 12 card system . Would it simply be like this : -
-eth_config=A123,A356,A254,A143,A256,A254…etc for all 12 gpu’s based on the console report from a previous trm autotune ?
I assume reading the documentation there is no reference of the tuning number to a specific gpu and the codes just follows logical thought in that A123=GPU0 A356=GPU1 this list would grow historically dependant on how many gu’s are present in the system.
thx
tony
