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

andrucrypt

member

Activity: 720

Merit: 49

Quote from: melloyellow on December 08, 2020, 11:36:47 AM

I'm not able to mine raven with the default settings at auto nor others

wildrig.exe --print-full --algo kawpow --url stratum+tcp://rvn.woolypooly.com:55555 --worker test --user RJjr1sMM2uVsiBpUN86vgbs3JnkPzwfWFD --pass x --opencl-threads auto --opencl-launch auto

I've tried 1 and 2 threads, lowered intensity from 23 to 18. I just get crashes. Any ideas?

what's your error? What gpu's are you using?

melloyellow

full member

Activity: 176

Merit: 100

I'm not able to mine raven with the default settings at auto nor others

wildrig.exe --print-full --algo kawpow --url stratum+tcp://rvn.woolypooly.com:55555 --worker test --user RJjr1sMM2uVsiBpUN86vgbs3JnkPzwfWFD --pass x --opencl-threads auto --opencl-launch auto

I've tried 1 and 2 threads, lowered intensity from 23 to 18. I just get crashes. Any ideas?

dagere76

newbie

Activity: 7

Merit: 0

Quote from: Bathmat on November 17, 2020, 08:38:54 AM

Quote from: dagere76 on November 16, 2020, 01:16:01 PM

Quote from: andrucrypt on November 16, 2020, 10:52:33 AM

Quote from: dagere76 on November 16, 2020, 10:23:01 AM

am on the latest version 28.1 beta with AMD 470, I have 4 of them. I start the miner and my hashrate is showing n/a on all 4 video cards and they are doing nothing. MY GPU's are in compute mode and they mine ETH fine with Pheonix. When I try to install Microsoft Visual 64 it will not install because it says that I have a newer version already installed. Could this possibly be the problem. Here is my script to start minus the wallet address and I have gave the EXE admin privileges;

wildrig.exe --print-full --algo progpow-veil --opencl-threads auto --opencl-launch auto --url veil.us.woolypooly.com:3098 --user WalletAddress.dagereGPU --pass x

Anythouts why they will not compute...I see no errors

Try --user WalletAddress without specifying a rig name, since I guess you don't even get any "new job" message in miner?

Did what you said and still the same

Did you use a basecoin address (starts with "bv") and not a stealth address (starts with "sv")?

https://woolypooly.medium.com/how-to-mine-veil-full-mining-guide-6d8a72914377

P.S. How to get basecoin address starts with bv? Go to wallet console and type this command:
getnewbasecoinaddress

EDIT: I'm assuming the 470s are 4GB? I think the DAG for Veil is over 4GB, so you need 6 or 8GB GPUs for it.

Actually I do have the 8gb 470's but I did not use the BV address I used the SV, have never ran into that before. I will try that and get back to you.
Thanks

*UPDATE*
That fixed it! I saw there was a new mining address also, used that one to try and works fine. I guess that I should have researched the coin more before mining. I am assuming the different addresses pertain to privacy. Anyways thanks again..

Bathmat

jr. member

Activity: 78

Merit: 3

Quote from: dagere76 on November 16, 2020, 01:16:01 PM

Quote from: andrucrypt on November 16, 2020, 10:52:33 AM

Quote from: dagere76 on November 16, 2020, 10:23:01 AM

am on the latest version 28.1 beta with AMD 470, I have 4 of them. I start the miner and my hashrate is showing n/a on all 4 video cards and they are doing nothing. MY GPU's are in compute mode and they mine ETH fine with Pheonix. When I try to install Microsoft Visual 64 it will not install because it says that I have a newer version already installed. Could this possibly be the problem. Here is my script to start minus the wallet address and I have gave the EXE admin privileges;

wildrig.exe --print-full --algo progpow-veil --opencl-threads auto --opencl-launch auto --url veil.us.woolypooly.com:3098 --user WalletAddress.dagereGPU --pass x

Anythouts why they will not compute...I see no errors

Try --user WalletAddress without specifying a rig name, since I guess you don't even get any "new job" message in miner?

Did what you said and still the same

Did you use a basecoin address (starts with "bv") and not a stealth address (starts with "sv")?

https://woolypooly.medium.com/how-to-mine-veil-full-mining-guide-6d8a72914377

P.S. How to get basecoin address starts with bv? Go to wallet console and type this command:
getnewbasecoinaddress

EDIT: I'm assuming the 470s are 4GB? I think the DAG for Veil is over 4GB, so you need 6 or 8GB GPUs for it.

andrucrypt

member

Activity: 720

Merit: 49

Quote from: dagere76 on November 16, 2020, 01:16:01 PM

Quote from: andrucrypt on November 16, 2020, 10:52:33 AM

Quote from: dagere76 on November 16, 2020, 10:23:01 AM

am on the latest version 28.1 beta with AMD 470, I have 4 of them. I start the miner and my hashrate is showing n/a on all 4 video cards and they are doing nothing. MY GPU's are in compute mode and they mine ETH fine with Pheonix. When I try to install Microsoft Visual 64 it will not install because it says that I have a newer version already installed. Could this possibly be the problem. Here is my script to start minus the wallet address and I have gave the EXE admin privileges;

wildrig.exe --print-full --algo progpow-veil --opencl-threads auto --opencl-launch auto --url veil.us.woolypooly.com:3098 --user WalletAddress.dagereGPU --pass x

Anythouts why they will not compute...I see no errors

Try --user WalletAddress without specifying a rig name, since I guess you don't even get any "new job" message in miner?

Did what you said and still the same

Code:

* VERSIONS: WildRig/0.28.1 beta libuv/1.21.0 OpenCL/2.0 MSVC/2015
* CPU: Intel(R) Pentium(R) CPU G4400 @ 3.30GHz
* ALGO: progpow-veil
* POOL #1: veil.us.woolypooly.com:3098
* COMMANDS: hashrate, statistics, pause, resume
[12:11:06] donation: 1%
[12:11:06] send-stale: no
[12:11:06] watchdog: disabled
[12:11:06] temp limits: 60C..85C
[12:11:06] initializing GPUs...
[12:11:06] GPU #0: Radeon (TM) RX 470 Graphics [busID: 1] [arch: ellesmere]
[12:11:06] threads: 1, intensity: 23, worksize: 0/256, cu: 32, mem: 8192Mb
[12:11:07] GPU #1: Radeon (TM) RX 470 Graphics [busID: 3] [arch: ellesmere]
[12:11:07] threads: 1, intensity: 23, worksize: 0/256, cu: 32, mem: 8192Mb
[12:11:08] GPU #2: Radeon (TM) RX 470 Graphics [busID: 8] [arch: ellesmere]
[12:11:08] threads: 1, intensity: 23, worksize: 0/256, cu: 32, mem: 8192Mb
[12:11:08] GPU #3: Radeon (TM) RX 470 Graphics [busID: 9] [arch: ellesmere]
[12:11:08] threads: 1, intensity: 23, worksize: 0/256, cu: 32, mem: 8192Mb
[12:11:55] Uptime: 0 days 00:00:49
[12:11:55] GPU #0[T:40C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:11:55] GPU #1[T:39C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:11:55] GPU #2[T:38C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:11:55] GPU #3[T:33C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:11:55] hashrate: 10s: n/a 60s: n/a 15m: n/a kH/s max: n/a kH/s
[12:12:05] Uptime: 0 days 00:00:59
[12:12:05] GPU #0[T:39C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:12:05] GPU #1[T:37C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:12:05] GPU #2[T:37C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:12:05] GPU #3[T:32C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:12:05] hashrate: 10s: n/a 60s: n/a 15m: n/a kH/s max: n/a kH/s
[12:13:05] Uptime: 0 days 00:01:59
[12:13:05] GPU #0[T:35C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:13:05] GPU #1[T:33C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:13:05] GPU #2[T:32C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:13:05] GPU #3[T:28C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:13:05] hashrate: 10s: n/a 60s: n/a 15m: n/a kH/s max: n/a kH/s
[12:14:05] Uptime: 0 days 00:02:59
[12:14:05] GPU #0[T:32C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:14:05] GPU #1[T:30C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:14:05] GPU #2[T:29C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:14:05] GPU #3[T:26C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:14:05] hashrate: 10s: n/a 60s: n/a 15m: n/a kH/s max: n/a kH/s

Can you try with --print-debug? Looks like pool rejects connection for some reason.

dagere76

newbie

Activity: 7

Merit: 0

Quote from: andrucrypt on November 16, 2020, 10:52:33 AM

Quote from: dagere76 on November 16, 2020, 10:23:01 AM

am on the latest version 28.1 beta with AMD 470, I have 4 of them. I start the miner and my hashrate is showing n/a on all 4 video cards and they are doing nothing. MY GPU's are in compute mode and they mine ETH fine with Pheonix. When I try to install Microsoft Visual 64 it will not install because it says that I have a newer version already installed. Could this possibly be the problem. Here is my script to start minus the wallet address and I have gave the EXE admin privileges;

wildrig.exe --print-full --algo progpow-veil --opencl-threads auto --opencl-launch auto --url veil.us.woolypooly.com:3098 --user WalletAddress.dagereGPU --pass x

Anythouts why they will not compute...I see no errors

Try --user WalletAddress without specifying a rig name, since I guess you don't even get any "new job" message in miner?

Did what you said and still the same

Code:

* VERSIONS: WildRig/0.28.1 beta libuv/1.21.0 OpenCL/2.0 MSVC/2015
* CPU: Intel(R) Pentium(R) CPU G4400 @ 3.30GHz
* ALGO: progpow-veil
* POOL #1: veil.us.woolypooly.com:3098
* COMMANDS: hashrate, statistics, pause, resume
[12:11:06] donation: 1%
[12:11:06] send-stale: no
[12:11:06] watchdog: disabled
[12:11:06] temp limits: 60C..85C
[12:11:06] initializing GPUs...
[12:11:06] GPU #0: Radeon (TM) RX 470 Graphics [busID: 1] [arch: ellesmere]
[12:11:06] threads: 1, intensity: 23, worksize: 0/256, cu: 32, mem: 8192Mb
[12:11:07] GPU #1: Radeon (TM) RX 470 Graphics [busID: 3] [arch: ellesmere]
[12:11:07] threads: 1, intensity: 23, worksize: 0/256, cu: 32, mem: 8192Mb
[12:11:08] GPU #2: Radeon (TM) RX 470 Graphics [busID: 8] [arch: ellesmere]
[12:11:08] threads: 1, intensity: 23, worksize: 0/256, cu: 32, mem: 8192Mb
[12:11:08] GPU #3: Radeon (TM) RX 470 Graphics [busID: 9] [arch: ellesmere]
[12:11:08] threads: 1, intensity: 23, worksize: 0/256, cu: 32, mem: 8192Mb
[12:11:55] Uptime: 0 days 00:00:49
[12:11:55] GPU #0[T:40C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:11:55] GPU #1[T:39C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:11:55] GPU #2[T:38C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:11:55] GPU #3[T:33C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:11:55] hashrate: 10s: n/a 60s: n/a 15m: n/a kH/s max: n/a kH/s
[12:12:05] Uptime: 0 days 00:00:59
[12:12:05] GPU #0[T:39C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:12:05] GPU #1[T:37C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:12:05] GPU #2[T:37C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:12:05] GPU #3[T:32C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:12:05] hashrate: 10s: n/a 60s: n/a 15m: n/a kH/s max: n/a kH/s
[12:13:05] Uptime: 0 days 00:01:59
[12:13:05] GPU #0[T:35C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:13:05] GPU #1[T:33C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:13:05] GPU #2[T:32C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:13:05] GPU #3[T:28C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:13:05] hashrate: 10s: n/a 60s: n/a 15m: n/a kH/s max: n/a kH/s
[12:14:05] Uptime: 0 days 00:02:59
[12:14:05] GPU #0[T:32C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:14:05] GPU #1[T:30C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:14:05] GPU #2[T:29C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:14:05] GPU #3[T:26C F:33%]: 10s: n/a 60s: n/a 15m: n/a kH/s
[12:14:05] hashrate: 10s: n/a 60s: n/a 15m: n/a kH/s max: n/a kH/s

andrucrypt

member

Activity: 720

Merit: 49

Quote from: dagere76 on November 16, 2020, 10:23:01 AM

am on the latest version 28.1 beta with AMD 470, I have 4 of them. I start the miner and my hashrate is showing n/a on all 4 video cards and they are doing nothing. MY GPU's are in compute mode and they mine ETH fine with Pheonix. When I try to install Microsoft Visual 64 it will not install because it says that I have a newer version already installed. Could this possibly be the problem. Here is my script to start minus the wallet address and I have gave the EXE admin privileges;

wildrig.exe --print-full --algo progpow-veil --opencl-threads auto --opencl-launch auto --url veil.us.woolypooly.com:3098 --user WalletAddress.dagereGPU --pass x

Anythouts why they will not compute...I see no errors

Try --user WalletAddress without specifying a rig name, since I guess you don't even get any "new job" message in miner?

dagere76

newbie

Activity: 7

Merit: 0

am on the latest version 28.1 beta with AMD 470, I have 4 of them. I start the miner and my hashrate is showing n/a on all 4 video cards and they are doing nothing. MY GPU's are in compute mode and they mine ETH fine with Pheonix. When I try to install Microsoft Visual 64 it will not install because it says that I have a newer version already installed. Could this possibly be the problem. Here is my script to start minus the wallet address and I have gave the EXE admin privileges;

wildrig.exe --print-full --algo progpow-veil --opencl-threads auto --opencl-launch auto --url veil.us.woolypooly.com:3098 --user WalletAddress.dagereGPU --pass x

Anythouts why they will not compute...I see no errors

Wolfie

member

Activity: 245

Merit: 13

Quote from: andrucrypt on October 16, 2020, 10:26:46 AM

0.28.1 beta
- updated progpow-veil for started testnet
- lowered devfee on megabtx and megamec to default 1%

Hey there Boss thx a lot very nice job.

Would you be so kind as to look into adding support for ProgPow-Epic ,

$EPIC = Epic Cash, 3 algo MW coin, 21mill supply, great little project

With all the 4GB cards available, we need some decent work for them.

Here is their GitLab link :

https://gitlab.com/epiccash

SRBminer already supports them RandomX\CPU,

TTminer already support them on ProgPOW\nVidia

thx in advance for anything you can do Wink

jgonzi

member

Activity: 639

Merit: 19

Quote from: andrucrypt on October 14, 2020, 08:22:19 AM

Quote from: jgonzi on October 14, 2020, 04:20:27 AM

errors:
[11:19:22] GPU #0: GeForce RTX 3080 [busID: 2] [arch: sm86]
[11:19:22] threads: 1, intensity: 19, worksize: 64/1024, cu: 68, mem: 10018Mb
[11:19:24] use pool x25x.eu.mine.zergpool.com:3225 51.210.180.98
[11:19:24] Stratum set raw difficulty to 0.0800
[11:19:24] new job from x25x.eu.mine.zergpool.com:3225 diff 343.60M
[11:19:24] block: 1,090,847 job target: 0x0000000c7ff37fff
[11:19:24] Error CL_INVALID_KERNEL_ARGS when calling clEnqueueNDRangeKernel for kernel 'swift_64'
[11:19:26] Error CL_INVALID_KERNEL_ARGS when calling clEnqueueNDRangeKernel for kernel 'swift_64'
[11:19:28] Error CL_INVALID_KERNEL_ARGS when calling clEnqueueNDRangeKernel for kernel 'swift_64'
[11:19:30] Error CL_INVALID_KERNEL_ARGS when calling clEnqueueNDRangeKernel for kernel 'swift_64'
[11:19:32] Error CL_INVALID_KERNEL_ARGS when calling clEnqueueNDRangeKernel for kernel 'swift_64'

Error:
[11:16:44] initializing GPUs...
[11:16:45] NVIDIA(sm86) not fully optimized yet for chosen algorithm
[11:16:45] GPU #0: GeForce RTX 3080 [busID: 2] [arch: sm86]
[11:16:45] threads: 1, intensity: 19, worksize: 64/1024, cu: 68, mem: 10018Mb
[11:16:46] use pool xevan.eu.mine.zergpool.com:3739 51.210.180.98
[11:16:46] Stratum set raw difficulty to 12.0000
[11:16:46] new job from xevan.eu.mine.zergpool.com:3739 diff 201.33M
[11:16:46] block: 860,381 job target: 0x0000001555400000
[11:16:46] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'bmw_512_128_volatile', argument 3
[11:16:47] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'groestl_512_128', argument 3
[11:16:48] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'skein_512_128', argument 3
[11:16:49] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'jh_512_128', argument 3
[11:16:50] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'keccak_512_128', argument 3
[11:16:51] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'luffa_512_128', argument 3
[11:16:52] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'cubehash_512_128', argument 3
[11:16:53] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'shavite_512_128', argument 3

Error:
[11:21:15] NVIDIA(sm86) not fully optimized yet for chosen algorithm
[11:21:15] GPU #0: GeForce RTX 3080 [busID: 2] [arch: sm86]
[11:21:15] threads: 1, intensity: 19, worksize: 64/1024, cu: 68, mem: 10018Mb
[11:21:16] use pool megabtx.eu.mine.zergpool.com:3557 51.210.180.98
[11:21:16] Stratum set raw difficulty to 16.0000
[11:21:16] new job from megabtx.eu.mine.zergpool.com:3557 diff 268.44M
[11:21:16] block: 686,196 job target: 0x0000000ffff00000
[11:21:24] rejected(0/1) diff 2.11G GPU#0 (258 ms)
[11:21:24] reason: Invalid share
[11:21:29] new job from megabtx.eu.mine.zergpool.com:3557 diff 268.44M
[11:21:29] block: 686,196 job target: 0x0000000ffff00000
[11:22:03] rejected(0/2) diff 509.95M GPU#0 (423 ms)
[11:22:03] reason: Invalid share
[11:22:11] rejected(0/3) diff 465.45M GPU#0 (514 ms)
[11:22:11] reason: Invalid share
[11:22:14] Uptime: 0 days 00:00:59
[11:22:14] hashrate: 10s: 8870 60s: n/a 15m: n/a kH/s max: 8925 kH/s

All Megabtc Rejects...

This is known issue(and mentioned in first message), not all algorithms are working properly on NVIDIA gpu's. But thanks, I will check those errors in next release. What about megabtx, this one is strange, did you choose megabtx algorithm? Probably they broke backward compatibility, since on previous generations same kernels are working fine. If so, I will try to recompile them specifically for sm86 arch.

Many thanks I will try it as soon is in HiveOS...

andrucrypt

member

Activity: 720

Merit: 49

0.28.1 beta
- updated progpow-veil for started testnet
- lowered devfee on megabtx and megamec to default 1%

andrucrypt

member

Activity: 720

Merit: 49

Quote from: jgonzi on October 14, 2020, 04:20:27 AM

errors:
[11:19:22] GPU #0: GeForce RTX 3080 [busID: 2] [arch: sm86]
[11:19:22] threads: 1, intensity: 19, worksize: 64/1024, cu: 68, mem: 10018Mb
[11:19:24] use pool x25x.eu.mine.zergpool.com:3225 51.210.180.98
[11:19:24] Stratum set raw difficulty to 0.0800
[11:19:24] new job from x25x.eu.mine.zergpool.com:3225 diff 343.60M
[11:19:24] block: 1,090,847 job target: 0x0000000c7ff37fff
[11:19:24] Error CL_INVALID_KERNEL_ARGS when calling clEnqueueNDRangeKernel for kernel 'swift_64'
[11:19:26] Error CL_INVALID_KERNEL_ARGS when calling clEnqueueNDRangeKernel for kernel 'swift_64'
[11:19:28] Error CL_INVALID_KERNEL_ARGS when calling clEnqueueNDRangeKernel for kernel 'swift_64'
[11:19:30] Error CL_INVALID_KERNEL_ARGS when calling clEnqueueNDRangeKernel for kernel 'swift_64'
[11:19:32] Error CL_INVALID_KERNEL_ARGS when calling clEnqueueNDRangeKernel for kernel 'swift_64'

Error:
[11:16:44] initializing GPUs...
[11:16:45] NVIDIA(sm86) not fully optimized yet for chosen algorithm
[11:16:45] GPU #0: GeForce RTX 3080 [busID: 2] [arch: sm86]
[11:16:45] threads: 1, intensity: 19, worksize: 64/1024, cu: 68, mem: 10018Mb
[11:16:46] use pool xevan.eu.mine.zergpool.com:3739 51.210.180.98
[11:16:46] Stratum set raw difficulty to 12.0000
[11:16:46] new job from xevan.eu.mine.zergpool.com:3739 diff 201.33M
[11:16:46] block: 860,381 job target: 0x0000001555400000
[11:16:46] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'bmw_512_128_volatile', argument 3
[11:16:47] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'groestl_512_128', argument 3
[11:16:48] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'skein_512_128', argument 3
[11:16:49] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'jh_512_128', argument 3
[11:16:50] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'keccak_512_128', argument 3
[11:16:51] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'luffa_512_128', argument 3
[11:16:52] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'cubehash_512_128', argument 3
[11:16:53] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'shavite_512_128', argument 3

Error:
[11:21:15] NVIDIA(sm86) not fully optimized yet for chosen algorithm
[11:21:15] GPU #0: GeForce RTX 3080 [busID: 2] [arch: sm86]
[11:21:15] threads: 1, intensity: 19, worksize: 64/1024, cu: 68, mem: 10018Mb
[11:21:16] use pool megabtx.eu.mine.zergpool.com:3557 51.210.180.98
[11:21:16] Stratum set raw difficulty to 16.0000
[11:21:16] new job from megabtx.eu.mine.zergpool.com:3557 diff 268.44M
[11:21:16] block: 686,196 job target: 0x0000000ffff00000
[11:21:24] rejected(0/1) diff 2.11G GPU#0 (258 ms)
[11:21:24] reason: Invalid share
[11:21:29] new job from megabtx.eu.mine.zergpool.com:3557 diff 268.44M
[11:21:29] block: 686,196 job target: 0x0000000ffff00000
[11:22:03] rejected(0/2) diff 509.95M GPU#0 (423 ms)
[11:22:03] reason: Invalid share
[11:22:11] rejected(0/3) diff 465.45M GPU#0 (514 ms)
[11:22:11] reason: Invalid share
[11:22:14] Uptime: 0 days 00:00:59
[11:22:14] hashrate: 10s: 8870 60s: n/a 15m: n/a kH/s max: 8925 kH/s

All Megabtc Rejects...

This is known issue(and mentioned in first message), not all algorithms are working properly on NVIDIA gpu's. But thanks, I will check those errors in next release. What about megabtx, this one is strange, did you choose megabtx algorithm? Probably they broke backward compatibility, since on previous generations same kernels are working fine. If so, I will try to recompile them specifically for sm86 arch.

jgonzi

member

Activity: 639

Merit: 19

Error:
[11:21:15] NVIDIA(sm86) not fully optimized yet for chosen algorithm
[11:21:15] GPU #0: GeForce RTX 3080 [busID: 2] [arch: sm86]
[11:21:15] threads: 1, intensity: 19, worksize: 64/1024, cu: 68, mem: 10018Mb
[11:21:16] use pool megabtx.eu.mine.zergpool.com:3557 51.210.180.98
[11:21:16] Stratum set raw difficulty to 16.0000
[11:21:16] new job from megabtx.eu.mine.zergpool.com:3557 diff 268.44M
[11:21:16] block: 686,196 job target: 0x0000000ffff00000
[11:21:24] rejected(0/1) diff 2.11G GPU#0 (258 ms)
[11:21:24] reason: Invalid share
[11:21:29] new job from megabtx.eu.mine.zergpool.com:3557 diff 268.44M
[11:21:29] block: 686,196 job target: 0x0000000ffff00000
[11:22:03] rejected(0/2) diff 509.95M GPU#0 (423 ms)
[11:22:03] reason: Invalid share
[11:22:11] rejected(0/3) diff 465.45M GPU#0 (514 ms)
[11:22:11] reason: Invalid share
[11:22:14] Uptime: 0 days 00:00:59
[11:22:14] hashrate: 10s: 8870 60s: n/a 15m: n/a kH/s max: 8925 kH/s

All Megabtc Rejects...

jgonzi

member

Activity: 639

Merit: 19

errors:
[11:19:22] GPU #0: GeForce RTX 3080 [busID: 2] [arch: sm86]
[11:19:22] threads: 1, intensity: 19, worksize: 64/1024, cu: 68, mem: 10018Mb
[11:19:24] use pool x25x.eu.mine.zergpool.com:3225 51.210.180.98
[11:19:24] Stratum set raw difficulty to 0.0800
[11:19:24] new job from x25x.eu.mine.zergpool.com:3225 diff 343.60M
[11:19:24] block: 1,090,847 job target: 0x0000000c7ff37fff
[11:19:24] Error CL_INVALID_KERNEL_ARGS when calling clEnqueueNDRangeKernel for kernel 'swift_64'
[11:19:26] Error CL_INVALID_KERNEL_ARGS when calling clEnqueueNDRangeKernel for kernel 'swift_64'
[11:19:28] Error CL_INVALID_KERNEL_ARGS when calling clEnqueueNDRangeKernel for kernel 'swift_64'
[11:19:30] Error CL_INVALID_KERNEL_ARGS when calling clEnqueueNDRangeKernel for kernel 'swift_64'
[11:19:32] Error CL_INVALID_KERNEL_ARGS when calling clEnqueueNDRangeKernel for kernel 'swift_64'

Error:
[11:16:44] initializing GPUs...
[11:16:45] NVIDIA(sm86) not fully optimized yet for chosen algorithm
[11:16:45] GPU #0: GeForce RTX 3080 [busID: 2] [arch: sm86]
[11:16:45] threads: 1, intensity: 19, worksize: 64/1024, cu: 68, mem: 10018Mb
[11:16:46] use pool xevan.eu.mine.zergpool.com:3739 51.210.180.98
[11:16:46] Stratum set raw difficulty to 12.0000
[11:16:46] new job from xevan.eu.mine.zergpool.com:3739 diff 201.33M
[11:16:46] block: 860,381 job target: 0x0000001555400000
[11:16:46] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'bmw_512_128_volatile', argument 3
[11:16:47] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'groestl_512_128', argument 3
[11:16:48] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'skein_512_128', argument 3
[11:16:49] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'jh_512_128', argument 3
[11:16:50] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'keccak_512_128', argument 3
[11:16:51] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'luffa_512_128', argument 3
[11:16:52] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'cubehash_512_128', argument 3
[11:16:53] Error CL_INVALID_ARG_INDEX when calling clSetKernelArg for kernel 'shavite_512_128', argument 3

andrucrypt

member

Activity: 720

Merit: 49

Quote from: mrschyguy on October 11, 2020, 03:57:01 PM

@andrucrypt Hello, just wanted to thank you for your amazing work. Have been using it for x11k. Was wondering if there are plans to optimize nvida or 5700xt cards for x11k? Thank you again for your hard work. Our community greatly appreciates it.

Hi, I have no plans for optimizations for this kind of algorithms(all that x-family). A lot of hashfunctions are involved here, and they are not popular, so... Better to work on some new algorithms/etc. But if I have some time or an easy idea of optimization - I will do that

mrschyguy

newbie

Activity: 4

Merit: 0

@andrucrypt Hello, just wanted to thank you for your amazing work. Have been using it for x11k. Was wondering if there are plans to optimize nvida or 5700xt cards for x11k? Thank you again for your hard work. Our community greatly appreciates it.

andrucrypt

member

Activity: 720

Merit: 49

0.28.0 beta
- implemented progpow-veil for Veil(testnet)
- all --benchmark-* parameters will start benchmark, so no need to use additionally --benchmark
- one more fix for minotaur on nvidia
- should be fixed monitoring via nvml on newer nvidia drivers

andrucrypt

member

Activity: 720

Merit: 49

0.27.6 beta
- fixed issue with getting banned while mining veriblock on official node(this issue possible with other progpow pools too)
- tuned a bit minotaur for nvidia

andrucrypt

member

Activity: 720

Merit: 49

0.27.4 beta
- fixed incorrect work and high CPU load of x11k, minotaur and some other similar algorithms for nvidia
- fixed --watchdog for nvidia(now miner will close correctly)

0.27.5 beta
- fixed crash of some algorithms on nvidia
- further fixes to minotaur on nvidia

andrucrypt

member

Activity: 720

Merit: 49

Quote from: BoozyTalking on September 29, 2020, 01:45:22 AM

Hi, @andrucrypt! Qureno think they defeated Wildrig Roll Eyes

Quote

Qureno 0.13.0.2

We implemented 17 unique algorithms inside the blockchain.
The kernel will choose which algorithm to use for the future block.
Random selection of one of the unique algorithms: x33, x34, x35, x36, x37, x38, x39, x40, x41, x42, x43, x44, x45, x46, x47, x48, x49

Date of the change of algorithm: 10/01/2020 @ 12:00am (UTC)

What do you think about this?

I think this is still possible to do gpu mining, but I won't, better to work on something else instead ) Especially if they want to close the source code(sic!) xD

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