 Show Posts
|
|
Pages: [1] 2 »
|
|
Thanks for the update -- FLUX works really well running it on NVIDIA and AMD rigs -- only issue I have is with rx 5500xt (8gb) -- miner program will not recognise the card -- will run the 5600xt on the same rig. BTW getting about the same as lolminer on the AMD cards -- but better stability.
|
|
|
|
I got the same issue . was running version 1.88 on Windows 10 pro on all my rigs without any problem.
From what I have been reading apparently the dev pool table that gminer calls on was screwed up -- couple of pool admins say it has been fixed. keep my fingers crossed. |
|
|
|
|
still getting dev fee pools unavailable -- running latest version v1.96 on windows 10 pro mining cuckrood29 -- no issue on linux version running multiple rigs.
|
|
|
|
|
Really nice job on the rainforest algo -- used auto on rig with 480/570/580 8gb working wonderfully. Oc'd on core left mem at stock and power alone.
|
|
|
|
linux version v0.15.3 on linux thrwing huge errors on x16rt -- downgraded to 0.15.2 no issues.
What errors? What cards? Please, specify more details. sorry should have been more specific, I apologize. Specifically, 90%+ of the shares were being rejected off of all the gpus (rx580 8gb). No other descriptive errors were given -- when I backed off one release it was fine. Mining Gincoin on Gos.cx. I should mention I am mining on SMOS. |
|
|
|
|
linux version v0.15.3 on linux thrwing huge errors on x16rt -- downgraded to 0.15.2 no issues.
|
|
|
|
|
So it has been pretty much a week that I have been running both the z9 software (1 unit) and z9 mini software (2 units) version 2.1. The results are impressive overall this has been equivalent for me of adding a z9 mini batch 1 overclocked without having to purchase the hardware with an incremental increase in power consumption. (a total of 100w on the two mini's) have not measured the Z9. So well worth it thanks. One of the z9 mini's was a batch 1 so only a small increase was to be had.
|
|
|
|
I bought one yesterday. I was up and running in a couple of minutes. The whole process from purchase to mining took maybe twenty minutes. The set up of the unit is intuitive and easy. Did not need to access any support. One thing people should be aware of in the hosted environment there is a restriction on pools and coins. The choice will be expanded over the coming months. I have requested some additional pools be added, however, I am not the first. It appears from their discord channel that they are concentrating on bitstream development. For me, this is an easy way to get into FGPA mining. I have tested most of the bitstreams to confirm hashrates and they are within +-5% -- very pleased -- now just need to make the purchase price back. :-)  |
|
|
|
Worked wonders for me too -- thanks for the tip about prohashing -- found it reflects a much more consistent hashrate -- has done wonders for my Z9's too. I have been mining the Zig Z1 for a couple of weeks now -- have tried a number of sites -- individual coins and multi-coin sites -- best I have come across so far a Prohash and Zpool. I found suprnova had issues with the hashrate falling off precipitously, experienced a less severe gradual decline at blockmaster as well. Zpool seems to be consistent however have to reboot machine every two to three days or so to keep hashrate up. Running at 850mhs -- average hashrate 6-6.2.
Try what was noted earlier in the forum... Change the foillowing in an exported JSON: From: "auto_frequent":"0","frequency":"850" to "auto_frequent":"1","frequency":"1000" It worked wonders for me. |
|
|
|
|
I have been mining the Zig Z1 for a couple of weeks now -- have tried a number of sites -- individual coins and multi-coin sites -- best I have come across so far a Prohash and Zpool. I found suprnova had issues with the hashrate falling off precipitously, experienced a less severe gradual decline at blockmaster as well. Zpool seems to be consistent however have to reboot machine every two to three days or so to keep hashrate up. Running at 850mhs -- average hashrate 6-6.2.
|
|
|
|
Hello,
I need your help, i have buying a zig z1 and after lot difficulty to doing boot the miner i have finally started it and let mine for 12 hours, after that, i have moved miner on another place and now i can't setting again, i don't understand why, all setting don't save, it return always on factory set and so i can't launch the miner.
Have you an idea where is the problem, i have burn the key again, reset miner and router, but always the same thing, impossible to save setting.
Thx for your help.
what are your settings? have you set starting freq to 800 or 850 -- i would start at 800 and work your way up |
|
|
|
|
Pointed a Z9 and Z9 mini at your equihash algo pool last night. It appears to have mined -- when checking the miners I found that even though they were set up on hub workers not both of those workers were showing up under the coin being mined -- in the case of Zcash both would register, Horizon -- just one and Zclassic neither -- but the coins appear to have been mined. Is there some setting I need to use. Little frustration on my end as I like to see hashrates.
|
|
|
|
Great summary below -- the only thing I would add is I set freq at 800, but seems to be unit dependent -- has been running solid for three days no drops and I added #xnsub to the pool address found it evened out the hashrates (less errors and stale shares) and less 0 hashrates -- found the sweet spot for the hashrate in my case was between 5.5 and 6.2. The other thing is patience -- I am used to asics that boot quickly -- this thing does not -- let it sit for 5 -10 minutes or so before deciding it is not working. Hello
Just wanna share some infos with you guys about the Zig Z1
But i also have some questions...
User Inetrface
First of all, i like it. Lots of information, options and easy to understand.
What i don't like, is the fact that the temerature does not refresh and it's impossibible that the temp does not change.
Du you guys have this issue too?
Network/IP
I had to change the IP range of my router from 192.168.0.xxx to 192.168.1.xxx to find the miner in my home network.
I you leave it on DHCP (dynamic ip), you have to search the miner almost each time after a reboot or disconnect.
For that you can access you router to check the new IP of the miner. Or you can use a tool. I use "Baikal Monitor"
It's pretty easy to use and you don't need to install it. Just double click the exe file and it starts. Works for Baikal, Bitmain and Dayun miner.
A known issue (at least for my miner) is that it changes the ip, even if you set a static ip after you unplug the powersupply.
I the use the "Baikal Monitor" to finde the new IP. The i can access ist again...
The funny part about this is, that when i check the network settings of the miner, it shows the static ip that i set.
No idea why it just takes another IP. So i only have to hit the "Save And Restart Miner" button for the network settings and then it boots with the right IP.
Do you guys have this issue too?
Settings - Options: Auto Restart Miner and Auto Stop Miner
Before you do some changes here, make sure to set te refresh rate (to find on the same page) at 120-180 sec or higher.
I you change the settings and this page does a refresh before you hit "save", then you lose all settings and have to to it again...
Option: Auto Restart Miner
Higher HW Counting In 30 Sec
For me, this is the most importat setting here. I set it somwhere between 50-60%
So if my miner starts to generate some HW (hardware) errors and they exceed the 50-60% that i set, then the miner restarts.
Still not sure what exactly a HW error is. But as far as i understand it, it's wehn the chips start to fail and send totally wrong results or no results at all.
Not to be confused with %-Rejected rates.
Lower Hashrate in 5 Min
If the avarage hashrate drops below 4Gh/s in a time of 5 mins, the miners just restarts.
It's also a good thing to activate.
Option: Auto Stop Miner
Higher Core Temperature
I also recommand to activate this option. I set it 60°C (140°F)
What it does? It stops the miner if it overheats...
Lower FanSpeed In/Out
I think i set it between 65-70%
So if a fan goes below this value (risk of overheating) the miner stops.
ASIC Status
To get near the 6.8GH/s, all the chips on the "ASIC Stauts" page have to be green.
Here is what i do if they are not:
Go on the Settings page and just hit the "Save and Restart Miner" button.
Check after 2-3 mins on the "ASIC Status" page if its better. If not...hit that "Save and Restart Miner" button again.
Again, go check after 2-3 mins on the "ASIC Status" page if its better. If not, try this tome the "Save and Restart Machine" button.
Now wait 5mins and then check the "ASIC Status" page. If its's better...good, if not, pull the plug from the PSU and wait 10-15min.
Pull the plug back in and wait...
Again, check the "ASIC Status" page...if it's not better, repeate the steps above.
Sometime i need "only" 15 mins to make the chips all green.
One time it took my almost 1h...but it works.
Sometimes some chips need more time to turn from black to green.
So if most chips on a card are green and just a few black, i just wait 2-3mins and then they turn green.
Do you guys have this issue too?
And what do you do to make it work?
ASIC Status and Hashrate
All chips are green but you get 0GH/s on one card on the mainpage? (Local Miner Details)
Wait or manually refresh the page after 30 sec. Hashrate for this card back to normal? Good...no problem.
A good way to see if something is wrong is to check the AC value of the cards: Mainpage Local Miner Details
The AC value shows you the acceptet shares for each card.
If the difference is to big, then you know that one or more crads ar not working at full speed or not working al all even if alle chips are green.
The AC value of the 4 card should be the "same": +/- 5%
Well, that's it for now...
|
|
|
|
|
Had been having issues with hashrates and high rates of rejected shares on a number of pools. Reduced the freq to 800mhs, added #xnsub to the pool address -- has reduced the error rate significantly.
xnsub stands for extra-nonce subscription. For algorithms with very high difficulties and for miners with very high hashrates, it's possible for a miner to completely exhaust the nonce-space (that is, the value that is changed for each hash to try and find the valid hash).
Extranonce was created to allow the miners to change a small field in the coinbase to continue hashing again from the beginning, but with a slightly different block.
By subscribing you're telling NH (or any pool that supports it) that even though you've already submitted a certain nonce, it's actually a different block because of this extranonce field.
|
|
|
|
|
Rumours of a verge fork q1 2019 -- just rumours.
|
|
|
|
|
run both gpus and asics == keep an eye on returns -- return on multi-coin pools are not bad especially when on asics. Prefer to mine single coin on gpu's -- if you have s9's look at zergpools sha pool better return then btc.
|
|
|
|
|
you can do that on blockmaster/zergpool/zpool all mining lyra2rev2 pool payment in btc or ltc. Better return then nicehash.
|
|
|
|
|
Have one as well -- got it last night. Hashed for 15 minutes then died. Tried every trick in the book to bring it back up but nothing.
I ended up reimaging the USB with the updated software -- brought it back to life. Got rid of the flashing red light on the front of the unit -- guess the operating system (firmware) was corrupted.
Reduced the starting frequency to 800 mhs -- helped with stability.
Also, oddity I found was all three local miner destinations needed to be loaded otherwise unit would not boot.
I still get a "may not boot" message when rebooting and boot process takes a good 10 minutes before it starts hashing.
Hashing on blockmaster Lyra2rev2 pool at averaging at around 5.6 to 6.3 at the pool.
|
|
|
|
|
Have one as well -- yes noisy but run cold -- had all kinds of issues with the operating software -- had to reimage the usb upgrade to a newer operating system --
which pools are you mining -- using blockmaster -- can't get zergpool to connect or Zpool to hash.
performance is decent -- have it hashing between 5.5 to 6.5 ghs -- reduced the starting frequency to 800 mhs -- but the boot time takes forever.
|
|
|
|
Just logged into my account -- earnings gone workers gone -- no way to contact support -- what should I do?  I have pointed my L3's somewhere else until I get this resolved. Seems never resolved... Yep I agree -- listening to the deafening lack of any response. Won't be using this pool again until they sort out the support. I understand stuff happens -- but then they need to fix it. |
|
|
|
|
