amirheavy666 (OP)
Full Member
Offline
Activity: 228
Merit: 101
NEM (XEM) Top Coin
|
|
August 17, 2020, 06:27:45 PM Last edit: August 18, 2020, 03:03:01 AM by frodocooper |
|
I updated my asic t17+ 55 ths to framework of asic.to successfully .My miner status and log is on below....you know that we can change voltage and frequency of chain manually in asic.to framework. i want to know with change of voltage or frequency of chains , can i solve this chip issue? any recommend setting is exists for asic.to? thanks. my asic is this status [2020/08/16 12:32:43] WARN: chain[2] - 0 of 44 chips detected [2020/08/16 12:32:44] INFO: chain[1] - 44 chips detected [2020/08/16 12:32:45] INFO: chain[0] - 44 chips detected
and after reset it manually it change to it: [2020/08/17 17:53:09] WARN: chain[1] - 0 of 44 chips detected [2020/08/17 17:53:10] INFO: chain[0] - 44 chips detected [2020/08/17 17:53:18] WARN: chain[2] - 24 of 44 chips detected
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: 202820K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 26556K 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: 13516K (ccdcd000 - 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 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: 5/2, WL threshold: 4096, image sequence number: 2881768101 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 2AF94D23-0760-4801-8C27-532C11A81FC1, 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: 177/36, WL threshold: 4096, image sequence number: 3563076859 ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36 ubi1: background thread "ubi_bgt1d" started, PID 720 UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723 UBIFS (ubi1:0): recovery needed UBIFS (ubi1:0): recovery completed UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1" UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs) UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB) UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID A21581E4-693A-4BBF-A66A-FCE5ACD2EF7F, small LPT model IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz macb e000b000.ethernet eth0: link up (100/Full) IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready random: nonblocking pool is initialized [2020/08/14 09:02:47] INFO: Detected 256 Mb of RAM [2020/08/14 09:02:47] INFO: Switching to manual fan control (30 %) [2020/08/14 09:02:47] INFO: Checking fans [2020/08/14 09:02:51] INFO: fan[0] - OK [2020/08/14 09:02:51] INFO: fan[1] - OK [2020/08/14 09:02:51] INFO: fan[2] - OK [2020/08/14 09:02:51] INFO: fan[3] - OK [2020/08/14 09:02:57] INFO: Power ON [2020/08/14 09:02:59] INFO: Starting FPGA queue [2020/08/14 09:02:59] INFO: Initializing hash boards [2020/08/14 09:02:59] INFO: chain[2] - Initializing [2020/08/14 09:02:59] INFO: chain[1] - Initializing [2020/08/14 09:02:59] INFO: chain[0] - Initializing [2020/08/14 09:03:12] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies [2020/08/14 09:03:13] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies [2020/08/14 09:03:14] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies [2020/08/14 09:03:14] WARN: chain[2] - 0 of 44 chips detected [2020/08/14 09:03:14] INFO: Shutting down the miner [2020/08/14 09:03:14] INFO: Stopping FPGA queue [2020/08/14 09:03:14] INFO: chain[0] - Shutting down the chain [2020/08/14 09:03:15] INFO: chain[1] - Shutting down the chain [2020/08/14 09:03:15] INFO: chain[1] - 44 chips detected [2020/08/14 09:03:15] INFO: chain[2] - Shutting down the chain [2020/08/14 09:03:16] INFO: Power OFF [2020/08/14 09:03:25] INFO: Detected 256 Mb of RAM [2020/08/14 09:03:25] INFO: Switching to manual fan control (30 %) [2020/08/14 09:03:25] INFO: Checking fans [2020/08/14 09:03:26] INFO: fan[0] - OK [2020/08/14 09:03:26] INFO: fan[1] - OK [2020/08/14 09:03:26] INFO: fan[2] - OK [2020/08/14 09:03:26] INFO: fan[3] - OK [2020/08/14 09:03:32] INFO: Power ON [2020/08/14 09:03:34] INFO: Starting FPGA queue [2020/08/14 09:03:34] INFO: Initializing hash boards [2020/08/14 09:03:34] INFO: chain[2] - Initializing [2020/08/14 09:03:34] INFO: chain[1] - Initializing [2020/08/14 09:03:34] INFO: chain[0] - Initializing [2020/08/14 09:03:48] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies [2020/08/14 09:03:49] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies [2020/08/14 09:03:50] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies [2020/08/14 09:03:50] WARN: chain[2] - 0 of 44 chips detected [2020/08/14 09:03:51] INFO: chain[1] - 44 chips detected [2020/08/14 09:03:52] INFO: chain[0] - 44 chips detected [2020/08/14 09:03:59] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies [2020/08/14 09:04:00] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies [2020/08/14 09:04:01] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies [2020/08/14 09:04:01] WARN: chain[2] - 0 of 44 chips detected [2020/08/14 09:04:11] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies [2020/08/14 09:04:12] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies [2020/08/14 09:04:13] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies [2020/08/14 09:04:13] WARN: chain[2] - 0 of 44 chips detected [2020/08/14 09:04:13] ERROR: driver-btm-chain.c:488 chain[2] - Failed to detect ASIC chips [2020/08/14 09:04:13] INFO: chain[2] - Shutting down the chain [2020/08/14 09:04:13] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed [2020/08/14 09:04:17] INFO: Start-up temperature is 26 C (min -15 C) [2020/08/14 09:04:17] INFO: Switching to manual fan control (100 %) [2020/08/14 09:04:17] INFO: Changing voltage from 19500 to 18500 mV gradually [2020/08/14 09:04:47] INFO: Raising freq from 50 to 500 Mhz gradually [2020/08/14 09:04:56] INFO: Switching to automatic fan control (75 C) [2020/08/14 09:04:56] INFO: Start mining! [2020/08/17 17:29:15] INFO: Changing voltage from 19000 to 18800 mV gradually [2020/08/17 17:29:38] INFO: Changing voltage from 18800 to 18600 mV gradually [2020/08/17 17:30:01] INFO: Changing voltage from 18600 to 18400 mV gradually [2020/08/17 17:30:24] INFO: Changing voltage from 18400 to 18200 mV gradually [2020/08/17 17:30:46] INFO: Changing voltage from 18200 to 18000 mV gradually [2020/08/17 17:31:06] INFO: Shutting down the miner [2020/08/17 17:31:06] INFO: Setting freq to 50 Mhz gradually [2020/08/17 17:31:11] INFO: Stopping FPGA queue [2020/08/17 17:31:11] INFO: chain[0] - Shutting down the chain [2020/08/17 17:31:18] INFO: Detected 256 Mb of RAM [2020/08/17 17:31:18] INFO: Switching to manual fan control (30 %) [2020/08/17 17:31:18] INFO: Checking fans [2020/08/17 17:31:19] INFO: fan[0] - OK [2020/08/17 17:31:19] INFO: fan[1] - OK [2020/08/17 17:31:19] INFO: fan[2] - OK [2020/08/17 17:31:19] INFO: fan[3] - OK [2020/08/17 17:31:25] INFO: Power ON [2020/08/17 17:31:27] INFO: Starting FPGA queue [2020/08/17 17:31:27] INFO: Initializing hash boards [2020/08/17 17:31:27] INFO: chain[2] - Initializing [2020/08/17 17:31:27] INFO: chain[1] - Initializing [2020/08/17 17:31:27] INFO: chain[0] - Initializing [2020/08/17 17:31:42] WARN: chain[2] - 24 of 44 chips detected [2020/08/17 17:31:43] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies [2020/08/17 17:31:44] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies [2020/08/17 17:31:45] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies [2020/08/17 17:31:45] WARN: chain[1] - 0 of 44 chips detected [2020/08/17 17:31:46] INFO: chain[0] - 44 chips detected [2020/08/17 17:31:54] WARN: chain[2] - 24 of 44 chips detected [2020/08/17 17:31:57] WARN: chain[1] - 20 of 44 chips detected [2020/08/17 17:32:05] WARN: chain[2] - 24 of 44 chips detected [2020/08/17 17:32:05] ERROR: driver-btm-chain.c:488 chain[2] - Failed to detect ASIC chips [2020/08/17 17:32:05] INFO: chain[2] - Shutting down the chain [2020/08/17 17:32:06] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed [2020/08/17 17:32:08] WARN: chain[1] - 20 of 44 chips detected [2020/08/17 17:32:08] ERROR: driver-btm-chain.c:488 chain[1] - Failed to detect ASIC chips [2020/08/17 17:32:08] INFO: chain[1] - Shutting down the chain [2020/08/17 17:32:09] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed [2020/08/17 17:32:12] INFO: Start-up temperature is 21 C (min -15 C) [2020/08/17 17:32:12] INFO: Switching to manual fan control (100 %) [2020/08/17 17:32:12] INFO: Changing voltage from 19500 to 19000 mV gradually [2020/08/17 17:32:36] INFO: Raising freq from 50 to 700 Mhz gradually [2020/08/17 17:32:49] INFO: Switching to manual fan control (95 %) [2020/08/17 17:32:49] INFO: Start mining! [2020/08/17 17:52:42] INFO: Detected 256 Mb of RAM [2020/08/17 17:52:42] INFO: Switching to manual fan control (30 %) [2020/08/17 17:52:42] INFO: Checking fans [2020/08/17 17:52:43] INFO: fan[0] - OK [2020/08/17 17:52:43] INFO: fan[1] - OK [2020/08/17 17:52:43] INFO: fan[2] - OK [2020/08/17 17:52:43] INFO: fan[3] - OK [2020/08/17 17:52:49] INFO: Power ON [2020/08/17 17:52:51] INFO: Starting FPGA queue [2020/08/17 17:52:51] INFO: Initializing hash boards [2020/08/17 17:52:51] INFO: chain[2] - Initializing [2020/08/17 17:52:51] INFO: chain[1] - Initializing [2020/08/17 17:52:51] INFO: chain[0] - Initializing [2020/08/17 17:53:06] WARN: chain[2] - 24 of 44 chips detected [2020/08/17 17:53:07] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies [2020/08/17 17:53:08] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies [2020/08/17 17:53:09] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies [2020/08/17 17:53:09] WARN: chain[1] - 0 of 44 chips detected [2020/08/17 17:53:10] INFO: chain[0] - 44 chips detected [2020/08/17 17:53:18] WARN: chain[2] - 24 of 44 chips detected [2020/08/17 17:53:19] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies [2020/08/17 17:53:20] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies [2020/08/17 17:53:21] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies [2020/08/17 17:53:21] WARN: chain[1] - 0 of 44 chips detected [2020/08/17 17:53:29] WARN: chain[2] - 24 of 44 chips detected [2020/08/17 17:53:29] ERROR: driver-btm-chain.c:488 chain[2] - Failed to detect ASIC chips [2020/08/17 17:53:29] INFO: chain[2] - Shutting down the chain [2020/08/17 17:53:30] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed [2020/08/17 17:53:30] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies [2020/08/17 17:53:31] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies [2020/08/17 17:53:32] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies [2020/08/17 17:53:32] WARN: chain[1] - 0 of 44 chips detected [2020/08/17 17:53:32] ERROR: driver-btm-chain.c:488 chain[1] - Failed to detect ASIC chips [2020/08/17 17:53:32] INFO: chain[1] - Shutting down the chain [2020/08/17 17:53:33] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed [2020/08/17 17:53:36] INFO: Start-up temperature is 20 C (min -15 C) [2020/08/17 17:53:36] INFO: Switching to manual fan control (100 %) [2020/08/17 17:53:36] INFO: Changing voltage from 19500 to 19000 mV gradually [2020/08/17 17:54:00] INFO: Raising freq from 50 to 700 Mhz gradually [2020/08/17 17:54:13] INFO: Switching to manual fan control (90 %) [2020/08/17 17:54:13] INFO: Start mining!
|
Nem.io
|
|
|
mikeywith
Legendary
Offline
Activity: 2408
Merit: 6618
be constructive or S.T.F.U
|
|
August 17, 2020, 08:10:15 PM Last edit: August 18, 2020, 03:03:47 AM by frodocooper Merited by amirheavy666 (1) |
|
What do you mean by resetting it manually? At which point do you get this output? [2020/08/17 17:53:09] WARN: chain[1] - 0 of 44 chips detected [2020/08/17 17:53:10] INFO: chain[0] - 44 chips detected [2020/08/17 17:53:18] WARN: chain[2] - 24 of 44 chips detected
Anyway, to answer your question, you need to go Miner Configuration > Chain Frequency settings Notice that there are two "Chain Frequency settings" tabs, you want the second to the left, scroll down and set the voltage and frequency you want. Before you do that I suggest you go to Miner Configuration > Profile Setting Go to Preset and chose a low-profile, let it run for about an hour and then see if that fix anything if not then simply disable the profile and go to Chain Frequency settings and set low-frequency on your chain 1 and 2 ( 0 seems to be fine showing 44 asics as it should). Please note that your chances are slim to nothing, but it still worth the try.
|
|
|
|
amirheavy666 (OP)
Full Member
Offline
Activity: 228
Merit: 101
NEM (XEM) Top Coin
|
|
August 21, 2020, 04:23:41 PM |
|
Dear Mikeywith my t17+ have this log now..and after 15 min power off automatically and again miner work for 15 min ...i don't know whats the problem...please guide me ...thanks [1970/01/01 00:05:10] INFO: Detected 256 Mb of RAM [1970/01/01 00:05:10] INFO: Switching to manual fan control (30 %) [1970/01/01 00:05:10] INFO: Checking fans [1970/01/01 00:05:15] INFO: fan[0] - OK [1970/01/01 00:05:15] INFO: fan[1] - OK [1970/01/01 00:05:15] INFO: fan[2] - OK [1970/01/01 00:05:15] INFO: fan[3] - OK [1970/01/01 00:05:21] INFO: Power ON [1970/01/01 00:05:23] INFO: Starting FPGA queue [1970/01/01 00:05:23] INFO: Initializing hash boards [1970/01/01 00:05:23] INFO: chain[2] - Initializing [1970/01/01 00:05:23] INFO: chain[1] - Initializing [1970/01/01 00:05:23] INFO: chain[0] - Initializing [1970/01/01 00:05:36] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [1970/01/01 00:05:37] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [1970/01/01 00:05:38] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [1970/01/01 00:05:38] WARN: chain[2] - 0 of 44 chips detected [1970/01/01 00:05:39] INFO: chain[1] - 44 chips detected [1970/01/01 00:05:40] INFO: chain[0] - 44 chips detected [1970/01/01 00:05:48] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [1970/01/01 00:05:49] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [1970/01/01 00:05:50] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [1970/01/01 00:05:50] WARN: chain[2] - 0 of 44 chips detected [1970/01/01 00:05:59] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [1970/01/01 00:06:00] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [1970/01/01 00:06:01] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [1970/01/01 00:06:01] WARN: chain[2] - 0 of 44 chips detected [1970/01/01 00:06:01] ERROR: driver-btm-chain.c:488 chain[2] - Failed to detect ASIC chips [1970/01/01 00:06:01] INFO: chain[2] - Shutting down the chain [1970/01/01 00:06:02] ERROR: driver-btm-base.c:356 chain[2] - Initialization failed [1970/01/01 00:06:05] INFO: Start-up temperature is 30 C (min -15 C) [1970/01/01 00:06:05] INFO: Switching to manual fan control (100 %) [1970/01/01 00:06:05] INFO: Changing voltage from 19500 to 18500 mV gradually [1970/01/01 00:06:35] INFO: Raising freq from 50 to 650 Mhz gradually [1970/01/01 00:06:48] INFO: Switching to manual fan control (96 %) [1970/01/01 00:06:48] INFO: Start mining! [1970/01/01 00:07:48] INFO: Changing voltage from 18500 to 18300 mV gradually [1970/01/01 00:08:12] INFO: Changing voltage from 18300 to 18200 mV gradually [1970/01/01 00:10:24] INFO: Changing voltage from 18200 to 18100 mV gradually [1970/01/01 00:11:36] INFO: Changing voltage from 18100 to 18000 mV gradually [1970/01/01 00:12:49] INFO: Changing voltage from 18000 to 17900 mV gradually [1970/01/01 00:14:02] INFO: Changing voltage from 17900 to 17800 mV gradually [1970/01/01 00:15:15] INFO: Changing voltage from 17800 to 17700 mV gradually [1970/01/01 00:16:28] INFO: Changing voltage from 17700 to 17600 mV gradually [1970/01/01 00:17:41] INFO: Changing voltage from 17600 to 17500 mV gradually [1970/01/01 00:18:54] INFO: Changing voltage from 17500 to 17400 mV gradually [1970/01/01 00:20:02] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [1970/01/01 00:20:03] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [1970/01/01 00:20:05] ERROR: src/chip139x.c:1049 chain[0] - Failed to receive chip replies [1970/01/01 00:20:06] ERROR: src/chip139x.c:1049 chain[0] - Failed to receive chip replies [1970/01/01 00:20:07] INFO: Changing voltage from 17400 to 17300 mV gradually [1970/01/01 00:20:07] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [1970/01/01 00:20:08] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [1970/01/01 00:20:10] ERROR: src/temp.c:217 chain[1] sen[1] - Lost, no updates for 10 sec [1970/01/01 00:20:10] ERROR: src/chip139x.c:1049 chain[0] - Failed to receive chip replies [1970/01/01 00:20:11] ERROR: src/temp.c:217 chain[0] sen[0] - Lost, no updates for 10 sec [1970/01/01 00:20:11] ERROR: src/temp.c:217 chain[0] sen[1] - Lost, no updates for 10 sec [1970/01/01 00:20:11] ERROR: src/temp.c:217 chain[0] sen[2] - Lost, no updates for 10 sec [1970/01/01 00:20:11] ERROR: src/temp.c:217 chain[0] sen[3] - Lost, no updates for 10 sec [1970/01/01 00:20:11] ERROR: driver-btm-chain.c:967 chain[0] - Failed to read temp from all sensors! [1970/01/01 00:20:11] INFO: chain[0] - Shutting down the chain [1970/01/01 00:20:11] ERROR: src/chip139x.c:1049 chain[0] - Failed to receive chip replies [1970/01/01 00:20:12] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [1970/01/01 00:20:13] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [1970/01/01 00:20:15] ERROR: src/temp.c:217 chain[1] sen[0] - Lost, no updates for 10 sec [1970/01/01 00:20:15] ERROR: src/temp.c:217 chain[1] sen[2] - Lost, no updates for 10 sec [1970/01/01 00:20:15] ERROR: src/temp.c:217 chain[1] sen[3] - Lost, no updates for 10 sec [1970/01/01 00:20:15] ERROR: driver-btm-chain.c:967 chain[1] - Failed to read temp from all sensors! [1970/01/01 00:20:15] INFO: chain[1] - Shutting down the chain [1970/01/01 00:20:15] ERROR: src/chip139x.c:1049 chain[0] - Failed to receive chip replies [1970/01/01 00:20:16] ERROR: src/chip139x.c:1049 chain[0] - Failed to receive chip replies [1970/01/01 00:20:17] WARN: No working chains [1970/01/01 00:20:17] INFO: Shutting down the miner [1970/01/01 00:20:17] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [1970/01/01 00:20:18] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [1970/01/01 00:20:19] INFO: Stopping FPGA queue [1970/01/01 00:20:19] INFO: chain[0] - Shutting down the chain [1970/01/01 00:20:19] INFO: chain[1] - Shutting down the chain [1970/01/01 00:20:19] INFO: chain[2] - Shutting down the chain [1970/01/01 00:20:19] INFO: Power OFF
|
Nem.io
|
|
|
BitMaxz
Legendary
Offline
Activity: 3430
Merit: 3165
Playbet.io - Crypto Casino and Sportsbook
|
|
August 21, 2020, 06:23:13 PM Last edit: August 22, 2020, 01:30:22 AM by frodocooper |
|
According to your logs "Failed to receive chip replies" your hashboard might be overheating that could lead to miner autoshutdown for overheating protection. The solution is already on the above post by mikeywith reducing the frequency might solve the issue. If not, try to increase the fan speed or set it fixed to the maximum. You can also, try to downvolt and manually set it to the lower frequency just to get rid of this issue. The guide is already on asic.to manual or download it from here https://asic.to/download/manual_english/And check this part. Enable the #3 for auto downscale if the HW errors still occur.
|
|
|
|
amirheavy666 (OP)
Full Member
Offline
Activity: 228
Merit: 101
NEM (XEM) Top Coin
|
|
August 21, 2020, 07:14:15 PM |
|
I did it but error is stable yet [2020/08/21 19:08:07] INFO: Detected 256 Mb of RAM [2020/08/21 19:08:07] INFO: Switching to manual fan control (30 %) [2020/08/21 19:08:07] INFO: Checking fans [2020/08/21 19:08:08] INFO: fan[0] - OK [2020/08/21 19:08:08] INFO: fan[1] - OK [2020/08/21 19:08:08] INFO: fan[2] - OK [2020/08/21 19:08:08] INFO: fan[3] - OK [2020/08/21 19:08:14] INFO: Power ON [2020/08/21 19:08:17] INFO: Starting FPGA queue [2020/08/21 19:08:17] INFO: Initializing hash boards [2020/08/21 19:08:17] INFO: chain[2] - Initializing [2020/08/21 19:08:17] INFO: chain[1] - Initializing [2020/08/21 19:08:17] INFO: chain[0] - Initializing [2020/08/21 19:08:30] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [2020/08/21 19:08:31] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [2020/08/21 19:08:32] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [2020/08/21 19:08:32] WARN: chain[2] - 0 of 44 chips detected [2020/08/21 19:08:33] INFO: chain[1] - 44 chips detected [2020/08/21 19:08:34] INFO: chain[0] - 44 chips detected [2020/08/21 19:08:41] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [2020/08/21 19:08:42] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [2020/08/21 19:08:43] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [2020/08/21 19:08:43] WARN: chain[2] - 0 of 44 chips detected [2020/08/21 19:08:53] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [2020/08/21 19:08:54] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [2020/08/21 19:08:55] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [2020/08/21 19:08:55] WARN: chain[2] - 0 of 44 chips detected [2020/08/21 19:08:55] ERROR: driver-btm-chain.c:488 chain[2] - Failed to detect ASIC chips [2020/08/21 19:08:55] INFO: chain[2] - Shutting down the chain [2020/08/21 19:08:56] ERROR: driver-btm-base.c:356 chain[2] - Initialization failed [2020/08/21 19:08:59] INFO: Start-up temperature is 31 C (min -15 C) [2020/08/21 19:08:59] INFO: Switching to manual fan control (100 %) [2020/08/21 19:08:59] INFO: Changing voltage from 19500 to 16000 mV gradually [2020/08/21 19:09:45] INFO: Raising freq from 50 to 400 Mhz gradually [2020/08/21 19:09:52] INFO: Switching to manual fan control (96 %) [2020/08/21 19:09:52] INFO: Start mining! [2020/08/21 19:10:52] INFO: Changing voltage from 16000 to 15800 mV gradually [2020/08/21 19:11:18] INFO: Changing voltage from 15800 to 15600 mV gradually [2020/08/21 19:11:44] INFO: Changing voltage from 15600 to 15400 mV gradually [2020/08/21 19:12:09] ERROR: src/chip139x.c:1049 chain[0] - Failed to receive chip replies [2020/08/21 19:12:10] ERROR: src/chip139x.c:1049 chain[0] - Failed to receive chip replies [2020/08/21 19:12:11] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [2020/08/21 19:12:12] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [2020/08/21 19:12:14] ERROR: src/chip139x.c:1049 chain[0] - Failed to receive chip replies [2020/08/21 19:12:15] ERROR: src/chip139x.c:1049 chain[0] - Failed to receive chip replies [2020/08/21 19:12:16] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [2020/08/21 19:12:17] ERROR: src/temp.c:217 chain[0] sen[3] - Lost, no updates for 10 sec [2020/08/21 19:12:17] ERROR: src/temp.c:217 chain[1] sen[0] - Lost, no updates for 10 sec [2020/08/21 19:12:17] ERROR: src/temp.c:217 chain[1] sen[1] - Lost, no updates for 10 sec [2020/08/21 19:12:17] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [2020/08/21 19:12:18] ERROR: src/temp.c:217 chain[0] sen[0] - Lost, no updates for 10 sec [2020/08/21 19:12:18] ERROR: src/temp.c:217 chain[0] sen[1] - Lost, no updates for 10 sec [2020/08/21 19:12:18] ERROR: src/temp.c:217 chain[0] sen[2] - Lost, no updates for 10 sec [2020/08/21 19:12:18] ERROR: driver-btm-chain.c:967 chain[0] - Failed to read temp from all sensors! [2020/08/21 19:12:18] INFO: chain[0] - Shutting down the chain [2020/08/21 19:12:19] ERROR: src/chip139x.c:1049 chain[0] - Failed to receive chip replies [2020/08/21 19:12:20] ERROR: src/temp.c:217 chain[1] sen[2] - Lost, no updates for 10 sec [2020/08/21 19:12:20] ERROR: src/temp.c:217 chain[1] sen[3] - Lost, no updates for 10 sec [2020/08/21 19:12:20] ERROR: driver-btm-chain.c:967 chain[1] - Failed to read temp from all sensors! [2020/08/21 19:12:20] INFO: chain[1] - Shutting down the chain [2020/08/21 19:12:20] ERROR: src/chip139x.c:1049 chain[0] - Failed to receive chip replies [2020/08/21 19:12:21] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [2020/08/21 19:12:22] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [2020/08/21 19:12:23] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=1164 mV tgt=15400 mV [2020/08/21 19:12:24] WARN: No working chains [2020/08/21 19:12:24] INFO: Shutting down the miner [2020/08/21 19:12:24] INFO: Stopping FPGA queue [2020/08/21 19:12:24] INFO: chain[0] - Shutting down the chain [2020/08/21 19:12:24] INFO: chain[1] - Shutting down the chain [2020/08/21 19:12:24] INFO: chain[2] - Shutting down the chain [2020/08/21 19:12:24] INFO: Power OFF
|
Nem.io
|
|
|
mikeywith
Legendary
Offline
Activity: 2408
Merit: 6618
be constructive or S.T.F.U
|
|
August 21, 2020, 07:27:52 PM Last edit: August 22, 2020, 01:31:31 AM by frodocooper |
|
[1970/01/01 00:20:11] ERROR: driver-btm-chain.c:967 chain[0] - Failed to read temp from all sensors!
The kernel log can be very tricky, but this single line suggests that your hash boards might be okay but the power supply isn't feeding them enough power, in other words, your PSU is bad, do you have a spare PSU? This isn't how he should do it, this is the auto-chip tune, he needs to go the next tab and set fixed frequency and voltage for each hashboard.
|
|
|
|
BitMaxz
Legendary
Offline
Activity: 3430
Merit: 3165
Playbet.io - Crypto Casino and Sportsbook
|
|
August 22, 2020, 09:51:16 PM |
|
That was hard to troubleshoot but I think much better to flash it back first on the original Bitmain firmware to check if the miner is fine and to check if it's actually a PSU issue. If the miner is running fine with the original firmware there might be misconfigured on asic.to firmware that causes the issue you might need the help of taserz to tweak your miner. Or your miner is broken and you are trying to fix the issue by using asic.to firmware?
Can you try to run the hashboard one by one? The one hashboard might be broken that can prevent other hashboard to run properly.
|
|
|
|
mikeywith
Legendary
Offline
Activity: 2408
Merit: 6618
be constructive or S.T.F.U
|
|
August 23, 2020, 01:14:21 PM Last edit: August 23, 2020, 09:08:05 PM by mikeywith |
|
That was hard to troubleshoot but I think much better to flash it back first on the original Bitmain firmware to check if the miner is fine and to check if it's actually a PSU issue.
That makes sense, he should try that as well. Can you try to run the hashboard one by one? The one hashboard might be broken that can prevent other hashboard to run properly.
It's unlikely, this used to be the case in the old miners S11 and older IIRC, but since the S15 the control board will simply ignore the bad hash board and move on to the next one, it's even better with Vnish firmware since even if the board needs tunning the other two will work while the bad one gets turned individually, so it's unlikely that 1 board is causing the miner to shut-down. However, it would be worth it to test the hash boards one by one not for the reason you mentioned but for the fact that his PSU could be bad but not totally broken and it may be able to run a single hash board but not 3 of them.
|
|
|
|
amirheavy666 (OP)
Full Member
Offline
Activity: 228
Merit: 101
NEM (XEM) Top Coin
|
|
August 24, 2020, 03:29:00 PM Last edit: August 25, 2020, 02:34:35 AM by frodocooper |
|
Dear Mikeywith and BitMaxz I tried all chain one by one and this is the results (freq 650,700 and voltage 18.5,19.5 (framework asic.to) : chain 1 : work without problem [2020/08/24 14:01:52] INFO: Detected 256 Mb of RAM [2020/08/24 14:01:52] INFO: Switching to manual fan control (30 %) [2020/08/24 14:01:52] INFO: Checking fans [2020/08/24 14:01:53] INFO: fan[0] - OK [2020/08/24 14:01:53] INFO: fan[1] - OK [2020/08/24 14:01:53] INFO: fan[2] - OK [2020/08/24 14:01:53] INFO: fan[3] - OK [2020/08/24 14:01:59] INFO: Power ON [2020/08/24 14:02:01] INFO: Starting FPGA queue [2020/08/24 14:02:04] INFO: Initializing hash boards [2020/08/24 14:02:05] INFO: chain[1] - Initializing [2020/08/24 14:02:07] INFO: chain[1] - 44 chips detected [2020/08/24 14:02:08] INFO: Start-up temperature is 25 C (min -15 C) [2020/08/24 14:02:11] INFO: Switching to manual fan control (100 %) [2020/08/24 14:02:13] INFO: Raising freq from 50 to 700 Mhz gradually [2020/08/24 14:02:17] INFO: Switching to manual fan control (96 %) [2020/08/24 14:02:19] INFO: Start mining!
chain 2: work with this log and shut down [2020/08/24 14:21:13] INFO: Detected 256 Mb of RAM [2020/08/24 14:21:13] INFO: Switching to manual fan control (30 %) [2020/08/24 14:21:13] INFO: Checking fans [2020/08/24 14:21:18] INFO: fan[0] - OK [2020/08/24 14:21:18] INFO: fan[1] - OK [2020/08/24 14:21:18] INFO: fan[2] - OK [2020/08/24 14:21:18] INFO: fan[3] - OK [2020/08/24 14:21:24] INFO: Power ON [2020/08/24 14:21:26] INFO: Starting FPGA queue [2020/08/24 14:21:26] INFO: Initializing hash boards [2020/08/24 14:21:26] INFO: chain[2] - Initializing [2020/08/24 14:21:37] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=608 mV tgt=19500 mV [2020/08/24 14:21:37] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage [2020/08/24 14:21:37] INFO: chain[2] - Shutting down the chain [2020/08/24 14:21:37] ERROR: driver-btm-base.c:356 chain[2] - Initialization failed [2020/08/24 14:21:37] ERROR: driver-btm-base.c:2154 Failed to initialize hash boards [2020/08/24 14:21:37] INFO: Shutting down the miner [2020/08/24 14:21:37] INFO: Stopping FPGA queue [2020/08/24 14:21:37] INFO: chain[2] - Shutting down the chain
chain 3:work without problem : [2020/08/24 15:06:37] INFO: Start mining! [2020/08/24 15:16:49] INFO: Detected 256 Mb of RAM [2020/08/24 15:16:49] INFO: Switching to manual fan control (30 %) [2020/08/24 15:16:49] INFO: Checking fans [2020/08/24 15:16:56] INFO: fan[0] - OK [2020/08/24 15:16:56] INFO: fan[1] - OK [2020/08/24 15:16:56] INFO: fan[2] - OK [2020/08/24 15:16:56] INFO: fan[3] - OK [2020/08/24 15:17:02] INFO: Power ON [2020/08/24 15:17:04] INFO: Starting FPGA queue [2020/08/24 15:17:04] INFO: Initializing hash boards [2020/08/24 15:17:04] INFO: chain[1] - Initializing [2020/08/24 15:17:16] INFO: chain[1] - 44 chips detected [2020/08/24 15:17:22] INFO: Start-up temperature is 25 C (min -15 C) [2020/08/24 15:17:22] INFO: Switching to manual fan control (100 %) [2020/08/24 15:17:22] INFO: Raising freq from 50 to 700 Mhz gradually [2020/08/24 15:17:35] INFO: Switching to manual fan control (96 %) [2020/08/24 15:17:35] INFO: Start mining!
but when connect two chain 1,3 that worked correctly in one mode : [2020/08/24 14:42:13] INFO: Detected 256 Mb of RAM [2020/08/24 14:42:13] INFO: Switching to manual fan control (30 %) [2020/08/24 14:42:13] INFO: Checking fans [2020/08/24 14:42:14] INFO: fan[0] - OK [2020/08/24 14:42:14] INFO: fan[1] - OK [2020/08/24 14:42:14] INFO: fan[2] - OK [2020/08/24 14:42:14] INFO: fan[3] - OK [2020/08/24 14:42:20] INFO: Power ON [2020/08/24 14:42:22] INFO: Starting FPGA queue [2020/08/24 14:42:22] INFO: Initializing hash boards [2020/08/24 14:42:22] INFO: chain[2] - Initializing [2020/08/24 14:42:22] INFO: chain[1] - Initializing [2020/08/24 14:42:35] INFO: chain[2] - 44 chips detected [2020/08/24 14:42:36] INFO: chain[1] - 44 chips detected [2020/08/24 14:42:42] INFO: Start-up temperature is 24 C (min -15 C) [2020/08/24 14:42:42] INFO: Switching to manual fan control (100 %) [2020/08/24 14:42:42] INFO: Changing voltage from 19500 to 18500 mV gradually [2020/08/24 14:43:12] INFO: Raising freq from 50 to 650 Mhz gradually [2020/08/24 14:43:25] INFO: Switching to manual fan control (96 %) [2020/08/24 14:43:25] INFO: Start mining! [2020/08/24 14:46:47] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [2020/08/24 14:46:48] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [2020/08/24 14:46:49] ERROR: src/chip139x.c:1049 chain[2] - Failed to receive chip replies [2020/08/24 14:47:03] INFO: Detected 256 Mb of RAM [2020/08/24 14:47:03] INFO: Switching to manual fan control (30 %) [2020/08/24 14:47:03] INFO: Checking fans [2020/08/24 14:47:04] INFO: fan[0] - OK [2020/08/24 14:47:04] INFO: fan[1] - OK [2020/08/24 14:47:04] INFO: fan[2] - OK [2020/08/24 14:47:04] INFO: fan[3] - OK [2020/08/24 14:47:10] INFO: Power ON [2020/08/24 14:47:12] INFO: Starting FPGA queue [2020/08/24 14:47:12] INFO: Initializing hash boards [2020/08/24 14:47:12] INFO: chain[2] - Initializing [2020/08/24 14:47:12] INFO: chain[1] - Initializing [2020/08/24 14:47:23] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=874 mV tgt=19500 mV [2020/08/24 14:47:23] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage [2020/08/24 14:47:23] INFO: chain[2] - Shutting down the chain [2020/08/24 14:47:23] ERROR: driver-btm-base.c:356 chain[2] - Initialization failed [2020/08/24 14:47:24] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=946 mV tgt=19500 mV [2020/08/24 14:47:24] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage [2020/08/24 14:47:24] INFO: chain[1] - Shutting down the chain [2020/08/24 14:47:24] ERROR: driver-btm-base.c:356 chain[1] - Initialization failed [2020/08/24 14:47:24] ERROR: driver-btm-base.c:2154 Failed to initialize hash boards [2020/08/24 14:47:24] INFO: Shutting down the miner
what do you think about this problem?
|
Nem.io
|
|
|
mikeywith
Legendary
Offline
Activity: 2408
Merit: 6618
be constructive or S.T.F.U
|
|
August 24, 2020, 05:14:09 PM Last edit: August 25, 2020, 02:35:38 AM by frodocooper |
|
so chain 1 alone shows INFO: chain[1] - 44 chips detected chain 2 alone shows ERROR: driver-btm-base.c:2154 Failed to initialize hash boards chain 3 alone shows chain[3] - 44 chips detected chain 3 and 1 showed both hashbaords asics but failed to start, what this suggests is exactly what I said in my previous post The kernel log can be very tricky, but this single line suggests that your hash boards might be okay but the power supply isn't feeding them enough power, in other words, your PSU is bad...
|
|
|
|
amirheavy666 (OP)
Full Member
Offline
Activity: 228
Merit: 101
NEM (XEM) Top Coin
|
|
August 24, 2020, 06:44:12 PM Last edit: August 25, 2020, 02:36:00 AM by frodocooper |
|
Thanks for reply... can i use power miner t17 40th/s or other model power for t17+ 55 ths or exactly my power must be t17+55 and can't be t17+58 or others ?
|
Nem.io
|
|
|
mikeywith
Legendary
Offline
Activity: 2408
Merit: 6618
be constructive or S.T.F.U
|
|
August 24, 2020, 08:21:16 PM Last edit: August 25, 2020, 02:37:01 AM by frodocooper |
|
You need to use APW9+ and not APW9, in other words any power supply that works on T17+ will work on S17e, T17e, S17+ and vice versa obviously, but T17, S17 and S17 pro use APW9 which won't work on your miner.
APW9 > S17, T17, S17pro
APW9+ > S17e, T17e, S17+, T17+
|
|
|
|
amirheavy666 (OP)
Full Member
Offline
Activity: 228
Merit: 101
NEM (XEM) Top Coin
|
|
August 26, 2020, 04:36:39 PM Last edit: August 28, 2020, 01:39:52 AM by frodocooper |
|
thanks , 2chain work for 15 minutes without any problem and have this log on below. [2020/08/26 16:11:56] INFO: fan[1] - OK [2020/08/26 16:11:56] INFO: fan[2] - OK [2020/08/26 16:11:56] INFO: fan[3] - OK [2020/08/26 16:12:02] INFO: Power ON [2020/08/26 16:12:04] INFO: Starting FPGA queue [2020/08/26 16:12:04] INFO: Initializing hash boards [2020/08/26 16:12:04] INFO: chain[2] - Initializing [2020/08/26 16:12:04] INFO: chain[1] - Initializing [2020/08/26 16:12:17] INFO: chain[2] - 44 chips detected [2020/08/26 16:12:18] INFO: chain[1] - 44 chips detected [2020/08/26 16:12:24] INFO: Start-up temperature is 27 C (min -15 C) [2020/08/26 16:12:24] INFO: Switching to manual fan control (100 %) [2020/08/26 16:12:24] INFO: Changing voltage from 19500 to 19000 mV gradually [2020/08/26 16:12:51] INFO: Raising freq from 50 to 700 Mhz gradually [2020/08/26 16:13:04] INFO: Switching to automatic fan control (75 C) [2020/08/26 16:13:04] INFO: Start mining! [2020/08/26 16:14:04] INFO: Changing voltage from 19000 to 18800 mV gradually [2020/08/26 16:14:29] INFO: Changing voltage from 18800 to 18600 mV gradually [2020/08/26 16:14:54] INFO: Changing voltage from 18600 to 18500 mV gradually [2020/08/26 16:26:56] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [2020/08/26 16:26:57] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [2020/08/26 16:27:23] INFO: Detected 256 Mb of RAM [2020/08/26 16:27:23] INFO: Switching to manual fan control (30 %) [2020/08/26 16:27:23] INFO: Checking fans [2020/08/26 16:27:24] INFO: fan[0] - OK [2020/08/26 16:27:24] INFO: fan[1] - OK [2020/08/26 16:27:24] INFO: fan[2] - OK [2020/08/26 16:27:24] INFO: fan[3] - OK [2020/08/26 16:27:30] INFO: Power ON [2020/08/26 16:27:32] ERROR: src/power.c:161 Malformed power response [2020/08/26 16:27:34] INFO: Starting FPGA queue [2020/08/26 16:27:34] INFO: Initializing hash boards [2020/08/26 16:27:34] INFO: chain[2] - Initializing [2020/08/26 16:27:34] INFO: chain[1] - Initializing [2020/08/26 16:27:45] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=801 mV tgt=19500 mV [2020/08/26 16:27:45] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage [2020/08/26 16:27:45] INFO: chain[2] - Shutting down the chain [2020/08/26 16:27:45] ERROR: driver-btm-base.c:356 chain[2] - Initialization failed [2020/08/26 16:27:46] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=874 mV tgt=19500 mV [2020/08/26 16:27:46] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage [2020/08/26 16:27:46] INFO: chain[1] - Shutting down the chain [2020/08/26 16:27:46] ERROR: driver-btm-base.c:356 chain[1] - Initialization failed [2020/08/26 16:27:46] ERROR: driver-btm-base.c:2154 Failed to initialize hash boards [2020/08/26 16:27:46] INFO: Shutting down the miner [2020/08/26 16:27:46] INFO: Stopping FPGA queue [2020/08/26 16:27:46] INFO: chain[1] - Shutting down the chain [2020/08/26 16:27:46] INFO: chain[2] - Shutting down the chain [2020/08/26 16:27:46] INFO: Power OFF
after about 5 min this log happen, and miner continue mining without problem: [2020/08/26 16:14:04] INFO: Changing voltage from 19000 to 18800 mV gradually [2020/08/26 16:14:29] INFO: Changing voltage from 18800 to 18600 mV gradually [2020/08/26 16:14:54] INFO: Changing voltage from 18600 to 18500 mV gradually
but after about 15 min this log showed : (do you know which part of power have problem with this comment "Malformed power" [2020/08/26 16:26:56] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [2020/08/26 16:26:57] ERROR: src/chip139x.c:1049 chain[1] - Failed to receive chip replies [2020/08/26 16:27:32] ERROR: src/power.c:161 Malformed power response
|
Nem.io
|
|
|
philipma1957
Legendary
Online
Activity: 4298
Merit: 8804
'The right to privacy matters'
|
|
August 26, 2020, 04:44:45 PM Last edit: August 28, 2020, 01:40:17 AM by frodocooper |
|
disconnect chain 1 as it looks to have a bad chip.
|
|
|
|
amirheavy666 (OP)
Full Member
Offline
Activity: 228
Merit: 101
NEM (XEM) Top Coin
|
|
August 26, 2020, 04:59:47 PM Last edit: August 28, 2020, 01:40:55 AM by frodocooper |
|
Can i disable this chip139x.c:1049 only in chain 1 and other chips work in this chain? because i use framework asic.to?
|
Nem.io
|
|
|
BitMaxz
Legendary
Offline
Activity: 3430
Merit: 3165
Playbet.io - Crypto Casino and Sportsbook
|
|
August 26, 2020, 09:45:55 PM Last edit: August 28, 2020, 01:41:34 AM by frodocooper |
|
I think asic.to firmware won't be able to do that and I think you can only set the frequency of chips but you can't be able to disable the broken chip. However, you can try to change the frequency of that chip under chip frequency settings. Find that broken chip and set the freq to lowest.
|
|
|
|
mikeywith
Legendary
Offline
Activity: 2408
Merit: 6618
be constructive or S.T.F.U
|
|
August 27, 2020, 06:22:49 PM Last edit: August 28, 2020, 01:41:55 AM by frodocooper |
|
You need to replace the PSU, there isn't much of work arounds you can do fix this, your best option would be running a singel hash boards at pretty low settings until the new psu arrives, although if i were you i would shut it down and wait for the new psu to make sure i don't harm more things.
One thing worth mentioning that lower/higher voltage than what bitmain specifies will kill the new psu as well, make sure your voltage is between 200-240v.
|
|
|
|
amirheavy666 (OP)
Full Member
Offline
Activity: 228
Merit: 101
NEM (XEM) Top Coin
|
|
September 04, 2020, 10:53:06 AM Last edit: September 04, 2020, 11:35:37 PM by frodocooper |
|
Thanks mikeywith. I gave my power to technician to repair it. after fixed it , I'll check and give u the results.
|
Nem.io
|
|
|
|