Bitcoin Forum
May 08, 2024, 10:03:02 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 [26] 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 »
  Print  
Author Topic: WildRig Multi 0.40.5 multi-algo miner with low dev-fee (AMD/NVIDIA/INTEL)  (Read 91623 times)
andrucrypt (OP)
Member
**
Offline Offline

Activity: 719
Merit: 49


View Profile
January 13, 2019, 07:25:29 PM
 #501

Hey guys, trying to get 6 Vega64s to run stable. At this point after 10 minutes one or two gpu's dies, and the rig freezes.
Looking for a stable bat file for startup. Speed isn't an issue at the moment, just want to keep it running.
Any help appreciated! Thanks!
Check your voltage for core, if you use modification for cryptonight mining - it won't work on almost all other algorithms here. So try to test on one GPU first, starting from stock voltage and decrease it step by step finding the lowest stable value.
1715205782
Hero Member
*
Offline Offline

Posts: 1715205782

View Profile Personal Message (Offline)

Ignore
1715205782
Reply with quote  #2

1715205782
Report to moderator
1715205782
Hero Member
*
Offline Offline

Posts: 1715205782

View Profile Personal Message (Offline)

Ignore
1715205782
Reply with quote  #2

1715205782
Report to moderator
"In a nutshell, the network works like a distributed timestamp server, stamping the first transaction to spend a coin. It takes advantage of the nature of information being easy to spread but hard to stifle." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715205782
Hero Member
*
Offline Offline

Posts: 1715205782

View Profile Personal Message (Offline)

Ignore
1715205782
Reply with quote  #2

1715205782
Report to moderator
unsivilaudio
Newbie
*
Offline Offline

Activity: 18
Merit: 0


View Profile
January 13, 2019, 10:45:30 PM
 #502

Just fyi, easier ethos installation is here. Full integration.

https://github.com/cynixx3/third-party-miner-installer-for-ethos
andrucrypt (OP)
Member
**
Offline Offline

Activity: 719
Merit: 49


View Profile
January 14, 2019, 09:02:46 AM
 #503

Just fyi, easier ethos installation is here. Full integration.

https://github.com/cynixx3/third-party-miner-installer-for-ethos
Thanks! Will add this link into OP Smiley
melt7777
Jr. Member
*
Offline Offline

Activity: 128
Merit: 5


View Profile WWW
January 14, 2019, 02:12:52 PM
 #504

Hey andrucrypt Thanks again for the latest round of updates. The wildrig-multi is running fast and very stable on PiMP OS. We have it fully integrated, so all the miner must do is set their pool and wallet and go. Keep up the great work! and thanks again for the solid API so we can get the stats for miner.farm. See you in the wildrig discord!

~ melt
getpimp.org | miner.farm
hashit2passit
Newbie
*
Offline Offline

Activity: 19
Merit: 0


View Profile
January 15, 2019, 08:26:11 AM
 #505

Add lyra2zz algo please.
andrucrypt (OP)
Member
**
Offline Offline

Activity: 719
Merit: 49


View Profile
January 17, 2019, 07:42:57 AM
Last edit: January 17, 2019, 08:33:12 AM by andrucrypt
 #506

WARNING:
If you were using some Grin miner, you will get system freeze using WildRig. That miner changes driver behavior, because of recommendation to use command setx GPU_MAX_WORKGROUP_SIZE 1024. So if you get freezes, now you need to specify worksize precisely. Like --opencl-launch 20x256 instead of --opencl-launch 20x0.
powerstr
Newbie
*
Offline Offline

Activity: 107
Merit: 0


View Profile
January 18, 2019, 07:06:50 AM
 #507

http://prntscr.com/m8rb0r
nanona
Full Member
***
Offline Offline

Activity: 307
Merit: 101


View Profile
January 18, 2019, 10:30:19 PM
 #508

WARNING:
If you were using some Grin miner, you will get system freeze using WildRig. That miner changes driver behavior, because of recommendation to use command setx GPU_MAX_WORKGROUP_SIZE 1024. So if you get freezes, now you need to specify worksize precisely. Like --opencl-launch 20x256 instead of --opencl-launch 20x0.

I never understood why most mining software comes with "setx" in the sample batch file. This is wrong and dangerous. The command "set" is what should be used.

set modifies the current shell's (the window's) environment values, and the change is available immediately, but it is temporary. The change will not affect other shells that are running, and as soon as you close the shell, the new value is lost until such time as you run set again.

setx modifies the value permanently, which affects all future shells, but does not modify the environment of the shells already running. You have to exit the shell and reopen it before the change will be available, but the value will remain modified until you change it again.
dragonmike
Hero Member
*****
Offline Offline

Activity: 1274
Merit: 556



View Profile
January 19, 2019, 12:40:24 AM
 #509

WARNING:
If you were using some Grin miner, you will get system freeze using WildRig. That miner changes driver behavior, because of recommendation to use command setx GPU_MAX_WORKGROUP_SIZE 1024. So if you get freezes, now you need to specify worksize precisely. Like --opencl-launch 20x256 instead of --opencl-launch 20x0.
Well there you go then, it's exactly what I experienced the other day when I wrote it to you in the Discord. Glad you found out what actually happened.
I originally thought it had something to do with the .net runtime.

What is the "regular" max workgroup size in Windows then, assuming the variable would never be forced/set by the Grin miner?
VasilyS
Member
**
Offline Offline

Activity: 618
Merit: 21


View Profile WWW
January 19, 2019, 01:31:06 AM
 #510

Finally, I achieved to launch your miner on hmq1725 algo. It is possible with your latest version 0.15.1. Thank you for your work!

                             ❱  CRYPTOPROFI  ❱
4ward
Member
**
Offline Offline

Activity: 473
Merit: 18


View Profile
January 19, 2019, 01:17:47 PM
 #511

Something is wrong with Astralhash (0.15.1.3)

Zergpool:

Code:
[15:15:29] new job from astralhash.mine.zergpool.com:8640 diff 16.78M
[15:15:29] rejected(0/1) diff 16.78M "Invalid share" GPU#0 (99 ms)
[15:15:29] rejected(0/2) diff 16.78M "Invalid share" GPU#0 (100 ms)
[15:15:30] rejected(0/3) diff 16.78M "Invalid share" GPU#0 (100 ms)
[15:15:33] rejected(0/4) diff 16.78M "Invalid share" GPU#0 (399 ms)

GltMiner:

Code:
[15:16:33] use pool fra.gltminer.com:50001 80.240.29.156
[15:16:36] rejected(0/1) diff 268.44M "low difficulty share of 7.615351028059327e-8" GPU#0 (32 ms)
[15:17:16] rejected(0/2) diff 268.44M "low difficulty share of 2.6222327381709165e-7" GPU#0 (31 ms)

p.s.
0.14 was fine

john1010
Hero Member
*****
Offline Offline

Activity: 2086
Merit: 562


View Profile WWW
January 19, 2019, 01:55:36 PM
 #512

I am using the v 0.15 but i got the waiting connection notification even i changed the pool that i am using, my config is the same with my other rig which i got no problem, i only got this waiting connection problem in my another rig, I checked everything, I don't missed something, but still I got the error of connection.
andrucrypt (OP)
Member
**
Offline Offline

Activity: 719
Merit: 49


View Profile
January 19, 2019, 05:46:47 PM
 #513

Something is wrong with Astralhash (0.15.1.3)

Zergpool:

Code:
[15:15:29] new job from astralhash.mine.zergpool.com:8640 diff 16.78M
[15:15:29] rejected(0/1) diff 16.78M "Invalid share" GPU#0 (99 ms)
[15:15:29] rejected(0/2) diff 16.78M "Invalid share" GPU#0 (100 ms)
[15:15:30] rejected(0/3) diff 16.78M "Invalid share" GPU#0 (100 ms)
[15:15:33] rejected(0/4) diff 16.78M "Invalid share" GPU#0 (399 ms)

GltMiner:

Code:
[15:16:33] use pool fra.gltminer.com:50001 80.240.29.156
[15:16:36] rejected(0/1) diff 268.44M "low difficulty share of 7.615351028059327e-8" GPU#0 (32 ms)
[15:17:16] rejected(0/2) diff 268.44M "low difficulty share of 2.6222327381709165e-7" GPU#0 (31 ms)

p.s.
0.14 was fine
Yeah, something is broken there. But fixed in current development version, so next release will fix that, thanks for info.
andrucrypt (OP)
Member
**
Offline Offline

Activity: 719
Merit: 49


View Profile
January 19, 2019, 05:50:43 PM
 #514

I am using the v 0.15 but i got the waiting connection notification even i changed the pool that i am using, my config is the same with my other rig which i got no problem, i only got this waiting connection problem in my another rig, I checked everything, I don't missed something, but still I got the error of connection.
Wi-Fi?
mrpenta
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
January 19, 2019, 09:05:21 PM
 #515

hi guys
I cant run miner for mtp algo in hiveos.whats the problem?



[00:34:57] HTTP Daemon failed to start
[00:34:57] strategy: 0
[00:34:57] send-stale: no
[00:34:57] watchdog: disabled
[00:34:57] good-risers: default
[00:34:57] compiling code and initializing GPUs. This will take a while...
[00:34:57] GPU #0 [BusID: #3] [gfx900] Radeon RX Vega
[00:34:57] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #1 [BusID: #8] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #2 [BusID: #11] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #3 [BusID: #14] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #4 [BusID: #17] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:35:00] use pool xzc.f2pool.com:5780 47.92.184.84
[00:35:00] Stratum set target 0x00000020 0x00000000
[00:35:00] new job from xzc.f2pool.com:5780 diff 134.22M
[00:35:00] CPU: hashing inputs, allocating memory, filling first blocks

wildrig-multi exited, waiting to cooldown a bit

alucard20724
Sr. Member
****
Offline Offline

Activity: 703
Merit: 272


View Profile
January 19, 2019, 09:40:12 PM
 #516

hi guys
I cant run miner for mtp algo in hiveos.whats the problem?



[00:34:57] HTTP Daemon failed to start
[00:34:57] strategy: 0
[00:34:57] send-stale: no
[00:34:57] watchdog: disabled
[00:34:57] good-risers: default
[00:34:57] compiling code and initializing GPUs. This will take a while...
[00:34:57] GPU #0 [BusID: #3] [gfx900] Radeon RX Vega
[00:34:57] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #1 [BusID: #8] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #2 [BusID: #11] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #3 [BusID: #14] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #4 [BusID: #17] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:35:00] use pool xzc.f2pool.com:5780 47.92.184.84
[00:35:00] Stratum set target 0x00000020 0x00000000
[00:35:00] new job from xzc.f2pool.com:5780 diff 134.22M
[00:35:00] CPU: hashing inputs, allocating memory, filling first blocks

wildrig-multi exited, waiting to cooldown a bit



waiting to cooldown a bit

looks like your cards are over thermal threshold.   have you gone to the hiveos forum?
andrucrypt (OP)
Member
**
Offline Offline

Activity: 719
Merit: 49


View Profile
January 20, 2019, 07:54:02 AM
 #517

hi guys
I cant run miner for mtp algo in hiveos.whats the problem?



[00:34:57] HTTP Daemon failed to start
[00:34:57] strategy: 0
[00:34:57] send-stale: no
[00:34:57] watchdog: disabled
[00:34:57] good-risers: default
[00:34:57] compiling code and initializing GPUs. This will take a while...
[00:34:57] GPU #0 [BusID: #3] [gfx900] Radeon RX Vega
[00:34:57] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #1 [BusID: #8] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #2 [BusID: #11] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #3 [BusID: #14] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #4 [BusID: #17] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:35:00] use pool xzc.f2pool.com:5780 47.92.184.84
[00:35:00] Stratum set target 0x00000020 0x00000000
[00:35:00] new job from xzc.f2pool.com:5780 diff 134.22M
[00:35:00] CPU: hashing inputs, allocating memory, filling first blocks

wildrig-multi exited, waiting to cooldown a bit
Probably you have less than 8Gb of RAM, or CPU is weak
prominertools
Newbie
*
Offline Offline

Activity: 24
Merit: 0


View Profile
January 20, 2019, 02:21:36 PM
 #518

Wildrig Multi has been added to the PMT mirror: https://prominertools.com/wildrig-multi/
huntingthesnark
Member
**
Offline Offline

Activity: 357
Merit: 26


View Profile WWW
January 21, 2019, 03:00:09 PM
 #519

SMoS Wildrig just crashes before it finishes setup for me. Says it might be too much overclock, but I've set everything to stock, removed all powersaving.

--opencl-threads 1 --opencl-launch 16x0 Is this the correct starting point for MTP? It's unfortunate that the detailed setup on the first page of this thread doesn't include MTP...



hi guys
I cant run miner for mtp algo in hiveos.whats the problem?



[00:34:57] HTTP Daemon failed to start
[00:34:57] strategy: 0
[00:34:57] send-stale: no
[00:34:57] watchdog: disabled
[00:34:57] good-risers: default
[00:34:57] compiling code and initializing GPUs. This will take a while...
[00:34:57] GPU #0 [BusID: #3] [gfx900] Radeon RX Vega
[00:34:57] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #1 [BusID: #8] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #2 [BusID: #11] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #3 [BusID: #14] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:34:58] GPU #4 [BusID: #17] [gfx900] Radeon RX Vega
[00:34:58] threads: 1, intensity: 18, worksize: 0/256, cu: 64, mem: 8176Mb
[00:35:00] use pool xzc.f2pool.com:5780 47.92.184.84
[00:35:00] Stratum set target 0x00000020 0x00000000
[00:35:00] new job from xzc.f2pool.com:5780 diff 134.22M
[00:35:00] CPU: hashing inputs, allocating memory, filling first blocks

wildrig-multi exited, waiting to cooldown a bit
Probably you have less than 8Gb of RAM, or CPU is weak

For the latest Crypto news and alts info check out https://coinsjar.info/
andrucrypt (OP)
Member
**
Offline Offline

Activity: 719
Merit: 49


View Profile
January 21, 2019, 04:10:02 PM
 #520

SMoS Wildrig just crashes before it finishes setup for me. Says it might be too much overclock, but I've set everything to stock, removed all powersaving.

--opencl-threads 1 --opencl-launch 16x0 Is this the correct starting point for MTP? It's unfortunate that the detailed setup on the first page of this thread doesn't include MTP...
As I wrote - rig should have 8Gb of RAM and decent CPU for mining ZCoin. But even so, Vega cards currently shows same hashrate as RX580, so not worth a try. This algorithm need improvements, but no plans for working on it in next week or two.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 [26] 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!