Pages:
Author

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

newbie
Activity: 32
Merit: 0
I think there is a problem with 1.5t version.  Huh

Around 2. Feb I updated to 1.5t version, and from then 3 times I got one card "minining" with 0 Sol/s (or 0 point something).
First time I thought that it could be faulty pci-e riser, they are almost 2 years old, then I restated miner with same setting (also same OC) and then again after like 12-24 hours different card drop to 0 Sol/s.

Then I lower OC settings to confirm if it's something wrong with cards, and then after almost 2 days 3rd card drop to 0 Sol/s, in all cases power consumption also dropped to idle.

All 3 cars are GTX 1080, in a rig with 1x 1080ti + 5x  1080, with fee-time set to 40 sec and OC1 but later I saw that that is not supported on 1080.

So I reverted to 1.5s to confirm if it's hardware problem or problem with new miner version.
There wasn't any changes to driver or other software.

On 1.5s I was mining for more than 2 months without a problem.
Only minor defect on 1.5s is that miner was switching to dev fee but cards actually wasn't mining (gpu usage was 0, power consumption idle) but luckly they always returned to mining properly to pool.





member
Activity: 952
Merit: 17
raskul


many thanks for all your hard work miniZ!
member
Activity: 690
Merit: 17

Don't improvements: 150,5 Verified on 1080 and 1080ti graphics cards!
Hi monster7321,

thank you for the feedback, but  could you clarify if you had improvements? Smiley Or regression? Sad

Improvements depend on GPU.  150,5 (GRIMM and CASH algo) improved for most GPUs (particularly for Turing architectures).

Cheers
member
Activity: 690
Merit: 17
Why isnt there a Cuda 9.1/9.2 version and you drop down to Cuda 8? This is the only miner out there that has CUDA 8 then jumps to Cuda 10?

I dont have cuda 10 yet and cuda 8 severely degrades my performance.
Hi teammaf,

Which NVIDIA driver version do you have installed?

To run miniZ CUDA10 you just need to have NVIDIA driver >=411.31 (Windows) or >=410.48 (Linux).
For driver <=391 the miniZ CUDA8 will run at full speed.

miniZ CUDA version runs independently of the CUDA version you may have installed.
It is the NVIDIA driver version that matters. Smiley

Cheers
newbie
Activity: 1
Merit: 0
Hi everyone,

Thank you for your patience! A new version miniZ v1.5t is out! Smiley

We took a bit longer this time (sorry for the silence), however we kept working and did our best to make miniZ a fast and friendly equihash miner!

* Major improvements: 150,5 and 210,9. Up to 4% depending on algo and GPU.
  Also for RTX 2070 (up to 8% on 192,7), 1660 Ti.
* Minor improvements in all other algos. Up to 2% depending on algo and GPU.
* Better support for GTX 1660 Ti and GTX 1070.
* Improved stability.
* Fixed telemetry on Chrome browser.
* Fixed CPU load when mining Beam on Windows.
* Cleaner program exit/termination.
* Added --color and --fee-time to command line options. (see Usage page)

Download miniZ v1.5t here.

Few notes:
  * When adjusting your GPUs settings do not forget to test it with --oc1/oc2 since it may boost your performance a little. --oc1/oc2 changed for some GPUs and algos in the new version.
     For updated information read the specific topic on FAQ page.
  * On Download page you can find Cuda 10 and Cuda 8 versions (Linux and Windows).
     For Turing architectures (16xx series and RTX) you need to use Cuda 10.0 versions.

For additional information check our Usage or FAQ pages.
Let us know how it goes!

Happy mining!


Don't improvements: 150,5 Verified on 1080 and 1080ti graphics cards!
member
Activity: 690
Merit: 17
Hi everyone,

Thank you for your patience! A new version miniZ v1.5t is out! Smiley

We took a bit longer this time (sorry for the silence), however we kept working and did our best to make miniZ a fast and friendly equihash miner!

* Major improvements: 150,5 and 210,9. Up to 4% depending on algo and GPU.
  Also for RTX 2070 (up to 8% on 192,7), 1660 Ti.
* Minor improvements in all other algos. Up to 2% depending on algo and GPU.
* Better support for GTX 1660 Ti and GTX 1070.
* Improved stability.
* Fixed telemetry on Chrome browser.
* Fixed CPU load when mining Beam on Windows.
* Cleaner program exit/termination.
* Added --color and --fee-time to command line options. (see Usage page)

Download miniZ v1.5t here.

Few notes:
  * When adjusting your GPUs OC settings check if your GPU supports oc1/oc2 (FAQ). If so it may boost your performance a little.
     --oc1/oc2 changed for some GPUs, for 150,5,3 (BEAM) in the new version.
     For updated and more detailed information read the specific topic on FAQ page.

  * On Download page you can find Cuda 10 and Cuda 8 versions (Linux and Windows).
     For Turing architectures (16xx series and RTX) you need to use Cuda 10.0 versions.

For additional information check our Usage or FAQ pages.
Let us know how it goes!

Happy mining!
member
Activity: 690
Merit: 17
Is this miner properly optimized for Turing uarch?
Hi cryptosize,
In the new version v1.5t we have improved support for some GPUs, it should benefit Turing architectures.
Let us know if this was the case for you.
Cheers
member
Activity: 690
Merit: 17

uh-huh...

Hi fistsofgod,
Thanks for your patience Smiley
It is out!
Cheers
sr. member
Activity: 1666
Merit: 310
Is this miner properly optimized for Turing uarch?
newbie
Activity: 164
Merit: 0
we're getting our pitchforks and torches ready. been too long between updates

also getting a lot of rejected shares on 192,7 Arrow. more than gminer
Hi fistsofgod,
thanks the reminder Smiley It is s busy time...
We have been working and we expect to have a new release very soon! (Within a week)
Rejected shares on 192,7 is already fixed and will be out for the new version.
Cheers

uh-huh...
newbie
Activity: 164
Merit: 0
yes, i reconnected few days later and it happened again. im currently on different pool and having no disconnection issues
member
Activity: 690
Merit: 17
mining Arrow and this occurs on only one pool. I've discussed this issue with the pool op also.
this error appears roughly 30 minutes after miner stops submitting shares. all green/red asterisks stop displaying in console but the shares number goes up. after the error miner begins submitting  
Hi fistsofgod,
thanks a lot for the feedback!
Could you let us know which pool is it? We will try to understand what is happening.
Cheers
dapool.io

Have also experienced a lot more rejected shares with dapool than snowmining.com I dont know if it is dapool specific because those are the only 2 i have used.
Already had a chat with fistsofgod but we weren't able to debug the issue. I may add that not every (miniz) worker is experiencing the same behaviour.

We're very interested in the resolution of this issue. If you need any support, please let us know.

Thank you again

ps you are welcome to join our Discord if it can help https://discord.gg/7UKcGcK
Hi fistsofgod, daPool,

So far we were unable to reproduce this behavior (stop submitting shares ans socket error).
Do you keep experiencing these issues?

However we see slight higher number of rejected shares.

We are trying to understand this.

Thanks!
Cheers
newbie
Activity: 8
Merit: 0
mining Arrow and this occurs on only one pool. I've discussed this issue with the pool op also.
this error appears roughly 30 minutes after miner stops submitting shares. all green/red asterisks stop displaying in console but the shares number goes up. after the error miner begins submitting  
Hi fistsofgod,
thanks a lot for the feedback!
Could you let us know which pool is it? We will try to understand what is happening.
Cheers
dapool.io

Have also experienced a lot more rejected shares with dapool than snowmining.com I dont know if it is dapool specific because those are the only 2 i have used.
Already had a chat with fistsofgod but we weren't able to debug the issue. I may add that not every (miniz) worker is experiencing the same behaviour.

We're very interested in the resolution of this issue. If you need any support, please let us know.

Thank you again

ps you are welcome to join our Discord if it can help https://discord.gg/7UKcGcK
newbie
Activity: 164
Merit: 0
mining Arrow and this occurs on only one pool. I've discussed this issue with the pool op also.
this error appears roughly 30 minutes after miner stops submitting shares. all green/red asterisks stop displaying in console but the shares number goes up. after the error miner begins submitting  
Hi fistsofgod,
thanks a lot for the feedback!
Could you let us know which pool is it? We will try to understand what is happening.
Cheers
dapool.io

Have also experienced a lot more rejected shares with dapool than snowmining.com I dont know if it is dapool specific because those are the only 2 i have used.
member
Activity: 690
Merit: 17
mining Arrow and this occurs on only one pool. I've discussed this issue with the pool op also.
this error appears roughly 30 minutes after miner stops submitting shares. all green/red asterisks stop displaying in console but the shares number goes up. after the error miner begins submitting  
Hi fistsofgod,
thanks a lot for the feedback!
Could you let us know which pool is it? We will try to understand what is happening.
Cheers
newbie
Activity: 164
Merit: 0
Code:
[ERROR  ] Socket write error2.
write: No error
[ERROR  ] Socket write error2.
write: No error
[ERROR  ] Socket write error2.
rite: No error
2;31m[ERROR  ] Socket write error2.
write: No error
[ERROR  ] Socket write error2.
write: No error
Any way to get more info about this error?
Hi fistsofgod,
the error refers to a communication problem with the pool. miniz is trying to write to the communication channel with the pool but is being closed.
Please check the port number and server address. What are you trying to mine?
Let us know how it goes.
Cheers
mining Arrow and this occurs on only one pool. I've discussed this issue with the pool op also.
this error appears roughly 30 minutes after miner stops submitting shares. all green/red asterisks stop displaying in console but the shares number goes up. after the error miner begins submitting  
member
Activity: 690
Merit: 17
Code:
[ERROR  ] Socket write error2.
write: No error
[ERROR  ] Socket write error2.
write: No error
[ERROR  ] Socket write error2.
rite: No error
2;31m[ERROR  ] Socket write error2.
write: No error
[ERROR  ] Socket write error2.
write: No error
Any way to get more info about this error?
Hi fistsofgod,
the error refers to a communication problem with the pool. miniz is trying to write to the communication channel with the pool but is being closed.
Please check the port number and server address. What are you trying to mine?
Let us know how it goes.
Cheers
member
Activity: 690
Merit: 17
hi all what command line for 150,5
Hi qwep1,
What are you trying to mine?
For Grimm you can, for example, use this cmd line:
Code:
miniZ.exe --url=ssl://[email protected]:3334 --log --extra
For further information pelase check How to mine Grimm? in the FAQ page.
Cheers
newbie
Activity: 164
Merit: 0
Code:
[ERROR  ] Socket write error2.
write: No error
[ERROR  ] Socket write error2.
write: No error
[ERROR  ] Socket write error2.
rite: No error
2;31m[ERROR  ] Socket write error2.
write: No error
[ERROR  ] Socket write error2.
write: No error
Any way to get more info about this error?
hero member
Activity: 610
Merit: 500
hi all what command line for 150,5
Pages:
Jump to: