Bitcoin Forum
December 04, 2022, 12:07:32 PM *
News: Bitcointalk Community Awards
 
   Home   Help Search Login Register More  
Pages: « 1 ... 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 [178] 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 ... 503 »
  Print  
Author Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)  (Read 775965 times)
UnclWish
Sr. Member
****
Offline Offline

Activity: 1484
Merit: 253


View Profile
July 29, 2019, 02:41:27 PM
Last edit: July 29, 2019, 02:52:11 PM by UnclWish
 #3541

I get the same speed on any drivers allready about 2 years.
On phoenix I have a bit more speed than Claymore. If I use double kernels (2x more vram needed) I got additional 200-300 kH.
Phoenix allways faster Claymore with the same core and memory clocks even on usual kernels. If you get lower speed on Phoenix, you forget to find optimal -gt parameter values for your cards.

With use of AMD Memory Tweak Tool it's possible to get additional 500-1000 kH of speed.
One of my RX 580 8Gb cards - Sapphire with hynix MJR memory gives on Claymore 33,5-33,7MH/s with -REF 90 on AMD Memory Tweak tool. And 34,2 MH/s on Phoenix with double kernels. About 34MH/s with usual optimized kernels.

Just tried ref 90 on 4gb hynix Sapphire got a small bump to 32,6

guess 4gb cards cant go more than that  
I forgot - I use vbios with flashed ETH optimized timings...

Just tried - set REF to 5 (default) - 32,9MH, REF 90 - 34,2MH Smiley
Speed didn't change immediately, just need 10-20 seconds...
1670155652
Hero Member
*
Offline Offline

Posts: 1670155652

View Profile Personal Message (Offline)

Ignore
1670155652
Reply with quote  #2

1670155652
Report to moderator
1670155652
Hero Member
*
Offline Offline

Posts: 1670155652

View Profile Personal Message (Offline)

Ignore
1670155652
Reply with quote  #2

1670155652
Report to moderator
1670155652
Hero Member
*
Offline Offline

Posts: 1670155652

View Profile Personal Message (Offline)

Ignore
1670155652
Reply with quote  #2

1670155652
Report to moderator
Even in the event that an attacker gains more than 50% of the network's computational power, only transactions sent by the attacker could be reversed or double-spent. The network would not be destroyed.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1670155652
Hero Member
*
Offline Offline

Posts: 1670155652

View Profile Personal Message (Offline)

Ignore
1670155652
Reply with quote  #2

1670155652
Report to moderator
1670155652
Hero Member
*
Offline Offline

Posts: 1670155652

View Profile Personal Message (Offline)

Ignore
1670155652
Reply with quote  #2

1670155652
Report to moderator
Paullus
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile WWW
July 29, 2019, 05:39:46 PM
 #3542

I get the same speed on any drivers allready about 2 years.
On phoenix I have a bit more speed than Claymore. If I use double kernels (2x more vram needed) I got additional 200-300 kH.
Phoenix allways faster Claymore with the same core and memory clocks even on usual kernels. If you get lower speed on Phoenix, you forget to find optimal -gt parameter values for your cards.

With use of AMD Memory Tweak Tool it's possible to get additional 500-1000 kH of speed.
One of my RX 580 8Gb cards - Sapphire with hynix MJR memory gives on Claymore 33,5-33,7MH/s with -REF 90 on AMD Memory Tweak tool. And 34,2 MH/s on Phoenix with double kernels. About 34MH/s with usual optimized kernels.

Just tried ref 90 on 4gb hynix Sapphire got a small bump to 32,6

guess 4gb cards cant go more than that  
I forgot - I use vbios with flashed ETH optimized timings...

Just tried - set REF to 5 (default) - 32,9MH, REF 90 - 34,2MH Smiley
Speed didn't change immediately, just need 10-20 seconds...
What kind of timings? Can you publish here?
Lunga Chung
Member
**
Offline Offline

Activity: 278
Merit: 23


View Profile
July 29, 2019, 06:04:43 PM
 #3543

Just tried - set REF to 5 (default) - 32,9MH, REF 90 - 34,2MH Smiley
Speed didn't change immediately, just need 10-20 seconds...

good timings Smiley

Just obtained couple of nitro+ with 4gb trying to get the sweet spot with --REF value, looks like 90 is a  good startso we will see...wonder if same goes for samsung memory

P.S. rx570 doesn't like --REF 90 Cheesy
justoiurii
Newbie
*
Offline Offline

Activity: 103
Merit: 0


View Profile
July 29, 2019, 06:38:14 PM
 #3544

Dear PhoenixMiner,
I can not use -mt option. How to fix it?
Phoenix wrotes: "This works only on Windows and with relatively recent drivers (from the last 6-8 months)"
Your 18.5.1 drivers is too old - allready more than year past...
Thank you very much. So what best driver for rx 570?
I use latest 19.7.3... But I have RX 580 8Gb. For 4Gb cards better driver that uses less memory...
If you have Windows 10 1903 use at least 19.5.1 driver. If not try 19.4.3.

... and what hashrate do you have on 19.7.3? On bc drivers for my RX480 8Gb I've got 31,5 Mh/sec. With Claymore - 32,5 Mh, but more power from the wall.
I get the same speed on any drivers allready about 2 years.
On phoenix I have a bit more speed than Claymore. If I use double kernels (2x more vram needed) I got additional 200-300 kH.
Phoenix allways faster Claymore with the same core and memory clocks even on usual kernels. If you get lower speed on Phoenix, you forget to find optimal -gt parameter values for your cards.

With use of AMD Memory Tweak Tool it's possible to get additional 500-1000 kH of speed.
One of my RX 580 8Gb cards - Sapphire with hynix MJR memory gives on Claymore 33,5-33,7MH/s with -REF 90 on AMD Memory Tweak tool. And 34,2 MH/s on Phoenix with double kernels. About 34MH/s with usual optimized kernels.

Thanks a lot, friend) Could you share your additional parameters in .bat and lock values? Thanks in advance)
UnclWish
Sr. Member
****
Offline Offline

Activity: 1484
Merit: 253


View Profile
July 29, 2019, 09:33:48 PM
 #3545

What kind of timings? Can you publish here?
Sorry, but I can't do that. They're not my...
UnclWish
Sr. Member
****
Offline Offline

Activity: 1484
Merit: 253


View Profile
July 29, 2019, 09:37:25 PM
 #3546

Thanks a lot, friend) Could you share your additional parameters in .bat and lock values? Thanks in advance)
I can share my .bat. But what is "lock" values?

PhoenixMiner.exe -pool pool -wal wal -pass x -worker w1 -stales 0 -cclock 1235 -cvddc 856 -mclock 2250 -mvddc 800 -gt 36 -mi 14 -log 0 -amd -tstop 75 -tstart 72 -clKernel 3 -clNew 1 -leaveoc

It's for Sapphire RX 580 8 Gb SE with hynix MJR memory.
-clKernel 3 - is for double kernels. Not for 4Gb cards...

P.S. -gt parameter is individual for each card. It depends on clocks and timings. Not depend on -REF. On -ref 5 and -ref 50 best -gt parameter will be the same. Best way to find optimal -gt value is to use autotune by "z" key during mining. It can last 5-10 minutes to auto find best value. Just be patient. When value will be found you can see it in stats by "s" key and add it in .bat file.
justoiurii
Newbie
*
Offline Offline

Activity: 103
Merit: 0


View Profile
July 30, 2019, 07:02:20 AM
 #3547

Thanks a lot, friend) Could you share your additional parameters in .bat and lock values? Thanks in advance)
I can share my .bat. But what is "lock" values?

PhoenixMiner.exe -pool pool -wal wal -pass x -worker w1 -stales 0 -cclock 1235 -cvddc 856 -mclock 2250 -mvddc 800 -gt 36 -mi 14 -log 0 -amd -tstop 75 -tstart 72 -clKernel 3 -clNew 1 -leaveoc

It's for Sapphire RX 580 8 Gb SE with hynix MJR memory.
-clKernel 3 - is for double kernels. Not for 4Gb cards...

P.S. -gt parameter is individual for each card. It depends on clocks and timings. Not depend on -REF. On -ref 5 and -ref 50 best -gt parameter will be the same. Best way to find optimal -gt value is to use autotune by "z" key during mining. It can last 5-10 minutes to auto find best value. Just be patient. When value will be found you can see it in stats by "s" key and add it in .bat file.

Thanks again. You helped to rise to 32,5 Mh/sec
UnclWish
Sr. Member
****
Offline Offline

Activity: 1484
Merit: 253


View Profile
July 30, 2019, 01:35:31 PM
Last edit: July 30, 2019, 03:27:29 PM by UnclWish
 #3548

AMD released 19.7.4 driver... In evening I will try them...

EDIT: Thank heaven! In 19.7.4 AMD didn't touched OpenCL. Miner shows 19.7.3...
karim_hassan777
Newbie
*
Offline Offline

Activity: 58
Merit: 0


View Profile
July 30, 2019, 04:41:13 PM
 #3549

AMD released 19.7.4 driver... In evening I will try them...

EDIT: Thank heaven! In 19.7.4 AMD didn't touched OpenCL. Miner shows 19.7.3...
whait is the importance for that ?
PhoenixMiner (OP)
Full Member
***
Offline Offline

Activity: 357
Merit: 101


View Profile
July 31, 2019, 04:49:39 AM
 #3550

PhoenixMiner 4.5c is the new stable release. You can find the download link and other information in the first post of this thread. If you have already downloaded and installed it, there is no need to do this again - there is no change from 4.5c that was published as a beta version.
Divinity666
Jr. Member
*
Offline Offline

Activity: 300
Merit: 2


View Profile
July 31, 2019, 06:38:35 AM
 #3551

Why no timings for nvidia?((((
jeca
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
July 31, 2019, 08:57:15 AM
 #3552

Hi, Phoenix!
For your miner to be perfect, all that remains is to implement the option to automatically increment tREF while maintaining clgreen. I don't know if it's possible, but I'm looking forward to it. Hugs!
UnclWish
Sr. Member
****
Offline Offline

Activity: 1484
Merit: 253


View Profile
July 31, 2019, 08:58:00 AM
 #3553

AMD released 19.7.4 driver... In evening I will try them...

EDIT: Thank heaven! In 19.7.4 AMD didn't touched OpenCL. Miner shows 19.7.3...
whait is the importance for that ?
Importance is that we can update driver up to 19.7.4 and normal use Phoenix miner 4.5c.
mariano_quilmes
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
July 31, 2019, 01:14:25 PM
 #3554

Hello, can I ask if I´m correct? When PM shows Shares: x/x/x, it is showing Shares: Accepted / Stale / Rejected?

Regards.

Mariano.
YaStaer
Member
**
Offline Offline

Activity: 137
Merit: 10


View Profile
July 31, 2019, 02:14:54 PM
 #3555

Hello, can I ask if I´m correct? When PM shows Shares: x/x/x, it is showing Shares: Accepted / Stale / Rejected?

Regards.

Mariano.

Yes
anbe2305
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
July 31, 2019, 08:06:06 PM
 #3556

Mr. Phoenix...how can i set the new Phoenix 4.5c miner with Nvidia Inspector to run P0 mode, when im using it is reseting my settings made by nvidia inspector and lowers the core to -200 and memory to -1000 ( it stays in P0 mode) but the hashrate drops from 31 MHS to 24 MHS. Why is this version not working with nvidia inspector like the version 4.2c?
ManDoneKTM
Newbie
*
Offline Offline

Activity: 150
Merit: 0


View Profile
August 01, 2019, 04:21:38 PM
 #3557

i added -mt 1 and -mt 2 and i have the same result on the hashrate ... hmmm
karim_hassan777
Newbie
*
Offline Offline

Activity: 58
Merit: 0


View Profile
August 01, 2019, 07:33:51 PM
 #3558

Any progress with RX 5700 XT cards ?
Mondos
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
August 02, 2019, 12:20:52 PM
 #3559

Phoenix 4.5c + 7x nVidia GTX 1080ti + 1x 1070ti + Windows 10, after few hours, or few minutes I see this error:

Code:
2019.08.02:12:44:36.932: main GPU1: 57C 69% 159W, GPU2: 54C 65% 160W, GPU3: 56C 68% 81W, GPU4: 48C 56% 160W, GPU5: 61C 74% 166W, GPU6: 57C 69% 158W, GPU7: 59C 72% 156W, GPU8: 58C 70% 161W
GPU1: cclock 1582 MHz, cvddc 775 mV, mclock 5737 MHz, p-state P0
GPU2: cclock 1582 MHz, cvddc 787 mV, mclock 5737 MHz, p-state P0
GPU3: cclock 1265 MHz, cvddc 712 mV, mclock 4463 MHz, p-state P0
GPU4: cclock 1607 MHz, cvddc 775 mV, mclock 5740 MHz, p-state P0
GPU5: cclock 1632 MHz, cvddc 725 mV, mclock 5737 MHz, p-state P0
GPU6: cclock 1569 MHz, cvddc 775 mV, mclock 5742 MHz, p-state P0
GPU7: cclock 1607 MHz, cvddc 762 mV, mclock 5740 MHz, p-state P0
GPU8: cclock 1607 MHz, cvddc 750 mV, mclock 5737 MHz, p-state P0
GPUs power: 1200.8 W
2019.08.02:12:44:39.385: main Eth speed: 397.244 MH/s, shares: 29/0/0, time: 0:07
2019.08.02:12:44:39.385: main GPUs: 1: 51.628 MH/s (3) 2: 51.900 MH/s (3) 3: 32.094 MH/s (1) 4: 52.577 MH/s (5) 5: 52.955 MH/s (6) 6: 51.677 MH/s (2) 7: 52.300 MH/s (3) 8: 52.114 MH/s (6)
2019.08.02:12:44:41.557: eths Eth: Received: {"jsonrpc":"2.0","method":"mining.notify","params":["00002d8a","a0275568be8c3f375891da2d277016f3449695d182f095c761d6d1e91a85a40b","270422a4e70bb25f969e3b0290cb04e468c82e9cfae1cdf0df04e8469d426d68",true],"id":null}
2019.08.02:12:44:41.557: eths Eth: New job #270422a4 from pps-etc-eu.adaminers.com:2222; diff: 4999MH
2019.08.02:12:44:41.638: GPU4 Eth: GPU4: ETH share found!
2019.08.02:12:44:41.638: eths Eth: Send: {"id":4,"method":"mining.submit","params": ["0xd3e37d13a40f5884177ef44aab7d45acecbfb4ce.1080ti","00002d8a","30083d8b6320"]}

2019.08.02:12:44:41.638: eths Eth: Share actual difficulty: 27.3 GH (!)
2019.08.02:12:44:41.751: eths Eth: Received: {"result":true,"error":null,"id":4}
2019.08.02:12:44:41.751: eths Eth: Share accepted in 113 ms
2019.08.02:12:44:44.477: main Eth speed: 397.237 MH/s, shares: 30/0/0, time: 0:07
2019.08.02:12:44:44.477: main GPUs: 1: 51.633 MH/s (3) 2: 51.891 MH/s (3) 3: 32.093 MH/s (1) 4: 52.578 MH/s (6) 5: 52.954 MH/s (6) 6: 51.677 MH/s (2) 7: 52.298 MH/s (3) 8: 52.114 MH/s (6)
2019.08.02:12:44:49.576: main Eth speed: 397.226 MH/s, shares: 30/0/0, time: 0:07
2019.08.02:12:44:49.576: main GPUs: 1: 51.629 MH/s (3) 2: 51.901 MH/s (3) 3: 32.093 MH/s (1) 4: 52.578 MH/s (6) 5: 52.938 MH/s (6) 6: 51.677 MH/s (2) 7: 52.298 MH/s (3) 8: 52.112 MH/s (6)
2019.08.02:12:44:51.686: eths Eth: Received: {"jsonrpc":"2.0","method":"mining.notify","params":["00002d8b","a0275568be8c3f375891da2d277016f3449695d182f095c761d6d1e91a85a40b","655b99a27173145991dd9b8973237f1702ade83a429021112b9c72e3d9ab3254",true],"id":null}
2019.08.02:12:44:51.686: eths Eth: New job #655b99a2 from pps-etc-eu.adaminers.com:2222; diff: 4999MH
2019.08.02:12:44:53.838: GPU5 Eth: GPU5: ETH share found!
2019.08.02:12:44:53.838: eths Eth: Send: {"id":4,"method":"mining.submit","params": ["0xd3e37d13a40f5884177ef44aab7d45acecbfb4ce.1080ti","00002d8b","400881f2c67b"]}

2019.08.02:12:44:53.838: eths Eth: Share actual difficulty: 20.6 GH (!)
2019.08.02:12:44:53.951: eths Eth: Received: {"result":true,"error":null,"id":4}
2019.08.02:12:44:53.951: eths Eth: Share accepted in 113 ms
2019.08.02:12:44:54.702: main Eth speed: 397.217 MH/s, shares: 31/0/0, time: 0:07
2019.08.02:12:44:54.702: main GPUs: 1: 51.624 MH/s (3) 2: 51.926 MH/s (3) 3: 32.093 MH/s (1) 4: 52.574 MH/s (6) 5: 52.912 MH/s (7) 6: 51.676 MH/s (2) 7: 52.301 MH/s (3) 8: 52.113 MH/s (6)
2019.08.02:12:44:59.821: main Eth speed: 397.239 MH/s, shares: 31/0/0, time: 0:08
2019.08.02:12:44:59.821: main GPUs: 1: 51.622 MH/s (3) 2: 51.956 MH/s (3) 3: 32.093 MH/s (1) 4: 52.571 MH/s (6) 5: 52.908 MH/s (7) 6: 51.676 MH/s (2) 7: 52.302 MH/s (3) 8: 52.110 MH/s (6)
2019.08.02:12:45:02.043: GPU7 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.071: GPU2 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.071: GPU4 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.071: GPU5 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.102: GPU3 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.102: GPU1 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.110: GPU7 GPU7 search error: unspecified launch failure
2019.08.02:12:45:02.110: GPU1 GPU1 search error: unspecified launch failure
2019.08.02:12:45:02.110: GPU3 GPU3 search error: unspecified launch failure
2019.08.02:12:45:02.110: GPU5 GPU5 search error: unspecified launch failure
2019.08.02:12:45:02.110: GPU2 GPU2 search error: unspecified launch failure
2019.08.02:12:45:02.110: GPU4 GPU4 search error: unspecified launch failure
2019.08.02:12:45:02.118: GPU6 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.118: GPU6 GPU6 search error: unspecified launch failure
2019.08.02:12:45:02.149: GPU8 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.149: GPU8 GPU8 search error: unspecified launch failure
2019.08.02:12:45:02.945: wdog Thread(s) not responding. Restarting.

 ---------- OR -------------

Code:
2019.08.02:12:34:26.269: GPU7 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.269: GPU7 GPU7 initMiner error: unspecified launch failure
2019.08.02:12:34:26.273: GPU1 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.273: GPU1 GPU1 initMiner error: unspecified launch failure
2019.08.02:12:34:26.278: GPU6 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.278: GPU6 GPU6 initMiner error: unspecified launch failure
2019.08.02:12:34:26.311: GPU8 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.311: GPU4 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.311: GPU8 GPU8 initMiner error: unspecified launch failure
2019.08.02:12:34:26.311: GPU4 GPU4 initMiner error: unspecified launch failure
2019.08.02:12:34:26.311: GPU2 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.311: GPU5 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.311: GPU2 GPU2 initMiner error: unspecified launch failure
2019.08.02:12:34:26.311: GPU5 GPU5 initMiner error: unspecified launch failure
2019.08.02:12:34:26.315: GPU3 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.315: GPU3 GPU3 initMiner error: unspecified launch failure
2019.08.02:12:34:26.950: wdog Thread(s) not responding. Restarting.
karim_hassan777
Newbie
*
Offline Offline

Activity: 58
Merit: 0


View Profile
August 02, 2019, 12:49:04 PM
 #3560

Any progress with RX 5700 XT ?
Pages: « 1 ... 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 [178] 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 ... 503 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!