Search content
Sort by
Showing 20 of 97 results by alex31
Re: PhoenixMiner 5.0e: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
When I try to mine RVN it crashes.
I don't hear that the PhoenixMner support RVN
Re: [ANN] KawPowMiner v1.2.3 - first KawPow miner for miners (Nvidia/AMD) (Win/Linx)
Hi!
Please, tell us can I mining KawPow with video cards 4Gb
Hello, yes you canPlease, tell us can I mining KawPow with video cards 4Gb
Otherwise, simply type “kawpow algo” into the search engine of your browser to select the source of information.
If I understand you correctly.
Re: [ANN] KawPowMiner v1.2.3 - first KawPow miner for miners (Nvidia/AMD) (Win/Linx)
Hi!
Please, tell us can I mining KawPow with video cards 4Gb
Hello, yes you canPlease, tell us can I mining KawPow with video cards 4Gb
Re: PhoenixMiner 5.0b: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
hi
How to make sure that when reaching for example 62 degrees, the mining intensity decreases so as not to exceed the temperature threshold. What commands to put in a batch file. Driver version 19.7.5 mining 5.0b (my current settings, but on them the temperature continues to rise and above 62 degrees without reducing the intensity of mining -tt 61 -tstop 67 -tstart 50 -tmax 62 -fcm (0 or 2) -fanmin 50)
try set only -tt parameter excluding any another (include fan control parameters), in some cases it is resolved similar issuesHow to make sure that when reaching for example 62 degrees, the mining intensity decreases so as not to exceed the temperature threshold. What commands to put in a batch file. Driver version 19.7.5 mining 5.0b (my current settings, but on them the temperature continues to rise and above 62 degrees without reducing the intensity of mining -tt 61 -tstop 67 -tstart 50 -tmax 62 -fcm (0 or 2) -fanmin 50)
the -tt parameter only affects the fans and it works well with its own, but when the rotation of the fans reaches 99%, i need to keep the temperature still, for example, at 62 degrees, the -tmax parameter should be used, but it does not work on drivers above 18.9.3
with one parameter -tt i won’t get what it takes to keep the temperature at the selected limit
screen how it works on 18.9.3
hmm, very hot farm! I think that you need additional fan's to cool this hot-dog -)
Re: PhoenixMiner 5.0b: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
hi
How to make sure that when reaching for example 62 degrees, the mining intensity decreases so as not to exceed the temperature threshold. What commands to put in a batch file. Driver version 19.7.5 mining 5.0b (my current settings, but on them the temperature continues to rise and above 62 degrees without reducing the intensity of mining -tt 61 -tstop 67 -tstart 50 -tmax 62 -fcm (0 or 2) -fanmin 50)
How to make sure that when reaching for example 62 degrees, the mining intensity decreases so as not to exceed the temperature threshold. What commands to put in a batch file. Driver version 19.7.5 mining 5.0b (my current settings, but on them the temperature continues to rise and above 62 degrees without reducing the intensity of mining -tt 61 -tstop 67 -tstart 50 -tmax 62 -fcm (0 or 2) -fanmin 50)
try set only -tt parameter excluding any another (include fan control parameters), in some cases it is resolved similar issues
Re: PhoenixMiner 5.0d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
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.more correct way is to switch to another pool / as Phoenix wrote:
Quote
it seems that recently nicehash started changing the jobs more often, leading to more rejected shares.
Re: PhoenixMiner 5.0d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
Quote
I has in practice 4 Gb gpus on WIN10 and mined without problems as I told early 
But maybe your monitor is connected to the motherboard video... Not on the mining card...
No, my monitor connected to the first video card because my processor no has integrated video
What and where are you mining?
I tried to mine eth in ethermine and i tried to mine in nicehash - a lot of problems and restarts... And some of mine RX480 are with a speed 7-8 MHs
I mined ETC on ethermine ... on RX470 , RX560, RX570 4Gb and all nice , don't overclock its too much cclock 1000 MHz , mclock 1800-2000MHz vddc 850-1000 mV
Re: PhoenixMiner 5.0d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
Quote
I has in practice 4 Gb gpus on WIN10 and mined without problems as I told early
But maybe your monitor is connected to the motherboard video... Not on the mining card...
No, my monitor connected to the first video card because my processor no has integrated video
Re: PhoenixMiner 5.0d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
Code:
2020.06.09:11:34:45.506: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB <---------
2020.06.09:11:34:45.506: GPU1 GPU1: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:45.510: GPU1 GPU1: Generating DAG for epoch #341
2020.06.09:11:34:45.506: GPU1 GPU1: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:45.510: GPU1 GPU1: Generating DAG for epoch #341
You obviously can't mine at epoch 351 with the 4GB card that is connected with the monitor because there isn't enough VRAM for both activities. Just exclude it from mining: -gpus 23456 . Remove also your first gt: -gt 26,27,25,25,24
You can run second instance of PM to mine ETH with the first card. Use the same command line parameters, just change the pool with ETH pool (e.g.: -pool ssl://eu1.ethermine.org:5555), change wallet with some ETH wallet (e.g.: -wal 0x...SOME...ETH...WALLET...) and set -gpus 1 -gt 25 for the second instance of PM.
I think that you on wrong way , he has enough vram on first card
I has in practice 4 Gb gpus on WIN10 and mined without problems as I told early
Re: PhoenixMiner 5.0d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
When it makes a DAG for ETH and epoch #341 - yes,
but when it makes a DAG for ETC and epoch #351 the problem comes...
2020.06.09:11:43:45.258: GPU1 GPU1: Allocating DAG for epoch #351 (3.74) GB
2020.06.09:11:43:45.336: GPU1 GPU1: Generating DAG for epoch #351
but when it makes a DAG for ETC and epoch #351 the problem comes...
2020.06.09:11:43:45.258: GPU1 GPU1: Allocating DAG for epoch #351 (3.74) GB
2020.06.09:11:43:45.336: GPU1 GPU1: Generating DAG for epoch #351
I have 4Gb gpus and mined only ETC without any problems ... issue become only when you change coin on the fly (see prev posts)
so you need try mine only one coin
Re: PhoenixMiner 5.0d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
Code:
2020.06.09:11:34:45.506: GPU1 GPU1: [b]Free VRAM: 3.948 GB; used: 0.052 GB[/b]
2020.06.09:11:34:45.506: GPU1 GPU1: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:45.510: GPU1 GPU1: Generating DAG for epoch #341
2020.06.09:11:34:45.506: GPU1 GPU1: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:45.510: GPU1 GPU1: Generating DAG for epoch #341
You obviously can't mine at epoch 351 with the 4GB card that is connected with the monitor because there isn't enough VRAM for both activities. Just exclude it from mining: -gpus 23456 . Remove also your first gt: -gt 26,27,25,25,24
You can run second instance of PM to mine ETH with the first card. Use the same command line parameters, just change the pool with ETH pool (e.g.: -pool ssl://eu1.ethermine.org:5555), change wallet with some ETH wallet (e.g.: -wal 0x...SOME...ETH...WALLET...) and set -gpus 1 -gt 25 for the second instance of PM.
I think that you on wrong way , he has enough vram on first card
Re: PhoenixMiner 5.0d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
I am with a driver version: 19.4.3 and Phoenix Miner 5.0e Windows/msvc - Release build. When the miner makes a DAG for epoch #340 is ok. But the 4GB card stops when the miner starts to make a DAG for epoch #351.
Try set -rvram -1 on command line or in config, may be this can resolve your issue I have this in my config...
In the begginig everything is ok, but after 8 min and
2020.06.09:11:43:41.083: GPU4 GPU4: Generating ethash light cache for epoch #351
2020.06.09:11:43:41.265: GPU1 GPU1: Starting up... (0)
the card with a monitor crashed:
Ok, I think that issue occurs when nicehash pool switch mining coin from ETH to ETC ...
you may try mine only ETH or ETC selecting different port on the nicehash pool ...
Re: PhoenixMiner 5.0d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
I am with a driver version: 19.4.3 and Phoenix Miner 5.0e Windows/msvc - Release build. When the miner makes a DAG for epoch #340 is ok. But the 4GB card stops when the miner starts to make a DAG for epoch #351.
Try set -rvram -1 on command line or in config, may be this can resolve your issue I have this in my config...
Re: PhoenixMiner 5.0d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
I am with a driver version: 19.4.3 and Phoenix Miner 5.0e Windows/msvc - Release build. When the miner makes a DAG for epoch #340 is ok. But the 4GB card stops when the miner starts to make a DAG for epoch #351.
Try set -rvram -1 on command line, may be this can resolve your issue у меня терпения не хватает на это смотреть -) странный софт на ноде не могу привыкнуть к этим прелестям -)
может надо на сутки оставить майнер на ноде?
Софт обычный. исходники по ссылке в шапке можно скачать и посмотреть. Может найдёте что поправить.может надо на сутки оставить майнер на ноде?
На сутки или нет решать Вам.
запущу на сутки как нибудь другого выхода пока не вижу
я и на 3-4 часа заходил и всё равно картина странная, в течении этого периода то очень сложные шары то очень низкие
и еще сложность прыгает туду сюда
причем с начала было норм и блоки находились и шары адекватные, а потом пошло в разнобой
т.е странно как то - если как вы говорите долго не копали будет много низких шар - но все наоборот было - только пришел были
тяжелые шары, затем скатились до нуля
у меня терпения не хватает на это смотреть -) странный софт на ноде не могу привыкнуть к этим прелестям -)
может надо на сутки оставить майнер на ноде?
и еще сложность прыгает туду сюда
причем с начала было норм и блоки находились и шары адекватные, а потом пошло в разнобой
т.е странно как то - если как вы говорите долго не копали будет много низких шар - но все наоборот было - только пришел были
тяжелые шары, затем скатились до нуля
у меня терпения не хватает на это смотреть -) странный софт на ноде не могу привыкнуть к этим прелестям -)
может надо на сутки оставить майнер на ноде?
что то с гроестлом никак не пойму что творится - то сложные шары то почти нулевые идут
мало того - еще сложность шар бывает скачет туда сюда прям на каждой шаре -)
хоть какие параметры задавай, нода плюёт на них -)
на других пулах всё норм а у вас непонятно что -)
голову уже сломал ))
мало того - еще сложность шар бывает скачет туда сюда прям на каждой шаре -)
хоть какие параметры задавай, нода плюёт на них -)
на других пулах всё норм а у вас непонятно что -)
голову уже сломал ))
скажите, почему на гроестле сложность шар такая большая и можно ли а параметрах подключения указать сложность?
Указать можно, как обычно после адреса, вот здесь есть инфа для scrypt как это делается: http://xpool.net/faq.htmlЯ глянул какие шары решаются, вроде не большая:
Code:
[13:37:45] 192.168.0.3 difficulty changed to 0.081
[13:37:45] Accepted 0a71f6f0 Diff 0.096/0.083 GPU 0
[13:39:15] 192.168.0.3 difficulty changed to 0.079
[13:39:15] Accepted 04df9bb6 Diff 0.205/0.081 GPU 0
[13:39:25] 192.168.0.3 difficulty changed to 0.078
[13:39:25] Accepted 02472c4f Diff 0.439/0.079 GPU 0
[13:40:55] Stratum connection to 192.168.0.3 interrupted
[13:40:55] 192.168.0.3 difficulty changed to 0.078
[13:41:22] 192.168.0.3 difficulty changed to 0.076
[13:41:22] Accepted 073caf47 Diff 0.138/0.078 GPU 0
[13:41:55] 192.168.0.3 difficulty changed to 0.074
[13:41:55] Accepted 0b202ee3 Diff 0.090/0.076 GPU 1
[13:42:37] 192.168.0.3 difficulty changed to 0.072
[13:42:37] Accepted 0cdb9541 Diff 0.078/0.074 GPU 1
В приведённом фрагменте максимум 0.439, сложность пула колеблется от 0.072 до 0.083[13:37:45] Accepted 0a71f6f0 Diff 0.096/0.083 GPU 0
[13:39:15] 192.168.0.3 difficulty changed to 0.079
[13:39:15] Accepted 04df9bb6 Diff 0.205/0.081 GPU 0
[13:39:25] 192.168.0.3 difficulty changed to 0.078
[13:39:25] Accepted 02472c4f Diff 0.439/0.079 GPU 0
[13:40:55] Stratum connection to 192.168.0.3 interrupted
[13:40:55] 192.168.0.3 difficulty changed to 0.078
[13:41:22] 192.168.0.3 difficulty changed to 0.076
[13:41:22] Accepted 073caf47 Diff 0.138/0.078 GPU 0
[13:41:55] 192.168.0.3 difficulty changed to 0.074
[13:41:55] Accepted 0b202ee3 Diff 0.090/0.076 GPU 1
[13:42:37] 192.168.0.3 difficulty changed to 0.072
[13:42:37] Accepted 0cdb9541 Diff 0.078/0.074 GPU 1
Большая - это сколько? И какую Вы хотите?
у меня в течении получаса сложность выросла до 1.6 и продолжала на таком уровне оставаться в течении часа...
я имею ввиду значение после "/" - это сложность чего?
какую сложность хочу? - не знаю, у меня скорость 80 Mh и на такой сложности еле-еле копаю