massivegoatdynamic (OP)
Newbie
 Offline
Activity: 19
Merit: 0
|
 |
January 11, 2023, 04:17:48 AM |
|
Hello all. I bought a used S17+ last year and didn't get around to plugging it in until this past week. The seller sent me a video of the thing working before shipping and of course I get it and I can't get it to mine. I get 2 error messages "Socket Connect Failed: Connection refused" and when I go into network diagnostic and hit "ping" I get the message "6 packets transmitted, 0 packets received, 100% packet loss. I have put the latest firmware from bitmain on there, rebooted it, hit the reset button on the machine, the IP search button and occasionally the "socket connect failed" message disappears but it never mines. Any thoughts on how I could get it to move? I am thinking of trying Slush Pools firmware to see if it acts any different.
The kernel readout has a ton of output, the only thing that stands out is: 2023-01-10 23:28:28 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
And does this mean it is actually the third hashboard "chain 2"? I am guessing that means the 14th chip on the third hashboard might be bad?
Any input would be greatly appreciated.
Also is there a cheat sheet of sorts to understand what all is going on in the kernel log? It kicks out a lot of information but I don't know what it means.
|
|
|
|
|
|
|
massivegoatdynamic (OP)
Newbie
Offline
Activity: 19
Merit: 0
|
|
January 11, 2023, 12:21:59 PM |
|
Do you think the "temp issue" which is likely a bad chip or solder job could explain the "socket connect failed" message or the "6 packets transmitted, 0 packets received" message? The socket connect failed message is intermittent, it occasionally goes away and you can go to the Miner status stab and see 2/3 hashboards attemping to work.
|
|
|
|
|
BitMaxz
Legendary
Offline
Activity: 3444
Merit: 3175
Playbet.io - Crypto Casino and Sportsbook
|
|
January 11, 2023, 04:40:59 PM |
|
Oh wow, zeusbtc has a new account here but it's weird he is promoting a different link instead of their own guide.
@OP would you mind posting the whole kernel logs here so that we can check exactly what your miner problem is?
If it's not normally running fine try to remove the 3rd hashboard and let it run while the other hash board is connected.
If it's running fine the 3rd hashboard is bad without the whole kernel logs I can't give you a few suggestions so try to post the whole kernel logs here or paste it to pastebin.com and paste the link here.
|
|
|
|
massivegoatdynamic (OP)
Newbie
Offline
Activity: 19
Merit: 0
|
|
January 12, 2023, 02:58:12 AM
Last edit: January 17, 2023, 03:15:11 AM by massivegoatdynamic |
|
I had peeked under the hood before but didn't notice what appears to be QC stickers on the 3rd hash board. I guess that board has had issues before and they did a bad patch job. I unplugged the third hash board turned the unit on and got a fault light. Hit the reset button on the back and after hitting the IP report button it seemed to try to mine (Normal Light was on) and heat coming off of the miner. The hardware error went away and it seemed to be trying but I still cant get a good "ping" diagnostic. Also of note was the fan was throttling down and up. No luck  What are the odds that I get a video of the thing working in china and then it arriving here, sitting for a few months and my first attempt at mining I get these errors? Are these issues typical of something happening during transit? Apologies for the large amount of text, I didn't see a button to attach a file. This is the kernel log after removing the third hashboard and it sounding like it was trying to mine. 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: 203432K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25944K 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: 12904K (cce67000 - 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: 21/10, WL threshold: 4096, image sequence number: 237714726
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 FF09433B-E002-4C29-97EC-6220DDC4BB36, 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: 4099/1014, WL threshold: 4096, image sequence number: 3265111179
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 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
macb e000b000.ethernet eth0: link down
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
2023-01-12 01:47:32 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2023-01-12 01:47:32 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version = 1
2023-01-12 01:47:32 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab = 1
2023-01-12 01:47:32 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2023-01-12 01:47:32 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun 2 10:31:07 CST 2020 type: Antminer S17+
2023-01-12 01:47:32 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2023-01-12 01:47:32 driver-btm-api.c:2083:show_sn: len:16, 80244d0c2b104814
2023-01-12 01:47:32 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2023-01-12 01:47:32 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2023-01-12 01:47:32 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 80244d0c2b104814
2023-01-12 01:47:32 fan.c:284:front_fan_power_on: Note: front fan is power on!
2023-01-12 01:47:32 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2023-01-12 01:47:32 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2023-01-12 01:47:32 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2023-01-12 01:47:38 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-12 01:47:38 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-12 01:47:42 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2023-01-12 01:47:42 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2023-01-12 01:47:42 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2023-01-12 01:47:42 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2023-01-12 01:47:42 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2023-01-12 01:47:42 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2023-01-12 01:47:42 thread.c:1363:create_read_nonce_reg_thread: create thread
2023-01-12 01:47:48 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-12 01:47:48 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-12 01:47:51 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2023-01-12 01:47:51 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2023-01-12 01:47:51 driver-btm-api.c:792:_set_project_type: project:0
2023-01-12 01:47:51 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2023-01-12 01:47:51 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2023-01-12 01:47:51 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2023-01-12 01:47:51 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2023-01-12 01:47:51 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2023-01-12 01:47:55 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2023-01-12 01:47:56 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2023-01-12 01:47:58 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2023-01-12 01:47:59 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2023-01-12 01:48:01 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2023-01-12 01:48:01 thread.c:1358:create_pic_heart_beat_thread: create thread
2023-01-12 01:48:01 power_api.c:213:power_init: Power init:
2023-01-12 01:48:01 power_api.c:214:power_init: current_voltage_raw = 0
2023-01-12 01:48:01 power_api.c:215:power_init: highest_voltage_raw = 2100
2023-01-12 01:48:01 power_api.c:216:power_init: working_voltage_raw = 1950
2023-01-12 01:48:01 power_api.c:217:power_init: higher_voltage_raw = 2040
2023-01-12 01:48:01 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2023-01-12 01:48:01 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2023-01-12 01:48:33 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2023-01-12 01:48:59 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-12 01:49:00 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.156368
2023-01-12 01:49:01 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.148242
2023-01-12 01:49:01 power_api.c:53:_get_avg_voltage: average_voltage = 21.152305
2023-01-12 01:49:01 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.15, check voltage passed.
2023-01-12 01:49:01 uart.c:72:set_baud: set fpga_baud to 115200
2023-01-12 01:49:12 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2023-01-12 01:49:23 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2023-01-12 01:49:29 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2023-01-12 01:49:29 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2023-01-12 01:49:29 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2023-01-12 01:49:29 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2023-01-12 01:49:29 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2023-01-12 01:49:30 voltage[0] = 1980
2023-01-12 01:49:30 voltage[1] = 1980
2023-01-12 01:49:30 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1980
2023-01-12 01:49:31 temperature.c:340:calibrate_temp_sensor_one_chain: chain 0 temp sensor TMP451
2023-01-12 01:49:32 temperature.c:340:calibrate_temp_sensor_one_chain: chain 1 temp sensor NCT218
2023-01-12 01:49:32 uart.c:72:set_baud: set fpga_baud to 12000000
2023-01-12 01:49:33 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 23
2023-01-12 01:49:33 thread.c:1378:create_check_miner_status_thread: create thread
2023-01-12 01:49:33 thread.c:1368:create_show_miner_status_thread: create thread
2023-01-12 01:49:33 thread.c:1348:create_temperature_monitor_thread: create thread
2023-01-12 01:49:33 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 23 dec_freq_index=0
2023-01-12 01:49:33 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2023-01-12 01:49:33 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2023-01-12 01:49:33 thread.c:1338:create_asic_status_monitor_thread: create thread
2023-01-12 01:49:33 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 550, is_higher_voltage = true
2023-01-12 01:50:46 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2023-01-12 01:50:48 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-12 01:50:50 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.986147
2023-01-12 01:50:51 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.978669
2023-01-12 01:50:51 power_api.c:53:_get_avg_voltage: average_voltage = 20.982408
2023-01-12 01:50:51 power_api.c:71:check_voltage: target_vol = 20.90, actural_vol = 20.98, check voltage passed.
2023-01-12 01:55:10 driver-btm-api.c:765:set_timeout: freq = 550, percent = 90, hcn = 44236, timeout = 80
2023-01-12 01:55:10 power_api.c:310:set_to_working_voltage_by_steps: Set to voltage raw 1980, step by step.
2023-01-12 01:55:15 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-12 01:55:17 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 19.933250
2023-01-12 01:55:18 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 19.882057
2023-01-12 01:55:18 power_api.c:53:_get_avg_voltage: average_voltage = 19.907653
2023-01-12 01:55:18 power_api.c:71:check_voltage: target_vol = 19.80, actural_vol = 19.91, check voltage passed.
2023-01-12 01:55:18 thread.c:1373:create_check_system_status_thread: create thread
2023-01-12 01:55:19 driver-btm-api.c:2618:bitmain_soc_init: Init done!
2023-01-12 01:55:19 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2023-01-12 01:55:23 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2023-01-12 01:55:24 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 46846
2023-01-12 01:55:24 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 46000
2023-01-12 01:55:28 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2023-01-12 01:55:28 driver-btm-api.c:1644:dhash_chip_send_job: stime.tv_sec 1673488528, block_ntime 1673488527
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 0, chip = 42, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 0, chip = 42, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 0, chip = 42, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 0, chip = 30, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 0, chip = 162, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 0, chip = 150, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 1, chip = 42, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 1, chip = 30, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 1, chip = 30, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 1, chip = 30, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 1, chip = 162, reg = 28
2023-01-12 01:58:47 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 0, chip = 30, reg = 28
2023-01-12 01:58:47 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 1, chip = 30, reg = 28
2023-01-12 01:58:49 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 0, chip = 42, reg = 28
2023-01-12 01:58:49 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 0, chip = 42, reg = 28
2023-01-12 01:58:49 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 0, chip = 162, reg = 28
2023-01-12 01:58:50 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 0, chip = 150, reg = 28
2023-01-12 01:58:50 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 0, chip = 150, reg = 28
2023-01-12 01:58:50 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 1, chip = 42, reg = 28
2023-01-12 01:58:50 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 1, chip = 30, reg = 28
2023-01-12 01:58:50 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 1, chip = 162, reg = 28
2023-01-12 01:58:50 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 1, chip = 162, reg = 28
2023-01-12 02:03:22 thread.c:1383:create_shutdown_thread: create thread
2023-01-12 02:03:22 driver-btm-api.c:222:set_miner_status: STATUS_SHUTDOWN
2023-01-12 02:03:22 thread.c:1419:cancel_check_miner_status_thread: cancel thread
2023-01-12 02:03:22 thread.c:1388:cancel_temperature_monitor_thread: cancel thread
2023-01-12 02:03:22 thread.c:1414:cancel_check_system_status_thread: cancel thread
2023-01-12 02:03:22 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2023-01-12 02:03:22 thread.c:1343:cancel_asic_status_monitor_thread: cancel thread
2023-01-12 02:03:24 thread.c:575:slowly_decrease_freq: set to 550M, delay 3000
2023-01-12 02:03:27 thread.c:575:slowly_decrease_freq: set to 545M, delay 3000
2023-01-12 02:03:30 thread.c:575:slowly_decrease_freq: set to 540M, delay 3000
2023-01-12 02:03:33 thread.c:575:slowly_decrease_freq: set to 535M, delay 3000
2023-01-12 02:03:36 thread.c:575:slowly_decrease_freq: set to 530M, delay 3000
2023-01-12 02:03:39 thread.c:575:slowly_decrease_freq: set to 525M, delay 3000
2023-01-12 02:03:42 thread.c:575:slowly_decrease_freq: set to 520M, delay 3000
2023-01-12 02:03:45 thread.c:575:slowly_decrease_freq: set to 515M, delay 3000
2023-01-12 02:03:48 thread.c:575:slowly_decrease_freq: set to 510M, delay 3000
2023-01-12 02:03:52 thread.c:575:slowly_decrease_freq: set to 505M, delay 3000
2023-01-12 02:03:55 thread.c:575:slowly_decrease_freq: set to 500M, delay 3000
2023-01-12 02:03:58 thread.c:575:slowly_decrease_freq: set to 495M, delay 3000
2023-01-12 02:04:01 thread.c:575:slowly_decrease_freq: set to 490M, delay 3000
2023-01-12 02:04:04 thread.c:575:slowly_decrease_freq: set to 485M, delay 3000
2023-01-12 02:04:07 thread.c:575:slowly_decrease_freq: set to 480M, delay 3000
2023-01-12 02:04:10 thread.c:575:slowly_decrease_freq: set to 475M, delay 3000
2023-01-12 02:04:13 thread.c:575:slowly_decrease_freq: set to 470M, delay 3000
2023-01-12 02:04:16 thread.c:575:slowly_decrease_freq: set to 465M, delay 3000
2023-01-12 02:04:19 thread.c:575:slowly_decrease_freq: set to 460M, delay 3000
2023-01-12 02:04:22 thread.c:575:slowly_decrease_freq: set to 455M, delay 3000
2023-01-12 02:04:25 thread.c:575:slowly_decrease_freq: set to 450M, delay 3000
2023-01-12 02:04:28 thread.c:575:slowly_decrease_freq: set to 445M, delay 3000
2023-01-12 02:04:31 thread.c:575:slowly_decrease_freq: set to 440M, delay 3000
2023-01-12 02:04:34 thread.c:575:slowly_decrease_freq: set to 435M, delay 3000
2023-01-12 02:04:37 thread.c:575:slowly_decrease_freq: set to 430M, delay 3000
2023-01-12 02:04:40 thread.c:575:slowly_decrease_freq: set to 425M, delay 3000
2023-01-12 02:04:43 thread.c:575:slowly_decrease_freq: set to 420M, delay 3000
2023-01-12 02:04:46 thread.c:575:slowly_decrease_freq: set to 415M, delay 3000
2023-01-12 02:04:49 thread.c:575:slowly_decrease_freq: set to 410M, delay 3000
2023-01-12 02:04:52 thread.c:575:slowly_decrease_freq: set to 405M, delay 3000
2023-01-12 02:04:55 thread.c:575:slowly_decrease_freq: set to 400M, delay 3000
2023-01-12 02:04:58 thread.c:575:slowly_decrease_freq: set to 395M, delay 3000
2023-01-12 02:05:01 thread.c:575:slowly_decrease_freq: set to 390M, delay 3000
2023-01-12 02:05:04 thread.c:575:slowly_decrease_freq: set to 385M, delay 3000
2023-01-12 02:05:07 thread.c:575:slowly_decrease_freq: set to 380M, delay 3000
2023-01-12 02:05:10 thread.c:575:slowly_decrease_freq: set to 375M, delay 3000
2023-01-12 02:05:13 thread.c:575:slowly_decrease_freq: set to 370M, delay 3000
2023-01-12 02:05:16 thread.c:575:slowly_decrease_freq: set to 365M, delay 3000
2023-01-12 02:05:19 thread.c:575:slowly_decrease_freq: set to 360M, delay 3000
2023-01-12 02:05:22 thread.c:575:slowly_decrease_freq: set to 355M, delay 3000
2023-01-12 02:05:25 thread.c:575:slowly_decrease_freq: set to 350M, delay 3000
2023-01-12 02:05:28 thread.c:575:slowly_decrease_freq: set to 345M, delay 3000
2023-01-12 02:05:31 thread.c:575:slowly_decrease_freq: set to 340M, delay 3000
2023-01-12 02:05:34 thread.c:575:slowly_decrease_freq: set to 335M, delay 3000
2023-01-12 02:05:37 thread.c:575:slowly_decrease_freq: set to 330M, delay 3000
2023-01-12 02:05:40 thread.c:575:slowly_decrease_freq: set to 325M, delay 3000
2023-01-12 02:05:43 thread.c:575:slowly_decrease_freq: set to 320M, delay 3000
2023-01-12 02:05:46 thread.c:575:slowly_decrease_freq: set to 315M, delay 3000
2023-01-12 02:05:49 thread.c:575:slowly_decrease_freq: set to 310M, delay 3000
2023-01-12 02:05:52 thread.c:575:slowly_decrease_freq: set to 305M, delay 3000
2023-01-12 02:05:55 thread.c:575:slowly_decrease_freq: set to 300M, delay 3000
2023-01-12 02:05:58 thread.c:575:slowly_decrease_freq: set to 295M, delay 3000
2023-01-12 02:06:01 thread.c:575:slowly_decrease_freq: set to 290M, delay 3000
2023-01-12 02:06:04 thread.c:575:slowly_decrease_freq: set to 285M, delay 3000
2023-01-12 02:06:07 thread.c:575:slowly_decrease_freq: set to 280M, delay 3000
2023-01-12 02:06:10 thread.c:575:slowly_decrease_freq: set to 275M, delay 3000
2023-01-12 02:06:13 thread.c:575:slowly_decrease_freq: set to 270M, delay 3000
2023-01-12 02:06:16 thread.c:575:slowly_decrease_freq: set to 265M, delay 3000
2023-01-12 02:06:19 thread.c:575:slowly_decrease_freq: set to 260M, delay 3000
2023-01-12 02:06:22 thread.c:575:slowly_decrease_freq: set to 255M, delay 3000
2023-01-12 02:06:25 thread.c:575:slowly_decrease_freq: set to 250M, delay 3000
2023-01-12 02:06:28 thread.c:575:slowly_decrease_freq: set to 245M, delay 3000
2023-01-12 02:06:31 thread.c:575:slowly_decrease_freq: set to 240M, delay 3000
2023-01-12 02:06:34 thread.c:575:slowly_decrease_freq: set to 235M, delay 3000
2023-01-12 02:06:37 thread.c:575:slowly_decrease_freq: set to 230M, delay 3000
2023-01-12 02:06:40 thread.c:575:slowly_decrease_freq: set to 225M, delay 3000
2023-01-12 02:06:43 thread.c:575:slowly_decrease_freq: set to 220M, delay 3000
2023-01-12 02:06:46 thread.c:575:slowly_decrease_freq: set to 215M, delay 3000
2023-01-12 02:06:49 thread.c:575:slowly_decrease_freq: set to 210M, delay 3000
2023-01-12 02:06:52 thread.c:575:slowly_decrease_freq: set to 205M, delay 3000
2023-01-12 02:06:55 thread.c:575:slowly_decrease_freq: set to 200M, delay 3000
2023-01-12 02:06:58 thread.c:575:slowly_decrease_freq: set to 195M, delay 3000
2023-01-12 02:07:01 thread.c:575:slowly_decrease_freq: set to 190M, delay 3000
2023-01-12 02:07:04 thread.c:575:slowly_decrease_freq: set to 185M, delay 3000
2023-01-12 02:07:07 thread.c:575:slowly_decrease_freq: set to 180M, delay 3000
2023-01-12 02:07:10 thread.c:575:slowly_decrease_freq: set to 175M, delay 3000
2023-01-12 02:07:13 thread.c:575:slowly_decrease_freq: set to 170M, delay 3000
2023-01-12 02:07:16 thread.c:575:slowly_decrease_freq: set to 165M, delay 3000
2023-01-12 02:07:19 thread.c:575:slowly_decrease_freq: set to 160M, delay 3000
|
|
|
|
|
massivegoatdynamic (OP)
Newbie
Offline
Activity: 19
Merit: 0
|
|
January 13, 2023, 05:02:36 AM
Last edit: January 17, 2023, 03:14:48 AM by massivegoatdynamic |
|
This was the kernel log from before i removed hashboard 3. Do you think chip 14 is the likely culprit of what is hurting hasboard 3? We are having cold weather tomorrow, perhaps I will have some luck getting it to hash if temperature is killing it. Aside from my sadness that this expensive paperweight I bought isn't working. Have you ever tried immersion cooling miners with the monolithic heat sink? I am wondering if the thermal paste could muck up the fluid. When I bought this miner it claimed to have upgraded heat sinks but ended up being the old individual type. I am wondering with the monolithic heat sink maybe there is less chance of board failure since there is less solder floating around. 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: 203432K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25944K 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: 12904K (cce67000 - 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: 21/10, WL threshold: 4096, image sequence number: 237714726
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 FF09433B-E002-4C29-97EC-6220DDC4BB36, 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: 4099/1014, WL threshold: 4096, image sequence number: 3265111179
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 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2023-01-10 23:26:26 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2023-01-10 23:26:26 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version = 1
2023-01-10 23:26:26 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab = 1
2023-01-10 23:26:26 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2023-01-10 23:26:26 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun 2 10:31:07 CST 2020 type: Antminer S17+
2023-01-10 23:26:26 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2023-01-10 23:26:26 driver-btm-api.c:2083:show_sn: len:16, 80244d0c2b104814
2023-01-10 23:26:26 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2023-01-10 23:26:26 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2023-01-10 23:26:26 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 80244d0c2b104814
2023-01-10 23:26:26 fan.c:284:front_fan_power_on: Note: front fan is power on!
2023-01-10 23:26:26 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2023-01-10 23:26:26 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2023-01-10 23:26:26 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2023-01-10 23:26:32 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-10 23:26:32 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-10 23:26:36 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2023-01-10 23:26:36 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2023-01-10 23:26:36 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2023-01-10 23:26:36 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2023-01-10 23:26:36 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2023-01-10 23:26:36 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2023-01-10 23:26:36 thread.c:1363:create_read_nonce_reg_thread: create thread
2023-01-10 23:26:42 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-10 23:26:42 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-10 23:26:45 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2023-01-10 23:26:45 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2023-01-10 23:26:45 driver-btm-api.c:792:_set_project_type: project:0
2023-01-10 23:26:45 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2023-01-10 23:26:45 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2023-01-10 23:26:45 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2023-01-10 23:26:45 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2023-01-10 23:26:45 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2023-01-10 23:26:49 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2023-01-10 23:26:50 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2023-01-10 23:26:53 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2023-01-10 23:26:54 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2023-01-10 23:26:56 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2023-01-10 23:26:56 thread.c:1358:create_pic_heart_beat_thread: create thread
2023-01-10 23:26:56 power_api.c:213:power_init: Power init:
2023-01-10 23:26:56 power_api.c:214:power_init: current_voltage_raw = 0
2023-01-10 23:26:56 power_api.c:215:power_init: highest_voltage_raw = 2100
2023-01-10 23:26:56 power_api.c:216:power_init: working_voltage_raw = 1950
2023-01-10 23:26:56 power_api.c:217:power_init: higher_voltage_raw = 2040
2023-01-10 23:26:56 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2023-01-10 23:26:56 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2023-01-10 23:27:28 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2023-01-10 23:27:53 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-10 23:27:55 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.159092
2023-01-10 23:27:56 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.156368
2023-01-10 23:27:56 power_api.c:53:_get_avg_voltage: average_voltage = 21.157730
2023-01-10 23:27:56 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.16, check voltage passed.
2023-01-10 23:27:56 uart.c:72:set_baud: set fpga_baud to 115200
2023-01-10 23:28:07 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2023-01-10 23:28:18 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2023-01-10 23:28:23 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2023-01-10 23:28:23 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2023-01-10 23:28:23 driver-btm-api.c:435:set_order_clock: chain[2]: set order clock, stragegy 3
2023-01-10 23:28:24 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2023-01-10 23:28:24 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2023-01-10 23:28:24 voltage[0] = 1980
2023-01-10 23:28:24 voltage[2] = 1980
2023-01-10 23:28:24 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1980
2023-01-10 23:28:25 temperature.c:340:calibrate_temp_sensor_one_chain: chain 0 temp sensor TMP451
2023-01-10 23:28:26 temperature.c:340:calibrate_temp_sensor_one_chain: chain 2 temp sensor NCT218
2023-01-10 23:28:26 uart.c:72:set_baud: set fpga_baud to 12000000
2023-01-10 23:28:27 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:28:27 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 24
2023-01-10 23:28:27 thread.c:1378:create_check_miner_status_thread: create thread
2023-01-10 23:28:27 thread.c:1368:create_show_miner_status_thread: create thread
2023-01-10 23:28:27 thread.c:1348:create_temperature_monitor_thread: create thread
2023-01-10 23:28:27 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 24 dec_freq_index=0
2023-01-10 23:28:27 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2023-01-10 23:28:27 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2023-01-10 23:28:27 thread.c:1338:create_asic_status_monitor_thread: create thread
2023-01-10 23:28:27 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 550, is_higher_voltage = true
2023-01-10 23:28:28 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:28:30 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:28:32 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:29:20 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2023-01-10 23:29:21 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:29:22 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-10 23:29:23 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.988650
2023-01-10 23:29:23 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:29:24 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.962217
2023-01-10 23:29:24 power_api.c:53:_get_avg_voltage: average_voltage = 20.975434
2023-01-10 23:29:24 power_api.c:71:check_voltage: target_vol = 20.90, actural_vol = 20.98, check voltage passed.
2023-01-10 23:29:25 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:03 driver-btm-api.c:765:set_timeout: freq = 550, percent = 90, hcn = 44236, timeout = 80
2023-01-10 23:34:03 power_api.c:310:set_to_working_voltage_by_steps: Set to voltage raw 1980, step by step.
2023-01-10 23:34:04 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:06 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:08 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:09 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-10 23:34:09 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:10 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 19.910466
2023-01-10 23:34:11 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 19.910466
2023-01-10 23:34:11 power_api.c:53:_get_avg_voltage: average_voltage = 19.910466
2023-01-10 23:34:11 power_api.c:71:check_voltage: target_vol = 19.80, actural_vol = 19.91, check voltage passed.
2023-01-10 23:34:11 thread.c:1373:create_check_system_status_thread: create thread
2023-01-10 23:34:11 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:12 driver-btm-api.c:2618:bitmain_soc_init: Init done!
2023-01-10 23:34:12 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2023-01-10 23:34:13 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:15 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:16 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2023-01-10 23:34:17 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:17 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 46846
2023-01-10 23:34:17 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 46000
2023-01-10 23:34:19 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:21 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:21 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2023-01-10 23:34:21 driver-btm-api.c:1644:dhash_chip_send_job: stime.tv_sec 1673393661, block_ntime 1673393660
2023-01-10 23:34:23 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1 |
|
|
|
|
massivegoatdynamic (OP)
Newbie
Offline
Activity: 19
Merit: 0
|
|
January 16, 2023, 08:19:58 PM |
|
Oh wow, zeusbtc has a new account here but it's weird he is promoting a different link instead of their own guide.
@OP would you mind posting the whole kernel logs here so that we can check exactly what your miner problem is?
If it's not normally running fine try to remove the 3rd hashboard and let it run while the other hash board is connected.
If it's running fine the 3rd hashboard is bad without the whole kernel logs I can't give you a few suggestions so try to post the whole kernel logs here or paste it to pastebin.com and paste the link here.
Any chance you could make sense of the kernel log? I am going to try using a monster fan to cool it while running to see if that helps. Other than that might buy a diagnostic computer from Zeus. |
|
|
|
|
BitMaxz
Legendary
Offline
Activity: 3444
Merit: 3175
Playbet.io - Crypto Casino and Sportsbook
|
|
January 16, 2023, 11:44:43 PM |
|
I hope that you know how to use the insert code tag a sharp # button while editing your post it may look better than pasting the whole logs without it. Anyway, what I see most of your logs are read temp/sensor errors it might be overheating or maybe the 3rd hashboard has a loose heatsink, and actually the miner itself is trying to fix the issue by gradually reducing the frequency. Miner heatsinks sometimes loosen during delivery that's a common issue the only solution for that is to find that loose heatsink and reglue it with thermal glue/adhesive most recommended glue is an artic silver thermal adhesive to reattach the loose heatsink. Another thing that I notice is the fan doesn't have signals Here's mine with an insert code tag do this in your post above it will attract more people to come here and help you. 2023-01-10 23:26:26 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0 Would you mind to try to remove the 3rd hashboard first and let it run and let see if the two fan are running fine because sometimes abnormal fan can give different logs to other hashboard but the only culprit is the fan. So make sure to check if the two fan is working fine. |
|
|
|
massivegoatdynamic (OP)
Newbie
Offline
Activity: 19
Merit: 0
|
|
January 17, 2023, 03:26:16 AM
Last edit: January 17, 2023, 04:00:35 AM by massivegoatdynamic |
|
I did not know that inserting code was a feature, thank you. I did unplug board 3 and 1 and managed to get board 2 to run but it eventually stopped (was only running at 11000 GH/S). I think unplugged board 2 and got board 1 to run for a bit (was running at 23,600 GH/S) but I still get the "socket connect failed: connection refused". It seems random, if I reset on the miner and then hit the IP report occasionally you can connect to the miner but it has always failed the "ping" diagnostic in network. I also hooked up a monster fan and used spoofers on this latest test. The board and chips were running cooler but maybe some chips aren't working. While running one board the highest temp the chip saw was 50°C, max PCB temp was 36°C. Maybe the damage was done the first time I ever turned it on. Before running my monster fan setup my chip temps were up to 77°C. The heat sinks all felt good, nothing was loose. That being said I think on the chip side it uses the mono-lithic type heat sinks that are held in place with screws. Not sure if there is poor contact or not. I can say for a used machine it at least looks like its in pretty good shape. The attached Kernel log was with just board 2 hooked up. 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: 203432K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25944K 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: 12904K (cce67000 - 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: 23/11, WL threshold: 4096, image sequence number: 237714726
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID FF09433B-E002-4C29-97EC-6220DDC4BB36, 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: 4099/1014, WL threshold: 4096, image sequence number: 3265111179
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2023-01-17 02:02:25 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2023-01-17 02:02:25 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version = 1
2023-01-17 02:02:25 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab = 1
2023-01-17 02:02:25 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2023-01-17 02:02:25 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun 2 10:31:07 CST 2020 type: Antminer S17+
2023-01-17 02:02:25 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2023-01-17 02:02:25 driver-btm-api.c:2083:show_sn: len:16, 80244d0c2b104814
2023-01-17 02:02:25 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2023-01-17 02:02:25 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2023-01-17 02:02:25 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 80244d0c2b104814
2023-01-17 02:02:25 fan.c:284:front_fan_power_on: Note: front fan is power on!
2023-01-17 02:02:25 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2023-01-17 02:02:25 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2023-01-17 02:02:25 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2023-01-17 02:02:31 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-17 02:02:31 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-17 02:02:33 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2023-01-17 02:02:33 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2023-01-17 02:02:33 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2023-01-17 02:02:33 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2023-01-17 02:02:33 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2023-01-17 02:02:33 thread.c:1363:create_read_nonce_reg_thread: create thread
2023-01-17 02:02:39 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-17 02:02:39 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-17 02:02:41 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2023-01-17 02:02:41 driver-btm-api.c:792:_set_project_type: project:0
2023-01-17 02:02:41 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2023-01-17 02:02:41 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2023-01-17 02:02:41 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2023-01-17 02:02:45 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2023-01-17 02:02:46 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2023-01-17 02:02:48 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2023-01-17 02:02:48 thread.c:1358:create_pic_heart_beat_thread: create thread
2023-01-17 02:02:48 power_api.c:213:power_init: Power init:
2023-01-17 02:02:48 power_api.c:214:power_init: current_voltage_raw = 0
2023-01-17 02:02:48 power_api.c:215:power_init: highest_voltage_raw = 2100
2023-01-17 02:02:48 power_api.c:216:power_init: working_voltage_raw = 1950
2023-01-17 02:02:48 power_api.c:217:power_init: higher_voltage_raw = 2040
2023-01-17 02:02:48 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2023-01-17 02:02:48 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish. |
|
|
|
|
mikeywith
Legendary
Offline
Activity: 2422
Merit: 6626
be constructive or S.T.F.U
|
|
January 17, 2023, 07:57:51 PM |
|
Oh wow, zeusbtc has a new account here but it's weird he is promoting a different link instead of their own guide.
What guide? nobody wrote a better guide on the 17 series temp sensor than mine  , jokes aside, I just noticed they used my guide in their post, and to be honest most of the knowledge I acquired regarding the 17 series when dozen of issues were coming my way when I bought those piece of shit gears actually came from ZeusBTC, they were probably the only reliable source of information, I "mined" the info they had online, got in direct touch with the founder whom I had a good relationship with, they never failed to provide me with the info I needed, add to that my awful experience with those gears which made me eager to learn about them, so ya I might have summed up the issue better, but ZeusBTC still remains the source of the most of that knowledge (gotta give credit where credit is due). |
|
|
|
massivegoatdynamic (OP)
Newbie
Offline
Activity: 19
Merit: 0
|
|
January 18, 2023, 01:58:20 AM |
|
Oh wow, zeusbtc has a new account here but it's weird he is promoting a different link instead of their own guide.
What guide? nobody wrote a better guide on the 17 series temp sensor than mine , jokes aside, I just noticed they used my guide in their post, and to be honest most of the knowledge I acquired regarding the 17 series when dozen of issues were coming my way when I bought those piece of shit gears actually came from ZeusBTC, they were probably the only reliable source of information, I "mined" the info they had online, got in direct touch with the founder whom I had a good relationship with, they never failed to provide me with the info I needed, add to that my awful experience with those gears which made me eager to learn about them, so ya I might have summed up the issue better, but ZeusBTC still remains the source of the most of that knowledge (gotta give credit where credit is due). MikeyWith, could you point me to your "guide" on the matter? I am guessing I either need to pick up one of these testers: https://www.zeusbtc.com/ASIC-Miner-Repair/Parts-Tools-Details.asp?ID=1467Or https://tester.asic.repair/enDid you have a chance to look at my logs to see if it was something obvious? Also, since I have a monolithic heatsink on the S17 are those best removed by putting the entire thing in an oven and if so what temp? All of the videos I have seen so far deal with individual heat sinks. On my most recent test I got rid of the stock fans and used a monster fan to push air through so that it will run cooler. Mission accomplished on that front however the miner still wasn't working. I never been able to connect to my mining pool, always fail the ping diagnostic test and get the "socked failed to connect" message. |
|
|
|
|
mikeywith
Legendary
Offline
Activity: 2422
Merit: 6626
be constructive or S.T.F.U
|
|
January 18, 2023, 04:22:31 AM
Last edit: January 18, 2023, 12:20:50 PM by mikeywith |
|
You do have an issue with temp sensor but has nothing to do with ping/diagnostics , send me your telegram id in PM, let us arrange for anydesk session so I can help troubleshoot this faster if you want. (For free of course).
Not being able to ping suggests a network-related issue, probably something wrong with the DNS settings, or maybe your firewall, could be one of a few things, there are a few things that I can trouble shoot in 15 mins if I have access to the miner, whereby I'll need double or triple the time explaining it and then probably even more time on your side to perform them, so if anydesk is not an option, please just start by checking your DNS.
|
|
|
|
BitMaxz
Legendary
Offline
Activity: 3444
Merit: 3175
Playbet.io - Crypto Casino and Sportsbook
|
|
January 19, 2023, 11:59:50 PM |
|
What guide? nobody wrote a better guide on the 17 series temp sensor than mine , jokes aside, I just noticed they used my guide in their post, and to be honest most of the knowledge I acquired regarding the 17 series when dozen of issues were coming my way when I bought those piece of shit gears actually came from ZeusBTC, they were probably the only reliable source of information, I "mined" the info they had online, got in direct touch with the founder whom I had a good relationship with, they never failed to provide me with the info I needed, add to that my awful experience with those gears which made me eager to learn about them, so ya I might have summed up the issue better, but ZeusBTC still remains the source of the most of that knowledge (gotta give credit where credit is due). I'm thinking about this account ZeusBtc.com registered this month they can make a guide and point people to their own guide but this one is not. What I think is that he might be pretending as Zeusbtc and grow up using that name without real Zeusbtc knowing that someone uses their name here on the forum. Like last year someone pretending to be Electrum support but the real purpose they use that name to scam people. |
|
|
|
massivegoatdynamic (OP)
Newbie
Offline
Activity: 19
Merit: 0
|
|
January 20, 2023, 01:59:48 AM |
|
Mikey I think you are right. I finally managed to connect to a mining pool and am finally earning negative money but it is neat to say I have mined. My miner's has rate dropped off and when i went to go check the miner it had disconnected and was reporting chip temps on 127°C even though I am pumping a ton of air through it and previously the chips were setting at 55°C.
I looked at your earlier post referenced by zeus and it seems I have to do the same thing (Step 1. Reboot miner, Step 2. In my case hit the IPS report, Step 3. Un-plug and plug in the network cable) and it seems to come back to life. I am guessing when the miner senses high temps it is trying to save it self by shutting down.
The good and bad is that the side that the chips are mounted on are covered with a monolithic heat sink so I have to remove that to test the chips. I had gently tried to do it after removing the screws and I am guessing they used the thermal glue? Any idea how to remove the heat sink to get to the chips?
Do you know if the thermal paste/glue is typically non-electrically conductive? I have dreams of eventually trying to immersion cool these things and I am wondering if the dielectric would dissolve the paste/glue and then you would have bits of conductive stuff floating in the fluid.
I may consider taking you up with telegram (which I don't have yet) and anydesk. I am scared of stranger danger though...
|
|
|
|
|
massivegoatdynamic (OP)
Newbie
Offline
Activity: 19
Merit: 0
|
|
January 20, 2023, 02:46:29 AM |
|
After messing around with it, all chips and all PCB's are registering super high temps even though its pretty chilly at the moment. Looking at some earlier posts if all boards and chips are registering high temps that means the power supply has crapped out?
|
|
|
|
|
BitMaxz
Legendary
Offline
Activity: 3444
Merit: 3175
Playbet.io - Crypto Casino and Sportsbook
|
|
January 20, 2023, 12:32:26 PM
Last edit: January 20, 2023, 12:42:54 PM by BitMaxz |
|
After messing around with it, all chips and all PCB's are registering super high temps even though its pretty chilly at the moment. Looking at some earlier posts if all boards and chips are registering high temps that means the power supply has crapped out?
No usually high chip temps sometimes it is due to loose heatsinks or no proper ventilation. Do you mind telling us what exactly your room temp is? You can try to run the miner with low power mode let's see if it can help to drop the chip temps. There is other thing that I would like you to try there and maybe this unit also has hidden settings where you can able to adjust frequency and voltages. Check the Mikeywith guide here https://bitcointalk.org/index.php?topic=5247179.0And then set the voltage/frequency to the lowest and gradually increase it depending on the chip temps until you find the right spot. |
|
|
|
mikeywith
Legendary
Offline
Activity: 2422
Merit: 6626
be constructive or S.T.F.U
|
|
January 20, 2023, 01:49:37 PM |
|
I may consider taking you up with telegram (which I don't have yet) and anydesk. I am scared of stranger danger though...
The fact that you got to connect to the pool even for a while eliminates the network related issues, which means you no longer need my help in network diagnoisis, your issue is now hardware related and I am not the best person for that. One thing I know is that if all temp sensors are acting weird it usually means a bad PSU, so you might need to replace the PSU, if it turns out to be actually sensor issues, it will require a pro to fix it, not something the average person can do, there is a pinned thread in this sections that is dedicated to repair services which you can check. Although with all honesty, that gear is worth less than 300$ fully working with no issues, fixing it will cost probably 100-200$, with shipping and all that you may go past the 300$. |
|
|
|
massivegoatdynamic (OP)
Newbie
Offline
Activity: 19
Merit: 0
|
|
January 20, 2023, 06:46:52 PM |
|
@ BitMaxz
Room temp was 55 (this is out in the barn for now) and I have the miner hooked up to a 10" ducted fan that can move a lot of air. I would post a picture of the setup but I don't know how. Do you have to post pictures to another site and then link it here?
I looked into to the post of mikeywith but I did not see that on mine. I have an S17+ if that makes a difference. I am guessing you went to "more tools" and "developer tools" to get that to pop up? Currently I only have the normal and sleep mode available.
Side note, when I turn on the miner I got a voltage of 20 volts across the buss bars going to the hashboards. I let it run and it connected again today but you see the hashrate slowly dropping off. Once I saw the 127 C chip temp I went back to measure the voltage and it was reading 0 volts.
So at least when you first turn on the power supply it appears to be working, but could the voltage dropping off be from the miner telling it to dial back the frequency/Voltage?
@ Mikeywith
Agreed that it is almost not worth it to fix at current prices. I got this miner to learn the ropes and see what you can do with them. Seems like a bought a lemon or just a really finicky miner. I eventually would like to have several miners and was hoping to get into immersion cooling them and trying to power them with solar. I was planning on messing with overclocking but now it seems you may want to baby these things to make them last longer.
|
|
|
|
|
mikeywith
Legendary
Offline
Activity: 2422
Merit: 6626
be constructive or S.T.F.U
|
|
January 20, 2023, 08:14:59 PM |
|
The 17 series is the worst thing made by mankind, there is nothing much you can do to make them survive longer, the main issue is in the solder quality between the chips and the board itself, running them cooler delays the issues from happening and that is it.
|
|
|
|
massivegoatdynamic (OP)
Newbie
Offline
Activity: 19
Merit: 0
|
|
January 20, 2023, 08:21:09 PM |
|
@ Mikeywith
This one is different in that each board has the monolithic heat sink. Each board only has chips on one side right?
I would think that the solder issue should be less since the chip side has a different heat sink. The backside still has the old style. I would post a picture of my boards but don't know how.
|
|
|
|
|
|
