Pages:
Author

Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 16. (Read 60004 times)

hero member
Activity: 677
Merit: 500
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.
jr. member
Activity: 200
Merit: 3
miniZ 1.7x3 & 1.7x4 fails mining Ethash @ ProHashing

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!
jr. member
Activity: 95
Merit: 2

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
member
Activity: 690
Merit: 17
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
member
Activity: 690
Merit: 17
miniZ 1.7x3 & 1.7x4 fails mining Ethash @ ProHashing

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
hero member
Activity: 677
Merit: 500
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.

jr. member
Activity: 200
Merit: 3
miniZ 1.7x3 & 1.7x4 fails mining Ethash @ ProHashing

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

hero member
Activity: 677
Merit: 500
Hi!  Thanks for the new release!

I am still not able to get the --quit-disconnect to work.  When the stratum disconnects, miniZ just hangs.

I also tried to use the --jobtimeout=10 to see if it will help force a disconnect and terminate in case the pool isn't disconnecting.
(...)
Hi guytechie,

Thanks a lot for the feedback!

The --quit disconnect was not working if the pool was down right from the beginning. When the pool is down and we start miniZ it can take a bit longer to log a warning/error message.
It was hanging a bit longer trying to resolve the connection, and then was giving an error message. Could this be what it was happening? Otherwise it was working well here.

We added a version (v1.7x4 here) with improvement for the --quit-disconnect option that allows the pool to disconnect at the beginning.
Could you try it out and see if it resolves the issue?

Cheers,
miniZ

It is working now!  Thanks!

member
Activity: 690
Merit: 17
Hi!  Thanks for the new release!

I am still not able to get the --quit-disconnect to work.  When the stratum disconnects, miniZ just hangs.

I also tried to use the --jobtimeout=10 to see if it will help force a disconnect and terminate in case the pool isn't disconnecting.
(...)
Hi guytechie,

Thanks a lot for the feedback!

The --quit disconnect was not working if the pool was down right from the beginning. When the pool is down and we start miniZ it can take a bit longer to log a warning/error message.
It was hanging a bit longer trying to resolve the connection, and then was giving an error message. Could this be what it was happening? Otherwise it was working well here.

We added a version (v1.7x4 here) with improvement for the --quit-disconnect option that allows the pool to disconnect at the beginning.
Could you try it out and see if it resolves the issue?

Cheers,
miniZ
hero member
Activity: 677
Merit: 500
Hi!  Thanks for the new release!

I am still not able to get the --quit-disconnect to work.  When the stratum disconnects, miniZ just hangs.

I also tried to use the --jobtimeout=10 to see if it will help force a disconnect and terminate in case the pool isn't disconnecting.



Since this is a script I'm working on that is suppose to go to the next line, I have the commands like this:

./miniZ --templimit 95 --intensity 100 --latency --tempunits C -cd 0 --telemetry 4069 --url [email protected]:2144 --algo 144,5 --pers auto --ocX --retries=0 --retrydelay=0 --jobtimeout=10 --quit-disconnect --pass tmp-temp,c=BTC,equihash192,equihash125,equihash144

./miniZ --templimit 95 --intensity 100 --latency --tempunits C -cd 0 --telemetry 4069 --url [email protected]:2192 --algo 192,7 --pers auto --ocX --retries=0 --retrydelay=0 --jobtimeout=10 --quit-disconnect --pass tmp-temp,c=BTC,equihash192,equihash125,equihash144

./miniZ --templimit 95 --intensity 100 --latency --tempunits C -cd 0 --telemetry 4069 --url [email protected]:2125 --algo 125,4 --pers auto --ocX --retries=0 --retrydelay=0 --jobtimeout=10 --quit-disconnect --pass tmp-temp,c=BTC,equihash192,equihash125,equihash144

Based on the password, the pool will disconnect if what's listed in the password is not the most profitable.  So in this example, it disconnect until you're mining the most profitable between equihash192, equihash125, and equihash144.

But here, when it's not the most profitable, it would just hang instead of disconnect, exit, then moving to the next line to attempt mining that algo.
member
Activity: 690
Merit: 17
Hi everyone,

You can find miniZ version v1.7x3 here.

Changelog:

* Fixed major issues handling connections on Windows.
* Added kernel for ETH mining with the RTX 30XX GPUs.
* Improved stale shares for all algos.


For additional information check our Usage or FAQ pages.

Let us know how it goes!

Happy mining!
member
Activity: 690
Merit: 17
Hey,

just wanted to test the new ETH algo on NiceHash, but wasnt able to run miniZ. I get this error:



Its the newest Win10 pro 2H20 with 461.40 driver. What is the deviceZ code? (Btw. the T** miner also have such a problem with 3070 and wont start, but the G** miner is running smooth. Maybe its the same strange error here?).
Hi joseph32,
Sorry about this.
We'll add a version with the kernel for the RTX 30XX as soon as possible.
Thank you for the feedback!
Cheers,
miniZ
member
Activity: 690
Merit: 17
Hi cryptosize,
You can already find a FAQ for ETH Smiley
Thank you for your feedback!
Cheers,
miniZ
member
Activity: 690
Merit: 17
Thanks for adding ethash, already testing  Cheesy
Hi RoninAlek,
Thanks. It is still a beta version.
We found some issues in the Windows version that affect mining.
We're working to release a fix asap.
Cheers,
miniZ
member
Activity: 418
Merit: 21
Hey,

just wanted to test the new ETH algo on NiceHash, but wasnt able to run miniZ. I get this error:



Its the newest Win10 pro 2H20 with 461.40 driver. What is the deviceZ code? (Btw. the T** miner also have such a problem with 3070 and wont start, but the G** miner is running smooth. Maybe its the same strange error here?).
sr. member
Activity: 1666
Merit: 310
newbie
Activity: 26
Merit: 1
Thanks for adding ethash, already testing  Cheesy
member
Activity: 690
Merit: 17
Hi everyone,

Thank you for all your patience and for using miniZ miner! Sorry for making you wait a little longer than usual for the new release.


A new miniZ v1.7x2 version is out with major news - we added support for the ProgPoW family algos, and Ethash (beta)!
Also, we added a nice alternative looking for miniZ. Smiley

Please find miniZ v1.7x2 version @ Download page.
   
Changelog:

 * Added support for:
    - Ravencoin (RVN), Zelantus (ZELS)
    - Super Zero (SERO)
    - Zano (ZANO)
    - Veil (VEIL)
    - Veriblock (VBK)

    Fee is 1% of mining time.
 * Added support for ethash - ETH/ETC (beta)!
    Fee 0.75% of mining time.
 * Fixed 192,7 mining.
 * Minor improvements for 210,9 and 96,5.
 * Removed support for 150,5,3.
 * Fixed colours on Windows 7 terminal.
 * Improved overall stability.
 * --smart-pers enabled by default (use —smart-pers=0 do disable). miniZ will adjust the pers string as needed.
 * Fixed hashrate reporting for 96,5.
 * Added --coolui option for alternative interface.
 * Added --quit-disconnect to force the miner to quit when the connection drops (or when quit file is detected).
 
 You can check some of our Kawpow testing conditions here. See also FAQ - How to mine XXX? 
 
Remember to try --oc1/--oc2/--ocX options for optimum performance.
 
Download miniZ v1.7x2 version here.

For additional information check our Usage or FAQ pages. 
 
Follow us
On Twitter

Let us know how it goes!

Happy mining!
member
Activity: 690
Merit: 17
hi any have hashrate for Equihash 192,7 (Equihash Heavy):

FOR RTX CARDS 3080 & 3090 really important for me any1  cheers
Hi hurr1cane,

We updated the 192,7 table with values for the RTX 3090.

Unfortunately we do not have values for the RTX 3080.

The versions later than v1.5t may have stopped working for the 192,7.
You can still use the last version to test the performance, but we do not recommend it for production.

We are preparing the new version that will fix this. We're finalising testing and it should be out very soon.

Cheers,
miniZ
member
Activity: 690
Merit: 17
Hi.  Any updates?
Hi guytechie,
Sorry for such a late response.

We ended up making major changes.
Currently, we are finalising testing. We expect to release a new version in no more than two days.

Thank you for your patience.
Cheers,
miniZ
Hi guytechie,

We are still performing some tests.
Sorry about the delays!

Cheers,
miniZ
Pages:
Jump to: