Bitcoin Forum>Bitcoin>Mining>Mining support
Author

Topic: Antminer T17 will only hash on 2 boards (Read 433 times)

philipma1957
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
Antminer T17 will only hash on 2 boards
June 26, 2020, 03:03:51 PM
#18
Thank you for the followup reply. It is helpful for members to get information on miners struggles to get gear to work.
JamesB88
newbie
Activity: 8
Merit: 5
Re: Antminer T17 will only hash on 2 boards
June 26, 2020, 02:25:28 PM
#17
Hey everyone, just wanted to post an update here on my Antminer T17, as it might help somebody else out in the future. I tried the trick of pulling out the bad board, and putting pressure on the chips/heat sinks, to no avail. Was still getting the temp sensor errors. So then I decided to try and flash Asic.to firmware to the miner. It's a very simple process. Just created a temporary SD card firmware, and once that was loaded, I simply downloaded their Asic.to firmware and flashed it to the miner... very detailed instructions on their website as to how to flash it. Once I got this firmware running, that 3rd board IMMEDIATELY started working again! It's hashing just as it should, 40T, pulling 2,000 watts and everything looks good on the pool end as well. I couldn't be any happier, thinking I was going to have to send this bad board in for repair. Another thing is this firmware is amazing! There are SO many different settings and options I am going to be playing around with. Supposedly, you can down volt and get an efficiency as low as 45W/Th, which is 10W below the rated 55W/Th on a T17. You can also overclock, and get a much higher hashrate, but I am more a fan of down clocking for efficiency. I have been able to achieve a 70W/Th rating with my S9j's running Braiins OS firmware. Anyway, anxious to see what I can achieve with this new firmware, and it will be going on all of my S and T17 series Antminers now. Thanks so much again for all the help here, and I hope this will be good info for someone else to use.
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: Antminer T17 will only hash on 2 boards
June 02, 2020, 03:04:05 PM
#16
Quote from: sale023 on June 01, 2020, 03:09:40 PM
In that case I might put the whole hash board into the oven for 10 minutes at 200C. Maybe it will help Cheesy

That will be a perfect way to toast all 30 asics including the 29 chips which are likely working just fine at the moment, asic boards are very different from those GPUs (this does not mean this method will actually work and not damage a GPU) but the chips on these boards have a max temp of 100c or below depending on the model, putting them under heat for 10 mins will most likely break all of them, please don't do that, follow the proper method of fixing the soldering on the bad chip.
danieleither
full member
Activity: 219
Merit: 426
Re: Antminer T17 will only hash on 2 boards
June 01, 2020, 05:43:49 PM
#15
Quote from: sale023 on June 01, 2020, 03:09:40 PM
In that case I might put the whole hash board into the oven for 10 minutes at 200C. Maybe it will help Cheesy

Whilst I wouldn't advise this... I have heard of this method working to fix faulty graphics cards!
BitMaxz
legendary
Activity: 3374
Merit: 3095
Playbet.io - Crypto Casino and Sportsbook
Re: Antminer T17 will only hash on 2 boards
June 01, 2020, 05:43:11 PM
#14
Quote from: sale023 on June 01, 2020, 03:09:40 PM
In that case I might put the whole hash board into the oven for 10 minutes at 200C. Maybe it will help Cheesy

How about trying to dump the hex file first from known working hashboard then flash the hex file to this faulty hashboard. It might be a hashboard program issue that's why it gets 0 ASIC.

Don't touch the hardware first because sometimes the issue is related only to software/program so if you put it to the oven the issue might getting worst and won't be able to find the real issue.

Try another possible solution first like this one below
- https://bitcointalksearch.org/topic/repair-a-t9-after-a-bad-firmware-lost-chain-5032987

I don't know if this pickit3 will work on t17 hashboard but it works on old hashboards.
sale023
newbie
Activity: 3
Merit: 0
Re: Antminer T17 will only hash on 2 boards
June 01, 2020, 03:09:40 PM
#13
In that case I might put the whole hash board into the oven for 10 minutes at 200C. Maybe it will help Cheesy
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: Antminer T17 will only hash on 2 boards
June 01, 2020, 02:27:17 PM
#12
Code:
2020-06-01 15:38:33 driver-btm-api.c:1037:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2

Troubleshooting the 17 series gears make you feel like a robot, it's almost always the same cause for every problem out there, what you described sounds like a bad connection on one of the chips/heatsinks, due to bad soldering in most cases, at least based on my personal experience and the data I collect from research and asking around, a chain that shows 0 asic in most cases has a fault chip number 1, so for your case with the T17, you can use this image to identity that chip.



Keep in mind that it's not always chip 0, the solution to this is to identify the bad chip/heatsink, usually, if the soldering is too bad and just about to fail, applying side pressure using your finger/s can be enough to remove to the bad chip, you have to do that on the 30 chips that have the larger heatsinks and not the once at the back, and once that chip falls off, you have to resolder it, and that is a whole different story.

Also if you are lucky, applying some pressure at the top of all 30 chips (pressing them down while the board is flat on a solid surface) will help with the connection, as weird as it sounds, it does work at times, also the chip could eventually re-solder itself if kept under heat coming from the other working boards, but it is unlikely, so try the pressure trick, if it doesn't work, you will need to remove the bad chip and re-solder it.

Quote from: Pendrak on June 01, 2020, 01:44:23 PM
Just cry like me, i lost my only high end equipment i have (a T17) after a 1 month of use, i cant send it back, cost too much. Soo is time to cry.

If I were to cry over every board I lost on shitty bitmain gears, I would have caused floods that will sink the other working boards  Cry, losing a board or a miner is something you should get used to when dealing with bitmain gears, sadly I have only released this a bit too late, but better late than never, no more 17 series for me.
Pendrak
member
Activity: 208
Merit: 46
Re: Antminer T17 will only hash on 2 boards
June 01, 2020, 01:44:23 PM
#11
Just cry like me, i lost the only high end equipment i have (a T17) after a 1 month of use, i cant send it back, cost too much. Soo is time to cry.
sale023
newbie
Activity: 3
Merit: 0
Re: Antminer T17 will only hash on 2 boards
June 01, 2020, 10:50:34 AM
#10
Hi there good people! Can I jump in on a bad T17 train with you? Cheesy I have an issue of different kind. My miner detects 0 chips on one of the boards when doing initialisation. On every 20-30 restarts it detects 30 chips and it works without any issues until next power outage or something like that. And then it's all over again. It's a T17-42TH Cheesy

Here's my 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: 203756K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25620K 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 
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: 12580K (cceb8000 - 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 MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
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: 24/10, WL threshold: 4096, image sequence number: 72543235
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 D94047F6-1175-4366-977B-837CC879EE19, 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: 360/71, WL threshold: 4096, image sequence number: 3389548455
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 721E72E7-F382-4130-AD9F-6C10D9102537, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-06-01 15:36:32 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2020-06-01 15:36:32 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version     = 1
2020-06-01 15:36:32 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab        = 1
2020-06-01 15:36:32 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-06-01 15:36:32 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2020-06-01 15:36:32 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2020-06-01 15:36:32 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2020-06-01 15:36:32 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2020-06-01 15:36:32 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2020-06-01 15:36:32 thread.c:789:create_read_nonce_reg_thread: create thread
2020-06-01 15:36:38 driver-btm-api.c:1067:init_miner_version: miner ID : 814cf4025c20885c
2020-06-01 15:36:38 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-06-01 15:36:40 eeprom.c:456:check_pattern_test_level: L6 board
2020-06-01 15:36:41 eeprom.c:456:check_pattern_test_level: L6 board
2020-06-01 15:36:43 eeprom.c:456:check_pattern_test_level: L6 board
2020-06-01 15:36:43 eeprom.c:545:eeprom_load: try higher voltage open core
2020-06-01 15:36:43 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-06-01 15:36:43 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-06-01 15:36:43 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-06-01 15:36:43 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-06-01 15:36:43 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-06-01 15:36:43 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-06-01 15:36:43 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-06-01 15:36:43 driver-btm-api.c:644:_set_project_type: project:2
2020-06-01 15:36:43 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-06-01 15:36:43 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-06-01 15:36:43 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-06-01 15:36:43 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-06-01 15:36:43 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-06-01 15:36:43 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-06-01 15:36:43 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-06-01 15:36:43 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-06-01 15:36:45 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-06-01 15:36:48 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-06-01 15:36:50 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-06-01 15:36:54 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-06-01 15:36:55 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-06-01 15:36:59 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-06-01 15:36:59 thread.c:784:create_pic_heart_beat_thread: create thread
2020-06-01 15:36:59 power_api.c:55:power_init: power init ... 
2020-06-01 15:36:59 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-06-01 15:36:59 power_api.c:46:power_off: init gpio907
2020-06-01 15:37:31 power_api.c:264:set_iic_power_to_custom_voltage: setting to voltage: 18.00 ...
2020-06-01 15:37:37 power_api.c:124:check_voltage_multi: retry time: 0
2020-06-01 15:37:38 power_api.c:86:get_average_voltage: chain[0], voltage is: 19.330459 
2020-06-01 15:37:40 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.669170 
2020-06-01 15:37:42 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.124219 
2020-06-01 15:37:42 power_api.c:97:get_average_voltage: aveage voltage is: 18.707949 
2020-06-01 15:37:42 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 18.000000 
2020-06-01 15:37:42 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-06-01 15:37:42 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-06-01 15:37:42 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-06-01 15:37:42 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-06-01 15:37:53 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2020-06-01 15:38:03 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-06-01 15:38:13 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2020-06-01 15:38:23 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2020-06-01 15:38:33 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2020-06-01 15:38:33 driver-btm-api.c:1037:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2020-06-01 15:38:37 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0xff
2020-06-01 15:38:37 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0xff
2020-06-01 15:38:37 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-06-01 15:38:37 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-06-01 15:38:37 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-06-01 15:38:37 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-06-01 15:38:37 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-06-01 15:38:38 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-06-01 15:38:38 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-06-01 15:38:38 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-06-01 15:38:38 voltage[0] = 1690
2020-06-01 15:38:38 voltage[1] = 1690
2020-06-01 15:38:38 power_api.c:140:set_working_voltage: working_voltage = 16.900000
2020-06-01 15:38:39 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-06-01 15:38:40 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-06-01 15:38:40 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-06-01 15:38:40 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-06-01 15:38:40 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-06-01 15:38:42 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 23
2020-06-01 15:38:42 thread.c:804:create_check_miner_status_thread: create thread
2020-06-01 15:38:42 thread.c:794:create_set_miner_status_thread: create thread
2020-06-01 15:38:42 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-06-01 15:38:42 thread.c:779:create_temperature_monitor_thread: create thread
2020-06-01 15:38:42 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2020-06-01 15:38:42 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.80 ...
2020-06-01 15:39:02 power_api.c:124:check_voltage_multi: retry time: 0
2020-06-01 15:39:05 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.989511 
2020-06-01 15:39:08 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.940527 
2020-06-01 15:39:08 power_api.c:97:get_average_voltage: aveage voltage is: 17.965019 
2020-06-01 15:39:08 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-06-01 15:39:08 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-06-01 15:39:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-06-01 15:39:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-06-01 15:39:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-06-01 15:39:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-06-01 15:39:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-06-01 15:39:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-06-01 15:39:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-06-01 15:39:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-06-01 15:39:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-06-01 15:39:09 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-06-01 15:39:10 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-06-01 15:39:10 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-06-01 15:39:10 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-06-01 15:39:10 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-06-01 15:39:10 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-06-01 15:39:10 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-06-01 15:39:10 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-06-01 15:39:10 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-06-01 15:39:10 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-06-01 15:39:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-06-01 15:39:11 driver-btm-api.c:612:set_timeout: freq 720 final timeout=163
2020-06-01 15:39:11 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 16.90 ...
2020-06-01 15:39:39 power_api.c:124:check_voltage_multi: retry time: 0
2020-06-01 15:39:41 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.028193 
2020-06-01 15:39:43 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.003701 
2020-06-01 15:39:43 power_api.c:97:get_average_voltage: aveage voltage is: 17.015947 
2020-06-01 15:39:43 frequency.c:540:get_current_min_freq: current min freq 720
2020-06-01 15:39:43 driver-btm-api.c:1660:check_clock_counter: freq 720 clock_counter_limit 92
2020-06-01 15:39:44 thread.c:799:create_check_system_status_thread: create thread
2020-06-01 15:39:45 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2020-06-01 15:39:45 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2020-06-01 15:39:50 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-06-01 15:39:55 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4

Things i've tried so far:
I've tried to disconnect all the boards except the faulty one and start the miner, it's still faulty
I've tried to switch cables, connected the faulty board on a cable of a good board, then that chain becomes faulty, so it's not cable issue, the board itself seems to have an issue.
I've tried with a custom firmware. Same result.

Any suggestions? Cheesy
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: Antminer T17 will only hash on 2 boards
May 31, 2020, 05:35:48 AM
#9
Quote from: JamesB88 on May 30, 2020, 08:44:58 PM
2020-05-31 01:38:46 temperature.c:203:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 6, type = 0x0, retry.
2020-05-31 01:38:46 temperature.c:203:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 6, type = 0x0, retry.
2020-05-31 01:38:47 temperature.c:203:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 6, type = 0x0, retry.
2020-05-31 01:38:47 temperature.c:203:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 6, type = 0x0, retry.

This confirms my previous wild guess, you have a faulty heatsink/chip, don't let the kernel log deceive you, the chances of 4 sensors going down at the same time are less than your chances of hitting a block with an old Nokia, can you take out the board and apply some pressure on all the heat sinks and then put it back in the miner and power it on, this might (with a low probability) fix the issue for some time, but eventually, it will stop hashing again, one or more of the chips or heatsinks need re-soldering sadly, if you are interested in doing so I can post some tutorials and the tools needed for the task.

Also, you could try a custom firmware to see if you get any luck, some people reported some positive results in that regards, use Asic.to for testing, I guess with that firmware if it manages to read 1 sensor at least, the board will hash away with whatever asics it finds, sometimes once you get the board to work for a while on different firmware, going back to the original firmware will make it work too, as strange as it sounds, it happens.
JamesB88
newbie
Activity: 8
Merit: 5
Re: Antminer T17 will only hash on 2 boards
May 30, 2020, 08:44:58 PM
#8
Okay, finally got around to hooking up that third chain, and getting the kernel log. Here it is:

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: 203756K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25620K 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 
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: 12580K (cceb8000 - 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 MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
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: 14/6, WL threshold: 4096, image sequence number: 72543235
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 D94047F6-1175-4366-977B-837CC879EE19, 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: 930/167, WL threshold: 4096, image sequence number: 3389548455
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 721E72E7-F382-4130-AD9F-6C10D9102537, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-05-31 01:36:58 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2020-05-31 01:36:58 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version     = 1
2020-05-31 01:36:58 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab        = 1
2020-05-31 01:36:58 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-05-31 01:36:58 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2020-05-31 01:36:58 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2020-05-31 01:36:58 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2020-05-31 01:36:58 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2020-05-31 01:36:58 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2020-05-31 01:36:58 thread.c:789:create_read_nonce_reg_thread: create thread
2020-05-31 01:37:04 driver-btm-api.c:1067:init_miner_version: miner ID : 8152c42e5740885c
2020-05-31 01:37:04 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-31 01:37:06 eeprom.c:431:check_pattern_test_level: L1 board
2020-05-31 01:37:07 eeprom.c:431:check_pattern_test_level: L1 board
2020-05-31 01:37:09 eeprom.c:431:check_pattern_test_level: L1 board
2020-05-31 01:37:09 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-31 01:37:09 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-31 01:37:09 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-05-31 01:37:09 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-31 01:37:09 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-31 01:37:09 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-05-31 01:37:09 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-31 01:37:09 driver-btm-api.c:644:_set_project_type: project:2
2020-05-31 01:37:09 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-31 01:37:09 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-31 01:37:09 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-31 01:37:09 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-31 01:37:09 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-31 01:37:09 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-31 01:37:09 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-31 01:37:10 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-31 01:37:12 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-31 01:37:15 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-31 01:37:17 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-31 01:37:21 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-31 01:37:22 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-31 01:37:26 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-05-31 01:37:26 thread.c:784:create_pic_heart_beat_thread: create thread
2020-05-31 01:37:26 power_api.c:55:power_init: power init ... 
2020-05-31 01:37:26 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-31 01:37:58 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-31 01:38:04 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-31 01:38:05 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.077178 
2020-05-31 01:38:07 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.064931 
2020-05-31 01:38:09 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.040439 
2020-05-31 01:38:09 power_api.c:97:get_average_voltage: aveage voltage is: 17.060849 
2020-05-31 01:38:09 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000 
2020-05-31 01:38:09 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-31 01:38:09 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-31 01:38:09 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-31 01:38:09 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-31 01:38:20 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2020-05-31 01:38:30 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-31 01:38:41 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-05-31 01:38:44 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-31 01:38:44 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-31 01:38:44 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-05-31 01:38:45 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-31 01:38:45 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-31 01:38:45 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-31 01:38:45 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-05-31 01:38:45 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-31 01:38:45 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-31 01:38:45 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-31 01:38:45 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-31 01:38:45 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-31 01:38:45 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-31 01:38:45 voltage[0] = 1690
2020-05-31 01:38:45 voltage[1] = 1690
2020-05-31 01:38:45 voltage[2] = 1690
2020-05-31 01:38:45 power_api.c:140:set_working_voltage: working_voltage = 16.900000
2020-05-31 01:38:46 temperature.c:203:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 6, type = 0x0, retry.
2020-05-31 01:38:46 temperature.c:203:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 6, type = 0x0, retry.
2020-05-31 01:38:47 temperature.c:203:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 6, type = 0x0, retry.
2020-05-31 01:38:47 temperature.c:203:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 6, type = 0x0, retry.
2020-05-31 01:38:47 driver-btm-api.c:201:set_miner_status: ERROR_TEMP_LOST
2020-05-31 01:38:47 driver-btm-api.c:142:stop_mining: stop mining: Can't get temperature sensor type!
2020-05-31 01:38:47 thread.c:834:cancel_read_nonce_reg_thread: cancel thread
2020-05-31 01:38:47 driver-btm-api.c:128:killall_hashboard: ****power off hashboard****

Thank you again for the help you have given me already!
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: Antminer T17 will only hash on 2 boards
May 26, 2020, 09:50:24 PM
#7
Quote from: JamesB88 on May 26, 2020, 08:26:37 PM
What you're saying about the heatsinks/chips soldering makes good since, hopefully this is something I could re solder myself if it is indeed the case. Thanks again!

You will need a few tools and a bit of skill for obvious reason, honestly it is only worth it if you plan on doing it more often, but investing in the tools just to fix a single board might not make any sense economical wise, with that being said if you own a few 17 series it is only a matter of time before the same problem happens to other boards, but let's hope your luck will save you.

Quote my post or mention my name when you post the kernel log so that i get notified about it.
JamesB88
newbie
Activity: 8
Merit: 5
Re: Antminer T17 will only hash on 2 boards
May 26, 2020, 08:26:37 PM
#6
Thanks so much for your reply, and willingness to help me, I truly appreciate it. I will get the full kernel log within the next day and post it here for you to see. What you're saying about the heatsinks/chips soldering makes good since, hopefully this is something I could re solder myself if it is indeed the case. Thanks again!
BitMaxz
legendary
Activity: 3374
Merit: 3095
Playbet.io - Crypto Casino and Sportsbook
Re: Antminer T17 will only hash on 2 boards
May 26, 2020, 06:08:14 PM
#5
Don't forget to start cleaning first before you touch any components from the hash board because sometimes the sensor giving false temp due to dirt, dust, and corrosion.

Cleaning them first, if you have a thinner, Laquer Flo uses a brush to clean all parts of the hashboard not only the temp sensor.

Also, if you have a hot air blower, you can heat/reflow the sensor parts if the cleanings don't work or if you don't have hotair you can use the oven to reheat the whole hashboard. Get the idea from this video https://youtu.be/8Xanr4jkmEc.
JamesB88
newbie
Activity: 8
Merit: 5
Re: Antminer T17 will only hash on 2 boards
May 26, 2020, 05:31:39 PM
#4
Quote from: Pendrak on May 25, 2020, 09:18:15 PM
[...]

Hey thanks for sharing this, very much appreciated!
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: Antminer T17 will only hash on 2 boards
May 26, 2020, 04:02:23 AM
#3
Quote from: JamesB88 on May 25, 2020, 06:32:55 PM
My question is, is this something I can repair myself, can I replace this "temp sensor," or do I need to send it in for repair? Are there any other suggestions I can try? Thanks!

First thing you should post the kernel log, the complete kernel log while chain 0 is plugged in, use the code function to paste the kernel log like so

Code:
kernel log goes here

A wild guess based on what I already know, you have one or more heatsinks/chips with bad soldering which has lost contact to the board, it causing a problem in the electricity flow within the board and stopping the temp sensors from working, the control board "thinks" all 4 temp sensors are bad so it does not allow the chain to mine for safety purposes.

What to do and how to fix it is a different topic, i will guide you through it once I see the kernel log.
Pendrak
member
Activity: 208
Merit: 46
Re: Antminer T17 will only hash on 2 boards
May 25, 2020, 09:18:15 PM
#2
Welcome to the club

https://bitcointalksearch.org/topic/antminer-t17s17-temp-sensor-problem-discussion-5244120

https://cointelegraph.com/news/samson-mow-bitmain-s17-t17-antminer-has-high-failure-rate
JamesB88
newbie
Activity: 8
Merit: 5
Re: Antminer T17 will only hash on 2 boards
May 25, 2020, 06:32:55 PM
#1
Hello, I am getting an error in the kernal log of my T17 that reads "temperature.c:203:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 6, type = 0x0, retry." After this, the miner powers down all hashboards and will not mine. I have swapped power supplies, with a known good one from another T17, as well as the control board. I have figured out, that if I disconnect the board chain 0, it will boot up and mine just fine at 27T with 2 boards, so it is obviously an issue with this one hashboard. My question is, is this something I can repair myself, can I replace this "temp sensor," or do I need to send it in for repair? Are there any other suggestions I can try? Thanks!

-James.
Bitcoin Forum>Bitcoin>Mining>Mining support
Jump to: