Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 326. (Read 784965 times)
July 26, 2019, 02:49:42 PM
Thanks for the miner!
July 26, 2019, 03:31:28 AM
md5 and sha checksums match with this bitcointalk forum, I downloaded and checked.
the ETH-ready program with .but files is loaded into github
but it is better to download from this official thread!
the ETH-ready program with .but files is loaded into github
but it is better to download from this official thread!
July 26, 2019, 02:51:00 AM
thank u bro, i read this, i now testing 4.5b and works fine with my rig of 6 rx 580 sapphire nitro... thanks
July 26, 2019, 02:46:56 AM
July 26, 2019, 02:20:41 AM
July 25, 2019, 04:35:58 PM
@PhoenixMiner, you said:
So... Are all 4+ Gb AMD cards (even Radeon VII) become usless, when we reach epoch 378? If AMD didn't fix drivers...
Please, correct me if I wrong.
...
- Increased the maximum supported DAG epoch to 450. Note that AMD drivers don't allow buffers larger than 4 GB so the biggest possible DAG epoch with current AMD drivers is 378
So... Are all 4+ Gb AMD cards (even Radeon VII) become usless, when we reach epoch 378? If AMD didn't fix drivers...
Please, correct me if I wrong.
No, 4+ Gb AMD cards will survive epoch 378+. PM already uses 2 buffers with 2 copies of the DAG = 6.4GB when you pass parameter -clkernel 3. So there isn't any principle problem the second buffer to contain the second half of the dag instead of its copy.
July 25, 2019, 01:36:42 PM
AMD Driver 19.7.3 - Unknown OpenCL version. ((((
AMD quick changed their OpenCL driver... It's too bad, that miner depends on known OpenCL versions...
Phoenix, please, update miner for support new drivers next version... AMD quick changed their OpenCL driver... It's too bad, that miner depends on known OpenCL versions...
July 25, 2019, 01:35:50 PM
@PhoenixMiner, you said:
So... Are all 4+ Gb AMD cards (even Radeon VII) become usless, when we reach epoch 378? If AMD didn't fix drivers...
Please, correct me if I wrong.
No, 4Gb cards became useless more early than 4Gb+. Cause of system use some vmemory... On 4Gb cards not all 4Gb free. ...
- Increased the maximum supported DAG epoch to 450. Note that AMD drivers don't allow buffers larger than 4 GB so the biggest possible DAG epoch with current AMD drivers is 378
So... Are all 4+ Gb AMD cards (even Radeon VII) become usless, when we reach epoch 378? If AMD didn't fix drivers...
Please, correct me if I wrong.
July 25, 2019, 01:34:20 PM
AMD Driver 19.7.3 - Unknown OpenCL version. ((((
AMD quick changed their OpenCL driver... It's too bad, that miner depends on known OpenCL versions...
AMD quick changed their OpenCL driver... It's too bad, that miner depends on known OpenCL versions...
July 25, 2019, 11:57:16 AM
@PhoenixMiner, you said:
So... Are all 4+ Gb AMD cards (even Radeon VII) become usless, when we reach epoch 378? If AMD didn't fix drivers...
Please, correct me if I wrong.
...
- Increased the maximum supported DAG epoch to 450. Note that AMD drivers don't allow buffers larger than 4 GB so the biggest possible DAG epoch with current AMD drivers is 378
So... Are all 4+ Gb AMD cards (even Radeon VII) become usless, when we reach epoch 378? If AMD didn't fix drivers...
Please, correct me if I wrong.
July 24, 2019, 10:59:53 PM
hello, i just found a big bug on your miner
when a mining rig for any reason looses the internet conection about 10 min to an hour, the system should make some switches the pool, because the miner, has not internet conection, it thinks that the mining pool is down, and changes to the next configuated pool in the bat file, or in my case that i am using ETHos the local.conf configuration file, for example
i am minig etc on the server ssl://us1-etc.ethermine.org:5555 and the failover is ssl://eu1-etc.ethermine.org:5555
So, the miner looses the internet conection on the main pool it thinks that the first server is down and switches to the second, and backwards, over and over and over again, and at the end, the miner switches to the DevFee pool, and stays there, when the internet conection is restablished, the miner mines locked in the DevFee account, you can see in the ETHos panel the rigs are running normally, but in the minig pools, all rigs using Phoenixminer are down, and it has happend to me in the last few months that i am using the miner, that somethimes, my internet conection fails after midnight and when i wake up in the morning all my rigs apparently are working fine according to the ethos panel, but on the pool side, they're down several hours ago, i found a solution on my side, and it has worked for me, but i'd love that the dev would contact me and see what we can do, from my part i disabled the devfee mining by code on the miner, but it would be great if the dev could repair the bug and mine again paying the devfee to @phoenixminer that he deserves for an excelent miner that he has created
when a mining rig for any reason looses the internet conection about 10 min to an hour, the system should make some switches the pool, because the miner, has not internet conection, it thinks that the mining pool is down, and changes to the next configuated pool in the bat file, or in my case that i am using ETHos the local.conf configuration file, for example
i am minig etc on the server ssl://us1-etc.ethermine.org:5555 and the failover is ssl://eu1-etc.ethermine.org:5555
So, the miner looses the internet conection on the main pool it thinks that the first server is down and switches to the second, and backwards, over and over and over again, and at the end, the miner switches to the DevFee pool, and stays there, when the internet conection is restablished, the miner mines locked in the DevFee account, you can see in the ETHos panel the rigs are running normally, but in the minig pools, all rigs using Phoenixminer are down, and it has happend to me in the last few months that i am using the miner, that somethimes, my internet conection fails after midnight and when i wake up in the morning all my rigs apparently are working fine according to the ethos panel, but on the pool side, they're down several hours ago, i found a solution on my side, and it has worked for me, but i'd love that the dev would contact me and see what we can do, from my part i disabled the devfee mining by code on the miner, but it would be great if the dev could repair the bug and mine again paying the devfee to @phoenixminer that he deserves for an excelent miner that he has created
July 24, 2019, 08:31:37 AM
thanks for your great work @phoenixminer
would u mind to give an example on how to use the new options?
thanks and regards
would u mind to give an example on how to use the new options?
thanks and regards
- Added hardware control and monitoring (clocks, voltages, fans, etc.) for Nvidia cards under Windows. Note that you should specify the clocks for Nvidia cards relative to the defaults (e.g. -mclock +400 instead of -mclock 4400)
- Added hardware control and monitoring (clocks, voltages, fans, etc.) for Radeon VII cards (Windows only)
- Added advanced hardware monitoring (specify -hstats 2 to activate it). It will show you the GPU core and memory clocks, voltages, and P-states (if supported)
- Added GPU power consumption if the driver reports it. You can also specify the idle power (-pidle), PSU/GPU efficiency (-ppf) and electricity cost (-prate) and have the miner calculate the daily electricity costs for you. If you are using third-party mining software which doesn't expect the power consumption figures in the miner's log, you can disable it by specifying -hstats 0
- Added new parameter -mt to set the memory timings on AMD cards. -mt 0 is the default, which uses the VBIOS memory timings. -mt 1, and -mt 2 use predefined memory timings that are independent from the VBIOS timings. This option is useful for mining with RX580/570/560/480/470/460 cards without modding the VBIOS. This works only on Windows and with relatively recent drivers (from the last 6-8 months)
- The bench mode now works for dual mining and ProgPOW. The algorithm is determined by the -coin and -dcoin parameters. E.g. -bench 10 -coin bci will bench the BCI ProgPOW, and -bench 10 -dcoin blake2s will bench the dual mining
July 24, 2019, 12:57:18 AM
i use rx 570 with driver "Adrenalin Edition" 18.5.1.
We have retested RX570 under both older and latest AMD Windows drivers and there is no performance decrease between 4.2c and 4.5b. Please check if your cards are throttling (use -hstats 2 as explained in our previous post) because 4.5b enforces the -tt, and -fanmax parameters more strictly than 4.2c. Also, don't use -mt if you have modded your cards or are using other means to change the memory timings.@PhoenixMiner
Are you planning to add memory straps/timings for Nvidia cards?
I don't like claymore (compared to yours)
but was forced to switch because of nvidia memory timings (gives a lot more of hash rate)
(which is a big advantage)
We are considering this for the next release but there are some concerns with long-term stability and (probably not very likely) possible DRAM overheating with these aggressive timings.Are you planning to add memory straps/timings for Nvidia cards?
I don't like claymore (compared to yours)
but was forced to switch because of nvidia memory timings (gives a lot more of hash rate)
(which is a big advantage)
I have the same hashrate, which is on 4.2c, which is on 4.5b, but on drivers version 18.6.1
On version 19.7.1, the speed is 20-30 hashes lower
If you are getting lower hashrate from 4.5b on drivers ver. 19.7.1, you definitely need to rerun auto-tuning (press z in the miner console or run the miner without the -gt option). 4.2c doesn't support the most optimized kernels on drivers 19.7.1, and its optimal -gt values are very different than these of the optimized kernels.On version 19.7.1, the speed is 20-30 hashes lower
I keep seeing everyone mentioning 4.5b, yet I don't see the link on this forum. I am going
to assume it is not a legit release?
It is a beta version but it is legit. We don't put it in the first post to keep it clear that it is not the stable release yet. You can find the relevant post here: https://bitcointalksearch.org/topic/m.51874428to assume it is not a legit release?
@phoenix correct me if I'm wrong but isn't 5700 already limited with memory bandwidth and theoreticall speed for them is 37mhs for non xt and 50mhs for 5700xt?
No, both 5700 and 5700 XT could do about 50 MH/s without the TLB entry count/page size problem. That much is certain from our tests. Why exactly there is such limitation is just a wild speculation on our part as well as when (or if) it will be removed....
With the current no-so-great mining profitability, they really didn't have to do this but it's absolutely their choice, and with the current prices of Polaris, it is still one of the best cards for ethash mining. If the Navi cards weren't locked down, they would achieve hashrate in the 50 MH/s ballpark. We are still working on some kind of workaround but it doesn't look good at this moment.
With the current no-so-great mining profitability, they really didn't have to do this but it's absolutely their choice, and with the current prices of Polaris, it is still one of the best cards for ethash mining. If the Navi cards weren't locked down, they would achieve hashrate in the 50 MH/s ballpark. We are still working on some kind of workaround but it doesn't look good at this moment.
All those limitations can be worked around in linux easily if thats the only issue preventing ethash from working properly.
@PhoenixMiner,
Need some help here to fix this issue I'm having... See below
Windows 10
Awesome Miner used to run / control the miner.
Latest drivers for Nvidia installed
RTX 2080 FE << Will not mine ... see log below for the NVRTC error.
EVGA 1070Ti << Mines fine when selected on it's own (GPUS 2 option).
Looking forward to some info on what's wrong here.
Thank you for reporting this! Thanks to the detailed info and the log, we were able to reproduce the problem and it will be fixed in the 4.5c, which will be ready in a few days.Need some help here to fix this issue I'm having... See below
Windows 10
Awesome Miner used to run / control the miner.
Latest drivers for Nvidia installed
RTX 2080 FE << Will not mine ... see log below for the NVRTC error.
EVGA 1070Ti << Mines fine when selected on it's own (GPUS 2 option).
Looking forward to some info on what's wrong here.
Code:
...
July 23, 2019, 10:45:10 AM
@PhoenixMiner,
Need some help here to fix this issue I'm having... See below
Windows 10
Awesome Miner used to run / control the miner.
Latest drivers for Nvidia installed
RTX 2080 FE << Will not mine ... see log below for the NVRTC error.
EVGA 1070Ti << Mines fine when selected on it's own (GPUS 2 option).
Looking forward to some info on what's wrong here.
Need some help here to fix this issue I'm having... See below
Windows 10
Awesome Miner used to run / control the miner.
Latest drivers for Nvidia installed
RTX 2080 FE << Will not mine ... see log below for the NVRTC error.
EVGA 1070Ti << Mines fine when selected on it's own (GPUS 2 option).
Looking forward to some info on what's wrong here.
Code:
2019.07.23:11:34:31.404: main Phoenix Miner 4.5b Windows/msvc - Release build
2019.07.23:11:34:31.404: main Cmd line: -mi 10 -nvidia -gpus 1 -mi 6 -cdm 0 -wdog 1 -rmode 0 -cdmport 4033
2019.07.23:11:34:31.567: main CUDA version: 10.0, CUDA runtime: 8.0
2019.07.23:11:34:31.568: main Available GPUs for mining:
2019.07.23:11:34:31.568: main GPU1: GeForce RTX 2080 (pcie 1), CUDA cap. 7.5, 8 GB VRAM, 46 CUs
2019.07.23:11:34:31.574: main NVML library initialized
2019.07.23:11:34:31.592: main Nvidia driver version: 431.36
2019.07.23:11:34:31.823: main Eth: Loading pools from epools.txt
2019.07.23:11:34:31.823: main PP: the pool list contains 1 pool (0 from command-line)
2019.07.23:11:34:31.823: main PP: primary pool: progpow.mine.zergpool.com:3200
2019.07.23:11:34:31.823: main Starting GPU mining
2019.07.23:11:34:31.823: wdog Starting watchdog thread
2019.07.23:11:34:31.824: main PP: Connecting to progpow pool progpow.mine.zergpool.com:3200 (proto: Stratum)
2019.07.23:11:34:32.025: main GPU1: 26C 41% 2W
GPUs power: 2.1 W
2019.07.23:11:34:32.090: eths PP: Connected to progpow pool progpow.mine.zergpool.com:3200 (103.77.224.73)
2019.07.23:11:34:32.090: eths PP: Send: {"id":1,"method":"mining.subscribe","params":[]}
2019.07.23:11:34:32.305: eths PP: Received: {"id":1,"result":[null,"fbd04e0400008820"],"error":null}
2019.07.23:11:34:32.305: eths PP: Subscribed to progpow pool
2019.07.23:11:34:32.306: eths PP: Send: {"id":2,"method":"mining.extranonce.subscribe","params":[]}
{"id":3,"method":"mining.authorize","params":["DELETED","c=BTC"]}
2019.07.23:11:34:32.519: eths PP: Received: {"id":null,"method":"mining.set_target","params":["00000016c16aaaaaaaab00000000000000000000000000000000000000000000"]}
2019.07.23:11:34:32.774: eths PP: Received: {"id":2,"result":false,"error":[20,"Not supported.",null]}
2019.07.23:11:34:32.774: eths PP: Received: {"id":3,"result":true,"error":null}
2019.07.23:11:34:32.774: eths PP: Worker DELETED authorized
2019.07.23:11:34:32.774: eths PP: Received: {"id":null,"method":"mining.notify","params":["0000000000000000000000000000000000000000000000000000000000014160","aa64f03f26bdac3e1482f337f8ee8754d4b03dc3f44fa9897fe5ec6021278f4d","1c43434ae099df696d682e68d0611cc9b9eda636466134d6e857c86c4bd6ed28","00000016c16aaaaaaaab00000000000000000000000000000000000000000000",false]}
2019.07.23:11:34:32.774: eths PP: New job #aa64f03f from progpow.mine.zergpool.com:3200; diff: 188MH
2019.07.23:11:34:32.774: GPU1 GPU1: Starting up... (0)
2019.07.23:11:34:32.774: GPU1 GPU1: Generating ethash light cache for epoch #17
2019.07.23:11:34:33.542: GPU1 Light cache generated in 0.8 s (23.6 MB/s)
2019.07.23:11:34:34.824: GPU1 GPU1: ProgPOW seed set to 17
2019.07.23:11:34:34.827: GPU1 NVRTC error in CudaProgram.cu:276 : NVRTC_ERROR_INVALID_OPTION (5)
2019.07.23:11:34:34.827: GPU1 GPU1 initMiner error: NVRTC_ERROR_INVALID_OPTION
July 23, 2019, 09:48:04 AM
Go away, troll. We have kernels for Navi - RDNA isn't that different from GCN. The problem is that the GPUs are "locked down" for ethash mining by either limiting the number of TLB entries, or lowering the page size. This may be unintentional but we suspect that it is by design, probably to prevent miners from buying out all Navi GPUs and leaving the gamers with high prices and low availability. RX5700 is the first very competitive AMD gaming GPU since Polaris, so they probably want to win some market share as far as gaming market goes. We hope that this is not hardware limitation and a future driver will remove it but only time will tell.
With the current no-so-great mining profitability, they really didn't have to do this but it's absolutely their choice, and with the current prices of Polaris, it is still one of the best cards for ethash mining. If the Navi cards weren't locked down, they would achieve hashrate in the 50 MH/s ballpark. We are still working on some kind of workaround but it doesn't look good at this moment.
All those limitations can be worked around in linux easily if thats the only issue preventing ethash from working properly.
July 22, 2019, 08:50:53 PM
Is 4.2c crashing for anyone else, it just started yesterday.
July 22, 2019, 01:04:27 PM
I keep seeing everyone mentioning 4.5b, yet I don't see the link on this forum. I am going
to assume it is not a legit release?
to assume it is not a legit release?
It is legit if the post is from the thread starter.
Right.. Missed that.. Saw it now when paging back. Checked the first post where updates normally get posted.
July 22, 2019, 09:28:35 AM
In the 4.5b version of the program, the hashrate is lower than in the 4.2c
I have the same hashrate, which is on 4.2c, which is on 4.5b, but on drivers version 18.6.1On version 19.7.1, the speed is 20-30 hashes lower
On so big driver difference I recommend to make new autotune -gt parameter... Maybe you recieve 20-30 hashes more...
July 22, 2019, 08:26:44 AM
@phoenix correct me if I'm wrong but isn't 5700 already limited with memory bandwidth and theoreticall speed for them is 37mhs for non xt and 50mhs for 5700xt?
July 22, 2019, 06:41:42 AM
I keep seeing everyone mentioning 4.5b, yet I don't see the link on this forum. I am going
to assume it is not a legit release?
to assume it is not a legit release?
It is legit if the post is from the thread starter.
Jump to: