Code:
\ufffd\ufffd\u0001\\\u0003\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000g:14444
Topic: SRBMiner-MULTI GPU & CPU Miner 0.9.4 - page 21. (Read 42979 times)
There is a bug in API that misreports the pool address. It contains some unknown chars. 0.8.7 was fine; for example:
V0.8.8
+ Added socks5 proxy support (--proxy parameter)
+ Added algorithm 'argon2d_16000' (ADOT - Alterdot coin) for CPU/GPU mining, fee 0.85%
+ Performance increase on 'heavyhash' algorithm for Vega GPU's (up to ~13%)
+ Performance increase on 'argon2id_chukwa2' algorithm for RDNA/RDNA2 GPU's (up to ~12%) & lower power consumption
+ Performance increase on 'argon2d_dynamic' algorithm for RDNA/RDNA2 GPU's (up to ~45%) & lower power consumption
+ Removed devfee for 'yespoweric' algorithm
+ Removed devfee for 'yespowerlitb' algorithm
+ Removed devfee for 'yespowerres' algorithm
+ If using '--multi-algorithm-job-mode 3' miner now auto sets --max-no-share-sent to 45 minutes if no other value was set
+ Rewrote restarting mechanism on Linux so it shouldn't spawn a new process anymore on miner auto restart
+ Minor bug fixes
***
--proxy parameter
Format : ip:port or user:password@ip:port
Supports: tcp, ssl/tls connections
Tested with socks5 proxies from : https://hideip.me/en/proxy/socks5list
+ Added socks5 proxy support (--proxy parameter)
+ Added algorithm 'argon2d_16000' (ADOT - Alterdot coin) for CPU/GPU mining, fee 0.85%
+ Performance increase on 'heavyhash' algorithm for Vega GPU's (up to ~13%)
+ Performance increase on 'argon2id_chukwa2' algorithm for RDNA/RDNA2 GPU's (up to ~12%) & lower power consumption
+ Performance increase on 'argon2d_dynamic' algorithm for RDNA/RDNA2 GPU's (up to ~45%) & lower power consumption
+ Removed devfee for 'yespoweric' algorithm
+ Removed devfee for 'yespowerlitb' algorithm
+ Removed devfee for 'yespowerres' algorithm
+ If using '--multi-algorithm-job-mode 3' miner now auto sets --max-no-share-sent to 45 minutes if no other value was set
+ Rewrote restarting mechanism on Linux so it shouldn't spawn a new process anymore on miner auto restart
+ Minor bug fixes
***
--proxy parameter
Format : ip:port or user:password@ip:port
Supports: tcp, ssl/tls connections
Tested with socks5 proxies from : https://hideip.me/en/proxy/socks5list
Anyone can share setting for HiveOS, mining AVN with ryzen
Thanks
Thanks
YadaCoin is on SRBMiner-MULTI!
Join our discord for assistance with pools and solo mining! https://discord.gg/JEDJaFS
Join our discord for assistance with pools and solo mining! https://discord.gg/JEDJaFS
V0.8.7
+ Fixed hashrate regression on 'heavyhash' algorithm for Navi cards
+ Fixed 'progpow' algorithms that got broken with previous release (0.8.6)
+ Fixed hashrate regression on 'heavyhash' algorithm for Navi cards
+ Fixed 'progpow' algorithms that got broken with previous release (0.8.6)
V0.8.6
+ Performance increase on 'heavyhash' algorithm for Polaris GPU's up to ~10%
+ Performance increase on 'heavyhash' algorithm for VEGA GPU's ~5%
+ Fixed 'heavyhash' algorithm for RX6500/6600/6700 GPU's
+ Fixed detection of GPU's on some linux systems
+ Performance increase on 'heavyhash' algorithm for Polaris GPU's up to ~10%
+ Performance increase on 'heavyhash' algorithm for VEGA GPU's ~5%
+ Fixed 'heavyhash' algorithm for RX6500/6600/6700 GPU's
+ Fixed detection of GPU's on some linux systems
Hello,
any chance for a macos version?
thx
any chance for a macos version?
thx
V0.8.5
+ Performance increase on 'heavyhash' algorithm for VEGA/RDNA/RDNA2 GPU's
+ Fixed 'verushash' algorithm 'invalid solution version' error
+ Performance increase on 'heavyhash' algorithm for VEGA/RDNA/RDNA2 GPU's
+ Fixed 'verushash' algorithm 'invalid solution version' error
Heavyhash hashrate:
RX 6900XT ~1070Mh/s @ ~240W PPT
RX VEGA 64 ~300Mh/s @ ~150W PPT
Can you share your CC and mV ?
RX 6900XT CC: ~2130MHz ~880mV (HWiNFO64)
RX VEGA64 CC: ~1200Mhz ~825mV (HWiNFO64)
Vega 64 is not tuned, only PPT adjusted really, RX 6900XT has has some voltage adjustments to hit it's efficiency in both AMD drivers & MPT but not maximized for potential.
Hotspot is around 100C on the 6900XT and 90C on the Vega 64.
Hotspot is a issue, can't run more wattage through the cards that much more. (insufficient cooling setup)
6900xt is really nice, but can't you go lower than 880mv ?
I can go lower to around 870mv but with risk of instabilities if you do other stuff than only have it mining on the PC, performance doesn't increase though really for the effort.
You need to increase wattage for more performance.
V0.8.5
+ Performance increase on 'heavyhash' algorithm for VEGA/RDNA/RDNA2 GPU's
+ Fixed 'verushash' algorithm 'invalid solution version' error
+ Performance increase on 'heavyhash' algorithm for VEGA/RDNA/RDNA2 GPU's
+ Fixed 'verushash' algorithm 'invalid solution version' error
Heavyhash hashrate:
RX 6900XT ~1070Mh/s @ ~240W PPT
RX VEGA 64 ~300Mh/s @ ~150W PPT
Can you share your CC and mV ?
RX 6900XT CC: ~2130MHz ~880mV (HWiNFO64)
RX VEGA64 CC: ~1200Mhz ~825mV (HWiNFO64)
Vega 64 is not tuned, only PPT adjusted really, RX 6900XT has has some voltage adjustments to hit it's efficiency in both AMD drivers & MPT but not maximized for potential.
Hotspot is around 100C on the 6900XT and 90C on the Vega 64.
Hotspot is a issue, can't run more wattage through the cards that much more. (insufficient cooling setup)
6900xt is really nice, but can't you go lower than 880mv ?
V0.8.5
+ Performance increase on 'heavyhash' algorithm for VEGA/RDNA/RDNA2 GPU's
+ Fixed 'verushash' algorithm 'invalid solution version' error
+ Performance increase on 'heavyhash' algorithm for VEGA/RDNA/RDNA2 GPU's
+ Fixed 'verushash' algorithm 'invalid solution version' error
Heavyhash hashrate:
RX 6900XT ~1070Mh/s @ ~240W PPT
RX VEGA 64 ~300Mh/s @ ~150W PPT
Can you share your CC and mV ?
RX 6900XT CC: ~2130MHz ~880mV (HWiNFO64)
RX VEGA64 CC: ~1200Mhz ~825mV (HWiNFO64)
Vega 64 is not tuned, only PPT adjusted really, RX 6900XT has has some voltage adjustments to hit it's efficiency in both AMD drivers & MPT but not maximized for potential.
Hotspot is around 100C on the 6900XT and 90C on the Vega 64.
Hotspot is a issue, can't run more wattage through the cards that much more. (insufficient cooling setup)
V0.8.5
+ Performance increase on 'heavyhash' algorithm for VEGA/RDNA/RDNA2 GPU's
+ Fixed 'verushash' algorithm 'invalid solution version' error
+ Performance increase on 'heavyhash' algorithm for VEGA/RDNA/RDNA2 GPU's
+ Fixed 'verushash' algorithm 'invalid solution version' error
Heavyhash hashrate:
RX 6900XT ~1070Mh/s @ ~240W PPT
RX VEGA 64 ~300Mh/s @ ~150W PPT
Can you share your CC and mV ?
V0.8.5
+ Performance increase on 'heavyhash' algorithm for VEGA/RDNA/RDNA2 GPU's
+ Fixed 'verushash' algorithm 'invalid solution version' error
+ Performance increase on 'heavyhash' algorithm for VEGA/RDNA/RDNA2 GPU's
+ Fixed 'verushash' algorithm 'invalid solution version' error
Heavyhash hashrate:
RX 6900XT ~1070Mh/s @ ~240W PPT
RX VEGA 64 ~300Mh/s @ ~150W PPT
V0.8.5
+ Performance increase on 'heavyhash' algorithm for VEGA/RDNA/RDNA2 GPU's
+ Fixed 'verushash' algorithm 'invalid solution version' error
+ Performance increase on 'heavyhash' algorithm for VEGA/RDNA/RDNA2 GPU's
+ Fixed 'verushash' algorithm 'invalid solution version' error
AFAIK NBMiner is maybe the only one having an option to enable iGPU's according to their readme.md
--enable-igpu AMD igpu is disabled by default, set this option to enable.
Don't know how well it works.
[/quote]
It didn't work, crashes
[/quote]
How much system RAM have you installed, 8/16/32GB? AFAIK iGPU's 5000g can use shared memory (2GB default) but upto 16GB with 32GB RAM installed. It depends on BIOS settings
@doktor83
Verus need an update. All shares rejected.
Verus need an update. All shares rejected.
Yes, fix incoming.
nice @doktor83
Verus need an update. All shares rejected.
Verus need an update. All shares rejected.
Yes, fix incoming.
@doktor83
Verus need an update. All shares rejected.
Verus need an update. All shares rejected.
[/quote]
AFAIK NBMiner is maybe the only one having an option to enable iGPU's according to their readme.md
--enable-igpu AMD igpu is disabled by default, set this option to enable.
Don't know how well it works.
[/quote]
It didn't work, crashes
V0.8.4
Hello friends!Tell me about my problem: I'm trying to run the oBTC (heavy hash) algorithm on the embedded video CPU p5 5600G. But the miner crashes right away, can I solve my problem?
Logminer:
Known issue, iGPU on APU isn't found by the miner or crashes.
It's not fully supported.
I tried to have it work but we got nowhere with it some time back.
@doktor83
A clue might be that "stats" is causing a crash when it queries the iGPU. (this was an issue for Team Black Miner)
You had to use the miner with a --no-stats parameter for it to work without issues if you wanted to use a iGPU from a Ryzen CPU like 5700G.
You do not have a option like this that I could see.
Strangely, on a laptop with AMD Ryzen 5 4500U it works.
It's not crashing, as you can see in the log (GPU0 can't build program ).
I added support for gfx90c blindly, that means i didn't have / don't have a real cpu to test with/optimise/make work.
@Din@slav78RUS , try using the same AMD GPU driver that you use on the laptop where it works
AMD Ryzen 5 4500U has a Vega 6 (gfx902) / (gfx903), while your other CPU has a gfx90c
V0.8.4
Hello friends!Tell me about my problem: I'm trying to run the oBTC (heavy hash) algorithm on the embedded video CPU p5 5600G. But the miner crashes right away, can I solve my problem?
Logminer:
Known issue, iGPU on APU isn't found by the miner or crashes.
It's not fully supported.
I tried to have it work but we got nowhere with it some time back.
@doktor83
A clue might be that "stats" is causing a crash when it queries the iGPU. (this was an issue for Team Black Miner)
You had to use the miner with a --no-stats parameter for it to work without issues if you wanted to use a iGPU from a Ryzen CPU like 5700G.
You do not have a option like this that I could see.
Strangely, on a laptop with AMD Ryzen 5 4500U it works.
AFAIK NBMiner is maybe the only one having an option to enable iGPU's according to their readme.md
--enable-igpu AMD igpu is disabled by default, set this option to enable.
Don't know how well it works.
Jump to: