Title: S17+ (70 TH/s) - Hashboard 3 Only Find 10 ASIC
Post by: franx47 on November 24, 2021, 06:19:25 AM
Hi. I have 1 unit of used Antminer S17+ (70 TH/s). From the 3 hashboards, chain 0 and 1 find 65 ASIC (work normally), but chain 2 only find 10 ASIC (instead of 65 ASIC), and the program shutdown chain 2 automatically. So, it's now working with 2 hashboards (2 x 65 ASIC = 130 ASIC) only. Hashrate is about 48 TH/s. Things I have done: 1. Cleaning the machine inside / outside. 2. Flash and upgrade the control board using SD Card with the latest firmware from Bitmain. (Also tried to flash the firmware from HiveOS, MSKMiner, Asic.to, etc.. undervolt, changing frequency, etc .. but no luck. Finally, back again to Bitmain firmware). 3. Changing the signal data cable from hashboard 1 (chain 0) to hashboard 3 (chain 2), vice versa. 4. Tighten the power cord and signal data cable. But, still the problem occurs. Chain 2 only finds 10 ASIC. So, what is really the problem? Is it coming from the PSU (APW9+) or the Control Board or the 3rd hashboard chip is really broken and need to be repaired? Technical support from Bitmain told me to try with a new PSU. But haven't done that, since no other PSU available here. Have to import from China. Thanks for your help. # Miner Statushttps://freeimage.host/i/5rdkJa# Kernel Log
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) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
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 c0b39280, 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: 203432K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25944K 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 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 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
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12904K (cce67000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 32/18, WL threshold: 4096, image sequence number: 3881267153
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 11A554BB-615C-4F03-94F7-C1BEF37C3831, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 3928/900, WL threshold: 4096, image sequence number: 530904360
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 3E9C38B1-5AEA-4FD6-850C-698DB389147B, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2021-11-23 00:22:02 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2021-11-23 00:22:02 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version = 1
2021-11-23 00:22:02 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab = 1
2021-11-23 00:22:02 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2021-11-23 00:22:02 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun 2 10:31:07 CST 2020 type: Antminer S17+
2021-11-23 00:22:02 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2021-11-23 00:22:02 driver-btm-api.c:2083:show_sn: len:16, 8062148c2b104814
2021-11-23 00:22:02 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2021-11-23 00:22:02 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2021-11-23 00:22:02 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 8062148c2b104814
2021-11-23 00:22:02 fan.c:284:front_fan_power_on: Note: front fan is power on!
2021-11-23 00:22:02 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2021-11-23 00:22:02 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2021-11-23 00:22:02 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2021-11-23 00:22:08 driver-btm-api.c:1239:init_miner_version: miner ID : 8062148c2b104814
2021-11-23 00:22:08 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2021-11-23 00:22:14 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2021-11-23 00:22:14 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2021-11-23 00:22:14 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2021-11-23 00:22:14 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2021-11-23 00:22:14 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2021-11-23 00:22:14 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2021-11-23 00:22:14 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2021-11-23 00:22:14 thread.c:1363:create_read_nonce_reg_thread: create thread
2021-11-23 00:22:20 driver-btm-api.c:1239:init_miner_version: miner ID : 8062148c2b104814
2021-11-23 00:22:20 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2021-11-23 00:22:25 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2021-11-23 00:22:25 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2021-11-23 00:22:25 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2021-11-23 00:22:25 driver-btm-api.c:792:_set_project_type: project:0
2021-11-23 00:22:25 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2021-11-23 00:22:25 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2021-11-23 00:22:25 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2021-11-23 00:22:25 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2021-11-23 00:22:25 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2021-11-23 00:22:25 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2021-11-23 00:22:25 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2021-11-23 00:22:27 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2021-11-23 00:22:28 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-11-23 00:22:30 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2021-11-23 00:22:31 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-11-23 00:22:33 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2021-11-23 00:22:34 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-11-23 00:22:36 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2021-11-23 00:22:36 thread.c:1358:create_pic_heart_beat_thread: create thread
2021-11-23 00:22:36 power_api.c:213:power_init: Power init:
2021-11-23 00:22:36 power_api.c:214:power_init: current_voltage_raw = 0
2021-11-23 00:22:36 power_api.c:215:power_init: highest_voltage_raw = 2100
2021-11-23 00:22:36 power_api.c:216:power_init: working_voltage_raw = 1950
2021-11-23 00:22:36 power_api.c:217:power_init: higher_voltage_raw = 2040
2021-11-23 00:22:36 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2021-11-23 00:22:36 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-11-23 00:22:36 power_api.c:186:power_off: init gpio907
2021-11-23 00:23:08 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2021-11-23 00:23:34 power_api.c:85:check_voltage_multi: retry time: 0
2021-11-23 00:23:35 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.105671
2021-11-23 00:23:36 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.054053
2021-11-23 00:23:37 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.081186
2021-11-23 00:23:37 power_api.c:53:_get_avg_voltage: average_voltage = 21.080304
2021-11-23 00:23:37 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.08, check voltage passed.
2021-11-23 00:23:37 uart.c:72:set_baud: set fpga_baud to 115200
2021-11-23 00:23:49 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2021-11-23 00:24:00 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2021-11-23 00:24:11 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 10 asic, times 0
2021-11-23 00:24:22 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 10 asic, times 1
2021-11-23 00:24:32 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 10 asic, times 2
2021-11-23 00:24:32 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-11-23 00:24:41 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 10 asic, times 3
2021-11-23 00:24:41 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2050
2021-11-23 00:24:41 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2021-11-23 00:24:45 power_api.c:85:check_voltage_multi: retry time: 0
2021-11-23 00:24:47 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.564993
2021-11-23 00:24:48 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.514139
2021-11-23 00:24:49 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.516087
2021-11-23 00:24:49 power_api.c:53:_get_avg_voltage: average_voltage = 20.531740
2021-11-23 00:24:49 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.53, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-11-23 00:24:58 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 10 asic, times 4
2021-11-23 00:24:58 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2000
2021-11-23 00:24:58 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2021-11-23 00:25:02 power_api.c:85:check_voltage_multi: retry time: 0
2021-11-23 00:25:04 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.051480
2021-11-23 00:25:05 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.025707
2021-11-23 00:25:06 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.027026
2021-11-23 00:25:06 power_api.c:53:_get_avg_voltage: average_voltage = 20.034738
2021-11-23 00:25:06 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.03, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-11-23 00:25:15 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 10 asic, times 5
2021-11-23 00:25:15 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
2021-11-23 00:25:15 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2021-11-23 00:25:20 power_api.c:85:check_voltage_multi: retry time: 0
2021-11-23 00:25:22 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.054053
2021-11-23 00:25:23 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.002571
2021-11-23 00:25:24 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.032217
2021-11-23 00:25:24 power_api.c:53:_get_avg_voltage: average_voltage = 21.029614
2021-11-23 00:25:24 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.03, check voltage passed.
2021-11-23 00:25:24 driver-btm-api.c:1193:check_asic_number: Chain 2 only find 10 asic, will power off hash board 2
2021-11-23 00:25:25 driver-btm-api.c:1195:check_asic_number: Chain 2 voltage: an0 = 2.783871, an2 2.770968, an6 2.506452.
2021-11-23 00:25:31 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2021-11-23 00:25:31 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2021-11-23 00:25:32 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2021-11-23 00:25:32 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2021-11-23 00:25:32 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2021-11-23 00:25:32 voltage[0] = 1960
2021-11-23 00:25:32 voltage[1] = 1960
2021-11-23 00:25:32 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1960
2021-11-23 00:25:34 temperature.c:340:calibrate_temp_sensor_one_chain: chain 0 temp sensor NCT218
2021-11-23 00:25:35 temperature.c:340:calibrate_temp_sensor_one_chain: chain 1 temp sensor NCT218
2021-11-23 00:25:35 uart.c:72:set_baud: set fpga_baud to 12000000
2021-11-23 00:25:36 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 32
2021-11-23 00:25:36 thread.c:1378:create_check_miner_status_thread: create thread
2021-11-23 00:25:36 thread.c:1368:create_show_miner_status_thread: create thread
2021-11-23 00:25:36 thread.c:1348:create_temperature_monitor_thread: create thread
2021-11-23 00:25:36 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 32 dec_freq_index=0
2021-11-23 00:25:36 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2021-11-23 00:25:36 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2021-11-23 00:25:36 thread.c:1338:create_asic_status_monitor_thread: create thread
2021-11-23 00:25:36 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 530, is_higher_voltage = true
2021-11-23 00:25:36 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2021-11-23 00:25:37 power_api.c:85:check_voltage_multi: retry time: 0
2021-11-23 00:25:39 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.931788
2021-11-23 00:25:40 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.880463
2021-11-23 00:25:40 power_api.c:53:_get_avg_voltage: average_voltage = 20.906126
2021-11-23 00:25:40 power_api.c:71:check_voltage: target_vol = 20.90, actural_vol = 20.91, check voltage passed.
2021-11-23 00:28:05 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2080, step by step.
2021-11-23 00:28:07 power_api.c:85:check_voltage_multi: retry time: 0
2021-11-23 00:28:09 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.785070
2021-11-23 00:28:10 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.733934
2021-11-23 00:28:10 power_api.c:53:_get_avg_voltage: average_voltage = 20.759502
2021-11-23 00:28:10 power_api.c:71:check_voltage: target_vol = 20.80, actural_vol = 20.76, check voltage passed.
2021-11-23 00:28:51 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2060, step by step.
2021-11-23 00:28:52 power_api.c:85:check_voltage_multi: retry time: 0
2021-11-23 00:28:54 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.589446
2021-11-23 00:28:55 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.512194
2021-11-23 00:28:55 power_api.c:53:_get_avg_voltage: average_voltage = 20.550820
2021-11-23 00:28:55 power_api.c:71:check_voltage: target_vol = 20.60, actural_vol = 20.55, check voltage passed.
2021-11-23 00:30:56 frequency.c:1152:inc_freq_with_fixed_step: chain = 0, freq_start = 530, freq_end = 540, freq_step = 5, is_higher_voltage = true
2021-11-23 00:31:00 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2030, step by step.
2021-11-23 00:31:01 power_api.c:85:check_voltage_multi: retry time: 0
2021-11-23 00:31:02 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.296010
2021-11-23 00:31:04 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.245502
2021-11-23 00:31:04 power_api.c:53:_get_avg_voltage: average_voltage = 20.270756
2021-11-23 00:31:04 power_api.c:71:check_voltage: target_vol = 20.30, actural_vol = 20.27, check voltage passed.
2021-11-23 00:31:04 frequency.c:1181:inc_asic_diff_freq_by_steps: chain = 0, start = 540, freq_step = 5
2021-11-23 00:31:08 frequency.c:1181:inc_asic_diff_freq_by_steps: chain = 1, start = 530, freq_step = 5
2021-11-23 00:31:12 driver-btm-api.c:765:set_timeout: freq = 570, percent = 90, hcn = 44236, timeout = 77
2021-11-23 00:31:12 power_api.c:310:set_to_working_voltage_by_steps: Set to voltage raw 1960, step by step.
2021-11-23 00:31:16 power_api.c:85:check_voltage_multi: retry time: 0
2021-11-23 00:31:17 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 19.611325
2021-11-23 00:31:18 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 19.561697
2021-11-23 00:31:18 power_api.c:53:_get_avg_voltage: average_voltage = 19.586511
2021-11-23 00:31:18 power_api.c:71:check_voltage: target_vol = 19.60, actural_vol = 19.59, check voltage passed.
2021-11-23 00:31:18 thread.c:1373:create_check_system_status_thread: create thread
2021-11-23 00:31:18 driver-btm-api.c:2618:bitmain_soc_init: Init done!
2021-11-23 00:31:18 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2021-11-23 00:31:24 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2021-11-23 00:31:25 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 47612
2021-11-23 00:31:25 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 46000
2021-11-23 00:31:29 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2021-11-23 00:31:29 driver-btm-api.c:1644:dhash_chip_send_job: stime.tv_sec 1637627489, block_ntime 1637627472
2021-11-23 01:01:29 thread.c:259:calc_hashrate_avg: avg rate is 48347.97 in 30 mins
2021-11-23 01:01:29 temperature.c:516:temp_statistics_show: pcb temp 50~64 chip temp 68~79
2021-11-23 01:31:31 thread.c:259:calc_hashrate_avg: avg rate is 48750.92 in 30 mins
2021-11-23 01:31:31 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 69~80
2021-11-23 02:01:32 thread.c:259:calc_hashrate_avg: avg rate is 48664.07 in 30 mins
2021-11-23 02:01:32 temperature.c:516:temp_statistics_show: pcb temp 50~63 chip temp 68~79
2021-11-23 02:31:34 thread.c:259:calc_hashrate_avg: avg rate is 48460.93 in 30 mins
2021-11-23 02:31:34 temperature.c:516:temp_statistics_show: pcb temp 50~63 chip temp 69~79
2021-11-23 03:01:35 thread.c:259:calc_hashrate_avg: avg rate is 48554.34 in 30 mins
2021-11-23 03:01:35 temperature.c:516:temp_statistics_show: pcb temp 50~63 chip temp 68~80
2021-11-23 03:31:36 thread.c:259:calc_hashrate_avg: avg rate is 48312.00 in 30 mins
2021-11-23 03:31:36 temperature.c:516:temp_statistics_show: pcb temp 50~63 chip temp 69~80
2021-11-23 04:01:38 thread.c:259:calc_hashrate_avg: avg rate is 48547.62 in 30 mins
2021-11-23 04:01:38 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 68~79
2021-11-23 04:31:39 thread.c:259:calc_hashrate_avg: avg rate is 48415.12 in 30 mins
2021-11-23 04:31:39 temperature.c:516:temp_statistics_show: pcb temp 51~63 chip temp 69~79
2021-11-23 05:01:40 thread.c:259:calc_hashrate_avg: avg rate is 48679.49 in 30 mins
2021-11-23 05:01:40 temperature.c:516:temp_statistics_show: pcb temp 51~63 chip temp 69~79
2021-11-23 05:31:42 thread.c:259:calc_hashrate_avg: avg rate is 48292.43 in 30 mins
2021-11-23 05:31:42 temperature.c:516:temp_statistics_show: pcb temp 50~63 chip temp 69~80
2021-11-23 06:01:43 thread.c:259:calc_hashrate_avg: avg rate is 48291.87 in 30 mins
2021-11-23 06:01:43 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 69~79
2021-11-23 06:31:45 thread.c:259:calc_hashrate_avg: avg rate is 48290.60 in 30 mins
2021-11-23 06:31:45 temperature.c:516:temp_statistics_show: pcb temp 50~64 chip temp 69~79
2021-11-23 07:01:46 thread.c:259:calc_hashrate_avg: avg rate is 48493.22 in 30 mins
2021-11-23 07:01:46 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 69~80
2021-11-23 07:31:47 thread.c:259:calc_hashrate_avg: avg rate is 48293.65 in 30 mins
2021-11-23 07:31:47 temperature.c:516:temp_statistics_show: pcb temp 51~63 chip temp 69~79
2021-11-23 08:01:49 thread.c:259:calc_hashrate_avg: avg rate is 48592.19 in 30 mins
2021-11-23 08:01:49 temperature.c:516:temp_statistics_show: pcb temp 51~63 chip temp 69~80
2021-11-23 08:31:50 thread.c:259:calc_hashrate_avg: avg rate is 48544.48 in 30 mins
2021-11-23 08:31:50 temperature.c:516:temp_statistics_show: pcb temp 50~64 chip temp 69~79
2021-11-23 09:01:52 thread.c:259:calc_hashrate_avg: avg rate is 48395.00 in 30 mins
2021-11-23 09:01:52 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 69~79
2021-11-23 09:31:53 thread.c:259:calc_hashrate_avg: avg rate is 48224.75 in 30 mins
2021-11-23 09:31:53 temperature.c:516:temp_statistics_show: pcb temp 51~63 chip temp 69~80
2021-11-23 10:01:55 thread.c:259:calc_hashrate_avg: avg rate is 48255.80 in 30 mins
2021-11-23 10:01:55 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 69~79
2021-11-23 10:31:56 thread.c:259:calc_hashrate_avg: avg rate is 48852.26 in 30 mins
2021-11-23 10:31:56 temperature.c:516:temp_statistics_show: pcb temp 50~64 chip temp 69~80
2021-11-23 11:01:57 thread.c:259:calc_hashrate_avg: avg rate is 48493.22 in 30 mins
2021-11-23 11:01:57 temperature.c:516:temp_statistics_show: pcb temp 50~63 chip temp 69~80
2021-11-23 11:31:59 thread.c:259:calc_hashrate_avg: avg rate is 48460.32 in 30 mins
2021-11-23 11:31:59 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 69~80
2021-11-23 11:53:42 driver-btm-api.c:1496:dhash_chip_send_job: Version num 1.
2021-11-23 11:53:54 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2021-11-23 12:02:00 thread.c:259:calc_hashrate_avg: avg rate is 48395.60 in 30 mins
2021-11-23 12:02:00 temperature.c:516:temp_statistics_show: pcb temp 50~63 chip temp 70~79
2021-11-23 12:32:02 thread.c:259:calc_hashrate_avg: avg rate is 48431.01 in 30 mins
2021-11-23 12:32:02 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 69~79
2021-11-23 13:02:03 thread.c:259:calc_hashrate_avg: avg rate is 48434.68 in 30 mins
2021-11-23 13:02:03 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 68~79
2021-11-23 13:32:04 thread.c:259:calc_hashrate_avg: avg rate is 47981.30 in 30 mins
2021-11-23 13:32:04 temperature.c:516:temp_statistics_show: pcb temp 50~63 chip temp 69~79
2021-11-23 14:02:06 thread.c:259:calc_hashrate_avg: avg rate is 48289.99 in 30 mins
2021-11-23 14:02:06 temperature.c:516:temp_statistics_show: pcb temp 50~64 chip temp 68~79
2021-11-23 14:32:07 thread.c:259:calc_hashrate_avg: avg rate is 48419.39 in 30 mins
2021-11-23 14:32:07 temperature.c:516:temp_statistics_show: pcb temp 50~64 chip temp 69~79
2021-11-23 15:02:08 thread.c:259:calc_hashrate_avg: avg rate is 48471.31 in 30 mins
2021-11-23 15:02:08 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 69~79
2021-11-23 15:32:10 thread.c:259:calc_hashrate_avg: avg rate is 48502.44 in 30 mins
2021-11-23 15:32:10 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 69~80
2021-11-23 16:02:11 thread.c:259:calc_hashrate_avg: avg rate is 48055.13 in 30 mins
2021-11-23 16:02:11 temperature.c:516:temp_statistics_show: pcb temp 51~63 chip temp 69~80
2021-11-23 16:32:13 thread.c:259:calc_hashrate_avg: avg rate is 48561.66 in 30 mins
2021-11-23 16:32:13 temperature.c:516:temp_statistics_show: pcb temp 52~64 chip temp 69~80
2021-11-23 16:42:26 driver-btm-api.c:222:set_miner_status: WARN_NET_LOST
2021-11-23 16:43:50 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2021-11-23 17:02:14 thread.c:259:calc_hashrate_avg: avg rate is 48344.95 in 30 mins
2021-11-23 17:02:14 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 70~79
2021-11-23 17:32:16 thread.c:259:calc_hashrate_avg: avg rate is 48318.68 in 30 mins
2021-11-23 17:32:16 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 69~80
2021-11-23 18:02:17 thread.c:259:calc_hashrate_avg: avg rate is 48580.48 in 30 mins
2021-11-23 18:02:17 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 69~80
2021-11-23 18:32:18 thread.c:259:calc_hashrate_avg: avg rate is 48392.55 in 30 mins
2021-11-23 18:32:18 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 69~80
2021-11-23 19:02:20 thread.c:259:calc_hashrate_avg: avg rate is 48576.31 in 30 mins
2021-11-23 19:02:20 temperature.c:516:temp_statistics_show: pcb temp 51~63 chip temp 69~79
2021-11-23 19:32:21 thread.c:259:calc_hashrate_avg: avg rate is 48720.20 in 30 mins
2021-11-23 19:32:21 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 69~80
2021-11-23 20:02:23 thread.c:259:calc_hashrate_avg: avg rate is 48443.84 in 30 mins
2021-11-23 20:02:23 temperature.c:516:temp_statistics_show: pcb temp 51~63 chip temp 69~79
2021-11-23 20:32:24 thread.c:259:calc_hashrate_avg: avg rate is 48216.82 in 30 mins
2021-11-23 20:32:24 temperature.c:516:temp_statistics_show: pcb temp 51~64 chip temp 69~79
2021-11-23 21:02:26 thread.c:259:calc_hashrate_avg: avg rate is 48402.32 in 30 mins
2021-11-23 21:02:26 temperature.c:516:temp_statistics_show: pcb temp 50~63 chip temp 68~78
2021-11-23 21:32:27 thread.c:259:calc_hashrate_avg: avg rate is 48520.15 in 30 mins
2021-11-23 21:32:27 temperature.c:516:temp_statistics_show: pcb temp 50~64 chip temp 69~80
2021-11-23 22:02:28 thread.c:259:calc_hashrate_avg: avg rate is 48304.07 in 30 mins
2021-11-23 22:02:28 temperature.c:516:temp_statistics_show: pcb temp 50~64 chip temp 69~79
2021-11-23 22:32:30 thread.c:259:calc_hashrate_avg: avg rate is 48730.77 in 30 mins
2021-11-23 22:32:30 temperature.c:516:temp_statistics_show: pcb temp 50~63 chip temp 69~79
2021-11-23 23:02:31 thread.c:259:calc_hashrate_avg: avg rate is 48845.90 in 30 mins
2021-11-23 23:02:31 temperature.c:516:temp_statistics_show: pcb temp 50~63 chip temp 69~80
2021-11-23 23:32:33 thread.c:259:calc_hashrate_avg: avg rate is 48470.09 in 30 mins
2021-11-23 23:32:33 temperature.c:516:temp_statistics_show: pcb temp 50~64 chip temp 69~79
2021-11-24 00:02:34 thread.c:259:calc_hashrate_avg: avg rate is 48326.04 in 30 mins
2021-11-24 00:02:34 temperature.c:516:temp_statistics_show: pcb temp 50~64 chip temp 68~80
2021-11-24 00:32:35 thread.c:259:calc_hashrate_avg: avg rate is 48496.34 in 30 mins
2021-11-24 00:32:35 temperature.c:516:temp_statistics_show: pcb temp 50~63 chip temp 69~79
2021-11-24 01:02:37 thread.c:259:calc_hashrate_avg: avg rate is 48625.76 in 30 mins
2021-11-24 01:02:37 temperature.c:516:temp_statistics_show: pcb temp 50~64 chip temp 69~79
Title: Re: S17+ (70 TH/s) - Hashboard 3 Only Find 10 ASIC
Post by: Perverza on November 24, 2021, 07:21:55 AM
Hello,
i think you have bad soldering or bad chip on the hashboard.
Chip 10 or 11 need to be repair.
Where are you from ?
Do you have technical skill ? With hot air soldering ?
M.
Title: Re: S17+ (70 TH/s) - Hashboard 3 Only Find 10 ASIC
Post by: franx47 on November 24, 2021, 09:51:16 AM
Hello,
i think you have bad soldering or bad chip on the hashboard.
Chip 10 or 11 need to be repair.
Where are you from ?
Do you have technical skill ? With hot air soldering ?
M.
Hi, thanks for your info. So the 3rd hashboard chip is really broken. I thought it was a PSU problem. Unfortunately, I don't have any skill on electronic thing or soldering. I'm from Indonesia. Frans
Title: Re: S17+ (70 TH/s) - Hashboard 3 Only Find 10 ASIC
Post by: BitMaxz on November 24, 2021, 03:27:48 PM
You almost did all basic thing but have you tried to run only one hashboard I mean keep the chain 2 running and disconnect the other two hashboard and test if it still detects only 10 ASICs. Unfortunately, I don't have any skill on electronic thing or soldering.
If you don't have skills your best option is to bring them to the professional technician about ASIC hashboard ZeusBTC is one of the known who can repair these boards and they have lots of repair centers where you can send them but the problem is they don't have a center in Indonesia. But if you still want you can check the list of their repair centers here https://www.zeusbtc.com/ASIC-Miner-Repair/ Another option is to buy a replacement hashboard you can directly buy it on Bitmain or buy on ZeusBTC.
Title: Re: S17+ (70 TH/s) - Hashboard 3 Only Find 10 ASIC
Post by: franx47 on November 25, 2021, 11:57:16 PM
You almost did all basic thing but have you tried to run only one hashboard I mean keep the chain 2 running and disconnect the other two hashboard and test if it still detects only 10 ASICs. Unfortunately, I don't have any skill on electronic thing or soldering.
If you don't have skills your best option is to bring them to the professional technician about ASIC hashboard ZeusBTC is one of the known who can repair these boards and they have lots of repair centers where you can send them but the problem is they don't have a center in Indonesia. But if you still want you can check the list of their repair centers here https://www.zeusbtc.com/ASIC-Miner-Repair/ Another option is to buy a replacement hashboard you can directly buy it on Bitmain or buy on ZeusBTC. Tried to change the signal data cable (18 PINS - 2x9) with a new cable for the chain 3 and run it with single hashboard (only chain 3), but still no result. The chain 3 only find 10 ASIC (instead of 65 ASIC). The chain is shutdown automatically by the program. # Here's the Kernel Log (for chain 3 only):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) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
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 c0b39280, 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: 203432K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25944K 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 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 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
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12904K (cce67000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 32/18, WL threshold: 4096, image sequence number: 3881267153
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 11A554BB-615C-4F03-94F7-C1BEF37C3831, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 3928/903, WL threshold: 4096, image sequence number: 530904360
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 3E9C38B1-5AEA-4FD6-850C-698DB389147B, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
2021-11-25 08:30:52 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2021-11-25 08:30:52 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version = 1
2021-11-25 08:30:52 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab = 1
2021-11-25 08:30:52 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2021-11-25 08:30:52 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun 2 10:31:07 CST 2020 type: Antminer S17+
2021-11-25 08:30:52 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2021-11-25 08:30:52 driver-btm-api.c:2083:show_sn: len:16, 8062148c2b104814
2021-11-25 08:30:52 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2021-11-25 08:30:52 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2021-11-25 08:30:52 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 8062148c2b104814
2021-11-25 08:30:52 fan.c:284:front_fan_power_on: Note: front fan is power on!
2021-11-25 08:30:52 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2021-11-25 08:30:52 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2021-11-25 08:30:52 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2021-11-25 08:30:58 driver-btm-api.c:1239:init_miner_version: miner ID : 8062148c2b104814
2021-11-25 08:30:58 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2021-11-25 08:31:00 driver-btm-api.c:837:get_product_id: product_id[3] = 0
2021-11-25 08:31:00 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2021-11-25 08:31:00 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2021-11-25 08:31:00 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2021-11-25 08:31:00 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2021-11-25 08:31:00 thread.c:1363:create_read_nonce_reg_thread: create thread
2021-11-25 08:31:06 driver-btm-api.c:1239:init_miner_version: miner ID : 8062148c2b104814
2021-11-25 08:31:06 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2021-11-25 08:31:08 driver-btm-api.c:837:get_product_id: product_id[3] = 0
2021-11-25 08:31:08 driver-btm-api.c:792:_set_project_type: project:0
2021-11-25 08:31:08 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2021-11-25 08:31:08 driver-btm-api.c:824:dump_pcb_bom_version: Chain [3] PCB Version: 0x0100
2021-11-25 08:31:08 driver-btm-api.c:825:dump_pcb_bom_version: Chain [3] BOM Version: 0x0100
2021-11-25 08:31:14 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2021-11-25 08:31:15 board.c:36:jump_and_app_check_restore_pic: chain[3] PIC jump to app
2021-11-25 08:31:17 board.c:40:jump_and_app_check_restore_pic: Check chain[3] PIC fw version=0x88
2021-11-25 08:31:17 thread.c:1358:create_pic_heart_beat_thread: create thread
2021-11-25 08:31:17 power_api.c:213:power_init: Power init:
2021-11-25 08:31:17 power_api.c:214:power_init: current_voltage_raw = 0
2021-11-25 08:31:17 power_api.c:215:power_init: highest_voltage_raw = 2100
2021-11-25 08:31:17 power_api.c:216:power_init: working_voltage_raw = 1950
2021-11-25 08:31:17 power_api.c:217:power_init: higher_voltage_raw = 2040
2021-11-25 08:31:17 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2021-11-25 08:31:17 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-11-25 08:31:17 power_api.c:186:power_off: init gpio907
2021-11-25 08:31:49 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2021-11-25 08:32:15 power_api.c:85:check_voltage_multi: retry time: 0
2021-11-25 08:32:17 power_api.c:40:_get_avg_voltage: chain = 3, voltage = 21.081186
2021-11-25 08:32:17 power_api.c:53:_get_avg_voltage: average_voltage = 21.081186
2021-11-25 08:32:17 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.08, check voltage passed.
2021-11-25 08:32:17 uart.c:72:set_baud: set fpga_baud to 115200
2021-11-25 08:32:28 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[3]: find 10 asic, times 0
2021-11-25 08:32:39 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[3]: find 10 asic, times 1
2021-11-25 08:32:49 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[3]: find 10 asic, times 2
2021-11-25 08:32:49 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
chain 3, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-11-25 08:32:58 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[3]: find 10 asic, times 3
2021-11-25 08:32:58 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2050
2021-11-25 08:32:58 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2021-11-25 08:33:02 power_api.c:85:check_voltage_multi: retry time: 0
2021-11-25 08:33:03 power_api.c:40:_get_avg_voltage: chain = 3, voltage = 20.540540
2021-11-25 08:33:03 power_api.c:53:_get_avg_voltage: average_voltage = 20.540540
2021-11-25 08:33:03 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.54, check voltage passed.
chain 3, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-11-25 08:33:12 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[3]: find 10 asic, times 4
2021-11-25 08:33:12 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2000
2021-11-25 08:33:12 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2021-11-25 08:33:15 power_api.c:85:check_voltage_multi: retry time: 0
2021-11-25 08:33:16 power_api.c:40:_get_avg_voltage: chain = 3, voltage = 20.027026
2021-11-25 08:33:16 power_api.c:53:_get_avg_voltage: average_voltage = 20.027026
2021-11-25 08:33:16 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.03, check voltage passed.
chain 3, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-11-25 08:33:25 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[3]: find 10 asic, times 5
2021-11-25 08:33:25 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
2021-11-25 08:33:25 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2021-11-25 08:33:31 power_api.c:85:check_voltage_multi: retry time: 0
2021-11-25 08:33:32 power_api.c:40:_get_avg_voltage: chain = 3, voltage = 21.029600
2021-11-25 08:33:32 power_api.c:53:_get_avg_voltage: average_voltage = 21.029600
2021-11-25 08:33:32 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.03, check voltage passed.
2021-11-25 08:33:32 driver-btm-api.c:1193:check_asic_number: Chain 3 only find 10 asic, will power off hash board 3
2021-11-25 08:33:33 driver-btm-api.c:1195:check_asic_number: Chain 3 voltage: an0 = 2.787097, an2 2.774194, an6 2.506452.
2021-11-25 08:33:34 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2021-11-25 08:33:34 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2021-11-25 08:33:34 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2021-11-25 08:33:34 driver-btm-api.c:141:killall_hashboard: ****power off hashboard****
Thanks for the info about ZeusBTC, I have contacted them. But they said that they don't have new hashboard for S17+ (70 TH/s) available. They might be can repair hashboard. But, I think I will just follow procedure from Bitmain technical support on how to repair 1 hashboard only, without sending the whole machine to China (if it's possible), since I read that hashboard produced started from 17 series has been programmed with unique code, so it has to match with the other hashboards in a single machine. Except, one can reprogram the hashboard unique code using code editor to successfully mix with other hashboard. Not sure enough, but I think the factory has the complete tools to solve this technical issue when doing check / reparation.
Title: Re: S17+ (70 TH/s) - Hashboard 3 Only Find 10 ASIC
Post by: BitMaxz on November 26, 2021, 04:04:39 PM
Actually, Bitmain doesn't have a guide if it's related to a hardware issue they will always recommend you to send the hashboard back to them for warranty repair.
ZeusBTC centers are not only in China they have many centers in different countries you just need to read the link that I posted above and choose which country is near you.
Or you can troubleshoot that hashboard there is a guide from ZeusBTC that you can follow on how to check each ASIC chip through test points.
You can find it here https://www.zeusbtc.com/articles/information/170-antminer-s17-manual-download
About software where you can ignore the other ASIC chip well you can try Braiins OS I don't think you can able to disable those affected chips but you can try to ask them on BraiinsOS official thread here https://bitcointalk.org/index.php?topic=5036844
Title: Re: S17+ (70 TH/s) - Hashboard 3 Only Find 10 ASIC
Post by: franx47 on February 21, 2022, 04:30:33 AM
UPDATE !! I just want to inform you that my machine is now running on > 70 TH/s hashrate. But before that, it was a long story that the point is I did return the hashboard for repair to the Bitmain HK repair center. It was done twice and spent so much money on it for the freight cost. Until I gave up returning the second replacement hashboard, because it gave the same error. I just let the machine run at 48 TH/s for more than a month, since I last returned. I guess the certain chip had broken within the replacement hashboard, or the PSU issue. On Wednesday 16 February 2022, it was raining hard in the afternoon. Suddenly, a very loud lightning struck in the sky, made my computer monitor blips and the mining machine got an error in the Kernel Log. (But, the electricity was not blackout). I was really worried at that time, and did a restart on the machine as quick as possible. After restart, the 3 hashboards were all back to normal again. Especially the replacement hashboard (chain 2). At first, I was not believe the replacement hashboard can run again after more than a month inactive. But after more than 24 hours (several days, till now) run without error at all, I can assure the replacement hashboard is now working good. I can't explain it technically, but believe it or not, the machine now runs at 70 TH/s (or up), and no problem at all till this time. Hope it can run normally for a very long time. I'm happy now !! Alhamdulillahi robbil 'aalamiin (All Glory be to Allah, Lord of the worlds). Thank you guys for all your best support. https://postimg.cc/68ZNhFYs
Title: Re: S17+ (70 TH/s) - Hashboard 3 Only Find 10 ASIC
Post by: mikeywith on February 21, 2022, 11:01:09 PM
On Wednesday 16 February 2022, it was raining hard in the afternoon. Suddenly, a very loud lightning struck in the sky,
Merit given for reporting back after the problem was solved. The electromagnetic disturbance caused by that afternoon lightning strike probably did have an effect on your miner, it could have burned it but it seems to have fixed your issue, my guess is that your PSU caused the problem and not the hashboard itself, so just in case the problem comes back, check the PSU.
|