PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 42.

UnclWish

sr. member

Activity: 1484

Merit: 253

Quote from: bategojko74 on August 19, 2021, 05:44:09 AM

Quote from: UnclWish on August 19, 2021, 05:25:21 AM

What about -clgreen 1 ? Why my RX 580 8Gb ignores it? Latest 21.8.1 driver.

-clgreen 1 is currently not supported. Why would you like to trade higher hashrate for lower power consumption and lower hashrate at the current ETH prices?

I just try to find best hashrate with best power consumption...
F.e. TR miner uses 4% less power with 1.2% less hashrate in compare with PM for my RX 580 8Gb cards.
I wanted to try PM with clgreen kernels. Maybe with them it can be better than TR.
PM make more rejected shares on nicehash than TR.

bategojko74

member

Activity: 220

Merit: 12

Quote from: UnclWish on August 19, 2021, 05:25:21 AM

What about -clgreen 1 ? Why my RX 580 8Gb ignores it? Latest 21.8.1 driver.

-clgreen 1 is currently not supported. Why would you like to trade higher hashrate for lower power consumption and lower hashrate at the current ETH prices?

100gh

newbie

Activity: 7

Merit: 0

It's strange how Phoenix miner gets noticed by windows defender every few months
This time its PUA:Win32/Presenoker on 5.6c
probably a false positive right?

UnclWish

sr. member

Activity: 1484

Merit: 253

What about -clgreen 1 ? Why my RX 580 8Gb ignores it? Latest 21.8.1 driver.

bategojko74

member

Activity: 220

Merit: 12

Quote from: speed07 on August 18, 2021, 09:56:56 PM

Quote from: bategojko74 on August 18, 2021, 05:55:09 PM

Quote

maybe due to driver?, i find st in this topic https://github.com/ethereum-mining/ethminer/issues/1966

From 19.X.X till now all amd gpu drivers support 8gb single memory allocation. You can try installing other driver but your chances are little.

oh, tk u

FIXED: You were right for the driver. Install driver 20.5.1 or later and you will be able to run -clKernel 3. It seems that 8GB allocation is introduced in 20.5.1 driver. I have installed 20.4.2 driver on my computer and got the same message as you "clKernel 3 is ignored", and my "Max allocation size" went down to 4244635648.

speed07

newbie

Activity: 28

Merit: 0

Quote from: bategojko74 on August 18, 2021, 05:55:09 PM

Quote

maybe due to driver?, i find st in this topic https://github.com/ethereum-mining/ethminer/issues/1966

From 19.X.X till now all amd gpu drivers support 8gb single memory allocation. You can try installing other driver but your chances are little.

oh, tk u

miner29

full member

Activity: 1275

Merit: 141

Quote from: Cka3ka on August 18, 2021, 01:42:28 PM

still cant figure out how to fix this damn issue .....clkernel 3 is ignored for gpu
i downgraded driver,tryed on linux but still dont work. help plz
eth for 570 4gb should stay alive

Um 4gb hasnt been viable for a while now. Switch to another coin or get a bigger gpu. This isnt a technical / programming issue. Zombie mode for 4gb worked for a good bit but was always going to fade away. It was a limited time hack that once the dag grew it would slowly fail until it completely failed.

bategojko74

member

Activity: 220

Merit: 12

Quote

maybe due to driver?, i find st in this topic https://github.com/ethereum-mining/ethminer/issues/1966

From 19.X.X till now all amd gpu drivers support 8gb single memory allocation. You can try installing other driver but your chances are little.

Cka3ka

newbie

Activity: 2

Merit: 0

still cant figure out how to fix this damn issue .....clkernel 3 is ignored for gpu
i downgraded driver,tryed on linux but still dont work. help plz
eth for 570 4gb should stay alive

eddirush

newbie

Activity: 7

Merit: 1

Quote from: deedeeranged on August 16, 2021, 08:18:01 AM

Quote from: Kumic on August 16, 2021, 04:54:16 AM

Quote from: Deafran on August 15, 2021, 09:51:58 PM

Quote from: Kumic on August 14, 2021, 03:31:38 PM

I have 1070 but with this miner I get only 18 mh for ethereum.
Can I get around 30 mh with this miner if I set it up correctly?

try this set

memory +500
core +100
power 85%-90%

I tried, but hashrate is the same, 18 mh per card with Phoenix miner.

I have a GTX1070 running on Linux. My config settings are:

-nvidia
-nvKernel 3
-nvdo 1
-proto 3
-cdm 1
-prate 0.0703
-coin eth
-log 1
-logdir /home/USER/Miners/logs
-logfile ethermine-pm.log
-pool ssl://eu1.ethermine.org:5555
-pool2 ssl://us1.ethermine.org:5555
-wal YOUR_WALLET.nvidia

Need to run PhoenixMiner as root.
Average speed (5 min): 25.050 MH/s
Effective speed: 24.51 MH/s; at pool: 24.49 MH/s

Hope it helps.

If ur using PM with win7 u will get 18mh on all GTX10xx series cards doesnt matter what drivers u use either, dev hasnt fixed this problem yet I messaged him several times already, it started earlier this year I think, using Linux or Win10 ull see full speed, if u want to keep using win7 then switch to Gminer, they solved the problem pretty quickly, I use Pminer on my Win10 rigs and Gminer on win7 rigs

speed07

newbie

Activity: 28

Merit: 0

bategojko74

member

Activity: 220

Merit: 12

relax69

member

Activity: 61

Merit: 40

Quote from: liyuchang on August 14, 2021, 08:20:10 PM

Quote from: relax69 on August 14, 2021, 03:18:56 PM

Quote from: liyuchang on August 14, 2021, 08:42:33 AM

Hi all,

I got a strange problem and am not sure if anyone here has the same issue.

My rig is running win10 with phoneix5.6d. Since I only mine 12 hrs a day to avoid peak time electric fees, it is auto turn on and off every day. The miner is autorun using the task scheduler after the rig is on. It has 10 gpus (6*rx580 + 4*gtx1070) so can generate around 300mhs. However, I have noted that when the rig is auto on and run the miner, it only got around 292mhs. I have to manually close the miner and run it again to get 300mhs, otherwise, it will stay around 289~292. I also found that the report hashrates in bitfly is unsteady when it's around 289~292. if I restart the miner (not rig), the report hashrates will be steadily staying at 300mhs

For me, it sounds like the miner needs to be "warm up"?? anyone here got the same problem?? Btw, I remember I don't have this problem when using claymore.

For better answer you need to share your log files. I’m guessing from what you said possibly reason is, if you are using straps and rxboost they don’t running with automatic start until you start the rig manually with administrator rights.

this is my log file when running the miner the first time and got 292mhs
https://www.dropbox.com/s/d568k76xa8urlg1/log20210814_214923.txt?dl=0

this is when close and reopen the miner for a second time. I can get around 300mhs
https://www.dropbox.com/s/k2ej440ogvp4yjo/log20210814_224919.txt?dl=0

I don't use rxboost and strape. the setting is just a simple wallet address. I use afterburner for oc. I also noted that if the rig is running at 300mhs, which means the miner is restarted for a second time. The rig will become unstable, it will crash and reboot at least once 12hrs. after reboot it will back to around 292mhs unless close and open the miner again.

It looks like you have the Nvidia cards running the same in both examples but the difference is coming from the AMD cards. I don't like doing overclocking for mining with Afterburner, Watman, or third-party software because it makes the system unstable. PM is the best for me because it's a great tool for overclocking. I will recommend you do not use Afterburner at all or use it only for monitoring.
Also, recommend you to add this to your config file and give it try:

Code:

# RX 580, RX 580, GTX 1070, RX 580, GTX 1070, GTX 1070, RX 580, GTX 1070, RX 580, RX 580

 -powlim 0,0,75,0,75,75,0,75,0,0


  -tt 65
  -fcm 2
  -fanmin 50
  -tstop 88
  -tstart 65
  -hstats 2
  -hwm 1
  -fanstop 1
# -ttj 75
# -ttmem 79


 -mt 1,1,0,1,0,0,1,0,1,1
 -vmr 25
 -straps 1
 -vmt1 25
 -vmt2 20
 -vmt3 0

# -rxboost 1

 -cclock 1100,1100,-200,1100,-200,-200,1100,-200,1100,1100
 -cvddc 850,850,0,850,0,0,850,0,850,850
 -mclock 2075,2075,+700,2075,+700,+700,2075,+700,2075,2075
# -mvddc 750,750,0,750,0,0,750,0,750,750

I did not see your frequencies in the log files so, in the example, I used some information from the internet for the Nvidia cards because I never had GTX 1070 but you can replace the numbers from the Afterburner.
In the example for the RX 580, I use the settings I have for my Sapphire Pulse RX 580 with Samsung memory. Your settings may be different for different brands and memory, but you can replace clocks from the Afterburner.
I have my Sapphire Pulse RX 580 using only 83 Watts and running slightly above 30 Mh/s.

If these settings work for you well, you should lower your power usage too.

webhead

newbie

Activity: 123

Merit: 0

some nice rtx lhr unlocks would be nice thanks .

janding

jr. member

Activity: 170

Merit: 6

speed07

newbie

Activity: 28

Merit: 0

Quote from: bategojko74 on August 17, 2021, 02:50:17 AM

Quote from: speed07 on August 08, 2021, 10:27:28 PM

Quote from: bategojko74 on August 08, 2021, 10:25:32 PM

Quote from: speed07 on August 08, 2021, 04:59:17 AM

Quote from: bategojko74 on August 08, 2021, 02:21:32 AM

Quote from: dazmann on August 07, 2021, 05:59:42 PM

Quote from: dazmann on August 07, 2021, 12:24:07 AM

Quote from: bategojko74 on August 06, 2021, 11:21:38 AM

Quote from: dazmann on August 04, 2021, 12:47:02 PM

Quote from: PhoenixMiner on August 04, 2021, 01:59:24 AM

Implemented new "turbo" kernels (-clkernel 3) for AMD Polaris cards that can work with the current DAG sizes over 4 GB. Note that -clkernel 3 uses double the VRAM and will provide slightly faster hashrate with slightly higher power consumption. You can use the -rvram command-line parameter to specify how much VRAM to be left unused

Please let us know if you have any problems or questions related to PhoenixMiner 5.7b.

Tried the -clkernel 3 on my RX 480 8GB and got lower hashrates than -clkernel 2.
I'm on windows 10 20H2, Radeon Software version 21.6.1
I'm only using the -vmr 25 parameter and -gt 69 as per benchmark suggestion.
Everything else is default.

Your current gt value 69 is not the optimal for -clkernel 3. Put -gt 0 in your settings to find the new best gt value for -clkernel 3. After that you can put -gt NEW_BEST_GT_FOUND_VALUE in your settings.

Thank you very much. I will look into that.

Aaaand nothing changed.

If you have amd rx470/480/570/580 GPUs you will get +0.1mh/s per GPU with -clkernel 3. You will not get increase with Vega, Navi or Nvidia GPUs.

The option -clKernel 3 is ignored for all GPU, when i use -clKernel 3. nitro+ rx570 8g samsung, stock bios.

You are using very old drivers. Update the amd gpu driver.

which version bro? im using 20.4.2

Increase your VRAM to (NUMBER_OF_GPUS+1)*8 GB. If you print the beginning of your log file I will tell you why clkernel 3 is ignored.

Code:

2021.08.04:19:05:12.583: main Phoenix Miner 5.7b Windows/msvc - Release build
2021.08.04:19:05:12.583: main Cmd line: 
2021.08.04:19:05:12.583: main config.txt: -pool asia1.ethermine.org:4444 -pool2 eu1.ethermine.org:4444 -wal 0x67503b7b1833688167eec36fee017bf3cf6e1c79.bo -amd -acm -tt 54 -clKernel 3 -fanmin 52 -fanmax 58 -cclock 1170 -cvddc 830 -mclock *:2040,1:2010,3:2020 -mvddc *:830,1:840 -mi 13 -rxboost 1 -straps 1 -mt 1 
2021.08.04:19:05:14.338: main OpenCL driver version: 20.4.x
2021.08.04:19:05:14.366: main Available GPUs for mining:
2021.08.04:19:05:14.366: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs
2021.08.04:19:05:14.366: main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 32 CUs
2021.08.04:19:05:14.366: main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 32 CUs
2021.08.04:19:05:14.366: main GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 8 GB VRAM, 32 CUs
2021.08.04:19:05:14.366: main GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 8 GB VRAM, 32 CUs
2021.08.04:19:05:14.366: main GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 8 GB VRAM, 32 CUs
2021.08.04:19:05:14.367: main ADL library initialized
2021.08.04:19:05:15.671: main Eth: the pool list contains 2 pools (2 from command-line)
2021.08.04:19:05:15.671: main Eth: primary pool: asia1.ethermine.org:4444
2021.08.04:19:05:15.671: main Starting GPU mining
2021.08.04:19:05:15.671: main Matched GPU1 to ADL adapter index 32 (method 1)
2021.08.04:19:05:15.699: main GPU1: AMD driver 20.4.2
2021.08.04:19:05:15.699: main GPU1: Created ADL monitor for adapter 32; overdrive version: 7 (7)
2021.08.04:19:05:15.699: main GPU1: using AMD driver ver 20.4.2
2021.08.04:19:05:15.700: main Matched GPU2 to ADL adapter index 0 (method 1)
2021.08.04:19:05:15.728: main GPU2: AMD driver 20.4.2
2021.08.04:19:05:15.728: main GPU2: Created ADL monitor for adapter 0; overdrive version: 7 (7)
2021.08.04:19:05:15.728: main GPU2: using AMD driver ver 20.4.2
2021.08.04:19:05:15.728: main Matched GPU3 to ADL adapter index 16 (method 1)
2021.08.04:19:05:15.759: main GPU3: AMD driver 20.4.2
2021.08.04:19:05:15.759: main GPU3: Created ADL monitor for adapter 16; overdrive version: 7 (7)
2021.08.04:19:05:15.759: main GPU3: using AMD driver ver 20.4.2
2021.08.04:19:05:15.759: main Matched GPU4 to ADL adapter index 24 (method 1)
2021.08.04:19:05:15.789: main GPU4: AMD driver 20.4.2
2021.08.04:19:05:15.789: main GPU4: Created ADL monitor for adapter 24; overdrive version: 7 (7)
2021.08.04:19:05:15.789: main GPU4: using AMD driver ver 20.4.2
2021.08.04:19:05:15.789: main Matched GPU5 to ADL adapter index 8 (method 1)
2021.08.04:19:05:15.819: main GPU5: AMD driver 20.4.2
2021.08.04:19:05:15.819: main GPU5: Created ADL monitor for adapter 8; overdrive version: 7 (7)
2021.08.04:19:05:15.820: main GPU5: using AMD driver ver 20.4.2
2021.08.04:19:05:15.820: main Matched GPU6 to ADL adapter index 40 (method 1)
2021.08.04:19:05:15.849: main GPU6: AMD driver 20.4.2
2021.08.04:19:05:15.849: main GPU6: Created ADL monitor for adapter 40; overdrive version: 7 (7)
2021.08.04:19:05:15.849: main GPU6: using AMD driver ver 20.4.2
2021.08.04:19:05:15.913: hwmc GPU1: set VMEM timing level to 1
2021.08.04:19:05:16.023: hwmc GPU2: set VMEM timing level to 1
2021.08.04:19:05:16.129: hwmc GPU3: set VMEM timing level to 1
2021.08.04:19:05:16.236: hwmc GPU4: set VMEM timing level to 1
2021.08.04:19:05:16.342: hwmc GPU5: set VMEM timing level to 1
2021.08.04:19:05:16.448: hwmc GPU6: set VMEM timing level to 1
2021.08.04:19:05:16.599: hwmc GPU1: switching to alt fan control mode
2021.08.04:19:05:16.600: hwmc GPU1: set auto fan: 54C target temp (min fan 52, max fan 58)
2021.08.04:19:05:16.606: hwmc GPU1: set GPU clocks to 1170 MHz (Vddc 830 mV)
2021.08.04:19:05:16.633: hwmc GPU1: set VMEM clocks to 2010 MHz (Vddc 840 mV)
2021.08.04:19:05:16.633: hwmc GPU2: switching to alt fan control mode
2021.08.04:19:05:16.634: hwmc GPU2: set auto fan: 54C target temp (min fan 52, max fan 58)
2021.08.04:19:05:16.640: hwmc GPU2: set GPU clocks to 1170 MHz (Vddc 830 mV)
2021.08.04:19:05:16.647: hwmc GPU2: set VMEM clocks to 2040 MHz (Vddc 830 mV)
2021.08.04:19:05:16.648: hwmc GPU3: switching to alt fan control mode
2021.08.04:19:05:16.648: hwmc GPU3: set auto fan: 54C target temp (min fan 52, max fan 58)
2021.08.04:19:05:16.654: hwmc GPU3: set GPU clocks to 1170 MHz (Vddc 830 mV)
2021.08.04:19:05:16.659: hwmc GPU3: set VMEM clocks to 2020 MHz (Vddc 830 mV)
2021.08.04:19:05:16.661: hwmc GPU4: switching to alt fan control mode
2021.08.04:19:05:16.662: hwmc GPU4: set auto fan: 54C target temp (min fan 52, max fan 58)
2021.08.04:19:05:16.670: hwmc GPU4: set GPU clocks to 1170 MHz (Vddc 830 mV)
2021.08.04:19:05:16.675: hwmc GPU4: set VMEM clocks to 2040 MHz (Vddc 830 mV)
2021.08.04:19:05:16.676: hwmc GPU5: switching to alt fan control mode
2021.08.04:19:05:16.677: hwmc GPU5: set auto fan: 54C target temp (min fan 52, max fan 58)
2021.08.04:19:05:16.688: hwmc GPU5: set GPU clocks to 1170 MHz (Vddc 830 mV)
2021.08.04:19:05:16.694: hwmc GPU5: set VMEM clocks to 2040 MHz (Vddc 830 mV)
2021.08.04:19:05:16.694: hwmc GPU6: switching to alt fan control mode
2021.08.04:19:05:16.695: hwmc GPU6: set auto fan: 54C target temp (min fan 52, max fan 58)
2021.08.04:19:05:16.703: hwmc GPU6: set GPU clocks to 1170 MHz (Vddc 830 mV)
2021.08.04:19:05:16.708: hwmc GPU6: set VMEM clocks to 2040 MHz (Vddc 830 mV)
2021.08.04:19:05:16.759: wdog Starting watchdog thread
2021.08.04:19:05:16.759: main Eth: Connecting to ethash pool asia1.ethermine.org:4444 (proto: EthProxy)
2021.08.04:19:05:16.761: main GPU1: 53C 17% 33W, GPU2: 49C 17% 32W, GPU3: 50C 17% 33W, GPU4: 49C 17% 32W, GPU5: 51C 17% 33W, GPU6: 53C 17% 32W
GPUs power: 193.6 W
2021.08.04:19:05:16.823: eths Eth: Connected to ethash pool asia1.ethermine.org:4444 (172.65.231.156)
2021.08.04:19:05:16.823: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0x67503b7b1833688167eec36fee017bf3cf6e1c79.bo"]}

2021.08.04:19:05:16.896: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2021.08.04:19:05:16.896: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2021.08.04:19:05:16.963: main Listening for CDM remote manager at port 3333 in read-only mode
2021.08.04:19:05:16.964: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xd35ad1ac3a8d6c52be021ff0788f6e18cb76f3ea6d9163b36ad8c5efcfeff249","0x787fc048d668f524ffd65484f99d9e60a25cfa3e5e8254f111e6b7968f195e9c","0x00000000ffff00000000ffff00000000ffff00000000ffff00000000ffff0000","0xc5bb4b"]}
2021.08.04:19:05:16.964: eths Eth: New job #d35ad1ac from asia1.ethermine.org:4444; diff: 4295MH
2021.08.04:19:05:16.965: GPU1 GPU1: Starting up... (0)
2021.08.04:19:05:16.965: GPU1 GPU1: Generating ethash light cache for epoch #431
2021.08.04:19:05:16.967: GPU2 GPU2: Starting up... (0)
2021.08.04:19:05:16.969: GPU3 GPU3: Starting up... (0)
2021.08.04:19:05:16.971: GPU4 GPU4: Starting up... (0)
2021.08.04:19:05:16.974: GPU5 GPU5: Starting up... (0)
2021.08.04:19:05:16.976: GPU6 GPU6: Starting up... (0)
2021.08.04:19:05:18.374: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xae9ee9fadfbbbe9ecbfd293fb52dce24bff17a37d3640b710c138cdb0101f143","0x787fc048d668f524ffd65484f99d9e60a25cfa3e5e8254f111e6b7968f195e9c","0x00000000ffff00000000ffff00000000ffff00000000ffff00000000ffff0000","0xc5bb4b"]}
2021.08.04:19:05:18.374: eths Eth: New job #ae9ee9fa from asia1.ethermine.org:4444; diff: 4295MH
2021.08.04:19:05:21.326: GPU1 Light cache generated in 4.4 s (16.0 MB/s)
2021.08.04:19:05:21.677: GPU1 The option -clKernel 3 is ignored for GPU1
2021.08.04:19:05:21.796: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2021.08.04:19:05:21.796: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
2021.08.04:19:05:22.237: GPU1 GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
2021.08.04:19:05:22.237: GPU1 GPU1: Allocating DAG (4.38 GB); good for epoch up to #433
2021.08.04:19:05:22.319: GPU1 GPU1: Generating DAG for epoch #431
2021.08.04:19:05:22.635: GPU2 The option -clKernel 3 is ignored for GPU2
2021.08.04:19:05:23.188: GPU2 GPU2: Free VRAM: 7.948 GB; used: 0.052 GB
2021.08.04:19:05:23.188: GPU2 GPU2: Allocating DAG (4.38 GB); good for epoch up to #433
2021.08.04:19:05:23.250: GPU2 GPU2: Generating DAG for epoch #431
2021.08.04:19:05:23.586: GPU3 The option -clKernel 3 is ignored for GPU3
2021.08.04:19:05:24.138: GPU3 GPU3: Free VRAM: 7.948 GB; used: 0.052 GB
2021.08.04:19:05:24.138: GPU3 GPU3: Allocating DAG (4.38 GB); good for epoch up to #433
2021.08.04:19:05:24.201: GPU3 GPU3: Generating DAG for epoch #431
2021.08.04:19:05:24.248: GPU1 GPU1: DAG  15%
2021.08.04:19:05:24.372: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x6bb4a5dea15afce537ac20b510f4f3bc817a663979e5df9c6728ef647c953a59","0x787fc048d668f524ffd65484f99d9e60a25cfa3e5e8254f111e6b7968f195e9c","0x00000000ffff00000000ffff00000000ffff00000000ffff00000000ffff0000","0xc5bb4b"]}
2021.08.04:19:05:24.372: eths Eth: New job #6bb4a5de from asia1.ethermine.org:4444; diff: 4295MH
2021.08.04:19:05:24.560: GPU4 The option -clKernel 3 is ignored for GPU4
2021.08.04:19:05:25.110: GPU4 GPU4: Free VRAM: 7.948 GB; used: 0.052 GB
2021.08.04:19:05:25.110: GPU4 GPU4: Allocating DAG (4.38 GB); good for epoch up to #433
2021.08.04:19:05:25.174: GPU4 GPU4: Generating DAG for epoch #431
2021.08.04:19:05:25.202: GPU2 GPU2: DAG  15%
2021.08.04:19:05:25.514: GPU5 The option -clKernel 3 is ignored for GPU5
2021.08.04:19:05:25.783: GPU1 GPU1: DAG  30%
2021.08.04:19:05:26.075: GPU5 GPU5: Free VRAM: 7.948 GB; used: 0.052 GB
2021.08.04:19:05:26.075: GPU5 GPU5: Allocating DAG (4.38 GB); good for epoch up to #433
2021.08.04:19:05:26.135: GPU3 GPU3: DAG  15%
2021.08.04:19:05:26.142: GPU5 GPU5: Generating DAG for epoch #431
2021.08.04:19:05:26.477: GPU6 The option -clKernel 3 is ignored for GPU6

UnclWish

sr. member

Activity: 1484

Merit: 253

Quote from: bategojko74 on August 17, 2021, 02:42:33 AM

Quote from: UnclWish on August 16, 2021, 12:41:03 PM

I think that clgreen work only up to some DAG number. Now I mine on DAG #434 (4.48Gb).
And I use latest 21.8.1 driver. Maybe clgreen works only on several set of drivers.

clgreen is incompatible wit clkernel 3. clkernel 3 overrides clgreen.

I tried clgreen with all possible kernels - 1,2,3. Always miner shows that GPU ignores clgreen 1.

bategojko74

member

Activity: 220

Merit: 12

Quote from: speed07 on August 08, 2021, 10:27:28 PM

Quote from: bategojko74 on August 08, 2021, 10:25:32 PM

Quote from: speed07 on August 08, 2021, 04:59:17 AM

Quote from: bategojko74 on August 08, 2021, 02:21:32 AM

Quote from: dazmann on August 07, 2021, 05:59:42 PM

Quote from: dazmann on August 07, 2021, 12:24:07 AM

Quote from: bategojko74 on August 06, 2021, 11:21:38 AM

Quote from: dazmann on August 04, 2021, 12:47:02 PM

Quote from: PhoenixMiner on August 04, 2021, 01:59:24 AM

Implemented new "turbo" kernels (-clkernel 3) for AMD Polaris cards that can work with the current DAG sizes over 4 GB. Note that -clkernel 3 uses double the VRAM and will provide slightly faster hashrate with slightly higher power consumption. You can use the -rvram command-line parameter to specify how much VRAM to be left unused

Please let us know if you have any problems or questions related to PhoenixMiner 5.7b.

Tried the -clkernel 3 on my RX 480 8GB and got lower hashrates than -clkernel 2.
I'm on windows 10 20H2, Radeon Software version 21.6.1
I'm only using the -vmr 25 parameter and -gt 69 as per benchmark suggestion.
Everything else is default.

Your current gt value 69 is not the optimal for -clkernel 3. Put -gt 0 in your settings to find the new best gt value for -clkernel 3. After that you can put -gt NEW_BEST_GT_FOUND_VALUE in your settings.

Thank you very much. I will look into that.

Aaaand nothing changed.

If you have amd rx470/480/570/580 GPUs you will get +0.1mh/s per GPU with -clkernel 3. You will not get increase with Vega, Navi or Nvidia GPUs.

The option -clKernel 3 is ignored for all GPU, when i use -clKernel 3. nitro+ rx570 8g samsung, stock bios.

You are using very old drivers. Update the amd gpu driver.

which version bro? im using 20.4.2

Increase your VRAM to (NUMBER_OF_GPUS+1)*8 GB. If you print the beginning of your log file I will tell you why clkernel 3 is ignored.

bategojko74

member

Activity: 220

Merit: 12

Quote from: UnclWish on August 16, 2021, 12:41:03 PM

I think that clgreen work only up to some DAG number. Now I mine on DAG #434 (4.48Gb).
And I use latest 21.8.1 driver. Maybe clgreen works only on several set of drivers.

clgreen is incompatible wit clkernel 3. clkernel 3 overrides clgreen.

deedeeranged

member

Activity: 325

Merit: 42

Quote from: janding on August 16, 2021, 12:32:45 PM

Quote from: UnclWish on August 16, 2021, 12:05:14 PM

Thanks! Without clgreen speed faster? More power uses?

Actually there is not enough difference between having -clgreen on or off on either power or speed as I can tell.
I have ran it for long periods both ways, no noticeable impact on money or power. But, the -clKernel 3 instead of -clKernel 1
immediately increased my hash rate as I mentioned earlier, not a lot, but I welcome any small improvements.
The AMD cards with Phoenix work unbelievably well. I never have a crash or anything negative. It just runs forever without any intervention.
It's a great miner. Hope you find your issue with the green setting but unless you get different results than I do I'm not sure you will see much gain.
Let me know if you get different results please.

May I be so bold to ask what settings or config,txt you use to start PhoenixMiner for the rx580 (I have a rx580 8gb) also if anyone has some idea for settings to use with a r9 390?

Will be much appreciated.

Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 42. (Read 784857 times)