Pages:
Author

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

member
Activity: 221
Merit: 12
Okay, I have some problems with 0.38.2 when mining SkyDoge, the miner freeze after some time of mining, this happened 2 times and I switched back to 0.36.10, no problems here. The rig is with 4x4090 on Windows 11. I am also mining SkyDoge with 1x4070 Ti with 0.38.2 on Windows 10 but this problem doesn't occur there.
Hmm, and there was no errors? What hashrate do you have with 4x4090? Probably I know one possible situation when it can hang.

170MH, no error, the miner is not responding and the PC became very laggy and I can barely close the miner and restart the PC.
hm, but does gpu's were hashing? Or hashrate was n/a?

No, the miner is not responding, it is frozen like a screenshot and shows for example 10 o'clock (the time when stopped), but it is 16 o'clock already when I saw it.
member
Activity: 720
Merit: 49
Okay, I have some problems with 0.38.2 when mining SkyDoge, the miner freeze after some time of mining, this happened 2 times and I switched back to 0.36.10, no problems here. The rig is with 4x4090 on Windows 11. I am also mining SkyDoge with 1x4070 Ti with 0.38.2 on Windows 10 but this problem doesn't occur there.
Hmm, and there was no errors? What hashrate do you have with 4x4090? Probably I know one possible situation when it can hang.

170MH, no error, the miner is not responding and the PC became very laggy and I can barely close the miner and restart the PC.
hm, but does gpu's were hashing? Or hashrate was n/a?
member
Activity: 221
Merit: 12
Okay, I have some problems with 0.38.2 when mining SkyDoge, the miner freeze after some time of mining, this happened 2 times and I switched back to 0.36.10, no problems here. The rig is with 4x4090 on Windows 11. I am also mining SkyDoge with 1x4070 Ti with 0.38.2 on Windows 10 but this problem doesn't occur there.
Hmm, and there was no errors? What hashrate do you have with 4x4090? Probably I know one possible situation when it can hang.

170MH, no error, the miner is not responding and the PC became very laggy and I can barely close the miner and restart the PC.
member
Activity: 720
Merit: 49
Okay, I have some problems with 0.38.2 when mining SkyDoge, the miner freeze after some time of mining, this happened 2 times and I switched back to 0.36.10, no problems here. The rig is with 4x4090 on Windows 11. I am also mining SkyDoge with 1x4070 Ti with 0.38.2 on Windows 10 but this problem doesn't occur there.
Hmm, and there was no errors? What hashrate do you have with 4x4090? Probably I know one possible situation when it can hang.
member
Activity: 221
Merit: 12
Okay, I have some problems with 0.38.2 when mining SkyDoge, the miner freeze after some time of mining, this happened 2 times and I switched back to 0.36.10, no problems here. The rig is with 4x4090 on Windows 11. I am also mining SkyDoge with 1x4070 Ti with 0.38.2 on Windows 10 but this problem doesn't occur there.
member
Activity: 720
Merit: 49
WildRig Multi 0.38.3
- now AMD APU's will be skipped and not listed as GPU0
- implemented support of AMD Vega/VII/MI25/etc. gpu's on newer Linux drivers
- fixed broken sha512256d for AMD RDNA2 gpu's on Linux
member
Activity: 221
Merit: 12
so many upgrades !
I was still running several versions ago. ;-)
yeah, got some free time and started to break and fix everything )

Thanks, I also upgraded to the latest version, still mining SkyDoge. Smiley
member
Activity: 720
Merit: 49
so many upgrades !
I was still running several versions ago. ;-)
yeah, got some free time and started to break and fix everything )
member
Activity: 750
Merit: 15
so many upgrades !
I was still running several versions ago. ;-)
member
Activity: 720
Merit: 49
WildRig Multi 0.38.2
- improved progpow family algorithms on AMD RDNA3 and NVIDIA RTX gpu's
- slightly improved sha512256d for AMD RDNA3
- slightly lower power consumption on AMD RDNA1/RDNA2 gpu's for sha512256d
- proper default intensity for ghostrider algo for NVIDIA
- now Intel iGPU will be skipped, so it won't be listed as gpu 0
- implemented --gpu-fan-speed
- added reset OC on exit
legendary
Activity: 1834
Merit: 1131
WildRig Multi 0.38.1
fixed choosing gpu's when there is skipped one
fixed broken progpow family algorithms since 0.38.0 on AMD and NVIDIA
fixed incorrect intensity for ghostrider algorithm on AMD and NVIDIA
now if use --gpu-memory-clock, miner will set it only after DAG generation
implemented progpow-quai for their Iron Age Testnet node

https://github.com/andru-kun/wildrig-multi/releases/tag/0.38.1
Check all links with first post from the developer!
member
Activity: 720
Merit: 49
WildRig Multi 0.38.0
- implemented support of Intel GPU's(Intel Arc, Intel Arc Pro and Intel Data Center GPU Flex). All algorithms are supported except heavyhash
- implemented OC for NVIDIA gpu's(full support of RTX cards only so far, see --help for commands)
member
Activity: 720
Merit: 49
I like how the miner is getting smaller in size. Is this from removing algos?
not quite, just changed compression method )
member
Activity: 750
Merit: 15
I like how the miner is getting smaller in size. Is this from removing algos?
member
Activity: 720
Merit: 49
WildRig Multi 0.37.0
- implemented rwahash
- removed memehash and memehashv2

WildRig Multi 0.37.1
- significant hashrate improvement for rwahash on Polaris/Vega gpu's
- fixed CPU usage on NVIDIA gpu's while mining rwahash

WildRig Multi 0.37.2
- fixed support of old drivers on Linux for RDNA gpu's
- significant hashrate improvements for RDNA3(and slight for RDNA1) on skydoge, rwahash and other nist-based family algorithms(like x16r)
member
Activity: 720
Merit: 49
What does the cu:## mean?
As mentioned, previous versions displayed double what it says now.
compute units, in old version there was just a bug because of solution I use for AMD RDNA gpu's previously. Don't ask how that impact on NVIDIA Smiley))
member
Activity: 750
Merit: 15
What does the cu:## mean?
As mentioned, previous versions displayed double what it says now.
member
Activity: 720
Merit: 49
It was the SSL issue. Wrong port.
Interesting how it didn't give me a connection error, just kept saying N/A.
cpuminer would say it can't connect:

 stratum_recv_line failed
 ...retry after 15 seconds

Strange, after some time it should print timeout, but probably need to fix something.
member
Activity: 750
Merit: 15
It was the SSL issue. Wrong port.
Interesting how it didn't give me a connection error, just kept saying N/A.
cpuminer would say it can't connect:

 stratum_recv_line failed
 ...retry after 15 seconds
member
Activity: 720
Merit: 49
Hello.
Long time listener, first time caller...

Mining Ghostrider with 3060ti in windows and P2000 in linux still gets n/a for hashrate. I tried --opencl-launch 256 (and 512, 348, 128...) and still no luck.
Any thoughts?

Windows nVidia driver: 536.23

I did notice that in an older version, the 'cu:76' was higher than the current 'cu:38'. Is it calculating something differently?
I guess you use wrong port for pool, e.g. SSL one instead of non-SSL or vice versa. If you use SSL one, don't forget to use prefix stratum+tcps://, if non-SSL - just stratum+tcp:// or no preix at all. Also if you use newest version on 3060Ti, use additional parameter --opencl-launch 1024. For some reason without it you will get a lot of rejects(even they don't harm the real hashrate, but anyway).
Pages:
Jump to: