Used Antminer S17 Pro - Having issues and PO finally said he had it plugged 120v

[mysticbitcoin]

I just bought a used Antminer S17Pro and it shows a Red Fault light. When you plug it in it goes to maximum fan speed. I'll pull the logs as the controller still works and shows a socket connection failed message in the HW field. The previous owner finally told me that he had it plugged in his garage on 120v for a few days. My question is that what kind of damage does this do, I haven't plugged it into my 240V yet, as I'd like to know what damage was done before powering it up again.

[NotFuzzyWarm]

The only possible damage would have been to the PSU with blown input rectifiers or soft-start thermistor. Frankly I am surprised the PO was able to run it at all (did they say it ran?) as the PSU should have shut down/not started at that low voltage. I'd plug it into 240VAC and see if it runs.

[mikeywith]

Frankly I am surprised the PO was able to run it at all (did they say it ran?)

Even if the seller says it worked i wouldn't believe them, i have personal experience with these gears, anything below 200v it starts acting, maybe 198v and it shuts down all hash boards, i highly doubt his gear would be any different.

Your only option now is to plug it into a 200-240v socket and see how it does, it is a 50/50 chance i'd sat,it will either work just fine or you will need a new psu, it is highly unlikely that any other components got toasted in the process.

[mysticbitcoin]

Many thanks for the information. I'll post my findings. To answer your question. YES, it does run on 120V, but he was able to for about 4 days.

[mikeywith]

... it does run on 120V, but he was able to for about 4 days.

Do you trust the seller's words like 100%? I hope you don't because I am pretty confident he is not telling you the truth, I have at least one the following gears.

T17
T17e
S17 pro
S17+

NONE of them would work without a voltage regulator and the voltage hardly dips below 190v, so even 195v was not enough, let alone 110-120v, so it's one of two things, either he is not telling you the truth, or he has gotten a magically different S17 pro that somehow manages to run on a 120v socket, and I highly doubt the latter, unless by "run" he means fans spinning, LEDs are on but not exactly hashing.

[philipma1957]

Like mikey


my

t17
s17
s17pro
t17e
t17+

all need to be at 210 to 240 volts to run and actually hash

[Artemis3]

Does it fail with 208v? (two 120v hot from different phases) Did you ever try?

[mysticbitcoin]

Ok, Got it setup on 240v and she powers up but I have an error:

Code:

Hardware Version:	Socket connect failed: Connection refused

Here is the log:

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: 203612K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25764K 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: 12724K (cce94000 - 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: 10/4, WL threshold: 4096, image sequence number: 306349061
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 038216C1-D266-46DA-A76E-C04B142933A3, 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: 874/320, WL threshold: 4096, image sequence number: 1751317449
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 51C7124B-A562-4AA0-948B-184BE8DB9030, 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 = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-04-08 16:02:40 driver-btm-api.c:515:init_freq_mode: This is scan-user version
2020-04-08 16:02:40 driver-btm-api.c:1871:bitmain_soc_init: opt_multi_version     = 1
2020-04-08 16:02:40 driver-btm-api.c:1872:bitmain_soc_init: opt_bitmain_ab        = 1
2020-04-08 16:02:40 driver-btm-api.c:1873:bitmain_soc_init: opt_bitmain_work_mode = 2
2020-04-08 16:02:40 driver-btm-api.c:1874:bitmain_soc_init: Miner compile time: Wed Dec 25 09:47:07 CST 2019 type: Antminer S17 Pro
2020-04-08 16:02:40 driver-btm-api.c:1875:bitmain_soc_init: commit version: b1e11d0 2019-12-24 22:26:20, build by: lol 2019-12-25 09:59:19
2020-04-08 16:02:40 driver-btm-api.c:1664:show_sn: no SN got, please write SN to /nvdata/sn
2020-04-08 16:02:40 driver-btm-api.c:1013:miner_device_init: Detect 256MB control board of XILINX
2020-04-08 16:02:40 driver-btm-api.c:961:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2020-04-08 16:02:46 driver-btm-api.c:945:init_miner_version: miner ID : 802c542e57408854
2020-04-08 16:02:46 driver-btm-api.c:951:init_miner_version: FPGA Version = 0xB013
2020-04-08 16:02:51 thread.c:699:create_read_nonce_reg_thread: create thread
2020-04-08 16:02:51 driver-btm-api.c:589:get_product_id: product_id[0] = 0
2020-04-08 16:02:51 driver-btm-api.c:589:get_product_id: product_id[1] = 0
2020-04-08 16:02:51 driver-btm-api.c:589:get_product_id: product_id[2] = 0
2020-04-08 16:02:51 driver-btm-api.c:533:_set_project_type: project:0
2020-04-08 16:02:51 driver-btm-api.c:558:_set_project_type: Project type: Antminer S17 Pro
2020-04-08 16:02:51 driver-btm-api.c:569:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2020-04-08 16:02:51 driver-btm-api.c:570:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2020-04-08 16:02:51 driver-btm-api.c:569:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2020-04-08 16:02:51 driver-btm-api.c:570:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2020-04-08 16:02:51 driver-btm-api.c:569:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2020-04-08 16:02:51 driver-btm-api.c:570:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2020-04-08 16:02:52 driver-btm-api.c:1785:bitmain_board_init: Fan check passed.
2020-04-08 16:02:53 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-04-08 16:02:55 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-04-08 16:02:56 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-04-08 16:02:58 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-04-08 16:02:59 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-04-08 16:03:01 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-04-08 16:03:01 thread.c:694:create_pic_heart_beat_thread: create thread
2020-04-08 16:03:01 power_api.c:207:power_init: Power init:
2020-04-08 16:03:01 power_api.c:208:power_init: current_voltage_raw = 0
2020-04-08 16:03:01 power_api.c:209:power_init: highest_voltage_raw = 2100
2020-04-08 16:03:01 power_api.c:210:power_init: working_voltage_raw = 1830
2020-04-08 16:03:01 power_api.c:211:power_init: higher_voltage_raw  = 1950
2020-04-08 16:03:01 driver-btm-api.c:1795:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-04-08 16:03:33 power_api.c:251:set_to_highest_voltage: Set to voltage raw 2100, one step.
2020-04-08 16:03:35 power_api.c:87:check_voltage_multi: retry time: 0
2020-04-08 16:03:36 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 21.038789
2020-04-08 16:03:38 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.106142
2020-04-08 16:03:39 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 20.965312
2020-04-08 16:03:39 power_api.c:50:_get_avg_voltage: average_voltage = 21.036748
2020-04-08 16:03:39 power_api.c:68:check_voltage: target_vol = 21.00, actural_vol = 21.04, check voltage passed.
2020-04-08 16:03:39 uart.c:71:set_baud: set fpga_baud to 115200
2020-04-08 16:03:39 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-04-08 16:03:39 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-04-08 16:03:39 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-04-08 16:03:50 driver-btm-api.c:888:check_asic_number_with_power_on: Chain[0]: find 47 asic, times 0
2020-04-08 16:04:01 driver-btm-api.c:888:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 1
2020-04-08 16:04:12 driver-btm-api.c:888:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2020-04-08 16:04:23 driver-btm-api.c:888:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2020-04-08 16:04:28 driver-btm-api.c:344:set_order_clock: chain[0]: set order clock, stragegy 3
2020-04-08 16:04:28 driver-btm-api.c:344:set_order_clock: chain[1]: set order clock, stragegy 3
2020-04-08 16:04:28 driver-btm-api.c:344:set_order_clock: chain[2]: set order clock, stragegy 3
2020-04-08 16:04:28 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2020-04-08 16:04:28 uart.c:71:set_baud: set fpga_baud to 3000000
2020-04-08 16:04:28 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-04-08 16:04:28 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-04-08 16:04:28 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-04-08 16:04:28 driver-btm-api.c:1547:check_clock_counter: freq 50 clock_counter_limit 6
2020-04-08 16:04:30 uart.c:71:set_baud: set fpga_baud to 115200
2020-04-08 16:04:30 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-04-08 16:04:30 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-04-08 16:04:30 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-04-08 16:04:31 voltage[0] = 1840
2020-04-08 16:04:31 voltage[1] = 1840
2020-04-08 16:04:31 voltage[2] = 1840
2020-04-08 16:04:31 power_api.c:219:set_working_voltage_raw: working_voltage_raw = 1840
2020-04-08 16:04:32 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-04-08 16:04:33 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-04-08 16:04:35 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-04-08 16:04:35 uart.c:71:set_baud: set fpga_baud to 6000000
2020-04-08 16:04:35 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-04-08 16:04:35 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-04-08 16:04:35 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-04-08 16:04:36 driver-btm-api.c:244:check_bringup_temp: Bring up temperature is 13
2020-04-08 16:04:36 thread.c:714:create_check_miner_status_thread: create thread
2020-04-08 16:04:36 thread.c:704:create_set_miner_status_thread: create thread
2020-04-08 16:04:36 thread.c:689:create_temperature_monitor_thread: create thread
2020-04-08 16:04:36 freq_tuning.c:195:freq_tuning_get_max_freq: Max freq of tuning is 780
2020-04-08 16:04:36 frequency.c:711:inc_freq_with_fixed_vco: chain = 255, freq = 545, is_higher_voltage = true
2020-04-08 16:04:36 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 2020, step by step.
2020-04-08 16:04:56 power_api.c:87:check_voltage_multi: retry time: 0
2020-04-08 16:04:57 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 20.212177
2020-04-08 16:04:58 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 20.291777
2020-04-08 16:05:00 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 20.150947
2020-04-08 16:05:00 power_api.c:50:_get_avg_voltage: average_voltage = 20.218301
2020-04-08 16:05:00 power_api.c:68:check_voltage: target_vol = 20.20, actural_vol = 20.22, check voltage passed.

[mysticbitcoin]

Right now the S17 Pro seems to be going through some sort of diagnoses loop. Where the machine boots with the Hardware Version Error Socket connect failed: Connection refused and the Kernel only shows an warning:

Code:

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

It cycles the fans through out the process of booting and in the end it starts stepping (systematically increasing the fans and the heat of the asics) over a period of time ~10-15minutes then it seems to reboot. Because when I check the kernel logs again it has cleared and shows that it had rebooted.

So, to be verbose and for any future people who have had a machine plugged into 120V. So far the fact that the S17 Pro boots and kernel log doesn't show any major errors, the lower voltage is not a critical event where the miner ends up with major damage. Now, its just finding out this issue. I have downloaded the latest firmware from Bitmain (https://service.bitmain.com/support/download?product=Antminer%20S17%20Pro) the top one for the version V12.25 (Antminer-S17Pro-user-OM-201912250947-sig_5073.tar.gz) and done many resets to default, with no success. The only other error I get is when you do not populate the Miner Configuration and it shows up as an error in the kernel log.

[NotFuzzyWarm]

You have read the various about Antminers and esp. one regarding the S17 to know that all Antminers go through an autotune process when they are powered up right?.... It can take anywhere from several min to around a 1/2hr for them to figure out optimum voltage & speeds before they start hashing on your pools.

[mysticbitcoin]

Yes, correct I have read the forums, but the machine has been on for hours and the same thing keeps rebooting. Here is the latest logs ( sorry I wish I knew how to do the embedded text file with scrolling)

*EDIT: Found it it's the"code" flag to properly post logs. (Credit: mikeywith)

Kernel Log

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: 203612K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25764K 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: 12724K (cce94000 - 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: 10/4, WL threshold: 4096, image sequence number: 306349061
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 038216C1-D266-46DA-A76E-C04B142933A3, 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: 874/320, WL threshold: 4096, image sequence number: 1751317449
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 51C7124B-A562-4AA0-948B-184BE8DB9030, 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 = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-04-08 16:55:15 driver-btm-api.c:515:init_freq_mode: This is scan-user version
2020-04-08 16:55:15 driver-btm-api.c:1871:bitmain_soc_init: opt_multi_version     = 1
2020-04-08 16:55:15 driver-btm-api.c:1872:bitmain_soc_init: opt_bitmain_ab        = 1
2020-04-08 16:55:15 driver-btm-api.c:1873:bitmain_soc_init: opt_bitmain_work_mode = 2
2020-04-08 16:55:15 driver-btm-api.c:1874:bitmain_soc_init: Miner compile time: Wed Dec 25 09:47:07 CST 2019 type: Antminer S17 Pro
2020-04-08 16:55:15 driver-btm-api.c:1875:bitmain_soc_init: commit version: b1e11d0 2019-12-24 22:26:20, build by: lol 2019-12-25 09:59:19
2020-04-08 16:55:15 driver-btm-api.c:1664:show_sn: no SN got, please write SN to /nvdata/sn
2020-04-08 16:55:15 driver-btm-api.c:1013:miner_device_init: Detect 256MB control board of XILINX
2020-04-08 16:55:15 driver-btm-api.c:961:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2020-04-08 16:55:21 driver-btm-api.c:945:init_miner_version: miner ID : 802c542e57408854
2020-04-08 16:55:21 driver-btm-api.c:951:init_miner_version: FPGA Version = 0xB013
2020-04-08 16:55:26 thread.c:699:create_read_nonce_reg_thread: create thread
2020-04-08 16:55:26 driver-btm-api.c:589:get_product_id: product_id[0] = 0
2020-04-08 16:55:26 driver-btm-api.c:589:get_product_id: product_id[1] = 0
2020-04-08 16:55:26 driver-btm-api.c:589:get_product_id: product_id[2] = 0
2020-04-08 16:55:26 driver-btm-api.c:533:_set_project_type: project:0
2020-04-08 16:55:26 driver-btm-api.c:558:_set_project_type: Project type: Antminer S17 Pro
2020-04-08 16:55:26 driver-btm-api.c:569:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2020-04-08 16:55:26 driver-btm-api.c:570:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2020-04-08 16:55:26 driver-btm-api.c:569:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2020-04-08 16:55:26 driver-btm-api.c:570:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2020-04-08 16:55:26 driver-btm-api.c:569:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2020-04-08 16:55:26 driver-btm-api.c:570:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2020-04-08 16:55:27 driver-btm-api.c:1785:bitmain_board_init: Fan check passed.
2020-04-08 16:55:28 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-04-08 16:55:30 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-04-08 16:55:31 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-04-08 16:55:34 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-04-08 16:55:35 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-04-08 16:55:37 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-04-08 16:55:37 thread.c:694:create_pic_heart_beat_thread: create thread
2020-04-08 16:55:37 power_api.c:207:power_init: Power init:
2020-04-08 16:55:37 power_api.c:208:power_init: current_voltage_raw = 0
2020-04-08 16:55:37 power_api.c:209:power_init: highest_voltage_raw = 2100
2020-04-08 16:55:37 power_api.c:210:power_init: working_voltage_raw = 1830
2020-04-08 16:55:37 power_api.c:211:power_init: higher_voltage_raw  = 1950
2020-04-08 16:55:37 driver-btm-api.c:1795:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-04-08 16:56:09 power_api.c:251:set_to_highest_voltage: Set to voltage raw 2100, one step.
2020-04-08 16:56:11 power_api.c:87:check_voltage_multi: retry time: 0
2020-04-08 16:56:12 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 21.014297
2020-04-08 16:56:13 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.100019
2020-04-08 16:56:14 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 20.977558
2020-04-08 16:56:14 power_api.c:50:_get_avg_voltage: average_voltage = 21.030625
2020-04-08 16:56:14 power_api.c:68:check_voltage: target_vol = 21.00, actural_vol = 21.03, check voltage passed.
2020-04-08 16:56:14 uart.c:71:set_baud: set fpga_baud to 115200
2020-04-08 16:56:14 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-04-08 16:56:14 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-04-08 16:56:14 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-04-08 16:56:25 driver-btm-api.c:888:check_asic_number_with_power_on: Chain[0]: find 47 asic, times 0
2020-04-08 16:56:36 driver-btm-api.c:888:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 1
2020-04-08 16:56:47 driver-btm-api.c:888:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2020-04-08 16:56:58 driver-btm-api.c:888:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2020-04-08 16:57:03 driver-btm-api.c:344:set_order_clock: chain[0]: set order clock, stragegy 3
2020-04-08 16:57:04 driver-btm-api.c:344:set_order_clock: chain[1]: set order clock, stragegy 3
2020-04-08 16:57:04 driver-btm-api.c:344:set_order_clock: chain[2]: set order clock, stragegy 3
2020-04-08 16:57:04 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2020-04-08 16:57:04 uart.c:71:set_baud: set fpga_baud to 3000000
2020-04-08 16:57:04 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-04-08 16:57:04 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-04-08 16:57:04 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-04-08 16:57:04 driver-btm-api.c:1547:check_clock_counter: freq 50 clock_counter_limit 6
2020-04-08 16:57:06 uart.c:71:set_baud: set fpga_baud to 115200
2020-04-08 16:57:06 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-04-08 16:57:06 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-04-08 16:57:06 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-04-08 16:57:06 voltage[0] = 1840
2020-04-08 16:57:06 voltage[1] = 1840
2020-04-08 16:57:06 voltage[2] = 1840
2020-04-08 16:57:06 power_api.c:219:set_working_voltage_raw: working_voltage_raw = 1840
2020-04-08 16:57:07 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-04-08 16:57:09 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-04-08 16:57:10 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-04-08 16:57:10 uart.c:71:set_baud: set fpga_baud to 6000000
2020-04-08 16:57:10 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-04-08 16:57:10 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-04-08 16:57:10 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-04-08 16:57:12 driver-btm-api.c:244:check_bringup_temp: Bring up temperature is 16
2020-04-08 16:57:12 thread.c:714:create_check_miner_status_thread: create thread
2020-04-08 16:57:12 thread.c:704:create_set_miner_status_thread: create thread
2020-04-08 16:57:12 thread.c:689:create_temperature_monitor_thread: create thread
2020-04-08 16:57:12 freq_tuning.c:195:freq_tuning_get_max_freq: Max freq of tuning is 780
2020-04-08 16:57:12 frequency.c:711:inc_freq_with_fixed_vco: chain = 255, freq = 545, is_higher_voltage = true
2020-04-08 16:57:12 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 2020, step by step.
2020-04-08 16:57:32 power_api.c:87:check_voltage_multi: retry time: 0
2020-04-08 16:57:33 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 20.206054
2020-04-08 16:57:34 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 20.267285
2020-04-08 16:57:35 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 20.175439
2020-04-08 16:57:35 power_api.c:50:_get_avg_voltage: average_voltage = 20.216260
2020-04-08 16:57:35 power_api.c:68:check_voltage: target_vol = 20.20, actural_vol = 20.22, check voltage passed.
2020-04-08 16:59:47 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1920, step by step.
2020-04-08 17:00:03 power_api.c:87:check_voltage_multi: retry time: 0
2020-04-08 17:00:04 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 19.189629
2020-04-08 17:00:05 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 19.244736
2020-04-08 17:00:06 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 19.140644
2020-04-08 17:00:06 power_api.c:50:_get_avg_voltage: average_voltage = 19.191670
2020-04-08 17:00:06 power_api.c:68:check_voltage: target_vol = 19.20, actural_vol = 19.19, check voltage passed.
2020-04-08 17:00:36 frequency.c:761:inc_freq_with_fixed_step: chain = 0, freq_start = 545, freq_end = 560, freq_step = 5, is_higher_voltage = true
2020-04-08 17:00:37 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1880, step by step.
2020-04-08 17:00:55 power_api.c:87:check_voltage_multi: retry time: 0
2020-04-08 17:00:56 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 18.791631
2020-04-08 17:00:57 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 18.834492
2020-04-08 17:00:58 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 18.748769
2020-04-08 17:00:58 power_api.c:50:_get_avg_voltage: average_voltage = 18.791631
2020-04-08 17:00:58 power_api.c:68:check_voltage: target_vol = 18.80, actural_vol = 18.79, check voltage passed.
2020-04-08 17:00:59 frequency.c:761:inc_freq_with_fixed_step: chain = 2, freq_start = 545, freq_end = 560, freq_step = 5, is_higher_voltage = true
2020-04-08 17:00:59 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1920, step by step.
2020-04-08 17:01:20 power_api.c:87:check_voltage_multi: retry time: 0
2020-04-08 17:01:21 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 19.201875
2020-04-08 17:01:22 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 19.232490
2020-04-08 17:01:23 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 19.171260
2020-04-08 17:01:23 power_api.c:50:_get_avg_voltage: average_voltage = 19.201875
2020-04-08 17:01:23 power_api.c:68:check_voltage: target_vol = 19.20, actural_vol = 19.20, check voltage passed.
2020-04-08 17:01:24 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1880, step by step.
2020-04-08 17:01:42 power_api.c:87:check_voltage_multi: retry time: 0
2020-04-08 17:01:44 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 18.791631
2020-04-08 17:01:45 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 18.846738
2020-04-08 17:01:46 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 18.761015
2020-04-08 17:01:46 power_api.c:50:_get_avg_voltage: average_voltage = 18.799795
2020-04-08 17:01:46 power_api.c:68:check_voltage: target_vol = 18.80, actural_vol = 18.80, check voltage passed.
2020-04-08 17:01:47 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1900, step by step.
2020-04-08 17:02:06 power_api.c:87:check_voltage_multi: retry time: 0
2020-04-08 17:02:08 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 19.030429
2020-04-08 17:02:09 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 19.048799
2020-04-08 17:02:10 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 18.950830
2020-04-08 17:02:10 power_api.c:50:_get_avg_voltage: average_voltage = 19.010019
2020-04-08 17:02:10 power_api.c:68:check_voltage: target_vol = 19.00, actural_vol = 19.01, check voltage passed.
2020-04-08 17:02:10 frequency.c:761:inc_freq_with_fixed_step: chain = 0, freq_start = 560, freq_end = 590, freq_step = 5, is_higher_voltage = true
2020-04-08 17:02:13 driver-btm-api.c:501:set_timeout: freq = 590, percent = 90, hcn = 73728, timeout = 124
2020-04-08 17:02:13 power_api.c:225:set_higher_voltage_raw: higher_voltage_raw = 1940
2020-04-08 17:02:13 power_api.c:281:set_to_higher_voltage_by_steps: Set to voltage raw 1940, step by step.
2020-04-08 17:02:33 power_api.c:87:check_voltage_multi: retry time: 0
2020-04-08 17:02:35 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 19.397812
2020-04-08 17:02:36 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 19.416181
2020-04-08 17:02:37 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 19.342705
2020-04-08 17:02:37 power_api.c:50:_get_avg_voltage: average_voltage = 19.385566
2020-04-08 17:02:37 power_api.c:68:check_voltage: target_vol = 19.40, actural_vol = 19.39, check voltage passed.
2020-04-08 17:02:37 thread.c:709:create_check_system_status_thread: create thread
2020-04-08 17:02:37 driver-btm-api.c:1980:bitmain_soc_init: Init done!
2020-04-08 17:02:37 driver-btm-api.c:197:set_miner_status: STATUS_INIT
2020-04-08 17:02:42 driver-btm-api.c:197:set_miner_status: STATUS_OKAY
2020-04-08 17:02:43 frequency.c:196:get_ideal_hash_rate_GH: ideal_hash_rate = 53579
2020-04-08 17:02:43 frequency.c:212:get_sale_hash_rate_GH: sale_hash_rate = 53000

[thierry4wd]

This miner showing good run !

Code:

2020-04-08 17:02:37 driver-btm-api.c: 197: set_miner_status: STATUS_INIT
2020-04-08 17:02:42 driver-btm-api.c: 197: set_miner_status: STATUS_OKAY
2020-04-08 17:02:43 fréquence.c: 196: get_ideal_hash_rate_GH: ideal_hash_rate = 53579
2020-04-08 17:02:43 fréquence.c: 212: get_sale_hash_rate_GH: sale_hash_rate = 53000

[mysticbitcoin]

Yes, that's what the logs show, but there still is an issue with constant Rebooting after showing that status in the Kernel Log as well as on the main overview page showing the error Hardware Version:   Socket connect failed: Connection refused.

[philipma1957]

Once again   the shit in red is standard  and will show  until machine connects

once miner gets here:

Code:

2020-04-08 17:02:37 driver-btm-api.c: 197: set_miner_status: STATUS_INIT
2020-04-08 17:02:42 driver-btm-api.c: 197: set_miner_status: STATUS_OKAY
2020-04-08 17:02:43 fréquence.c: 196: get_ideal_hash_rate_GH: ideal_hash_rate = 53579
2020-04-08 17:02:43 fréquence.c: 212: get_sale_hash_rate_GH: sale_hash_rate = 53000

that red type goes bye bye.

So the question is  do you connect and mine at all?

The logs show you start to mine.  do you get and hash action at all say 5 minutes then the reboot?

Or does the

Code:

2020-04-08 17:02:37 driver-btm-api.c: 197: set_miner_status: STATUS_INIT
2020-04-08 17:02:42 driver-btm-api.c: 197: set_miner_status: STATUS_OKAY
2020-04-08 17:02:43 fréquence.c: 196: get_ideal_hash_rate_GH: ideal_hash_rate = 53579
2020-04-08 17:02:43 fréquence.c: 212: get_sale_hash_rate_GH: sale_hash_rate = 53000

show and it reboots in  under 30 seconds or a minute?

I had a miner  that would go all the way until  mining then would reboot.

I took away 1 board and issue ended.

[mikeywith]

[...]

Your pool settings are bad, take a screenshot of your pool settings and status page, check for an extra space in the pool url or worker details, use more than one pool (try to fill the 3 of them) for an example.

1- slushpool
2-cksolo
3-viabtc

Hardware wise everything seems ok, so that is good news.

[philipma1957]

some pools may have issues and not accept the miner.

solo.ckpool.org should work. you can put it in three times with different address you control.

[mysticbitcoin]

Just to do a follow up. This machine is now working fine. Thanks for the help.

[mikeywith]

Just to do a follow up. This machine is now working fine. Thanks for the help.

I am sure everyone here appreciates the follow-up since 90% of people just get what they want and never post again, but honestly, saying the machine now works fine without any details on what was the problem and how was it fixed adds nothing to the community, you had a few of the finest members in the mining board trying to help you, and I assume everyone wants to see more details, so kindly let us know what was the problem and the solution.

Thanks.

[mysticbitcoin]

Right,
Sorry about that. So my initially issue was that the S17Pro was run on 120V by the Previous Owner (PO). This caused the machine not to initialize and I could not get it to hash. At the end of the day, the configuration was wrong on the Miner Setup section as Mikeywith has indicated and it was not hashing due to the improper configuration. It has been hashing ever since without issue. I'd like to thank everyone for their help. This forum is awesome and the people on here (the old timers) really know their stuff. Thanks Mikeywith & philipma1957!

In my case the previous owner supposedly had it running on 120V. I had figured that there was damage done, but since it is a lower voltage no damage occurred. The next issue I had, since it was being properly powered 240V was that the configuration on the miner Settings was incorrect or the pool was not accepting the miner. I have it currently running without issue with ViaBTC, Ckpool, and tried a few others.

[MoparMiningLLC]

glad to hear it is fine and working. luckily the psu did not get damaged trying to power the miner with lower voltage. lower voltages will not hurt the miner but I believe it can hurt the psu.