here is my feedback.
got the miner 3 days ago
to make it go online had to change the ip to .10 instead of .100 and put manually DNS server name
then tried different pools. nicehash, MPH, powermining. all same performance, 1 board not hashing fine.
changing frequency doesn't seem to do a big deal, with 900 one board stays dead all the time, with 800 dies after a while.
sent message to crypto drilling (shop I bought) and told me to freq 845 (which I can only put 850)
waiting for their technical team to reply..
this is my configuration


{
"pools": [
{
"url": "stratum+tcp:\/\/lyra2rev2.eu.nicehash.com:3347",
"user": "3GKgz3dj7nE3NFdrEECKdqjQf1US5rz6YR",
"pass": "x"
},
{
"url": "stratum+tcp:\/\/pool.powermining.pw:4535",
"user": "MErJBFcuRdAYCSidG3P8UQYmXVFmhpK53j",
"pass": "x"
},
{
"url": "stratum+tcp:\/\/hub.miningpoolhub.com:12018",
"user": "roberto_f.zig",
"pass": "x"
}
],
"api-allow": "W:0\/0",
"api-description": "cgminer 4.11.1",
"api-listen": true,
"api-mcast-addr": "224.0.0.75",
"api-mcast-code": "FTW",
"api-mcast-des": "",
"api-mcast-port": "4028",
"api-network": true,
"api-port": "4028",
"expiry": "120",
"failover-switch-delay": "300",
"log": "5",
"queue": "9999",
"scan-time": "60",
"shares": "0",
"lyra2rev2-clk": "850",
"lyra2rev2-vol": "0",
"lyra2rev2-asic-x": "4",
"lyra2rev2-asic-y": "24",
"lyra2rev2-asic-num": "50",
"lyra2rev2-cutofftemperature": "50",
"lyra2rev2-cutofffanspeedin": "100",
"lyra2rev2-cutofffanspeedout": "100",
"lyra2rev2-restarthashrate": "3",
"lyra2rev2-restartfailedcount": "100",
"lyra2rev2-fan": "LV1",
"lyra2rev2-check-testnonce": true,
"lyra2rev2-scan-serial": "\/dev\/ttyS3",
"lyra2rev2-restartenable": true,
"lyra2rev2-cutoffenable": true
}
and this is the results

hash rate quite erratic but never higher than 5GH

nicehash stats

any feedback or suggestion, very welcome
The Z1's seems to send a lot of stale shares(these are being shown as rejects on powermining pool, and seems to be doing the same on nicehash i see). That is software related issue, so i hope they will supply an update soon to fix this.
, but seems like lots of chips that does not work? If so, try to reduce frequency slightly.. You won`t get advertised hashrate, but maybe some more than now if those chips becomes active again. You would probably have to return the faulty hashing board