Prohashing Equihash pool not compatible with Antminer Z9

[rjenkin]

Hi everyone,

I was lucky to receive my Z9 last Friday and tried the equihash Prohashing pool. It doesn't work unfortunately. For now I'm having to use MiningPoolHub but would love to switch it to Prohashing. I realise this is a new unit and am not sure what the issue is. Anyway, I'm happy to assist with testing in getting this working. It's the first of a fairly large amount of Z9s coming over the next three months so I'm guessing it's worth the effort from the Prohashing side to get it working?

Best wishes,

Robert

[Eyedol-X]

Hi everyone,

I was lucky to receive my Z9 last Friday and tried the equihash Prohashing pool. It doesn't work unfortunately. For now I'm having to use MiningPoolHub but would love to switch it to Prohashing. I realise this is a new unit and am not sure what the issue is. Anyway, I'm happy to assist with testing in getting this working. It's the first of a fairly large amount of Z9s coming over the next three months so I'm guessing it's worth the effort from the Prohashing side to get it working?

Best wishes,

Robert

I suspected this was going to happen, I too have at least 1 coming and was hoping to use it here

[Steve Sokolowski]

Hi everyone,

I was lucky to receive my Z9 last Friday and tried the equihash Prohashing pool. It doesn't work unfortunately. For now I'm having to use MiningPoolHub but would love to switch it to Prohashing. I realise this is a new unit and am not sure what the issue is. Anyway, I'm happy to assist with testing in getting this working. It's the first of a fairly large amount of Z9s coming over the next three months so I'm guessing it's worth the effort from the Prohashing side to get it working?

Best wishes,

Robert

Could you tell me a little more information about the problem? When you say that the miner "doesn't work," are you having trouble connecting to the system at all? Or, does the error occur during authorization? If so, could you tell me what the error message is that is being returned from mining.authorize()?

[rjenkin]

Hi Steve,

I rented it on miningrigrentals for 24 hours so will follow-up on this tomorrow. From memory it broke the miner pretty badly, I had to do a full hardware reset on it

I did save the logs though from when I was trying with Prohashing, not sure if these are useful:
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
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0938d00, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
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: 205928K/245760K available (5317K kernel code, 230K rwdata, 1844K rodata, 1024K init, 222K bss, 23448K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc07fe410 (8154 kB)
.init : 0xc0800000 - 0xc0900000 (1024 kB)
.data : 0xc0900000 - 0xc0939a60 ( 231 kB)
.bss : 0xc0939a60 - 0xc09713e8 ( 223 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16

On the mining page of the interface no chains showed at all and no mining information at all so there is no feedback at all as to if it was connecting OK or whatever.

[Steve Sokolowski]

Unfortunately, these logs don't contain a record of any communications with the mining server, so as you thought, they won't be useful for debugging.

You mentioned Miningrigrentals. Did you try to pass hashrate through Miningrigrentals to here, or were you directly connected to here? If you tried to pass hashrate through Miningrigrentals, it's possible that their servers could have been blocked due to abuse of their services. We plan to work with them to deal with that problem later this week.

If you tried to directly connect, then what we need is the log of communications between your system and the mining servers. Most miners have the ability to look at the stratum protocol messages. Specifically, I need to know whether the miner is able to connect at all. If it can't, that indicates a network problem. If it can, then the stratum logs will provide the error message returned by the server, or they will stop at whatever command caused the miner to crash, and we can continue from there.

[rjenkin]

I will look when I get the miner back, I was connected as usual on prohashing.com:3333 directly. It's an antminer with the standard interface, not sure where you can pull up such messages, if you know how to do it on other Antminer's let me know as I'm sure it will be the same.

[Steve Sokolowski]

Is it possible that the issue is the set_difficulty command?

If so, tonight once the new server is released, you'll be able to connect to the algorithm-specific equihash port and only set_target will be sent.

[Eyedol-X]

Is it possible that the issue is the set_difficulty command?

If so, tonight once the new server is released, you'll be able to connect to the algorithm-specific equihash port and only set_target will be sent.

Awesome!

[rjenkin]

Just to let you know that I tried today with the algorithm specific port and everything works fine. I'm actually able to overclock the thing to 15k/sol and run stable

[Eyedol-X]

Just to let you know that I tried today with the algorithm specific port and everything works fine. I'm actually able to overclock the thing to 15k/sol and run stable

Thanks for the follow up post, I will have my Z9 soon and this is good to hear.