S17+ Socket connect failed / Find 0 asic - HELP!!

[pintoric]

Hi All,

I got 2 used s17+ to try the waters and learn. Total newbie here. At first, after I configured NiceHash stratums, they started hashing. However one would only recognize one of the three boards and the second two of the three. After rebooting and reflashing the firmware one is hashing nicely on NiceHash but the other looks like an expensive paper weight. Nothing I do would make the Socket Connect Failed message go away and the machine recognize the boards. To be honest the machine that is working has not being turned down yet for complete fear it would brick as well - I'll try once the first one is back working so at least one is hashing.

I already tried everything I could find in this forum and others. See list below. This is my last effort to fix it myself before I find a place to send it to be fixed. I'm that desperate now.

What I already tried:
1. reboot - from browser connected to machine and by turning power off and on
2. reset - from browser and front panel
3. loading new updated firmware - from browser / tried from SD card as well but it didn't go thru - maybe card is to large, 16G
4. opened the control board cover and checked connections
5. checked if machine was properly grounded
6. maybe something else but this is all I remember now
7. every time I try anything I let it run 10/ 20 minutes before trying something else

Attaching the Kernel Log of my last attempt

I'd really appreciate any help this community can provide!! Thanks in advance!!

Code:

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 MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
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: 17/6, WL threshold: 4096, image sequence number: 262741923
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 A9E8BDA4-70DE-45D9-83BE-2DD9F129C0C6, 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: 2814/578, WL threshold: 4096, image sequence number: 3563076859
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 A21581E4-693A-4BBF-A66A-FCE5ACD2EF7F, 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-08-23 00:39:33 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2021-08-23 00:39:33 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version     = 1
2021-08-23 00:39:33 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab        = 1
2021-08-23 00:39:33 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2021-08-23 00:39:33 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun  2 10:31:07 CST 2020 type: Antminer S17+
2021-08-23 00:39:33 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-08-23 00:39:33 driver-btm-api.c:2083:show_sn: len:16, 814c34c42b10481c
2021-08-23 00:39:33 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2021-08-23 00:39:33 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2021-08-23 00:39:33 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 814c34c42b10481c
2021-08-23 00:39:33 fan.c:284:front_fan_power_on: Note: front fan is power on!
2021-08-23 00:39:33 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2021-08-23 00:39:33 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2021-08-23 00:39:33 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2021-08-23 00:39:39 driver-btm-api.c:1239:init_miner_version: miner ID : 814c34c42b10481c
2021-08-23 00:39:39 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2021-08-23 00:39:45 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2021-08-23 00:39:45 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2021-08-23 00:39:45 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2021-08-23 00:39:45 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2021-08-23 00:39:45 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2021-08-23 00:39:45 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2021-08-23 00:39:45 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2021-08-23 00:39:45 thread.c:1363:create_read_nonce_reg_thread: create thread
2021-08-23 00:39:51 driver-btm-api.c:1239:init_miner_version: miner ID : 814c34c42b10481c
2021-08-23 00:39:51 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2021-08-23 00:39:56 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2021-08-23 00:39:56 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2021-08-23 00:39:56 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2021-08-23 00:39:56 driver-btm-api.c:792:_set_project_type: project:0
2021-08-23 00:39:56 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2021-08-23 00:39:56 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2021-08-23 00:39:56 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2021-08-23 00:39:56 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2021-08-23 00:39:56 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2021-08-23 00:39:56 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2021-08-23 00:39:56 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2021-08-23 00:39:58 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2021-08-23 00:39:59 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-08-23 00:40:01 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2021-08-23 00:40:02 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-08-23 00:40:04 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2021-08-23 00:40:05 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-08-23 00:40:07 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2021-08-23 00:40:07 thread.c:1358:create_pic_heart_beat_thread: create thread
2021-08-23 00:40:07 power_api.c:213:power_init: Power init:
2021-08-23 00:40:07 power_api.c:214:power_init: current_voltage_raw = 0
2021-08-23 00:40:07 power_api.c:215:power_init: highest_voltage_raw = 2100
2021-08-23 00:40:07 power_api.c:216:power_init: working_voltage_raw = 1950
2021-08-23 00:40:07 power_api.c:217:power_init: higher_voltage_raw  = 2040
2021-08-23 00:40:07 power_api.c:218:power_init: check_asic_voltage_raw  = 2100
2021-08-23 00:40:07 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-08-23 00:40:07 power_api.c:186:power_off: init gpio907
2021-08-23 00:40:39 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2021-08-23 00:41:05 power_api.c:85:check_voltage_multi: retry time: 0
2021-08-23 00:41:06 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.162404
2021-08-23 00:41:07 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.016624
2021-08-23 00:41:08 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.138107
2021-08-23 00:41:08 power_api.c:53:_get_avg_voltage: average_voltage = 21.105712
2021-08-23 00:41:08 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.11, check voltage passed.
2021-08-23 00:41:08 uart.c:72:set_baud: set fpga_baud to 115200
2021-08-23 00:41:19 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 0
2021-08-23 00:41:30 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 1
2021-08-23 00:41:41 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2
2021-08-23 00:41:41 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2100
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-08-23 00:41:50 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 3
2021-08-23 00:41:50 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2050
2021-08-23 00:41:50 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2021-08-23 00:41:53 power_api.c:85:check_voltage_multi: retry time: 0
2021-08-23 00:41:55 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.652174
2021-08-23 00:41:56 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.506394
2021-08-23 00:41:57 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.627877
2021-08-23 00:41:57 power_api.c:53:_get_avg_voltage: average_voltage = 20.595482
2021-08-23 00:41:57 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.60, check voltage passed.
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-08-23 00:42:06 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 4
2021-08-23 00:42:06 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2000
2021-08-23 00:42:06 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2021-08-23 00:42:09 power_api.c:85:check_voltage_multi: retry time: 0
2021-08-23 00:42:11 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.141944
2021-08-23 00:42:12 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 19.996164
2021-08-23 00:42:13 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.117647
2021-08-23 00:42:13 power_api.c:53:_get_avg_voltage: average_voltage = 20.085251
2021-08-23 00:42:13 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.09, check voltage passed.
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-08-23 00:42:21 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 5
2021-08-23 00:42:21 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2100
2021-08-23 00:42:21 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2021-08-23 00:42:26 power_api.c:85:check_voltage_multi: retry time: 0
2021-08-23 00:42:28 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.162404
2021-08-23 00:42:29 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.992327
2021-08-23 00:42:30 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.113811
2021-08-23 00:42:30 power_api.c:53:_get_avg_voltage: average_voltage = 21.089514
2021-08-23 00:42:30 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.09, check voltage passed.
2021-08-23 00:42:30 driver-btm-api.c:1193:check_asic_number: Chain 0 only find 0 asic, will power off hash board 0
2021-08-23 00:42:31 driver-btm-api.c:1195:check_asic_number: Chain 0 voltage: an0 = 2.800000, an2 2.809677, an6 2.525806.
2021-08-23 00:42:43 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2021-08-23 00:42:53 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2021-08-23 00:43:04 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2021-08-23 00:43:04 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2100
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-08-23 00:43:13 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 3
2021-08-23 00:43:13 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2050
2021-08-23 00:43:13 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2021-08-23 00:43:16 power_api.c:85:check_voltage_multi: retry time: 0
2021-08-23 00:43:17 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.480203
2021-08-23 00:43:18 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.627877
2021-08-23 00:43:18 power_api.c:53:_get_avg_voltage: average_voltage = 20.554040
2021-08-23 00:43:18 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.55, check voltage passed.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-08-23 00:43:27 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 4
2021-08-23 00:43:27 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2000
2021-08-23 00:43:27 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2021-08-23 00:43:30 power_api.c:85:check_voltage_multi: retry time: 0
2021-08-23 00:43:32 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 19.970624
2021-08-23 00:43:33 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.117647
2021-08-23 00:43:33 power_api.c:53:_get_avg_voltage: average_voltage = 20.044136
2021-08-23 00:43:33 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.04, check voltage passed.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-08-23 00:43:41 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 5
2021-08-23 00:43:41 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2100
2021-08-23 00:43:41 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2021-08-23 00:43:46 power_api.c:85:check_voltage_multi: retry time: 0
2021-08-23 00:43:47 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.965516
2021-08-23 00:43:49 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.113811
2021-08-23 00:43:49 power_api.c:53:_get_avg_voltage: average_voltage = 21.039663
2021-08-23 00:43:49 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.04, check voltage passed.
2021-08-23 00:43:49 driver-btm-api.c:1193:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2021-08-23 00:43:50 driver-btm-api.c:1195:check_asic_number: Chain 1 voltage: an0 = 2.803226, an2 2.787097, an6 2.525806.
2021-08-23 00:44:01 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2021-08-23 00:44:12 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2021-08-23 00:44:23 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2021-08-23 00:44:23 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2100
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-08-23 00:44:32 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 3
2021-08-23 00:44:32 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2050
2021-08-23 00:44:32 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2021-08-23 00:44:35 power_api.c:85:check_voltage_multi: retry time: 0
2021-08-23 00:44:36 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.601531
2021-08-23 00:44:36 power_api.c:53:_get_avg_voltage: average_voltage = 20.601531
2021-08-23 00:44:36 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.60, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-08-23 00:44:45 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 4
2021-08-23 00:44:45 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2000
2021-08-23 00:44:45 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2021-08-23 00:44:48 power_api.c:85:check_voltage_multi: retry time: 0
2021-08-23 00:44:50 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.091953
2021-08-23 00:44:50 power_api.c:53:_get_avg_voltage: average_voltage = 20.091953
2021-08-23 00:44:50 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.09, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-08-23 00:44:59 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 5
2021-08-23 00:44:59 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2100
2021-08-23 00:44:59 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2021-08-23 00:45:04 power_api.c:85:check_voltage_multi: retry time: 0
2021-08-23 00:45:05 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.086844
2021-08-23 00:45:05 power_api.c:53:_get_avg_voltage: average_voltage = 21.086844
2021-08-23 00:45:05 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.09, check voltage passed.
2021-08-23 00:45:05 driver-btm-api.c:1193:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2021-08-23 00:45:06 driver-btm-api.c:1195:check_asic_number: Chain 2 voltage: an0 = 2.800000, an2 2.803226, an6 2.525806.
2021-08-23 00:45:07 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2021-08-23 00:45:07 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2021-08-23 00:45:07 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2021-08-23 00:45:07 driver-btm-api.c:141:killall_hashboard: ****power off hashboard****

[1715455480]

1715455480

[1715455480]

1715455480

[philipma1957]

nicehash is not a great choice.


that aside

it looks like you have bad boards.

try flashing braiins firmware to and sd card and boot from the sd card.

if it boots and lets you do manual settings try freq 400 for each board and volts 16.3


good luck

[pintoric]

I was afraid of bad boards. I'm trying your suggestion right now, thanks.

[pintoric]

nicehash is not a great choice.


that aside

it looks like you have bad boards.

try flashing braiins firmware to and sd card and boot from the sd card.

if it boots and lets you do manual settings try freq 400 for each board and volts 16.3


good luck

my miner seems to have some real issues. I formatted a 16g SD card to FAT32 and copied the BOS+ to work from SD and to Auto Install. On both the machine turns on but keeps both lights on and never seem to really boot. Seems like it gets stuck on booting from the card. Any suggestions? Maybe this is where I should ask for people that could check my miner and fix it? Thoughts?

BTW completely agree with the NH statement, it was just the first one I tried / tested but am already looking into other options


Thanks

[ruber1]

Chain[1]: find 0 asic, times 2
Chain[1]: find 0 asic, times 2
Chain[2]: find 0 asic, times 2
All three boards are failing to boot and likely have bad asic chips. Way to common with S17 models.

I have one board that if I reboot maybe 6 - 8 times in a row, it comes to life. And hashes without hiccup for weeks until I have to reboot.
**You could try that just to see if you can get a board to go, but may not work and the board will still need repair eventually.

I have had 6 of 9 boards fail in three machines. I was able to get 2 repaired, 1 unrepairable, and others pending repair hopefully.
If you feel like it, you could carefully remove the boards, and may find loose or shifted heat sinks as well. That's a sign it got too hot. Loose heatsinks (completely detached), or even shifted, can sometimes be reset with a heat gun if you know what you are doing, and board MAY come back. This has worked for me a few times. But there is likely still an issue with that chip overheating in general. Shifted heatsinks, again because that chip got too hot, and heatsink did re-fuse, may not have re-fused completely or created solder balls under on chip shorting out asic.

Finding a repair facility is hard. At least has been for me as they are backlogged. I used HMtech most recently but they have stopped accepting new customers with less than 25 units in need of repair due to backlog.

[pintoric]

I'll give it a try on rebooting several times in a row. That's one thing I haven't tried yet

I started looking for a repair facility and, like you said, no one is taking new orders, specially for only one machine.

I'll also try to find time this weekend to open it up and check the boards. I'm also suspicious of the control board. Following another thread I disconnected the boards to check if it would connect to no success. But Besides the socket connect failed everything else seems to work, I can ping other urls and all seem to work. Then back to the hashboard option - maybe I'll try to learn myself a way to DIY and fix one to start.

[mikeywith]

In most cases, when the kernel log says hash board x found 0 Asics, it simply means the board is dead, it either has a dead chip somewhere or another burned component, in other rare cases a bad PSU will cause this error, the PSU needs to supply enough power to those hash boards in order for them to function and report the correct asic count, sometimes when the PSU is faulty but not completely dead (it only supplies 12v to the control board) you might get this 0 asic error.

So long story short, try swapping the PSU and see if you get lucky.

[pintoric]

In most cases, when the kernel log says hash board x found 0 Asics, it simply means the board is dead, it either has a dead chip somewhere or another burned component, in other rare cases a bad PSU will cause this error, the PSU needs to supply enough power to those hash boards in order for them to function and report the correct asic count, sometimes when the PSU is faulty but not completely dead (it only supplies 12v to the control board) you might get this 0 asic error.

So long story short, try swapping the PSU and see if you get lucky.

Is there a way to check if it's the psu instead of a swap? Would I be able to measure the voltage with a multimeter? or would the kernel log report the actual voltage in the case of a faulty unit?

Thanks

[mikeywith]

Is there a way to check if it's the psu instead of a swap? Would I be able to measure the voltage with a multimeter? or would the kernel log report the actual voltage in the case of a faulty unit?

You could measure the voltage across all three board at the edge of the busbar, but honestly, I don't have enough knowledge about that PSU to confirm if that will be a sufficient and accurate test, I still think the best approach is swapping the PSU, it's not that hard, it takes like 5 mins or so.

[pintoric]

hey, had some progress this weekend. Managed to install Braiins on the machine after installing the Antminer MP firmware. Got the Kernel log from the MP firmware, see below, and to my untrained eyes almost looks like it could recognize all the asics. However I could not configure it to mine so installed Braiins. With Brains the machine connects to NiceHash but shows zero activity on hashing. In my view proves control board is working but hashing are bad except for the MP firmware that seems to say something else. I also opened the top and measured the voltage whish was aligned with expectations, 21v solid.

Unless anyone has any other suggestions I'm starting to reach out to places to send the machine for repair. I'm not sure I'd try to open it further and check the hashboards etc. Also not sure I would be able to fix it anyway, any thoughts?

Thanks for the guidance so far.

[Artemis3]

In Braiins OS the logs may have a line that says x voltage requested, y given.
Also for nicehash you have to use sha256asicboost urls, not sha256.

I would also try Autotuning enabled and the lowest power limit.

Remember, with Autotuning enabled, none of the manual settings (speed/voltage) apply.

[pintoric]

hey, thanks for the note.

I was pointing it to sha256 boost, my mistake not calling it out.

I tried the different settings in Braiins and still got the same old 0 hash. Only difference this time is that NiceHash aknowledged the miner was connected but no hashing

I'm packing the unit and sending for repair.

Thank you all for your suggestions!! Was worth trying!!

[1710r238]

you have to go to the repair house. but if you have the ability to handle the electronics, you can fix it by yourself.

in my case, I can fix the older miner, for example L3+, S9, also having S17 series, just send to repair center due to it has still not to be the EOS.