Title: help with t17 Post by: johnrig35 on December 05, 2021, 01:01:20 AM CPU1: failed to boot: -1 this is all i can find please help
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:
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: 203608K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25768K 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: 12728K (cce93000 - cdb01000) hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available futex hash table entries: 512 (order: 3, 32768 bytes) workingset: timestamp_bits=28 max_order=16 bucket_order=0 jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330 dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16 e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps console [ttyPS0] enabled xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000 [drm] Initialized drm 1.1.0 20060810 brd: module loaded loop: module loaded CAN device driver interface gpiod_set_value: invalid GPIO libphy: MACB_mii_bus: probed macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00) Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1) e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k e1000e: Copyright(c) 1999 - 2015 Intel Corporation. ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-pci: EHCI PCI platform driver usbcore: registered new interface driver usb-storage mousedev: PS/2 mouse device common for all mice i2c /dev entries driver Xilinx Zynq CpuIdle Driver started sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman sdhci-pltfm: SDHCI platform and OF driver helper mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA ledtrig-cpu: registered to indicate activity on CPUs usbcore: registered new interface driver usbhid usbhid: USB HID core driver nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda nand: Micron MT29F2G08ABAEAWP nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip Bad block table found at page 131008, version 0x01 Bad block table found at page 130944, version 0x01 6 ofpart partitions found on MTD device pl35x-nand Creating 6 MTD partitions on "pl35x-nand": 0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel" 0x000002800000-0x000004800000 : "ramfs" 0x000004800000-0x000005000000 : "configs" 0x000005000000-0x000006000000 : "reserve" 0x000006000000-0x000008000000 : "ramfs-bak" 0x000008000000-0x000010000000 : "reserve1" NET: Registered protocol family 10 sit: IPv6 over IPv4 tunneling driver NET: Registered protocol family 17 can: controller area network core (rev 20120528 abi 9) NET: Registered protocol family 29 can: raw protocol (rev 20120528) can: broadcast manager protocol (rev 20120528 t) can: netlink gateway (rev 20130117) max_hops=1 zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05' zynq_pm_late_init: Unable to map DDRC IO memory. Registering SWP/SWPB emulation handler hctosys: unable to open rtc device (rtc0) ALSA device list: No soundcards found. RAMDISK: gzip image found at block 0 EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) VFS: Mounted root (ext4 filesystem) on device 1:0. devtmpfs: mounted Freeing unused kernel memory: 1024K (c0a00000 - c0b00000) EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr random: dd urandom read with 0 bits of entropy available ubi0: attaching mtd2 ubi0: scanning is finished ubi0: attached mtd2 (name "configs", size 8 MiB) ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096 ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0 ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128 ubi0: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 964972085 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): 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 2C83B01D-C872-4775-B873-0306F6490386, 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: 2/1, WL threshold: 4096, image sequence number: 100324054 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): 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 058C0E40-6EAA-4676-9C52-F694F6D34F3B, small LPT model alloc_contig_range: [e043, e044) PFNs busy IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready alloc_contig_range: [e043, e044) PFNs busy 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 = 0xfb013 In fpga mem driver! request_mem_region OK! fpga mem virtual address is 0xd2000000 2021-12-05 00:31:00 driver-btm-api.c:542:init_freq_mode: This is scan-user version 2021-12-05 00:31:00 driver-btm-api.c:1877:bitmain_soc_init: opt_multi_version = 1 2021-12-05 00:31:00 driver-btm-api.c:1878:bitmain_soc_init: opt_bitmain_ab = 1 2021-12-05 00:31:00 driver-btm-api.c:1879:bitmain_soc_init: opt_bitmain_work_mode = 2 2021-12-05 00:31:00 driver-btm-api.c:1880:bitmain_soc_init: Miner compile time: Mon Apr 27 13:25:08 CST 2020 type: Antminer S17 2021-12-05 00:31:00 driver-btm-api.c:1881:bitmain_soc_init: commit version: d22f356 2020-04-24 18:30:49, build by: lol 2020-04-27 13:31:45 2021-12-05 00:31:00 driver-btm-api.c:1691:show_sn: no SN got, please write SN to /nvdata/sn 2021-12-05 00:31:00 driver-btm-api.c:1040:miner_device_init: Detect 256MB control board of XILINX 2021-12-05 00:31:00 driver-btm-api.c:988:init_fan_parameter: fan_eft : 0 fan_pwm : 0 2021-12-05 00:31:00 thread.c:783:create_read_nonce_reg_thread: create thread 2021-12-05 00:31:06 driver-btm-api.c:972:init_miner_version: miner ID : 80506d0a5c20881c 2021-12-05 00:31:06 driver-btm-api.c:978:init_miner_version: FPGA Version = 0xB013 2021-12-05 00:31:07 Cgminer CRC check fail. 2021-12-05 00:31:09 Cgminer CRC check fail. 2021-12-05 00:31:11 Cgminer CRC check fail. 2021-12-05 00:31:11 driver-btm-api.c:616:get_product_id: product_id[0] = 1 2021-12-05 00:31:11 driver-btm-api.c:616:get_product_id: product_id[1] = 1 2021-12-05 00:31:11 driver-btm-api.c:616:get_product_id: product_id[2] = 1 2021-12-05 00:31:11 Cgminer crc check is not pass. 2021-12-05 00:31:11 Cgminer crc check is not pass. 2021-12-05 00:31:11 Project type is X17. 2021-12-05 00:31:11 driver-btm-api.c:560:_set_project_type: project:2 2021-12-05 00:31:11 driver-btm-api.c:585:_set_project_type: Project type: Antminer X17 2021-12-05 00:31:11 driver-btm-api.c:596:dump_pcb_bom_version: Chain
2021-12-05 00:31:11 driver-btm-api.c:597:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100 2021-12-05 00:31:11 driver-btm-api.c:596:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100 2021-12-05 00:31:11 driver-btm-api.c:597:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100 2021-12-05 00:31:13 driver-btm-api.c:1802:bitmain_board_init: Fan check passed. 2021-12-05 00:31:14 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app 2021-12-05 00:31:16 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9 2021-12-05 00:31:17 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app 2021-12-05 00:31:19 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9 2021-12-05 00:31:20 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app 2021-12-05 00:31:22 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9 2021-12-05 00:31:22 thread.c:778:create_pic_heart_beat_thread: create thread 2021-12-05 00:31:22 power_api.c:207:power_init: Power init: 2021-12-05 00:31:22 power_api.c:208:power_init: current_voltage_raw = 0 2021-12-05 00:31:22 power_api.c:209:power_init: highest_voltage_raw = 2100 2021-12-05 00:31:22 power_api.c:210:power_init: working_voltage_raw = 1830 2021-12-05 00:31:22 power_api.c:211:power_init: higher_voltage_raw = 1950 2021-12-05 00:31:22 driver-btm-api.c:1812:bitmain_board_init: Enter 30s sleep to make sure power release finish. 2021-12-05 00:31:22 power_api.c:181:power_off: init gpio907 2021-12-05 00:31:54 power_api.c:251:set_to_highest_voltage: Set to voltage raw 2100, one step. 2021-12-05 00:31:57 power_api.c:87:check_voltage_multi: retry time: 0 2021-12-05 00:31:58 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 21.020420 2021-12-05 00:31:59 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.057158 2021-12-05 00:32:00 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 20.934697 2021-12-05 00:32:00 power_api.c:50:_get_avg_voltage: average_voltage = 21.004092 2021-12-05 00:32:00 power_api.c:68:check_voltage: target_vol = 21.00, actural_vol = 21.00, check voltage passed. 2021-12-05 00:32:00 uart.c:71:set_baud: set fpga_baud to 115200 2021-12-05 00:32:11 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0 2021-12-05 00:32:22 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 1 2021-12-05 00:32:33 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 2 2021-12-05 00:32:33 driver-btm-api.c:942:check_asic_number: Chain 0 only find 30 asic, will power off hash board 0 2021-12-05 00:32:45 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0 Title: Re: help with t17 Post by: wndsnb on December 05, 2021, 07:06:18 PM 2021-12-05 00:31:00 driver-btm-api.c:1880:bitmain_soc_init: Miner compile time: Mon Apr 27 13:25:08 CST 2020 type: Antminer S17 Well .... it looks like you've got S17 firmware burned into a T17. You'll need to burn in T17 firmware for it to work. Not sure if stock firmware will let you load the T17 firmware back into it through the GUI, you may have to use the SD card. Title: Re: help with t17 Post by: BitMaxz on December 05, 2021, 10:43:24 PM If you don't know how to flash it with an SD card there is a guide from Bitmain that you can follow.
Here's the link below just translate it into English that's the guide they provided for t17 units even it is not listed there. - https://support.bitmain.com/hc/zh-cn/articles/900000267926 For the SD card you can find it here SD_T17 (https://service.bitmain.com/support/download?product=Flashing%20SD%20card%20with%20image) Take note of other firmware because there are also t17+ and t17e so make sure only download T17 SD card firmware. After you successfully flash the unit through an SD card make sure to flash it again through Web GUI and take note of the exact firmware it won't work if you flash it with different firmware. Title: Re: help with t17 Post by: johnrig35 on December 13, 2021, 11:34:19 PM thank for your help now i but another board in and i am getting this are my boards bad not for sure
[2021/12/13 23:28:30] INFO: Initializing hash boards [2021/12/13 23:28:30] INFO: chain[2] - Initializing [2021/12/13 23:28:30] INFO: chain[1] - Initializing [2021/12/13 23:28:30] INFO: chain[0] - Initializing [2021/12/13 23:28:43] INFO: chain[2] - 30 chips detected [2021/12/13 23:28:44] INFO: chain[1] - 30 chips detected [2021/12/13 23:28:45] INFO: chain[0] - 30 chips detected [2021/12/13 23:28:51] INFO: Start-up temperature is 28 C (min -15 C) [2021/12/13 23:28:51] INFO: Switching to manual fan control (100 %) [2021/12/13 23:28:51] INFO: Changing voltage from 17000 to 17300 mV gradually [2021/12/13 23:29:13] INFO: Raising freq from 50 to 750 Mhz gradually [2021/12/13 23:29:28] INFO: Switching to automatic fan control (75 C) [2021/12/13 23:29:28] INFO: Start mining! [2021/12/13 23:29:45] WARN: chain[1] - Overheated, chip temp=90 [2021/12/13 23:29:45] WARN: Switching to emergency fan control [2021/12/13 23:29:45] INFO: chain[1] - Shutting down the chain [2021/12/13 23:29:46] WARN: chain[2] - Overheated, chip temp=91 [2021/12/13 23:29:46] WARN: Switching to emergency fan control [2021/12/13 23:29:46] INFO: chain[2] - Shutting down the chain [2021/12/13 23:29:48] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [2021/12/13 23:29:51] WARN: chain[0] - Overheated, chip temp=90 [2021/12/13 23:29:51] WARN: Switching to emergency fan control [2021/12/13 23:29:51] INFO: chain[0] - Shutting down the chain [2021/12/13 23:29:53] WARN: No working chains [2021/12/13 23:29:53] INFO: Shutting down the miner [2021/12/13 23:29:55] INFO: Stopping FPGA queue [2021/12/13 23:29:55] INFO: chain[0] - Shutting down the chain [2021/12/13 23:29:55] INFO: chain[1] - Shutting down the chain [2021/12/13 23:29:55] INFO: chain[2] - Shutting down the chain [2021/12/13 23:29:55] INFO: Power OFF [2021/12/13 23:30:11] INFO: Detected 256 Mb of RAM [2021/12/13 23:30:11] INFO: Switching to manual fan control (30 %) [2021/12/13 23:30:11] INFO: Checking fans [2021/12/13 23:30:12] INFO: fan[0] - OK [2021/12/13 23:30:12] INFO: fan[1] - OK [2021/12/13 23:30:12] INFO: fan[2] - OK [2021/12/13 23:30:12] INFO: fan[3] - OK [2021/12/13 23:30:18] INFO: Power ON [2021/12/13 23:30:20] INFO: Starting FPGA queue [2021/12/13 23:30:20] INFO: Initializing hash boards [2021/12/13 23:30:20] INFO: chain[2] - Initializing [2021/12/13 23:30:20] INFO: chain[1] - Initializing [2021/12/13 23:30:20] INFO: chain[0] - Initializing [2021/12/13 23:30:33] INFO: chain[2] - 30 chips detected [2021/12/13 23:30:34] INFO: chain[1] - 30 chips detected [2021/12/13 23:30:35] INFO: chain[0] - 30 chips detected [2021/12/13 23:30:42] INFO: Start-up temperature is 29 C (min -15 C) [2021/12/13 23:30:42] INFO: Switching to manual fan control (100 %) [2021/12/13 23:30:42] INFO: Changing voltage from 17000 to 17300 mV gradually Title: Re: help with t17 Post by: BitMaxz on December 13, 2021, 11:50:16 PM Did you already flash it with the proper firmware?
All troubleshooting guide is already on Bitmain here https://support.bitmain.com/hc/en-us/articles/360020839134-Antminer-T17 What I can see is overheating for both hashboard chains 1 and 2. Next time use the "insert tag" with icon # before you post your kernel logs to make your thread clean. What I think is maybe you are running this miner at 120v? So the power supply is not giving enough power that is why it detects only a few ASIC chips and overheating? Or maybe it's overheating because you didn't separate the hot airflow? What is your room temperature? Actually, it's hard to troubleshoot the miner without the whole kernel logs you must post the whole logs here with "insert tag code" or if you can't able to post the whole then use pastebin.com and paste the URL here. Title: Re: help with t17 Post by: wndsnb on December 14, 2021, 01:58:22 AM Might want to verify your fans are all blowing in the correct direction. All should be sucking in from the side with the ethernet port, and exhausting out the other side.
Title: Re: help with t17 Post by: johnrig35 on December 14, 2021, 02:10:34 AM thanks
it on 220 not 110 i keep trying to fig it out Title: Re: help with t17 Post by: mikeywith on December 14, 2021, 09:39:10 PM Post the complete kernel log using pastebin.com
It seems like your miner is overheating shortly after the mining process starts, which doesn't make sense unless the place is really super hot or the temp sensor is bad, but then all 3 hash boards are reporting the same issue which makes me doubt that it has anything to do with temps, post the complete kernel log first and then we can troubleshoot it one step at a time. Title: Re: help with t17 Post by: wndsnb on December 14, 2021, 10:11:45 PM It makes sense if one set of fans is reversed so the front and rear fans are fighting each other....
Title: Re: help with t17 Post by: mikeywith on December 14, 2021, 10:47:16 PM It makes sense if one set of fans is reversed so the front and rear fans are fighting each other.... Not sure all 4 fans will pass the fan-check if 2 of them were reversed, also if you check this line Code: [2021/12/13 23:29:28] INFO: Start mining! I highly doubt 17 seconds is enough to overheat the hash board, but ya, he should just check to make sure. Title: Re: help with t17 Post by: BitMaxz on December 14, 2021, 11:01:04 PM Actually what I think is the exhaust from the miner is not running
The first logs shows this Code: 2021-12-05 00:31:00 driver-btm-api.c:988:init_fan_parameter: fan_eft : 0 fan_pwm : 0 which is the fan no power signal there is a possibility any of the exhaust fans is defective or broken. That is why I need the whole kernel logs and maybe we can see the first issue before it detects overheating. Title: Re: help with t17 Post by: wndsnb on December 15, 2021, 02:58:25 PM Not sure all 4 fans will pass the fan-check if 2 of them were reversed, also if you check this line Code: [2021/12/13 23:29:28] INFO: Start mining! I highly doubt 17 seconds is enough to overheat the hash board, but ya, he should just check to make sure. Yes, it will pass the fan check if two are mounted incorrectly ... I know from experience... Also, the chips actually start drawing power before the "Start mining!" line, they start heating up quickly as soon as the chip frequencies are raised, so closer to 30 seconds. johnrig35 ... if you solved your issue, let us know what did it! If not, post the full logs and we'll try to help... |