miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 26.

rgsnedds

member

Activity: 952

Merit: 17

raskul

Quote from: miniZ on June 26, 2020, 09:48:12 AM

Quote from: MrPlus on June 26, 2020, 09:10:26 AM

Hi,

Any info on coming Beam fork support (june 28th)

Hi MrPlus,
We are currently taking care of the last details. The release will be out today....within the next hour or so.

Cheers

and
to offer a great pool for your devfee -

https://minebeam.raskul.com (USA)
or
https://pool.raskul.com (UK)

Guy Corem

donator

Activity: 1414

Merit: 1051

Spondoolies, Beam & DAGlabs

Quote from: miniZ on June 26, 2020, 09:48:12 AM

Quote from: MrPlus on June 26, 2020, 09:10:26 AM

Hi,

Any info on coming Beam fork support (june 28th)

Hi MrPlus,
We are currently taking care of the last details. The release will be out today....within the next hour or so.

Cheers

Wonderful.

miniZ

member

Activity: 690

Merit: 17

Quote from: MrPlus on June 26, 2020, 09:10:26 AM

Hi,

Any info on coming Beam fork support (june 28th)

Hi MrPlus,
We are currently taking care of the last details. The release will be out today....within the next hour or so.

Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: Ziv1 on June 25, 2020, 04:13:44 AM

Hello miniZ.
W 7 125.4 ZEL 1060-3GB
The main version that I use is 1.5t.
When using it, there are no problems with the joint launch of control and monitoring of video cards (in the operating load mode).
Version 1.5u2 is being tested.
Monitoring does not work (in operating mode) .Try
switch to monitoring settings in GPUZ.
I associate this with the increased volume of video memory
maps (3067mv).
Can one hope that in new versions this value will decrease to 2692mv (as in version 1.5t)?

Hi Ziv1,
Thank you for the information.
The mode 0 takes almost all the memory of the GPU, and there is nothing left for GPUz.
In the new version (1.6v, will be out today) the default kernel is a tiny smaller (few MB). We hope that this size decrease will be enough to make your GPUs run with newest kernel.
However, we managed to recover the older kernel that you can run just by adding --oc2 (or --mode 16). But remember that this one is way smaller and it does not perform as good as the kernel in recent versions.
We'll try to decrease the best kernel a bit more without compromising performance, in future versions.
Let us know if this solves your issue.
Cheers

MrPlus

member

Activity: 514

Merit: 11

Hi,

Any info on coming Beam fork support (june 28th)

Ziv1

newbie

Activity: 25

Merit: 1

Hello miniZ.
W 7 125.4 ZEL 1060-3GB
The main version that I use is 1.5t.
When using it, there are no problems with the joint launch of control and monitoring of video cards (in the operating load mode).
Version 1.5u2 is being tested.
Monitoring does not work (in operating mode) .Try
switch to monitoring settings in GPUZ.
I associate this with the increased volume of video memory
maps (3067mv).
Can one hope that in new versions this value will decrease to 2692mv (as in version 1.5t)?

miniZ

member

Activity: 690

Merit: 17

Quote from: somaton on June 20, 2020, 06:58:32 PM

miniZ: Got two pools working through one .conf file, thank you for all your suggestions!

Quote from: somaton on June 24, 2020, 06:24:38 AM

Last two days when zergpool and zpool are not working well because of ddos atacks, i have tested miniz capability to switch between main and backup pools - need more work with error and info messages. Every 30 secs i see this: No error: connect - what problem with connect or it cant connect anywhere? I have to check gpu temperatures to see is it mining at all or is miner really not connected to any pool or what is going on? Every ~1,5 min i see this: Cannot connect to equihash192.mine.zergpool.com pool, reconnect in 5 seconds! Why reconnect in 5 seconds if it is down for many hours? Why then i see this error every 1,5 min if reconnect attempt is every 5 secs? This part of miner still need some work, too many weird messages. T-rex is very good example how it can be.

Hi somaton,
Nice that you managed to add the two pools and to use miniZ from the config file.

Regarding the messages, when miniZ cannot connect to the first mining pool (the first you define, in case there two or more pools defined by the user) it will start saying that it cannot connect.
If after a few quick attempts it cannot connect then it will connect to the second pool. However, it keeps trying to connect to the first pool.

If the miner cannot connect to any mining pool it will keep looping through the list of pools until it can connect somewhere, it still tries to reconnect to the first pool all the time.

The No error: connect message, just means that there was a failed attempt to connect, in this case because the pool is down.

The miner does not know when the pool will be back up, so it keeps trying, it does not matter for how long it was down.

Hope this helps to clarify some doubts. We'll have a look and review the messages in future releases.
Thanks for the feedback!
Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: MineOrDie on June 22, 2020, 11:10:12 AM

I tend to get 15 sols less on my 1060 3GB rigs compared to 1.5t2.
Running 1.5u2, Windows 8.1 and the latest drivers.

Hi MineOrDie,
We are not aware of any regressions on 1060 3GB.
What is the algo that you are mining?

Could you help us understand what is happening by giving some more information?

If you paste here the start of the log (until it starts mining), for both versions, for example, this may be helpful.

Thank you for the feedback!
Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: Ziv1 on June 21, 2020, 06:43:39 AM

Mine ZEL-125.4 mode 0.
How much video memory is required for such mining.

Hi Ziv1,
sorry for taking a bit longer than usual to reply, we've been busy with Beam fork.

On Windows, mode 0 for ZEL mining needs slight less than 3GB (it is a bit tight). This also depends on how much is the operative system overhead.

If miniZ starts mining then the memory is not the problem.

Is miniZ not starting anymore? The last time you showed the log it was looking fine despite the fact that it was not submitting the shares.
Cheers

somaton

jr. member

Activity: 211

Merit: 6

Last two days when zergpool and zpool are not working well because of ddos atacks, i have tested miniz capability to switch between main and backup pools - need more work with error and info messages. Every 30 secs i see this: No error: connect - what problem with connect or it cant connect anywhere? I have to check gpu temperatures to see is it mining at all or is miner really not connected to any pool or what is going on? Every ~1,5 min i see this: Cannot connect to equihash192.mine.zergpool.com pool, reconnect in 5 seconds! Why reconnect in 5 seconds if it is down for many hours? Why then i see this error every 1,5 min if reconnect attempt is every 5 secs? This part of miner still need some work, too many weird messages. T-rex is very good example how it can be.

MineOrDie

jr. member

Activity: 75

Merit: 1

I tend to get 15 sols less on my 1060 3GB rigs compared to 1.5t2.
Running 1.5u2, Windows 8.1 and the latest drivers.

Ziv1

newbie

Activity: 25

Merit: 1

Mine ZEL-125.4 mode 0.
How much video memory is required for such mining.

somaton

jr. member

Activity: 211

Merit: 6

miniZ: Got two pools working through one .conf file, thank you for all your suggestions!

miniZ

member

Activity: 690

Merit: 17

Quote from: topteam on June 20, 2020, 04:43:59 PM

yea ubuntu 16 and driver 396.82
reason - only GTX cards

Hi topteam,
The cuda 10 version of miniZ works fine with GTX GPUs, you just need to update the Nvidia driver. (NVIDIA 410.48 driver or later)
The latest should be fine.
We added Cuda 8 Linux version to Download page, but we suggest you to update the Nvidia driver.

Cheers

topteam

newbie

Activity: 157

Merit: 0

yea ubuntu 16 and driver 396.82
reason - only GTX cards

miniZ

member

Activity: 690

Merit: 17

Quote from: topteam on June 20, 2020, 01:47:55 PM

can't find cuda 8 build

Hi topteam,
From version t3 we announced that we would stop supporting Cuda 8.
If you really need it, we can add it for now, but you should consider updating your drivers

do you have a reason to not do so?
(You still use Linux ,right?)
Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: Kringel on June 20, 2020, 01:38:56 PM

The problem is that in order to get a hashrate comparable to that achieved with the 1.5t3 version, I have to use both --oc1/oc2 and --mode options, at least on 1070s. --ocX alone gives inferior results; so I have to wait till it finishes and finds kinda the best mode, and then add that mode to the command line with either --oc1 or --oc2 (depending on the power limit and thermal conditions for particular cards). Not sure if that procedure gives the best possible result, but it's definitely better than just running --ocX.

Imagine my frustration: after spending a lot of time and efforts I get the same hashrate that I got with the older version literally within a minute, just by empirically selecting an appropriate kernel.

Hi Kringel,
Sorry for the confusion. We understand your frustration.
We'll do our best to improve this and will also optimise the default kernels for the 1070, in all agos.
Thank you for your feedback.
Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: Ziv1 on June 20, 2020, 01:19:44 AM

farms run under the operating system
W 7.
For management and monitoring I use programs - AB, G P U Z.
These programs run by default.
In version 1.5u 2, when working with G P U Z (switching the viewing of video card parameters), a malfunction occurs.
In my previous post, this is shown in the work log
(there was talk about version 1.5u).
I pay attention to the-memory used parameter (in version 1.5u -1.5u 2 reaches 3067mb) v 1.5t -2692mb.
Perhaps because of this, a crash occurs.

Hi Ziv1,
Thank you for your reply.

Kernels 0 and 14 should work with your GPU on Windows 7 (ZEL).

If your GPUs are unstable do not use ocX option, just run try directly --mode 0 or --mode 14.

If miniZ is still unstable you may need to adjust your oc settings a little bit, maybe decreasing slightly the core clock.

You may also try to run only one gpu at a time to understand which one is triggering the instability.

Hope this will help.
Cheers

topteam

newbie

Activity: 157

Merit: 0

can't find cuda 8 build

Kringel

jr. member

Activity: 151

Merit: 7

Quote from: miniZ on June 19, 2020, 04:06:34 PM

More recently we managed to make it better with --ocX. --ocX will run a few available miniZ kernels and choose the one that performs best, for your GPU, and for the overclocks you apply to your GPU.

Do not use oc1/oc2/ocX (or --mode) at the same time on the same GPU. This could cause confusion in understanding miniZ behavior. One of the options will prevail though, usually the last one appearing in the command line.

The problem is that in order to get a hashrate comparable to that achieved with the 1.5t3 version, I have to use both --oc1/oc2 and --mode options, at least on 1070s. --ocX alone gives inferior results; so I have to wait till it finishes and finds kinda the best mode, and then add that mode to the command line with either --oc1 or --oc2 (depending on the power limit and thermal conditions for particular cards). Not sure if that procedure gives the best possible result, but it's definitely better than just running --ocX.

Imagine my frustration: after spending a lot of time and efforts I get the same hashrate that I got with the older version literally within a minute, just by empirically selecting an appropriate kernel.

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