Quote from: gunnersaurus on March 09, 2021, 05:53:41 PM

I'm currently mining with PhoenixMiner using NiceHash (I would stop using NH if I felt I could make batch file correctly!) as it is by far the best miner I've used due to how stable it is, the level of info displayed and the amount command line of switches.

I'm only using my laptop (yes well aware of the risks and I know I'm not going to make a fortune) with its GTX 1660 Ti (temps around 65-67 with good airflow) and I use the following extra launch parameters:

-lidag 3 -mcdag 1 -mi 14 -nvdo 1 -eres 3 -cclock -305 -mclock +575

My questions are am I using them correctly? Are there some where the value could be changed? Do I need all of the ones I'm currently using?

Thanks in advance!

The parameters are fine but you may try using -powlim to lower the core clock instead of using -cclock. On most Nvidia cards -cclock will not lower the voltages sufficiently (or at all), and the GPU will consume more power than needed. Start with -powlim -10 (this will decrease the power limit by 10%), then try decreasing the power limit further (e.g. -powlim -20) until the hashrate starts to be affected.

Quote from: DireWolfM14 on March 09, 2021, 08:52:38 PM

I don't blame you for wanting to keep your identity a secret, and good job standing your ground. I wouldn't have reacted to Nicehash's message any differently.

However, there were a few days this past week where your clients were scrambling trying to find your software, and since this thread is under constant attack by malware shilling sockpuppets, this episode put your clients in a high-risk situation. Many didn't know whether the software they found was the right version, and there was also suspicion that your Mega and Bitcointalk.org accounts were hacked, or (god forbid,) you went rogue yourself.

Checksums are great, but they don't guarantee that your accounts haven't been hacked, or the software and checksums weren't replaced by the hacker. To help the members of this forum (and the folks at Github will appreciate it also) I suggest you create and stake a PGP key that you use to sign the binaries and/or the checksums. That gives the community a second factor for authentication. If this kind of thing happens in the future we can use the PGP to authenticate your checksums or the binaries and avoid this kind of drama.

This is not a bad idea, and we will definitely look into it. Our main concern is with github - if somebody starts complaining to them like they did to MEGA, they may close our account there too. We already prepared a few backup hosts but won't make them public until they are needed (hopefully not soon).

Quote from: MinermanNC on March 09, 2021, 11:20:18 PM

Well for me I am and have been using most versions of Phoenix miner with no issues. I am currently using Phoenix 5.5c within the Nicehash miner for about the last month. Only to switch things up for a BTC payout. Otherwise I normally have used the Phoenix miner as a stand alone.

I am glad to see the Phoenix devs coming forward to defend themselves and go to lengths to give reassurance on their software and that they are not "MIA"

Lets hope both Nicehash and Phoenix can find a middle ground and get this resolved soon for the benefit of everyone who uses both software's. Its not healthy for the mining world to have doubts on either side.

MMNC

We certainly don't want any "wars" with NH, or anybody else. If they were just telling their clients to avoid third-party miners (and they are doing this for months) without spreading any FUD, well, we may not like it but we would accept it without any complains. But apparently that wasn't enough to move people to their miner, so they had to start smearing us.

Quote from: Renkyz on March 10, 2021, 09:26:40 AM

Quote from: PhoenixMiner on March 10, 2021, 08:30:54 AM

Quote from: Renkyz on March 10, 2021, 08:18:24 AM

Hi, hoping for some help with 1 of my 3090's I use for mining. Using v5.5c.
The problem I'm having is as soon as it hits around 60c temp, the performance drastically goes down. For some reason the card stops pulling the usual ~350 watts and only draws ~270 watts after 60c ish temperature is hit. I have a 2nd 3090 which pulls much higher, has no monitors plugged into it and draws around 400 watts. That card will happily go up to 66-67c temps and remains at the 400 watts draw. I'm really scratching my head with the first 3090. It hurts watching it's hshrate go from 120mh to 90mh just because the temp climbs from 56c to 60c lol. Meanwhile the 2nd card doesn't seem to care about temperature and will chug away doing 122mh with 400 watts.
If you need any extra information such as logs, OC settings etc then please let me know and I can provide them.

Yes, a log will be helpful, but first make sure you add the command-line option -hstats 2 to see the actual clocks, and the reason for throttling (we assume that there is throttling involved), and because 60C is too low for temperature-related throttling, it is probably power-related but we need the log for more information.

If the card is throttling because of the power limit, you can increase it with this option -powlim +20,0 (the 0 is to leave the power limit of the second card at default value as it doesn't have throttling issues).

Hi Phoenix, thanks for the response. I've added in the command line options you suggested and ran the miner for a couple minutes. Sadly the -powlim argument didn't really help. I wasn't sure what the most convenient way of sharing the log would be so I just went ahead and threw it in a pastebin. You can see that here: https://pastebin.com/q780sgsL

The exact cards are EVGA 3090 FTW Ultra's and I'm using EVGA's Precision X1 overclocking software. The OC settings I'm running are the same for each card and they are as follows.
GPU: -400
Mem: +1200
Power and Temp target slider is maxed at 119% for power and 91c for temp. The fans are also all set to 100%.

The log also shows that the performance cap (throttling) reason for the first GPU is the temperature:

Code:

GPU1: cclock 990 MHz, cvddc 743 mV, mclock 10702 MHz, p-state P2, pcap temp

The others called it correctly - the memory is overheating.

Quote from: Shlimann on March 10, 2021, 09:46:34 AM

Quote from: PhoenixMiner on March 10, 2021, 07:55:32 AM

... and when we release the actual new version, it will not be named 5.5d[/b].

Hello. Thanks for the releases.
Will you add more DAG epohs in the next release?

We will but even the current limit (epoch 500) should be enough for at least 14-15 more months.

Quote from: miner1987 on March 10, 2021, 10:26:01 AM

Quote from: Shlimann on March 10, 2021, 09:46:34 AM

Hello. Thanks for the releases.
Will you add more DAG epohs in the next release?

I agree. Current epoch # 400, there are less than 100 left because I think that it will stop working much earlier than 500.

I saw some other ethash miners add more DAGs...

No, 5.5c will work without any problems until epoch 500 (provided that you have enough VRAM). But it is not a big deal to increase limit, and we will do so for the next release.

Quote from: Searinox on March 10, 2021, 08:51:04 PM

You could opt for a middle ground, producing your own private key and signing all subsequent PhoenixMiner releases with it, without registering with an official CA to sign that key. You could then post your public key here in the thread's first post, so any future binaries can be verified against it.

Yes, it seems that a lot of people will be OK with this, so we will probably do it soon. We will also put the public case in another big "verifying" transaction to prove we are behind it.

Quote from: skinnyfalcon on March 11, 2021, 02:22:35 AM

Dear Phoenix Miner Dev,

With the impending end of life for ethereum mining in the near future any plans to add Ravencoin to the mix since other progpow crypto is already on the list?

Yes, but not in the next release - it is already feature-frozen. But definitely in a few months at most.

Quote from: Shlimann on March 11, 2021, 04:50:34 PM

Phoenix still needs our support because today some of my friends asked if they could use this program.
NiceHash blamed the developer for a lot and still hasn't apologized. But they did not forget to post QuickMiner on Twitter today.
At this rate, Phoenix will become an underpopular miner.

Thank for you support. Do not worry too much about that - people will "vote" with their rigs. If their miner is so good, they wouldn't resort to such dirty tactics, and the believe that whole thing will blow over soon enough.