miniZv2.3c Equihash144,5 125,4 210,9 150,5 192,7 Beam ProgPoW Ethash CFX KLS PYI

[miniZ]

Hi, I am getting Invalid job parameters error when mining Equihash210.  I am using --pers auto and it defaults correctly to AION0PoW and this is on miningrigrentals; gminer is working fine.

Hi platinum4,
 
When adding the pool in "Pool Configuration" tab leave "Pers value (-pers)" blank.

However, for now, you need to add --pers or --par to the command line. Example:

Code:

miniZ.exe --url=WorkerLogin@us-central01.miningrigrentals.com:3333 --pass WorkerPass --pers AION0PoW

Let us know if this helped.
Thanks for the feedback, this may help other miner too.
Cheers

[1714714817]

1714714817

[1714714817]

1714714817

[1714714817]

1714714817

[1714714817]

1714714817

[platinum4]

https://i.imgur.com/QsxG1jd.png

https://i.imgur.com/lyb4nQ8.png

Same problem

[miniZ]

https://i.imgur.com/QsxG1jd.png

https://i.imgur.com/lyb4nQ8.png

Same problem

Hi platinum4,

It looks that the problem is not the command line. We tested it with our worker and it is OK.
Your worker name and ID should also be OK, otherwise the error would be something like " worker not authorized: platinum4.000000".

So we think that the problem might be at Pool configuration @ miningrigrentals website. Did you check if the field we mentioned before was left unfilled?
When adding the pool in "Pool Configuration" tab leave "Pers value (-pers)" blank. See example in image  https://i.ibb.co/bRTP7Lk/image1.png

Could you confirm this?
Cheers

[platinum4]

Oh OK I can't change that because that is the renter, thanks.

[miniZ]

Oh OK I can't change that because that is the renter, thanks.

Hi platinum4,
sorry, this will be resolved in the next version.
We expect to release it soon (a week or less) with improvements for 210,9 - AION.
Cheers

[UselessGuru]

miniZ.exe --par=192,7 --smart-pers --ocX --url *************.*****@asia.equihash-hub.miningpoolhub.com:17029 --pass x --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.6w4 ************
Algo:           EQ[192,7] [smart-pers]
Pool#0:         user[*************.*****]
                server[asia.equihash-hub.miningpoolhub.com] port[17029] ssl[no] pers[BgoldPoW]
Telemetry:      [http://localhost:4003]
Optimisation:   ocX[0]
Temp. limit:    [90°C]
miniZ<192,7>[11:0:00:5167]: Selecting GPU#0[0] GeForce GTX 1660 SUPER
[FATAL  ] Cannot load deviceZ code.
[INFO   ] Disconnecting from asia.equihash-hub.miningpoolhub.com
[INFO   ]asia.equihash-hub.miningpoolhub.com Stopping miner

Hi UselessGuru,

miniZ v1.6w4 is only to be used with RTX 30XX.

You'll need to use v1.6w2, for now.

Next version, v1.6x, will support all GPUs.

Thank you for the feedback.
Cheers

Thank you for your feedback..
>> miniZ v1.6w4 is only to be used with RTX 30XX.
Cannot load deviceZ code.
It is just odd that it sometimes works...

[platinum4]

Oh OK I can't change that because that is the renter, thanks.

Hi platinum4,
sorry, this will be resolved in the next version.
We expect to release it soon (a week or less) with improvements for 210,9 - AION.
Cheers

Can you put this on beta page?  I'd like to test it on a rig of 1070s that are rented for 2 days.

@UselessGuru Hi again -- I am using 16w4 on CUDA10 for Pascal/Turing just fine.  Don't use the CUDA11.1 version but use the CUDA10 from the beta page.

[sxemini]

@miniZ

The Solution per second in the API is the average speed right?
Can you add Solution Average and Solution per second for the realtime hashrate.

Makes more sense to see the realtime hashrate over API.

Because a RIG goes down or slow down after 50 Day´s, i will recognize the slow down after days, because the average speed will go down very slow.

[miniZ]

Hi everyone,

Thank you for all your feedback and for using miniZ miner!

A new miniZ v1.6x version is out with major improvements for 210,9 algorithm - AION.

Please find miniZ v1.6x version @ Download page.
  
Changelog:

 * 210,9 major improvements: up to 8% depending on GPU.
 * 144,5 improved hashrate for the RTX 30XX GPUs.
 * Added support for SM_30 (Kepler) devices.
 * Fixed issues with --pers on MiningRigRentals
 * Combined CUDA 8/10/11 versions into one (same) executable.
 
You can check some of our 210,9 testing conditions here. See also FAQ - How to mine AION?  
  
Remember to try --oc1--oc2--ocX options for optimum performance.
 
Download miniZ version v1.6x here.

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

Happy miniZ mining!

[miniZ]

Thank you for your feedback..
>> miniZ v1.6w4 is only to be used with RTX 30XX.
Cannot load deviceZ code.
It is just odd that it sometimes works...

Can you put this on beta page?  I'd like to test it on a rig of 1070s that are rented for 2 days.

@UselessGuru Hi again -- I am using 16w4 on CUDA10 for Pascal/Turing just fine.  Don't use the CUDA11.1 version but use the CUDA10 from the beta page.

Hi UselessGuru, platinum4,
We've just released a new version v1.6x

Could you try it out and see if it works for you?
Cheers

[miniZ]

@miniZ

The Solution per second in the API is the average speed right?
Can you add Solution Average and Solution per second for the realtime hashrate.

Makes more sense to see the realtime hashrate over API.

Because a RIG goes down or slow down after 50 Day´s, i will recognize the slow down after days, because the average speed will go down very slow.

Hi sxemini,

The api speed_sps is a 3h average.

If you want you can read speed_is (iteration rate, 3 minutes average) and multiply by 2.

You could also add --avg1=period_in_seconds to the miniZ command line. This way you can adjust as you wish.

Let us know if this helps.
Cheers

[tymeksm]

Hello

Question about new cuda8/10/11 support:

Example output:

Code:

$ ./miniZ -ci
Number of miniZ CUDA[8.0] driver[11.10] devices found: 6
  #0 GeForce GTX 1070    | SM version: 6.1 | SM count: 15 | cores: 1920 | Memory:  3.767GB | BusID: 0000:01:00.0
  #1 GeForce GTX 1070    | SM version: 6.1 | SM count: 15 | cores: 1920 | Memory:  3.767GB | BusID: 0000:03:00.0
  #2 GeForce GTX 1070    | SM version: 6.1 | SM count: 15 | cores: 1920 | Memory:  3.767GB | BusID: 0000:06:00.0
  #3 GeForce GTX 1070    | SM version: 6.1 | SM count: 15 | cores: 1920 | Memory:  3.767GB | BusID: 0000:07:00.0
  #4 GeForce GTX 1070    | SM version: 6.1 | SM count: 15 | cores: 1920 | Memory:  3.767GB | BusID: 0000:08:00.0
  #5 GeForce GTX 1070    | SM version: 6.1 | SM count: 15 | cores: 1920 | Memory:  3.767GB | BusID: 0000:09:00.0

tells me, that cuda8 libraries are used, yes?

I have Ubuntu20 with no any cuda libraries installed. Just NVIDIA driver 455.45.01 installed.
As I understand the miniz binary from 1.6x has integrated 3 versions of cuda libraries. How to make the binary use cuda10 or 11 libraries?
Or is it only used for newer NV GPUs that required newer cuda libraries?

[sxemini]

@miniZ

The Solution per second in the API is the average speed right?
Can you add Solution Average and Solution per second for the realtime hashrate.

Makes more sense to see the realtime hashrate over API.

Because a RIG goes down or slow down after 50 Day´s, i will recognize the slow down after days, because the average speed will go down very slow.

Hi sxemini,

The api speed_sps is a 3h average.

If you want you can read speed_is (iteration rate, 3 minutes average) and multiply by 2.

You could also add --avg1=period_in_seconds to the miniZ command line. This way you can adjust as you wish.

Let us know if this helps.
Cheers

Thanks --avg1 works. I need this for Awesomeminer. Maybe you can change your usage list on your page? So many commands are missing there.
--mode
--avg1

and more you explained some times in this thread, but didn´t find it in your usage commandline list.

[miniZ]

Hello

Question about new cuda8/10/11 support:

Example output:

Code:

$ ./miniZ -ci
Number of miniZ CUDA[8.0] driver[11.10] devices found: 6
  #0 GeForce GTX 1070    | SM version: 6.1 | SM count: 15 | cores: 1920 | Memory:  3.767GB | BusID: 0000:01:00.0
  #1 GeForce GTX 1070    | SM version: 6.1 | SM count: 15 | cores: 1920 | Memory:  3.767GB | BusID: 0000:03:00.0
  #2 GeForce GTX 1070    | SM version: 6.1 | SM count: 15 | cores: 1920 | Memory:  3.767GB | BusID: 0000:06:00.0
  #3 GeForce GTX 1070    | SM version: 6.1 | SM count: 15 | cores: 1920 | Memory:  3.767GB | BusID: 0000:07:00.0
  #4 GeForce GTX 1070    | SM version: 6.1 | SM count: 15 | cores: 1920 | Memory:  3.767GB | BusID: 0000:08:00.0
  #5 GeForce GTX 1070    | SM version: 6.1 | SM count: 15 | cores: 1920 | Memory:  3.767GB | BusID: 0000:09:00.0

tells me, that cuda8 libraries are used, yes?

I have Ubuntu20 with no any cuda libraries installed. Just NVIDIA driver 455.45.01 installed.
As I understand the miniz binary from 1.6x has integrated 3 versions of cuda libraries. How to make the binary use cuda10 or 11 libraries?
Or is it only used for newer NV GPUs that required newer cuda libraries?

Hi tymeksm,
 Yes, miniZ integrates cuda 8/10/11. You only need to have the driver installed.
Cuda 8 is the minimum Cuda version that miniZ supports.

In the next version there will be a more clear message.
Something like this:
Number of miniZ CUDA>=[8.0] using driver CUDA[10.20] devices found: 1

Thank you for the feedback!
Cheers

[miniZ]

Thanks --avg1 works. I need this for Awesomeminer. Maybe you can change your usage list on your page? So many commands are missing there.
--mode
--avg1

and more you explained some times in this thread, but didn´t find it in your usage commandline list.

Hi sxemini,
Good that it worked for you.

You're right, we'll review a few things on the website  (and --help) in the next few days.
For information on --mode see FAQ

Thanks!
Cheers

[UselessGuru]

Thank you for your feedback..
>> miniZ v1.6w4 is only to be used with RTX 30XX.
Cannot load deviceZ code.
It is just odd that it sometimes works...

Can you put this on beta page?  I'd like to test it on a rig of 1070s that are rented for 2 days.

@UselessGuru Hi again -- I am using 16w4 on CUDA10 for Pascal/Turing just fine.  Don't use the CUDA11.1 version but use the CUDA10 from the beta page.

Hi UselessGuru, platinum4,
We've just released a new version v1.6x

Could you try it out and see if it works for you?
Cheers

The issues I had have been fixed.
1.6x is working fine here - thank you!

[tymeksm]

In the next version there will be a more clear message.
Something like this:
Number of miniZ CUDA>=[8.0] using driver CUDA[10.20] devices found: 1

Thank you. Now it's clear ;-)

[tymeksm]

Hi again

I found the problem with API..but do not know whats the reason.

On Ubuntu 16 and 18 works ok, but under Ubuntu 20 there is a problem...but only sometimes - not stable API

I use this method to retrive JSON data:
curl -s http://127.0.0.1:20000/getstat

but under ubuntu20 this act like this:
- very often give just no output (empty string)
in this same time respond with HTML page if request with:
curl -s http://127.0.0.1:20000/
gives full html page
- after some period of time api freezes and hangs every connection (both of avobe). Must enter Ctrl+C to back to bash
- only sometimes after few miner restarts work ok, and respond with JSON data.

can you help?

[miniZ]

Hi again

I found the problem with API..but do not know whats the reason.

On Ubuntu 16 and 18 works ok, but under Ubuntu 20 there is a problem...but only sometimes - not stable API

I use this method to retrive JSON data:
curl -s http://127.0.0.1:20000/getstat

but under ubuntu20 this act like this:
- very often give just no output (empty string)
in this same time respond with HTML page if request with:
curl -s http://127.0.0.1:20000/
gives full html page
- after some period of time api freezes and hangs every connection (both of avobe). Must enter Ctrl+C to back to bash
- only sometimes after few miner restarts work ok, and respond with JSON data.

can you help?

Hi tymeksm,

Could you try the following :
curl http://localhost:20000/getstat -s --http0.9

Curl has been modified in Ubuntu 20.

Let us know if it works for you.

Thank you for your question.
This may help other miners too.

Cheers

[cryptosize]

With the latest nVidia driver (460.79) I get this on Windows 10 and latest miniZ:

"Cannot read health status! (is libnvidia-ml.so installed?): No such file or directory"

"Sol/W=inf"

457.51 worked fine.

What gives?