Quote from: natewin on March 12, 2021, 08:00:33 PM

@PhoenixMiner

Any plans for monitoring and allowing fan control based on memory temperature?

Aside from the weirdness going on lately, Nicehash Quickminer does have some really nice new features. Itcan set fan speed based on monitoring of 'Hot Spot' memory temp in DDR6 cards and Memory TJ on 3080/90 cards.

Yes, there will be several options to control the junction temperatures and memory temperatures with the fan speed in the new version but only for AMD cards that report these temperatures. We are working on the same feature for Nvidia 3080/3090 but we are not sure it will make it for the next release.

Quote from: vig3 on March 13, 2021, 02:16:36 AM

Is it me or has Mega always been a bit sketch?

Everyone used it for hosting mining software when we started, and we usually don't try to fix things that aren't broken. Of course, after terminating our account, we had no choice but move elsewhere. It is encouraging that other miner software survives fine on github, so hopefully it will be our new hosting solution.

Quote from: earlybird36 on March 13, 2021, 03:50:04 PM

Is there any way to delay the application of overclock on the core during dag creation. I know its possible on the memory with -mcdag but Im having issues on the coreclock during dag creation process. I know increasing memory will increase the hashrate but in my case, increasing the coreclock increases the hashrate as well. Weirdly it only happens on my gtx 1070.

Not that weird - the TLB cache is part of the core, and its speed is the limiting factor of the hashrate of GTX1070 with the current DAG sizes. We could add it but not in the next release.

Quote from: globula_neagra on March 13, 2021, 07:46:28 PM

Hello all,

Want to mention first that I am not here to blame anyone, probably the only one to blame is just me for not enabling 2FA.

I got hacked and here is the story.
Been using NH for about two weeks, I was like, let me jump on the train with the rest.
....

It's hard to tell - could be anything. We know that the (non-fake) releases of PhoenixMiner are clean but we can't speculate for the rest. It could even be some kind of vulnerability at a browser, or OS level. We would recommend using firewall that is blocking outgoing connections (in the default state Windows firewall only asks for permission for incoming connections and allows all outgoing connections). With such firewall even if something is compromised, at least it won't be able to "phone home". These firewalls are a bit of pain in the ass to configure though, as a lot of things connect to the Internet all the time.

Quote from: micdee on March 13, 2021, 10:00:39 PM

Situation:

We are no experts miners..
First we used 6 Radeon RX 580 GPU's (mixed brands) with Ubuntu as OS and Phoenixminer 5.5c as miner for a while.. Then we added a 7th 580 which came available and with no hussle we got it running. I have been busy to get the best settings for each card and got decent hashrates..

Now we wanted to up the hashrates by replacing the 580's GPU's with RX 5700 XT's one by one.
But for some reason we do not get the first one to be recognized in Phoenixminer.
It shows in the PCI list of Linux..

To make sure the 580's would run kind of optimized and since I do not know yet at what GPU number the 5700 would be get by phoenixminer, I wrote following lines in the config file:

-cclock RX*580:1150
-cvddc RX*580:850

-mclock RX*850:2175
-mvddc RX*580:860

As I understood from the help for the config file this should set the core/mem clock and voltage for all GPU's that are named RX AND 580 with the specified numbers.. all other cards (the RX 5700 XT) should use their default.
But when the miner is started the settings are not used and the RX 5700 is not displayed and we start mining with only 6 iso 7 cards.

I tried to look for any sollutions already but came without any..

Any help, ideas are highly appreciated.

The commands look fine but you need to check how the cards are listed by the miner when you run ./PhoenixMiner -list. Some cards may be named differently and won't match the selector in the commands. You should also check the log for applying the clocks and voltages for all cards. For example:

Code:

2021.03.14:04:14:44.503: hwmc GPU1: set GPU clocks to 1090 MHz (Vddc 920 mV)
2021.03.14:04:14:44.510: hwmc GPU1: set VMEM clocks to 2000 MHz (Vddc 900 mV)