Bitmain introduces the Antminer S17 Pro, Antminer S17, and the Antminer T17

[Steamtyme]

Nope standard S17 56th unit, it appears bitmains auto-tune function is broken because my my first 2 hashboards are avg 18000gh each and board #3 is averaging 12000gh and I only have Normal and Low Power, no turbo.

Those sound like problems that might be solved with reflashing the FW, eait until you hear from Bitmain. That's assuming it's not in fact the board itself, have you checked the logs for anything that stands out? Has anyone looked to see if the units all arrived with the same FW? This is probably going to be step one for Bitmains troubleshooting; here's to hoping it's not a physical problem save some shipping and down time.

[1714117692]

1714117692

[1714117692]

1714117692

[jhartbarger]

After further testing the 3rd hashboard that was reporting 12,000GH finally dropped offline, the first 2 hashboards clock at 575mhz and 600mhz and the 3rd that was showing 615mhz. Now after multiple reboots and factory defaults sometimes it detects 22, 38, or 41 chips.

I am hopings its just a goofed up flash but I am doubting it at this point. Did anyone else notice on theirs that there were NO pools configured by default which I find odd since this is the first I have ever seen that had no default pools configured.

Below is a copy of the kernel log.....

Code:

22:06:18 driver-btm-soc.c:3160:init_freq_mode: This is scan-user version
22:06:18 driver-btm-soc.c:3896:bitmain_soc_init: opt_multi_version=1
22:06:18 driver-btm-soc.c:3897:bitmain_soc_init: opt_bitmain_ab=1
22:06:18 driver-btm-soc.c:3898:bitmain_soc_init: opt_bitmain_work_mode=2
22:06:18 driver-btm-soc.c:3521:_show_sn: no SN got, please write SN to /nvdata/sn
22:06:18 driver-btm-soc.c:3191:init_phy_mem_nonce2_jobid_address: Detect 256MB control board of XILINX
22:06:18 driver-btm-soc.c:3904:bitmain_soc_init: Miner compile time: Tue Apr 16 19:03:06 CST 2019
22:06:18 driver-btm-soc.c:3906:bitmain_soc_init: last commit version: 8b856e7 commit time: 2019-04-16 16:36:14 build: 2019-04-16 19:07:51
22:06:18 driver-btm-soc.c:3223:check_fan_multi: check fan for 20 times...
22:06:20 driver-btm-soc.c:3299:init_miner_version: miner ID : 81280c2e57408854
22:06:20 driver-btm-soc.c:3305:init_miner_version: FPGA Version = 0xB011
22:06:20 driver-btm-soc.c:404:check_chain: !! chain[0]is exist
22:06:20 driver-btm-soc.c:404:check_chain: !! chain[1]is exist
22:06:20 driver-btm-soc.c:404:check_chain: !! chain[2]is exist
22:06:24 driver-btm-soc.c:3722:get_product_id: product_id[0] = 0
22:06:24 driver-btm-soc.c:3722:get_product_id: product_id[1] = 0
22:06:24 driver-btm-soc.c:3722:get_product_id: product_id[2] = 0
22:06:24 driver-btm-soc.c:3823:bitmain_board_init: g_product_id = 0
22:06:24 driver-btm-soc.c:3574:_set_project_type: Project type: Antminer S17
22:06:24 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
22:06:24 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
22:06:24 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
22:06:24 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
22:06:24 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
22:06:24 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
22:06:25 pic.c:619:pic_reset: chain[0] ok
22:06:29 pic.c:898:jump_to_app_from_loader: chain[0] ok
22:06:30 pic.c:619:pic_reset: chain[1] ok
22:06:34 pic.c:898:jump_to_app_from_loader: chain[1] ok
22:06:35 pic.c:619:pic_reset: chain[2] ok
22:06:39 pic.c:898:jump_to_app_from_loader: chain[2] ok
22:06:39 driver-btm-soc.c:3840:bitmain_board_init: Enter 30s sleep to make sure power release finish.
22:06:39 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 2
22:06:39 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 1
22:06:39 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 0
22:07:09 power.c:216:power_init: power init ... 
22:07:11 power.c:348:power_get_firmware_version: power firmware version is 00 06
22:07:13 power.c:338:power_get_device_no: power device no is 00 41
22:07:13 power.c:203:power_check_protocol_type: power protocol 00, using package cmd
22:07:13 power.c:204:power_check_protocol_type: power type APW9 3600W
22:07:13 power.c:155:power_on: init gpio907
22:07:14 power.c:624:set_iic_power_to_highest_voltage: setting to voltage: 21.00 ...
22:07:16 power.c:573:set_iic_power_by_voltage: now setting voltage to : 21.000000 
22:07:16 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000ffff
22:07:20 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
22:07:22 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
22:07:25 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
22:07:25 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
22:07:29 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
22:07:31 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
22:07:34 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
22:07:34 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
22:07:38 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
22:07:40 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
22:07:44 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 22 asic, times 0
22:07:44 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
22:07:48 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
22:07:50 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
22:07:54 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 22 asic, times 1
22:07:54 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
22:07:58 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
22:08:00 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
22:08:04 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 22 asic, times 2
22:08:04 driver-btm-soc.c:3682:check_asic_number: Chain 2 only find 22 asic, will power off hash board 2
22:08:05 pic.c:234:hashboard_power_cntl: [0] ok, i2c=2!
22:08:05 chip139x.c:736:set_order_clock: chain[0]: set order clock, stragegy 3
22:08:05 chip139x.c:736:set_order_clock: chain[1]: set order clock, stragegy 3
22:08:11 chip139x.c:318:set_baud_one_chain: chain[0]: chip baud = 6000000, chip_divider = 7
22:08:11 chip139x.c:318:set_baud_one_chain: chain[1]: chip baud = 6000000, chip_divider = 7
22:08:11 chip139x.c:275:set_baud_fpga: set fpga_baud = 6000000, fpga_divider = 3
22:08:11 chip139x.c:837:set_core_clock_delay_control: pwth_sel = 3, ccdly_sel = 0
22:08:11 chip139x.c:852:set_core_clock_delay_control: set CLOCK_DELAY_CTRL to 0x34
voltage[0] = 1840
voltage[1] = 1840
22:08:11 power.c:233:set_working_voltage: working_voltage = 18.400000
sensor type = 1,sensor num = 4
sensor pos: 12  9  37  40  0  0  0  0 

[Steamtyme]

You should merge your posts and use the "Code" function to post your logs. It looks like this #
Keeps the thread readable. Also can you merge your posts together instead of multiple posts in a row.

Code:

22:06:18 driver-btm-soc.c:3160:init_freq_mode: This is scan-user version
22:06:18 driver-btm-soc.c:3896:bitmain_soc_init: opt_multi_version=1
22:06:18 driver-btm-soc.c:3897:bitmain_soc_init: opt_bitmain_ab=1
22:06:18 driver-btm-soc.c:3898:bitmain_soc_init: opt_bitmain_work_mode=2
22:06:18 driver-btm-soc.c:3521:_show_sn: no SN got, please write SN to /nvdata/sn
22:06:18 driver-btm-soc.c:3191:init_phy_mem_nonce2_jobid_address: Detect 256MB control board of XILINX
22:06:18 driver-btm-soc.c:3904:bitmain_soc_init: Miner compile time: Tue Apr 16 19:03:06 CST 2019
22:06:18 driver-btm-soc.c:3906:bitmain_soc_init: last commit version: 8b856e7 commit time: 2019-04-16 16:36:14 build: 2019-04-16 19:07:51
22:06:18 driver-btm-soc.c:3223:check_fan_multi: check fan for 20 times...
22:06:20 driver-btm-soc.c:3299:init_miner_version: miner ID : 81280c2e57408854
22:06:20 driver-btm-soc.c:3305:init_miner_version: FPGA Version = 0xB011
22:06:20 driver-btm-soc.c:404:check_chain: !! chain[0]is exist
22:06:20 driver-btm-soc.c:404:check_chain: !! chain[1]is exist
22:06:20 driver-btm-soc.c:404:check_chain: !! chain[2]is exist
22:06:24 driver-btm-soc.c:3722:get_product_id: product_id[0] = 0
22:06:24 driver-btm-soc.c:3722:get_product_id: product_id[1] = 0
22:06:24 driver-btm-soc.c:3722:get_product_id: product_id[2] = 0
22:06:24 driver-btm-soc.c:3823:bitmain_board_init: g_product_id = 0
22:06:24 driver-btm-soc.c:3574:_set_project_type: Project type: Antminer S17
22:06:24 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
22:06:24 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
22:06:24 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
22:06:24 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
22:06:24 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
22:06:24 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
22:06:25 pic.c:619:pic_reset: chain[0] ok
22:06:29 pic.c:898:jump_to_app_from_loader: chain[0] ok
22:06:30 pic.c:619:pic_reset: chain[1] ok
22:06:34 pic.c:898:jump_to_app_from_loader: chain[1] ok
22:06:35 pic.c:619:pic_reset: chain[2] ok
22:06:39 pic.c:898:jump_to_app_from_loader: chain[2] ok
22:06:39 driver-btm-soc.c:3840:bitmain_board_init: Enter 30s sleep to make sure power release finish.
22:06:39 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 2
22:06:39 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 1
22:06:39 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 0
22:07:09 power.c:216:power_init: power init ... 
22:07:11 power.c:348:power_get_firmware_version: power firmware version is 00 06
22:07:13 power.c:338:power_get_device_no: power device no is 00 41
22:07:13 power.c:203:power_check_protocol_type: power protocol 00, using package cmd
22:07:13 power.c:204:power_check_protocol_type: power type APW9 3600W
22:07:13 power.c:155:power_on: init gpio907
22:07:14 power.c:624:set_iic_power_to_highest_voltage: setting to voltage: 21.00 ...
22:07:16 power.c:573:set_iic_power_by_voltage: now setting voltage to : 21.000000 
22:07:16 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000ffff
22:07:20 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
22:07:22 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
22:07:25 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
22:07:25 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
22:07:29 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
22:07:31 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
22:07:34 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
22:07:34 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
22:07:38 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
22:07:40 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
22:07:44 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 22 asic, times 0
22:07:44 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
22:07:48 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
22:07:50 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
22:07:54 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 22 asic, times 1
22:07:54 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
22:07:58 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
22:08:00 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
22:08:04 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 22 asic, times 2
22:08:04 driver-btm-soc.c:3682:check_asic_number: Chain 2 only find 22 asic, will power off hash board 2
22:08:05 pic.c:234:hashboard_power_cntl: [0] ok, i2c=2!
22:08:05 chip139x.c:736:set_order_clock: chain[0]: set order clock, stragegy 3
22:08:05 chip139x.c:736:set_order_clock: chain[1]: set order clock, stragegy 3
22:08:11 chip139x.c:318:set_baud_one_chain: chain[0]: chip baud = 6000000, chip_divider = 7
22:08:11 chip139x.c:318:set_baud_one_chain: chain[1]: chip baud = 6000000, chip_divider = 7
22:08:11 chip139x.c:275:set_baud_fpga: set fpga_baud = 6000000, fpga_divider = 3
22:08:11 chip139x.c:837:set_core_clock_delay_control: pwth_sel = 3, ccdly_sel = 0
22:08:11 chip139x.c:852:set_core_clock_delay_control: set CLOCK_DELAY_CTRL to 0x34
voltage[0] = 1840
voltage[1] = 1840
22:08:11 power.c:233:set_working_voltage: working_voltage = 18.400000
sensor type = 1,sensor num = 4
sensor pos: 12  9  37  40  0  0  0  0

Edit: I'm not very familiar with troubleshooting antminers but i've never heard of one showing up not pointed to their pool by default.

[mgoz]

Did anyone else notice on theirs that there were NO pools configured by default

My S17 Pro 53TH/s had default Antminer pools. All the boards also report the same frequency and turbo is 595.

[jhartbarger]

My S17 Pro 53TH/s had default Antminer pools. All the boards also report the same frequency and turbo is 595.

Very Interesting...... If I do a factory default on the unit here is what my kernel log shows and all 3 boards in my unit clock differently in both Normal or Low Power modes. Maybee I get lucky and its just a goofed factory flash but I cant even try and reload it because it hasn't been posted.

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: 190356K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 39020K 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: 25980K (cc1a1000 - cdb00000)
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: 5/2, WL threshold: 4096, image sequence number: 306349061
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 038216C1-D266-46DA-A76E-C04B142933A3, 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: 7/4, WL threshold: 4096, image sequence number: 1751317449
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 51C7124B-A562-4AA0-948B-184BE8DB9030, 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 = 0xab011
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
 [2019-05-01 22:46:11.705] httpListenThread start ret=0
2019-05-01 22:46:11 driver-btm-soc.c:3160:init_freq_mode: This is scan-user version
2019-05-01 22:46:11 driver-btm-soc.c:3896:bitmain_soc_init: opt_multi_version=1
2019-05-01 22:46:11 driver-btm-soc.c:3897:bitmain_soc_init: opt_bitmain_ab=1
2019-05-01 22:46:11 driver-btm-soc.c:3898:bitmain_soc_init: opt_bitmain_work_mode=2
2019-05-01 22:46:11 driver-btm-soc.c:3521:_show_sn: no SN got, please write SN to /nvdata/sn
2019-05-01 22:46:11 driver-btm-soc.c:3191:init_phy_mem_nonce2_jobid_address: Detect 256MB control board of XILINX
2019-05-01 22:46:11 driver-btm-soc.c:3904:bitmain_soc_init: Miner compile time: Tue Apr 16 19:03:06 CST 2019
2019-05-01 22:46:11 driver-btm-soc.c:3906:bitmain_soc_init: last commit version: 8b856e7 commit time: 2019-04-16 16:36:14 build: 2019-04-16 19:07:51
2019-05-01 22:46:11 driver-btm-soc.c:3223:check_fan_multi: check fan for 20 times...
2019-05-01 22:46:13 driver-btm-soc.c:3299:init_miner_version: miner ID : 81280c2e57408854
2019-05-01 22:46:13 driver-btm-soc.c:3305:init_miner_version: FPGA Version = 0xB011
2019-05-01 22:46:13 driver-btm-soc.c:404:check_chain: !! chain[0]is exist
2019-05-01 22:46:13 driver-btm-soc.c:404:check_chain: !! chain[1]is exist
2019-05-01 22:46:13 driver-btm-soc.c:404:check_chain: !! chain[2]is exist
2019-05-01 22:46:17 driver-btm-soc.c:3722:get_product_id: product_id[0] = 0
2019-05-01 22:46:17 driver-btm-soc.c:3722:get_product_id: product_id[1] = 0
2019-05-01 22:46:17 driver-btm-soc.c:3722:get_product_id: product_id[2] = 0
2019-05-01 22:46:17 driver-btm-soc.c:3823:bitmain_board_init: g_product_id = 0
2019-05-01 22:46:17 driver-btm-soc.c:3574:_set_project_type: Project type: Antminer S17
2019-05-01 22:46:17 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2019-05-01 22:46:17 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2019-05-01 22:46:17 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2019-05-01 22:46:17 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2019-05-01 22:46:17 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2019-05-01 22:46:17 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2019-05-01 22:46:17 driver-btm-soc.c:3791:check_pool_worker: No valid pools, please configure them first!

[madmartyk]

My S17 Pro 53TH/s had default Antminer pools. All the boards also report the same frequency and turbo is 595.

The one I received 2 days ago had no pools listed, today's had the antminer pools. Strange...

[mindtrip]

I noticed my S17 (NON PRO) had no pool info but the S17 Pro's had default antpool set so it is a mixed bag.

I dug around the Code in S17Pro and its pretty clear Turbo mode is no different then Normal mode in a NON Pro S17. the big difference is the Low power Mode On a Pro is whats not really available on a NON Pro. They change the values depending on the model type so essentially Turbo mode is Normal mode I don't see any negative effect to running it in Turbo Mode based on my testing other then about 1 AMP more in power consumption.

[Biffa]

So about a 240W difference?

What about the difference between Normal and Turbo on a Pro?

[fccs]

So far my tests, ranging from 50 degrees F outside to 80 degrees.  The s17 pro (50th version if it even matters)  is doing a avg of 11amps @ 240v for 60th in turbo mode.  I am kinda pissed I can't just set the damn fans myself at 100% though.  This was damn stupid of bitmain to take out.  Like... why.  All my miners have the fans set to 100%, why can't I do it on the s17 series?  Normal mode was doing 50-52TH and turbo seems to do 58-60th.

[Artemis3]

So far my tests, ranging from 50 degrees F outside to 80 degrees.  The s17 pro (50th version if it even matters)  is doing a avg of 11amps @ 240v for 60th in turbo mode.  I am kinda pissed I can't just set the damn fans myself at 100% though.  This was damn stupid of bitmain to take out.  Like... why.  All my miners have the fans set to 100%, why can't I do it on the s17 series?  Normal mode was doing 50-52TH and turbo seems to do 58-60th.

Why not just disconnect the 4th wire from the fans? Oh the warranty sticker is in the way i guess? Its silly from Bitmain, as the older units did had full fan controls in the ui. No wonder people want to mod the firmware, they keep locking it down fueling the drive for changing it even more...

[philipma1957]

So far my tests, ranging from 50 degrees F outside to 80 degrees.  The s17 pro (50th version if it even matters)  is doing a avg of 11amps @ 240v for 60th in turbo mode.  I am kinda pissed I can't just set the damn fans myself at 100% though.  This was damn stupid of bitmain to take out.  Like... why.  All my miners have the fans set to 100%, why can't I do it on the s17 series?  Normal mode was doing 50-52TH and turbo seems to do 58-60th.

Why set at 100%

90 to 95% is better for the most part.

They take longer to break.
They save power.
They have almost the exact same cooling power.

The last 5 to 10% on the fan do not cool much better at all.

I do agree that stealing the ability set fans sucks.

[fccs]

Well whatever haha I just want to be able to set the fans.

[philipma1957]

Well whatever haha I just want to be able to set the fans.

I do agree with that option.

[minefarmbuy]

Can't inspect the UI page anymore?

[mindtrip]

anyone figure out how to get SSH enabled on these new miners?

[MoparMiningLLC]

anyone figure out how to get SSH enabled on these new miners?

no luck on mine yet - makes the money i spent on AM wasted - I also have the web services - but cannot do anything but look at them.

[Artemis3]

Probably it will take some exploit to regain access back. I'm willing to bet the web server could be a good starting place... Perhaps someone should, for science, provide access to an S17 controller for the community to, umm verify its security?. Maybe a bounty would set things in motion...

[SOL-RIQUEZA]

Performance summary of the Antminer S/17-53TH/s.

Hola to all Bitcoiners member! I want to share to interested member my miner performance model S/17-53TH/s working on normal mode.

Code:

(Antpool)

58.80 TH/s
10M Hashrate
58.80 TH/s
30M Hashrate
58.80 TH/s
1H Hashrate
GH/S(RT)	GH/S(avg)	
54644.23.  54352.68

Code:

(Slushpool)           
37 Minutes
52.09Th/s
0.00013089 BTC
3 %
1 Hour 9 Minutes
55.67Th/s
0.00013996 BTC
5 %
7 Hours 47 Minutes
52.15Th/s
0.00012708 BTC
40 %
8 Hours 11 Minutes
54.02Th/s
0.00013796 BTC
43 %
11 Hours 26 Minutes
54.38Th/s
0.00013524 BTC
64 %

I have screenshot of Recent Hash Rate from slush pool  =  https://imgur.com/ousnsTZ

[Artemis3]

Performance summary of the Antminer S/17-53TH/s.

Hola to all Bitcoiners member! I want to share to interested member my miner performance model S/17-53TH/s working on normal mode...

Mind trying with KanoPool or ckpool? you can use either anonymously. A full day would be preferable than some minutes.

[SOL-RIQUEZA]

Cheap power electricity cost from Québec 0,0591 $ CAD/kWh.