 Show Posts
|
|
Pages: [1] 2 3 »
|
Dynex+Zil (windows) V2.3.8 [2023-10-18 05:00:34] Update capacity FAILED [hk.dynex.herominers.com:1119]
[2023-10-18 05:00:35] Update capacity FAILED [https://dnx.eu.ekapool.com]
[2023-10-18 05:00:36] Update capacity FAILED [eu.dnx.minenow.space:8000]
[2023-10-18 05:00:38] Update capacity FAILED [sg.dynex.herominers.com:1119]
[2023-10-18 05:00:38] Update capacity FAILED [mallob.deepminerz.com:9000]
[2023-10-18 05:00:39] Update capacity FAILED [https://dnx.ca.ekapool.com]
[2023-10-18 05:00:40] Update capacity FAILED [au.dynex.herominers.com:1119]
[2023-10-18 05:00:41] Update capacity FAILED [ru.dynex.herominers.com:1119]
[2023-10-18 05:00:42] Update capacity FAILED [https://dnx.eu.ekapool.com]
[2023-10-18 05:00:43] Update capacity FAILED [us2.dynex.herominers.com:1119]
[2023-10-18 05:00:45] Update capacity FAILED [http://mallob-ml.us.neuropool.net/]
[2023-10-18 05:00:47] Update capacity FAILED [https://dnx.sg.ekapool.com]
[2023-10-18 05:00:48] Update capacity FAILED [http://mallob-ml.us.neuropool.net/]
[2023-10-18 05:00:48] Update capacity FAILED [tr.dynex.herominers.com:1119]
[2023-10-18 05:00:49] Update capacity FAILED [ru.dynex.herominers.com:1119]
[2023-10-18 05:00:50] Update capacity FAILED [mallob.deepminerz.com:9001]
[2023-10-18 05:00:50] Update capacity FAILED [au.dynex.herominers.com:1119]
[2023-10-18 05:00:52] Update capacity FAILED [https://dnx.eu.ekapool.com] only miner restart helps to fix this. |
|
|
|
gpu-cclock0 - not working properly,it only takes first value and applies to all gpus ex: config : --gpu-cclock0 1470,1480,1490,1470,1470,2205,1470 gives us: [2023-10-04 03:01:44] GPU0 CC0: 1470MHZ
[2023-10-04 03:01:44] GPU1 CC0: 1470MHZ
[2023-10-04 03:01:44] GPU2 CC0: 1470MHZ
[2023-10-04 03:01:44] GPU3 CC0: 1470MHZ
[2023-10-04 03:01:44] GPU4 CC0: 1470MHZ
[2023-10-04 03:01:44] GPU5 CC0: 1470MHZ
[2023-10-04 03:01:44] GPU6 CC0: 1470MHZ
and yes I've tried all kinds of separators. |
|
|
|
Is it the right place to report a bug? I have a mixed rig with RX570 + 1070 + 1060 and I was running T-rex + Teamredminer. The combined dashboard hash rate was pretty good (83.5MH/s) but the effective hash rate was a bit disappointed (around 80.5MH/s). So I decided to give PhoenixMiner a try, I am using the latest version 5.6b but I noticed that I can only see the GPU temperature on the RX570 while it is missing on the 1060+1070. Nvidia driver is 466.11 / AMD driver is 21.4.1. I keep all the parameters default except "-cmdport", "-rxboost 20" for the AMD card, and "-straps 4" for Nvidia cards. I posted it on Reddit and it seems someone running a mixed rig also notice the same issue. https://www.reddit.com/r/EtherMining/comments/n357te/phoenixminer_missing_temperature_on_nvidia_cards/I also have the same problem of the temperature not being reported with Nvidia Pascal GPU's in Linux when I try the latest Phoenix miner 5.6 betas. v5.5c works fine. add: -hstats 2 |
|
|
|
The new beta version is finally ready. You can download PhoenixMiner 5.6a from here: PhoenixMiner_5.6a_Windows.zip (GitHub) PhoenixMiner_5.6a_Linux.tar.gz (GitHub) To check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows): File: PhoenixMiner_5.6a_Windows.zip
===================================
SHA-1: e9134f0b3985e967597f1e82c1cd7b0246fe4568
SHA-256: e3e10bc0ed7af17c4f38fb8314f9c72350750a554475498346f67a0a590e759b
SHA-512: 66b3e39daaadcb85fb79143697d8e10f7fc27bc8fc464f48ce1f362fc96235b15aa8a78bcfc547cd1416ebed19bb6e65746136a93318bc17875f50754ba90e57
File: PhoenixMiner_5.6a_Linux.tar.gz
====================================
SHA-1: d733df2b92876a1ecaff8c7d1f8fe6d5bf675f2d
SHA-256: 671218da670fc02318e3b4c296b9335984997a512242bdc7d17ed2cde2506de0
SHA-512: b38934dbdbaff49894ee30d4ae2937b84cd9f997432d68fffc8e23fb1cf8cab57d139533eee354b3be6625987bf628956c54826d42a21bbcebdc76edc3e521d4
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are: - Added native kernels for AMD RX6700 GPUs. These are faster than the generic kernels and produce a lot less stale shares
- Increase the max supported DAG epoch to 550 (should be enough to about Jan 2023)
- Full support for setting clocks, fan speeds, voltages, and memory timings of AMD RX6900/6800/6700 cards
- The specific hashrate is now shown in the form of kilo hashes per joule (kH/J). Example: if a GPU has hashrate of 30 MH/s with 100W power usage, the specific hashrate is 300 kH/J
- Added new command-line parameters -ttj and -ttmem, allowing automatic fan speed control based on GPU hotspot (junction), and memory temperatures respectively. Example: -ttmem 83 will keep the GPU memory temperature at or bellow 83C by increasing the fan speed as necessary. These parameters can be combined with -tt, as well as with each other. These options are supported only on AMD GPUs that report junction and memory temperatures
- Added new command-line parameters -tmaxj and -tmaxmem, allowing to decrease the GPU usage when the GPU hotspot (junction), or GPU memory temperatures are above the specified thresholds. These options are supported only on AMD GPUs that report junction and memory temperatures
- Added support for AMD Windows drivers 21.3.2, and 21.3.1
- Added support for AMD Linux drivers 20.50.x. Use this drivers only if you have Polaris or older GPUs, or the latest RX6x000 GPUs. WARNING: Vega, Radeon VII, and Navi GPUs won't work with these drivers!
- Turn off the zero fan feature on AMD cards whenever a fixed fan speed is used (e.g. -tt -40), or when an auto fan with min fan speed is used (e.g. -tt 63 -minfan 35). To disable this feature, add -fanstop 1 command-line parameter
- When -mcdag 1 is specified under Linux, the miner will not wait for the daggen.sh script to finish before starting to generate the DAGs. Instead it will for a fixed 7 seconds. This allows you to do all the following in the daggen.sh: turn off the overclocking of Nvidia GPUs, sleep for 30-60 seconds to allow time for DAG generation, and then re-apply the overclocking of the Nvidia GPUs
- Other small improvements and fixes
The support for - ttj, -ttmem, -tmaxj, and -tmaxmem for Nvidia 3090 and 3080 GPUs is not yet ready for release. We hope to have it ready for the final 5.6 release. For more robust integrity check, you can use our GPG public key, which was verifyed with ETH transaction from our main devfee account as explained here: https://bitcointalk.org/index.php?topic=2647654.msg56755869#msg56755869. Here are the signatures for the files in this release: Please let us know if you have any problems or questions related to PhoenixMiner 5.6a. Bug: No temps in on Nvidia cards in Windows driver 461.92 |
|
|
|
NVIDIA GeForce RTX 3080 ETH (Dagger-Hashimoto)________________________________________________________ Power Limit___Board Power__Hash Rate (Stock)____Hash Rate (OC)____Watt/Mh (OC) 100%_________~320W______~81.2 MH/s_________~89.1 MH/s________3.59 90%__________~290W______~81.3 MH/s_________~89.5 MH/s________3.25 80%__________~255W______~80.9 MH/s_________~88.4 MH/s________2.89 70%__________~225W______~80.7 MH/s_________~87.8 MH/s________2.58 65%________~210W_____~79.8 MH/s_______~86.0 MH/s______2.44 ****60%__________~193W______~60.2 MH/s_________~61.3 MH/s________3.06 Not bad!!! 
|
|
|
|
14.7 I got increased rejects, same settings as 14.6  |
|
|
|
90mh  |
|
|
|
Claymore's CryptoNight AMD GPU Miner.
Hi, can you add reject statistics by GPU like in Ethminer? |
|
|
|
|
11.4 - still 8-10% stales
let's wait a day to make sure
|
|
|
|
|
with 11.2 I rather got more stales +3-4% stale shares
|
|
|
|
(maybe antmine now.. was overloaded but i dont know about payments).
antminepool is stable but it steals about 25-30% |
|
|
|
If you get disconnected
I get dissconnected very often, pls fix |
|
|
|
Anyway, there're other algos and what hashrate are this asics can hit on ddr3? They might consume less power but I don't think they'll influence the network hashrate a lot |
|
|
|
VERGE is damned coin, hard to find a working pool, hard to find a working exchange  |
|
|
|
So, after testing XVG pools it seems http://antminepool.com is the only proper pool yet, but it's heavily overloaded, need to write a petition to increase its power |
|
|
|
Is there a proper pool for XVG? unimining, zpool - not seem to work properly, amount of mined coins is very low
We need big good XVG pools. Yes, we need, but they should not steal our shares, as lot of others do. welcome to our fellow russians pool http://xvgminingclub.info/supported by miningclub.info forum спасибо товарищ, попробую. |
|
|
|
|
