ironside444 (OP)
Newbie
Offline
Activity: 21
Merit: 6
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2020, 05:16:01 PM Last edit: June 20, 2020, 02:04:54 AM by frodocooper |
|
Can anyone suggest anything to help here?
1. After around 20-30 mins of mining, I get a message of No data (in chinese) and it stops mining for about 10 minutes. Then starts up again and continues mining. Wondering whether it's a BT thing...
2. Of the 3 chains on the reporting page, the first one doesn't appear to have any hashing rate. The asic status is ok and all the other figures. The PCB temp is 51, the chip temp is 71 and the frequency is 555 compared to the other 2 at 585. The fans are all up around 6000rpm.
|
|
|
|
philipma1957
Legendary
Offline
Activity: 4242
Merit: 8460
'The right to privacy matters'
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2020, 05:38:27 PM Last edit: June 20, 2020, 02:16:52 AM by frodocooper |
|
copy the logs and paste them here in code format
|
|
|
|
ironside444 (OP)
Newbie
Offline
Activity: 21
Merit: 6
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2020, 10:17:15 PM |
|
This is the initial state before the clock sets: 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: 203620K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25756K 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: 12716K (cce95000 - cdb00000) 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: 15/7, WL threshold: 4096, image sequence number: 2419912869 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 1303F5C2-F3EF-4059-9B98-C469B28B1788, 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: 4/1, WL threshold: 4096, image sequence number: 2324953515 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 8C5051EC-2BDF-4773-B69A-558999E9CEC7, 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 macb e000b000.ethernet eth0: link down macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz macb e000b000.ethernet eth0: link up (100/Full) 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 macb e000b000.ethernet eth0: link down macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz macb e000b000.ethernet eth0: link up (100/Full) random: nonblocking pool is initialized 1970-01-01 00:05:16 driver-btm-api.c:515:init_freq_mode: This is scan-user version 1970-01-01 00:05:16 driver-btm-api.c:1871:bitmain_soc_init: opt_multi_version = 1 1970-01-01 00:05:16 driver-btm-api.c:1872:bitmain_soc_init: opt_bitmain_ab = 1 1970-01-01 00:05:16 driver-btm-api.c:1873:bitmain_soc_init: opt_bitmain_work_mode = 2 1970-01-01 00:05:16 driver-btm-api.c:1874:bitmain_soc_init: Miner compile time: Wed Dec 25 09:45:06 CST 2019 type: Antminer S17 1970-01-01 00:05:16 driver-btm-api.c:1875:bitmain_soc_init: commit version: b1e11d0 2019-12-24 22:26:20, build by: lol 2019-12-25 09:54:26 1970-01-01 00:05:16 driver-btm-api.c:1664:show_sn: no SN got, please write SN to /nvdata/sn 1970-01-01 00:05:16 driver-btm-api.c:1013:miner_device_init: Detect 256MB control board of XILINX 1970-01-01 00:05:16 driver-btm-api.c:961:init_fan_parameter: fan_eft : 0 fan_pwm : 0 1970-01-01 00:05:22 driver-btm-api.c:945:init_miner_version: miner ID : 800864467910481c 1970-01-01 00:05:22 driver-btm-api.c:951:init_miner_version: FPGA Version = 0xB013 1970-01-01 00:05:27 thread.c:699:create_read_nonce_reg_thread: create thread 1970-01-01 00:05:27 driver-btm-api.c:589:get_product_id: product_id[0] = 0 1970-01-01 00:05:27 driver-btm-api.c:589:get_product_id: product_id[1] = 0 1970-01-01 00:05:27 driver-btm-api.c:589:get_product_id: product_id[2] = 0 1970-01-01 00:05:27 driver-btm-api.c:533:_set_project_type: project:1 1970-01-01 00:05:27 driver-btm-api.c:558:_set_project_type: Project type: Antminer S17 1970-01-01 00:05:27 driver-btm-api.c:569:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101 1970-01-01 00:05:27 driver-btm-api.c:570:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103 1970-01-01 00:05:27 driver-btm-api.c:569:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101 1970-01-01 00:05:27 driver-btm-api.c:570:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103 1970-01-01 00:05:27 driver-btm-api.c:569:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101 1970-01-01 00:05:27 driver-btm-api.c:570:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103 1970-01-01 00:05:28 driver-btm-api.c:1785:bitmain_board_init: Fan check passed. 1970-01-01 00:05:29 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app 1970-01-01 00:05:31 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9 1970-01-01 00:05:33 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app 1970-01-01 00:05:35 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9 1970-01-01 00:05:36 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app 1970-01-01 00:05:38 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9 1970-01-01 00:05:38 thread.c:694:create_pic_heart_beat_thread: create thread 1970-01-01 00:05:38 power_api.c:207:power_init: Power init: 1970-01-01 00:05:38 power_api.c:208:power_init: current_voltage_raw = 0 1970-01-01 00:05:38 power_api.c:209:power_init: highest_voltage_raw = 2100 1970-01-01 00:05:38 power_api.c:210:power_init: working_voltage_raw = 1830 1970-01-01 00:05:38 power_api.c:211:power_init: higher_voltage_raw = 1950 1970-01-01 00:05:38 driver-btm-api.c:1795:bitmain_board_init: Enter 30s sleep to make sure power release finish. 1970-01-01 00:06:10 power_api.c:251:set_to_highest_voltage: Set to voltage raw 2100, one step. 1970-01-01 00:06:12 power_api.c:87:check_voltage_multi: retry time: 0 1970-01-01 00:06:13 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 21.020420 1970-01-01 00:06:14 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.057158 1970-01-01 00:06:15 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 21.032666 1970-01-01 00:06:15 power_api.c:50:_get_avg_voltage: average_voltage = 21.036748 1970-01-01 00:06:15 power_api.c:68:check_voltage: target_vol = 21.00, actural_vol = 21.04, check voltage passed. 1970-01-01 00:06:15 uart.c:71:set_baud: set fpga_baud to 115200 1970-01-01 00:06:15 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26 1970-01-01 00:06:15 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26 1970-01-01 00:06:15 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26 1970-01-01 00:06:26 driver-btm-api.c:888:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0 1970-01-01 00:06:37 driver-btm-api.c:888:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0 1970-01-01 00:06:48 driver-btm-api.c:888:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0 1970-01-01 00:06:53 driver-btm-api.c:344:set_order_clock: chain[0]: set order clock, stragegy 3 1970-01-01 00:06:54 driver-btm-api.c:344:set_order_clock: chain[1]: set order clock, stragegy 3 1970-01-01 00:06:54 driver-btm-api.c:344:set_order_clock: chain[2]: set order clock, stragegy 3 1970-01-01 00:06:54 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34 1970-01-01 00:06:54 uart.c:71:set_baud: set fpga_baud to 3000000 1970-01-01 00:06:54 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0 1970-01-01 00:06:54 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0 1970-01-01 00:06:54 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0 1970-01-01 00:06:54 driver-btm-api.c:1547:check_clock_counter: freq 50 clock_counter_limit 6 1970-01-01 00:06:56 driver-btm-api.c:1537:clear_bad_clock_mark: clock counter check pass. 1970-01-01 00:06:56 uart.c:71:set_baud: set fpga_baud to 115200 1970-01-01 00:06:56 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26 1970-01-01 00:06:56 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26 1970-01-01 00:06:56 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26 1970-01-01 00:06:56 voltage[0] = 1820 1970-01-01 00:06:56 voltage[1] = 1820 1970-01-01 00:06:56 voltage[2] = 1820 1970-01-01 00:06:56 power_api.c:219:set_working_voltage_raw: working_voltage_raw = 1820 1970-01-01 00:06:57 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success. 1970-01-01 00:06:59 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success. 1970-01-01 00:07:00 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success. 1970-01-01 00:07:00 uart.c:71:set_baud: set fpga_baud to 6000000 1970-01-01 00:07:00 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7 1970-01-01 00:07:00 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7 1970-01-01 00:07:00 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7 1970-01-01 00:07:02 driver-btm-api.c:244:check_bringup_temp: Bring up temperature is 18 1970-01-01 00:07:02 thread.c:714:create_check_miner_status_thread: create thread 1970-01-01 00:07:02 thread.c:704:create_set_miner_status_thread: create thread 1970-01-01 00:07:02 thread.c:689:create_temperature_monitor_thread: create thread 1970-01-01 00:07:02 freq_tuning.c:195:freq_tuning_get_max_freq: Max freq of tuning is 780 1970-01-01 00:07:02 frequency.c:711:inc_freq_with_fixed_vco: chain = 255, freq = 555, is_higher_voltage = true 1970-01-01 00:07:02 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 2020, step by step. 1970-01-01 00:07:20 power_api.c:87:check_voltage_multi: retry time: 0 1970-01-01 00:07:21 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 20.193808 1970-01-01 00:07:22 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 20.224424 1970-01-01 00:07:23 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 20.212177 1970-01-01 00:07:23 power_api.c:50:_get_avg_voltage: average_voltage = 20.210136 1970-01-01 00:07:23 power_api.c:68:check_voltage: target_vol = 20.20, actural_vol = 20.21, check voltage passed. 1970-01-01 00:07:32 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 1970-01-01 00:07:46 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 1970-01-01 00:07:52 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 1970-01-01 00:08:05 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 1970-01-01 00:08:12 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 1970-01-01 00:08:25 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 1970-01-01 00:08:31 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 1970-01-01 00:08:45 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 1970-01-01 00:08:53 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 1970-01-01 00:09:06 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 1970-01-01 00:09:13 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 1970-01-01 00:09:26 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 1970-01-01 00:09:33 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 1970-01-01 00:09:36 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1900, step by step. 1970-01-01 00:09:46 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 1970-01-01 00:09:52 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 1970-01-01 00:09:54 power_api.c:87:check_voltage_multi: retry time: 0 1970-01-01 00:09:55 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 18.981445 1970-01-01 00:09:56 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 19.048799 1970-01-01 00:09:58 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 18.987568 1970-01-01 00:09:58 power_api.c:50:_get_avg_voltage: average_voltage = 19.005937 1970-01-01 00:09:58 power_api.c:68:check_voltage: target_vol = 19.00, actural_vol = 19.01, check voltage passed. 1970-01-01 00:10:05 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 1970-01-01 00:10:14 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 1970-01-01 00:10:27 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 1970-01-01 00:10:31 frequency.c:761:inc_freq_with_fixed_step: chain = 1, freq_start = 555, freq_end = 585, freq_step = 5, is_higher_voltage = true 1970-01-01 00:10:31 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1880, step by step. 1970-01-01 00:10:34 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 1970-01-01 00:10:47 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 1970-01-01 00:10:49 power_api.c:87:check_voltage_multi: retry time: 0 1970-01-01 00:10:50 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 18.822246 1970-01-01 00:10:51 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 18.858984 1970-01-01 00:10:52 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 18.803877 1970-01-01 00:10:52 power_api.c:50:_get_avg_voltage: average_voltage = 18.828369 1970-01-01 00:10:52 power_api.c:68:check_voltage: target_vol = 18.80, actural_vol = 18.83, check voltage passed. 1970-01-01 00:10:53 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 1970-01-01 00:10:55 frequency.c:761:inc_freq_with_fixed_step: chain = 2, freq_start = 555, freq_end = 585, freq_step = 5, is_higher_voltage = true 1970-01-01 00:10:58 frequency.c:761:inc_freq_with_fixed_step: chain = 1, freq_start = 585, freq_end = 585, freq_step = 5, is_higher_voltage = true 1970-01-01 00:10:58 frequency.c:761:inc_freq_with_fixed_step: chain = 2, freq_start = 585, freq_end = 585, freq_step = 5, is_higher_voltage = true 1970-01-01 00:10:58 driver-btm-api.c:501:set_timeout: freq = 585, percent = 90, hcn = 73728, timeout = 126 1970-01-01 00:10:58 power_api.c:225:set_higher_voltage_raw: higher_voltage_raw = 1900 1970-01-01 00:10:58 power_api.c:281:set_to_higher_voltage_by_steps: Set to voltage raw 1900, step by step. 1970-01-01 00:11:06 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 1970-01-01 00:11:13 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 1970-01-01 00:11:16 power_api.c:87:check_voltage_multi: retry time: 0 1970-01-01 00:11:17 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 18.975322 1970-01-01 00:11:18 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 19.042676 1970-01-01 00:11:19 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 18.993691 1970-01-01 00:11:19 power_api.c:50:_get_avg_voltage: average_voltage = 19.003896 1970-01-01 00:11:19 power_api.c:68:check_voltage: target_vol = 19.00, actural_vol = 19.00, check voltage passed. 1970-01-01 00:11:19 thread.c:709:create_check_system_status_thread: create thread 1970-01-01 00:11:20 driver-btm-api.c:1980:bitmain_soc_init: Init done! 1970-01-01 00:11:20 driver-btm-api.c:197:set_miner_status: STATUS_INIT 1970-01-01 00:11:25 driver-btm-api.c:197:set_miner_status: STATUS_OKAY 1970-01-01 00:11:26 frequency.c:196:get_ideal_hash_rate_GH: ideal_hash_rate = 55249 1970-01-01 00:11:26 frequency.c:212:get_sale_hash_rate_GH: sale_hash_rate = 53000 1970-01-01 00:11:26 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 1970-01-01 00:11:30 driver-btm-api.c:1172:dhash_chip_send_job: Version num 4 1970-01-01 00:11:35 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 1970-01-01 00:11:48 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 1970-01-01 00:11:54 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 1970-01-01 00:12:07 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 1970-01-01 00:12:14 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 1970-01-01 00:12:27 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 1970-01-01 00:12:34 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 1970-01-01 00:12:47 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 1970-01-01 00:12:55 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 1970-01-01 00:13:09 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 1970-01-01 00:13:15 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 1970-01-01 00:13:28 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 1970-01-01 00:13:35 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 1970-01-01 00:13:48 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 1970-01-01 00:13:54 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 1970-01-01 00:14:08 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 1970-01-01 00:14:16 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 1970-01-01 00:14:29 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 1970-01-01 00:14:36 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 1970-01-01 00:14:49 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 1970-01-01 00:14:56 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 1970-01-01 00:15:09 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 1970-01-01 00:15:15 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 1970-01-01 00:15:28 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 1970-01-01 00:15:37 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 1970-01-01 00:15:50 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 1970-01-01 00:15:57 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 1970-01-01 00:16:10 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 1970-01-01 00:16:16 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 1970-01-01 00:16:29 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 1970-01-01 00:16:36 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 1970-01-01 00:16:49 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 1970-01-01 00:16:58 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 1970-01-01 00:17:11 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 1970-01-01 00:17:17 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 1970-01-01 00:17:30 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 1970-01-01 00:17:37 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 1970-01-01 00:17:50 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 1970-01-01 00:17:57 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0
|
|
|
|
PopoJeff
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2020, 10:26:19 PM Last edit: June 20, 2020, 02:19:03 AM by frodocooper |
|
Looks like ANOTHER case of the dreaded Temp sensor error. temperature.c:695:get_temp_info: read temp sensor failed Check here for more information. Very common: https://bitcointalk.org/index.php?topic=5244120.0.
|
Home garage miner: (3) S19j pro
|
|
|
ironside444 (OP)
Newbie
Offline
Activity: 21
Merit: 6
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2020, 10:31:12 PM |
|
And this is after. The hashrate dropped to zero in this section. 2020-06-19 21:44:43 driver-btm-api.c:197:set_miner_status: WARN_NET_LOST 2020-06-19 21:44:44 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 21:44:52 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 21:44:58 log.c:100:_log_update_name: _log_update_name 2020-06-19 21:44:58 log.c:100:_log_update_name: _log_update_name 2020-06-19 21:45:05 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 21:45:12 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 21:45:13 driver-btm-api.c:197:set_miner_status: STATUS_OKAY 2020-06-19 21:45:25 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 21:45:32 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 21:45:45 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 21:45:51 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 21:46:04 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 21:46:13 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 21:46:26 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 21:46:33 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 21:46:46 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 21:46:52 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 21:47:06 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 21:47:12 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 21:47:25 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 21:47:34 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 21:47:47 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 21:47:54 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 21:48:07 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 21:48:13 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 21:48:26 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 21:48:33 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 21:48:46 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 21:48:55 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 21:49:08 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 21:49:14 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 21:49:27 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 21:49:34 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 21:49:47 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 21:49:54 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 21:50:07 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 21:50:15 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 21:50:28 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 21:50:35 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 21:50:48 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 21:50:55 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 21:51:08 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 21:51:14 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 21:51:27 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 21:51:36 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 21:51:49 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 21:51:56 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 21:52:09 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 21:52:15 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 21:52:28 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 21:52:35 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 21:52:48 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 21:52:57 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 21:53:10 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 21:53:16 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 21:53:29 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 21:53:36 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 21:53:49 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 21:53:56 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 21:54:09 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 21:54:17 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 21:54:31 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 21:54:37 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 21:54:50 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 21:54:57 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 21:55:10 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 21:55:16 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 21:55:30 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 21:55:38 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 21:55:51 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 21:55:58 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 21:56:11 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 21:56:18 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 21:56:31 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 21:56:37 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 21:56:50 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 21:56:59 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 21:57:12 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 21:57:19 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 21:57:32 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 21:57:38 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 21:57:51 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 21:57:58 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 21:58:11 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 21:58:20 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 21:58:33 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 21:58:39 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 21:58:52 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 21:58:59 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 21:59:12 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 21:59:19 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 21:59:32 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 21:59:40 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 21:59:54 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 22:00:00 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 22:00:13 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 22:00:20 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 22:00:33 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 22:00:39 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 22:00:53 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 22:01:01 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 22:01:14 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 22:01:21 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 22:01:34 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 22:01:40 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 22:01:53 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 22:02:00 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 22:02:13 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 22:02:22 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 22:02:35 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 22:02:41 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 22:02:54 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 22:03:01 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 22:03:14 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 22:03:21 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 22:03:34 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 22:03:42 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 22:03:55 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 22:04:02 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 22:04:15 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 22:04:22 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 22:04:35 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 22:04:41 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 22:04:54 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 22:05:03 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 22:05:16 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 22:05:23 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 22:05:36 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 22:05:42 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 22:05:55 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 22:06:02 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 22:06:15 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 22:06:24 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 22:06:37 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 22:06:43 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 22:06:56 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 22:07:03 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 22:07:16 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 22:07:23 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 22:07:36 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 22:07:44 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-06-19 22:07:58 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 2020-06-19 22:08:04 thread.c:221:calc_hashrate_avg: avg rate is 37667.44 in 30 mins 2020-06-19 22:08:04 temperature.c:449:temp_statistics_show: pcb temp 32~50 chip temp 55~69 2020-06-19 22:08:04 thread.c:302:check_hashrate: latest avg rate < 0.98...... 2020-06-19 22:08:04 thread.c:303:check_hashrate: current PCB min temperature 32 2020-06-19 22:08:04 thread.c:304:check_hashrate: current voltage raw is 1900, working voltage raw is 1820 2020-06-19 22:08:04 thread.c:335:check_hashrate: high temp, increase voltage 0.1V/0.2V to 1910 2020-06-19 22:08:04 driver-btm-api.c:1996:bitmain_reopen_core: reopen_core start! 2020-06-19 22:08:04 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0 2020-06-19 22:08:17 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-06-19 22:08:24 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-06-19 22:08:37 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 2020-06-19 22:08:43 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0 2020-06-19 22:08:57 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 2020-06-19 22:09:04 driver-btm-api.c:945:init_miner_version: miner ID : 800864467910481c 2020-06-19 22:09:04 driver-btm-api.c:951:init_miner_version: FPGA Version = 0xB013 2020-06-19 22:09:09 driver-btm-api.c:589:get_product_id: product_id[0] = 0 2020-06-19 22:09:09 driver-btm-api.c:589:get_product_id: product_id[1] = 0 2020-06-19 22:09:09 driver-btm-api.c:589:get_product_id: product_id[2] = 0 2020-06-19 22:09:09 driver-btm-api.c:533:_set_project_type: project:1 2020-06-19 22:09:09 driver-btm-api.c:558:_set_project_type: Project type: Antminer S17 2020-06-19 22:09:09 driver-btm-api.c:569:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101 2020-06-19 22:09:09 driver-btm-api.c:570:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103 2020-06-19 22:09:09 driver-btm-api.c:569:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101 2020-06-19 22:09:09 driver-btm-api.c:570:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103 2020-06-19 22:09:09 driver-btm-api.c:569:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101 2020-06-19 22:09:09 driver-btm-api.c:570:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103 2020-06-19 22:09:10 driver-btm-api.c:1785:bitmain_board_init: Fan check passed. 2020-06-19 22:09:11 register.c:283:get_register: !!! reg crc error 2020-06-19 22:09:12 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app 2020-06-19 22:09:14 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9 2020-06-19 22:09:15 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app 2020-06-19 22:09:17 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9 2020-06-19 22:09:18 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app 2020-06-19 22:09:20 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9 2020-06-19 22:09:20 power_api.c:207:power_init: Power init: 2020-06-19 22:09:20 power_api.c:208:power_init: current_voltage_raw = 0 2020-06-19 22:09:20 power_api.c:209:power_init: highest_voltage_raw = 2100 2020-06-19 22:09:20 power_api.c:210:power_init: working_voltage_raw = 1830 2020-06-19 22:09:20 power_api.c:211:power_init: higher_voltage_raw = 1950 2020-06-19 22:09:20 driver-btm-api.c:1795:bitmain_board_init: Enter 30s sleep to make sure power release finish. 2020-06-19 22:09:52 power_api.c:251:set_to_highest_voltage: Set to voltage raw 2100, one step. 2020-06-19 22:09:54 power_api.c:87:check_voltage_multi: retry time: 0 2020-06-19 22:09:55 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 21.063281 2020-06-19 22:09:56 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.069404 2020-06-19 22:09:57 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 21.044912 2020-06-19 22:09:57 power_api.c:50:_get_avg_voltage: average_voltage = 21.059199 2020-06-19 22:09:57 power_api.c:68:check_voltage: target_vol = 21.00, actural_vol = 21.06, check voltage passed. 2020-06-19 22:09:57 uart.c:71:set_baud: set fpga_baud to 115200 2020-06-19 22:09:57 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26 2020-06-19 22:09:57 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26 2020-06-19 22:09:57 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26 2020-06-19 22:10:09 driver-btm-api.c:888:check_asic_number_with_power_on: Chain[0]: find 47 asic, times 0 2020-06-19 22:10:20 driver-btm-api.c:888:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 1 2020-06-19 22:10:31 driver-btm-api.c:888:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0 2020-06-19 22:10:42 driver-btm-api.c:888:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0 2020-06-19 22:10:47 driver-btm-api.c:344:set_order_clock: chain[0]: set order clock, stragegy 3 2020-06-19 22:10:47 driver-btm-api.c:344:set_order_clock: chain[1]: set order clock, stragegy 3 2020-06-19 22:10:47 driver-btm-api.c:344:set_order_clock: chain[2]: set order clock, stragegy 3 2020-06-19 22:10:47 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34 2020-06-19 22:10:47 uart.c:71:set_baud: set fpga_baud to 3000000 2020-06-19 22:10:47 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0 2020-06-19 22:10:47 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0 2020-06-19 22:10:47 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0 2020-06-19 22:10:47 driver-btm-api.c:1547:check_clock_counter: freq 50 clock_counter_limit 6 2020-06-19 22:10:49 uart.c:71:set_baud: set fpga_baud to 115200 2020-06-19 22:10:49 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26 2020-06-19 22:10:49 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26 2020-06-19 22:10:49 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26 2020-06-19 22:10:49 voltage[0] = 1820 2020-06-19 22:10:49 voltage[1] = 1820 2020-06-19 22:10:49 voltage[2] = 1820 2020-06-19 22:10:49 power_api.c:219:set_working_voltage_raw: working_voltage_raw = 1820 2020-06-19 22:10:50 frequency.c:196:get_ideal_hash_rate_GH: ideal_hash_rate = 55249 2020-06-19 22:10:50 frequency.c:212:get_sale_hash_rate_GH: sale_hash_rate = 53000 2020-06-19 22:10:51 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success. 2020-06-19 22:10:52 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success. 2020-06-19 22:10:53 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success. 2020-06-19 22:10:53 uart.c:71:set_baud: set fpga_baud to 6000000 2020-06-19 22:10:53 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7 2020-06-19 22:10:53 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7 2020-06-19 22:10:53 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7 2020-06-19 22:10:55 driver-btm-api.c:244:check_bringup_temp: Bring up temperature is 23 2020-06-19 22:10:55 frequency.c:711:inc_freq_with_fixed_vco: chain = 255, freq = 555, is_higher_voltage = true 2020-06-19 22:10:55 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 2020, step by step. 2020-06-19 22:11:14 power_api.c:87:check_voltage_multi: retry time: 0 2020-06-19 22:11:15 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 20.218301 2020-06-19 22:11:16 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 20.255039 2020-06-19 22:11:17 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 20.212177 2020-06-19 22:11:17 power_api.c:50:_get_avg_voltage: average_voltage = 20.228506 2020-06-19 22:11:17 power_api.c:68:check_voltage: target_vol = 20.20, actural_vol = 20.23, check voltage passed.
|
|
|
|
mikeywith
Legendary
Online
Activity: 2352
Merit: 6511
be constructive or S.T.F.U
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2020, 10:39:27 PM Last edit: June 20, 2020, 02:20:05 AM by frodocooper |
|
Could be a network issue, try a different ethernet cable, and also reset the miner and flash the latest firmware, you should also include the kernel for this miner. I suppose the kernel log is for this miner, judging by the temp sensor error on chain 0 1970-01-01 00:17:11 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1 1970-01-01 00:17:30 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 1970-01-01 00:17:50 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1 1970-01-01 00:17:57 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0
Each hashboard has 4 PCB sensors labeled 0,1,2,3, after a lot of research, help, and testing we have come to realize that this issue is not caused by the temp sensors themselves but rather bad soldering on one or more of the heatsinks/chips, to fix this you will need to firstly identify the bad chip/heatsink by taking the board out and physically inspect it if there are no signs of anything you will need to use a multimeter like a "fluke" or buy a fixture tool to know which chip/heatsink needs soldering, and then, of course, you will need to have the right sets of tools and skills. When the miner fails to sense pcb temps from that board, after a certain time it will simply disable it and hash with the two other boards, there is a tiny little chance that by flashing another firmware this board might come back to life, give it a shot but if it doesn't work, you probably want to disconnect it as it does slow the start-up process, also follow the topic posted above by popojeff for more details.
|
|
|
|
ironside444 (OP)
Newbie
Offline
Activity: 21
Merit: 6
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 20, 2020, 09:15:24 PM Last edit: June 22, 2020, 12:33:54 AM by frodocooper |
|
[...]
Thanks, will check it out.
This may well be another stupid question, but I downloaded what I think is the firmware for the S17 and put it on a microSD card. I put it in and switched it on, but all I get is the two lights steadily on. Which is the right one to flash the firmware? Maybe I'm using the wrong one. The instructions on the Bitmain site are not helpful.
|
|
|
|
philipma1957
Legendary
Offline
Activity: 4242
Merit: 8460
'The right to privacy matters'
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 20, 2020, 10:01:31 PM Last edit: June 22, 2020, 12:34:48 AM by frodocooper |
|
you may need to pull the controller and shift some jumpers. you have to do it on s9 controllers I have a youtube video that shows how to move the pins: this is an s9 controller https://www.youtube.com/watch?v=U-tLR6sEVQsi lifted this shot from my video above. I have a blue square around a chip and just to the right are the jumpers I mention. This is for an s9. hoping some one will mention a s17 controller ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2Ff0hsmeO.png&t=665&c=r9z_kkwz4sW9Aw)
|
|
|
|
mikeywith
Legendary
Online
Activity: 2352
Merit: 6511
be constructive or S.T.F.U
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 20, 2020, 11:08:23 PM Last edit: June 22, 2020, 12:35:26 AM by frodocooper Merited by philipma1957 (2), BitMaxz (1) |
|
This may well be another stupid question, but I downloaded what I think is the firmware for the S17 and put it on a microSD card. I put it in and switched it on, but all I get is the two lights steadily on.
Which is the right one to flash the firmware? Maybe I'm using the wrong one. The instructions on the Bitmain site are not helpful.
That's because you are doing it wrong, you don't put a flashable firmware on an Sdcard and expect it to work! you need the special recovery files on that Sdcard which you probably don't have, how do I know you don't have it? simply because it's not available for download on Bitmain's website. You can download the recovery files from this link thanks to taserz for uploading them, follow the guide from bitmain, it's rather simple, if you have any questions feel free to ask. you may need to pull the controller and shift some jumpers.
The 17 series have no jumper on them, the moment you put in an Sdcard it starts to boot from the Sdcard, the 17 series are nothing like those T9 and S9 , in fact, even the S9e and S9k are different and don't have the jumper.
|
|
|
|
ironside444 (OP)
Newbie
Offline
Activity: 21
Merit: 6
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 21, 2020, 12:57:00 PM |
|
Thanks for your patience ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) I realise that I'm probably asking questions that will make people want to pull their hair out. Once I get it, I'll be able to just leave it running. I've downloaded those files, and there are 3 sets. My miner is an S17-53T so I'm not sure which of these to use, as they don't match the filename precisely?
|
|
|
|
favebook
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 21, 2020, 04:49:07 PM Last edit: June 22, 2020, 07:57:11 AM by favebook Merited by frodocooper (2), mikeywith (1) |
|
SD_S17+ should be only for S17+ (not sure if it is for T17+ too) *As mikeywith noted (check message below), there could be a separate T17+ one. Never had T17/T17+ in my hands so I wouldn't know as I have never used one, better to ask Taserz. SD-X17 should be for any S17 and S17 Pro. And T17 should be for T17 only (not sure if it is for T17+ too).
|
|
|
|
mikeywith
Legendary
Online
Activity: 2352
Merit: 6511
be constructive or S.T.F.U
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 21, 2020, 06:33:44 PM Last edit: June 22, 2020, 12:37:19 AM by frodocooper |
|
I've downloaded those files, and there are 3 sets. My miner is an S17-53T so I'm not sure which of these to use, as they don't match the filename precisely?
TH rating doesn't matter, for S17 you must use SD-X17, of course you need to unzip it and copy the content inside it, follow the instructions on bitmain's website. SD_S17+ (not sure if it is for T17+ too).
Possible, but I have seen a T17+ recovery files that are different from the S17+. And T17 (not sure if it is for T17+ too).
absolutely not, the T17 and T17+ use a completely different control board, since the recovery firmware is MP_test which you later need to flash to the appropriate firmware I think that S17e,T17e,S17+, and T17+ > could use the same files. T17, S17, and S17 pro > could use the same files.
|
|
|
|
favebook
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 22, 2020, 08:04:08 AM Last edit: June 23, 2020, 02:25:05 AM by frodocooper |
|
Possible, but I have seen a T17+ recovery files that are different from the S17+.
Could be, will have to check with Taserz. absolutely not, the T17 and T17+ use a completely different control board, since the recovery firmware is MP_test which you later need to flash to the appropriate firmware I think that
S17e,T17e,S17+, and T17+ > could use the same files. T17, S17, and S17 pro > could use the same files.
You are totally correct, T17 and T17+ are different files. Also, I think T17 are different from S17 and S17 Pro, but I am not sure about this either. What I am almost sure of is that S/T17e are different than S/T17+ in files but they do actually use same control board: https://shop.bitmain.com/product/detail?pid=000201912301516442301jqzV9Ep06B6
|
|
|
|
mikeywith
Legendary
Online
Activity: 2352
Merit: 6511
be constructive or S.T.F.U
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 22, 2020, 04:38:37 PM |
|
Also, I think T17 are different from S17 and S17 Pro, but I am not sure about this either.
I am pretty sure that T17,S17 ad S17 pro can use the same recovery files, you can take my words for it, as far as the E and + versions of both S17 and T17 I am not 100% certain of how they differ in terms of firmware, the reason why I initially thought that all the E and + versions could use the same the recovery files is because when you order a new control board from Bitmain labeled with (S17+,T17+,T17e,S17e) it comes with the MP Test firmware, and then whichever firmware you flash on it, it will accept it, Bitmain doesn't know which mining gear out of those 4 you have, and the recovery files all have the MP test firmware so I still think it will work, unless someone trusted like yourself, phill, thierry4wd or taserz tell me that they have tried E files on + files or vice versa and it didn't work.
|
|
|
|
ironside444 (OP)
Newbie
Offline
Activity: 21
Merit: 6
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 23, 2020, 11:22:00 AM |
|
Thanks for all the help on my problems. I took the boards out and pushed in the heatsinks etc. Worked beautifully! All working at 100% now.
|
|
|
|
mikeywith
Legendary
Online
Activity: 2352
Merit: 6511
be constructive or S.T.F.U
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 23, 2020, 09:58:27 PM Last edit: June 25, 2020, 08:08:41 PM by mikeywith Merited by philipma1957 (1) |
|
Thanks for all the help on my problems. I took the boards out and pushed in the heatsinks etc. Worked beautifully! All working at 100% now.
I believe you learned this trick from me ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) , you are welcome ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) , just kidding, I am glad that more and more people are getting to prove that what most people think of as a stupid way of fixing things actually works sometimes, I got laughed at by someone about this trick and most people think it's so stupid they won't even try it, on the other hand, many people reported great results with simple physical pressure applied on the heatsinks, the bad news, of course, they won't last for too long, but you can always try to revive them using the same method until there is no more hope.
|
|
|
|
ironside444 (OP)
Newbie
Offline
Activity: 21
Merit: 6
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 25, 2020, 03:19:47 PM Last edit: June 26, 2020, 12:31:32 AM by frodocooper |
|
I absolutely did get that trick from you ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) It was one of the very few things I could do myself to try to solve the problem, without sending it to someone else. I am really grateful for the help!!
|
|
|
|
NotFuzzyWarm
Legendary
Offline
Activity: 3738
Merit: 2666
Evil beware: We have waffles!
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 25, 2020, 03:26:55 PM Last edit: June 25, 2020, 05:08:25 PM by NotFuzzyWarm |
|
^^ rather sounds like a case of very iffy solder joints on the chips. As someone else said here earlier on, BM needs to take a hard look at the materials (solder & flux used) & process temp profiles they are using to eliminate the cause of this problem.
|
|
|
|
CryptoLLC
Newbie
Offline
Activity: 25
Merit: 11
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 24, 2020, 05:06:54 AM |
|
Im getting this same exact problem. None of my heat sinks came off. How do I find the bad heat sink? What do I check for? What pin? Please let me know in detail if you can. Im in real need to get my boards fixed. Any help is appreciated. Thank you.
|
|
|
|
mikeywith
Legendary
Online
Activity: 2352
Merit: 6511
be constructive or S.T.F.U
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 24, 2020, 10:35:10 AM Last edit: November 24, 2020, 11:19:45 PM by frodocooper |
|
The heatsink does NOT have to come off to be declared "bad", if it's not perfectly connected then it won't work, in most cases, it's not something you see with your bare eyes. You need to check for " CLK-CO-RI-BO-RST" points, Zeusbtc has fix manuals for most of the 17 series, what model are you having issues with?
|
|
|
|
|