nanopool / phoenix-miner Goto Github PK

Hello guys...i buy a rtx 3070 putt it alone for benchmark and its going awesome...when i putt it with the others i have this errors
MVML error in cudaprogram.cu 216 : not supported (3)
NVML error in cudaprogram.cu 219 : invalid argument (2)

Unable to init NVML : not supported (3)

and all is incorrect shares..i take it out and put it in benchmark pc and continued to take this errors with incorrect shares!!! Any help would be great thanks!!!

Windows 10
tr4 2950
asus x399
Radeon vii
clksetkerneArg (-48) fatal error detected.
I got it to work with -clKernel 0 for a little bit, but now it fails stating
stratum thread no responsive fatal error restarting,

Nvidia 2070 super
just gives stratum thread no responsive fatal error restarting,

This has only come up in the last few days.

Why i find sassy worms and other worms in all miner online , i got some from Github and wow its anoying they steal from me when mining zz .so focking anoying. will learn pyton now and will not mine untill i made my own.

I have geth running on the same machine as phoenix miner. It refuses to connect giving an "exception -32603". There's almost no documentation about troubleshooting for solo mining. I can ping the address (through cmd-> 'ping 127.0.0.1'), not really sure what's wrong. My geth node is synced, I checked it vs the current block number.

I've tried:

PhoenixMiner -pool http://127.0.0.1 -wal 0x58a3E54FAa325aF436368F224c1f75BE61b1948A
PhoenixMiner -pool http://127.0.0.1:8545 -wal 0x58a3E54FAa325aF436368F224c1f75BE61b1948A

Any help is appreciated.

Hi, I have problem generating DAG with GTX 1650 with 4GB dedicated VRAM and I understand the limitation, what I can't understand is why I can successfully generate DAG with Integrated AMD Radeon RX Vega 10 with 512MB dedicated VRAM , the only thing I see here is that this card has 7GB shared VRAM (but also my 1650 has) and it shows "AMD#1 AMD Radeon(TM) RX Vega 10 Graphics 6.1GB)" in the NiceHash window. Maybe it is this "fake" 6.1GB ram that let the minner generate the DAG? The true is that it can generate! Maybe there is a way we can pass the shared memory as a "fake" dedicated VRAM to the miner, or let it create DAG on the shared memory and like this we can again mine with the 4GB cards like 1650? Regards

Hi for mining what is the vram minumum needed 2gb? 3gb? or higher I couldn't finy any information about it

When i start Phoenix Miner an error appears

FATAL ERROR: Debugger detected

How can i fix this? :(

I had been using your miner for some days, until I noticed that your executable file takes up 4GB of memory and therefore raises my SSD temperatures (paging file).

My specs:
Ryzen 5 4600H
AMD Radeon RX 5600M
8GB Ram
512GB SSD

I request you to work on this miner so that this GPU becomes supported.
Thank you. Refer to the attached screenshot.

Hello i am new... Anyone can please help me.. i got very low hash rate how can i slove this..

so i downloaded salad.io in hopes of making some cash and a soon as i booted up the chopping avast gave me a notification that Phoenixminer.exe was put into my virus chest because it was infected with "win64: Malware-Gen"

I have a very restrictive firewall here, which blocks network traffic to pools.
An option to use http/https/socks porxy to connect to pools would be nice.

Do you have any plans to implement dual mining for TON coin?

Hello,

I am using Nvidia A100 160gb GPU and just testing different mining software. (Don't predict that it's commercial product that I am using it personally -- as it's my own box that I have managed to get it)

its all pre-built like drivers, cuda-toolkit, docker and everything.

I am testing PhoenixMiner to test the speed which I am getting 174MH per card averagely 650MZ to 750MH with all cards. However, it is only utilising 5GB VRAM per card instead of using maximum or say atleast 10 to 15GB per card.

Here is the output of nvidia-smi command:

`+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.82.01 Driver Version: 470.82.01 CUDA Version: 11.4 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 NVIDIA A100-SXM... On | 00000000:01:00.0 Off | Off |
| N/A 69C P0 279W / 275W | 5140MiB / 40536MiB | 100% Default |
| | | Disabled |
+-------------------------------+----------------------+----------------------+
| 1 NVIDIA A100-SXM... On | 00000000:47:00.0 Off | Off |
| N/A 68C P0 274W / 275W | 5140MiB / 40536MiB | 100% Default |
| | | Disabled |
+-------------------------------+----------------------+----------------------+
| 2 NVIDIA A100-SXM... On | 00000000:81:00.0 Off | Off |
| N/A 67C P0 279W / 275W | 5140MiB / 40536MiB | 100% Default |
| | | Disabled |
+-------------------------------+----------------------+----------------------+
| 3 NVIDIA DGX Display On | 00000000:C1:00.0 Off | N/A |
| 34% 38C P8 N/A / 50W | 1MiB / 3911MiB | 0% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+
| 4 NVIDIA A100-SXM... On | 00000000:C2:00.0 Off | Off |
| N/A 67C P0 274W / 275W | 5140MiB / 40536MiB | 100% Default |
| | | Disabled |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=============================================================================|
| 0 N/A N/A 111324 C ./PhoenixMiner 5137MiB |
| 1 N/A N/A 111324 C ./PhoenixMiner 5137MiB |
| 2 N/A N/A 111324 C ./PhoenixMiner 5137MiB |
| 4 N/A N/A 111324 C ./PhoenixMiner 5137MiB |
+-----------------------------------------------------------------------------+`

As you can see above memory usage is only 5137MiB per card but GPU-Utilisation shows 100%.

I don't know if it is the default behaviour or not, so thought to ask experts if they can help achieving more juices out of 160GB total GPUs.

I have a guess that the memory chip use of some Ethash mining implementations is uneven, constantly using the same subset of chips on the GPU.

For example, memory chips on one side of my 3080 GPU runs far hotter than the other side. (Note that I am not the first to notice this, but I cannot immediately find the other person's content).

Maybe this could be caused by Ethash implementations like T-Rex loading the DAG file (currently ~4 GB in size) into physically contiguous chips that are beside each other on the card. In the 3080 GPU, the DAG would fill about half the ten 1GB chips, which lines up with what I’ve seen.

If this speculation is true, the thermal problems caused by this unbalanced memory use could be large and spreading out the load would be beneficial.

For example, the 3090 can spread out loads and cooling over 5 times more space because it has 24 GB VRAM.

As you know, high memory temperatures are a big issue in the 3080/3090 cards. Thermal throttling due to memory temperature often limits hash rate, and there are concerns about wear and tear on the chips and on fans. To address this, people have spent a lot of money and time on various thermal pads and other cooling modifications.

Can T-Rex or another miner create an Ethash implementation that distributes the load across the chips?

Not a hardware engineer here, but for example, you could insert space to expand the DAG file across the memory chips, or just have two instances with two DAG files, and alternate work between them.

It seems that a miner that implements this would have a huge advantage over others, have higher market share, charge higher fees, etc.

2020.08.12:16:08:55.218: main Phoenix Miner 4.2c Windows/msvc - Release build
2020.08.12:16:08:55.218: main Cmd line: -pool eth-asia1.nanopool.org:9999 -wal 0xa67c6705a64e90ddd75cbb23b99d658e2d7ad631.Main -pass x
2020.08.12:16:08:55.242: main CUDA version: 11.0, CUDA runtime: 8.0
2020.08.12:16:08:55.258: main No OpenCL platforms found
2020.08.12:16:08:55.258: main Available GPUs for mining:
2020.08.12:16:08:55.258: main GPU1: GeForce GTX 1660 SUPER (pcie 1), CUDA cap. 7.5, 6 GB VRAM, 22 CUs
2020.08.12:16:08:55.258: main Unable to load NVML
2020.08.12:16:08:55.994: main Eth: Loading pools from epools.txt
2020.08.12:16:08:55.994: main Eth: the pool list contains 1 pool (1 from command-line)
2020.08.12:16:08:55.994: main Eth: primary pool: eth-asia1.nanopool.org:9999
2020.08.12:16:08:55.994: main Starting GPU mining
2020.08.12:16:08:55.994: wdog Starting watchdog thread
2020.08.12:16:08:55.994: main Eth: Connecting to ethash pool eth-asia1.nanopool.org:9999 (proto: EthProxy)
2020.08.12:16:08:56.125: eths Eth: Connected to ethash pool eth-asia1.nanopool.org:9999 (139.99.102.74)
2020.08.12:16:08:56.125: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0xa67c6705a64e90ddd75cbb23b99d658e2d7ad631.Main","x"]}

2020.08.12:16:08:56.198: main Listening for CDM remote manager at port 3333 in read-only mode
2020.08.12:16:08:56.551: eths Eth: Received: {"jsonrpc":"2.0","id":1,"result":true}
2020.08.12:16:08:56.551: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2020.08.12:16:08:56.551: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xb6903e5385fcb87ceaa5de1a7e896a0c551fbd9b7034e95bc1dccb32ea8eb6bf","0x2e9c37e381a67352111d539c6dc514b71530900fba66e26585fcd69e7463cb49","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2020.08.12:16:08:56.551: eths Eth: New job #b6903e53 from eth-asia1.nanopool.org:9999; diff: 10000MH
2020.08.12:16:08:56.552: GPU1 GPU1: Starting up... (0)
2020.08.12:16:08:56.552: GPU1 GPU1: Generating ethash light cache for epoch #354
2020.08.12:16:08:56.833: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xb6903e5385fcb87ceaa5de1a7e896a0c551fbd9b7034e95bc1dccb32ea8eb6bf","0x2e9c37e381a67352111d539c6dc514b71530900fba66e26585fcd69e7463cb49","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2020.08.12:16:08:58.381: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xae7cb416aa598c2051e3cb359d15a6fb30bde5a849498a34cb5bbc41a3fb4f95","0x2e9c37e381a67352111d539c6dc514b71530900fba66e26585fcd69e7463cb49","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2020.08.12:16:08:58.381: eths Eth: New job #ae7cb416 from eth-asia1.nanopool.org:9999; diff: 10000MH
2020.08.12:16:09:00.307: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xe703bd9cd70d9ef2663d6b9c36316213e1b67d1822ea1034e08d0eaa06300115","0x2e9c37e381a67352111d539c6dc514b71530900fba66e26585fcd69e7463cb49","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2020.08.12:16:09:00.307: eths Eth: New job #e703bd9c from eth-asia1.nanopool.org:9999; diff: 10000MH
2020.08.12:16:09:00.390: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x1ce36d97b5635a149053c4b2f86ac5453cc7c89b7dae7131b50d12db2b3df98b","0x2e9c37e381a67352111d539c6dc514b71530900fba66e26585fcd69e7463cb49","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2020.08.12:16:09:00.390: eths Eth: New job #1ce36d97 from eth-asia1.nanopool.org:9999; diff: 10000MH
2020.08.12:16:09:00.517: GPU1 Light cache generated in 4.0 s (15.2 MB/s)
2020.08.12:16:09:01.089: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2020.08.12:16:09:01.365: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xeebcc0890db399bee17971b6cc53e7c9ca953bdb93219f65e784fd8f585d24fe","0x2e9c37e381a67352111d539c6dc514b71530900fba66e26585fcd69e7463cb49","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2020.08.12:16:09:01.365: eths Eth: New job #eebcc089 from eth-asia1.nanopool.org:9999; diff: 10000MH
2020.08.12:16:09:01.453: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xd4888b5953542a4973564328cdca4692f824b025ef9522a4fad3bceebd8cadaf","0x2e9c37e381a67352111d539c6dc514b71530900fba66e26585fcd69e7463cb49","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2020.08.12:16:09:01.453: eths Eth: New job #d4888b59 from eth-asia1.nanopool.org:9999; diff: 10000MH
2020.08.12:16:09:02.351: GPU1 GPU1: Allocating DAG (3.78) GB; good for epoch up to #356
2020.08.12:16:09:02.460: GPU1 GPU1: Allocating light cache buffer (60.5) MB; good for epoch up to #356
2020.08.12:16:09:02.472: GPU1 GPU1: Generating DAG for epoch #354
2020.08.12:16:09:02.472: GPU1 GPU1: Unable to generate DAG for epoch #354; please upgrade to the latest version of PhoenixMiner
2020.08.12:16:09:02.472: GPU1 GPU1 initMiner error: Unable to initialize CUDA miner

Hello.

I've been using phoenix miner for 2 weeks now with my 2070 Super without any problems. However, a couple of days ago I got a Zotac 3060 Ti (P=70%, Mem=+1000) and I'm getting 10-15% invalid shares. I haven't changed any settings in 5_Ethereum-ethermine.bat (only wallet).

If i switch to T-Rex, I get almost no invalid shares.

Will you add LHR plugin?

Can you make this option alive in Phoenix?

Hello.
I have mixed rig - 8 different RX580's, 2 RX590's and 4 reference RX5700XT's.
And I'm trying to dual-mine ETH and XVG (blake2s).

My command-line:
-worker cat02⁣⁣⁣ -pool eth-eu.f2pool.com:6688 -wal xx⁣.cat02 -pass x -eres 0 -log 0 -gbase 0 -mode 0 -dcoin blake2s -dworker cat02 -dpool stratum+tcp://xvg-blake2s.f2pool.com:9008 -dwal xx-dpass x -proto 2⁣​

And I'm getting this for every GPU:
B2S: New job #1bcc718d from xvg-blake2s.f2pool.com:9008; diff: 274.9GH
GPU10 doesn't support Blake2s dual mining
GPU10: Using Ethash OCL kernels (Ellesmere; -clkernel 1)
GPU10: no -gt value specified, switching to auto-tune
GPU10 is already in auto-tune process

ETH mining is working fine but i cannot get Dual-mining to work.

Thanks for your time!