Topic: Bitmain launches the Z9 Equihash miner - page 4. (Read 37202 times)
Getting 50k sols at 550 turbo mode, not bad.
Daily profit?
Daily profit is not the only thing concerning while buying mining equipment. There are many other factors like electricity cost etc, Because the price of electricity decide your profit. You don't specify the country for profit but let me tell you profit average in U.S.Period /day /month /year
Income $4.71 $141.27 $1,695.27
(0.0007 BTC) (0.022 BTC) (0.2649 BTC)
Electricity -$0.94 -$28.08 -$336.96
Profit $3.77 $113.19 $1,358.31
source https://www.asicminervalue.com/miners/bitmain/antminer-z9-mini
Folk,
I have created a post with information about the released firmware at https://bitcointalksearch.org/topic/efudd-z-series-fuddware-23-z11z11ez11jz9mini-5036968 - I welcome testing, feedback, and positive discussion.
As of that post, the 575Mhz version is available, and I will continue working on the fully unlocked version based on the feedback received.
-j
I have created a post with information about the released firmware at https://bitcointalksearch.org/topic/efudd-z-series-fuddware-23-z11z11ez11jz9mini-5036968 - I welcome testing, feedback, and positive discussion.
As of that post, the 575Mhz version is available, and I will continue working on the fully unlocked version based on the feedback received.
-j
A fully unlocked version is now available. I have updated information in the thread quoted here.
Thank you,
jason
Folk,
I have created a post with information about the released firmware at https://bitcointalksearch.org/topic/efudd-z-series-fuddware-23-z11z11ez11jz9mini-5036968 - I welcome testing, feedback, and positive discussion.
As of that post, the 575Mhz version is available, and I will continue working on the fully unlocked version based on the feedback received.
-j
I have created a post with information about the released firmware at https://bitcointalksearch.org/topic/efudd-z-series-fuddware-23-z11z11ez11jz9mini-5036968 - I welcome testing, feedback, and positive discussion.
As of that post, the 575Mhz version is available, and I will continue working on the fully unlocked version based on the feedback received.
-j
Alright -- I've successfully overclocked the Z9 and I can now build flashable images so the modifications persist across reboot. I'll post a new thread in Altcoins later today with a link to the 575Mhz image that others can test with.
Thank you for keeping us posted as well as for documenting your process! I hope you'll add a link here to your Altcoins post when it goes up, very curious to try this out!
Just got Z9 shipping notice, and US Customs bill for $900!
Could be the last miner I buy direct from Bitmain under these tariffs...
Could be the last miner I buy direct from Bitmain under these tariffs...
Alright -- I've successfully overclocked the Z9 and I can now build flashable images so the modifications persist across reboot. I'll post a new thread in Altcoins later today with a link to the 575Mhz image that others can test with.
Thanks,
Jason
Thanks,
Jason
If you are looking for coins to mine and a pool to mine it on, get on ZCL coin and this pool allows asics :
https://pool.zclassicblue.org/
Best pool i've found so far as ZCL is tricky to get pools working for asics
z9 mini and z9 compatible
https://pool.zclassicblue.org/
Best pool i've found so far as ZCL is tricky to get pools working for asics
z9 mini and z9 compatible
New pool? How new is this pool? When I did a quick look it seems not many miners (only 9 right now).
What's your measurement that you use to declare it the best pool for you?
I've been testing a lot of big pools for zcl mining with asics and they arent configured right and get invalid shares on their end, this pool is created by the zcl team themselves and they designed it to work for asics . Im posting it on here to get more people on it obviously I would like to see more hash but it is healthy atm and has 0 fee.
If you are looking for coins to mine and a pool to mine it on, get on ZCL coin and this pool allows asics :
https://pool.zclassicblue.org/
Best pool i've found so far as ZCL is tricky to get pools working for asics
z9 mini and z9 compatible
https://pool.zclassicblue.org/
Best pool i've found so far as ZCL is tricky to get pools working for asics
z9 mini and z9 compatible
lol There is like... 2 z9 running on that entire pool at 100kh total.
If you are looking for coins to mine and a pool to mine it on, get on ZCL coin and this pool allows asics :
https://pool.zclassicblue.org/
Best pool i've found so far as ZCL is tricky to get pools working for asics
z9 mini and z9 compatible
https://pool.zclassicblue.org/
Best pool i've found so far as ZCL is tricky to get pools working for asics
z9 mini and z9 compatible
Anyone happen to know how to get into the serial console on currently shipping Antminer control boards? I'm looking at "Miner_Ctrlboard_V1.1" which is used in at least the Z9mini and Z9 (and I believe V9 also). I'm trying to use a buspirate right on the TX/RX/GND pins with no luck. I'm wondering if it isn't designed have it so you have to short something else on boot to enable serial terminal now.
Any pointers would be welcomed (I have and am continuing to search/try).
*EDIT*: Was able to get into the serial ports -- my buspirate was bad.. and you have to invert the logic on the RX side.
... But now I am in at the lowest levels of this thing. More fun ensues.
-j
Any pointers would be welcomed (I have and am continuing to search/try).
*EDIT*: Was able to get into the serial ports -- my buspirate was bad.. and you have to invert the logic on the RX side.
... But now I am in at the lowest levels of this thing. More fun ensues.
Code:
Xilinx First Stage Boot Loader
Release 2017.1 Mar 12 2018-19:08:47
Devcfg driver initialized
Silicon Version 3.1
Boot mode is NAND
InitNand: Geometry = 0x8
Nand driver initialized
NAND Init Done
Flash Base Address: 0xE1000000
Reboot status register: 0x60400000
Multiboot Register: 0x0000C000
Image Start Address: 0x00000000
Partition Header Offset:0x00000C80
Partition Count: 3
Partition Number: 1
Header Dump
Image Word Len: 0x0007F2E8
Data Word Len: 0x0007F2E8
Partition Word Len:0x0007F2E8
Load Addr: 0x00000000
Exec Addr: 0x00000000
Partition Start: 0x000075D0
Partition Attr: 0x00000020
Partition Checksum Offset: 0x00000000
Section Count: 0x00000001
Checksum: 0xFFE7AF06
Bitstream
In FsblHookBeforeBitstreamDload function
PCAP:StatusReg = 0x40000A30
PCAP:device ready
PCAP:Clear done
Level Shifter Value = 0xA
Devcfg Status register = 0x40000A30
PCAP:Fabric is Initialized done
PCAP register dump:
PCAP CTRL 0xF8007000: 0x4C00E07F
PCAP LOCK 0xF8007004: 0x0000001A
PCAP CONFIG 0xF8007008: 0x00000508
PCAP ISR 0xF800700C: 0x0802000B
PCAP IMR 0xF8007010: 0xFFFFFFFF
PCAP STATUS 0xF8007014: 0x50000F30
PCAP DMA SRC ADDR 0xF8007018: 0x00100001
PCAP DMA DEST ADDR 0xF800701C: 0xFFFFFFFF
PCAP DMA SRC LEN 0xF8007020: 0x0007F2E8
PCAP DMA DEST LEN 0xF8007024: 0x0007F2E8
PCAP ROM SHADOW CTRL 0xF8007028: 0xFFFFFFFF
PCAP MBOOT 0xF800702C: 0x0000C000
PCAP SW ID 0xF8007030: 0x00000000
PCAP UNLOCK 0xF8007034: 0x757BDF0D
PCAP MCTRL 0xF8007080: 0x30800100
DMA Done !
FPGA Done !
In FsblHookAfterBitstreamDload function
Partition Number: 2
Header Dump
Image Word Len: 0x000216CC
Data Word Len: 0x000216CC
Partition Word Len:0x000216CC
Load Addr: 0x04000000
Exec Addr: 0x04000000
Partition Start: 0x000868C0
Partition Attr: 0x00000010
Partition Checksum Offset: 0x00000000
Section Count: 0x00000001
Checksum: 0xF7F1506A
Application
Handoff Address: 0x04000000
In FsblHookBeforeHandoff function
SUCCESSFUL_HANDOFF
FSBL Status = 0x1
U-Boot 2016.07-g7640c9f-dirty (Feb 27 2018 - 17:57:23 +0800)
Model: Zynq MicroZED Board
Board: Xilinx Zynq
DRAM:
dram_init: sys_sdram_size = 0x10000000
dram_init: sys_sdram_size = 256 MB
dram_init: gd->ram_size = 0x0f000000
ECC disabled 240 MiB
NAND: 256 MiB
MMC: sdhci@e0100000: 0
Invalid bus 0 (err=-1)
*** Warning - spi_flash_probe() failed, using default environment
In: serial@e0000000
Out: serial@e0000000
Err: serial@e0000000
Model: Zynq MicroZED Board
Board: Xilinx Zynq
board_late_init: bootargs: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
--- boot gpio value = 0x003fff3c
--- nand boot nand ---
Net: --- phy_broadcom_init
ZYNQ GEM: e000b000, phyaddr 0, interface gmii
--- zynq_gem_probe
--- mdio_register
--- mdio_register 1
--- mdio_register 2
--- mdio_register 3
--- zynq_phy_init: interface = 1
--- zynq_phy_init
0000000000
PHY is not detected
GEM PHY init failed
No ethernet found.
Hit any key to stop autoboot: 0
Copying Linux from NAND flash to RAM...
NAND read: device 0 offset 0x2000000, size 0x800000
8388608 bytes read: OK
NAND read: device 0 offset 0x1a00000, size 0x20000
131072 bytes read: OK
Copying ramdisk...
NAND read: device 0 offset 0x2800000, size 0x2000000
33554432 bytes read: OK
## Booting kernel from Legacy Image at 02000000 ...
Image Name: Linux-4.6.0-xilinx-gff8137b-dirt
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3851576 Bytes = 3.7 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy for 0, Image at 04000000 ...
Image Name:
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 12693249 Bytes = 12.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
get ramdisk ok
## Flattened Device Tree blob at 03000000
Booting using the fdt blob at 0x3000000
Loading Kernel Image ... OK
Loading Ramdisk to 0cee5000, end 0dafff01 ... OK
Loading Device Tree to 0cee0000, end 0cee4d99 ... OK
Starting kernel ...
Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #22 SMP PREEMPT Fri Dec 22 12:25:44 CST 2017
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 205988K/245760K available (5317K kernel code, 230K rwdata, 1844K rodata, 1024K init, 222K bss, 23388K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
....
-j
Update: I've managed to remove the limits they put in place and can re-enable full frequency selection. I'm still working on building an image that others can test with.
"Soon(tm)".
-j
"Soon(tm)".
-j
Are you also adjusting voltage?
Update: I've managed to remove the limits they put in place and can re-enable full frequency selection. I'm still working on building an image that others can test with.
"Soon(tm)".
-j
"Soon(tm)".
-j
Could see it happening on the mini's. A dedicated effort to reduce failure. Less warranty claims potentially? Better for their budget (since it's news now). Imagine any of these companies following these threads to learn to make their gear better or how a consumer prefers them.
Success. I have overclocked my Z9 to 650... here's a picture of it at 600.
https://imgur.com/n87ky6J
I'm going to let this 650 run for a while to check stability. The change I have made is hard coded at the moment, it'll take me a little longer to make something that should work for others... and even longer to make an image we can just install (maybe).
-j
https://imgur.com/n87ky6J
I'm going to let this 650 run for a while to check stability. The change I have made is hard coded at the moment, it'll take me a little longer to make something that should work for others... and even longer to make an image we can just install (maybe).
-j
Definitely looking forward to what you come up with keep us posted
I'm running mine at 681Mhz now. At 700 the voltage regulators start to cut back voltage, power draw and hashrates bottom out. I haven't tested to see how far I can push past 681 that I randomly selected.
What I'm doing is lost on each reboot. I'm working to build an image that can be flashed to the Z9 that will let it run up to 575Mhz and will persist across reboots. My first attempt at a flashable image failed and until I can connect to to a serial console on these boards, I won't be able to troubleshoot it.
What bitmain has done is purposefully try to lock these down -- I'm still hoping to be able to restore the ability to select 500-750Mhz or so, but that is on the backburner at the moment.
My next goal is to build that test image and get some feedback. Given the fact that my last image bricked it, I'm going to have to connect to the serial on the unit and see why it failed.
I also expect that the tactic they have used here may apply to more of their product line... but one thing at a time.
-j
Anyone know how to fix a 'bricked' Z9? 
Yeah - read through a bunch of useless bitmain articles, piece together components, find the recovery for "V9-Tools.zip", pretend your Z9 is a V9, extract that V9-tools.zip to your 32GB or less FAT32 formatted SD card, power off miner, insert SD card, power on, wait for all lights but ethernet to go off (~60 seconds), unplug miner, remove SD card, replug miner in.
Then go find the Z9 firmware image and use the web interface to flash your "V9" back to a "Z9" while unchecking the option to "Keep Settings".
Once that reboots, congratulations, you now have 1 factory hobbled Z9 back up and running.
-j
Success. I have overclocked my Z9 to 650... here's a picture of it at 600.
https://imgur.com/n87ky6J
I'm going to let this 650 run for a while to check stability. The change I have made is hard coded at the moment, it'll take me a little longer to make something that should work for others... and even longer to make an image we can just install (maybe).
-j
https://imgur.com/n87ky6J
I'm going to let this 650 run for a while to check stability. The change I have made is hard coded at the moment, it'll take me a little longer to make something that should work for others... and even longer to make an image we can just install (maybe).
-j
Definitely looking forward to what you come up with keep us posted
btw the zec difficulty chart is through the roof
i received my Z9 mini 3 days ago, overclocked it to 743 about 5 hours ago, fan 100% (i dont care about the noise), temp of the cells is 58 celcius
so far i have an average of around 17 KH/s with peaks at up to 25KH/S
edit: also without overlocking it was around 11 KH/S, so it was pretty good even though it was running at 500
so far i have an average of around 17 KH/s with peaks at up to 25KH/S
edit: also without overlocking it was around 11 KH/S, so it was pretty good even though it was running at 500
At aoutomatic fan speed it will let it go to about 70 degrees celsius and try to keep it there as max.
at 80 degrees it restarts.
Soo..
You probably don't need to keep it at 58 degrees.
Every degree will cost som fan speed?
try to find a sweetspot where it runs stable and save the fan a little.
Just my thoughts !!!
i thought about that but i did some research and found that having the fan set to 100% is no problem. It makes a very big noise but i dont mind, i guess only time will tell about the durability. Also If the fan gets fucked its not as much of a problem as if its the chips
i'll see in a few days the average, but when i saw it was doing peaks at 24-25KH/S i was like wtf
Whatever works for you!!!
What pool do you use to mine at when you get peaks like 24-25 KSols/s ? ? ?
i received my Z9 mini 3 days ago, overclocked it to 743 about 5 hours ago, fan 100% (i dont care about the noise), temp of the cells is 58 celcius
so far i have an average of around 17 KH/s with peaks at up to 25KH/S
edit: also without overlocking it was around 11 KH/S, so it was pretty good even though it was running at 500
so far i have an average of around 17 KH/s with peaks at up to 25KH/S
edit: also without overlocking it was around 11 KH/S, so it was pretty good even though it was running at 500
At aoutomatic fan speed it will let it go to about 70 degrees celsius and try to keep it there as max.
at 80 degrees it restarts.
Soo..
You probably don't need to keep it at 58 degrees.
Every degree will cost som fan speed?
try to find a sweetspot where it runs stable and save the fan a little.
Just my thoughts !!!
i thought about that but i did some research and found that having the fan set to 100% is no problem. It makes a very big noise but i dont mind, i guess only time will tell about the durability. Also If the fan gets fucked its not as much of a problem as if its the chips
i'll see in a few days the average, but when i saw it was doing peaks at 24-25KH/S i was like wtf
Jump to: