S9 - Hashboard red light on but don't appear

[508std]

Hi there.

I have some spare hashboard from different S9 miner that have red light on when I plugged in, but nothing appear in Miner Statut section. I'm 100% sure that my mother board is working fine, is there a way to bring them back to life ?

I already tried to clean them with isopropyl alcohol, tried to install latest Bitmain software on mother board. I read on internet that it's possible to flash a software inside the hashboard with some tools, is it the only solution remaining ?

I tried to understand logs, but it's like Chinese for me :s Does someone can help ?

Thanks ++

Code:

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.0-xilinx-g16220c3 (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #83 SMP PREEMPT Thu Jul 12 11:42:53 CST 2018
[    0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Xilinx Zynq
[    0.000000] cma: CMA: reserved 128 MiB at 16800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 126976
[    0.000000] free_area_init_node: node 0, pgdat c074ac00, node_mem_map debd8000
[    0.000000]   Normal zone: 992 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 126976 pages, LIFO batch:31
[    0.000000] PERCPU: Embedded 8 pages/cpu @debc1000 s9088 r8192 d15488 u32768
[    0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 125984
[    0.000000] Kernel command line: noinitrd mem=496M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 364316K/507904K available (5057K kernel code, 284K rwdata, 1928K rodata, 204K init, 258K bss, 143588K reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xdf800000 - 0xff000000   ( 504 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xdf000000   ( 496 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06da8ac   (6987 kB)
[    0.000000]       .init : 0xc06db000 - 0xc070e380   ( 205 kB)
[    0.000000]       .data : 0xc0710000 - 0xc0757138   ( 285 kB)
[    0.000000]        .bss : 0xc0757144 - 0xc0797bfc   ( 259 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] 	Dump stacks of tasks blocking RCU-preempt GP.
[    0.000000] 	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] ps7-slcr mapped to df802000
[    0.000000] zynq_clock_init: clkc starts at df802100
[    0.000000] Zynq clock init
[    0.000014] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[    0.000288] ps7-ttc #0 at df804000, irq=43
[    0.000587] Console: colour dummy device 80x30
[    0.000616] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328)
[    0.040194] pid_max: default: 32768 minimum: 301
[    0.040401] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.040421] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.042589] CPU: Testing write buffer coherency: ok
[    0.042902] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.042958] Setting up static identity map for 0x4cb118 - 0x4cb170
[    0.043177] L310 cache controller enabled
[    0.043197] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[    0.120983] CPU1: Booted secondary processor
[    0.210215] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.210346] Brought up 2 CPUs
[    0.210365] SMP: Total of 2 processors activated.
[    0.210373] CPU: All CPU(s) started in SVC mode.
[    0.211029] devtmpfs: initialized
[    0.213458] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.214646] regulator-dummy: no parameters
[    0.221992] NET: Registered protocol family 16
[    0.224206] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.226470] cpuidle: using governor ladder
[    0.226483] cpuidle: using governor menu
[    0.233825] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.235330] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.235343] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.235453] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000
[    0.257248] bio: create slab <bio-0> at 0
[    0.258623] vgaarb: loaded
[    0.259323] SCSI subsystem initialized
[    0.260243] usbcore: registered new interface driver usbfs
[    0.260900] usbcore: registered new interface driver hub
[    0.261180] usbcore: registered new device driver usb
[    0.261694] media: Linux media interface: v0.10
[    0.261856] Linux video capture interface: v2.00
[    0.262094] pps_core: LinuxPPS API ver. 1 registered
[    0.262106] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.262226] PTP clock support registered
[    0.262587] EDAC MC: Ver: 3.0.0
[    0.263778] Advanced Linux Sound Architecture Driver Initialized.
[    0.266511] DMA-API: preallocated 4096 debug entries
[    0.266526] DMA-API: debugging enabled by kernel config
[    0.266591] Switched to clocksource arm_global_timer
[    0.286534] NET: Registered protocol family 2
[    0.287476] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.287534] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.287619] TCP: Hash tables configured (established 4096 bind 4096)
[    0.287663] TCP: reno registered
[    0.287680] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.287712] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.287948] NET: Registered protocol family 1
[    0.288292] RPC: Registered named UNIX socket transport module.
[    0.288304] RPC: Registered udp transport module.
[    0.288312] RPC: Registered tcp transport module.
[    0.288321] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.288333] PCI: CLS 0 bytes, default 64
[    0.288757] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.290755] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.292798] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.292988] msgmni has been set to 967
[    0.293738] io scheduler noop registered
[    0.293752] io scheduler deadline registered
[    0.293797] io scheduler cfq registered (default)
[    0.301861] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.301880] dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.423947] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    0.991644] console [ttyPS0] enabled
[    0.995899] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000
[    1.003537] [drm] Initialized drm 1.1.0 20060810
[    1.020639] brd: module loaded
[    1.030006] loop: module loaded
[    1.039397] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.045147] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.053120] libphy: XEMACPS mii bus: probed
[    1.057670] ------------- phy_id = 0x3625e62
[    1.062395] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.071154] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.077998] ehci-pci: EHCI PCI platform driver
[    1.085212] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[    1.092049] usbcore: registered new interface driver usb-storage
[    1.098912] mousedev: PS/2 mouse device common for all mice
[    1.104984] i2c /dev entries driver
[    1.111919] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[    1.117438] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.123299] Xilinx Zynq CpuIdle Driver started
[    1.128203] sdhci: Secure Digital Host Controller Interface driver
[    1.134299] sdhci: Copyright(c) Pierre Ossman
[    1.138665] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.144436] mmc0: no vqmmc regulator found
[    1.148543] mmc0: no vmmc regulator found
[    1.186612] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.195296] usbcore: registered new interface driver usbhid
[    1.200808] usbhid: USB HID core driver
[    1.205506] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.211808] nand: Micron MT29F2G08ABAEAWP
[    1.215773] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.221713] Bad block table found at page 131008, version 0x01
[    1.227942] Bad block table found at page 130944, version 0x01
[    1.233990] 3 ofpart partitions found on MTD device pl353-nand
[    1.239772] Creating 3 MTD partitions on "pl353-nand":
[    1.244868] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.252901] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.260215] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[    1.270932] TCP: cubic registered
[    1.274164] NET: Registered protocol family 17
[    1.278857] Registering SWP/SWPB emulation handler
[    1.284754] regulator-dummy: disabling
[    1.289066] UBI: attaching mtd1 to ubi0
[    1.814989] UBI: scanning is finished
[    1.826645] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[    1.833702] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.840502] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.847178] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.854013] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[    1.860022] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.867139] UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 1113221046
[    1.876147] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[    1.885373] UBI: background thread "ubi_bgt0d" started, PID 1084
[    1.891364] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.901495] ALSA device list:
[    1.904381]   No soundcards found.
[    1.909621] UBIFS: background thread "ubifs_bgt0_0" started, PID 1086
[    1.965216] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    1.971168] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    1.980283] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    1.990168] UBIFS: reserved for root: 0 bytes (0 KiB)
[    1.995192] UBIFS: media format: w4/r0 (latest is w4/r0), UUID E8A4479F-B15D-4C7A-964D-0F246E2BB6ED, small LPT model
[    2.006735] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    2.013906] devtmpfs: mounted
[    2.017068] Freeing unused kernel memory: 204K (c06db000 - c070e000)
[    2.849734] random: dd urandom read with 1 bits of entropy available
[    3.236635] 
[    3.236635] bcm54xx_config_init
[    4.306648] 
[    4.306648] bcm54xx_config_init
[    8.307464] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[    8.313567] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[   23.655531] In axi fpga driver!
[   23.658626] request_mem_region OK!
[   23.661992] AXI fpga dev virtual address is 0xdf9fe000
[   23.667122] *base_vir_addr = 0xc51e
[   23.681547] In fpga mem driver!
[   23.684869] request_mem_region OK!
[   23.688486] fpga mem virtual address is 0xe2000000
[   24.486623] 
[   24.486623] bcm54xx_config_init
[   25.586640] 
[   25.586640] bcm54xx_config_init
[   29.587444] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[   29.593549] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
main.c:13992: log_level = 4
main.c:14019: This is XILINX board. Totalram:       507486208
main.c:14031: Detect 512MB control board of XILINX
driver-bitmain.c:1776: mmap axi_fpga_addr = 0xb6f33000
driver-bitmain.c:1781: axi_fpga_addr data = 0xc51e
driver-bitmain.c:1797: mmap fpga_mem_addr = 0xb5d2c000
driver-bitmain.c:994: forceFreq=-1 forceFlag=0
driver-bitmain.c:1696: min work minertest[0]:912


main.c:8570: DETECT HW version=0000c51e
main.c:14064: miner ID : 8052a5292f90481c
main.c:14089: Miner Type = S9
main.c:14101: AsicType = 1387
main.c:14104: real AsicNum = 63
main.c:14197: use critical mode to search freq...
driver-bitmain.c:1876: get PLUG ON=0x000000e0
driver-bitmain.c:1946: Find hashboard on Chain[5]
driver-bitmain.c:1946: Find hashboard on Chain[6]
driver-bitmain.c:1946: Find hashboard on Chain[7]
main.c:2282: Check chain[5] PIC fw version=0x03
main.c:2282: Check chain[6] PIC fw version=0x03
main.c:2282: Check chain[7] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[5] has freq in PIC and will jump over...
main.c:9103: Chain[5] has core num in PIC
main.c:9113: Chain[5] ASIC[5] has core num=8
main.c:9113: Chain[5] ASIC[7] has core num=2
main.c:9113: Chain[5] ASIC[16] has core num=5
main.c:9113: Chain[5] ASIC[19] has core num=1
main.c:9113: Chain[5] ASIC[23] has core num=1
main.c:9113: Chain[5] ASIC[29] has core num=15
main.c:9113: Chain[5] ASIC[55] has core num=1
main.c:9113: Chain[5] ASIC[59] has core num=15
main.c:9113: Chain[5] ASIC[60] has core num=15
main.c:2282: Check chain[5] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[6] has freq in PIC and will jump over...
main.c:9103: Chain[6] has core num in PIC
main.c:9113: Chain[6] ASIC[17] has core num=11
main.c:9113: Chain[6] ASIC[32] has core num=1
main.c:9113: Chain[6] ASIC[58] has core num=1
main.c:2282: Check chain[6] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[7] has freq in PIC and will jump over...
main.c:9103: Chain[7] has core num in PIC
main.c:9113: Chain[7] ASIC[40] has core num=1
main.c:9113: Chain[7] ASIC[46] has core num=1
main.c:2282: Check chain[7] PIC fw version=0x03
main.c:9183: get PIC voltage=6 on chain[5], value=940
main.c:9183: get PIC voltage=6 on chain[6], value=940
main.c:9183: get PIC voltage=6 on chain[7], value=940
main.c:9349: chain[5] temp offset record: 62,0,0,0,0,0,41,28
main.c:9366: chain[5] temp chip I2C addr=0x9a
main.c:9349: chain[6] temp offset record: 62,0,0,0,0,0,41,28
main.c:9366: chain[6] temp chip I2C addr=0x9a
main.c:9349: chain[7] temp offset record: 62,0,0,0,0,0,41,28
main.c:9366: chain[7] temp chip I2C addr=0x9a
main.c:13956: total_exist_chain_num = 3
main.c:9562: CRC error counter=0
main.c:9577: set command mode to VIL
main.c:9649: 
--- check asic number
main.c:9745: After Get ASIC NUM CRC error counter=0
main.c:9768: set_baud=0
main.c:10693: The min freq=700
main.c:10695: set real timeout 52, need sleep=379392
main.c:12825: After TEST CRC error counter=0
main.c:14236: search freq for 1 times, completed chain = 3, total chain num = 3 
board_frq_tuning.c:628: single_board_frq_tuning enter
board_frq_tuning.c:629: min_rate, des_rate, fix_volt:13800, 14000, 880
board_frq_tuning.c:254: force_freq not set, don't need tuning
main.c:14645: restart Miner chance num=2
main.c:14685: waiting for receive_func to exit!
main.c:14699: waiting for pic heart to exit!
main.c:13927: bmminer not found= 1827 root       0:00 grep bmminer

main.c:14758: bmminer not found, restart bmminer ...
driver-btm-c5.c:12243:bitmain_c5_init: This is user mode for mining
driver-btm-c5.c:12292:bitmain_c5_init: Detect 512MB control board of XILINX
driver-btm-c5.c:12313:bitmain_c5_init: Miner Type = S9
driver-btm-c5.c:12324:bitmain_c5_init: Miner compile time: Wed Jul 31 16:18:27 CST 2019 type: Antminer S9
driver-btm-c5.c:12414:bitmain_c5_init: miner ID : 8052a5292f90481c
driver-btm-c5.c:12571:bitmain_c5_init: Checking fans...
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=4560
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=4560
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=4320
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=4560
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=4320
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=4560
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=4320
driver-btm-c5.c:13108:bitmain_c5_init: chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
driver-btm-c5.c:13122:bitmain_c5_init: last_freq: 0x00 0x7d 0x00 0x50 0x00 0x50 0x05 0x50 0x00 0x50 0x00 0x50 0x03 0x50 0x03 0x50 0x03 0x50 0x03 0x50 0x03 0x50 0x03 0x50 0x01 0x50 0x01 0x50 0x0f 0x50 0x0f 0x50 0x0f 0x50 0x0f 0x50 0x05 0x50 0x07 0x50 0x23 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 
driver-btm-c5.c:13149:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:13155:bitmain_c5_init: Detect: S9_63 use voltage level=1 : 1
driver-btm-c5.c:13171:bitmain_c5_init: Chain[J6] has backup chain_voltage=870
driver-btm-c5.c:13188:bitmain_c5_init: No scan based on domain
driver-btm-c5.c:1899:jump_to_app_CheckAndRestorePIC: Check chain[5] PIC fw version=0x03
driver-btm-c5.c:13108:bitmain_c5_init: chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
driver-btm-c5.c:13122:bitmain_c5_init: last_freq: 0x00 0x7d 0x00 0x4b 0x00 0x4b 0x04 0x4b 0x0b 0x4b 0x00 0x4b 0x03 0x4b 0x03 0x4b 0x03 0x4b 0x03 0x4b 0x03 0x4b 0x03 0x4b 0x01 0x4b 0x01 0x4b 0x0f 0x4b 0x0f 0x4b 0x0f 0x4b 0x0f 0x4b 0x05 0x4b 0x07 0x4b 0x23 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 0x00 0x4b 
driver-btm-c5.c:13149:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:13155:bitmain_c5_init: Detect: S9_63 use voltage level=1 : 1
driver-btm-c5.c:13171:bitmain_c5_init: Chain[J7] has backup chain_voltage=870
driver-btm-c5.c:13188:bitmain_c5_init: No scan based on domain
driver-btm-c5.c:1899:jump_to_app_CheckAndRestorePIC: Check chain[6] PIC fw version=0x03
driver-btm-c5.c:13108:bitmain_c5_init: chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
driver-btm-c5.c:13122:bitmain_c5_init: last_freq: 0x00 0x7d 0x00 0x47 0x00 0x47 0x04 0x47 0x07 0x47 0x00 0x47 0x03 0x47 0x03 0x47 0x03 0x47 0x03 0x47 0x03 0x47 0x03 0x47 0x01 0x47 0x01 0x47 0x0f 0x47 0x0f 0x47 0x0f 0x47 0x0f 0x47 0x05 0x47 0x09 0x47 0x23 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 0x00 0x47 
driver-btm-c5.c:13149:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:13155:bitmain_c5_init: Detect: S9_63 use voltage level=1 : 1
driver-btm-c5.c:13171:bitmain_c5_init: Chain[J8] has backup chain_voltage=890
driver-btm-c5.c:13188:bitmain_c5_init: No scan based on domain
driver-btm-c5.c:1899:jump_to_app_CheckAndRestorePIC: Check chain[7] PIC fw version=0x03
driver-btm-c5.c:12195:init_exist_chain_table: total_exist_chain_num = 3
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J6] orignal chain_voltage_pic=6 value=940
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J6] will use backup chain_voltage_pic=870 [125]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J6] get working chain_voltage_pic=125
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J7] orignal chain_voltage_pic=6 value=940
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J7] will use backup chain_voltage_pic=870 [125]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J7] get working chain_voltage_pic=125
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J8] orignal chain_voltage_pic=6 value=940
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J8] will use backup chain_voltage_pic=890 [91]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J8] get working chain_voltage_pic=91
driver-btm-c5.c:13421:bitmain_c5_init: Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13421:bitmain_c5_init: Chain[J7] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J7] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J7] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J7] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J7] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J7] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J7] has 0 asic
driver-btm-c5.c:13421:bitmain_c5_init: Chain[J8] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J8] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J8] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J8] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J8] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J8] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J8] has 0 asic
driver-btm-c5.c:4571:set_frequency: miner total rate=0GH/s ideal_total_hash_rate = 0GH/s

driver-btm-c5.c:4819:set_frequency: Miner fix freq ...
driver-btm-c5.c:5119:set_frequency: max freq = 100
driver-btm-c5.c:4162:ProcessFixFreq: totalRate = 0, fixed_totalRate = 0
driver-btm-c5.c:9604:init_uart_baud: set baud=1
driver-btm-c5.c:12103:set_working_voltage: setting to working voltage...
driver-btm-c5.c:13954:bitmain_c5_init: start thread for read temp
setStartTimePoint total_tv_start_sys=199 total_tv_end_sys=200
driver-btm-c5.c:10320:check_system_work: restartNum = 2 , auto-reinit enabled...
driver-btm-c5.c:8727:read_temp_func: bring_up_pcb_temp = -100
do read_temp_func once...
Done check_asic_reg
Max pcb temp : -100
set FAN speed according to: temp_highest=-100 temp_top1[PWM_T]=-100 temp_top1[TEMP_POS_LOCAL]=-100 temp_change=0 fix_fan_steps=0
FAN PWM: 0
read_temp_func Done!
CRC error counter=2

[1714952317]

1714952317

[1714952317]

1714952317

[1714952317]

1714952317

[BitMaxz]

You mean about the motherboard is the control board?

Can you try to test it first with one hashboard or run them one by one follow the guide from this link below to troubleshoot - https://support.bitmain.com/hc/en-us/articles/226142788-Test-hash-board-one-by-one

The logs show that all chains have 0 ASIC have you tried to replace all cables it looks like this below.



It might not be connected properly that is why all ASICs can't detect and also the temp is abnormal.

You can try to flash the control board with an SD card if you feel it's a software issue you can follow the guide - https://support.bitmain.com/hc/en-us/articles/360019493654-S9-series-S9-S9i-S9j-S9-Hydro-Control-Board-Program-Recovery.

[mikeywith]

Code:

driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J7] has 0 asic
driver-btm-c5.c:13421:bitmain_c5_init: Chain[J8] has 0 asic

This implies that all 3 hashboards are dead, this really has nothing to do with the firmware or anything else, if 1 hash board is dead, it usually is, if more than 1 show dead then it could be the PSU, it's very unlikely and uncommon for anything else to be the problem.

[508std]

[...]

Yep by motherboard I mean control board  I'v already tried to replace the cables, also tried the same control board with others hashboard that I know there are working. That's why I'm 100% sure than control board is working.

But the light of the hashboards is turning red? Because on this site I read that you can flash S9 Hashboard with PICKit3, by flashing s9-4.21.hex software. https://asicseer.com/page/restoring-hashboards.

Do you know this solution?

[BitMaxz]

Yes, you can try it but I'm not 100% sure if this will fix your issue unless if the kernel log shows "pic fw version=0x00 or 0xff" it means that the pic firmware is corrupted or deleted. So the only solution to fix the pic issue is to flash it with Pickit 3 with working hex file.

We have an old guide here on how to flash hashboard with a working hex file but it's only for t9+ miner you can find it from this link below that you can use as reference
- https://bitcointalk.org/index.php?topic=5032987.0.


Have you tried to test them one by one? Then run it with low freq. If you don't know how to lower the freq you can follow this guide https://bitcointalk.org/index.php?topic=2690140.msg34057256#msg34057256.

Do this while testing them one by one and maybe the reason for this is because of overtemp that's why all hashboard acting dead.

[508std]

Alright I will try to low the frequence 1 by 1, but if it's work that mean that each hasboard will never came back to the original hash rate right ?

Thanks for your help

[mikeywith]

Do this while testing them one by one and maybe the reason for this is because of overtemp that's why all hashboard acting dead.

This is unlikely to be the case, in fact, it's almost impossible, the reason is that during the initial chip-count the fans will be spinning at 100% and the heating process has just started, actually, the time it takes to count the chips is too short that you can even get away with no fans at all, 0 asic problem is almost never a temperature-related problem.