Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 14. (Read 59063 times)
April 10, 2021, 10:12:59 PM
125,4 is not working on RTX 3060Ti, driver 465.89
March 26, 2021, 04:51:40 PM
Hi miniZ,
i have slower speeds on my testcard GTX970 mining beamhash3. At version 1.6v3 i get up to 9 hashes, but all newer versions i only get around 4 - 5 hash. I run --ocX several times, but it stands on 4 -5 hash.
Hi sxemini,i have slower speeds on my testcard GTX970 mining beamhash3. At version 1.6v3 i get up to 9 hashes, but all newer versions i only get around 4 - 5 hash. I run --ocX several times, but it stands on 4 -5 hash.
Thanks for letting us know.
We may have changed the kernel without realising that it was affecting those GPUs.
Could you let us know which kernel was miniZ running with your GPU, with version 1.6v3, when you got 9 hash?
You can use --show-mode to see this information in the log output.
Cheers,
miniZ
Hey sorry for the late response. I use mode 0 for my GTX970.
Hi sxemini,
Thanks for the feedback!
We'll try to fix this in the next release.
Cheers,
miniZ
March 26, 2021, 04:51:09 PM
RTX3060Ti 8GB
RTX3060 12GB
anyone try equihash 210,9 ?
RTX3060 12GB
anyone try equihash 210,9 ?
Hi igotek,
Although we did not test on that specific model.
It should work well with all RTX 30XX
Let us know how it works for you.
Cheers,
miniZ
March 25, 2021, 07:51:59 AM
Hi miniZ,
i have slower speeds on my testcard GTX970 mining beamhash3. At version 1.6v3 i get up to 9 hashes, but all newer versions i only get around 4 - 5 hash. I run --ocX several times, but it stands on 4 -5 hash.
Hi sxemini,i have slower speeds on my testcard GTX970 mining beamhash3. At version 1.6v3 i get up to 9 hashes, but all newer versions i only get around 4 - 5 hash. I run --ocX several times, but it stands on 4 -5 hash.
Thanks for letting us know.
We may have changed the kernel without realising that it was affecting those GPUs.
Could you let us know which kernel was miniZ running with your GPU, with version 1.6v3, when you got 9 hash?
You can use --show-mode to see this information in the log output.
Cheers,
miniZ
Hey sorry for the late response. I use mode 0 for my GTX970.
March 24, 2021, 08:22:56 PM
RTX3060Ti 8GB
RTX3060 12GB
anyone try equihash 210,9 ?
RTX3060 12GB
anyone try equihash 210,9 ?
March 16, 2021, 04:28:41 PM
Hi miniZ,
i have slower speeds on my testcard GTX970 mining beamhash3. At version 1.6v3 i get up to 9 hashes, but all newer versions i only get around 4 - 5 hash. I run --ocX several times, but it stands on 4 -5 hash.
Hi sxemini,i have slower speeds on my testcard GTX970 mining beamhash3. At version 1.6v3 i get up to 9 hashes, but all newer versions i only get around 4 - 5 hash. I run --ocX several times, but it stands on 4 -5 hash.
Thanks for letting us know.
We may have changed the kernel without realising that it was affecting those GPUs.
Could you let us know which kernel was miniZ running with your GPU, with version 1.6v3, when you got 9 hash?
You can use --show-mode to see this information in the log output.
Cheers,
miniZ
March 16, 2021, 04:25:42 PM
Sorry for the late response. I don't check back that often.
It's better, but still getting "Stale share: Invalid job id" every so often.
Indeed it looks better, but it would be necessary a long term statistic to understand if the number of stale jobs falls within an acceptable range of values.
We suggest you to run miniZ with --show-shares to show submitted/stale/rejected shares.
We'll continue to investigate this. (You're mining to zpool.ca right?)
Thank your for the update!
Cheers,
miniZ
March 16, 2021, 09:02:54 AM
Hi miniZ,
i have slower speeds on my testcard GTX970 mining beamhash3. At version 1.6v3 i get up to 9 hashes, but all newer versions i only get around 4 - 5 hash. I run --ocX several times, but it stands on 4 -5 hash.
i have slower speeds on my testcard GTX970 mining beamhash3. At version 1.6v3 i get up to 9 hashes, but all newer versions i only get around 4 - 5 hash. I run --ocX several times, but it stands on 4 -5 hash.
March 16, 2021, 08:51:00 AM
Sorry I typed wrong in the forum. I did use oc2, not ocx2. It is better with --cleanjobs and stales=99. However, it doesn't report the hashrate on zpool's dashboard for some weird reason.
Hi guytechie,
It is better not to use --cleanjobs.
It works on very few pools and with the last version of miniZ there is no benefit in using it. It can cause high number of invalid shares. We will remove this option on the next version.
Could you try again without this option and let us know if the issue is solved? We are not able to reproduce the same problem.
Thanks!
Cheers,
miniZ
Sorry for the late response. I don't check back that often.
It's better, but still getting "Stale share: Invalid job id" every so often.
March 08, 2021, 07:27:22 PM
The problem is, if I have a wallet with "." or an email address. This happens for MiningRigRentals, for example. We need
So, either, you allow using url-encoded characters, or you use everything after the last dot, or you come back to separate username / workername parameters.
Thank you for your message.
We think we understand your request and will implement it on the next build.
Cheers,
miniZ
March 08, 2021, 07:26:16 PM
Sorry I typed wrong in the forum. I did use oc2, not ocx2. It is better with --cleanjobs and stales=99. However, it doesn't report the hashrate on zpool's dashboard for some weird reason.
Hi guytechie,
It is better not to use --cleanjobs.
It works on very few pools and with the last version of miniZ there is no benefit in using it. It can cause high number of invalid shares. We will remove this option on the next version.
Could you try again without this option and let us know if the issue is solved? We are not able to reproduce the same problem.
Thanks!
Cheers,
miniZ
March 08, 2021, 11:45:14 AM
Hi,
we need (or is there already?) a way to specify the workername, especially important for Ethash and all ProgPow algorithms. MiniZ seems to always use the current machine name and add it to the username. This works for some, but not for all pools.
RBM
We are not sure we understand your question.
You can specify the worker name.
Generically the command line is, for example:
miniZ.exe --url=YourWallet.Workername@PoolServer:PortNumber --log --extra
Does this help?
You can find more specific examples in out FAQ page.
Cheers,
miniZ
The problem is, if I have a wallet with "." or an email address. This happens for MiningRigRentals, for example. We need
So, either, you allow using url-encoded characters, or you use everything after the last dot, or you come back to separate username / workername parameters.
March 08, 2021, 09:35:36 AM
I stated too early. It works as far as disconnecting correctly, but it would start giving stale shares after a while (zpool.ca on 192,7). Not sure why. Happens in Windows and Linux both using latest drivers. Not OC'd.
Hi guytechie,The stales might be related to ocx, we will investigate.
For now, if you know in advance what is the best mode, it is best to just add it to the command line using --mode.
Thank you for the feedback!
Cheers,
miniZ
Hi miniZ. Ocx1 doesn't work, but ocx2 it works. However, even setting it manually to ocx2 I get stales after a few good shares.
Update: Nevermind, they seem to be stale shares invalid job I'd. But it still stays 100% and green.
Regarding the oc options, it is best to clarify that the ocx option runs a few available miniZ kernels and chooses the one that performs best. Then --oc1 or --oc2 (not ocx1 or ocx2!) will set a specific kernel mode for the GPU, these kernels were found to perform best under certain oc settings. It may work for you, but if you feel that it is not optimal for your settings you can run ocx.
Regarding the stale share issue, could you paste here your command line? Are you running miniZ with --cleanjobs option?
If you are getting too many stale shares we need to check it out.
Thanks!
Cheers,
miniZ
Sorry I typed wrong in the forum. I did use oc2, not ocx2. It is better with --cleanjobs and stales=99. However, it doesn't report the hashrate on zpool's dashboard for some weird reason.
March 05, 2021, 01:54:09 PM
I stated too early. It works as far as disconnecting correctly, but it would start giving stale shares after a while (zpool.ca on 192,7). Not sure why. Happens in Windows and Linux both using latest drivers. Not OC'd.
Hi guytechie,The stales might be related to ocx, we will investigate.
For now, if you know in advance what is the best mode, it is best to just add it to the command line using --mode.
Thank you for the feedback!
Cheers,
miniZ
Hi miniZ. Ocx1 doesn't work, but ocx2 it works. However, even setting it manually to ocx2 I get stales after a few good shares.
Update: Nevermind, they seem to be stale shares invalid job I'd. But it still stays 100% and green.
Regarding the oc options, it is best to clarify that the ocx option runs a few available miniZ kernels and chooses the one that performs best. Then --oc1 or --oc2 (not ocx1 or ocx2!) will set a specific kernel mode for the GPU, these kernels were found to perform best under certain oc settings. It may work for you, but if you feel that it is not optimal for your settings you can run ocx.
Regarding the stale share issue, could you paste here your command line? Are you running miniZ with --cleanjobs option?
If you are getting too many stale shares we need to check it out.
Thanks!
Cheers,
miniZ
March 05, 2021, 01:52:34 PM
Hi,
we need (or is there already?) a way to specify the workername, especially important for Ethash and all ProgPow algorithms. MiniZ seems to always use the current machine name and add it to the username. This works for some, but not for all pools.
RBM
We are not sure we understand your question.
You can specify the worker name.
Generically the command line is, for example:
miniZ.exe --url=YourWallet.Workername@PoolServer:PortNumber --log --extra
Does this help?
You can find more specific examples in out FAQ page.
Cheers,
miniZ
March 04, 2021, 09:17:27 AM
I stated too early. It works as far as disconnecting correctly, but it would start giving stale shares after a while (zpool.ca on 192,7). Not sure why. Happens in Windows and Linux both using latest drivers. Not OC'd.
Hi guytechie,The stales might be related to ocx, we will investigate.
For now, if you know in advance what is the best mode, it is best to just add it to the command line using --mode.
Thank you for the feedback!
Cheers,
miniZ
Hi miniZ. Ocx1 doesn't work, but ocx2 it works. However, even setting it manually to ocx2 I get stales after a few good shares.
Update: Nevermind, they seem to be stale shares invalid job I'd. But it still stays 100% and green.
March 03, 2021, 12:47:05 PM
miniZ 1.7x3 & 1.7x4 fails mining Ethash @ ProHashing
Other pools, e.g. NiceHash are working with miniZ
GPU is a GTX 1660 Super 6GB
Code:
miniZ.exe --par=Ethash --ocX --url ##################@prohashing.com:3339 --pass a=Ethash,m=pps,n=############## --jobtimeout=900 --retries=99 --retrydelay=1 --stat-int 10 --latency --extra --tempunits C --show-pers --fee-time=60 --telemetry 4003 --cuda-devices 0
************ miniZ v1.7x4 ************
Algo: EQ[ethash] [smart-pers]
Pool#0: user[########################.#########]
server[prohashing.com] port[3339] ssl[no] pers[]
Telemetry: [http://localhost:4003]
Optimisation: ocX[0]
Temp. limit: [90°C]
[INFO ] Mining fee set to 0.75%
miniZ[49:0:00.0:5008]: Selecting GPU#0[0] GeForce GTX 1660 SUPER
[FATAL ] GPU[0]: CUDA error 77 'an illegal memory access was encountered' in line 824
Other pools, e.g. NiceHash are working with miniZ
GPU is a GTX 1660 Super 6GB
Hi UselessGuru,
Thank you for your message!
For now you need to add stratum1 to the url, in the command line:
--url=stratum1://[email protected]:3339
In the next release this will not be necessary anymore.
Cheers,
miniZ
Thank you!
March 03, 2021, 06:39:00 AM
Hi,
we need (or is there already?) a way to specify the workername, especially important for Ethash and all ProgPow algorithms. MiniZ seems to always use the current machine name and add it to the username. This works for some, but not for all pools.
RBM
March 02, 2021, 08:00:28 PM
I stated too early. It works as far as disconnecting correctly, but it would start giving stale shares after a while (zpool.ca on 192,7). Not sure why. Happens in Windows and Linux both using latest drivers. Not OC'd.
Hi guytechie,The stales might be related to ocx, we will investigate.
For now, if you know in advance what is the best mode, it is best to just add it to the command line using --mode.
Thank you for the feedback!
Cheers,
miniZ
March 02, 2021, 07:55:41 PM
miniZ 1.7x3 & 1.7x4 fails mining Ethash @ ProHashing
Other pools, e.g. NiceHash are working with miniZ
GPU is a GTX 1660 Super 6GB
Code:
miniZ.exe --par=Ethash --ocX --url ##################@prohashing.com:3339 --pass a=Ethash,m=pps,n=############## --jobtimeout=900 --retries=99 --retrydelay=1 --stat-int 10 --latency --extra --tempunits C --show-pers --fee-time=60 --telemetry 4003 --cuda-devices 0
************ miniZ v1.7x4 ************
Algo: EQ[ethash] [smart-pers]
Pool#0: user[########################.#########]
server[prohashing.com] port[3339] ssl[no] pers[]
Telemetry: [http://localhost:4003]
Optimisation: ocX[0]
Temp. limit: [90°C]
[INFO ] Mining fee set to 0.75%
miniZ[49:0:00.0:5008]: Selecting GPU#0[0] GeForce GTX 1660 SUPER
[FATAL ] GPU[0]: CUDA error 77 'an illegal memory access was encountered' in line 824
Other pools, e.g. NiceHash are working with miniZ
GPU is a GTX 1660 Super 6GB
Hi UselessGuru,
Thank you for your message!
For now you need to add stratum1 to the url, in the command line:
--url=stratum1://[email protected]:3339
In the next release this will not be necessary anymore.
Cheers,
miniZ
Jump to: