Bitcoin Forum
May 04, 2024, 06:53:23 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: S17 Pro 53th Troubleshooting  (Read 228 times)
carlbutler86 (OP)
Jr. Member
*
Offline Offline

Activity: 37
Merit: 6


View Profile
January 16, 2021, 08:12:45 PM
Last edit: January 19, 2021, 07:31:55 PM by carlbutler86
 #1

Hey everyone, I just bought some S17 Pro 53th rigs from a Chinese seller and 5 of the work fine, 1 only gives me 2 hashboards, but the seller said it was working fine before shipment, they even sent me a video showing it working before they shipped it, so i'm trying to figure out what's wrong  Cry

thanks so much for any info!
1714805603
Hero Member
*
Offline Offline

Posts: 1714805603

View Profile Personal Message (Offline)

Ignore
1714805603
Reply with quote  #2

1714805603
Report to moderator
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, which will follow the rules of the network no matter what miners do. Even if every miner decided to create 1000 bitcoins per block, full nodes would stick to the rules and reject those blocks.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
BTC-Explorer
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
January 16, 2021, 08:31:16 PM
 #2

You can read the "Kernel Log". it will give you detailed description of what is going on in the miner. it might have bad temp sensor or bad chips.

You can also do the "Antminer Repair Course" online from Bitmain and learn to do repair yourself professionally.

Akm
Steamtyme
Legendary
*
Offline Offline

Activity: 1540
Merit: 2036


Betnomi.com Sportsbook, Casino and Poker


View Profile WWW
January 18, 2021, 06:03:21 PM
Last edit: January 18, 2021, 06:20:31 PM by Steamtyme
Merited by suchmoon (4)
 #3

Hey so the best place for some free advice and assistance is the Mining Support board here on the forum. You can move the thread there yourself by selecting move-topic on the bottom left of your screen, or Mods will have moved it by then.


Apart from that any specific information you can provide will be helpful. You say one machine is running, and the other 4 are doing the same thing? They just throw up some red lights. You said you can log in? If you can then you should be able to access the logs and those can be copied and pasted on forum using the # code tag.

Code:
Pase logs in here for ease of scrolling

This way people can scroll them to look for issues. To be sure though you have everything else set up properly - Proper circuit sizing for the gear, appropriate voltage. Do you hear or feel anything rattling around or loose in the miner as you move them around?

Where these ordered from Bitmain or a reseller?


░░░░░▄▄██████▄▄
░░▄████▀▀▀▀▀▀████▄
███▀░░░░░░░░░░▀█▀█
███░░░▄██████▄▄░░░██
░░░░░█████████░░░░██▌
░░░░█████████████████
░░░░█████████████████
░░░░░████████████████
███▄░░▀██████▀░░░███
█▀█▄▄░░░░░░░░░░▄███
░░▀████▄▄▄▄▄▄████▀
░░░░░▀▀██████▀▀
Ripmixer
░░░░░▄▄██████▄▄
░░▄████▀▀▀▀▀▀████▄
███▀░░░░░░░░░░▀█▀█
███░░░▄██████▄▄░░░██
░░░░░█████████░░░░██▌
░░░░█████████████████
░░░░█████████████████
░░░░░████████████████
███▄░░▀██████▀░░░███
█▀█▄▄░░░░░░░░░░▄███
░░▀████▄▄▄▄▄▄████▀
░░░░░▀▀██████▀▀
mikeywith
Legendary
*
Offline Offline

Activity: 2226
Merit: 6367


be constructive or S.T.F.U


View Profile
January 19, 2021, 12:21:14 AM
Last edit: January 19, 2021, 12:34:56 AM by frodocooper
 #4

Anyone have experience troubleshooting or fixing these rigs? If so I'd be happy to pay you for your time to help me out!  Smiley

That's nice of you, I have probably helped hunderds of people fix their mining gears, and so did the other folks here in the mining board, and well, we rarely get a "thank you", let alone a tip. Grin

Well, first thing first, you need to post the following in order to get a proper (and free) answer.

1- The complete Kernel log

2- A screenshot of the miner status

3- A screenshot of the pool settings ( you can hide your worker name).

... majority of them are flashing a red fault light and won't give me miner stats.

This is what happens with almost all issues, some of these issues can be easily fixed, some are impossible to fix, but in general, you can't conclude anything just from a non-status and a red light on the control board.

█▀▀▀











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











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
carlbutler86 (OP)
Jr. Member
*
Offline Offline

Activity: 37
Merit: 6


View Profile
January 19, 2021, 07:47:02 PM
Last edit: January 19, 2021, 10:55:34 PM by frodocooper
 #5

Wow thank you everyone. I turned out these rigs start off with a red fault light before turning into a green normal light. I'd never seen that before in the 3 years I've been mining.

So 5 rigs are working great, and 1 is giving me only 2 hashboards, although the third party seller (Shenzhen Dovina Electronic Technology Co., Ltd.) says it was working fine when they tested before shipping, and sent me a video where all 3 boards are in fact working prior to shipping.

Here's the kernel log:

Code:
Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
  Normal zone: 480 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203608K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25768K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12728K (cce93000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 4/2, WL threshold: 4096, image sequence number: 3409746667
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 80BFC54B-44B7-4832-96FB-E47FBAE4EBF9, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 2096991123
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 1FDCE1B9-0FDE-48F6-ADE5-519598D46C4C, small LPT model
alloc_contig_range: [e043, e044) PFNs busy
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
alloc_contig_range: [e043, e044) PFNs busy
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
Jan 19 19:40:31 (none) user.notice kernel: random: nonblocking pool is initialized
Jan 19 19:43:35 (none) local0.notice bmminer: set_start_time_point total_tv_start_sys=411 total_tv_end_sys=412
Jan 19 19:43:38 (none) local0.notice cgminer: cgminer_socket_init reg bitmain_api_detect return: 0
Jan 19 19:43:38 (none) local0.notice cgminer: cgminer_socket_init reg bitmain_update_job return: 0
Jan 19 19:43:39 (none) local0.notice cgminer: cgminer_socket_init reg bitmain_shutdown return: 0
Jan 19 19:43:39 (none) local0.err cgminer: Miner compile time: Mon Apr 27 13:25:08 CST 2020 type: Antminer S17 Pro
Jan 19 19:43:39 (none) local0.notice cgminer[1517]: about to send detect
Jan 19 19:43:39 (none) local0.notice cgminer[1517]: set_start_time_point total_tv_start_sys=415 total_tv_end_sys=416
Jan 19 19:43:39 (none) local0.notice cgminer[1517]: Probing for an alive pool
Jan 19 19:43:40 (none) local0.notice cgminer[1517]: Pool 2 difficulty changed to 32768
Jan 19 19:43:40 (none) local0.notice cgminer[1517]: Pool 1 difficulty changed to 32768
Jan 19 19:43:40 (none) local0.notice cgminer[1517]: Pool 0 difficulty changed to 32768
Jan 19 19:43:40 (none) local0.notice cgminer[1517]: LOW POWER MODE!
Jan 19 19:43:40 (none) local0.notice cgminer[1517]: Switching to pool 1 stratum+tcp://stratum.antpool.com:443 - first alive pool
Jan 19 19:43:40 (none) local0.notice cgminer[1517]: LOW POWER MODE!
Jan 19 19:43:40 (none) local0.notice cgminer[1517]: in stratum_sthread
Jan 19 19:43:40 (none) local0.notice cgminer[1517]: in stratum_sthread
Jan 19 19:43:40 (none) local0.notice cgminer[1517]: LOW POWER MODE!
Jan 19 19:43:40 (none) local0.warn cgminer[1517]: Pool 0 stratum+tcp://stratum.antpool.com:3333 alive, testing stability
Jan 19 19:43:40 (none) local0.warn cgminer[1517]: Switching to pool 0 stratum+tcp://stratum.antpool.com:3333
Jan 19 19:43:40 (none) local0.notice cgminer[1517]: in stratum_sthread
Jan 19 19:43:40 (none) local0.notice cgminer[1517]: POOL 0 support ab mode!
Jan 19 19:43:40 (none) local0.notice cgminer[1517]: Network diff set to 20.6T
Jan 19 19:43:40 (none) local0.notice cgminer[1517]: update job
Jan 19 19:43:40 (none) local0.notice cgminer[1517]: job buf total len:2597, offset:2597
Jan 19 19:43:40 (none) local0.notice cgminer[1517]: about to send job, size is 2597
Jan 19 19:43:40 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000480 size: 2597
Jan 19 19:43:40 (none) local0.notice bmminer: parse job buf len:2597
Jan 19 19:43:41 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:43:41 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:43:41 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:43:41 (none) local0.notice cgminer[1517]: Accepted 01620559 Diff 47.4K/32768 BTM_SOC 0 pool 0
Jan 19 19:43:45 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:43:45 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:43:45 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:43:45 (none) local0.notice cgminer[1517]: Accepted 01f3fb8d Diff 33.6K/32768 BTM_SOC 0 pool 0
Jan 19 19:43:45 (none) local0.warn cgminer[1517]: API running in IP access mode on port 4028 (14)
Jan 19 19:43:49 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:43:49 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:43:49 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:43:49 (none) local0.notice cgminer[1517]: Accepted 014f66e5 Diff 50K/32768 BTM_SOC 0 pool 0
Jan 19 19:43:52 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:43:52 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:43:52 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:43:52 (none) local0.notice cgminer[1517]: Accepted c3b9dece Diff 85.7K/32768 BTM_SOC 0 pool 0
Jan 19 19:44:00 (none) local0.notice cgminer[1517]: update job
Jan 19 19:44:00 (none) local0.notice cgminer[1517]: job buf total len:2597, offset:2597
Jan 19 19:44:00 (none) local0.notice cgminer[1517]: about to send job, size is 2597
Jan 19 19:44:00 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000480 size: 2597
Jan 19 19:44:00 (none) local0.notice bmminer: parse job buf len:2597
Jan 19 19:44:07 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:07 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:07 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:07 (none) local0.notice cgminer[1517]: Accepted c27b1546 Diff 86.3K/32768 BTM_SOC 0 pool 0
Jan 19 19:44:07 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:07 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:07 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:07 (none) local0.notice cgminer[1517]: Accepted 6ece67c7 Diff 151K/32768 BTM_SOC 0 pool 0
Jan 19 19:44:09 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:09 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:09 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:09 (none) local0.notice cgminer[1517]: Accepted f0f9ff07 Diff 69.6K/32768 BTM_SOC 0 pool 0
Jan 19 19:44:12 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:12 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:12 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:12 (none) local0.notice cgminer[1517]: Accepted 1726d1d3 Diff 725K/32768 BTM_SOC 0 pool 0
Jan 19 19:44:13 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:13 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:13 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:13 (none) local0.notice cgminer[1517]: Accepted 8e83c87a Diff 118K/32768 BTM_SOC 0 pool 0
Jan 19 19:44:21 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:21 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:21 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:21 (none) local0.notice cgminer[1517]: Accepted 01406b98 Diff 52.4K/32768 BTM_SOC 0 pool 0
Jan 19 19:44:22 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:22 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:22 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:22 (none) local0.notice cgminer[1517]: Accepted 0183b0f8 Diff 43.3K/32768 BTM_SOC 0 pool 0
Jan 19 19:44:23 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:23 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:23 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:23 (none) local0.notice cgminer[1517]: Accepted 018764de Diff 42.9K/32768 BTM_SOC 0 pool 0
Jan 19 19:44:25 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:25 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:25 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:25 (none) local0.notice cgminer[1517]: Accepted 1251f245 Diff 916K/32768 BTM_SOC 0 pool 0
Jan 19 19:44:27 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:27 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:27 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:27 (none) local0.notice cgminer[1517]: Accepted 01d453f4 Diff 35.8K/32768 BTM_SOC 0 pool 0
Jan 19 19:44:27 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:27 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:27 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:27 (none) local0.notice cgminer[1517]: Accepted eb3a6dbf Diff 71.3K/32768 BTM_SOC 0 pool 0
Jan 19 19:44:28 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:28 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:28 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:28 (none) local0.notice cgminer[1517]: Accepted d0eb93d7 Diff 80.3K/32768 BTM_SOC 0 pool 0
Jan 19 19:44:28 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:28 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:28 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:28 (none) local0.notice cgminer[1517]: Accepted 01d7bff6 Diff 35.6K/32768 BTM_SOC 0 pool 0
Jan 19 19:44:29 (none) local0.notice cgminer[1517]: Pool 0 difficulty changed to 131072
Jan 19 19:44:30 (none) local0.notice cgminer[1517]: update job
Jan 19 19:44:30 (none) local0.notice cgminer[1517]: job buf total len:2597, offset:2597
Jan 19 19:44:30 (none) local0.notice cgminer[1517]: about to send job, size is 2597
Jan 19 19:44:30 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000480 size: 2597
Jan 19 19:44:30 (none) local0.notice bmminer: parse job buf len:2597
Jan 19 19:44:38 (none) local0.notice cgminer[1517]: Stratum from pool 0 detected new block at height 666798
Jan 19 19:44:38 (none) local0.notice cgminer[1517]: update job
Jan 19 19:44:38 (none) local0.notice cgminer[1517]: job buf total len:2213, offset:2213
Jan 19 19:44:38 (none) local0.notice cgminer[1517]: about to send job, size is 2213
Jan 19 19:44:38 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000480 size: 2213
Jan 19 19:44:38 (none) local0.notice bmminer: parse job buf len:2213
Jan 19 19:44:40 (none) local0.notice cgminer[1517]: update job
Jan 19 19:44:40 (none) local0.notice cgminer[1517]: job buf total len:2598, offset:2598
Jan 19 19:44:40 (none) local0.notice cgminer[1517]: about to send job, size is 2598
Jan 19 19:44:40 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000480 size: 2598
Jan 19 19:44:40 (none) local0.notice bmminer: parse job buf len:2598
Jan 19 19:44:43 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:43 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:43 (none) local0.notice cgminer[1517]: Pool 0 stale share detected, submitting as user requested
Jan 19 19:44:43 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:43 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:43 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:43 (none) local0.notice cgminer[1517]: Pool 0 stale share detected, submitting as user requested
Jan 19 19:44:43 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:43 (none) local0.notice cgminer[1517]: Accepted 6689a0ea Diff 164K/131072 BTM_SOC 0 pool 0
Jan 19 19:44:43 (none) local0.notice cgminer[1517]: Accepted 155fd4a0 Diff 785K/131072 BTM_SOC 0 pool 0
Jan 19 19:44:58 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:58 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:58 (none) local0.notice cgminer[1517]: Pool 0 stale share detected, submitting as user requested
Jan 19 19:44:58 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:58 (none) local0.notice cgminer[1517]: Accepted 61135707 Diff 173K/131072 BTM_SOC 0 pool 0
Jan 19 19:44:58 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:44:58 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:44:58 (none) local0.notice cgminer[1517]: Pool 0 stale share detected, submitting as user requested
Jan 19 19:44:58 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:44:58 (none) local0.notice cgminer[1517]: Accepted 4a513575 Diff 226K/131072 BTM_SOC 0 pool 0
Jan 19 19:45:10 (none) local0.notice cgminer[1517]: update job
Jan 19 19:45:10 (none) local0.notice cgminer[1517]: job buf total len:2597, offset:2597
Jan 19 19:45:10 (none) local0.notice cgminer[1517]: about to send job, size is 2597
Jan 19 19:45:10 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000480 size: 2597
Jan 19 19:45:10 (none) local0.notice bmminer: parse job buf len:2597
Jan 19 19:45:13 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:45:13 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:45:13 (none) local0.notice cgminer[1517]: Pool 0 stale share detected, submitting as user requested
Jan 19 19:45:13 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:45:14 (none) local0.notice cgminer[1517]: Accepted 1517e61d Diff 795K/131072 BTM_SOC 0 pool 0
Jan 19 19:45:15 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:45:15 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:45:15 (none) local0.notice cgminer[1517]: Pool 0 stale share detected, submitting as user requested
Jan 19 19:45:15 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:45:15 (none) local0.notice cgminer[1517]: Accepted 772c5a52 Diff 141K/131072 BTM_SOC 0 pool 0
Jan 19 19:45:25 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:45:25 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:45:25 (none) local0.notice cgminer[1517]: Pool 0 stale share detected, submitting as user requested
Jan 19 19:45:25 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:45:25 (none) local0.notice cgminer[1517]: Accepted 692f04df Diff 160K/131072 BTM_SOC 0 pool 0
Jan 19 19:45:25 (none) local0.notice bmminer: need data size:491, actual size:491
Jan 19 19:45:25 (none) local0.notice cgminer[1517]: got nonce sz 491
Jan 19 19:45:25 (none) local0.notice cgminer[1517]: Pool 0 stale share detected, submitting as user requested
Jan 19 19:45:25 (none) local0.notice cgminer[1517]: cb_bitmain_submit_nonce nonce submited
Jan 19 19:45:25 (none) local0.notice cgminer[1517]: Accepted 563cc53e Diff 195K/131072 BTM_SOC 0 pool 0
2021-01-19 19:39:16 driver-btm-api.c:542:init_freq_mode: This is scan-user version
2021-01-19 19:39:16 driver-btm-api.c:1877:bitmain_soc_init: opt_multi_version     = 1
2021-01-19 19:39:16 driver-btm-api.c:1878:bitmain_soc_init: opt_bitmain_ab        = 1
2021-01-19 19:39:16 driver-btm-api.c:1879:bitmain_soc_init: opt_bitmain_work_mode = 1
2021-01-19 19:39:16 driver-btm-api.c:1880:bitmain_soc_init: Miner compile time: Mon Apr 27 13:25:08 CST 2020 type: Antminer S17 Pro
2021-01-19 19:39:16 driver-btm-api.c:1881:bitmain_soc_init: commit version: d22f356 2020-04-24 18:30:49, build by: lol 2020-04-27 13:31:45
2021-01-19 19:39:16 driver-btm-api.c:1691:show_sn: no SN got, please write SN to /nvdata/sn
2021-01-19 19:39:16 driver-btm-api.c:1040:miner_device_init: Detect 256MB control board of XILINX
2021-01-19 19:39:16 driver-btm-api.c:988:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2021-01-19 19:39:16 thread.c:783:create_read_nonce_reg_thread: create thread
2021-01-19 19:39:22 driver-btm-api.c:972:init_miner_version: miner ID : 80081d801c208814
2021-01-19 19:39:22 driver-btm-api.c:978:init_miner_version: FPGA Version = 0xB013
2021-01-19 19:39:28 driver-btm-api.c:616:get_product_id: product_id[0] = 0
2021-01-19 19:39:28 driver-btm-api.c:616:get_product_id: product_id[1] = 0
2021-01-19 19:39:28 driver-btm-api.c:616:get_product_id: product_id[2] = 0
2021-01-19 19:39:28 driver-btm-api.c:560:_set_project_type: project:0
2021-01-19 19:39:28 driver-btm-api.c:585:_set_project_type: Project type: Antminer S17 Pro
2021-01-19 19:39:28 driver-btm-api.c:596:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2021-01-19 19:39:28 driver-btm-api.c:597:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2021-01-19 19:39:28 driver-btm-api.c:596:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2021-01-19 19:39:28 driver-btm-api.c:597:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2021-01-19 19:39:28 driver-btm-api.c:596:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2021-01-19 19:39:28 driver-btm-api.c:597:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2021-01-19 19:39:29 driver-btm-api.c:1802:bitmain_board_init: Fan check passed.
2021-01-19 19:39:30 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-01-19 19:39:32 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2021-01-19 19:39:33 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-01-19 19:39:35 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2021-01-19 19:39:36 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-01-19 19:39:38 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2021-01-19 19:39:38 thread.c:778:create_pic_heart_beat_thread: create thread
2021-01-19 19:39:38 power_api.c:207:power_init: Power init:
2021-01-19 19:39:38 power_api.c:208:power_init: current_voltage_raw = 0
2021-01-19 19:39:38 power_api.c:209:power_init: highest_voltage_raw = 2100
2021-01-19 19:39:38 power_api.c:210:power_init: working_voltage_raw = 1830
2021-01-19 19:39:38 power_api.c:211:power_init: higher_voltage_raw  = 1950
2021-01-19 19:39:38 driver-btm-api.c:1812:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-01-19 19:40:10 power_api.c:251:set_to_highest_voltage: Set to voltage raw 2100, one step.
2021-01-19 19:40:12 power_api.c:87:check_voltage_multi: retry time: 0
2021-01-19 19:40:13 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 21.436787
2021-01-19 19:40:14 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.283711
2021-01-19 19:40:15 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 21.265342
2021-01-19 19:40:15 power_api.c:50:_get_avg_voltage: average_voltage = 21.328613
2021-01-19 19:40:15 power_api.c:68:check_voltage: target_vol = 21.00, actural_vol = 21.33, check voltage passed.
2021-01-19 19:40:15 uart.c:71:set_baud: set fpga_baud to 115200
2021-01-19 19:40:27 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[0]: find 31 asic, times 0
2021-01-19 19:40:38 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[0]: find 31 asic, times 1
2021-01-19 19:40:49 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[0]: find 32 asic, times 2
2021-01-19 19:40:49 driver-btm-api.c:942:check_asic_number: Chain 0 only find 32 asic, will power off hash board 0
2021-01-19 19:41:01 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2021-01-19 19:41:12 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2021-01-19 19:41:15 driver-btm-api.c:345:set_order_clock: chain[1]: set order clock, stragegy 3
2021-01-19 19:41:15 driver-btm-api.c:345:set_order_clock: chain[2]: set order clock, stragegy 3
2021-01-19 19:41:15 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2021-01-19 19:41:15 uart.c:71:set_baud: set fpga_baud to 3000000
2021-01-19 19:41:15 driver-btm-api.c:1574:check_clock_counter: freq 50 clock_counter_limit 6
2021-01-19 19:41:17 uart.c:71:set_baud: set fpga_baud to 115200
2021-01-19 19:41:17 voltage[1] = 1800
2021-01-19 19:41:17 voltage[2] = 1800
2021-01-19 19:41:17 power_api.c:219:set_working_voltage_raw: working_voltage_raw = 1800
2021-01-19 19:41:18 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2021-01-19 19:41:20 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2021-01-19 19:41:20 uart.c:71:set_baud: set fpga_baud to 6000000
2021-01-19 19:41:21 driver-btm-api.c:245:check_bringup_temp: Bring up temperature is 20
2021-01-19 19:41:21 thread.c:798:create_check_miner_status_thread: create thread
2021-01-19 19:41:21 thread.c:788:create_set_miner_status_thread: create thread
2021-01-19 19:41:21 thread.c:773:create_temperature_monitor_thread: create thread
2021-01-19 19:41:21 frequency.c:749:inc_freq_with_fixed_vco: chain = 255, freq = 565, is_higher_voltage = true
2021-01-19 19:41:21 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 2020, step by step.
2021-01-19 19:41:40 power_api.c:87:check_voltage_multi: retry time: 0
2021-01-19 19:41:41 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 20.469345
2021-01-19 19:41:42 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 20.444853
2021-01-19 19:41:42 power_api.c:50:_get_avg_voltage: average_voltage = 20.457099
2021-01-19 19:41:42 power_api.c:68:check_voltage: target_vol = 20.20, actural_vol = 20.46, check voltage passed.
2021-01-19 19:42:12 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1900, step by step.
2021-01-19 19:42:31 power_api.c:87:check_voltage_multi: retry time: 0
2021-01-19 19:42:32 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 19.269228
2021-01-19 19:42:33 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 19.232490
2021-01-19 19:42:33 power_api.c:50:_get_avg_voltage: average_voltage = 19.250859
2021-01-19 19:42:33 power_api.c:68:check_voltage: target_vol = 19.00, actural_vol = 19.25, check voltage passed.
2021-01-19 19:42:39 frequency.c:801:inc_freq_with_fixed_step: chain = 1, freq_start = 565, freq_end = 565, freq_step = 5, is_higher_voltage = true
2021-01-19 19:42:39 frequency.c:801:inc_freq_with_fixed_step: chain = 2, freq_start = 565, freq_end = 565, freq_step = 5, is_higher_voltage = true
2021-01-19 19:42:39 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1850, step by step.
2021-01-19 19:42:54 power_api.c:87:check_voltage_multi: retry time: 0
2021-01-19 19:42:55 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 18.773261
2021-01-19 19:42:56 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 18.712031
2021-01-19 19:42:56 power_api.c:50:_get_avg_voltage: average_voltage = 18.742646
2021-01-19 19:42:56 power_api.c:68:check_voltage: target_vol = 18.50, actural_vol = 18.74, check voltage passed.
2021-01-19 19:42:56 frequency.c:618:inc_asic_diff_freq_by_steps: chain = 1, start = 565, freq_step = 5
2021-01-19 19:43:03 frequency.c:618:inc_asic_diff_freq_by_steps: chain = 2, start = 565, freq_step = 5
2021-01-19 19:43:10 driver-btm-api.c:528:set_timeout: freq = 625, percent = 90, hcn = 73728, timeout = 117
2021-01-19 19:43:10 power_api.c:225:set_higher_voltage_raw: higher_voltage_raw = 1890
2021-01-19 19:43:10 power_api.c:281:set_to_higher_voltage_by_steps: Set to voltage raw 1890, step by step.
2021-01-19 19:43:27 power_api.c:87:check_voltage_multi: retry time: 0
2021-01-19 19:43:29 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 19.159013
2021-01-19 19:43:30 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 19.116152
2021-01-19 19:43:30 power_api.c:50:_get_avg_voltage: average_voltage = 19.137583
2021-01-19 19:43:30 power_api.c:68:check_voltage: target_vol = 18.90, actural_vol = 19.14, check voltage passed.
2021-01-19 19:43:30 thread.c:793:create_check_system_status_thread: create thread
2021-01-19 19:43:31 driver-btm-api.c:1988:bitmain_soc_init: Init done!
2021-01-19 19:43:31 driver-btm-api.c:198:set_miner_status: STATUS_INIT
2021-01-19 19:43:35 driver-btm-api.c:198:set_miner_status: STATUS_OKAY
2021-01-19 19:43:36 frequency.c:216:get_ideal_hash_rate_GH: ideal_hash_rate = 38170
2021-01-19 19:43:36 frequency.c:236:get_sale_hash_rate_GH: sale_hash_rate = 38000
2021-01-19 19:43:40 driver-btm-api.c:1199:dhash_chip_send_job: Version num 4

and here are the images that you requested:

https://i.imgur.com/W6a5xWU.png
https://i.imgur.com/wYDCGGS.png

I can't thank you guys enough for any and all help!  Cheesy
wndsnb
Hero Member
*****
Offline Offline

Activity: 544
Merit: 589


View Profile
January 19, 2021, 08:13:32 PM
Last edit: January 19, 2021, 10:56:05 PM by frodocooper
 #6

2021-01-19 19:40:27 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[0]: find 31 asic, times 0
2021-01-19 19:40:38 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[0]: find 31 asic, times 1
2021-01-19 19:40:49 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[0]: find 32 asic, times 2
2021-01-19 19:40:49 driver-btm-api.c:942:check_asic_number: Chain 0 only find 32 asic, will power off hash board 0
2021-01-19 19:41:01 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2021-01-19 19:41:12 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0


Not finding all the chips on chain 0. It is likely that either excess solder laying on the hasboard moved during shipment, or marginal solder connections to a chip opened up. You can try tilting the miner or putting it on it's side like someone suggested in this thread. Or just shaking it around a bit. When I'm testing hashboards, many times tapping the board on a table and flexing it will produce or solve issues. So you might be able to get it running at least for some period of time that way.

Have some dead Bitmain 17 series hashboards or full miners?
I'll buy them ... send me a PM with what you have and I'll make you an offer!
carlbutler86 (OP)
Jr. Member
*
Offline Offline

Activity: 37
Merit: 6


View Profile
January 19, 2021, 08:53:59 PM
Last edit: January 19, 2021, 10:56:22 PM by frodocooper
 #7

Thanks for that, I just shook it around and tapped it several times, and put it on it's side. Then turned it on, and still only 2 hashboards are working. I wish I knew how to actually fix it, as I'm sure some of you experts would know how to. It's very frustrating to pay a bunch of money for a rig, and when it arrives, only 2 boards work, and the seller won't help you at all  Sad
wndsnb
Hero Member
*****
Offline Offline

Activity: 544
Merit: 589


View Profile
January 19, 2021, 09:07:20 PM
 #8

Unfortunately, your best option is probably to just mine with 2 hashboards. This is a very common issue with these miners.

If you can find a shop nearby that fixes them, it looks like the going rate is ~$200 to repair a hashboard.

Have some dead Bitmain 17 series hashboards or full miners?
I'll buy them ... send me a PM with what you have and I'll make you an offer!
carlbutler86 (OP)
Jr. Member
*
Offline Offline

Activity: 37
Merit: 6


View Profile
January 19, 2021, 09:08:50 PM
 #9

Unfortunately, your best option is probably to just mine with 2 hashboards. This is a very common issue with these miners.

If you can find a shop nearby that fixes them, it looks like the going rate is ~$200 to repair a hashboard.

I appreciate your help. Can I ask, how would one locate a shop that would repair a miner?
Steamtyme
Legendary
*
Offline Offline

Activity: 1540
Merit: 2036


Betnomi.com Sportsbook, Casino and Poker


View Profile WWW
January 19, 2021, 09:14:30 PM
 #10

Well I would check with the shop you bought from first. See if there is any sort of Warranty/RMA that they offer, Either way it was damaged in shipping so hopefully you have some option. If that doesn't work Look into this thread here Where to fix your Asic miners.

I've had a good experience with HMtech if you are North America based. Apart from that make sure it's worth the cost of repair for that board. (You'll earn back what it costs to repair in mining rewards)


░░░░░▄▄██████▄▄
░░▄████▀▀▀▀▀▀████▄
███▀░░░░░░░░░░▀█▀█
███░░░▄██████▄▄░░░██
░░░░░█████████░░░░██▌
░░░░█████████████████
░░░░█████████████████
░░░░░████████████████
███▄░░▀██████▀░░░███
█▀█▄▄░░░░░░░░░░▄███
░░▀████▄▄▄▄▄▄████▀
░░░░░▀▀██████▀▀
Ripmixer
░░░░░▄▄██████▄▄
░░▄████▀▀▀▀▀▀████▄
███▀░░░░░░░░░░▀█▀█
███░░░▄██████▄▄░░░██
░░░░░█████████░░░░██▌
░░░░█████████████████
░░░░█████████████████
░░░░░████████████████
███▄░░▀██████▀░░░███
█▀█▄▄░░░░░░░░░░▄███
░░▀████▄▄▄▄▄▄████▀
░░░░░▀▀██████▀▀
carlbutler86 (OP)
Jr. Member
*
Offline Offline

Activity: 37
Merit: 6


View Profile
January 19, 2021, 09:21:52 PM
 #11

Well I would check with the shop you bought from first. See if there is any sort of Warranty/RMA that they offer, Either way it was damaged in shipping so hopefully you have some option. If that doesn't work Look into this thread here =Where to fix your Asic miners.

I've had a good experience with HMtech if you are North America based. Apart from that make sure it's worth the cost of repair for that board. (You'll earn back what it costs to repair in mining rewards)

Perfect thank you for that referral! I just sent them an email!

And yes I am talking to the seller to see if I can file a claim with DHL for the damage.
Diego1907
Newbie
*
Offline Offline

Activity: 16
Merit: 1


View Profile
April 13, 2021, 03:23:06 PM
 #12

Well I would check with the shop you bought from first. See if there is any sort of Warranty/RMA that they offer, Either way it was damaged in shipping so hopefully you have some option. If that doesn't work Look into this thread here =Where to fix your Asic miners.

I've had a good experience with HMtech if you are North America based. Apart from that make sure it's worth the cost of repair for that board. (You'll earn back what it costs to repair in mining rewards)

Perfect thank you for that referral! I just sent them an email!

And yes I am talking to the seller to see if I can file a claim with DHL for the damage.

Hi Carl,

just found this topic as I have the same issue and also with the same Supplier Shenzhen Dovina! I have sent them the defect hashboard, they have said they repaired the hashboard and sent it back to me. But again the exact same issue! They didn´t do anything imo and a video is not proof enough! Anyway I have paid 3 times for shipping...

Did they offer you any other solution? I will write a realy bad review, they are a bit afraid of that. But I don´t believe there is more I can do and unfortunately there is nothing I can get...
mikeywith
Legendary
*
Offline Offline

Activity: 2226
Merit: 6367


be constructive or S.T.F.U


View Profile
April 14, 2021, 01:22:55 AM
 #13

just found this topic as I have the same issue and also with the same Supplier Shenzhen Dovina! I have sent them the defect hashboard, they have said they repaired the hashboard and sent it back to me. But again the exact same issue! They didn´t do anything imo and a video is not proof enough! Anyway I have paid 3 times for shipping...

It's safe to assume that the majority of people in this industry are either scammers or simply are not honest, but as wndsnb mentioned, these hash boards are so fragile, you might fix it, it works for a while and then breaks again, I have a few gears that sometimes would work with 3 boards and then out of a sudden only 1 board shows up, if I wanted to I could simply sell it as a miner that works with 3 boards but then I would be another scammer, unfortunately, this is what many people do.

I always tell my friends and clients that a video showing the full hashrate of the miner is not enough proof, I see resellers taking a 1-minute video of a miner that has been turned on for no more than 10 minutes and claiming that the miner is fully functional, it's pathetic, to say the least as many, many issues will only show up after mining for a few hours or days.

On the other hand, your supplier could very well be honest, they might have fixed the hash board and then it just broke again, to them, you could just be lying about it, or you might have overclocked the hash board beyond the max because you think you will get a refund or something, and most importantly, they probably think they did their part and deserve to get paid, if they would refund every sale the will go broke, this business is very complicated, I honestly wouldn't be running one even if I had the tools and the skills needed.

The moral of the story here is to try to send your miners to repair centers that shipping to doesn't cost you a lot, you should always assume that you will have to ship it back to them multiple times, sending the gear overseas to fix it is a huge gamble which will more likely than not end up with a negative outcome.

█▀▀▀











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











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
carlbutler86 (OP)
Jr. Member
*
Offline Offline

Activity: 37
Merit: 6


View Profile
April 14, 2021, 07:29:29 PM
 #14

Well I would check with the shop you bought from first. See if there is any sort of Warranty/RMA that they offer, Either way it was damaged in shipping so hopefully you have some option. If that doesn't work Look into this thread here =Where to fix your Asic miners.

I've had a good experience with HMtech if you are North America based. Apart from that make sure it's worth the cost of repair for that board. (You'll earn back what it costs to repair in mining rewards)

Perfect thank you for that referral! I just sent them an email!

And yes I am talking to the seller to see if I can file a claim with DHL for the damage.

Hi Carl,

just found this topic as I have the same issue and also with the same Supplier Shenzhen Dovina! I have sent them the defect hashboard, they have said they repaired the hashboard and sent it back to me. But again the exact same issue! They didn´t do anything imo and a video is not proof enough! Anyway I have paid 3 times for shipping...

Did they offer you any other solution? I will write a realy bad review, they are a bit afraid of that. But I don´t believe there is more I can do and unfortunately there is nothing I can get...

They were the worst seller on Alibaba, and I bought T17 42T miners from another company on Alibaba around the same time I bought the S17 53 rigs, from Shandong Jiyun co, and same thing, half of them showed up with non working hashboards, questionable PSUs, and all of the miners showed up filthy as all hell, some of them were broken.

I fought with both companies through Alibaba, and I barely got anything of a refund. Just $200.

Thankfully I was able to file claims for both shipments through DHL for the damages, and was able to get a decent amount of claim money back.

I sent all the damaged rigs to HMTech for repair. So far one S53 they said they aren't able to repair the hashboard. They have 5 more miners, and I am hoping they can repair the hashboards on all of them.

I'm done buying from China on Alibaba, they are the worst. They send you the crappiest, dirtiest, most used, barely functioning rigs. And once they get your money, they don't help you at all!
warrenyeo
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
March 15, 2022, 06:31:53 PM
 #15

Well I would check with the shop you bought from first. See if there is any sort of Warranty/RMA that they offer, Either way it was damaged in shipping so hopefully you have some option. If that doesn't work Look into this thread here =Where to fix your Asic miners.

I've had a good experience with HMtech if you are North America based. Apart from that make sure it's worth the cost of repair for that board. (You'll earn back what it costs to repair in mining rewards)

Perfect thank you for that referral! I just sent them an email!

And yes I am talking to the seller to see if I can file a claim with DHL for the damage.

Hi Carl,

just found this topic as I have the same issue and also with the same Supplier Shenzhen Dovina! I have sent them the defect hashboard, they have said they repaired the hashboard and sent it back to me. But again the exact same issue! They didn´t do anything imo and a video is not proof enough! Anyway I have paid 3 times for shipping...

Did they offer you any other solution? I will write a realy bad review, they are a bit afraid of that. But I don´t believe there is more I can do and unfortunately there is nothing I can get...

They were the worst seller on Alibaba, and I bought T17 42T miners from another company on Alibaba around the same time I bought the S17 53 rigs, from Shandong Jiyun co, and same thing, half of them showed up with non working hashboards, questionable PSUs, and all of the miners showed up filthy as all hell, some of them were broken.

I fought with both companies through Alibaba, and I barely got anything of a refund. Just $200.

Thankfully I was able to file claims for both shipments through DHL for the damages, and was able to get a decent amount of claim money back.

I sent all the damaged rigs to HMTech for repair. So far one S53 they said they aren't able to repair the hashboard. They have 5 more miners, and I am hoping they can repair the hashboards on all of them.

I'm done buying from China on Alibaba, they are the worst. They send you the crappiest, dirtiest, most used, barely functioning rigs. And once they get your money, they don't help you at all!

hey!

I have been about to buy the antminer s17 with this distributor (Dovina) and as I see in the comments I do not think it is a good choice to buy there.... Do you think it is advisable to buy on the official website of Bitmain? is there any seller of Alibaba that you recommend? or another website?
BitMaxz
Legendary
*
Offline Offline

Activity: 3248
Merit: 2955


Block halving is coming.


View Profile WWW
March 15, 2022, 11:27:40 PM
 #16

hey!

I have been about to buy the antminer s17 with this distributor (Dovina) and as I see in the comments I do not think it is a good choice to buy there.... Do you think it is advisable to buy on the official website of Bitmain? is there any seller of Alibaba that you recommend? or another website?

Yes, it's recommended to buy directly from the manufacturer or authorized distributor you will most likely scam if you deal to unknown resellers.

you can also try to contact this man offordscott he is the one that I know trusted selling miner.
Or try to check this website https://www.zeusbtc.com/Used-ASIC-Miner/

█▀▀▀











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











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
Pages: [1]
  Print  
 
Jump to:  

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