Ninjastic
Search content
Sort by
Showing 15 of 15 results by katatunix
Post
Topic
Board Mining support
Topic OP
Antminer S9 not hashing
by
katatunix
on 20/10/2020, 13:06:38 UTC
My S9 is using the newest firmware from the Bitmain website https://service.bitmain.com/support/download?product=Antminer%20S9

It had run well for one or two months. Then I turned it off for a few months. However, at the moment, the problem is that it is not hashing. Pool connection seems OK as I see the Status "Alive" in the "Miner Status" tab.

I tried to reset the miner using the "IP Reporter" button but no luck.

Below is Kernel Log:

Code:
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.0-xilinx-g16220c3 (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #83 SMP PREEMPT Thu Jul 12 11:42:53 CST 2018
[    0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Xilinx Zynq
[    0.000000] cma: CMA: reserved 128 MiB at 27800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 258048
[    0.000000] free_area_init_node: node 0, pgdat c074ac00, node_mem_map e6fd8000
[    0.000000]   Normal zone: 1520 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 194560 pages, LIFO batch:31
[    0.000000]   HighMem zone: 496 pages used for memmap
[    0.000000]   HighMem zone: 63488 pages, LIFO batch:15
[    0.000000] PERCPU: Embedded 8 pages/cpu @e6fc0000 s9088 r8192 d15488 u32768
[    0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 256528
[    0.000000] Kernel command line: noinitrd mem=1008M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 884108K/1032192K available (5057K kernel code, 284K rwdata, 1928K rodata, 204K init, 258K bss, 148084K reserved, 253952K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06da8ac   (6987 kB)
[    0.000000]       .init : 0xc06db000 - 0xc070e380   ( 205 kB)
[    0.000000]       .data : 0xc0710000 - 0xc0757138   ( 285 kB)
[    0.000000]        .bss : 0xc0757144 - 0xc0797bfc   ( 259 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[    0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] ps7-slcr mapped to f0004000
[    0.000000] zynq_clock_init: clkc starts at f0004100
[    0.000000] Zynq clock init
[    0.000014] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[    0.000293] ps7-ttc #0 at f0006000, irq=43
[    0.000594] Console: colour dummy device 80x30
[    0.000630] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[    0.090243] pid_max: default: 32768 minimum: 301
[    0.090453] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.090475] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.092629] CPU: Testing write buffer coherency: ok
[    0.092952] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.093009] Setting up static identity map for 0x4cb118 - 0x4cb170
[    0.093229] L310 cache controller enabled
[    0.093250] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[    0.170988] CPU1: Booted secondary processor
[    0.260220] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.260348] Brought up 2 CPUs
[    0.260368] SMP: Total of 2 processors activated.
[    0.260376] CPU: All CPU(s) started in SVC mode.
[    0.261051] devtmpfs: initialized
[    0.263464] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.264652] regulator-dummy: no parameters
[    0.271509] NET: Registered protocol family 16
[    0.273784] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.276038] cpuidle: using governor ladder
[    0.276051] cpuidle: using governor menu
[    0.283416] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.284920] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.284934] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.285043] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xf0080000
[    0.306625] bio: create slab <bio-0> at 0
[    0.308018] vgaarb: loaded
[    0.308737] SCSI subsystem initialized
[    0.309607] usbcore: registered new interface driver usbfs
[    0.309793] usbcore: registered new interface driver hub
[    0.310018] usbcore: registered new device driver usb
[    0.310682] media: Linux media interface: v0.10
[    0.310838] Linux video capture interface: v2.00
[    0.311442] pps_core: LinuxPPS API ver. 1 registered
[    0.311454] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.311588] PTP clock support registered
[    0.311933] EDAC MC: Ver: 3.0.0
[    0.313121] Advanced Linux Sound Architecture Driver Initialized.
[    0.315846] DMA-API: preallocated 4096 debug entries
[    0.315858] DMA-API: debugging enabled by kernel config
[    0.315928] Switched to clocksource arm_global_timer
[    0.336124] NET: Registered protocol family 2
[    0.336778] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.336872] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.337031] TCP: Hash tables configured (established 8192 bind 8192)
[    0.337095] TCP: reno registered
[    0.337111] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.337160] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.337412] NET: Registered protocol family 1
[    0.337746] RPC: Registered named UNIX socket transport module.
[    0.337758] RPC: Registered udp transport module.
[    0.337767] RPC: Registered tcp transport module.
[    0.337775] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.337786] PCI: CLS 0 bytes, default 64
[    0.338210] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.340200] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.341568] bounce pool size: 64 pages
[    0.342437] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.342641] msgmni has been set to 1486
[    0.343395] io scheduler noop registered
[    0.343409] io scheduler deadline registered
[    0.343449] io scheduler cfq registered (default)
[    0.355673] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.355693] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.478687] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    1.050741] console [ttyPS0] enabled
[    1.054981] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to f0068000
[    1.062587] [drm] Initialized drm 1.1.0 20060810
[    1.079562] brd: module loaded
[    1.088950] loop: module loaded
[    1.098346] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.104098] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.112151] libphy: XEMACPS mii bus: probed
[    1.116719] ------------- phy_id = 0x3625e62
[    1.121440] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.130081] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.136733] ehci-pci: EHCI PCI platform driver
[    1.143936] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[    1.150768] usbcore: registered new interface driver usb-storage
[    1.157628] mousedev: PS/2 mouse device common for all mice
[    1.163709] i2c /dev entries driver
[    1.170637] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[    1.176162] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.182020] Xilinx Zynq CpuIdle Driver started
[    1.186898] sdhci: Secure Digital Host Controller Interface driver
[    1.192989] sdhci: Copyright(c) Pierre Ossman
[    1.197355] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.204137] mmc0: no vqmmc regulator found
[    1.208220] mmc0: no vmmc regulator found
[    1.245947] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.254610] usbcore: registered new interface driver usbhid
[    1.260122] usbhid: USB HID core driver
[    1.264819] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.271114] nand: Micron MT29F2G08ABAEAWP
[    1.275080] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.281029] Bad block table found at page 131008, version 0x01
[    1.287256] Bad block table found at page 130944, version 0x01
[    1.293304] 3 ofpart partitions found on MTD device pl353-nand
[    1.299089] Creating 3 MTD partitions on "pl353-nand":
[    1.304179] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.312206] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.319525] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[    1.330227] TCP: cubic registered
[    1.333461] NET: Registered protocol family 17
[    1.338156] Registering SWP/SWPB emulation handler
[    1.344071] regulator-dummy: disabling
[    1.348399] UBI: attaching mtd1 to ubi0
[    1.657320] UBI: scanning is finished
[    1.677859] UBI: volume 0 ("rootfs") re-sized from 192 to 1108 LEBs
[    1.684915] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[    1.691995] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.698760] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.705424] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.712302] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[    1.718283] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.725390] UBI: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1113221046
[    1.734433] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[    1.743649] UBI: background thread "ubi_bgt0d" started, PID 1084
[    1.743654] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.747608] ALSA device list:
[    1.747611]   No soundcards found.
[    1.766145] UBIFS: background thread "ubifs_bgt0_0" started, PID 1086
[    1.838291] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    1.844217] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    1.853364] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    1.863241] UBIFS: reserved for root: 0 bytes (0 KiB)
[    1.868277] UBIFS: media format: w4/r0 (latest is w4/r0), UUID E8A4479F-B15D-4C7A-964D-0F246E2BB6ED, small LPT model
[    1.888578] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    2.000873] devtmpfs: mounted
[    2.003982] Freeing unused kernel memory: 204K (c06db000 - c070e000)
[    3.268115] random: dd urandom read with 1 bits of entropy available
[    3.875945]
[    3.875945] bcm54xx_config_init
[    4.985968]
[    4.985968] bcm54xx_config_init
[    7.986813] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[    7.992900] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[   21.416469] In axi fpga driver!
[   21.419541] request_mem_region OK!
[   21.422937] AXI fpga dev virtual address is 0xf0200000
[   21.428068] *base_vir_addr = 0xc51e
[   21.442664] In fpga mem driver!
[   21.446087] request_mem_region OK!
[   21.449600] fpga mem virtual address is 0xf3000000
[   22.215976]
[   22.215976] bcm54xx_config_init
[   23.295979]
[   23.295979] bcm54xx_config_init
[   26.296813] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[   26.302830] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[ 1086.424488] random: nonblocking pool is initialized
main.c:13992: log_level = 4
main.c:14019: This is XILINX board. Totalram:       1039753216
main.c:14025: Detect 1GB control board of XILINX
driver-bitmain.c:1776: mmap axi_fpga_addr = 0xb6f55000
driver-bitmain.c:1781: axi_fpga_addr data = 0xc51e
driver-bitmain.c:1797: mmap fpga_mem_addr = 0xb5d4e000
driver-bitmain.c:994: forceFreq=-1 forceFlag=0
driver-bitmain.c:1696: min work minertest[0]:912


main.c:8570: DETECT HW version=0000c51e
main.c:14064: miner ID : 8128ed8162bb8854
main.c:14089: Miner Type = S9
main.c:14101: AsicType = 1387
main.c:14104: real AsicNum = 63
main.c:14197: use critical mode to search freq...
driver-bitmain.c:1876: get PLUG ON=0x000000e0
driver-bitmain.c:1946: Find hashboard on Chain[5]
driver-bitmain.c:1946: Find hashboard on Chain[6]
driver-bitmain.c:1946: Find hashboard on Chain[7]
main.c:2282: Check chain[5] PIC fw version=0x03
main.c:2282: Check chain[6] PIC fw version=0x03
main.c:2282: Check chain[7] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[5]: [44:101] [38:104] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
main.c:8974: Chain[5] disabled chip[38] core[104]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[5] has freq in PIC and will jump over...
main.c:9103: Chain[5] has core num in PIC
main.c:9113: Chain[5] ASIC[0] has core num=1
main.c:9113: Chain[5] ASIC[1] has core num=2
main.c:9113: Chain[5] ASIC[2] has core num=1
main.c:9113: Chain[5] ASIC[3] has core num=1
main.c:9113: Chain[5] ASIC[4] has core num=1
main.c:9113: Chain[5] ASIC[5] has core num=1
main.c:9113: Chain[5] ASIC[6] has core num=1
main.c:9113: Chain[5] ASIC[7] has core num=1
main.c:9113: Chain[5] ASIC[8] has core num=2
main.c:9113: Chain[5] ASIC[9] has core num=1
main.c:9113: Chain[5] ASIC[11] has core num=1
main.c:9113: Chain[5] ASIC[12] has core num=1
main.c:9113: Chain[5] ASIC[13] has core num=1
main.c:9113: Chain[5] ASIC[14] has core num=1
main.c:9113: Chain[5] ASIC[15] has core num=1
main.c:9113: Chain[5] ASIC[16] has core num=1
main.c:9113: Chain[5] ASIC[17] has core num=1
main.c:9113: Chain[5] ASIC[18] has core num=1
main.c:9113: Chain[5] ASIC[19] has core num=1
main.c:9113: Chain[5] ASIC[20] has core num=1
main.c:9113: Chain[5] ASIC[21] has core num=1
main.c:9113: Chain[5] ASIC[23] has core num=1
main.c:9113: Chain[5] ASIC[24] has core num=1
main.c:9113: Chain[5] ASIC[25] has core num=1
main.c:9113: Chain[5] ASIC[26] has core num=1
main.c:9113: Chain[5] ASIC[27] has core num=1
main.c:9113: Chain[5] ASIC[28] has core num=1
main.c:9113: Chain[5] ASIC[29] has core num=2
main.c:9113: Chain[5] ASIC[30] has core num=1
main.c:9113: Chain[5] ASIC[31] has core num=1
main.c:9113: Chain[5] ASIC[32] has core num=1
main.c:9113: Chain[5] ASIC[33] has core num=1
main.c:9113: Chain[5] ASIC[35] has core num=1
main.c:9113: Chain[5] ASIC[36] has core num=1
main.c:9113: Chain[5] ASIC[37] has core num=1
main.c:9113: Chain[5] ASIC[38] has core num=1
main.c:9113: Chain[5] ASIC[39] has core num=1
main.c:9113: Chain[5] ASIC[40] has core num=1
main.c:9113: Chain[5] ASIC[41] has core num=2
main.c:9113: Chain[5] ASIC[42] has core num=1
main.c:9113: Chain[5] ASIC[43] has core num=2
main.c:9113: Chain[5] ASIC[44] has core num=1
main.c:9113: Chain[5] ASIC[45] has core num=1
main.c:9113: Chain[5] ASIC[46] has core num=1
main.c:9113: Chain[5] ASIC[47] has core num=1
main.c:9113: Chain[5] ASIC[48] has core num=1
main.c:9113: Chain[5] ASIC[49] has core num=1
main.c:9113: Chain[5] ASIC[50] has core num=1
main.c:9113: Chain[5] ASIC[51] has core num=1
main.c:9113: Chain[5] ASIC[52] has core num=1
main.c:9113: Chain[5] ASIC[54] has core num=1
main.c:9113: Chain[5] ASIC[55] has core num=1
main.c:9113: Chain[5] ASIC[56] has core num=1
main.c:9113: Chain[5] ASIC[57] has core num=1
main.c:9113: Chain[5] ASIC[58] has core num=1
main.c:9113: Chain[5] ASIC[59] has core num=1
main.c:9113: Chain[5] ASIC[61] has core num=1
main.c:9113: Chain[5] ASIC[62] has core num=1
main.c:2282: Check chain[5] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[6] has freq in PIC and will jump over...
main.c:9103: Chain[6] has core num in PIC
main.c:9113: Chain[6] ASIC[0] has core num=1
main.c:9113: Chain[6] ASIC[1] has core num=2
main.c:9113: Chain[6] ASIC[2] has core num=1
main.c:9113: Chain[6] ASIC[5] has core num=2
main.c:9113: Chain[6] ASIC[8] has core num=1
main.c:9113: Chain[6] ASIC[9] has core num=1
main.c:9113: Chain[6] ASIC[11] has core num=1
main.c:9113: Chain[6] ASIC[12] has core num=1
main.c:9113: Chain[6] ASIC[13] has core num=1
main.c:9113: Chain[6] ASIC[16] has core num=1
main.c:9113: Chain[6] ASIC[17] has core num=1
main.c:9113: Chain[6] ASIC[19] has core num=1
main.c:9113: Chain[6] ASIC[21] has core num=1
main.c:9113: Chain[6] ASIC[22] has core num=2
main.c:9113: Chain[6] ASIC[23] has core num=1
main.c:9113: Chain[6] ASIC[24] has core num=1
main.c:9113: Chain[6] ASIC[25] has core num=15
main.c:9113: Chain[6] ASIC[26] has core num=1
main.c:9113: Chain[6] ASIC[27] has core num=1
main.c:9113: Chain[6] ASIC[29] has core num=2
main.c:9113: Chain[6] ASIC[30] has core num=2
main.c:9113: Chain[6] ASIC[31] has core num=1
main.c:9113: Chain[6] ASIC[32] has core num=1
main.c:9113: Chain[6] ASIC[34] has core num=1
main.c:9113: Chain[6] ASIC[35] has core num=1
main.c:9113: Chain[6] ASIC[36] has core num=1
main.c:9113: Chain[6] ASIC[37] has core num=1
main.c:9113: Chain[6] ASIC[38] has core num=3
main.c:9113: Chain[6] ASIC[40] has core num=1
main.c:9113: Chain[6] ASIC[41] has core num=1
main.c:9113: Chain[6] ASIC[42] has core num=3
main.c:9113: Chain[6] ASIC[43] has core num=2
main.c:9113: Chain[6] ASIC[45] has core num=1
main.c:9113: Chain[6] ASIC[46] has core num=1
main.c:9113: Chain[6] ASIC[47] has core num=1
main.c:9113: Chain[6] ASIC[50] has core num=1
main.c:9113: Chain[6] ASIC[51] has core num=2
main.c:9113: Chain[6] ASIC[52] has core num=1
main.c:9113: Chain[6] ASIC[53] has core num=1
main.c:9113: Chain[6] ASIC[54] has core num=1
main.c:9113: Chain[6] ASIC[55] has core num=1
main.c:9113: Chain[6] ASIC[56] has core num=1
main.c:9113: Chain[6] ASIC[58] has core num=15
main.c:9113: Chain[6] ASIC[59] has core num=1
main.c:9113: Chain[6] ASIC[60] has core num=2
main.c:9113: Chain[6] ASIC[61] has core num=1
main.c:9113: Chain[6] ASIC[62] has core num=1
main.c:2282: Check chain[6] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[7] has freq in PIC and will jump over...
main.c:9103: Chain[7] has core num in PIC
main.c:9113: Chain[7] ASIC[0] has core num=1
main.c:9113: Chain[7] ASIC[1] has core num=2
main.c:9113: Chain[7] ASIC[2] has core num=2
main.c:9113: Chain[7] ASIC[3] has core num=1
main.c:9113: Chain[7] ASIC[4] has core num=1
main.c:9113: Chain[7] ASIC[6] has core num=1
main.c:9113: Chain[7] ASIC[7] has core num=2
main.c:9113: Chain[7] ASIC[8] has core num=1
main.c:9113: Chain[7] ASIC[9] has core num=1
main.c:9113: Chain[7] ASIC[10] has core num=4
main.c:9113: Chain[7] ASIC[11] has core num=1
main.c:9113: Chain[7] ASIC[12] has core num=1
main.c:9113: Chain[7] ASIC[14] has core num=1
main.c:9113: Chain[7] ASIC[15] has core num=1
main.c:9113: Chain[7] ASIC[16] has core num=1
main.c:9113: Chain[7] ASIC[17] has core num=1
main.c:9113: Chain[7] ASIC[18] has core num=1
main.c:9113: Chain[7] ASIC[19] has core num=1
main.c:9113: Chain[7] ASIC[20] has core num=1
main.c:9113: Chain[7] ASIC[21] has core num=1
main.c:9113: Chain[7] ASIC[22] has core num=1
main.c:9113: Chain[7] ASIC[23] has core num=1
main.c:9113: Chain[7] ASIC[24] has core num=1
main.c:9113: Chain[7] ASIC[26] has core num=1
main.c:9113: Chain[7] ASIC[27] has core num=1
main.c:9113: Chain[7] ASIC[28] has core num=1
main.c:9113: Chain[7] ASIC[29] has core num=1
main.c:9113: Chain[7] ASIC[30] has core num=1
main.c:9113: Chain[7] ASIC[31] has core num=1
main.c:9113: Chain[7] ASIC[32] has core num=2
main.c:9113: Chain[7] ASIC[33] has core num=1
main.c:9113: Chain[7] ASIC[34] has core num=1
main.c:9113: Chain[7] ASIC[35] has core num=1
main.c:9113: Chain[7] ASIC[36] has core num=1
main.c:9113: Chain[7] ASIC[37] has core num=1
main.c:9113: Chain[7] ASIC[40] has core num=1
main.c:9113: Chain[7] ASIC[41] has core num=1
main.c:9113: Chain[7] ASIC[42] has core num=1
main.c:9113: Chain[7] ASIC[43] has core num=1
main.c:9113: Chain[7] ASIC[44] has core num=1
main.c:9113: Chain[7] ASIC[45] has core num=1
main.c:9113: Chain[7] ASIC[46] has core num=1
main.c:9113: Chain[7] ASIC[47] has core num=1
main.c:9113: Chain[7] ASIC[48] has core num=1
main.c:9113: Chain[7] ASIC[49] has core num=1
main.c:9113: Chain[7] ASIC[50] has core num=1
main.c:9113: Chain[7] ASIC[51] has core num=1
main.c:9113: Chain[7] ASIC[52] has core num=1
main.c:9113: Chain[7] ASIC[53] has core num=1
main.c:9113: Chain[7] ASIC[54] has core num=1
main.c:9113: Chain[7] ASIC[55] has core num=1
main.c:9113: Chain[7] ASIC[56] has core num=1
main.c:9113: Chain[7] ASIC[57] has core num=1
main.c:9113: Chain[7] ASIC[58] has core num=1
main.c:9113: Chain[7] ASIC[60] has core num=1
main.c:9113: Chain[7] ASIC[61] has core num=1
main.c:9113: Chain[7] ASIC[62] has core num=1
main.c:2282: Check chain[7] PIC fw version=0x03
main.c:9183: get PIC voltage=6 on chain[5], value=940
main.c:9183: get PIC voltage=6 on chain[6], value=940
main.c:9183: get PIC voltage=6 on chain[7], value=940
main.c:9349: chain[5] temp offset record: 62,0,0,0,0,0,35,28
main.c:9366: chain[5] temp chip I2C addr=0x98
main.c:9372: chain[5] has no middle temp, use special fix mode.
main.c:9349: chain[6] temp offset record: 62,0,0,0,0,0,35,28
main.c:9366: chain[6] temp chip I2C addr=0x98
main.c:9372: chain[6] has no middle temp, use special fix mode.
main.c:9349: chain[7] temp offset record: 62,0,0,0,0,0,35,28
main.c:9366: chain[7] temp chip I2C addr=0x98
main.c:9372: chain[7] has no middle temp, use special fix mode.
main.c:13956: total_exist_chain_num = 3
main.c:9562: CRC error counter=0
main.c:9577: set command mode to VIL
main.c:9649:
--- check asic number
main.c:9745: After Get ASIC NUM CRC error counter=0
main.c:9768: set_baud=0
main.c:10693: The min freq=700
main.c:10695: set real timeout 52, need sleep=379392
main.c:12825: After TEST CRC error counter=0
main.c:14236: search freq for 1 times, completed chain = 3, total chain num = 3
board_frq_tuning.c:628: single_board_frq_tuning enter
board_frq_tuning.c:629: min_rate, des_rate, fix_volt:13800, 14000, 880
board_frq_tuning.c:254: force_freq not set, don't need tuning
main.c:14645: restart Miner chance num=2
main.c:14685: waiting for receive_func to exit!
main.c:14699: waiting for pic heart to exit!
main.c:13927: bmminer not found=17661 root       0:00 grep bmminer

main.c:14758: bmminer not found, restart bmminer ...
main.c:13927: bmminer not found=12195 root       0:00 grep bmminer

main.c:14758: bmminer not found, restart bmminer ...
driver-btm-c5.c:12243:bitmain_c5_init: This is user mode for mining
driver-btm-c5.c:12286:bitmain_c5_init: Detect 1GB control board of XILINX
driver-btm-c5.c:12313:bitmain_c5_init: Miner Type = S9
driver-btm-c5.c:12324:bitmain_c5_init: Miner compile time: Wed Jul 31 16:18:27 CST 2019 type: Antminer S9
driver-btm-c5.c:12414:bitmain_c5_init: miner ID : 8128ed8162bb8854
driver-btm-c5.c:12571:bitmain_c5_init: Checking fans...
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=4320
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=4320
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=5280
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=4320
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=5280
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=4320
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=5280
driver-btm-c5.c:13108:bitmain_c5_init: chain[5]: [44:101] [38:104] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
driver-btm-c5.c:13122:bitmain_c5_init: last_freq: 0x00 0x7d 0x00 0x49 0x00 0x49 0x04 0x49 0x09 0x49 0x00 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x05 0x49 0x09 0x49 0x23 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49
driver-btm-c5.c:13149:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:13155:bitmain_c5_init: Detect: S9_63 use voltage level=3 : 0
driver-btm-c5.c:13171:bitmain_c5_init: Chain[J6] has backup chain_voltage=890
driver-btm-c5.c:13193:bitmain_c5_init: scan based on domain
driver-btm-c5.c:1899:jump_to_app_CheckAndRestorePIC: Check chain[5] PIC fw version=0x03
driver-btm-c5.c:13108:bitmain_c5_init: chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
driver-btm-c5.c:13122:bitmain_c5_init: last_freq: 0x00 0x7d 0x00 0x4f 0x00 0x4f 0x05 0x4f 0x00 0x4f 0x00 0x4f 0x03 0x4f 0x03 0x4f 0x03 0x4f 0x03 0x4f 0x03 0x4f 0x03 0x4f 0x03 0x4f 0x03 0x4f 0x03 0x4f 0x03 0x4f 0x03 0x4f 0x03 0x4f 0x05 0x4f 0x07 0x4f 0x23 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50 0x00 0x50
driver-btm-c5.c:13149:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:13155:bitmain_c5_init: Detect: S9_63 use voltage level=3 : 0
driver-btm-c5.c:13171:bitmain_c5_init: Chain[J7] has backup chain_voltage=870
driver-btm-c5.c:13193:bitmain_c5_init: scan based on domain
driver-btm-c5.c:1899:jump_to_app_CheckAndRestorePIC: Check chain[6] PIC fw version=0x03
driver-btm-c5.c:13108:bitmain_c5_init: chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
driver-btm-c5.c:13122:bitmain_c5_init: last_freq: 0x00 0x7d 0x00 0x49 0x00 0x49 0x04 0x49 0x09 0x49 0x00 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x03 0x49 0x05 0x49 0x09 0x49 0x23 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49 0x00 0x49
driver-btm-c5.c:13149:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:13155:bitmain_c5_init: Detect: S9_63 use voltage level=3 : 0
driver-btm-c5.c:13171:bitmain_c5_init: Chain[J8] has backup chain_voltage=890
driver-btm-c5.c:13193:bitmain_c5_init: scan based on domain
driver-btm-c5.c:1899:jump_to_app_CheckAndRestorePIC: Check chain[7] PIC fw version=0x03
driver-btm-c5.c:12195:init_exist_chain_table: total_exist_chain_num = 3
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J6] orignal chain_voltage_pic=6 value=940
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J6] will use backup chain_voltage_pic=890 [91]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J6] get working chain_voltage_pic=91
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J7] orignal chain_voltage_pic=6 value=940
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J7] will use backup chain_voltage_pic=870 [125]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J7] get working chain_voltage_pic=125
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J8] orignal chain_voltage_pic=6 value=940
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J8] will use backup chain_voltage_pic=890 [91]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J8] get working chain_voltage_pic=91
driver-btm-c5.c:13421:bitmain_c5_init: Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13421:bitmain_c5_init: Chain[J7] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J7] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J7] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J7] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J7] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J7] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J7] has 0 asic
driver-btm-c5.c:13421:bitmain_c5_init: Chain[J8] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J8] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J8] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J8] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J8] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J8] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J8] has 0 asic
driver-btm-c5.c:4571:set_frequency: miner total rate=0GH/s ideal_total_hash_rate = 0GH/s

driver-btm-c5.c:4819:set_frequency: Miner fix freq ...
driver-btm-c5.c:5119:set_frequency: max freq = 100
driver-btm-c5.c:4162:ProcessFixFreq: totalRate = 0, fixed_totalRate = 0
driver-btm-c5.c:9604:init_uart_baud: set baud=1
driver-btm-c5.c:12103:set_working_voltage: setting to working voltage...
driver-btm-c5.c:13954:bitmain_c5_init: start thread for read temp
setStartTimePoint total_tv_start_sys=1695 total_tv_end_sys=1696
driver-btm-c5.c:8727:read_temp_func: bring_up_pcb_temp = -100
driver-btm-c5.c:10320:check_system_work: restartNum = 2 , auto-reinit enabled...
driver-btm-c5.c:9887:if_avg_hash_ok: avg hash rate = 0.000000, ideal hash rate = 0
driver-btm-c5.c:10387:check_system_work: hash rate is low...
driver-btm-c5.c:15630:re_open_core: re_open_core enter
driver-btm-c5.c:15791:re_open_core: Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 0, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 1, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 2, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 3, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 4, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 5, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 6, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 7, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 8, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 9, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 10, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 11, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 12, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 13, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 14, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 15, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 16, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 17, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 18, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 19, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15791:re_open_core: Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 0, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 1, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 2, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 3, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 4, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 5, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 6, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 7, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 8, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 9, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 10, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 11, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 12, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 13, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 14, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 15, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 16, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 17, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 18, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 6, retry_count = 19, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J7] has 0 asic
driver-btm-c5.c:15791:re_open_core: Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 0, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 1, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 2, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 3, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 4, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 5, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 6, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 7, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 8, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 9, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 10, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 11, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 12, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 13, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 14, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 15, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 16, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 17, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 18, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 7, retry_count = 19, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J8] has 0 asic
driver-btm-c5.c:4571:set_frequency: miner total rate=0GH/s ideal_total_hash_rate = 0GH/s

driver-btm-c5.c:4819:set_frequency: Miner fix freq ...
driver-btm-c5.c:5119:set_frequency: max freq = 100
driver-btm-c5.c:4162:ProcessFixFreq: totalRate = 0, fixed_totalRate = 0
driver-btm-c5.c:9604:init_uart_baud: set baud=1
driver-btm-c5.c:16082:re_open_core: reopen core end
driver-btm-c5.c:10400:check_system_work: re-open core 1 times
driver-btm-c5.c:10427:check_system_work: checking hash again
driver-btm-c5.c:9887:if_avg_hash_ok: avg hash rate = 0.000000, ideal hash rate = 0
driver-btm-c5.c:9887:if_avg_hash_ok: avg hash rate = 0.000000, ideal hash rate = 0
driver-btm-c5.c:10387:check_system_work: hash rate is low...
driver-btm-c5.c:15630:re_open_core: re_open_core enter
driver-btm-c5.c:15791:re_open_core: Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 0, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 1, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 2, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 3, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 4, dev->chain_asic_num[i] = 0
driver-btm-c5.c:15818:re_open_core: retry Chain[J6] has 0 asic
driver-btm-c5.c:15795:re_open_core: i = 5, retry_count = 5, dev->chain_asic_num[i] = 0
do read_temp_func once...
Done check_asic_reg
Max pcb temp : -100
set FAN speed according to: temp_highest=-100 temp_top1[PWM_T]=-100 temp_top1[TEMP_POS_LOCAL]=-100 temp_change=0 fix_fan_steps=0
FAN PWM: 0
read_temp_func Done!
CRC error counter=9
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 4.5c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
by
katatunix
on 17/03/2020, 13:59:22 UTC
Quote from: gorkemg on August 26, 2019, 08:32:56 PM
I'm getting these  errors with 4.5c on 8x p106 rig   :

NVAPI error in NvapiWrapper.c:445 : -6
Unable to load NvAPI: error 3
Eth: the pool list contains 1 pool (1 from command-line)
Eth: primary pool: eu1-etc.ethermine.org:4444
Starting GPU mining
GPU1: unable to init NvAPI with bus ID 65536
GPU2: unable to init NvAPI with bus ID 131072
GPU3: unable to init NvAPI with bus ID 262144
GPU4: unable to init NvAPI with bus ID 327680
GPU5: unable to init NvAPI with bus ID 393216
GPU6: unable to init NvAPI with bus ID 458752
GPU7: unable to init NvAPI with bus ID 524288
GPU8: unable to init NvAPI with bus ID 589824

After these errors , Miner seems work like 4.2c  

Any idea ?

Still encountering this issue with version 4.9c (GPU: P106-100 with newest driver from Nvidia), please help, thank you.
Post
Topic
Board Mining (Altcoins)
Re: YoungBuffalo - iOS/Android app for monitoring miners - Claymores/Antminer/EWB
by
katatunix
on 18/06/2018, 17:30:11 UTC
YoungBuffalo is now available on Google Play Store also, check it out: https://play.google.com/store/apps/details?id=com.nghiabui.Buffalo
Post
Topic
Board Mining (Altcoins)
Re: YoungBuffalo - a new iOS app for monitoring miners - Claymores and Antminer
by
katatunix
on 11/06/2018, 10:02:53 UTC
Hello,

YoungBuffalo now already supports EWBF CUDA ZCash miner, check it out: https://itunes.apple.com/us/app/youngbuffalo/id1386685965?mt=8
Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.7 (Windows/Linux)
by
katatunix
on 29/05/2018, 05:32:54 UTC
Quote from: Maniac9331 on May 27, 2018, 05:12:00 PM
Quote from: katatunix on May 26, 2018, 08:51:53 AM
Hello,

This is an iOS app for monitoring cryptocurrency miners. Claymores and Antminer are supported.

Features:

- Fast loading.
- Smooth GUI with asynchronous computation.
- Users are allowed to edit rig information.
- Users can re-arrange the order of rigs.
- Remote rebooting is supported.
- Users can view the full console of Claymores with one touch.
- Easier viewing long lists of rigs with Compact view mode.
- Highlight problems of too low speed and/or too high temperature.
- Both iPhone and iPad are supported, iOS 9.0 or higher is required.

Screenshots:

https://imgur.com/a/1CAfNCy

Available on Apple Store:

https://itunes.apple.com/us/app/youngbuffalo/id1386685965?mt=8

Thanks for reading my post.


good app but is this only working when the phone is connected to the same network as the miners?

To use the app outside your local network, you need to know public IP of the rigs (go to ping.eu to see public IP). Also, you have to config your router/modem to NAT port from an outside port (e.g. 1234) to Claymore's monitor listening port (default 3333).

After that, in my app, you enter the public IP and the NAT port (1234), that's it.
Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.7 (Windows/Linux)
by
katatunix
on 26/05/2018, 08:51:53 UTC
Hello,

This is an iOS app for monitoring cryptocurrency miners. Claymores and Antminer are supported.

Features:

- Fast loading.
- Smooth GUI with asynchronous computation.
- Users are allowed to edit rig information.
- Users can re-arrange the order of rigs.
- Remote rebooting is supported.
- Users can view the full console of Claymores with one touch.
- Easier viewing long lists of rigs with Compact view mode.
- Highlight problems of too low speed and/or too high temperature.
- Both iPhone and iPad are supported, iOS 9.0 or higher is required.

Screenshots:

https://imgur.com/a/1CAfNCy

Available on Apple Store:

https://itunes.apple.com/us/app/youngbuffalo/id1386685965?mt=8

Thanks for reading my post.
Post
Topic
Board Mining (Altcoins)
Re: YoungBuffalo - a new iOS app for monitoring miners - Claymores and Antminer
by
katatunix
on 26/05/2018, 08:42:57 UTC
Quote from: young_lido on May 25, 2018, 02:53:44 AM
I am using this app. It's the best app for following the rigs
- Fast loading
- Showing full information of the rigs
- Showing incorrect share
- Can edit information of the rigs
- Can re-arrange
- Can view console of the rigs
- Can reboot the rigs via this app
- Specially, can following the S9 rigs

https://imgur.com/a/oMjD80V

That 's all things I want.  Wink

Thanks katatunix.


Thanks for using my app.

By the way, if you guys are mining on a miner without a good monitoring app on iOS or even Android, please tell me so I will try to support it. Currently I have a plan to support ZCash miners.
Post
Topic
Board Mining (Altcoins)
YoungBuffalo - iOS/Android app for monitoring miners - Claymores/Antminer/EWB
by
katatunix
on 23/05/2018, 07:33:08 UTC
Hello,

This is an iOS/Android app for monitoring mining rigs - Claymores, Antminer, and EWBF Zcash are supported.

Features:
- Fast loading.
- Smooth GUI with asynchronous computation.
- Users are allowed to edit rig information.
- Users can re-arrange the order of rigs.
- Remote rebooting is supported.
- Users can view the full console of miners with one touch.
- Easier viewing long lists of rigs with Compact view mode.
- Highlight problems of too low speed and/or too high temperature.
- Show incorrect shares (for Claymores) and rejected shares (for Antminer and EWBF).

Available on Apple App Store:

https://itunes.apple.com/us/app/youngbuffalo/id1386685965?mt=8

Available on Google Play Store:

https://play.google.com/store/apps/details?id=com.nghiabui.Buffalo

Thanks for reading my post.
Post
Topic
Board Mining (Altcoins)
Re: Claymore crash at startup - GPU Z no OpenCL
by
katatunix
on 03/05/2018, 08:29:05 UTC
It's win10 Creator which works well with my other rigs, and yeah, Blockchain Driver is very good.

In Device Manager all 8 cards are okay, run Pixel Patch already.

I execute EthDcrMiner64.exe directly, no any .bat file.

Everything is okay except what I mentioned in the first post.

I've just visit this site https://mining.help/ it mentioned about Adrenaline Edition and Crimson Edition. Maybe these drivers are more suitable to my rig. Will try them tonight.
Post
Topic
Board Mining (Altcoins)
Re: Claymore crash at startup - GPU Z no OpenCL
by
katatunix
on 03/05/2018, 03:04:52 UTC
I already disable Windows Defender and turn off Firewall in the first place.

Tried with ethminer with no luck, still crash at startup. It seem both Claymore and ethminer are able to start (some text were printed to console) but when the miners access OpenCL, crash!
Post
Topic
Board Mining (Altcoins)
Claymore crash at startup - GPU Z no OpenCL
by
katatunix
on 03/05/2018, 02:46:20 UTC
My rigs has 8 GPUs of PowerColor RX580 4G Samsung VRAM.

Claymore 11.6/11.7 just crashes at startup.

GPU Z reported that there is no OpenCL.

But in Radeon Setting, there is OpenCL.

Screenshots:

https://imgur.com/a/7Warkjh

What I did:
- Virtual Memory to 20000 MB
- Set the 5 recommended environment variables
- DDU, reinstall Blockchain Driver 23rd Aug
- Revert to stock rom (no modded)

Please help me.

Thank you very much.
Post
Topic
Board Mining (Altcoins)
Polly - a tool for monitoring CPU/GPU miners
by
katatunix
on 25/11/2017, 11:51:58 UTC
Run this tool on your mining rig, when any of predefined errors indicators happen (e.g., fan=0% or got incorrect share) with your miner, a predefined action will be automatically executed.

No scam!!!

Binary download: https://drive.google.com/drive/folders/1B-p-HME_HmSw10LV-MXqxDdhBHgltizh?usp=sharing
Source code: https://github.com/katatunix/polly

Features

  • Continuously check console output of the miner to detect errors, and based on that the tool will fire an action which is specified in a file called fire.bat.
  • Start miner again when it exits/crashes, fire the action if the exiting happens too quickly.
  • Periodically check new public IP address of the rig.
  • All important events (fire, exit, new IP) will be sent to a list of subscribed email addresses.

Usage

  • Copy folder /release/polly to your rig.
  • Open file fire.bat to specify your action, typically it is a call to restart the rig.
  • Open file config.json and modify it following the template below:

Code:
{
    "MinerPath" : "D:/Claymores/EthDcrMiner64.exe",
    "MinerArgs" : "-esm 1 -gser 0",
    "Polly" : {
        "SmtpHost" : "smtp.gmail.com",
        "SmtpPort" : 587,
        "Address" : "pollymonitor2@gmail.com",
        "Password" : "test",
        "DisplayedName" : "Polly"
    },
    "Subscribes" : [
        "apple@gmail.com",
        "banana@yahoo.com"
    ],
    "Profiles" : [
        {
            "Bad" : [ "ETH - Total Speed: 11", "ETH - Total Speed: 12", "ETH - Total Speed: 13" ],
            "Tolerance" : { "DurationMinutes" : 10, "Good" : [ "ETH - Total Speed: 14" ] }
        },
        {
            "Bad" : [
                "cannot get current temperature",
                "unspecified launch failure",
                "an illegal instruction was encountered",
                "got incorrect share",
                "fan=0%",
                "gpu error",
                "you need to restart miner",
                "cuda error",
                "opencl error",
                "gpuminer cu_k1 failed",
                "gpuminer cu_kx failed",
                "gpuminer cu_k01 failed",
                "gpuminer kx failed",
                "cannot get fan speed"
            ]
        }
    ],
    "ExitToleranceMinutes" : 1,
    "PublicIpCheckMinutes" : 30
}

  • Most of options are self-explanatory. Regarding the Polly option, it is recommended to use Gmail. You should change the pollymonitor2@gmail.com to your own Gmail address (and password, of course). Remember to turn on the  Allow less secure apps option of your account at myaccount.google.com/lesssecureapps
  • ExitToleranceMinutes defines what a too-quick exiting is: if the miner exits within this value, then fire.bat will be executed.
  • Execute the tool: polly.bat.
  • Make sure that the tool is executed every time your rig starts (e.g., create a shortcut of polly.bat and put it into the Startup folder of Windows).

Notes

  • You must use / or \\ (not \) in the MinerPath option.
  • It is recommended to set Screen Buffer Width (in Properties/Layout of the console) to be greater than the longest line in the console output of your miner. The typical value is 200. This should be done on the console window executed from the shortcut in the Startup folder, so that the setting will be applied permanently.

Happy mining!
Post
Topic
Board Development & Technical Discussion
Re: [Proposal] Why don't we sign receivers' addresses also?
by
katatunix
on 27/04/2015, 04:28:47 UTC
Thanks all. It's clear now.
Post
Topic
Board Development & Technical Discussion
Re: [Proposal] Why don't we sign receivers' addresses also?
by
katatunix
on 26/04/2015, 18:25:00 UTC
Quote from: shorena on April 26, 2015, 06:06:47 PM
Changing the receiving address(es) will render the signature(s) invalid.

Thanks for your reply Smiley

Could you please explain in more detail? If the signature was not produced from the receiving address, how can changing the receiving address render the signature invalid?

Note that the receiving address here is Apple.
Post
Topic
Board Development & Technical Discussion
Topic OP
[Proposal] Why don't we sign receivers' addresses also?
by
katatunix
on 26/04/2015, 17:55:32 UTC
Hello,

Let's consider following scenario:

  • Alice (a honest girl) is buying a product from the merchant Apple.
  • Alice create a new transaction TxA to send her bitcoins to Apple.
  • Bob (a bad guy) receives TxA and modifies the receiver's address to create TxB.
  • Assume that the TxB will be confirmed, not TxA. So Bob (not Apple) will receive Alice's bitcoins.
  • Apple will not send the product to Alice because the TxA has not been confirmed.
  • Alice is the only victim in this scenario.

As far as I know, to create TxA, Alice must sign her bitcoins which is identified by the output index in the former transaction. So why doesn't Alice sign the receiver's address (Apple) also when creating TxA? This will make Bob cannot modifies the receiver's address and thus can prevent the scenario above.