Hi everyone,
Thank you for the feedback!
We just released a beta version miniZ v1.8y4rc1.
Changelog:
* Improved stability for mining locked GPUs while mining ETH.
* Fixed rejected shares on 3060s. (Let us know if you get any.)
* If you get many invalid, and are overclocking, it may be usefull to use the option --dag-fix.
* Added --nohttpheaders to remove http headers from getstat api.
You can download it here https://miniz.ch/download/
Let us know how it works for you.
Happy mining!
Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 14. (Read 60004 times)
July 21, 2021, 11:48:54 AM
July 21, 2021, 11:02:31 AM
I've tested v1.8y3 for few hours on 3060's seems good.
I had issue on 1 rig(3060's) that the unlock thing did not work at all (all cards did 22M h/s) and other rigs did 38M h/s+)
- need to fix stale&invalid shares
- need to fix "re-unlock" sometimes hashrate dropped and not coming back to 38+
- would be awesome if we can keep 40M h/s+ stable without any drops
When the new version coming out? I'm really looking forward to test the new version as I'm using the last version for almost a day.
Hi brianshaw,I had issue on 1 rig(3060's) that the unlock thing did not work at all (all cards did 22M h/s) and other rigs did 38M h/s+)
- need to fix stale&invalid shares
- need to fix "re-unlock" sometimes hashrate dropped and not coming back to 38+
- would be awesome if we can keep 40M h/s+ stable without any drops
When the new version coming out? I'm really looking forward to test the new version as I'm using the last version for almost a day.
Thank you for the feedback.
You may want to try the beta version we've just released. We think that it answers/solves the issues you had.
You can download it here.
Let us know how it goes.
Cheers,
miniZ
July 20, 2021, 02:46:44 PM
I've tested v1.8y3 for few hours on 3060's seems good.
I had issue on 1 rig(3060's) that the unlock thing did not work at all (all cards did 22M h/s) and other rigs did 38M h/s+)
- need to fix stale&invalid shares
- need to fix "re-unlock" sometimes hashrate dropped and not coming back to 38+
- would be awesome if we can keep 40M h/s+ stable without any drops
When the new version coming out? I'm really looking forward to test the new version as I'm using the last version for almost a day.
I had issue on 1 rig(3060's) that the unlock thing did not work at all (all cards did 22M h/s) and other rigs did 38M h/s+)
- need to fix stale&invalid shares
- need to fix "re-unlock" sometimes hashrate dropped and not coming back to 38+
- would be awesome if we can keep 40M h/s+ stable without any drops
When the new version coming out? I'm really looking forward to test the new version as I'm using the last version for almost a day.
July 20, 2021, 07:18:01 AM
Sorry, I haven't been following. Does this mean miniZ can now mine without any special drivers with 3060 at 50 MH/s for ETH? Is this true with both Windows and Linux? And do we still need to feed it 8x PCI-E lanes at minimum? Or can 1x riser cards now work with them with miniZ?
I've been using T-Rex so far, and in Windows with the leaked driver.
Does this also work with the LHR version of the card?
I've been using T-Rex so far, and in Windows with the leaked driver.
Does this also work with the LHR version of the card?
Hi guytechie,
Thank you for asking.
Our antilock system can be used with any driver, with or without riser (and should work with any gpu).
But the leaked driver will always provide a better performance if running on the motherboard slot with dummy monitor plugs.
If your GPUs are all on riser maybe you'll get advantage with miniZ . If your GPUs are all on PCIE 16x, with leaked driver and dummy plugs, then your setup is already optimized and it should be fine to continue with T-rex.
In short, if you get 40MH/s (or more) with T-Rex keep it as it is, otherwise it should be better to use miniZ.
Cheers
July 19, 2021, 03:26:26 PM
Sorry, I haven't been following. Does this mean miniZ can now mine without any special drivers with 3060 at 50 MH/s for ETH? Is this true with both Windows and Linux? And do we still need to feed it 8x PCI-E lanes at minimum? Or can 1x riser cards now work with them with miniZ?
I've been using T-Rex so far, and in Windows with the leaked driver.
Does this also work with the LHR version of the card?
I've been using T-Rex so far, and in Windows with the leaked driver.
Does this also work with the LHR version of the card?
July 19, 2021, 05:09:36 AM
Hello, I want to work with miniz in my whole farm. It rejects many packages. What is the solution to this? There is no such error in other programs. Thank You.
Hive OS - 12x RTX 3060
Accepted Ratio:3000
Accepted Rejected Invalid:400
Hive OS - 12x RTX 3060
Accepted Ratio:3000
Accepted Rejected Invalid:400
Hi multimesut,
Thanks a lot for your feedback.
We fixed the issue with rejected shares and will be corrected in the next version.
It should be out soon.
Great to know that the version worked out with all your GPUs! 🙂
Cheers
Hi miniZ Developers,
This is very good news.
congratulations on your success. If there is a beta version I would like to try it. Cheers
July 18, 2021, 04:18:42 PM
Hello, I want to work with miniz in my whole farm. It rejects many packages. What is the solution to this? There is no such error in other programs. Thank You.
Hive OS - 12x RTX 3060
Accepted Ratio:3000
Accepted Rejected Invalid:400
Hive OS - 12x RTX 3060
Accepted Ratio:3000
Accepted Rejected Invalid:400
Hi multimesut,
Thanks a lot for your feedback.
We fixed the issue with rejected shares and will be corrected in the next version.
It should be out soon.
Great to know that the version worked out with all your GPUs! 🙂
Cheers
July 17, 2021, 03:18:36 PM
Hello, I want to work with miniz in my whole farm. It rejects many packages. What is the solution to this? There is no such error in other programs. Thank You.
Hive OS - 12x RTX 3060
Accepted Ratio:3000
Accepted Rejected Invalid:400
https://imgur.com/culmayD
https://imgur.com/mvo61Jz
https://imgur.com/6xkGruC
Hive OS - 12x RTX 3060
Accepted Ratio:3000
Accepted Rejected Invalid:400
https://imgur.com/culmayD
https://imgur.com/mvo61Jz
https://imgur.com/6xkGruC
July 12, 2021, 11:41:33 AM
Hello,
1.8y3 API stopped working with minerstat Windows.
Uploaded 1.8y2 until resolved.
Returns empty response, no headers needed with TCP query. Can you take a look at that?
On msOS Linux different TCP query method was working.
However, the header was inline in the text before the JSON API not as a header.
Hi coinscrow,1.8y3 API stopped working with minerstat Windows.
Uploaded 1.8y2 until resolved.
Code:
"127.0.0.1", 20000
{\"id\":0, \"method\":\"getstat\"}\n
{\"id\":0, \"method\":\"getstat\"}\n
Returns empty response, no headers needed with TCP query. Can you take a look at that?
On msOS Linux different TCP query method was working.
However, the header was inline in the text before the JSON API not as a header.
Could you paste here the code you are using to open api?
Thanks!
Cheers
July 12, 2021, 10:02:21 AM
Hello,
1.8y3 API stopped working with minerstat Windows.
Uploaded 1.8y2 until resolved.
Returns empty response, no headers needed with TCP query. Can you take a look at that?
On msOS Linux different TCP query method was working.
However, the header was inline in the text before the JSON API not as a header.
1.8y3 API stopped working with minerstat Windows.
Uploaded 1.8y2 until resolved.
Code:
"127.0.0.1", 20000
{\"id\":0, \"method\":\"getstat\"}\n
{\"id\":0, \"method\":\"getstat\"}\n
Returns empty response, no headers needed with TCP query. Can you take a look at that?
On msOS Linux different TCP query method was working.
However, the header was inline in the text before the JSON API not as a header.
July 11, 2021, 12:06:59 PM
...
- Added HTTP headers to json api.
How do I access stat information using the API in v1.8y3?
For older versions I could use (PowerShell based on https://miniz.ch/2018/07/28/trouble-running-miniz/#comment-138):
Code:
$Request = '{ "id":"0", "method":"getstat" }'
$Timeout = 5
$Response = ""
$Port = 4004
Try {
$Response = Invoke-TcpRequest "localhost" -Port $Port -Request $Request -Timeout $Timeout -ErrorAction Stop
$Data = $Response | ConvertFrom-Json -ErrorAction Stop
}
Catch {
Return $null
}
$Timeout = 5
$Response = ""
$Port = 4004
Try {
$Response = Invoke-TcpRequest "localhost" -Port $Port -Request $Request -Timeout $Timeout -ErrorAction Stop
$Data = $Response | ConvertFrom-Json -ErrorAction Stop
}
Catch {
Return $null
}
All I get now is:
Code:
HTTP/1.0 200 OK
Hi UselessGuru,
Thank you for the feedback.
We added the headers to be more compatible, if the request is http then the answer should also be http.
Try this modification inside your Try {} response code:
Code:
Try {
$Response = Invoke-TcpRequest "localhost" -Port $Port -Request $Request -Timeout $Timeout -ReadToEnd 1 -ErrorAction Stop
$Data = $Response.Substring($Response.IndexOf("{")) | ConvertFrom-Json -ErrorAction Stop
}
$Response = Invoke-TcpRequest "localhost" -Port $Port -Request $Request -Timeout $Timeout -ReadToEnd 1 -ErrorAction Stop
$Data = $Response.Substring($Response.IndexOf("{")) | ConvertFrom-Json -ErrorAction Stop
}
Let us know if this solved your issue.
Cheers,
miniZ
Thank you for your quick response.
gives me
Code:
Invoke-TcpRequest: A parameter cannot be found that matches parameter name 'ReadToEnd'.
My version can be found here:
https://github.com/Minerx117/NemosMiner/blob/testing/Includes/Include.psm1
I am using PowerShell 7.2-rc5
Edit: I found another version of Invoke-TcpRequest here
https://github.com/ethereum-mining/ethminer/issues/1918#issuecomment-533918209 (by me actually - I knew the issue sounded familiar)
that is working like a charm. Thank you!
July 11, 2021, 11:45:41 AM
...
- Added HTTP headers to json api.
How do I access stat information using the API in v1.8y3?
For older versions I could use (PowerShell based on https://miniz.ch/2018/07/28/trouble-running-miniz/#comment-138):
Code:
$Request = '{ "id":"0", "method":"getstat" }'
$Timeout = 5
$Response = ""
$Port = 4004
Try {
$Response = Invoke-TcpRequest "localhost" -Port $Port -Request $Request -Timeout $Timeout -ErrorAction Stop
$Data = $Response | ConvertFrom-Json -ErrorAction Stop
}
Catch {
Return $null
}
$Timeout = 5
$Response = ""
$Port = 4004
Try {
$Response = Invoke-TcpRequest "localhost" -Port $Port -Request $Request -Timeout $Timeout -ErrorAction Stop
$Data = $Response | ConvertFrom-Json -ErrorAction Stop
}
Catch {
Return $null
}
All I get now is:
Code:
HTTP/1.0 200 OK
Hi UselessGuru,
Thank you for the feedback.
We added the headers to be more compatible, if the request is http then the answer should also be http.
Try this modification inside your Try {} response code:
Code:
Try {
$Response = Invoke-TcpRequest "localhost" -Port $Port -Request $Request -Timeout $Timeout -ReadToEnd 1 -ErrorAction Stop
$Data = $Response.Substring($Response.IndexOf("{")) | ConvertFrom-Json -ErrorAction Stop
}
$Response = Invoke-TcpRequest "localhost" -Port $Port -Request $Request -Timeout $Timeout -ReadToEnd 1 -ErrorAction Stop
$Data = $Response.Substring($Response.IndexOf("{")) | ConvertFrom-Json -ErrorAction Stop
}
Let us know if this solved your issue.
Cheers,
miniZ
July 11, 2021, 10:10:17 AM
...
- Added HTTP headers to json api.
How do I access stat information using the API in v1.8y3?
For older versions I could use (PowerShell based on https://miniz.ch/2018/07/28/trouble-running-miniz/#comment-138):
Code:
$Request = '{ "id":"0", "method":"getstat" }'
$Timeout = 5
$Response = ""
$Port = 4004
Try {
$Response = Invoke-TcpRequest "localhost" -Port $Port -Request $Request -Timeout $Timeout -ErrorAction Stop
$Data = $Response | ConvertFrom-Json -ErrorAction Stop
}
Catch {
Return $null
}
$Timeout = 5
$Response = ""
$Port = 4004
Try {
$Response = Invoke-TcpRequest "localhost" -Port $Port -Request $Request -Timeout $Timeout -ErrorAction Stop
$Data = $Response | ConvertFrom-Json -ErrorAction Stop
}
Catch {
Return $null
}
All I get now is:
Code:
HTTP/1.0 200 OK
July 10, 2021, 12:20:48 PM
Hi everyone,
Thank you all for your feedback!
A new miniZ v1.8y3 is out!
Please find miniZ version v1.8y3 @ Download page.
Changelog:
About --mt options (Linux only): (Check Usage or FAQ pages.)
* The --mt options will only apply settings to Pascal devices (known to work well with GTX 1080, GTX 1080Ti), and will require super user permissions.
Also, these are usually applied to ethash/progpow algos, however equihash algos may also benefit from them.
* If you are unsure about the timing values, use the --mt-dump option first to get a hint. Lower values usually will give a better performance.
* Remember when using the --mt option to always specify the timing pair, with the values separated by ‘.’ such as ‘16.5’.
* If you have multiple devices you can specify multiple values like this --mt 16.5,0,16.5. The 0 means no timings should be applied.
* Warning: some values will be invalid for your GPU and may cause the driver/GPU to crash. In this case you will need to restart your rig/system/computer. Use with caution.
Remember to try --oc1/--oc2/--ocX options for optimum performance.
Regarding the Ethash mining locked GPUs feature, let us know if there is interest on mining lock workarounds for other GPUs and algos (equihash should not be affected by this lock).
We'll keep working on this, and see if we can make improvements. If you experience issues with locked devices it may be worth to have a look at lolminer that was the first miner trying to address this issue.
Download miniZ v1.8y3 version here.
For additional information check our Usage or FAQ pages.
Follow us
On Twitter
Let us know how it goes!
Happy mining!
Thank you all for your feedback!
A new miniZ v1.8y3 is out!
Please find miniZ version v1.8y3 @ Download page.
Changelog:
- Added kernel for Ethash mining locked GPUs (RTX 3060 default mode 80).
Use 461.40 (Windows) or 460.39 (Linux) drivers for best performance, although any driver should work. - Added dag verification on ETH.
- Improvements 150/5 for RTX 30XX GPUs, up to 8%.
- Added --mt-auto, --mt-dump and --mt options to adjust memory timings on Linux. (read below)
- Added HTTP headers to json api.
- Fixed low hashrate on Windows 7 while mining ETH, on some GPUs.
- Added mining rentals, and other pools, to magic list.
- Minor bug fixes.
About --mt options (Linux only): (Check Usage or FAQ pages.)
* The --mt options will only apply settings to Pascal devices (known to work well with GTX 1080, GTX 1080Ti), and will require super user permissions.
Also, these are usually applied to ethash/progpow algos, however equihash algos may also benefit from them.
* If you are unsure about the timing values, use the --mt-dump option first to get a hint. Lower values usually will give a better performance.
* Remember when using the --mt option to always specify the timing pair, with the values separated by ‘.’ such as ‘16.5’.
* If you have multiple devices you can specify multiple values like this --mt 16.5,0,16.5. The 0 means no timings should be applied.
* Warning: some values will be invalid for your GPU and may cause the driver/GPU to crash. In this case you will need to restart your rig/system/computer. Use with caution.
Remember to try --oc1/--oc2/--ocX options for optimum performance.
Regarding the Ethash mining locked GPUs feature, let us know if there is interest on mining lock workarounds for other GPUs and algos (equihash should not be affected by this lock).
We'll keep working on this, and see if we can make improvements. If you experience issues with locked devices it may be worth to have a look at lolminer that was the first miner trying to address this issue.
Download miniZ v1.8y3 version here.
For additional information check our Usage or FAQ pages.
Follow us
On Twitter
Let us know how it goes!
Happy mining!
June 19, 2021, 05:52:20 AM
@miniZ: Could you please explain the stratum/stratum1/stratum2 differences? Which is targeted for which of the different Ethash connection modes (stratum/ethproxy/qtminer/..) ? And last question: how to deal with SSL connection and the stratum1/stratum2?
Thank you in advance for your answers!
Thank you in advance for your answers!
Hi rainbowminer,
Unfortunately there is no standard for the ethereum stratum protocol, we found that there were at least five different ethereum stratum protocols. Unless the pool is on some "magic" list, when the miner is connecting to the mining pool it is impossible for the miner to know which stratum protocol it should use. After we connect with the wrong protocol the mining pool may disconnect or apply a temporary ban. So connecting again and trying a different stratum is not a great option. We choose to make our "magic" list as complete as possible but we forgot about MiningRigRentals 😊
Also there is no standard between miners in what they call stratum stratum1 or stratum2... which makes things even more tough.
For ssl connection with MiningRigRentals just write ssl+stratum2://, it should work (let us know if you encounter any issues). For the pools on the 'magic' list (most of them) ssl:// would do.
Cheers,
miniZ
Thank you for that reply!
I know pretty well about that lack of a standard. It took me a considerable amount of research to get all pools and miners working together for ethash with RainbowMiner. So, I am pretty happy about your "magic" list
Good work!I'll include that ssl+stratum2:// into the miniZ mining module.
June 18, 2021, 06:03:11 PM
@miniZ: Could you please explain the stratum/stratum1/stratum2 differences? Which is targeted for which of the different Ethash connection modes (stratum/ethproxy/qtminer/..) ? And last question: how to deal with SSL connection and the stratum1/stratum2?
Thank you in advance for your answers!
Thank you in advance for your answers!
Hi rainbowminer,
Unfortunately there is no standard for the ethereum stratum protocol, we found that there were at least five different ethereum stratum protocols. Unless the pool is on some "magic" list, when the miner is connecting to the mining pool it is impossible for the miner to know which stratum protocol it should use. After we connect with the wrong protocol the mining pool may disconnect or apply a temporary ban. So connecting again and trying a different stratum is not a great option. We choose to make our "magic" list as complete as possible but we forgot about MiningRigRentals 😊
Also there is no standard between miners in what they call stratum stratum1 or stratum2... which makes things even more tough.
For ssl connection with MiningRigRentals just write ssl+stratum2://, it should work (let us know if you encounter any issues). For the pools on the 'magic' list (most of them) ssl:// would do.
Cheers,
miniZ
June 17, 2021, 04:56:52 AM
@miniZ: Could you please explain the stratum/stratum1/stratum2 differences? Which is targeted for which of the different Ethash connection modes (stratum/ethproxy/qtminer/..) ? And last question: how to deal with SSL connection and the stratum1/stratum2?
Thank you in advance for your answers!
Thank you in advance for your answers!
June 17, 2021, 04:48:28 AM
Code:
stratum2://
did the job. Thank you! June 16, 2021, 08:07:09 AM
Thank you for the new version.
There is a problem on MiningRigRentals. I just tried to connect to an active Etchash rental (works in Trex, Gminer), but miniZ v1.8y2 fails:
Commandline:
Result:
Hi rainbowminer,There is a problem on MiningRigRentals. I just tried to connect to an active Etchash rental (works in Trex, Gminer), but miniZ v1.8y2 fails:
Commandline:
Code:
miniZ.exe --telemetry=33000 -cd 0 1 2 3 4 5 [email protected]:3344 -p x --gpu-line --extra --latency --par=etchash
Result:
Code:
************ miniZ v1.8y2 ************
Algo: EQ[etchash] [smart-pers]
Pool#0: user[whoever.123456]
server[eu-01.miningrigrentals.com] port[3344] ssl[no] pers[ethash]
Telemetry: [http://localhost:33000]
Temp. limit: [90 C]
[INFO ] Mining fee set to 0.75%
miniZ[50:0:00.0:6798]: Selecting GPU#3[3] NVIDIA GeForce GTX 1070
miniZ[50:0:00.0:6798]: Selecting GPU#0[0] NVIDIA GeForce GTX 1070
miniZ[50:0:00.0:6798]: Selecting GPU#5[5] NVIDIA GeForce GTX 1070
miniZ[50:0:00.0:6798]: Selecting GPU#2[2] NVIDIA GeForce GTX 1070
miniZ[50:0:00.0:6798]: Selecting GPU#1[1] NVIDIA GeForce GTX 1070
miniZ[50:0:00.0:6798]: Selecting GPU#4[4] NVIDIA GeForce GTX 1070
[ERROR ] Socket write error2.
write: No error
[ERROR ] Socket write error2.
write: No error
Algo: EQ[etchash] [smart-pers]
Pool#0: user[whoever.123456]
server[eu-01.miningrigrentals.com] port[3344] ssl[no] pers[ethash]
Telemetry: [http://localhost:33000]
Temp. limit: [90 C]
[INFO ] Mining fee set to 0.75%
miniZ
miniZ
miniZ
miniZ
miniZ
miniZ
[ERROR ] Socket write error2.
write: No error
[ERROR ] Socket write error2.
write: No error
Thank you for the feedback!
You will need to add stratum2:// to --url. Also --par ethash --pers etchash.
The following should work:
Code:
miniZ.exe --telemetry=33000 -cd 0 1 2 3 4 5 --url=stratum2://[email protected]:3344 -p x --gpu-line --extra --latency --par=ethash --pers etchash
Let us know how it goes.
Cheers,
miniZ
June 16, 2021, 03:02:31 AM
Thank you for the new version.
There is a problem on MiningRigRentals. I just tried to connect to an active Etchash rental (works in Trex, Gminer), but miniZ v1.8y2 fails:
Commandline:
Result:
There is a problem on MiningRigRentals. I just tried to connect to an active Etchash rental (works in Trex, Gminer), but miniZ v1.8y2 fails:
Commandline:
Code:
miniZ.exe --telemetry=33000 -cd 0 1 2 3 4 5 [email protected]:3344 -p x --gpu-line --extra --latency --par=etchash
Result:
Code:
************ miniZ v1.8y2 ************
Algo: EQ[etchash] [smart-pers]
Pool#0: user[whoever.123456]
server[eu-01.miningrigrentals.com] port[3344] ssl[no] pers[ethash]
Telemetry: [http://localhost:33000]
Temp. limit: [90 C]
[INFO ] Mining fee set to 0.75%
miniZ[50:0:00.0:6798]: Selecting GPU#3[3] NVIDIA GeForce GTX 1070
miniZ[50:0:00.0:6798]: Selecting GPU#0[0] NVIDIA GeForce GTX 1070
miniZ[50:0:00.0:6798]: Selecting GPU#5[5] NVIDIA GeForce GTX 1070
miniZ[50:0:00.0:6798]: Selecting GPU#2[2] NVIDIA GeForce GTX 1070
miniZ[50:0:00.0:6798]: Selecting GPU#1[1] NVIDIA GeForce GTX 1070
miniZ[50:0:00.0:6798]: Selecting GPU#4[4] NVIDIA GeForce GTX 1070
[ERROR ] Socket write error2.
write: No error
[ERROR ] Socket write error2.
write: No error
Algo: EQ[etchash] [smart-pers]
Pool#0: user[whoever.123456]
server[eu-01.miningrigrentals.com] port[3344] ssl[no] pers[ethash]
Telemetry: [http://localhost:33000]
Temp. limit: [90 C]
[INFO ] Mining fee set to 0.75%
miniZ
miniZ
miniZ
miniZ
miniZ
miniZ
[ERROR ] Socket write error2.
write: No error
[ERROR ] Socket write error2.
write: No error
Jump to: