You probably need to set fixed difficulty, Z1+ does 7.2GH/s and higher if configured properly.
what would you recommend for difficulty setting?
Topic: Dayun Zig Z1 - Lyra2Rev2 6.8GH/s Asic miner - page 10. (Read 42511 times)
what would you recommend for difficulty setting?
Hi,
my Z1 stopped working, I can log in via http (shows offline status) and SSH, but all I get is:
root@dayun:~# miner
[2019-01-11 20:59:27] Started cgminer 4.11.1
[2019-01-11 20:59:27] All devices disabled, cannot mine!
Is that hardware malfunction? How to repair it?
Thanks.
my Z1 stopped working, I can log in via http (shows offline status) and SSH, but all I get is:
root@dayun:~# miner
[2019-01-11 20:59:27] Started cgminer 4.11.1
[2019-01-11 20:59:27] All devices disabled, cannot mine!
Is that hardware malfunction? How to repair it?
Thanks.
The Z1+ is logging to the flash drive, which will kill cheap flash in quick order. An external drive would actually be faster, as well as more reliable.
Does anyone else's Z1+ seem to eat USB sticks? Admittedly I bought some pretty cheap 16+32GB models during holiday sales... but I've had two go so bad Windows can't write to them (fail formatting, or show as read-only) and a third that fails to verify firmware flashes. Makes me wonder if I could boot from an external HDD - yes it would be slower, but maybe it would be more durable?
Is there a difference in firmware upgrade file or firmware update file? What is the upgrade firmware that you can do in the zig z1 interface page? Is the interface page for different firmware then what you put on the flash drive? This zig z1 miner is a piece of crap!! If someone would like to tell me the difference between the flash drive firmware and the firmware you can do right in the miner interface page that would be awesome!!
Hello,
I have my Zig Z1 since middle of october 2018.
I have a problem with my Zig Z1.
About 2 weeks ago, I was not able to connect via internet on my Zig Z1 but it was continuing to do mining. So yesterday I decide to do power off then power on my router and my Zig Z1 but now I can not see on internet and it's not mining. I used some software to give me the list of what ip adress is on my network but I can not see my Zig Z1.
Does someone have and idea of what I can do to fix that?
Thank-you
Daniel
you can use modem interface to find miner's ip. you can see ip there if you have a chance to log in modem. I have my Zig Z1 since middle of october 2018.
I have a problem with my Zig Z1.
About 2 weeks ago, I was not able to connect via internet on my Zig Z1 but it was continuing to do mining. So yesterday I decide to do power off then power on my router and my Zig Z1 but now I can not see on internet and it's not mining. I used some software to give me the list of what ip adress is on my network but I can not see my Zig Z1.
Does someone have and idea of what I can do to fix that?
Thank-you
Daniel
What do you mean by modem interface, do you mean to connect on my router and check the ip adress ?
Thank
Hello,
I have my Zig Z1 since middle of october 2018.
I have a problem with my Zig Z1.
About 2 weeks ago, I was not able to connect via internet on my Zig Z1 but it was continuing to do mining. So yesterday I decide to do power off then power on my router and my Zig Z1 but now I can not see on internet and it's not mining. I used some software to give me the list of what ip adress is on my network but I can not see my Zig Z1.
Does someone have and idea of what I can do to fix that?
Thank-you
Daniel
you can use modem interface to find miner's ip. you can see ip there if you have a chance to log in modem. I have my Zig Z1 since middle of october 2018.
I have a problem with my Zig Z1.
About 2 weeks ago, I was not able to connect via internet on my Zig Z1 but it was continuing to do mining. So yesterday I decide to do power off then power on my router and my Zig Z1 but now I can not see on internet and it's not mining. I used some software to give me the list of what ip adress is on my network but I can not see my Zig Z1.
Does someone have and idea of what I can do to fix that?
Thank-you
Daniel
Glad to inform followers on this thread ,new Innosilicon A9 ( 60ksol/s ,updated version ) ready to show now !!!
https://www.akminer.com/all-products/new-a9-zmaster-60ksol-s-ship-now
The fact that there is a new ASIC, different algo, that is moire profitable coming out soon is not good news to followers of this thread. Lol
I have been using Zig1 since release. All of a sudden I cannot load the dashboard anymore and so cannot get my Zig1s to operate. Every time I try to load the page it is showing "Internal Error Occurred". Can anyone advise me on how to fix this?"
I think there is no way but to renew the firmware
Hello,
I have my Zig Z1 since middle of october 2018.
I have a problem with my Zig Z1.
About 2 weeks ago, I was not able to connect via internet on my Zig Z1 but it was continuing to do mining. So yesterday I decide to do power off then power on my router and my Zig Z1 but now I can not see on internet and it's not mining. I used some software to give me the list of what ip adress is on my network but I can not see my Zig Z1.
Does someone have and idea of what I can do to fix that?
Is it possible that the software on the usb key near to the ethernet cable is the problem? (this answer was yes)
Thank-you
Daniel
UPDATE:
Finaly I succed. The usb key was not good. I bought a good 16 Gb usb key. And I have install a new image on it. I took all the information at this link: https://drive.google.com/drive/folders/1Y1YXEgEnIFVnmzmD7PaTAMrVEDikTrfR
At the beginning the ip adress is 192.168.1.100, so I had to go to my router and to be sure that is on this segment (I put mine 192.168.1.1). After I changed in the MENU of the Zig Z1 to put automatic DHCP. After that, it will connect automaticaly on any router.
I have my Zig Z1 since middle of october 2018.
I have a problem with my Zig Z1.
About 2 weeks ago, I was not able to connect via internet on my Zig Z1 but it was continuing to do mining. So yesterday I decide to do power off then power on my router and my Zig Z1 but now I can not see on internet and it's not mining. I used some software to give me the list of what ip adress is on my network but I can not see my Zig Z1.
Does someone have and idea of what I can do to fix that?
Is it possible that the software on the usb key near to the ethernet cable is the problem? (this answer was yes)
Thank-you
Daniel
UPDATE:
Finaly I succed. The usb key was not good. I bought a good 16 Gb usb key. And I have install a new image on it. I took all the information at this link: https://drive.google.com/drive/folders/1Y1YXEgEnIFVnmzmD7PaTAMrVEDikTrfR
At the beginning the ip adress is 192.168.1.100, so I had to go to my router and to be sure that is on this segment (I put mine 192.168.1.1). After I changed in the MENU of the Zig Z1 to put automatic DHCP. After that, it will connect automaticaly on any router.
Bad news 
This release contains the proposed upcoming Vertcoin main network hard fork to the new Lyra2REv3 mining algorithm at block 1080000 in order to rid the network of the current generation of Lyra2REv2 ASICs and FPGAs. It also contains the hard fork for the test network which already occurred at block 158221. The related pull request is here: #72. The difficulty will be forced down to 0x1b0ffff0 for 10 blocks after the fork before the usual KGW difficulty adjustment algorithm kicks in again to prevent the network from stalling due to the large expected decrease in network hashrate post-fork.
This release contains the proposed upcoming Vertcoin main network hard fork to the new Lyra2REv3 mining algorithm at block 1080000 in order to rid the network of the current generation of Lyra2REv2 ASICs and FPGAs. It also contains the hard fork for the test network which already occurred at block 158221. The related pull request is here: #72. The difficulty will be forced down to 0x1b0ffff0 for 10 blocks after the fork before the usual KGW difficulty adjustment algorithm kicks in again to prevent the network from stalling due to the large expected decrease in network hashrate post-fork.
Monacoin, the last hope...
Yeah I mean VTC was always planning to fork around ASICs, so this was to be 100% expected. Surprised it took so long honestly. We forked more than once before, and will fork around any ASICs in the future.
Mona is a tag-along coin that I guess you will all be forced to mine now. Or some other obscure shitcoin. VTC made the Lyra2REv2 algo and Mona just decided to take the algo. Thats fine, thats open source code, but now that VTC devs made Lyra2REv3 I wouldn't put it below the Mona devs to fork to it as well. We shall see. To be honest it will be nice to see the ASICs gone from "The peoples coin." VTC I believe will soon make it back into the top of GPU mineable coins.
Bad news
This release contains the proposed upcoming Vertcoin main network hard fork to the new Lyra2REv3 mining algorithm at block 1080000 in order to rid the network of the current generation of Lyra2REv2 ASICs and FPGAs. It also contains the hard fork for the test network which already occurred at block 158221. The related pull request is here: #72. The difficulty will be forced down to 0x1b0ffff0 for 10 blocks after the fork before the usual KGW difficulty adjustment algorithm kicks in again to prevent the network from stalling due to the large expected decrease in network hashrate post-fork.
eeeeeee baby! This release contains the proposed upcoming Vertcoin main network hard fork to the new Lyra2REv3 mining algorithm at block 1080000 in order to rid the network of the current generation of Lyra2REv2 ASICs and FPGAs. It also contains the hard fork for the test network which already occurred at block 158221. The related pull request is here: #72. The difficulty will be forced down to 0x1b0ffff0 for 10 blocks after the fork before the usual KGW difficulty adjustment algorithm kicks in again to prevent the network from stalling due to the large expected decrease in network hashrate post-fork.
Bad news
This release contains the proposed upcoming Vertcoin main network hard fork to the new Lyra2REv3 mining algorithm at block 1080000 in order to rid the network of the current generation of Lyra2REv2 ASICs and FPGAs. It also contains the hard fork for the test network which already occurred at block 158221. The related pull request is here: #72. The difficulty will be forced down to 0x1b0ffff0 for 10 blocks after the fork before the usual KGW difficulty adjustment algorithm kicks in again to prevent the network from stalling due to the large expected decrease in network hashrate post-fork.
This release contains the proposed upcoming Vertcoin main network hard fork to the new Lyra2REv3 mining algorithm at block 1080000 in order to rid the network of the current generation of Lyra2REv2 ASICs and FPGAs. It also contains the hard fork for the test network which already occurred at block 158221. The related pull request is here: #72. The difficulty will be forced down to 0x1b0ffff0 for 10 blocks after the fork before the usual KGW difficulty adjustment algorithm kicks in again to prevent the network from stalling due to the large expected decrease in network hashrate post-fork.
Monacoin, the last hope...
Bad news
This release contains the proposed upcoming Vertcoin main network hard fork to the new Lyra2REv3 mining algorithm at block 1080000 in order to rid the network of the current generation of Lyra2REv2 ASICs and FPGAs. It also contains the hard fork for the test network which already occurred at block 158221. The related pull request is here: #72. The difficulty will be forced down to 0x1b0ffff0 for 10 blocks after the fork before the usual KGW difficulty adjustment algorithm kicks in again to prevent the network from stalling due to the large expected decrease in network hashrate post-fork.
This release contains the proposed upcoming Vertcoin main network hard fork to the new Lyra2REv3 mining algorithm at block 1080000 in order to rid the network of the current generation of Lyra2REv2 ASICs and FPGAs. It also contains the hard fork for the test network which already occurred at block 158221. The related pull request is here: #72. The difficulty will be forced down to 0x1b0ffff0 for 10 blocks after the fork before the usual KGW difficulty adjustment algorithm kicks in again to prevent the network from stalling due to the large expected decrease in network hashrate post-fork.
I have been using Zig1 since release. All of a sudden I cannot load the dashboard anymore and so cannot get my Zig1s to operate. Every time I try to load the page it is showing "Internal Error Occurred". Can anyone advise me on how to fix this?"
You probably need to set fixed difficulty, Z1+ does 7.2GH/s and higher if configured properly.
https://www.zigminer.com/image/cache/catalog/banner/banner_z1+-1920x780.png
see this, truely spec Zig Z1+ is only 7.0Gh/s but in realized run only 6.5-6.6Gh/s
see this, truely spec Zig Z1+ is only 7.0Gh/s but in realized run only 6.5-6.6Gh/s
Good news for followers in this thread ,AKminer is selling Whatsminer D1 with very competitive price ( Jan pre-order batch )
https://www.akminer.com/all-products/new-dcr-master-whatsminer-d1-48th-s-with-psu-shipout-ships-on-january-20-30-2019
https://www.akminer.com/all-products/new-dcr-master-whatsminer-d1-48th-s-with-psu-shipout-ships-on-january-20-30-2019
WOW thats great news!! Very competition, fastest ROI.
Can I flash my Z1+ with the competetive priced Whatsminer D1?
I think I figured out the problem, it was switching pools like crazy (I had the same pool 3 times in the cases)...but shouldn't it stop consuming while switching, and the end result shouldn't it be the same? Also it was mining on very low difficulty from what I could see, but the rejects were still low...Anyways, put a version that is 2 releases back and it works now, it stopped jumping around, and shows OK hashrate (not the best but acceptable). The bad thing now is that I can't spin down the rpm on the fans...so no way to keep it in the house.
What makes you so sure that it's being stolen? Have you seen it sending shares to a foreign pool? Have you tried reducing the OC? It is very possible it is just malfunctioning, error reporting is not really guaranteed to work properly, especially when overclocking.
Jump to: