Our solver for 150,5,3 (Beam2) requires less memory than the 150,5 , but it will not fit on 3GB GPU Windows 10.
I do confirm--150,5,3 works brilliant under HiveOS.
Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 44. (Read 59781 times)
August 15, 2019, 02:30:38 PM
I do confirm--150,5,3 works brilliant under HiveOS.
August 15, 2019, 11:45:24 AM
Hi RelaxedCrypto, MineOrDie,
Apparently our solver has not shrink enough to fit in your cards.
We keep trying to improve this for the next version.
Cheers
August 15, 2019, 08:47:31 AM
August 15, 2019, 06:40:41 AM
Mode=10 do nothing for me.
August 15, 2019, 06:33:05 AM
Hi 2h4u, RelaxedCrypto, MineOrDie,
Our solver for 150,5,3 (Beam2) requires less memory than the 150,5 , but it will not fit on 3GB GPU Windows 10.
The miniZ v1.5p should be able to mine ZEL (125,4) on 3GB GPU Windows 10 (although still experimental),
According to your log miniZ is not picking the right mode, it should be loading mode 10. Try to add --mode=10 to your command line.
Cheers,
Our solver for 150,5,3 (Beam2) requires less memory than the 150,5 , but it will not fit on 3GB GPU Windows 10.
The miniZ v1.5p should be able to mine ZEL (125,4) on 3GB GPU Windows 10 (although still experimental),
************ miniZ v1.5p ************
miniZ,125,4[3:1:00:2480]: Selecting GPU#0[0] GeForce GTX 1060 3GB
Algo: EQ[125,4]
Pool#0: user[t1RXmYgTUeBgcnZWnEKkdbwAapD4Jwv7ZAw.GTX1060]
server[zel.2miners.com] port[9090] ssl[no] pers[ZelProof]
Telemetry: [http://localhost:20000]
Temp. limit: [90°C]
[FATAL ] CUDA: failed to alloc 2524 MB for main data
[INFO ] Disconnecting from zel.2miners.com
[INFO ]zel.2miners.com Stopping miner
miniZ,125,4[3:1:00:2480]: Selecting GPU#0[0] GeForce GTX 1060 3GB
Algo: EQ[125,4]
Pool#0: user[t1RXmYgTUeBgcnZWnEKkdbwAapD4Jwv7ZAw.GTX1060]
server[zel.2miners.com] port[9090] ssl[no] pers[ZelProof]
Telemetry: [http://localhost:20000]
Temp. limit: [90°C]
[FATAL ] CUDA: failed to alloc 2524 MB for main data
[INFO ] Disconnecting from zel.2miners.com
[INFO ]zel.2miners.com Stopping miner
According to your log miniZ is not picking the right mode, it should be loading mode 10. Try to add --mode=10 to your command line.
Cheers,
August 15, 2019, 04:22:19 AM
Hi
does miniZ v1.5p Zel Equihash 125,4 works on GTX1060 3gb Windows 10 ? tried both cuda 8 and cuda 10
I get this error
[FATAL ] CUDA: failed to alloc 2524 MB for main data
Hi RelaxedCrypto,does miniZ v1.5p Zel Equihash 125,4 works on GTX1060 3gb Windows 10 ? tried both cuda 8 and cuda 10
I get this error
[FATAL ] CUDA: failed to alloc 2524 MB for main data
thanks for letting us know.
It seems that the solver is still tight for some configurations.
Could you paste here the beginning of miniZ console output?
Cheers
************ miniZ v1.5p ************
miniZ,125,4[3:1:00:2480]: Selecting GPU#0[0] GeForce GTX 1060 3GB
Algo: EQ[125,4]
Pool#0: user[t1RXmYgTUeBgcnZWnEKkdbwAapD4Jwv7ZAw.GTX1060]
server[zel.2miners.com] port[9090] ssl[no] pers[ZelProof]
Telemetry: [http://localhost:20000]
Temp. limit: [90°C]
[FATAL ] CUDA: failed to alloc 2524 MB for main data
[INFO ] Disconnecting from zel.2miners.com
[INFO ]zel.2miners.com Stopping miner
August 15, 2019, 02:57:34 AM
Hi
does miniZ v1.5p Zel Equihash 125,4 works on GTX1060 3gb Windows 10 ? tried both cuda 8 and cuda 10
I get this error
[FATAL ] CUDA: failed to alloc 2524 MB for main data
Hi RelaxedCrypto,does miniZ v1.5p Zel Equihash 125,4 works on GTX1060 3gb Windows 10 ? tried both cuda 8 and cuda 10
I get this error
[FATAL ] CUDA: failed to alloc 2524 MB for main data
thanks for letting us know.
It seems that the solver is still tight for some configurations.
Could you paste here the beginning of miniZ console output?
Cheers
August 14, 2019, 11:02:48 PM
@miniZ,
would you confirm that 1063's tight 3Gb memory does suit the new 150,5,3?
would you confirm that 1063's tight 3Gb memory does suit the new 150,5,3?
August 14, 2019, 06:32:32 PM
Hi
does miniZ v1.5p Zel Equihash 125,4 works on GTX1060 3gb Windows 10 ? tried both cuda 8 and cuda 10
I get this error
[FATAL ] CUDA: failed to alloc 2524 MB for main data
Hi RelaxedCrypto,does miniZ v1.5p Zel Equihash 125,4 works on GTX1060 3gb Windows 10 ? tried both cuda 8 and cuda 10
I get this error
[FATAL ] CUDA: failed to alloc 2524 MB for main data
thanks for letting us know.
It seems that the solver is still tight for some configurations.
Could you paste here the beginning of miniZ console output?
Cheers
August 14, 2019, 06:31:14 PM
On 144.5 hashrate has dropped slightly on polaris cards in v1.5
Hi Divinity666,could you please confirm that it is a Polaris card and let us know the exact model?
miniZ is a CUDA miner, it does not support AMD cards.
Cheers
Err, just a misprint, I ment Pascal, I have 1070\1080\Ti
we did not make modifications to 144,5. Performance should be the same as the previous version.
Could you let us know what miniZ cuda version are you using (8 or 10)? Also which OS are you using and which nvidia driver version?
Thanks
Cheers
August 14, 2019, 06:17:44 PM
Hi
does miniZ v1.5p Zel Equihash 125,4 works on GTX1060 3gb Windows 10 ? tried both cuda 8 and cuda 10
I get this error
[FATAL ] CUDA: failed to alloc 2524 MB for main data
does miniZ v1.5p Zel Equihash 125,4 works on GTX1060 3gb Windows 10 ? tried both cuda 8 and cuda 10
I get this error
[FATAL ] CUDA: failed to alloc 2524 MB for main data
August 14, 2019, 04:03:14 PM
On 144.5 hashrate has dropped slightly on polaris cards in v1.5
Hi Divinity666,could you please confirm that it is a Polaris card and let us know the exact model?
miniZ is a CUDA miner, it does not support AMD cards.
Cheers
Err, just a misprint, I ment Pascal, I have 1070\1080\Ti
August 14, 2019, 08:51:17 AM
Many thanks!!! We had not seen the --pers beam --pers auto flag at the same time in the documentation. This is greatly appreciated!
Do not worry about adding our pools to your list, seeing as these flags work and we do not expect people to manually point their miners at this pool.
Hi strideynet2,Do not worry about adding our pools to your list, seeing as these flags work and we do not expect people to manually point their miners at this pool.
Great that it worked!
This is just a trick to solve your question, it is not a real option to be documented.
Cheers
August 14, 2019, 08:45:48 AM
Many thanks!!! We had not seen the --pers beam --pers auto flag at the same time in the documentation. This is greatly appreciated!
Do not worry about adding our pools to your list, seeing as these flags work and we do not expect people to manually point their miners at this pool.
Do not worry about adding our pools to your list, seeing as these flags work and we do not expect people to manually point their miners at this pool.
August 14, 2019, 08:43:18 AM
On 144.5 hashrate has dropped slightly on polaris cards in v1.5
Hi Divinity666,could you please confirm that it is a Polaris card and let us know the exact model?
miniZ is a CUDA miner, it does not support AMD cards.
Cheers
August 14, 2019, 08:42:03 AM
Good day.
Before loading the miner, the control and monitoring parameters of the GPU (AB MSI, GPUZ) are loaded.
I fix the availability of PhysX before and after the miner launchesccording to the testimony of the GPUZ.
Please comment.
Hi Ziv1,Before loading the miner, the control and monitoring parameters of the GPU (AB MSI, GPUZ) are loaded.
I fix the availability of PhysX before and after the miner launchesccording to the testimony of the GPUZ.
Please comment.
Sorry, we think we may have not understood exactly what is your problem.
Could you please try to elaborate a bit more.
Why do you want to run miniZ and PhyX at the same time?
Thanks.
Cheers
August 14, 2019, 08:40:29 AM
Hey. If we have specified pers and par, will it still correctly auto-switch to BHII when the fork occurs?
These are the parameters we currently use:
--par 150,5 --pers auto
Many thanks,
-- edit --
Have done some research. It looks like when you set the algo or the par, it completely ignores the forkheight and blockheight data in the stratum protocol. Our custom pool is obviously not in your magic list of URLs which support the auto detection of algo etc, so we have to specify the algo or it just mines with BitcoinGold params. Is there a commandline flag we can use to enable the auto switch???
If possible could you add it so that on the following address/port combos, it picks up Beam automatically:
proxy.cudopool.com:5317
staging.proxy.cudopool.com:5317
Hi strideynet2,These are the parameters we currently use:
--par 150,5 --pers auto
Many thanks,
-- edit --
Have done some research. It looks like when you set the algo or the par, it completely ignores the forkheight and blockheight data in the stratum protocol. Our custom pool is obviously not in your magic list of URLs which support the auto detection of algo etc, so we have to specify the algo or it just mines with BitcoinGold params. Is there a commandline flag we can use to enable the auto switch???
If possible could you add it so that on the following address/port combos, it picks up Beam automatically:
proxy.cudopool.com:5317
staging.proxy.cudopool.com:5317
In standard cases, standard mining pools, the miner will switch to the new BeamHashII.
When autoswitch is enabled the miner will check if the fork happened and if not it gives you a message
Code:
[INFO ] Beam not forked yet (319529<321321), switch to BeamHashI.
It switches to the old, but when the fork happens it will switch back again.On a custom pool, if you start miniZ v1.5p with --par 150,5 --pers auto this may not happen.
In your special case try to add --pers beam before the --pers auto.
Meaning, try this:
--par 150,5 --pers beam --pers auto
If you want, we can add your pool, for the next release.
Let us know how if this helps.
Cheers
August 14, 2019, 03:51:52 AM
Hey. If we have specified pers and par, will it still correctly auto-switch to BHII when the fork occurs?
These are the parameters we currently use:
--par 150,5 --pers auto
Many thanks,
-- edit --
Have done some research. It looks like when you set the algo or the par, it completely ignores the forkheight and blockheight data in the stratum protocol. Our custom pool is obviously not in your magic list of URLs which support the auto detection of algo etc, so we have to specify the algo or it just mines with BitcoinGold params. Is there a commandline flag we can use to enable the auto switch???
If possible could you add it so that on the following address/port combos, it picks up Beam automatically:
proxy.cudopool.com:5317
staging.proxy.cudopool.com:5317
These are the parameters we currently use:
--par 150,5 --pers auto
Many thanks,
-- edit --
Have done some research. It looks like when you set the algo or the par, it completely ignores the forkheight and blockheight data in the stratum protocol. Our custom pool is obviously not in your magic list of URLs which support the auto detection of algo etc, so we have to specify the algo or it just mines with BitcoinGold params. Is there a commandline flag we can use to enable the auto switch???
If possible could you add it so that on the following address/port combos, it picks up Beam automatically:
proxy.cudopool.com:5317
staging.proxy.cudopool.com:5317
August 14, 2019, 02:51:46 AM
On 144.5 hashrate has dropped slightly on polaris cards in v1.5
August 14, 2019, 01:12:13 AM
Good day.
Before loading the miner, the control and monitoring parameters of the GPU (AB MSI, GPUZ) are loaded.
I fix the availability of PhysX before and after the miner launchesccording to the testimony of the GPUZ.
Please comment.
Before loading the miner, the control and monitoring parameters of the GPU (AB MSI, GPUZ) are loaded.
I fix the availability of PhysX before and after the miner launchesccording to the testimony of the GPUZ.
Please comment.
Jump to: