Quote from: boregepco on June 09, 2020, 05:56:38 AM

Not a message like this. Everything looks ok in the beginning, but when it starts to change from epoch to epoch first gpu starts to mine with a lower speed and after a while the miner crash.
P.S. My monitor is on GPU 1...

There is nothing you can do unless you connect the display to 8 GB or 6 GB card. As this isn't possible in your case, you can instead run separate instance of PhoenixMiner for just GPU1 (adding the argument -gpus 1) and use a pool that only mines ETH. The other five cards will run on another instance of PhoenixMiner (with -gpus 23456), that can mine both ETH and ETC.

Quote from: Broomey on June 09, 2020, 06:14:27 AM

Is this what you're after Phoenix? Thanks for the prompt reply too!

I can Private message you a complete "log file" if you think it will help, but other than down the bottom where is says "Agent Service Error", I don't see anything abnormal. And as I say, everything is identical to the other 4 rigs, in every way. Please ignore the Maxhash pool below.. it was a test to see if it was an Ethermine issue.. but same result. Cheers.

Code:

bin: phoenixminer
conf: phoenixminer.pcfg
[707] 2020-06-08 09:37:10Z: (CLI user) Using port 4028...
[707] 2020-06-08 09:37:10Z: (CLI user) Starting screen 'miner-4028' with: /opt/miners/phoenixminer/phoenixminer -epool stratum+ssl://eth-eu.maxhash.org:13011 -ewal 0x972e782f1a165ac661ef716a5f1fcb283a85563a.Rig4 -epsw x -mport 4028 -allpools 1 -logfile /var/log/phoenixminer.log -logsmaxsize 100MB -eworker Rig4 -fanmin 35 -tt 66 -tstop 75 -clGreen 1 -acm -amd -mclock 1960 -cclock 1040 -mvddc 800 -cvddc 800 -mode 1
[707] 2020-06-08 09:37:12Z: (CLI user) Miner screen started...
[707] 2020-06-08 09:38:38Z: (CLI user) Starting command line miner on localhost
bin: phoenixminer
conf: phoenixminer.pcfg
[707] 2020-06-08 09:38:38Z: (CLI user) Using port 4028...
[707] 2020-06-08 09:38:38Z: (CLI user) Starting screen 'miner-4028' with: /opt/miners/phoenixminer/phoenixminer -epool stratum+tcp://eth-eu.maxhash.org:8011 -ewal 0x972e782f1a165ac661ef716a5f1fcb283a85563a.Rig4 -epsw x -mport 4028 -allpools 1 -logfile /var/log/phoenixminer.log -logsmaxsize 100MB -eworker Rig4 -fanmin 35 -tt 66 -tstop 75 -clGreen 1 -acm -amd -mclock 1960 -cclock 1040 -mvddc 800 -cvddc 800 -mode 1
[707] 2020-06-08 09:38:40Z: (CLI user) Miner screen started...
[707] 2020-06-08 09:56:40Z: (CLI user) Miner stopped.
[722] 2020-06-08 09:58:19Z: (FCTRL) service started.
[722] 2020-06-08 09:58:19Z: (FCTRL) Agent Server Error:
[722] 2020-06-08 09:58:32Z: (FCTRL) local IP is 192.168.1.72.
[722] 2020-06-08 09:59:05Z: (CLI user) Starting command line miner on localhost

No, we need the log from the miner itself, which in your case appears to be in /var/log/phoenixminer.log

Quote from: alex31 on June 09, 2020, 07:20:55 AM

Hi All. please tell me can I mine Ravencoin now or at the future with PhoenixMiner?
Thanks.

Now it isn't possible as Ravencoin uses another variant of ProgPOW. We may add support in the future but there is no specific timeframe.

Quote from: delevic on June 09, 2020, 05:10:57 PM

Jutst to report that Phoenix 5.0 works fantastic on Ubuntu 18.04.4 with Amd 20.10 drivers. Much much batter than Claymore in Linux.

Nice to hear

Quote from: UnclWish on June 09, 2020, 09:47:54 PM

So many rejected shares on 5.0x verisions... About 1-1.2% overall rejected shares (not stales or incorrect) on my RX 580 8Gb rigs...

Could you please tell us on which pools? This is normal on nicehash, as it doesn't accept stale shares and they count as rejected shares, and it seems that recently nicehash started changing the jobs more often, leading to more rejected shares.