WildRig Multi 0.35.1 beta 2 multi-algo miner for AMD & NVIDIA - page 43.

andrucrypt

member

Activity: 720

Merit: 49

Quote from: mrpenta on January 19, 2019, 04:05:21 PM

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

alucard20724

sr. member

Activity: 703

Merit: 272

Quote from: mrpenta on January 19, 2019, 04:05:21 PM

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?

mrpenta

newbie

Activity: 6

Merit: 0

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

andrucrypt

member

Activity: 720

Merit: 49

Quote from: john1010 on January 19, 2019, 08:55:36 AM

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?

andrucrypt

member

Activity: 720

Merit: 49

Quote from: 4ward on January 19, 2019, 08:17:47 AM

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.

john1010

hero member

Activity: 2100

Merit: 562

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.

4ward

member

Activity: 473

Merit: 18

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

VasilyS

member

Activity: 620

Merit: 21

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!

dragonmike

hero member

Activity: 1274

Merit: 556

Quote from: andrucrypt on January 17, 2019, 02:42:57 AM

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?

nanona

full member

Activity: 307

Merit: 101

Quote from: andrucrypt on January 17, 2019, 02:42:57 AM

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.

powerstr

newbie

Activity: 107

Merit: 0

http://prntscr.com/m8rb0r

andrucrypt

member

Activity: 720

Merit: 49

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.

hashit2passit

newbie

Activity: 19

Merit: 0

Add lyra2zz algo please.

melt7777

jr. member

Activity: 128

Merit: 5

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

andrucrypt

member

Activity: 720

Merit: 49

Quote from: unsivilaudio on January 13, 2019, 05:45:30 PM

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

unsivilaudio

newbie

Activity: 18

Merit: 0

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

https://github.com/cynixx3/third-party-miner-installer-for-ethos

andrucrypt

member

Activity: 720

Merit: 49

Quote from: TerpFan on January 13, 2019, 01:33:47 PM

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.

TerpFan

newbie

Activity: 10

Merit: 0

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!

melloyellow

full member

Activity: 176

Merit: 100

Quote from: Biggums on January 11, 2019, 11:17:21 AM

OK, so I guess I have my cards maxed out for a x16 variant.

Thanks for the replies

Yes sir Dev, we would love for you to make Wildrig to be the best at cuckoo cycle solving

Biggums, would you mind sharing your best settings?

Biggums

newbie

Activity: 45

Merit: 0

OK, so I guess I have my cards maxed out for a x16 variant.

Thanks for the replies

Yes sir Dev, we would love for you to make Wildrig to be the best at cuckoo cycle solving

Topic: WildRig Multi 0.35.1 beta 2 multi-algo miner for AMD & NVIDIA - page 43. (Read 92082 times)