 Show Posts
|
|
Pages: [1] 2 3 »
|
1.16.3 didn't work well, when crashed didn't show which GPU cause it.
1.16.2 is working OK.
Please run the miner with "--log-file rigel.log" and post the log file, I'll have a look. Done, thank you. Check PM for details. |
|
|
|
|
1.16.3 didn't work well, when crashed didn't show which GPU cause it.
1.16.2 is working OK.
|
|
|
|
|
Algorithm 'fishhash' is broken for 4060 Ti, always throw worker thread stopped working immediately.
(at default/ or any settings even with slight reduced core & memory clocks)
Tried 2.5.2 and 2.5.1, with the same results.
And there is nothing wrong with the hardware, other algos works fine.
And a different miner app also works fine with 'fishhash'.
The same is for RX5600XT too.
|
|
|
|
|
Super.
Thanks for the updates!
|
|
|
|
|
Thanks! That's working fine.
|
|
|
|
|
Update FYI:
Installed the new driver 474.66 fine,
but 0.39.6 version still throw the same errors.
Switched to 0.39.5, while keeping the new driver 474.66 works OK.
Will keep using the new nVidia driver 474.66.
|
|
|
|
P.S: Just noted some miracle, nVidia has released a new GPU driver for Win7, for GTX 10xx Series, after so many years++ ... https://www.nvidia.com/Download/driverResults.aspx/214106/en-us/Version: 474.66 Release Date: 2023.10.31 Operating System: Windows 7 64-bit, Windows 8.1 64-bit, Windows 8 64-bit Language: English (US) File Size: 593.89 MB GeForce 10 Series: GeForce GTX 1080 Ti, GeForce GTX 1080, GeForce GTX 1070 Ti, GeForce GTX 1070, GeForce GTX 1060, GeForce GTX 1050 Ti, GeForce GTX 1050, GeForce GT 1030, GeForce GT 1010 I'm going to try them now and will update you if will makes any difference with 0.39.6 version. |
|
|
|
|
Yep, I'm using the latest suitable nVidia drivers 474.30 for my GPUs/OS
|
|
|
|
WildRig Multi 0.39.6
- fixed 100% cpu load on Windows while mining ghostrider with NVIDIA gpu's
- one more fix of rejected shares for Mining Core based pools(mining4people, miningandco, etc.)
- fixed long initialization of NVIDIA gpu's with weak cpu's
- fixed broken hmq1725(and some other similar algorithms) on NVIDIA gpu's
That one is broken for me and can't work anymore:  Using Win7 OS. 0.39.5 and any older versions are working fine. If you could fix it would be great. |
|
|
|
Something is wrong with those v2.2.7 & v2.2.8 versions,
they are causing high constant CPU usage 13%-17%
switching back to v2.2.6 CPU usage drops to 3%-4%
you forgot to tell which algorithm are you talking about, which gpu's, and windows or linux? algorithm: 'sha512_256d_radiant' os: windows (10 & 11, issue exist on both ) GPUs: Any GPUs models like => [3080, 3070, 3070 Ti, 3090, 3060, RX5600XT, 2070, 2070M, 1660M, 1080 Ti, 1070 Ti, 1070, 1060 6GB, 1050 Ti] system: Any PCs => [Intel/AMD], [desktop/notebook] Some more examples from 4 different PCs: ------------------------------------------------------------------------------------ pc1: v2.2. 6 CPU:  v2.2. 8 CPU:  ------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------ pc2: v2.2. 6 CPU:  v2.2. 8 CPU:  ------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------ pc3: v2.2. 6 CPU:  v2.2. 8 CPU:  ------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------ pc4: v2.2. 6 CPU:  v2.2. 8 CPU:  ------------------------------------------------------------------------------------ |
|
|
|
V2.2.7+ Significantly improved mining performance of dual kernels for algorithm 'dynex' [AMD/NVIDIA/INTEL] + Added kernels for DUAL mining : DYNEX/BLAKE3_ALEPHIUM, DYNEX/SHA256DT + Improved mining performance on algorithm 'dynex' for some GPU's + Fixed algorithm 'sha256dt' broken in previous versions + Fixed algorithm 'dynamo' broken in previous versions + Fixed algorithm 'autolykos2' in dual mining for Nvidia Turing GPU's broken in previous version + Fixed low hashrate issue (again) when connecting to some ALEPHIUM pool/s [alph-pool.com, coinhunters.space, woolypooly for ex.] + Minor bug fixes
HiveOS update script from v2.2.6 to v2.2.7:cd /tmp && wget https://github.com/doktor83/SRBMiner-Multi/releases/download/2.2.7/SRBMiner-Multi-2-2-7-Linux.tar.xz && tar -xvf SRBMiner-Multi-2-2-7-Linux.tar.xz && cd SRBMiner-Multi-2-2-7 && miner stop && cp SRBMiner-MULTI /hive/miners/srbminer/2.2.6 && miner start V2.2.8+ Added algorithm 'memehash' (PEPEPOW coin) for CPU/GPU mining, fee 2% [AMD/NVIDIA/INTEL] + Minor improvement for algorithm 'dynex' in dual mining mode + Fixed hashrate regression on 'sha512_256d_radiant' algorithm for RX6600 GPU's [single mode] + Fixed algorithm 'lyra2v2_webchain' on NVIDIA GPU's broken in previous versions + Fixed algorithm 'autolykos2' in dual mining with 'sha512_256d_radiant' for some GPU's broken in previous version + Added sum of accepted/rejected/hw error shares to stats + Added parameter '--disable-gpu-dual-kernels' [disables usage of optimised dual kernels] HiveOS update script from v2.2.7 to v2.2.8:cd /tmp && wget https://github.com/doktor83/SRBMiner-Multi/releases/download/2.2.8/SRBMiner-Multi-2-2-8-Linux.tar.xz && tar -xvf SRBMiner-Multi-2-2-8-Linux.tar.xz && cd SRBMiner-Multi-2-2-8 && miner stop && cp SRBMiner-MULTI /hive/miners/srbminer/2.2.7 && miner start Something is wrong with those v2.2.7 & v2.2.8 versions, they are causing high constant CPU usage 13%-17% switching back to v2.2.6 CPU usage drops to 3%-4% |
|
|
|
Thanks for those updates! Does the miner supports Win7 x64? ..Win64 release should include Win7 too? Because unable to run it in Win7 x64, output is: Detecting GPU devices...
No suitable GPU devices found GPUs are: 1070, 1070Ti, GPU driver: 474.30/Win7 64 (latest one available) Any other different miners are working fine, but not this one. |
|
|
|
@doktor83 If you accept suggestions:   If you could make those values in red color, to be only in red when their value > 0 I.e: to be white color(or other color, but not red) by default, and to become red only if such rejected/incorrect share is found. Else currently with this red color by default, it always catch the eye attention (brings false attention everytime) and must read the exact value to figure if there is a problem or not. EDIT: Also is it possible to add reset default OC values on miner exit? --gpu-reset-oc-on-exit |
|
|
|
Is there a way to disable LHR within miner?
Because even with latest Nvidia drivers, miner still applies LHR mode automatically.
Does it affect the hashrate? Usually these settings are automatic. Probably yes, because LHR is not 100% unlocked, and hashrate is low compared to other miners. Usually these settings are automatic.
Yes, and automatically applies some LHR modes which is unwanted that hurts the hashrate |
|
|
|
|
Is there a way to disable LHR within miner?
Because even with latest Nvidia drivers, miner still applies LHR mode automatically.
|
|
|
|
@PhoenixMiner
Would you possible to add memory temp reading [for supported GPUs] in miner's API requests replies?
For AMD RDNA/RDNA2 videocards it is already available for some time, I have a RX 6600 XT it shows in the status. Probably the same with Nvidia cards but I am not to sure about as I only have a GTX 1070 and I am not mining with it anymore. Check the readme or other docs on the first page. For Nvidia GPUs 30xx Series it's not. Check the readme or other docs on the first page.
I've checked this already, and there is nothing about memory temp in docs for API requests. For AMD RDNA/RDNA2 videocards it is already available for some time, I have a RX 6600 XT it shows in the status. It could be shown in status if you check the stats from web-browser, but "Tmem" value is not included in API miner's raw response. And it's not mentioned in the docs either. |
|
|
|
|
@PhoenixMiner
Would you possible to add memory temp reading [for supported GPUs] in miner's API requests replies?
|
|
|
|
Thanks.. Sometimes the simple solutions are the best, but you need to know how to do it.
 |
|
|
|
|
