Bitcoin Forum
November 18, 2024, 12:39:11 PM *
News: Check out the artwork 1Dq created to commemorate this forum's 15th anniversary
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: t17+ killall_hashboard: *power off hashboard  (Read 187 times)
freakky (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
August 06, 2022, 09:14:41 AM
 #1

hello I have problems with my t17+ I can't get it to start mining I leave the kernel log if you can give me a solution thanks




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
  • 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: 203416K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25960K 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: 12920K (cce62000 - 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
nand_read_bbt: bad block at 0x000008000000
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: 9/3, 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: 1019, bad PEBs: 5, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 457/141, WL threshold: 4096, image sequence number: 1751317449
ubi1: available PEBs: 0, total reserved PEBs: 1019, PEBs reserved for bad PEB handling: 35
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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2022-08-02 03:41:33 driver-btm-api.c:762:init_freq_mode: This is scan-user version
2022-08-02 03:41:33 driver-btm-api.c:2553:bitmain_soc_init: opt_multi_version     = 1
2022-08-02 03:41:33 driver-btm-api.c:2554:bitmain_soc_init: opt_bitmain_ab        = 1
2022-08-02 03:41:33 driver-btm-api.c:2555:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-08-02 03:41:33 driver-btm-api.c:2556:bitmain_soc_init: Miner compile time: Tue Jun  2 10:11:10 CST 2020 type: Antminer T17+
2022-08-02 03:41:33 driver-btm-api.c:2557:bitmain_soc_init: commit version: 9e9a5bf 2020-06-01 18:48:14, build by: lol 2020-06-02 10:21:50
2022-08-02 03:41:33 driver-btm-api.c:2180:show_sn: 8028f40c2b104814�7
2022-08-02 03:41:33 driver-btm-api.c:2237:handle_sn_for_factory_mode: read sn success, 8028f40c2b104814�7
2022-08-02 03:41:33 fan.c:263:front_fan_power_on: Note: front fan is power on!
2022-08-02 03:41:33 fan.c:273:rear_fan_power_on: Note: rear fan is power on!
2022-08-02 03:41:33 driver-btm-api.c:1357:miner_device_init: Detect 256MB control board of XILINX
2022-08-02 03:41:33 driver-btm-api.c:1298:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2022-08-02 03:41:39 driver-btm-api.c:1281:init_miner_version: miner ID : 8028f40c2b104814
2022-08-02 03:41:39 driver-btm-api.c:1287:init_miner_version: FPGA Version = 0xB023
2022-08-02 03:41:44 driver-btm-api.c:814:get_product_id: product_id[1] = 0
2022-08-02 03:41:44 driver-btm-api.c:814:get_product_id: product_id[2] = 0
2022-08-02 03:41:44 driver-btm-api.c:814:get_product_id: product_id[3] = 0
2022-08-02 03:41:44 driver-btm-api.c:845:get_chip_version: chip_version[1] = 1
2022-08-02 03:41:44 driver-btm-api.c:845:get_chip_version: chip_version[2] = 1
2022-08-02 03:41:44 driver-btm-api.c:845:get_chip_version: chip_version[3] = 1
2022-08-02 03:41:44 driver-btm-api.c:2293:update_conf_by_power_feedback: Power feedback is disabled
2022-08-02 03:41:44 driver-btm-api.c:2261:get_calibration_voltage: calibration voltage flag is error data.
2022-08-02 03:41:44 driver-btm-api.c:2327:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2022-08-02 03:41:44 frequency.c:1389:adjust_higer_max_vol_table: adjust_higer_max_vol_table, ideal_hashrate = 56866, index = 2, adjust_vol = 20
2022-08-02 03:41:44 thread.c:1462:create_read_nonce_reg_thread: create thread
2022-08-02 03:41:50 driver-btm-api.c:1281:init_miner_version: miner ID : 8028f40c2b104814
2022-08-02 03:41:50 driver-btm-api.c:1287:init_miner_version: FPGA Version = 0xB023
2022-08-02 03:41:56 driver-btm-api.c:814:get_product_id: product_id[1] = 0
2022-08-02 03:41:56 driver-btm-api.c:814:get_product_id: product_id[2] = 0
2022-08-02 03:41:56 driver-btm-api.c:814:get_product_id: product_id[3] = 0
2022-08-02 03:41:56 driver-btm-api.c:845:get_chip_version: chip_version[1] = 1
2022-08-02 03:41:56 driver-btm-api.c:845:get_chip_version: chip_version[2] = 1
2022-08-02 03:41:56 driver-btm-api.c:845:get_chip_version: chip_version[3] = 1
2022-08-02 03:41:56 driver-btm-api.c:1944:get_ccdly_opt: ccdly_opt[1] = 0
2022-08-02 03:41:56 driver-btm-api.c:1944:get_ccdly_opt: ccdly_opt[2] = 0
2022-08-02 03:41:56 driver-btm-api.c:1944:get_ccdly_opt: ccdly_opt[3] = 0
2022-08-02 03:41:56 driver-btm-api.c:2439:bitmain_board_init: g_ccdly_opt = 0
2022-08-02 03:41:56 driver-btm-api.c:775:_set_project_type: project:0, set to T17Plus always
2022-08-02 03:41:56 driver-btm-api.c:790:_set_project_type: Project type: Antminer T17+
2022-08-02 03:41:56 driver-btm-api.c:801:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-08-02 03:41:56 driver-btm-api.c:802:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-08-02 03:41:56 driver-btm-api.c:801:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-08-02 03:41:56 driver-btm-api.c:802:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-08-02 03:41:56 driver-btm-api.c:801:dump_pcb_bom_version: Chain [3] PCB Version: 0x0100
2022-08-02 03:41:56 driver-btm-api.c:802:dump_pcb_bom_version: Chain [3] BOM Version: 0x0100
2022-08-02 03:41:57 driver-btm-api.c:2461:bitmain_board_init: Fan check passed.
2022-08-02 03:41:58 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-08-02 03:42:00 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-08-02 03:42:01 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-08-02 03:42:03 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-08-02 03:42:04 board.c:36:jump_and_app_check_restore_pic: chain[3] PIC jump to app
2022-08-02 03:42:06 board.c:40:jump_and_app_check_restore_pic: Check chain[3] PIC fw version=0x88
2022-08-02 03:42:06 thread.c:1457:create_pic_heart_beat_thread: create thread
2022-08-02 03:42:08 power_api.c:231:power_init: power type version: 0x0042
2022-08-02 03:42:08 power_api.c:249:power_init: Power init:
2022-08-02 03:42:08 power_api.c:250:power_init: current_voltage_raw = 0
2022-08-02 03:42:08 power_api.c:251:power_init: highest_voltage_raw = 1950
2022-08-02 03:42:08 power_api.c:252:power_init: working_voltage_raw = 1900
2022-08-02 03:42:08 power_api.c:253:power_init: higher_voltage_raw  = 1930
2022-08-02 03:42:08 power_api.c:254:power_init: check_asic_voltage_raw  = 2000
2022-08-02 03:42:08 driver-btm-api.c:2471:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-08-02 03:42:08 power_api.c:218:power_off: init gpio907
2022-08-02 03:42:08 power_api.c:221:power_off: set gpio907 to 1
2022-08-02 03:42:39 power_api.c:206:power_on: set gpio907 to 0
2022-08-02 03:42:40 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1850, step by step.
2022-08-02 03:42:58 power_api.c:120:check_voltage_multi: retry time: 0
2022-08-02 03:42:59 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2022-08-02 03:42:59 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.487179, an2 18.537180, an6 2.500000.
2022-08-02 03:43:00 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:43:00 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.634146, an2 18.585365, an6 2.500000.
2022-08-02 03:43:01 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:43:01 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.658537, an2 18.585365, an6 2.500000.
2022-08-02 03:43:01 power_api.c:85:_get_avg_voltage: average_voltage = 18.569303
2022-08-02 03:43:01 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.57, check voltage passed.
2022-08-02 03:43:03 power_api.c:56:_get_avg_voltage: an6 raw = 2.519355, factor = 1.007742
2022-08-02 03:43:03 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.486556, an2 18.513444, an6 2.500000.
2022-08-02 03:43:04 power_api.c:56:_get_avg_voltage: an6 raw = 2.509677, factor = 1.003871
2022-08-02 03:43:04 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.610540, an2 18.609255, an6 2.500000.
2022-08-02 03:43:05 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:43:05 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.658537, an2 18.585365, an6 2.500000.
2022-08-02 03:43:05 power_api.c:85:_get_avg_voltage: average_voltage = 18.569354
2022-08-02 03:43:05 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.57, check voltage passed.
2022-08-02 03:43:06 uart.c:81:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-08-02 03:43:14 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[1]: find 10 asic, times 0
2022-08-02 03:43:23 driver-btm-api.c:1163:check_asic_number_with_power_on: Chain[1]: find 10 asic, times 1
2022-08-02 03:43:35 driver-btm-api.c:1164:check_asic_number_with_power_on: Chain[1]: find 10 asic, times 2
2022-08-02 03:43:35 power_api.c:400:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2022-08-02 03:43:52 power_api.c:120:check_voltage_multi: retry time: 0
2022-08-02 03:43:53 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2022-08-02 03:43:53 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.487179, an2 20.023077, an6 2.500000.
2022-08-02 03:43:54 power_api.c:56:_get_avg_voltage: an6 raw = 2.509677, factor = 1.003871
2022-08-02 03:43:54 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.634961, an2 20.098972, an6 2.500000.
2022-08-02 03:43:55 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2022-08-02 03:43:55 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.682051, an2 20.071795, an6 2.500000.
2022-08-02 03:43:55 power_api.c:85:_get_avg_voltage: average_voltage = 20.064615
2022-08-02 03:43:55 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.06, check voltage passed.
2022-08-02 03:43:57 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2022-08-02 03:43:57 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.487179, an2 20.023077, an6 2.500000.
2022-08-02 03:43:58 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:43:58 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.634146, an2 20.073170, an6 2.500000.
2022-08-02 03:43:59 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2022-08-02 03:43:59 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.682051, an2 20.071795, an6 2.500000.
2022-08-02 03:43:59 power_api.c:85:_get_avg_voltage: average_voltage = 20.056014
2022-08-02 03:43:59 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.06, check voltage passed.
2022-08-02 03:44:09 driver-btm-api.c:1167:check_asic_number_with_power_on: Chain[1]: find 10 asic, times 3
2022-08-02 03:44:20 driver-btm-api.c:1168:check_asic_number_with_power_on: Chain[1]: find 10 asic, times 4
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-08-02 03:44:29 driver-btm-api.c:1169:check_asic_number_with_power_on: Chain[1]: find 10 asic, times 5
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-08-02 03:44:38 driver-btm-api.c:1170:check_asic_number_with_power_on: Chain[1]: find 10 asic, times 6
2022-08-02 03:44:38 driver-btm-api.c:1235:check_asic_number: Chain 1 only find 10 asic, will power off hash board 1
2022-08-02 03:44:39 driver-btm-api.c:1238:check_asic_number: Chain 1 voltage: an0 = 20.201290, an2 20.152257, an6 2.519355.
2022-08-02 03:44:40 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1850, step by step.
2022-08-02 03:44:58 power_api.c:120:check_voltage_multi: retry time: 0
2022-08-02 03:44:59 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:44:59 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.634146, an2 18.585365, an6 2.500000.
2022-08-02 03:45:00 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:45:00 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.658537, an2 18.585365, an6 2.500000.
2022-08-02 03:45:00 power_api.c:85:_get_avg_voltage: average_voltage = 18.585365
2022-08-02 03:45:00 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.59, check voltage passed.
2022-08-02 03:45:02 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:45:02 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.609756, an2 18.560975, an6 2.500000.
2022-08-02 03:45:04 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2022-08-02 03:45:04 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.657692, an2 18.585898, an6 2.500000.
2022-08-02 03:45:04 power_api.c:85:_get_avg_voltage: average_voltage = 18.573436
2022-08-02 03:45:04 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.57, check voltage passed.
2022-08-02 03:45:13 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2022-08-02 03:45:21 driver-btm-api.c:1163:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2022-08-02 03:45:32 driver-btm-api.c:1164:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2022-08-02 03:45:32 power_api.c:400:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2022-08-02 03:45:48 power_api.c:120:check_voltage_multi: retry time: 0
2022-08-02 03:45:49 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:45:49 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.634146, an2 20.073170, an6 2.500000.
2022-08-02 03:45:51 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:45:51 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.682927, an2 20.073170, an6 2.500000.
2022-08-02 03:45:51 power_api.c:85:_get_avg_voltage: average_voltage = 20.073170
2022-08-02 03:45:51 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.07, check voltage passed.
2022-08-02 03:45:53 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:45:53 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.634146, an2 20.073170, an6 2.500000.
2022-08-02 03:45:54 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:45:54 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.682927, an2 20.097560, an6 2.500000.
2022-08-02 03:45:54 power_api.c:85:_get_avg_voltage: average_voltage = 20.085365
2022-08-02 03:45:54 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.09, check voltage passed.
2022-08-02 03:46:03 driver-btm-api.c:1167:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 3
2022-08-02 03:46:14 driver-btm-api.c:1168:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 4
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-08-02 03:46:22 driver-btm-api.c:1169:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 5
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-08-02 03:46:31 driver-btm-api.c:1170:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 6
2022-08-02 03:46:31 driver-btm-api.c:1235:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2022-08-02 03:46:32 driver-btm-api.c:1238:check_asic_number: Chain 2 voltage: an0 = 20.152257, an2 20.176774, an6 2.516129.
2022-08-02 03:46:33 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1850, step by step.
2022-08-02 03:46:47 power_api.c:120:check_voltage_multi: retry time: 0
2022-08-02 03:46:49 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2022-08-02 03:46:49 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.657692, an2 18.561539, an6 2.500000.
2022-08-02 03:46:49 power_api.c:85:_get_avg_voltage: average_voltage = 18.561539
2022-08-02 03:46:49 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.56, check voltage passed.
2022-08-02 03:46:51 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:46:51 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.658537, an2 18.585365, an6 2.500000.
2022-08-02 03:46:51 power_api.c:85:_get_avg_voltage: average_voltage = 18.585365
2022-08-02 03:46:51 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.59, check voltage passed.
2022-08-02 03:47:00 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[3]: find 30 asic, times 0
2022-08-02 03:47:09 driver-btm-api.c:1163:check_asic_number_with_power_on: Chain[3]: find 30 asic, times 1
2022-08-02 03:47:20 driver-btm-api.c:1164:check_asic_number_with_power_on: Chain[3]: find 30 asic, times 2
2022-08-02 03:47:20 power_api.c:400:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2022-08-02 03:47:34 power_api.c:120:check_voltage_multi: retry time: 0
2022-08-02 03:47:35 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:47:35 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.682927, an2 20.073170, an6 2.500000.
2022-08-02 03:47:35 power_api.c:85:_get_avg_voltage: average_voltage = 20.073170
2022-08-02 03:47:35 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.07, check voltage passed.
2022-08-02 03:47:37 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:47:37 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.658537, an2 20.097560, an6 2.500000.
2022-08-02 03:47:37 power_api.c:85:_get_avg_voltage: average_voltage = 20.097560
2022-08-02 03:47:37 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.10, check voltage passed.
2022-08-02 03:47:46 driver-btm-api.c:1167:check_asic_number_with_power_on: Chain[3]: find 30 asic, times 3
2022-08-02 03:47:57 driver-btm-api.c:1168:check_asic_number_with_power_on: Chain[3]: find 30 asic, times 4
chain 3, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-08-02 03:48:06 driver-btm-api.c:1169:check_asic_number_with_power_on: Chain[3]: find 30 asic, times 5
chain 3, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-08-02 03:48:15 driver-btm-api.c:1170:check_asic_number_with_power_on: Chain[3]: find 30 asic, times 6
2022-08-02 03:48:15 driver-btm-api.c:1235:check_asic_number: Chain 3 only find 30 asic, will power off hash board 3
2022-08-02 03:48:16 driver-btm-api.c:1238:check_asic_number: Chain 3 voltage: an0 = 20.078709, an2 20.176774, an6 2.519355.
2022-08-02 03:48:17 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2022-08-02 03:48:17 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2022-08-02 03:48:17 thread.c:1502:cancel_read_nonce_reg_thread: cancel thread
2022-08-02 03:48:17 driver-btm-api.c:142:killall_hashboard: *power off hashboard*
DaveF
Legendary
*
Offline Offline

Activity: 3654
Merit: 6671


Crypto Swap Exchange


View Profile WWW
August 06, 2022, 12:48:36 PM
 #2

Looks like a bunch of bad hasboards. If you look you are getting found 0 ASIC messages or found 30 AISC messages.
Did this just start or has it been slowly dying (getting slower as it shuts off boards)

Pull the boards and see if there is any obvious damage, and check the cables and such.

The T17 units were not the best when new, now going on a couple of years old there seem to be more of them dropping.
At least from the posts that are popping up.

-Dave

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
BitMaxz
Legendary
*
Offline Offline

Activity: 3444
Merit: 3175


Playbet.io - Crypto Casino and Sportsbook


View Profile WWW
August 06, 2022, 10:57:57 PM
 #3

It seems that you have a bad PSU because you get the first error when the miner is trying to calibrate the PSU here's the logs that I'm talking about below

Code:
2022-08-02 03:41:44 driver-btm-api.c:2261:get_calibration_voltage: calibration voltage flag is error data.
I'm not sure what the logs means but according to the log above it is error data.

Would you mind checking the PSU first if it is connected properly or replug all PSU cables and test it again?

If nothing changes if you have extra PSU try to replace it to test.

Also, if all suggestions do not work above then don't forget to try to flash it through an SD card and upgrade it to the latest firmware. There are some reports that they solve this issue by flashing their units through SD card and upgrading it to the latest version or they flash the unit with a different OS.

So try to do software first before touching any hardware because if you don't have knowledge of disassembling the unit the issue might get worst.

███████████████
█████████████████████
██████▄▄███████████████
██████▐████▄▄████████████
██████▐██▀▀▀██▄▄█████████
████████▌█████▀██▄▄██████
██████████████████▌█████
█████████████▀▄██▀▀██████
██████▐██▄▄█▌███████████
██████▐████▀█████████████
██████▀▀███████████████
█████████████████████
███████████████

.... ..Playbet.io..Casino & Sportsbook.....Grab up to  BTC + 800 Free Spins........
████████████████████████████████████████
██████████████████████████████████████████████
██████▄▄████████████████████████████████████████
██████▐████▄▄█████████████████████████████████████
██████▐██▀▀▀██▄▄██████████████████████████████████
████████▌█████▀██▄▄█████▄███▄███▄███▄█████████████
██████████████████▌████▀░░██▌██▄▄▄██████████████
█████████████▀▄██▀▀█████▄░░██▌██▄░░▄▄████▄███████
██████▐██▄▄█▌██████████▀███▀███▀███▀███▀█████████
██████▐████▀██████████████████████████████████████
██████▀▀████████████████████████████████████████
██████████████████████████████████████████████
████████████████████████████████████████
GFDhd
Jr. Member
*
Offline Offline

Activity: 56
Merit: 12


View Profile
August 08, 2022, 01:28:37 AM
 #4

Like BitMaxz said, check your PSU and cables first. Or reset the miner to the factory settings. If it still doesn't work, flash the SD card program to restore the control board and upgrade to the latest firmware. Finally, you need to check hashboard.
philipma1957
Legendary
*
Offline Offline

Activity: 4312
Merit: 8871


'The right to privacy matters'


View Profile WWW
August 08, 2022, 03:20:38 AM
 #5

hello I have problems with my t17+ I can't get it to start mining I leave the kernel log if you can give me a solution thanks


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: 203416K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25960K 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: 12920K (cce62000 - 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
nand_read_bbt: bad block at 0x000008000000
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: 9/3, 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: 1019, bad PEBs: 5, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 457/141, WL threshold: 4096, image sequence number: 1751317449
ubi1: available PEBs: 0, total reserved PEBs: 1019, PEBs reserved for bad PEB handling: 35
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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2022-08-02 03:41:33 driver-btm-api.c:762:init_freq_mode: This is scan-user version
2022-08-02 03:41:33 driver-btm-api.c:2553:bitmain_soc_init: opt_multi_version     = 1
2022-08-02 03:41:33 driver-btm-api.c:2554:bitmain_soc_init: opt_bitmain_ab        = 1
2022-08-02 03:41:33 driver-btm-api.c:2555:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-08-02 03:41:33 driver-btm-api.c:2556:bitmain_soc_init: Miner compile time: Tue Jun  2 10:11:10 CST 2020 type: Antminer T17+
2022-08-02 03:41:33 driver-btm-api.c:2557:bitmain_soc_init: commit version: 9e9a5bf 2020-06-01 18:48:14, build by: lol 2020-06-02 10:21:50
2022-08-02 03:41:33 driver-btm-api.c:2180:show_sn: 8028f40c2b104814�7
2022-08-02 03:41:33 driver-btm-api.c:2237:handle_sn_for_factory_mode: read sn success, 8028f40c2b104814�7
2022-08-02 03:41:33 fan.c:263:front_fan_power_on: Note: front fan is power on!
2022-08-02 03:41:33 fan.c:273:rear_fan_power_on: Note: rear fan is power on!
2022-08-02 03:41:33 driver-btm-api.c:1357:miner_device_init: Detect 256MB control board of XILINX
2022-08-02 03:41:33 driver-btm-api.c:1298:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2022-08-02 03:41:39 driver-btm-api.c:1281:init_miner_version: miner ID : 8028f40c2b104814
2022-08-02 03:41:39 driver-btm-api.c:1287:init_miner_version: FPGA Version = 0xB023
2022-08-02 03:41:44 driver-btm-api.c:814:get_product_id: product_id[1] = 0
2022-08-02 03:41:44 driver-btm-api.c:814:get_product_id: product_id[2] = 0
2022-08-02 03:41:44 driver-btm-api.c:814:get_product_id: product_id[3] = 0
2022-08-02 03:41:44 driver-btm-api.c:845:get_chip_version: chip_version[1] = 1
2022-08-02 03:41:44 driver-btm-api.c:845:get_chip_version: chip_version[2] = 1
2022-08-02 03:41:44 driver-btm-api.c:845:get_chip_version: chip_version[3] = 1
2022-08-02 03:41:44 driver-btm-api.c:2293:update_conf_by_power_feedback: Power feedback is disabled
2022-08-02 03:41:44 driver-btm-api.c:2261:get_calibration_voltage: calibration voltage flag is error data.
2022-08-02 03:41:44 driver-btm-api.c:2327:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2022-08-02 03:41:44 frequency.c:1389:adjust_higer_max_vol_table: adjust_higer_max_vol_table, ideal_hashrate = 56866, index = 2, adjust_vol = 20
2022-08-02 03:41:44 thread.c:1462:create_read_nonce_reg_thread: create thread
2022-08-02 03:41:50 driver-btm-api.c:1281:init_miner_version: miner ID : 8028f40c2b104814
2022-08-02 03:41:50 driver-btm-api.c:1287:init_miner_version: FPGA Version = 0xB023
2022-08-02 03:41:56 driver-btm-api.c:814:get_product_id: product_id[1] = 0
2022-08-02 03:41:56 driver-btm-api.c:814:get_product_id: product_id[2] = 0
2022-08-02 03:41:56 driver-btm-api.c:814:get_product_id: product_id[3] = 0
2022-08-02 03:41:56 driver-btm-api.c:845:get_chip_version: chip_version[1] = 1
2022-08-02 03:41:56 driver-btm-api.c:845:get_chip_version: chip_version[2] = 1
2022-08-02 03:41:56 driver-btm-api.c:845:get_chip_version: chip_version[3] = 1
2022-08-02 03:41:56 driver-btm-api.c:1944:get_ccdly_opt: ccdly_opt[1] = 0
2022-08-02 03:41:56 driver-btm-api.c:1944:get_ccdly_opt: ccdly_opt[2] = 0
2022-08-02 03:41:56 driver-btm-api.c:1944:get_ccdly_opt: ccdly_opt[3] = 0
2022-08-02 03:41:56 driver-btm-api.c:2439:bitmain_board_init: g_ccdly_opt = 0
2022-08-02 03:41:56 driver-btm-api.c:775:_set_project_type: project:0, set to T17Plus always
2022-08-02 03:41:56 driver-btm-api.c:790:_set_project_type: Project type: Antminer T17+
2022-08-02 03:41:56 driver-btm-api.c:801:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-08-02 03:41:56 driver-btm-api.c:802:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-08-02 03:41:56 driver-btm-api.c:801:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-08-02 03:41:56 driver-btm-api.c:802:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-08-02 03:41:56 driver-btm-api.c:801:dump_pcb_bom_version: Chain [3] PCB Version: 0x0100
2022-08-02 03:41:56 driver-btm-api.c:802:dump_pcb_bom_version: Chain [3] BOM Version: 0x0100
2022-08-02 03:41:57 driver-btm-api.c:2461:bitmain_board_init: Fan check passed.
2022-08-02 03:41:58 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-08-02 03:42:00 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-08-02 03:42:01 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-08-02 03:42:03 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-08-02 03:42:04 board.c:36:jump_and_app_check_restore_pic: chain[3] PIC jump to app
2022-08-02 03:42:06 board.c:40:jump_and_app_check_restore_pic: Check chain[3] PIC fw version=0x88
2022-08-02 03:42:06 thread.c:1457:create_pic_heart_beat_thread: create thread
2022-08-02 03:42:08 power_api.c:231:power_init: power type version: 0x0042
2022-08-02 03:42:08 power_api.c:249:power_init: Power init:
2022-08-02 03:42:08 power_api.c:250:power_init: current_voltage_raw = 0
2022-08-02 03:42:08 power_api.c:251:power_init: highest_voltage_raw = 1950
2022-08-02 03:42:08 power_api.c:252:power_init: working_voltage_raw = 1900
2022-08-02 03:42:08 power_api.c:253:power_init: higher_voltage_raw  = 1930
2022-08-02 03:42:08 power_api.c:254:power_init: check_asic_voltage_raw  = 2000
2022-08-02 03:42:08 driver-btm-api.c:2471:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-08-02 03:42:08 power_api.c:218:power_off: init gpio907
2022-08-02 03:42:08 power_api.c:221:power_off: set gpio907 to 1
2022-08-02 03:42:39 power_api.c:206:power_on: set gpio907 to 0
2022-08-02 03:42:40 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1850, step by step.
2022-08-02 03:42:58 power_api.c:120:check_voltage_multi: retry time: 0
2022-08-02 03:42:59 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2022-08-02 03:42:59 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.487179, an2 18.537180, an6 2.500000.
2022-08-02 03:43:00 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:43:00 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.634146, an2 18.585365, an6 2.500000.
2022-08-02 03:43:01 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:43:01 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.658537, an2 18.585365, an6 2.500000.
2022-08-02 03:43:01 power_api.c:85:_get_avg_voltage: average_voltage = 18.569303
2022-08-02 03:43:01 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.57, check voltage passed.
2022-08-02 03:43:03 power_api.c:56:_get_avg_voltage: an6 raw = 2.519355, factor = 1.007742
2022-08-02 03:43:03 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.486556, an2 18.513444, an6 2.500000.
2022-08-02 03:43:04 power_api.c:56:_get_avg_voltage: an6 raw = 2.509677, factor = 1.003871
2022-08-02 03:43:04 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.610540, an2 18.609255, an6 2.500000.
2022-08-02 03:43:05 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:43:05 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.658537, an2 18.585365, an6 2.500000.
2022-08-02 03:43:05 power_api.c:85:_get_avg_voltage: average_voltage = 18.569354
2022-08-02 03:43:05 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.57, check voltage passed.
2022-08-02 03:43:06 uart.c:81:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-08-02 03:43:14 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[1]: find 10 asic, times 0
2022-08-02 03:43:23 driver-btm-api.c:1163:check_asic_number_with_power_on: Chain[1]: find 10 asic, times 1
2022-08-02 03:43:35 driver-btm-api.c:1164:check_asic_number_with_power_on: Chain[1]: find 10 asic, times 2
2022-08-02 03:43:35 power_api.c:400:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2022-08-02 03:43:52 power_api.c:120:check_voltage_multi: retry time: 0
2022-08-02 03:43:53 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2022-08-02 03:43:53 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.487179, an2 20.023077, an6 2.500000.
2022-08-02 03:43:54 power_api.c:56:_get_avg_voltage: an6 raw = 2.509677, factor = 1.003871
2022-08-02 03:43:54 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.634961, an2 20.098972, an6 2.500000.
2022-08-02 03:43:55 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2022-08-02 03:43:55 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.682051, an2 20.071795, an6 2.500000.
2022-08-02 03:43:55 power_api.c:85:_get_avg_voltage: average_voltage = 20.064615
2022-08-02 03:43:55 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.06, check voltage passed.
2022-08-02 03:43:57 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2022-08-02 03:43:57 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.487179, an2 20.023077, an6 2.500000.
2022-08-02 03:43:58 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:43:58 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.634146, an2 20.073170, an6 2.500000.
2022-08-02 03:43:59 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2022-08-02 03:43:59 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.682051, an2 20.071795, an6 2.500000.
2022-08-02 03:43:59 power_api.c:85:_get_avg_voltage: average_voltage = 20.056014
2022-08-02 03:43:59 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.06, check voltage passed.
2022-08-02 03:44:09 driver-btm-api.c:1167:check_asic_number_with_power_on: Chain[1]: find 10 asic, times 3
2022-08-02 03:44:20 driver-btm-api.c:1168:check_asic_number_with_power_on: Chain[1]: find 10 asic, times 4
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-08-02 03:44:29 driver-btm-api.c:1169:check_asic_number_with_power_on: Chain[1]: find 10 asic, times 5
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-08-02 03:44:38 driver-btm-api.c:1170:check_asic_number_with_power_on: Chain[1]: find 10 asic, times 6
2022-08-02 03:44:38 driver-btm-api.c:1235:check_asic_number: Chain 1 only find 10 asic, will power off hash board 1
2022-08-02 03:44:39 driver-btm-api.c:1238:check_asic_number: Chain 1 voltage: an0 = 20.201290, an2 20.152257, an6 2.519355.
2022-08-02 03:44:40 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1850, step by step.
2022-08-02 03:44:58 power_api.c:120:check_voltage_multi: retry time: 0
2022-08-02 03:44:59 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:44:59 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.634146, an2 18.585365, an6 2.500000.
2022-08-02 03:45:00 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:45:00 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.658537, an2 18.585365, an6 2.500000.
2022-08-02 03:45:00 power_api.c:85:_get_avg_voltage: average_voltage = 18.585365
2022-08-02 03:45:00 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.59, check voltage passed.
2022-08-02 03:45:02 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:45:02 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.609756, an2 18.560975, an6 2.500000.
2022-08-02 03:45:04 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2022-08-02 03:45:04 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.657692, an2 18.585898, an6 2.500000.
2022-08-02 03:45:04 power_api.c:85:_get_avg_voltage: average_voltage = 18.573436
2022-08-02 03:45:04 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.57, check voltage passed.
2022-08-02 03:45:13 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2022-08-02 03:45:21 driver-btm-api.c:1163:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2022-08-02 03:45:32 driver-btm-api.c:1164:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2022-08-02 03:45:32 power_api.c:400:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2022-08-02 03:45:48 power_api.c:120:check_voltage_multi: retry time: 0
2022-08-02 03:45:49 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:45:49 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.634146, an2 20.073170, an6 2.500000.
2022-08-02 03:45:51 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:45:51 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.682927, an2 20.073170, an6 2.500000.
2022-08-02 03:45:51 power_api.c:85:_get_avg_voltage: average_voltage = 20.073170
2022-08-02 03:45:51 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.07, check voltage passed.
2022-08-02 03:45:53 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:45:53 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.634146, an2 20.073170, an6 2.500000.
2022-08-02 03:45:54 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:45:54 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.682927, an2 20.097560, an6 2.500000.
2022-08-02 03:45:54 power_api.c:85:_get_avg_voltage: average_voltage = 20.085365
2022-08-02 03:45:54 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.09, check voltage passed.
2022-08-02 03:46:03 driver-btm-api.c:1167:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 3
2022-08-02 03:46:14 driver-btm-api.c:1168:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 4
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-08-02 03:46:22 driver-btm-api.c:1169:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 5
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-08-02 03:46:31 driver-btm-api.c:1170:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 6
2022-08-02 03:46:31 driver-btm-api.c:1235:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2022-08-02 03:46:32 driver-btm-api.c:1238:check_asic_number: Chain 2 voltage: an0 = 20.152257, an2 20.176774, an6 2.516129.
2022-08-02 03:46:33 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1850, step by step.
2022-08-02 03:46:47 power_api.c:120:check_voltage_multi: retry time: 0
2022-08-02 03:46:49 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2022-08-02 03:46:49 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.657692, an2 18.561539, an6 2.500000.
2022-08-02 03:46:49 power_api.c:85:_get_avg_voltage: average_voltage = 18.561539
2022-08-02 03:46:49 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.56, check voltage passed.
2022-08-02 03:46:51 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:46:51 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.658537, an2 18.585365, an6 2.500000.
2022-08-02 03:46:51 power_api.c:85:_get_avg_voltage: average_voltage = 18.585365
2022-08-02 03:46:51 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.59, check voltage passed.
2022-08-02 03:47:00 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[3]: find 30 asic, times 0
2022-08-02 03:47:09 driver-btm-api.c:1163:check_asic_number_with_power_on: Chain[3]: find 30 asic, times 1
2022-08-02 03:47:20 driver-btm-api.c:1164:check_asic_number_with_power_on: Chain[3]: find 30 asic, times 2
2022-08-02 03:47:20 power_api.c:400:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2022-08-02 03:47:34 power_api.c:120:check_voltage_multi: retry time: 0
2022-08-02 03:47:35 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:47:35 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.682927, an2 20.073170, an6 2.500000.
2022-08-02 03:47:35 power_api.c:85:_get_avg_voltage: average_voltage = 20.073170
2022-08-02 03:47:35 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.07, check voltage passed.
2022-08-02 03:47:37 power_api.c:56:_get_avg_voltage: an6 raw = 2.512903, factor = 1.005161
2022-08-02 03:47:37 power_api.c:60:_get_avg_voltage: chain 3, an0 = 0.658537, an2 20.097560, an6 2.500000.
2022-08-02 03:47:37 power_api.c:85:_get_avg_voltage: average_voltage = 20.097560
2022-08-02 03:47:37 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.10, check voltage passed.
2022-08-02 03:47:46 driver-btm-api.c:1167:check_asic_number_with_power_on: Chain[3]: find 30 asic, times 3
2022-08-02 03:47:57 driver-btm-api.c:1168:check_asic_number_with_power_on: Chain[3]: find 30 asic, times 4
chain 3, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-08-02 03:48:06 driver-btm-api.c:1169:check_asic_number_with_power_on: Chain[3]: find 30 asic, times 5
chain 3, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-08-02 03:48:15 driver-btm-api.c:1170:check_asic_number_with_power_on: Chain[3]: find 30 asic, times 6
2022-08-02 03:48:15 driver-btm-api.c:1235:check_asic_number: Chain 3 only find 30 asic, will power off hash board 3
2022-08-02 03:48:16 driver-btm-api.c:1238:check_asic_number: Chain 3 voltage: an0 = 20.078709, an2 20.176774, an6 2.519355.
2022-08-02 03:48:17 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2022-08-02 03:48:17 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2022-08-02 03:48:17 thread.c:1502:cancel_read_nonce_reg_thread: cancel thread
2022-08-02 03:48:17 driver-btm-api.c:142:killall_hashboard: *power off hashboard*

please set the log in code like i did

▄▄███████▄▄
▄██████████████▄
▄██████████████████▄
▄████▀▀▀▀███▀▀▀▀█████▄
▄█████████████▄█▀████▄
███████████▄███████████
██████████▄█▀███████████
██████████▀████████████
▀█████▄█▀█████████████▀
▀████▄▄▄▄███▄▄▄▄████▀
▀██████████████████▀
▀███████████████▀
▀▀███████▀▀
.
 MΞTAWIN  THE FIRST WEB3 CASINO   
.
.. PLAY NOW ..
freakky (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
August 10, 2022, 08:24:45 PM
 #6

the problem is the hashboard change the power supply and does the same
if i put a new hashboard will it work?
BitMaxz
Legendary
*
Offline Offline

Activity: 3444
Merit: 3175


Playbet.io - Crypto Casino and Sportsbook


View Profile WWW
August 10, 2022, 11:13:25 PM
 #7

the problem is the hashboard change the power supply and does the same
if i put a new hashboard will it work?

I'm confused a bit what do you mean by the hashboard change the power supply?

Did you mean that you already replace the PSU but the issue is still the same?

I suggest check carefully the unit there might be grounded that leads hashboard not showing the right ASIC.
Would you mind to try disassemble the unit and run them one by one then check for any changes in the logs or if one of the hashboard is running fine.

███████████████
█████████████████████
██████▄▄███████████████
██████▐████▄▄████████████
██████▐██▀▀▀██▄▄█████████
████████▌█████▀██▄▄██████
██████████████████▌█████
█████████████▀▄██▀▀██████
██████▐██▄▄█▌███████████
██████▐████▀█████████████
██████▀▀███████████████
█████████████████████
███████████████

.... ..Playbet.io..Casino & Sportsbook.....Grab up to  BTC + 800 Free Spins........
████████████████████████████████████████
██████████████████████████████████████████████
██████▄▄████████████████████████████████████████
██████▐████▄▄█████████████████████████████████████
██████▐██▀▀▀██▄▄██████████████████████████████████
████████▌█████▀██▄▄█████▄███▄███▄███▄█████████████
██████████████████▌████▀░░██▌██▄▄▄██████████████
█████████████▀▄██▀▀█████▄░░██▌██▄░░▄▄████▄███████
██████▐██▄▄█▌██████████▀███▀███▀███▀███▀█████████
██████▐████▀██████████████████████████████████████
██████▀▀████████████████████████████████████████
██████████████████████████████████████████████
████████████████████████████████████████
mikeywith
Legendary
*
Offline Offline

Activity: 2422
Merit: 6626


be constructive or S.T.F.U


View Profile
August 10, 2022, 11:17:17 PM
 #8

if i put a new hashboard will it work?

It will depend on how lucky you are, these hash boards come in with a fixed voltage input stored in the EEPROM, and the control board will want all of them to be matching, so if you happen to mix and match a few hash boards and one of them was not in the same voltage input the miner won't start hashing, you can solve this by one of two ways.

1- Use custom firmware like Vnish which doesn't read the voltage value and will allow any hashboard with the complete asic count to run.

or

2- Get the tool from Zuesbtc to copy-paste the values on all hash boards so that the original firmware will see them as "matching" and allows you to run them.

With that said, I don't think you should waste more money buying another piece of junk, if you can cheaply fix these hash boards go for it, if not, sell them as is for whatever price, along with the spare PSU you mentioned you tried, and get a proper mining gear that won't break again in a few weeks/months, avoid the 17 series of Bitmain at all costs.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
MinerMEDIC
Member
**
Offline Offline

Activity: 166
Merit: 82

EET/NASA intern 2013 Bitmain/MicroBT/IPC cert


View Profile
August 22, 2022, 04:09:30 AM
 #9

I would be very revealing if you installed HiveOS and it just starting working again.

---Hi, I'm Juergen "Jay" & I TEACH and REPAIR ASIC HASHBOARDS-- Purdue AS EET -- MinerMEDIC is NOW FREELANCE in Chicago!
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!