Bitcoin Forum
May 22, 2024, 03:56:34 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: S17+ Low hashrate / No hashrate  (Read 121 times)
TommySkog (OP)
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
March 11, 2021, 12:39:14 PM
 #1

Hello all. I recieved my used antminer S17+ yesterday, and after fiddling around with settings, trying all sorts of resets and reboots, and could not get it to hash more than around 40 TH/S average. It would sometimes spike up to 70-75, then drop down again after a little bit. It doesnt show anything wrong with the hashboards or asics at all, it kinda seems firmware-limited, in a way..

As a last resort, i downloaded the newest firmware from the bitmain site, and tried flashing it with it, via the web interface. And now it won't hash at all. I've tried both the normal SHA256 and the asicboost stratum, but to no luck.. Does anybody here have a clue?

Including the kernel log:

Code:

Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
  Normal zone: 480 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 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: 9/4, WL threshold: 4096, image sequence number: 2978436426
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 987A1571-FBC2-4732-A459-E9DD9DBA9F6F, 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: 540/266, WL threshold: 4096, image sequence number: 530904360
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 3E9C38B1-5AEA-4FD6-850C-698DB389147B, 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
2021-03-11 12:22:43 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2021-03-11 12:22:43 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version     = 1
2021-03-11 12:22:43 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab        = 1
2021-03-11 12:22:43 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2021-03-11 12:22:43 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun  2 10:31:07 CST 2020 type: Antminer S17+
2021-03-11 12:22:43 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
2021-03-11 12:22:43 driver-btm-api.c:2083:show_sn: len:16, 816425064e10481c
2021-03-11 12:22:43 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2021-03-11 12:22:43 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2021-03-11 12:22:43 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 816425064e10481c
2021-03-11 12:22:43 fan.c:284:front_fan_power_on: Note: front fan is power on!
2021-03-11 12:22:43 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2021-03-11 12:22:43 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2021-03-11 12:22:43 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2021-03-11 12:22:49 driver-btm-api.c:1239:init_miner_version: miner ID : 816425064e10481c
2021-03-11 12:22:49 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2021-03-11 12:22:55 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2021-03-11 12:22:55 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2021-03-11 12:22:55 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2021-03-11 12:22:55 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2021-03-11 12:22:55 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2021-03-11 12:22:55 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2021-03-11 12:22:55 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2021-03-11 12:22:55 thread.c:1363:create_read_nonce_reg_thread: create thread
2021-03-11 12:23:01 driver-btm-api.c:1239:init_miner_version: miner ID : 816425064e10481c
2021-03-11 12:23:01 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2021-03-11 12:23:06 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2021-03-11 12:23:06 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2021-03-11 12:23:06 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2021-03-11 12:23:06 driver-btm-api.c:792:_set_project_type: project:0
2021-03-11 12:23:06 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2021-03-11 12:23:06 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2021-03-11 12:23:06 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2021-03-11 12:23:06 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2021-03-11 12:23:06 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2021-03-11 12:23:06 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2021-03-11 12:23:06 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2021-03-11 12:23:08 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2021-03-11 12:23:09 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-03-11 12:23:11 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2021-03-11 12:23:12 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-03-11 12:23:14 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2021-03-11 12:23:16 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-03-11 12:23:18 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2021-03-11 12:23:18 thread.c:1358:create_pic_heart_beat_thread: create thread
2021-03-11 12:23:18 power_api.c:213:power_init: Power init:
2021-03-11 12:23:18 power_api.c:214:power_init: current_voltage_raw = 0
2021-03-11 12:23:18 power_api.c:215:power_init: highest_voltage_raw = 2100
2021-03-11 12:23:18 power_api.c:216:power_init: working_voltage_raw = 1950
2021-03-11 12:23:18 power_api.c:217:power_init: higher_voltage_raw  = 2040
2021-03-11 12:23:18 power_api.c:218:power_init: check_asic_voltage_raw  = 2100
2021-03-11 12:23:18 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-03-11 12:23:18 power_api.c:186:power_off: init gpio907
2021-03-11 12:23:50 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2021-03-11 12:24:15 power_api.c:85:check_voltage_multi: retry time: 0
2021-03-11 12:24:16 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.097560
2021-03-11 12:24:18 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.192308
2021-03-11 12:24:19 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.102960
2021-03-11 12:24:19 power_api.c:53:_get_avg_voltage: average_voltage = 21.130943
2021-03-11 12:24:19 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.13, check voltage passed.
2021-03-11 12:24:19 uart.c:72:set_baud: set fpga_baud to 115200
2021-03-11 12:24:30 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2021-03-11 12:24:41 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2021-03-11 12:24:52 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2021-03-11 12:25:00 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2021-03-11 12:25:00 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2021-03-11 12:25:00 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2021-03-11 12:25:01 driver-btm-api.c:435:set_order_clock: chain[2]: set order clock, stragegy 3
2021-03-11 12:25:01 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2021-03-11 12:25:01 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2021-03-11 12:25:02 voltage[0] = 1940
2021-03-11 12:25:02 voltage[1] = 1940
2021-03-11 12:25:02 voltage[2] = 1940
2021-03-11 12:25:02 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1940
2021-03-11 12:25:03 temperature.c:340:calibrate_temp_sensor_one_chain: chain 0 temp sensor NCT218
2021-03-11 12:25:04 temperature.c:340:calibrate_temp_sensor_one_chain: chain 1 temp sensor NCT218
2021-03-11 12:25:05 temperature.c:340:calibrate_temp_sensor_one_chain: chain 2 temp sensor NCT218
2021-03-11 12:25:05 uart.c:72:set_baud: set fpga_baud to 12000000
2021-03-11 12:25:06 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 21
2021-03-11 12:25:06 thread.c:1378:create_check_miner_status_thread: create thread
2021-03-11 12:25:06 thread.c:1368:create_show_miner_status_thread: create thread
2021-03-11 12:25:06 thread.c:1348:create_temperature_monitor_thread: create thread
2021-03-11 12:25:06 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 21 dec_freq_index=0
2021-03-11 12:25:06 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2021-03-11 12:25:06 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2021-03-11 12:25:06 thread.c:1338:create_asic_status_monitor_thread: create thread
2021-03-11 12:25:06 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 570, is_higher_voltage = true
2021-03-11 12:26:38 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2021-03-11 12:26:40 power_api.c:85:check_voltage_multi: retry time: 0
2021-03-11 12:26:41 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.875641
2021-03-11 12:26:42 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.994877
2021-03-11 12:26:43 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.904885
2021-03-11 12:26:43 power_api.c:53:_get_avg_voltage: average_voltage = 20.925134
2021-03-11 12:26:43 power_api.c:71:check_voltage: target_vol = 20.90, actural_vol = 20.93, check voltage passed.
2021-03-11 12:28:54 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2080, step by step.
2021-03-11 12:28:56 power_api.c:85:check_voltage_multi: retry time: 0
2021-03-11 12:28:57 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.753846
2021-03-11 12:28:58 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.848911
2021-03-11 12:28:59 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.758355
2021-03-11 12:28:59 power_api.c:53:_get_avg_voltage: average_voltage = 20.787037
2021-03-11 12:28:59 power_api.c:71:check_voltage: target_vol = 20.80, actural_vol = 20.79, check voltage passed.
2021-03-11 12:31:23 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2020, step by step.
2021-03-11 12:31:27 power_api.c:85:check_voltage_multi: retry time: 0
2021-03-11 12:31:28 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.120513
2021-03-11 12:31:29 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.265044
2021-03-11 12:31:30 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.172237
2021-03-11 12:31:30 power_api.c:53:_get_avg_voltage: average_voltage = 20.185931
2021-03-11 12:31:30 power_api.c:71:check_voltage: target_vol = 20.20, actural_vol = 20.19, check voltage passed.
2021-03-11 12:31:30 frequency.c:1181:inc_asic_diff_freq_by_steps: chain = 0, start = 570, freq_step = 5
2021-03-11 12:31:37 frequency.c:1181:inc_asic_diff_freq_by_steps: chain = 1, start = 570, freq_step = 5
2021-03-11 12:31:44 frequency.c:1181:inc_asic_diff_freq_by_steps: chain = 2, start = 570, freq_step = 5
2021-03-11 12:31:51 driver-btm-api.c:765:set_timeout: freq = 620, percent = 90, hcn = 44236, timeout = 71
2021-03-11 12:31:51 power_api.c:310:set_to_working_voltage_by_steps: Set to voltage raw 1940, step by step.
2021-03-11 12:31:54 power_api.c:85:check_voltage_multi: retry time: 0
2021-03-11 12:31:55 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 19.365385
2021-03-11 12:31:56 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 19.462227
2021-03-11 12:31:58 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 19.341903
2021-03-11 12:31:58 power_api.c:53:_get_avg_voltage: average_voltage = 19.389838
2021-03-11 12:31:58 power_api.c:71:check_voltage: target_vol = 19.40, actural_vol = 19.39, check voltage passed.
2021-03-11 12:31:58 thread.c:1373:create_check_system_status_thread: create thread
2021-03-11 12:31:58 driver-btm-api.c:2618:bitmain_soc_init: Init done!
2021-03-11 12:31:58 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2021-03-11 12:32:02 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2021-03-11 12:32:03 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 76911
2021-03-11 12:32:03 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 76000
2021-03-11 12:32:08 driver-btm-api.c:1496:dhash_chip_send_job: Version num 1.
wndsnb
Hero Member
*****
Offline Offline

Activity: 544
Merit: 589


View Profile
March 11, 2021, 12:59:57 PM
 #2

I don't see anything wrong in the log.

Does the log show any more messages after the hashrate drops?

When the hashrate drops, what does the miner status page look like?

Have you tried different pools?

You could also try flashing with an SD card to make sure you are getting a clean install.

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

Activity: 4
Merit: 0


View Profile
March 11, 2021, 01:15:20 PM
Last edit: March 11, 2021, 11:42:26 PM by frodocooper
 #3

Unfortunately, i did not save the log when the rate was just dropping. Now it just wont hash at all, even after resets and restarts. Guess i have to try with and sd card yeah.

I have not tried changing pools (i use nicehash), only switched between SHA256 and SHA256asicboost.

The status page now, says diff 50k, getworks 37, then everything is 0 until discarded, which says 448. I will upload some photos when i get back to my pc.

The machine was tested before it was shipped here, and everything looked good.



Update: after numerous restarts and resets, my machine started hashing properly. Still not sure what the problem was but atleast it works now.
wndsnb
Hero Member
*****
Offline Offline

Activity: 544
Merit: 589


View Profile
March 11, 2021, 06:30:36 PM
Merited by mikeywith (1)
 #4

I have not tried changing pools (i use nicehash), only switched between SHA256 and SHA256asicboost.

Lots of people have issues with Nicehash, try a pool like kano, viabtc, f2pool, etc... first before trying anything else.

also, with nicehash you should add #xnsub to the end of the pool URL if you haven't already.

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

Activity: 4
Merit: 0


View Profile
March 11, 2021, 09:37:41 PM
 #5

Well, it works now so i guess its okay... I’ll let it run for a day or two, and test another one and check my rewards in comparison.

Thank you, didnt know about the xnsub-thingie.
BitMaxz
Legendary
*
Offline Offline

Activity: 3262
Merit: 2974


Block halving is coming.


View Profile WWW
March 11, 2021, 10:02:24 PM
Merited by mikeywith (1)
 #6

I think the reason why you can't mine recently or drop in hashrate is due to their system maintenance a day ago that's why you experienced some drop in hashrate.

Next time always check their status page here https://status.nicehash.com/

If you just follow the first post of wndsnb by changing the pool maybe you solve this early.

█▀▀▀











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











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

Activity: 2240
Merit: 6405


be constructive or S.T.F.U


View Profile
March 11, 2021, 10:39:00 PM
 #7

Well, it works now so i guess its okay... I’ll let it run for a day or two, and test another one and check my rewards in comparison.

It works now but it will eventually fail as long as it's mining on Nicehash you should expect to face all kind of issues ahead, including but not limited to your funds being "hacked",  and you don't really make any extra mining on Nicehash, in fact, the last 7 days Nicehash made 3% less profit in BTC against mining directly to a PPS pool, the on-going difficulty changing and all the mess they create will go to as far as bricking your gear and many of us here have personal experience with such issues.

The only time I would consider nicehash is if there is a massive temporary pump on the rates there, and that will be for a quick run and I'd leave, but mining 24/7 on Nicehash is a terrible idea regardless of how you look it at.

█▀▀▀











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











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
TommySkog (OP)
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
March 12, 2021, 12:21:42 PM
 #8

Okay, thanks for all support guys. Im considering switching to slushpool, as i will try the braains os on my machine. On the topic of pools, anything you recommend?
Pages: [1]
  Print  
 
Jump to:  

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