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. |
|
|
|
|
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...
|
|
|
|
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. |
|
|
|
What kind of timings? Can you publish here?
Sorry, but I can't do that. They're not my... |
|
|
|
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  Speed didn't change immediately, just need 10-20 seconds... |
|
|
|
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. |
|
|
|
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. |
|
|
|
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... |
|
|
|
1. I hope that you will aquire a signed certificate and sign driver....
2. This is what I doing now ))) But want to use XL version in future without test mode.
Anyway, great work! Thank you!
We'll, see, maybe some good samaritan will offer to solve that Anyhow, just published a new release which fixes the startup bug. HereCheers! I know that Claymore signs it's driver. Maybe he can help? |
|
|
|
Hello  Would it be possible to convert the current settings back to a timing strap? (so we can put it inside a bios file and make it permanent) It could be even just a location reference, like "tREF is located in the x-th byte inside the timing strap". Btw, really a nice app I'm tweaking the hell out of my GPU. Yes, i've implemented this into the Extended XL version. Check OP for more info Link: HereCheers! It's very good! Only two questions: 1. Did you plan to sign your custom driver to run tool in usual not test mode? 2. Can you make use of tool in nontest mode with use driver IOMap for only changing timining like in non XL version? 1. I'd need a signed certificate for that. Not expensive, not "that" easy to aquire. 2. Can't you just use Non xl version then? Cheers 1. I hope that you will aquire a signed certificate and sign driver.... 2. This is what I doing now ))) But want to use XL version in future without test mode. Anyway, great work! Thank you! |
|
|
|
Hello Would it be possible to convert the current settings back to a timing strap? (so we can put it inside a bios file and make it permanent) It could be even just a location reference, like "tREF is located in the x-th byte inside the timing strap". Btw, really a nice app I'm tweaking the hell out of my GPU. Yes, i've implemented this into the Extended XL version. Check OP for more info Link: HereCheers! It's very good! Only two questions: 1. Did you plan to sign your custom driver to run tool in usual not test mode? 2. Can you make use of tool in nontest mode with use driver IOMap for only changing timining like in non XL version? |
|
|
|
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... |
|
|
|
@PhoenixMiner, you said: ... - 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, 4Gb cards became useless more early than 4Gb+. Cause of system use some vmemory... On 4Gb cards not all 4Gb free. |
|
|
|
|
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...
|
|
|
|
sure. But two of three rigs just hangs at this same moment (Rx 470 & Rx 480), it happens when ETC touch epoch 280. Below is my config.txt content (they nearly just the same on both machines)
Try "-eres 0". miner dont work/ test on 8 gb card EthDcrMiner64.exe -allcoins 1 -eres 0 -mode 1 -asm 2 -esm 3 -rxboost 1 epool POOL: stratum+tcp://daggerhashimoto.eu.nicehash.com:3353, WALLET: xxx.RIG01, PSW: x, ALLPOOLS: 1 then switch to etc mining DAG 281 have error pnoenixminer work fine test on lot of rigs with different card 4\8 gb same error 14.6 14.7 same error driver 18.6.1 19.7.2 same error plz fixminer add test directly on etc pool. same error What error you have? Post it here... |
|
|
|
I can paste log too, bu there is strictly NOTHING because miner hangs (sometime with restart, sometime not). It hangs after "setting dag epoch 280" line and before "setting dag epoch 280 done". I tried older version of claymore. It stops hanging but it just creating dag epoch and never finish. Changing port on pool to mining ETH solves the problem... for now
Looks like it's not enough memory to set DAG #280... Do you have enough virtual memory (page file) size? And another one thing. You use -allcoins 1. This is what Claymore writes in readme: -allcoins Specify "-allcoins 1" to be able to mine Ethereum forks, in this mode miner will use some default pools for devfee Ethereum mining. Note that if devfee mining pools will stop, entire mining will be stopped too. Miner has to use two DAGs in this mode - one for Ethereum and one for Ethereum fork, it can cause crashes because DAGs have different sizes. Therefore for this mode it is recommended to specify current Ethereum epoch (or a bit larger value), for example, "-allcoins 47" means that miner will expect DAG size for epoch #47 and will allocate appropriate GPU buffer at starting, instead of reallocating bigger GPU buffer (may crash) when it starts devfee mining. Another option is to specify "-allcoins -1", in this mode miner will start devfee round immediately after start and therefore will get current epoch for Ethereum, after that it will be able to mine Ethereum fork. If you mine ETC on some pool that does not accept wallet address but requires Username.Worker instead, the best way is to specify "-allcoins etc", in this mode devfee mining will be on ETC pools and DAG won't be recreated at all.Try to set "-allcoins etc" |
|
|
|
What's wrong with dag 281 epoch? It works fine in my tests. If you to get some support, it's a good idea to post your config.txt file and some hardware info (or log file).
I have a miner hang at epoch 280 (both Rx 470 4gb and Rx 480 4gb). After switch to ETH (epoch 272 it still working well). It is not a config problem it is problem with miner. Check phoenix miner topic and there is same epoch problem with older miner versions C&p "Read this if you can't mine ETH or ETC with PhoenixMiner: important message for everyone that is running older versions of PhoenixMiner (before 4.2). IMPORTANT! The versions of PhoenixMiner before 4.2 only support DAG epoch up to 265. Both ETC and ETH has reached epoch 266 already. To ensure uninterrupted operation, please upgrade to 4.2. If you are mining other coins, you can safely disregard this message. The reason for this limitation is that we need to perform some quite complex calculations for each future DAG epoch in order to increase the hashrate of the optimized kernels. Recently we have added more computational resources and PhoenixMiner 4.2 will work without problems up to DAG epoch 329. We will increase this number significantly (e.g. 400 or more) in the next version." Phoenix miner works another way than Claymore's. It use optimized kernels wich is must be calculated with depends of DAG epoch. This is why if miner didn't contains optimized kernels for some DAG it would give error. Claymore's miner didn't use kernels optimized for each epoch. So it must work on any DAG. You must provide your config, bat file and log to determine what's your problem. |
|
|
|
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.1 On version 19.7.1, the speed is 20-30 hashes lower Seriously, 20-30 HASHES lower? What mean 20-30 hashes on 30+ Megahashes? On so big driver difference I recommend to make new autotune -gt parameter... Maybe you recieve 20-30 hashes more... |
|
|
|
|
Maybe speed drop on old drivers? I use RX 580 8Gb on latest driver. Speed is the same as on 4.2c with 19.4.3. driver.
|
|
|
|
|
Show Posts
