Title: T17+ doesn`t start mining!
Post by: kungen12321 on October 07, 2022, 09:08:54 PM
Hi guys! I have an S17PRO that won't start mine, need some expert help. I can access the interface via the ip address. Red light on the miner. Run with Braiin's software. Tried changing the control board but no improvement. I hope someone can help me find the error. I am sending the log from the miner, hope it can be of help! Thanks in advance! Braiins kernel log
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 235148K/262144K available (5572K kernel code, 204K rwdata, 1844K rodata, 260K init, 221K bss, 10612K reserved, 16384K cma-reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xd0800000 - 0xff800000 ( 752 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc0746524 (7418 kB)
[ 0.000000] .init : 0xc0747000 - 0xc0788000 ( 260 kB)
[ 0.000000] .data : 0xc0788000 - 0xc07bb2a0 ( 205 kB)
[ 0.000000] .bss : 0xc07bb2a0 - 0xc07f29c4 ( 222 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] slcr mapped to d0800000
[ 0.000000] L2C: platform modifies aux control register: 0x02060000 -> 0x32460000
[ 0.000000] L2C: DT/platform modifies aux control register: 0x02060000 -> 0x32460000
[ 0.000000] L2C-310 erratum 769419 enabled
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x46460001
[ 0.000000] zynq_clock_init: clkc starts at d0800100
[ 0.000000] Zynq clock init
[ 0.000011] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
[ 0.000034] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
[ 0.000137] clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
[ 0.000167] timer #0 at d0808000, irq=17
[ 0.000534] Console: colour dummy device 80x30
[ 0.000556] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[ 0.090310] pid_max: default: 32768 minimum: 301
[ 0.090415] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090429] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090931] CPU: Testing write buffer coherency: ok
[ 0.091139] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.091231] Setting up static identity map for 0x8280 - 0x82d8
[ 0.260300] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.260372] Brought up 2 CPUs
[ 0.260391] SMP: Total of 2 processors activated (2664.03 BogoMIPS).
[ 0.260400] CPU: All CPU(s) started in SVC mode.
[ 0.265138] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.265561] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.266463] pinctrl core: initialized pinctrl subsystem
[ 0.267805] NET: Registered protocol family 16
[ 0.269895] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.300300] cpuidle: using governor ladder
[ 0.320278] cpuidle: using governor menu
[ 0.332928] zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0xd0880000
[ 0.333352] zynq-pinctrl 700.pinctrl: zynq pinctrl initialized
[ 0.381490] GPIO IRQ not connected
[ 0.381508] XGpio: /amba_pl/gpio@41200000: registered, base is 902
[ 0.381690] GPIO IRQ not connected
[ 0.381702] XGpio: /amba_pl/gpio@41210000: registered, base is 897
[ 0.381934] XGpio: /amba_pl/gpio@41220000: registered, base is 895
[ 0.382776] vgaarb: loaded
[ 0.383169] SCSI subsystem initialized
[ 0.383504] usbcore: registered new interface driver usbfs
[ 0.383581] usbcore: registered new interface driver hub
[ 0.383897] usbcore: registered new device driver usb
[ 0.384430] media: Linux media interface: v0.10
[ 0.384510] Linux video capture interface: v2.00
[ 0.384589] pps_core: LinuxPPS API ver. 1 registered
[ 0.384600] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.384649] PTP clock support registered
[ 0.384739] EDAC MC: Ver: 3.0.0
[ 0.390992] Advanced Linux Sound Architecture Driver Initialized.
[ 0.392228] clocksource: Switched to clocksource arm_global_timer
[ 0.400775] NET: Registered protocol family 2
[ 0.401479] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.401522] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.401569] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.401629] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.401662] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.401881] NET: Registered protocol family 1
[ 0.402294] RPC: Registered named UNIX socket transport module.
[ 0.402307] RPC: Registered udp transport module.
[ 0.402316] RPC: Registered tcp transport module.
[ 0.402324] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.402355] PCI: CLS 0 bytes, default 64
[ 0.403960] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.415747] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.428152] io scheduler noop registered
[ 0.428175] io scheduler deadline registered
[ 0.428228] io scheduler cfq registered (default)
[ 0.430101] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.430122] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.430834] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.432178] e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 143, base_baud = 6249999) is a xuartps
[ 1.067067] console [ttyPS0] enabled
[ 1.071191] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to d0826000
[ 1.077915] [drm] Initialized drm 1.1.0 20060810
[ 1.088296] brd: module loaded
[ 1.097456] loop: module loaded
[ 1.103364] CAN device driver interface
[ 1.108512] libphy: MACB_mii_bus: probed
[ 1.192363] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 145 (26:7a:6c:5c:1d:e9)
[ 1.202238] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
[ 1.213456] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 1.219199] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 1.230851] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.237345] ehci-pci: EHCI PCI platform driver
[ 1.241919] usbcore: registered new interface driver usb-storage
[ 1.249408] mousedev: PS/2 mouse device common for all mice
[ 1.265333] i2c /dev entries driver
[ 1.272189] EDAC MC: ECC not enabled
[ 1.275996] Xilinx Zynq CpuIdle Driver started
[ 1.280670] sdhci: Secure Digital Host Controller Interface driver
[ 1.286805] sdhci: Copyright(c) Pierre Ossman
[ 1.291117] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.297134] sdhci-arasan e0100000.mmc: No vmmc regulator found
[ 1.302916] sdhci-arasan e0100000.mmc: No vqmmc regulator found
[ 1.343281] mmc0: SDHCI controller on e0100000.mmc [e0100000.mmc] using ADMA
[ 1.351243] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.357634] usbcore: registered new interface driver usbhid
[ 1.363150] usbhid: USB HID core driver
[ 1.367894] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.374201] nand: Micron MT29F2G08ABAGAWP
[ 1.378160] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
[ 1.385834] nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[ 1.397303] Bad block table found at page 131008, version 0x01
[ 1.403547] Bad block table found at page 130944, version 0x01
[ 1.409617] 10 cmdlinepart partitions found on MTD device pl35x-nand
[ 1.415913] Creating 10 MTD partitions on "pl35x-nand":
[ 1.421094] 0x000000000000-0x000000080000 : "boot"
[ 1.426961] 0x000000080000-0x000000300000 : "uboot"
[ 1.432761] 0x000000300000-0x000000500000 : "fpga1"
[ 1.438547] 0x000000500000-0x000000700000 : "fpga2"
[ 1.454384] 0x000000700000-0x000000780000 : "uboot_env"
[ 1.470541] 0x000000780000-0x000000800000 : "miner_cfg"
[ 1.486662] 0x000000800000-0x000001e00000 : "recovery"
[ 1.502815] 0x000001e00000-0x000007d00000 : "firmware1"
[ 1.519548] 0x000007d00000-0x00000dc00000 : "firmware2"
[ 1.536275] 0x00000dc00000-0x000010000000 : "factory"
[ 1.555194] nf_conntrack version 0.5.0 (3930 buckets, 15720 max)
[ 1.563096] NET: Registered protocol family 10
[ 1.568729] sit: IPv6 over IPv4 tunneling driver
[ 1.574104] NET: Registered protocol family 17
[ 1.578530] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[ 1.591090] can: controller area network core (rev 20120528 abi 9)
[ 1.597293] NET: Registered protocol family 29
[ 1.601662] can: raw protocol (rev 20120528)
[ 1.605935] can: broadcast manager protocol (rev 20120528 t)
[ 1.611561] can: netlink gateway (rev 20130117) max_hops=1
[ 1.617232] 8021q: 802.1Q VLAN Support v1.8
[ 1.621728] Registering SWP/SWPB emulation handler
[ 1.627976] ubi0: attaching mtd7
[ 1.992391] ubi0: scanning is finished
[ 2.003955] ubi0: attached mtd7 (name "firmware1", size 95 MiB)
[ 2.009795] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 2.016700] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 2.023444] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 2.030365] ubi0: good PEBs: 760, bad PEBs: 0, corrupted PEBs: 0
[ 2.036369] ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
[ 2.043579] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1468341335
[ 2.052687] ubi0: available PEBs: 0, total reserved PEBs: 760, PEBs reserved for bad PEB handling: 40
[ 2.061889] ubi0: background thread "ubi_bgt0d" started, PID 818
[ 2.072816] block ubiblock0_1: created from ubi0:1(rootfs)
[ 2.078237] hctosys: unable to open rtc device (rtc0)
[ 2.087767] ALSA device list:
[ 2.090654] No soundcards found.
[ 2.096711] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[ 2.104143] Freeing unused kernel memory: 260K (c0747000 - c0788000)
[ 2.573958] init: Console is alive
[ 2.577426] init: - watchdog -
[ 2.984323] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[ 3.080780] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[ 3.095137] init: - preinit -
[ 3.706729] random: jshn urandom read with 0 bits of entropy available
[ 3.911720] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 5.192420] macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
[ 5.200521] macb e000b000.ethernet eth0: link up (100/Full)
[ 5.206111] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 7.082270] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" started, PID 893
[ 7.111680] UBIFS (ubi0:2): recovery needed
[ 7.189074] UBIFS (ubi0:2): recovery completed
[ 7.193546] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "rootfs_data"
[ 7.201292] UBIFS (ubi0:2): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 7.211205] UBIFS (ubi0:2): FS size: 69582848 bytes (66 MiB, 548 LEBs), journal size 3428352 bytes (3 MiB, 27 LEBs)
[ 7.221617] UBIFS (ubi0:2): reserved for root: 3286569 bytes (3209 KiB)
[ 7.228214] UBIFS (ubi0:2): media format: w4/r0 (latest is w4/r0), UUID 3DC3CC97-3056-4A0E-9A22-4B055C061057, small LPT model
[ 7.242287] mount_root: switching to ubifs overlay
[ 7.258172] urandom-seed: Seeding with /etc/urandom.seed
[ 7.385701] procd: - early -
[ 7.388555] procd: - watchdog -
[ 8.025790] procd: - watchdog -
[ 8.029065] procd: - ubus -
[ 8.202293] macb e000b000.ethernet eth0: link down
[ 8.251447] procd: - init -
[ 8.573556] kmodloader: loading kernel modules from /etc/modules.d/*
[ 8.652490] tun: Universal TUN/TAP device driver, 1.6
[ 8.657462] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 8.666641] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 8.679096] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 8.803715] xt_time: kernel timezone is -0000
[ 8.814156] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 11.741122] device eth0 entered promiscuous mode
[ 11.755577] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[ 11.879969] Start post-upgrade process...
[ 12.256946] macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
[ 12.265253] macb e000b000.ethernet eth0: link up (100/Full)
[ 12.270773] br-lan: port 1(eth0) entered forwarding state
[ 12.276203] br-lan: port 1(eth0) entered forwarding state
[ 12.285759] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[ 12.832673] random: nonblocking pool is initialized
[ 13.327662] Detecting miner model...
[ 14.272251] br-lan: port 1(eth0) entered forwarding state
[ 15.353916] Oct 06 07:07:49.884 INFO bosminer_plus_tuner: Detected architecture Antminer X17/X19
[ 20.409793] Oct 06 07:07:54.940 INFO bosminer_plus_tuner::arch: Detected Hash Board #0:
[ 20.409793] +--------------------+-------------------------+
[ 20.409793] |S/N |<Missing S/N> |
[ 20.409793] |BOM version |01.03 |
[ 20.409793] |PCB version |01.01 |
[ 20.409793] |Voltage (Avg.) |18.30 V |
[ 20.409793] |Frequency (Avg.) |597 MHz |
[ 20.409793] |Hashrate |18694.00 GH/s |
[ 20.409793] +--------------------+-------------------------+
[ 20.409793]
[ 20.410403] Antminer S17 Pro
[ 20.467354] Oct 06 07:07:54.941 INFO bosminer_plus_tuner::arch: Detected Hash Board #1:
[ 20.467354] +--------------------+-------------------------+
[ 20.467354] |S/N |<Missing S/N> |
[ 20.467354] |BOM version |01.03 |
[ 20.467354] |PCB version |01.01 |
[ 20.467354] |Voltage (Avg.) |18.40 V |
[ 20.467354] |Frequency (Avg.) |585 MHz |
[ 20.467354] |Hashrate |18492.00 GH/s |
[ 20.467354] +--------------------+-------------------------+
[ 20.467354]
[ 20.522034] Oct 06 07:07:54.941 INFO bosminer_plus_tuner::arch: Detected Hash Board #2:
[ 20.522034] +--------------------+-------------------------+
[ 20.522034] |S/N |<Missing S/N> |
[ 20.522034] |BOM version |01.03 |
[ 20.522034] |PCB version |01.01 |
[ 20.522034] |Voltage (Avg.) |18.40 V |
[ 20.522034] |Frequency (Avg.) |595 MHz |
[ 20.522034] |Hashrate |18808.00 GH/s |
[ 20.522034] +--------------------+-------------------------+
[ 20.522034]
Title: Re: S17 PRO- doesn`t start mining!
Post by: BitMaxz on October 07, 2022, 09:31:06 PM
Your thread is a bit messy would you mind to insert all your logs inside a code tag you can find it while editing your post it looks like # button. Or next time use pastebin.com instead.
I'm not so familiar with braiinsOS logs would you mind switching it back to stock firmware?
Then post the kernel logs here.
You can follow the guide from this link below
- https://support.bitmain.com/hc/en-us/articles/360033757513-S17-S17Pro-S9-SE-S9k-Z11-control-board-program-recovery-SD-card-flashing-with-customized-PW-
Title: Re: S17 PRO- doesn`t start mining!
Post by: NotFuzzyWarm on October 07, 2022, 10:31:20 PM
...
I'm not so familiar with braiinsOS logs would you mind switching it back to stock firmware?
Then post the kernel logs here.
.. Also a key missing point is, did you ever run it with the stock FW and if so -- did it work? If the stock firmware works then this is an issue that is best addressed in the Braiins thread...
Title: Re: S17 PRO- doesn`t start mining!
Post by: kungen12321 on October 08, 2022, 06:23:20 AM
Your thread is a bit messy would you mind to insert all your logs inside a code tag you can find it while editing your post it looks like # button. Or next time use pastebin.com instead.
I'm not so familiar with braiinsOS logs would you mind switching it back to stock firmware?
Then post the kernel logs here.
You can follow the guide from this link below
- https://support.bitmain.com/hc/en-us/articles/360033757513-S17-S17Pro-S9-SE-S9k-Z11-control-board-program-recovery-SD-card-flashing-with-customized-PW-
Thanks for your advise, will try pastebin later. What kind of log is most important for you to have, system log or kernel log? Can it be dangerous to give away miner logs on the internet, if the logs reveals sensitive informations about the miner? The miner worked with stock firmware and also first with braiins firmware. I change the place of the miner and this problem came. Thanks for trying to help me!
Title: Re: S17 PRO- doesn`t start mining!
Post by: BitMaxz on October 08, 2022, 11:04:56 PM
Thanks for your advise, will try pastebin later.
What kind of log is most important for you to have, system log or kernel log?
Can it be dangerous to give away miner logs on the internet, if the logs reveals sensitive informations about the miner?
The miner worked with stock firmware and also first with braiins firmware. I change the place of the miner and this problem came.
It's better if you edit your whole thread and put the logs right now inside the code tag because it's not attractive to read if you have a messy thread. About the system or kernel logs if you still using Braiins I think you need to post them both but if you already flash the unit to the stock/original firmware then kernel logs are enough to give information about what happens to your miner. And take note sharing the logs is not dangerous except if it includes your Home IP address you must remove it or replace it with another IP. So you mean it works on stock firmware and then you switch to Braiins it works on the first try but after you move it to another place it stops working? Why not try it again with stock firmware to make sure it's working and to replace the corrupted program we can read the kernel logs much better than braiins. You can switch it back to braiins once we know your miner is working and running fine with stock firmware.
Title: Re: S17 PRO- doesn`t start mining!
Post by: kungen12321 on October 10, 2022, 08:16:22 PM
I think, I was able to fix the tread. At least It looks better.
I downloaded the stock firmware for sd card from bitmains website and copy it to the sd card, put the sd card in the miner and started it up. But it doesn`t change it back to stock firmware. Yes, the sd card I format to fat32.
When I upgraded to braiins firmware I just downloaded the Braiins xxxxx.img file. Started balenaetcher and flashed it. Reboot the device and it worked.
Maybe I should just give you guys the system and kernel logs from the braiins firmware?
Yes, that is correct the miner worked first with stock firmware and also with braiins, but after changed the miners location, the controll board has the red light turned on and hashing doens`t start.
Title: Re: T17+ doesn`t start mining!
Post by: kungen12321 on October 10, 2022, 08:46:39 PM
It should be a T17+ miner. Logs from the Braiins firmware Kernel log
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 235148K/262144K available (5572K kernel code, 204K rwdata, 1844K rodata, 260K init, 221K bss, 10612K reserved, 16384K cma-reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xd0800000 - 0xff800000 ( 752 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc0746524 (7418 kB)
[ 0.000000] .init : 0xc0747000 - 0xc0788000 ( 260 kB)
[ 0.000000] .data : 0xc0788000 - 0xc07bb2a0 ( 205 kB)
[ 0.000000] .bss : 0xc07bb2a0 - 0xc07f29c4 ( 222 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] slcr mapped to d0800000
[ 0.000000] L2C: platform modifies aux control register: 0x02060000 -> 0x32460000
[ 0.000000] L2C: DT/platform modifies aux control register: 0x02060000 -> 0x32460000
[ 0.000000] L2C-310 erratum 769419 enabled
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x46460001
[ 0.000000] zynq_clock_init: clkc starts at d0800100
[ 0.000000] Zynq clock init
[ 0.000011] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
[ 0.000035] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
[ 0.000139] clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
[ 0.000169] timer #0 at d0808000, irq=17
[ 0.000532] Console: colour dummy device 80x30
[ 0.000554] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[ 0.090311] pid_max: default: 32768 minimum: 301
[ 0.090415] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090429] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090932] CPU: Testing write buffer coherency: ok
[ 0.091140] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.091232] Setting up static identity map for 0x8280 - 0x82d8
[ 0.260300] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.260374] Brought up 2 CPUs
[ 0.260393] SMP: Total of 2 processors activated (2664.03 BogoMIPS).
[ 0.260402] CPU: All CPU(s) started in SVC mode.
[ 0.265132] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.265558] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.266465] pinctrl core: initialized pinctrl subsystem
[ 0.267812] NET: Registered protocol family 16
[ 0.269907] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.300301] cpuidle: using governor ladder
[ 0.320280] cpuidle: using governor menu
[ 0.332977] zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0xd0880000
[ 0.333404] zynq-pinctrl 700.pinctrl: zynq pinctrl initialized
[ 0.381719] GPIO IRQ not connected
[ 0.381737] XGpio: /amba_pl/gpio@41200000: registered, base is 902
[ 0.381922] GPIO IRQ not connected
[ 0.381934] XGpio: /amba_pl/gpio@41210000: registered, base is 897
[ 0.382185] XGpio: /amba_pl/gpio@41220000: registered, base is 895
[ 0.383018] vgaarb: loaded
[ 0.383447] SCSI subsystem initialized
[ 0.383835] usbcore: registered new interface driver usbfs
[ 0.383931] usbcore: registered new interface driver hub
[ 0.384037] usbcore: registered new device driver usb
[ 0.384557] media: Linux media interface: v0.10
[ 0.384639] Linux video capture interface: v2.00
[ 0.384720] pps_core: LinuxPPS API ver. 1 registered
[ 0.384732] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.384779] PTP clock support registered
[ 0.384873] EDAC MC: Ver: 3.0.0
[ 0.386132] Advanced Linux Sound Architecture Driver Initialized.
[ 0.387403] clocksource: Switched to clocksource arm_global_timer
[ 0.396162] NET: Registered protocol family 2
[ 0.396924] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.396965] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.397013] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.397068] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.397099] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.397292] NET: Registered protocol family 1
[ 0.407857] RPC: Registered named UNIX socket transport module.
[ 0.407871] RPC: Registered udp transport module.
[ 0.407880] RPC: Registered tcp transport module.
[ 0.407889] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.407922] PCI: CLS 0 bytes, default 64
[ 0.409516] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.421415] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.423824] io scheduler noop registered
[ 0.423847] io scheduler deadline registered
[ 0.423900] io scheduler cfq registered (default)
[ 0.425808] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.425829] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.426569] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.428010] e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 143, base_baud = 6249999) is a xuartps
[ 1.062908] console [ttyPS0] enabled
[ 1.067065] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to d0826000
[ 1.073791] [drm] Initialized drm 1.1.0 20060810
[ 1.084073] brd: module loaded
[ 1.093226] loop: module loaded
[ 1.099212] CAN device driver interface
[ 1.104614] libphy: MACB_mii_bus: probed
[ 1.187538] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 145 (ce:d9:36:d2:b6:39)
[ 1.197411] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
[ 1.208633] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 1.214382] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 1.226017] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.232507] ehci-pci: EHCI PCI platform driver
[ 1.237071] usbcore: registered new interface driver usb-storage
[ 1.244570] mousedev: PS/2 mouse device common for all mice
[ 1.260510] i2c /dev entries driver
[ 1.267677] EDAC MC: ECC not enabled
[ 1.271434] Xilinx Zynq CpuIdle Driver started
[ 1.276160] sdhci: Secure Digital Host Controller Interface driver
[ 1.282291] sdhci: Copyright(c) Pierre Ossman
[ 1.286603] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.292626] sdhci-arasan e0100000.mmc: No vmmc regulator found
[ 1.298403] sdhci-arasan e0100000.mmc: No vqmmc regulator found
[ 1.338453] mmc0: SDHCI controller on e0100000.mmc [e0100000.mmc] using ADMA
[ 1.346395] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.352781] usbcore: registered new interface driver usbhid
[ 1.358299] usbhid: USB HID core driver
[ 1.363056] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.369359] nand: Micron MT29F2G08ABAEAWP
[ 1.373318] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.380893] nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[ 1.392359] Bad block table found at page 131008, version 0x01
[ 1.398576] Bad block table found at page 130944, version 0x01
[ 1.404632] 10 cmdlinepart partitions found on MTD device pl35x-nand
[ 1.410930] Creating 10 MTD partitions on "pl35x-nand":
[ 1.416111] 0x000000000000-0x000000080000 : "boot"
[ 1.421967] 0x000000080000-0x000000300000 : "uboot"
[ 1.427812] 0x000000300000-0x000000500000 : "fpga1"
[ 1.433594] 0x000000500000-0x000000700000 : "fpga2"
[ 1.449432] 0x000000700000-0x000000780000 : "uboot_env"
[ 1.465584] 0x000000780000-0x000000800000 : "miner_cfg"
[ 1.481720] 0x000000800000-0x000001e00000 : "recovery"
[ 1.497864] 0x000001e00000-0x000007d00000 : "firmware1"
[ 1.514566] 0x000007d00000-0x00000dc00000 : "firmware2"
[ 1.531297] 0x00000dc00000-0x000010000000 : "factory"
[ 1.550229] nf_conntrack version 0.5.0 (3930 buckets, 15720 max)
[ 1.558152] NET: Registered protocol family 10
[ 1.563790] sit: IPv6 over IPv4 tunneling driver
[ 1.569160] NET: Registered protocol family 17
[ 1.573575] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[ 1.586144] can: controller area network core (rev 20120528 abi 9)
[ 1.592346] NET: Registered protocol family 29
[ 1.596717] can: raw protocol (rev 20120528)
[ 1.600988] can: broadcast manager protocol (rev 20120528 t)
[ 1.606614] can: netlink gateway (rev 20130117) max_hops=1
[ 1.612303] 8021q: 802.1Q VLAN Support v1.8
[ 1.616798] Registering SWP/SWPB emulation handler
[ 1.623043] ubi0: attaching mtd7
[ 1.968994] ubi0: scanning is finished
[ 1.980313] ubi0: attached mtd7 (name "firmware1", size 95 MiB)
[ 1.986151] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.993029] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.999798] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 2.006722] ubi0: good PEBs: 760, bad PEBs: 0, corrupted PEBs: 0
[ 2.012725] ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
[ 2.019955] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 340354817
[ 2.028958] ubi0: available PEBs: 0, total reserved PEBs: 760, PEBs reserved for bad PEB handling: 40
[ 2.038178] ubi0: background thread "ubi_bgt0d" started, PID 818
[ 2.049066] block ubiblock0_1: created from ubi0:1(rootfs)
[ 2.054491] hctosys: unable to open rtc device (rtc0)
[ 2.064042] ALSA device list:
[ 2.066932] No soundcards found.
[ 2.072949] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[ 2.080389] Freeing unused kernel memory: 260K (c0747000 - c0788000)
[ 2.546730] init: Console is alive
[ 2.550303] init: - watchdog -
[ 2.956232] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[ 3.051688] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[ 3.068267] init: - preinit -
[ 3.674498] random: jshn urandom read with 0 bits of entropy available
[ 3.878494] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 5.217598] macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
[ 5.225703] macb e000b000.ethernet eth0: link up (100/Full)
[ 5.231292] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 7.047470] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" started, PID 892
[ 7.073276] UBIFS (ubi0:2): recovery needed
[ 7.150274] UBIFS (ubi0:2): recovery completed
[ 7.154722] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "rootfs_data"
[ 7.162493] UBIFS (ubi0:2): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 7.172379] UBIFS (ubi0:2): FS size: 69582848 bytes (66 MiB, 548 LEBs), journal size 3428352 bytes (3 MiB, 27 LEBs)
[ 7.182821] UBIFS (ubi0:2): reserved for root: 3286569 bytes (3209 KiB)
[ 7.189396] UBIFS (ubi0:2): media format: w4/r0 (latest is w4/r0), UUID F5A7F75C-260F-48B1-BC39-CAD6D09D8D95, small LPT model
[ 7.202857] mount_root: switching to ubifs overlay
[ 7.217793] urandom-seed: Seeding with /etc/urandom.seed
[ 7.344663] procd: - early -
[ 7.347565] procd: - watchdog -
[ 7.988820] procd: - watchdog -
[ 7.992098] procd: - ubus -
[ 8.215221] procd: - init -
[ 8.261275] macb e000b000.ethernet eth0: link down
[ 8.533327] kmodloader: loading kernel modules from /etc/modules.d/*
[ 8.612182] tun: Universal TUN/TAP device driver, 1.6
[ 8.617153] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 8.626514] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 8.639586] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 8.768878] xt_time: kernel timezone is -0000
[ 8.779330] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 11.710601] device eth0 entered promiscuous mode
[ 11.727620] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[ 11.870631] Start post-upgrade process...
[ 12.257616] macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
[ 12.265723] macb e000b000.ethernet eth0: link up (100/Full)
[ 12.281857] br-lan: port 1(eth0) entered forwarding state
[ 12.287230] br-lan: port 1(eth0) entered forwarding state
[ 12.307158] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[ 12.741700] random: nonblocking pool is initialized
[ 13.427963] Detecting miner model...
[ 14.277433] br-lan: port 1(eth0) entered forwarding state
[ 15.352857] Oct 06 05:54:37.922 INFO bosminer_plus_tuner: Detected architecture Antminer X17/X19
[ 20.426053] Oct 06 05:54:42.996 INFO bosminer_plus_tuner::arch: Detected Hash Board #0:
[ 20.426053] +--------------------+-------------------------+
[ 20.426053] |S/N |FXDZYH8BJJEAC026W |
[ 20.426053] |BOM version |01.00 |
[ 20.426053] |PCB version |01.00 |
[ 20.426053] |Voltage (Avg.) |17.90 V |
[ 20.426053] |Frequency (Avg.) |660 MHz |
[ 20.426053] |Hashrate |19515.00 GH/s |
[ 20.426053] +--------------------+-------------------------+
[ 20.426053]
[ 20.426657] Antminer T17+
[ 20.483328] Oct 06 05:54:42.996 INFO bosminer_plus_tuner::arch: Detected Hash Board #1:
[ 20.483328] +--------------------+-------------------------+
[ 20.483328] |S/N |FXDZYH8BJJEAC01RH |
[ 20.483328] |BOM version |01.00 |
[ 20.483328] |PCB version |01.00 |
[ 20.483328] |Voltage (Avg.) |17.90 V |
[ 20.483328] |Frequency (Avg.) |667 MHz |
[ 20.483328] |Hashrate |19714.00 GH/s |
[ 20.483328] +--------------------+-------------------------+
[ 20.483328]
[ 20.538078] Oct 06 05:54:42.996 INFO bosminer_plus_tuner::arch: Detected Hash Board #2:
[ 20.538078] +--------------------+-------------------------+
[ 20.538078] |S/N |FXDZYH8BJJEAC02MS |
[ 20.538078] |BOM version |01.00 |
[ 20.538078] |PCB version |01.00 |
[ 20.538078] |Voltage (Avg.) |17.90 V |
[ 20.538078] |Frequency (Avg.) |681 MHz |
[ 20.538078] |Hashrate |20110.00 GH/s |
[ 20.538078] +--------------------+-------------------------+
[ 20.538078]
Title: Re: T17+ doesn`t start mining!
Post by: kungen12321 on October 10, 2022, 09:04:54 PM
System log
INFO actix_web::middleware::logger: 192.168.1.999:54081 POST /graphql HTTP/1.1 200 2559 http://192.168.1.999/settings/pools/ 0.006139
Mon Oct 10 20:36:11 2022 daemon.info boser[1587]: Oct 10 20:36:11.098 INFO actix_web::middleware::logger: 192.168.1.999:54081 POST /graphql HTTP/1.1 200 989 http://192.168.1.999/settings/pools/ 0.004034
Mon Oct 10 20:36:11 2022 daemon.info boser[1587]: Oct 10 20:36:11.944 INFO actix_web::middleware::logger: 192.168.1.999:54081 POST /graphql HTTP/1.1 200 60 http://192.168.1.999/settings/pools/ 0.001085
Mon Oct 10 20:36:13 2022 daemon.info boser[1587]: Oct 10 20:36:13.127 INFO actix_web::middleware::logger: 192.168.1.999:54081 GET /cgi-bin/luci/admin/system/commands HTTP/1.1 200 7484 http://192.168.1.999/settings/pools/ 0.104143
Mon Oct 10 20:36:17 2022 daemon.info boser[1587]: Oct 10 20:36:17.076 INFO actix_web::middleware::logger: 192.168.1.999:54081 GET /cgi-bin/luci/admin/status/dmesg HTTP/1.1 200 19523 http://192.168.1.119/cgi-bin/luci/admin/system/commands 0.103909
Mon Oct 10 20:36:19 2022 daemon.err bosminer[1603]: Oct 10 20:36:19.265 INFO bosminer_backend::miner: CHAIN/2: Retrying hashboard start...
Mon Oct 10 20:36:19 2022 daemon.err bosminer[1603]: Oct 10 20:36:19.268 INFO bosminer_antminer::io: Hashboard 2: bm13xx 1.0.2 for Antminer S9 or higher built on 2020-12-04 14:49:18 UTC
Mon Oct 10 20:36:19 2022 daemon.err bosminer[1603]: Oct 10 20:36:19.273 INFO bosminer_am2_s17::power::antminer: PWR/2: Voltage controller reset
Mon Oct 10 20:36:19 2022 daemon.err bosminer[1603]: Oct 10 20:36:19.661 INFO bosminer_backend::miner: CHAIN/3: Retrying hashboard start...
Mon Oct 10 20:36:19 2022 daemon.err bosminer[1603]: Oct 10 20:36:19.665 INFO bosminer_antminer::io: Hashboard 3: bm13xx 1.0.2 for Antminer S9 or higher built on 2020-12-04 14:49:18 UTC
Mon Oct 10 20:36:19 2022 daemon.err bosminer[1603]: Oct 10 20:36:19.670 INFO bosminer_am2_s17::power::antminer: PWR/3: Voltage controller reset
Mon Oct 10 20:36:20 2022 daemon.err bosminer[1603]: Oct 10 20:36:20.711 INFO bosminer_am2_s17::power::antminer: PWR/2: Voltage controller application started
Mon Oct 10 20:36:20 2022 daemon.err bosminer[1603]: Oct 10 20:36:20.821 INFO bosminer_am2_s17::power::antminer: PWR/2: Voltage controller firmware version 0x88
Mon Oct 10 20:36:20 2022 daemon.err bosminer[1603]: Oct 10 20:36:20.821 INFO bosminer_backend::hashchain: CHAIN/2: Initializing (fingerprint: 30924e3d99f4a05f, difficulty: 4)
Mon Oct 10 20:36:20 2022 daemon.err bosminer[1603]: Oct 10 20:36:20.821 INFO bosminer_backend::hashchain: CHAIN/2: Resetting hash board
Mon Oct 10 20:36:21 2022 daemon.err bosminer[1603]: Oct 10 20:36:21.109 INFO bosminer_am2_s17::power::antminer: PWR/3: Voltage controller application started
Mon Oct 10 20:36:21 2022 daemon.err bosminer[1603]: Oct 10 20:36:21.218 INFO bosminer_am2_s17::power::antminer: PWR/3: Voltage controller firmware version 0x88
Mon Oct 10 20:36:21 2022 daemon.err bosminer[1603]: Oct 10 20:36:21.218 INFO bosminer_backend::hashchain: CHAIN/3: Initializing (fingerprint: 780c6c0773bd3ed9, difficulty: 4)
Mon Oct 10 20:36:21 2022 daemon.err bosminer[1603]: Oct 10 20:36:21.218 INFO bosminer_backend::hashchain: CHAIN/3: Resetting hash board
Mon Oct 10 20:36:21 2022 daemon.err bosminer[1603]: Oct 10 20:36:21.966 INFO bosminer_am2_s17::power::antminer: PWR/2: Enable voltage
Mon Oct 10 20:36:22 2022 daemon.err bosminer[1603]: Oct 10 20:36:22.217 INFO bosminer_antminer::io: CHAIN/2: Setting IP core baud rate @ requested: 115200, actual: 114679, divisor 0x6c
Mon Oct 10 20:36:22 2022 daemon.err bosminer[1603]: Oct 10 20:36:22.365 INFO bosminer_am2_s17::power::antminer: PWR/3: Enable voltage
Mon Oct 10 20:36:22 2022 daemon.err bosminer[1603]: Oct 10 20:36:22.615 INFO bosminer_antminer::io: CHAIN/3: Setting IP core baud rate @ requested: 115200, actual: 114679, divisor 0x6c
Mon Oct 10 20:36:23 2022 daemon.err bosminer[1603]: Oct 10 20:36:23.219 INFO bosminer_backend::hashchain: CHAIN/2: Initializing hashchain
Mon Oct 10 20:36:23 2022 daemon.err bosminer[1603]: Oct 10 20:36:23.321 INFO bosminer_am2_s17::hashchain: CHAIN/2: Discovered 0 chips (expected 44 chips)
Mon Oct 10 20:36:23 2022 daemon.err bosminer[1603]: Oct 10 20:36:23.321 ERROR bosminer_backend::hashchain: CHAIN/2: Init failed: no chips detected on the current chain
Mon Oct 10 20:36:23 2022 daemon.err bosminer[1603]: Oct 10 20:36:23.523 INFO bosminer_am2_s17::power::antminer: PWR/2: Disable voltage
Mon Oct 10 20:36:23 2022 daemon.err bosminer[1603]: Oct 10 20:36:23.616 INFO bosminer_backend::hashchain: CHAIN/3: Initializing hashchain
Mon Oct 10 20:36:23 2022 daemon.err bosminer[1603]: Oct 10 20:36:23.717 INFO bosminer_am2_s17::hashchain: CHAIN/3: Discovered 0 chips (expected 44 chips)
Mon Oct 10 20:36:23 2022 daemon.err bosminer[1603]: Oct 10 20:36:23.717 ERROR bosminer_backend::hashchain: CHAIN/3: Init failed: no chips detected on the current chain
Mon Oct 10 20:36:23 2022 daemon.err bosminer[1603]: Oct 10 20:36:23.919 INFO bosminer_am2_s17::power::antminer: PWR/3: Disable voltage
Mon Oct 10 20:36:24 2022 daemon.err bosminer[1603]: Oct 10 20:36:24.625 ERROR bosminer_backend::miner: CHAIN/2: Start failed: NoChipsDetected
Mon Oct 10 20:36:25 2022 daemon.err bosminer[1603]: Oct 10 20:36:25.020 ERROR bosminer_backend::miner: CHAIN/3: Start failed: NoChipsDetected
Mon Oct 10 20:36:28 2022 daemon.err bosminer[1603]: Oct 10 20:36:28.030 INFO bosminer::client::stratum_v2: Stratum: changing target to 00000000007fff80000000000000000000000000000000000000000000000000 diff=512
Mon Oct 10 20:36:34 2022 daemon.err bosminer[1603]: Oct 10 20:36:34.627 INFO bosminer_backend::miner: CHAIN/2: Retrying hashboard start...
Mon Oct 10 20:36:34 2022 daemon.err bosminer[1603]: Oct 10 20:36:34.630 INFO bosminer_antminer::io: Hashboard 2: bm13xx 1.0.2 for Antminer S9 or higher built on 2020-12-04 14:49:18 UTC
Mon Oct 10 20:36:34 2022 daemon.err bosminer[1603]: Oct 10 20:36:34.635 INFO bosminer_am2_s17::power::antminer: PWR/2: Voltage controller reset
Mon Oct 10 20:36:35 2022 daemon.err bosminer[1603]: Oct 10 20:36:35.021 INFO bosminer_backend::miner: CHAIN/3: Retrying hashboard start...
Mon Oct 10 20:36:35 2022 daemon.err bosminer[1603]: Oct 10 20:36:35.025 INFO bosminer_antminer::io: Hashboard 3: bm13xx 1.0.2 for Antminer S9 or higher built on 2020-12-04 14:49:18 UTC
Mon Oct 10 20:36:35 2022 daemon.err bosminer[1603]: Oct 10 20:36:35.031 INFO bosminer_am2_s17::power::antminer: PWR/3: Voltage controller reset
Mon Oct 10 20:36:36 2022 daemon.err bosminer[1603]: Oct 10 20:36:36.073 INFO bosminer_am2_s17::power::antminer: PWR/2: Voltage controller application started
Mon Oct 10 20:36:36 2022 daemon.err bosminer[1603]: Oct 10 20:36:36.182 INFO bosminer_am2_s17::power::antminer: PWR/2: Voltage controller firmware version 0x88
Mon Oct 10 20:36:36 2022 daemon.err bosminer[1603]: Oct 10 20:36:36.183 INFO bosminer_backend::hashchain: CHAIN/2: Initializing (fingerprint: 30924e3d99f4a05f, difficulty: 4)
Mon Oct 10 20:36:36 2022 daemon.err bosminer[1603]: Oct 10 20:36:36.183 INFO bosminer_backend::hashchain: CHAIN/2: Resetting hash board
Mon Oct 10 20:36:36 2022 daemon.err bosminer[1603]: Oct 10 20:36:36.468 INFO bosminer_am2_s17::power::antminer: PWR/3: Voltage controller application started
Mon Oct 10 20:36:36 2022 daemon.err bosminer[1603]: Oct 10 20:36:36.578 INFO bosminer_am2_s17::power::antminer: PWR/3: Voltage controller firmware version 0x88
Mon Oct 10 20:36:36 2022 daemon.err bosminer[1603]: Oct 10 20:36:36.578 INFO bosminer_backend::hashchain: CHAIN/3: Initializing (fingerprint: 780c6c0773bd3ed9, difficulty: 4)
Mon Oct 10 20:36:36 2022 daemon.err bosminer[1603]: Oct 10 20:36:36.578 INFO bosminer_backend::hashchain: CHAIN/3: Resetting hash board
Mon Oct 10 20:36:37 2022 daemon.err bosminer[1603]: Oct 10 20:36:37.328 INFO bosminer_am2_s17::power::antminer: PWR/2: Enable voltage
Mon Oct 10 20:36:37 2022 daemon.err bosminer[1603]: Oct 10 20:36:37.579 INFO bosminer_antminer::io: CHAIN/2: Setting IP core baud rate @ requested: 115200, actual: 114679, divisor 0x6c
Mon Oct 10 20:36:37 2022 daemon.err bosminer[1603]: Oct 10 20:36:37.728 INFO bosminer_am2_s17::power::antminer: PWR/3: Enable voltage
Mon Oct 10 20:36:37 2022 daemon.err bosminer[1603]: Oct 10 20:36:37.979 INFO bosminer_antminer::io: CHAIN/3: Setting IP core baud rate @ requested: 115200, actual: 114679, divisor 0x6c
Mon Oct 10 20:36:38 2022 daemon.err bosminer[1603]: Oct 10 20:36:38.581 INFO bosminer_backend::hashchain: CHAIN/2: Initializing hashchain
Mon Oct 10 20:36:38 2022 daemon.err bosminer[1603]: Oct 10 20:36:38.683 INFO bosminer_am2_s17::hashchain: CHAIN/2: Discovered 0 chips (expected 44 chips)
Mon Oct 10 20:36:38 2022 daemon.err bosminer[1603]: Oct 10 20:36:38.683 ERROR bosminer_backend::hashchain: CHAIN/2: Init failed: no chips detected on the current chain
Mon Oct 10 20:36:38 2022 daemon.err bosminer[1603]: Oct 10 20:36:38.884 INFO bosminer_am2_s17::power::antminer: PWR/2: Disable voltage
Mon Oct 10 20:36:38 2022 daemon.err bosminer[1603]: Oct 10 20:36:38.981 INFO bosminer_backend::hashchain: CHAIN/3: Initializing hashchain
Mon Oct 10 20:36:39 2022 daemon.err bosminer[1603]: Oct 10 20:36:39.081 INFO bosminer_am2_s17::hashchain: CHAIN/3: Discovered 0 chips (expected 44 chips)
Mon Oct 10 20:36:39 2022 daemon.err bosminer[1603]: Oct 10 20:36:39.082 ERROR bosminer_backend::hashchain: CHAIN/3: Init failed: no chips detected on the current chain
Mon Oct 10 20:36:39 2022 daemon.err bosminer[1603]: Oct 10 20:36:39.284 INFO bosminer_am2_s17::power::antminer: PWR/3: Disable voltage
Mon Oct 10 20:36:39 2022 daemon.info boser[1587]: Oct 10 20:36:39.971 INFO actix_web::middleware::logger: 192.168.1.999:54088 GET /cgi-bin/luci/admin/status/syslog HTTP/1.1 200 89435 http://192.168.1.119/cgi-bin/luci/admin/status/dmesg 0.325482
Mon Oct 10 20:36:39 2022 daemon.err bosminer[1603]: Oct 10 20:36:39.987 ERROR bosminer_backend::miner: CHAIN/2: Start failed: NoChipsDetected
Mon Oct 10 20:36:40 2022 daemon.err bosminer[1603]: Oct 10 20:36:40.386 ERROR bosminer_backend::miner: CHAIN/3: Start failed: NoChipsDetected
Mon Oct 10 20:36:49 2022 daemon.err bosminer[1603]: Oct 10 20:36:49.988 INFO bosminer_backend::miner: CHAIN/2: Retrying hashboard start...
Mon Oct 10 20:36:49 2022 daemon.err bosminer[1603]: Oct 10 20:36:49.991 INFO bosminer_antminer::io: Hashboard 2: bm13xx 1.0.2 for Antminer S9 or higher built on 2020-12-04 14:49:18 UTC
Mon Oct 10 20:36:49 2022 daemon.err bosminer[1603]: Oct 10 20:36:49.996 INFO bosminer_am2_s17::power::antminer: PWR/2: Voltage controller reset
Mon Oct 10 20:36:50 2022 daemon.err bosminer[1603]: Oct 10 20:36:50.387 INFO bosminer_backend::miner: CHAIN/3: Retrying hashboard start...
Mon Oct 10 20:36:50 2022 daemon.err bosminer[1603]: Oct 10 20:36:50.391 INFO bosminer_antminer::io: Hashboard 3: bm13xx 1.0.2 for Antminer S9 or higher built on 2020-12-04 14:49:18 UTC
Mon Oct 10 20:36:50 2022 daemon.err bosminer[1603]: Oct 10 20:36:50.396 INFO bosminer_am2_s17::power::antminer: PWR/3: Voltage controller reset
Mon Oct 10 20:36:51 2022 daemon.err bosminer[1603]: Oct 10 20:36:51.433 INFO bosminer_am2_s17::power::antminer: PWR/2: Voltage controller application started
Mon Oct 10 20:36:51 2022 daemon.err bosminer[1603]: Oct 10 20:36:51.541 INFO bosminer_am2_s17::power::antminer: PWR/2: Voltage controller firmware version 0x88
Mon Oct 10 20:36:51 2022 daemon.err bosminer[1603]: Oct 10 20:36:51.542 INFO bosminer_backend::hashchain: CHAIN/2: Initializing (fingerprint: 30924e3d99f4a05f, difficulty: 4)
Mon Oct 10 20:36:51 2022 daemon.err bosminer[1603]: Oct 10 20:36:51.542 INFO bosminer_backend::hashchain: CHAIN/2: Resetting hash board
Mon Oct 10 20:36:51 2022 daemon.err bosminer[1603]: Oct 10 20:36:51.835 INFO bosminer_am2_s17::power::antminer: PWR/3: Voltage controller application started
Mon Oct 10 20:36:51 2022 daemon.err bosminer[1603]: Oct 10 20:36:51.944 INFO bosminer_am2_s17::power::antminer: PWR/3: Voltage controller firmware version 0x88
Mon Oct 10 20:36:51 2022 daemon.err bosminer[1603]: Oct 10 20:36:51.944 INFO bosminer_backend::hashchain: CHAIN/3: Initializing (fingerprint: 780c6c0773bd3ed9, difficulty: 4)
Mon Oct 10 20:36:51 2022 daemon.err bosminer[1603]: Oct 10 20:36:51.944 INFO bosminer_backend::hashchain: CHAIN/3: Resetting hash board
Mon Oct 10 20:36:52 2022 daemon.err bosminer[1603]: Oct 10 20:36:52.687 INFO bosminer_am2_s17::power::antminer: PWR/2: Enable voltage
Mon Oct 10 20:36:52 2022 daemon.err bosminer[1603]: Oct 10 20:36:52.937 INFO bosminer_antminer::io: CHAIN/2: Setting IP core baud rate @ requested: 115200, actual: 114679, divisor 0x6c
Mon Oct 10 20:36:53 2022 daemon.err bosminer[1603]: Oct 10 20:36:53.089 INFO bosminer_am2_s17::power::antminer: PWR/3: Enable voltage
Mon Oct 10 20:36:53 2022 daemon.err bosminer[1603]: Oct 10 20:36:53.340 INFO bosminer_antminer::io: CHAIN/3: Setting IP core baud rate @ requested: 115200, actual: 114679, divisor 0x6c
Mon Oct 10 20:36:53 2022 daemon.err bosminer[1603]: Oct 10 20:36:53.938 INFO bosminer_backend::hashchain: CHAIN/2: Initializing hashchain
Mon Oct 10 20:36:54 2022 daemon.err bosminer[1603]: Oct 10 20:36:54.039 INFO bosminer_am2_s17::hashchain: CHAIN/2: Discovered 0 chips (expected 44 chips)
Mon Oct 10 20:36:54 2022 daemon.err bosminer[1603]: Oct 10 20:36:54.039 ERROR bosminer_backend::hashchain: CHAIN/2: Init failed: no chips detected on the current chain
Mon Oct 10 20:36:54 2022 daemon.err bosminer[1603]: Oct 10 20:36:54.241 INFO bosminer_am2_s17::power::antminer: PWR/2: Disable voltage
Mon Oct 10 20:36:54 2022 daemon.err bosminer[1603]: Oct 10 20:36:54.341 INFO bosminer_backend::hashchain: CHAIN/3: Initializing hashchain
Mon Oct 10 20:36:54 2022 daemon.err bosminer[1603]: Oct 10 20:36:54.442 INFO bosminer_am2_s17::hashchain: CHAIN/3: Discovered 0 chips (expected 44 chips)
Mon Oct 10 20:36:54 2022 daemon.err bosminer[1603]: Oct 10 20:36:54.442 ERROR bosminer_backend::hashchain: CHAIN/3: Init failed: no chips detected on the current chain
Mon Oct 10 20:36:54 2022 daemon.err bosminer[1603]: Oct 10 20:36:54.644 INFO bosminer_am2_s17::power::antminer: PWR/3: Disable voltage
Mon Oct 10 20:36:55 2022 daemon.info boser[1587]: Oct 10 20:36:55.013 INFO actix_web::middleware::logger: 192.168.1.999:54090 GET /cgi-bin/luci/admin/status/syslog HTTP/1.1 200 94011 - 0.344754
Mon Oct 10 20:36:55 2022 daemon.err bosminer[1603]: Oct 10 20:36:55.342 ERROR bosminer_backend::miner: CHAIN/2: Start failed: NoChipsDetected
Mon Oct 10 20:36:55 2022 daemon.err bosminer[1603]: Oct 10 20:36:55.746 ERROR bosminer_backend::miner: CHAIN/3: Start failed: NoChipsDetected
Mon Oct 10 20:36:55 2022 daemon.err bosminer[1603]: Oct 10 20:36:55.747 INFO bosminer_plus_tuner::tune::experiment: Tune/all: Status: Hashchain refused to start: InitError on hashchain 2: no chips detected on the current chain
Mon Oct 10 20:36:55 2022 daemon.err bosminer[1603]: Oct 10 20:36:55.747 INFO bosminer_plus_tuner::tune::experiment: Tune/2: Disabling hashchain, reason: no chips detected on the current chain
Mon Oct 10 20:36:55 2022 daemon.err bosminer[1603]: Oct 10 20:36:55.747 INFO bosminer_plus_tuner::tune: Tune/all: Tuning result: Err(Disabled hashboard 2 (init error no chips detected on the current chain)), shutting down hashboards and restarting in: 10s
Mon Oct 10 20:37:05 2022 daemon.err bosminer[1603]: Oct 10 20:37:05.748 INFO bosminer_plus_tuner::tune: Tune/all: Starting tuning: #2, hashboards: [1, 2, 3]
Mon Oct 10 20:37:05 2022 daemon.err bosminer[1603]: Oct 10 20:37:05.748 INFO bosminer_plus_tuner::tune: Tune/all: Starting miner
Mon Oct 10 20:37:05 2022 daemon.err bosminer[1603]: Oct 10 20:37:05.748 INFO bosminer_plus_tuner::tune::experiment: Tune/all: Status: starting chain
Mon Oct 10 20:37:05 2022 daemon.err bosminer[1603]: Oct 10 20:37:05.749 INFO bosminer_plus_tuner::tune::experiment: Waiting 0 s for miner to stabilize...
Mon Oct 10 20:37:05 2022 daemon.err bosminer[1603]: Oct 10 20:37:05.751 INFO bosminer_plus_tuner::tune::experiment: Woken up
Mon Oct 10 20:37:05 2022 daemon.err bosminer[1603]: Oct 10 20:37:05.753 INFO bosminer_antminer::io: Hashboard 1: bm13xx 1.0.2 for Antminer S9 or higher built on 2020-12-04 14:49:18 UTC
Mon Oct 10 20:37:05 2022 daemon.err bosminer[1603]: Oct 10 20:37:05.758 INFO bosminer_am2_s17::power::antminer: PWR/1: Voltage controller reset
Mon Oct 10 20:37:05 2022 daemon.err bosminer[1603]: Oct 10 20:37:05.761 INFO bosminer_antminer::io: Hashboard 2: bm13xx 1.0.2 for Antminer S9 or higher built on 2020-12-04 14:49:18 UTC
Mon Oct 10 20:37:05 2022 daemon.err bosminer[1603]: Oct 10 20:37:05.766 INFO bosminer_am2_s17::power::antminer: PWR/2: Voltage controller reset
Mon Oct 10 20:37:05 2022 daemon.err bosminer[1603]: Oct 10 20:37:05.771 INFO bosminer_antminer::io: Hashboard 3: bm13xx 1.0.2 for Antminer S9 or higher built on 2020-12-04 14:49:18 UTC
Mon Oct 10 20:37:05 2022 daemon.err bosminer[1603]: Oct 10 20:37:05.776 INFO bosminer_am2_s17::power::antminer: PWR/3: Voltage controller reset
Mon Oct 10 20:37:07 2022 daemon.err bosminer[1603]: Oct 10 20:37:07.362 INFO bosminer_am2_s17::power::antminer: PWR/1: Voltage controller application started
Mon Oct 10 20:37:07 2022 daemon.err bosminer[1603]: Oct 10 20:37:07.373 INFO bosminer_am2_s17::power::antminer: PWR/2: Voltage controller application started
Mon Oct 10 20:37:07 2022 daemon.err bosminer[1603]: Oct 10 20:37:07.408 INFO bosminer_am2_s17::power::antminer: PWR/3: Voltage controller application started
Mon Oct 10 20:37:07 2022 daemon.err bosminer[1603]: Oct 10 20:37:07.516 INFO bosminer_am2_s17::power::antminer: PWR/1: Voltage controller firmware version 0x88
Mon Oct 10 20:37:07 2022 daemon.err bosminer[1603]: Oct 10 20:37:07.516 INFO bosminer_backend::hashchain: CHAIN/1: Initializing (fingerprint: 40521e9e835407af, difficulty: 4)
Mon Oct 10 20:37:07 2022 daemon.err bosminer[1603]: Oct 10 20:37:07.516 INFO bosminer_backend::hashchain: CHAIN/1: Resetting hash board
Mon Oct 10 20:37:07 2022 daemon.err bosminer[1603]: Oct 10 20:37:07.578 INFO bosminer_am2_s17::power::antminer: PWR/2: Voltage controller firmware version 0x88
Mon Oct 10 20:37:07 2022 daemon.err bosminer[1603]: Oct 10 20:37:07.578 INFO bosminer_backend::hashchain: CHAIN/2: Initializing (fingerprint: 30924e3d99f4a05f, difficulty: 4)
Mon Oct 10 20:37:07 2022 daemon.err bosminer[1603]: Oct 10 20:37:07.578 INFO bosminer_backend::hashchain: CHAIN/2: Resetting hash board
Mon Oct 10 20:37:07 2022 daemon.err bosminer[1603]: Oct 10 20:37:07.652 INFO bosminer_am2_s17::power::antminer: PWR/3: Voltage controller firmware version 0x88
Mon Oct 10 20:37:07 2022 daemon.err bosminer[1603]: Oct 10 20:37:07.652 INFO bosminer_backend::hashchain: CHAIN/3: Initializing (fingerprint: 780c6c0773bd3ed9, difficulty: 4)
Mon Oct 10 20:37:07 2022 daemon.err bosminer[1603]: Oct 10 20:37:07.652 INFO bosminer_backend::hashchain: CHAIN/3: Resetting hash board
Mon Oct 10 20:37:08 2022 daemon.err bosminer[1603]: Oct 10 20:37:08.661 INFO bosminer_am2_s17::power::antminer: PWR/1: Enable voltage
Mon Oct 10 20:37:08 2022 daemon.err bosminer[1603]: Oct 10 20:37:08.910 INFO bosminer_antminer::io: CHAIN/1: Setting IP core baud rate @ requested: 115200, actual: 114679, divisor 0x6c
Mon Oct 10 20:37:09 2022 daemon.err bosminer[1603]: Oct 10 20:37:09.058 INFO bosminer_am2_s17::power::antminer: PWR/2: Enable voltage
Mon Oct 10 20:37:09 2022 daemon.err bosminer[1603]: Oct 10 20:37:09.311 INFO bosminer_antminer::io: CHAIN/2: Setting IP core baud rate @ requested: 115200, actual: 114679, divisor 0x6c
Mon Oct 10 20:37:09 2022 daemon.err bosminer[1603]: Oct 10 20:37:09.459 INFO bosminer_am2_s17::power::antminer: PWR/3: Enable voltage
Mon Oct 10 20:37:09 2022 daemon.err bosminer[1603]: Oct 10 20:37:09.710 INFO bosminer_am2_s17::power::antminer: PWR/3: Waiting for voltage to settle (measured 0.98 V, expected 19.25 V)
Mon Oct 10 20:37:09 2022 daemon.err bosminer[1603]: Oct 10 20:37:09.710 INFO bosminer_am2_s17::power::antminer: PWR/3: Disable voltage
Mon Oct 10 20:37:09 2022 daemon.err bosminer[1603]: Oct 10 20:37:09.813 ERROR bosminer_backend::hashchain: CHAIN/3: Init failed: SHORT CIRCUIT - measured voltage 0.98 V
Mon Oct 10 20:37:09 2022 daemon.info boser[1587]: Oct 10 20:37:09.897 INFO actix_web::middleware::logger: 192.168.1.999:54091 GET /cgi-bin/luci/admin/status/syslog HTTP/1.1 200 99235 - 0.796723
Mon Oct 10 20:37:09 2022 daemon.err bosminer[1603]: Oct 10 20:37:09.911 INFO bosminer_backend::hashchain: CHAIN/1: Initializing hashchain
Mon Oct 10 20:37:10 2022 daemon.err bosminer[1603]: Oct 10 20:37:10.012 INFO bosminer_am2_s17::hashchain: CHAIN/1: Discovered 0 chips (expected 44 chips)
Mon Oct 10 20:37:10 2022 daemon.err bosminer[1603]: Oct 10 20:37:10.012 ERROR bosminer_backend::hashchain: CHAIN/1: Init failed: no chips detected on the current chain
Mon Oct 10 20:37:10 2022 daemon.err bosminer[1603]: Oct 10 20:37:10.014 INFO bosminer_am2_s17::power::antminer: PWR/3: Disable voltage
Mon Oct 10 20:37:10 2022 daemon.err bosminer[1603]: Oct 10 20:37:10.215 INFO bosminer_am2_s17::power::antminer: PWR/1: Disable voltage
Mon Oct 10 20:37:10 2022 daemon.err bosminer[1603]: Oct 10 20:37:10.313 INFO bosminer_backend::hashchain: CHAIN/2: Initializing hashchain
Mon Oct 10 20:37:10 2022 daemon.err bosminer[1603]: Oct 10 20:37:10.414 INFO bosminer_am2_s17::hashchain: CHAIN/2: Discovered 0 chips (expected 44 chips)
Mon Oct 10 20:37:10 2022 daemon.err bosminer[1603]: Oct 10 20:37:10.414 ERROR bosminer_backend::hashchain: CHAIN/2: Init failed: no chips detected on the current chain
Mon Oct 10 20:37:10 2022 daemon.err bosminer[1603]: Oct 10 20:37:10.615 INFO bosminer_am2_s17::power::antminer: PWR/2: Disable voltage
Mon Oct 10 20:37:11 2022 daemon.err bosminer[1603]: Oct 10 20:37:11.117 ERROR bosminer_backend::miner: CHAIN/3: Start failed: Other(SHORT CIRCUIT - measured voltage 0.98 V)
Mon Oct 10 20:37:11 2022 daemon.err bosminer[1603]: Oct 10 20:37:11.315 ERROR bosminer_backend::miner: CHAIN/1: Start failed: NoChipsDetected
Mon Oct 10 20:37:11 2022 daemon.err bosminer[1603]: Oct 10 20:37:11.717 ERROR bosminer_backend::miner: CHAIN/2: Start failed: NoChipsDetected
Title: Re: T17+ doesn`t start mining!
Post by: BitMaxz on October 10, 2022, 09:22:27 PM
You might be downloaded the wrong image for the sd card flashing you can download it on bitmains download page on the drop-down list under other>flashing sd card image.
If you can't flash it back to stock firmware then bring this issue here https://bitcointalk.org/index.php?topic=5412808.0 :)
Title: Re: S17 PRO- doesn`t start mining!
Post by: mikeywith on October 10, 2022, 09:36:01 PM
I downloaded the stock firmware for sd card from bitmains website and copy it to the sd card, put the sd card in the miner and started it up. But it doesn`t change it back to stock firmware. Yes, the sd card I format to fat32.
Did you follow every step mentioned on Bitmain's website? I also recall Braiins has a tool that you run in CMD to remove their firmware without having to use a Sdcard. But anyway, it seems like you are posting the wrong logs, while it does say Kernel log, it looks more like system logs, the terms kernel/system/miner logs are used in different ways on different firmware versions, I think the one you need to copy is called "Miner Logs". Edit: I was about to post the above then saw that you just posted a new log, which is the correct one, so what do we have ? Mon Oct 10 20:37:09 2022 daemon.err bosminer[1603]: Oct 10 20:37:09.813 ERROR bosminer_backend::hashchain: CHAIN/3: Init failed: SHORT CIRCUIT - measured voltage 0.98 V
Mon Oct 10 20:37:10 2022 daemon.err bosminer[1603]: Oct 10 20:37:10.012 INFO bosminer_am2_s17::hashchain: CHAIN/1: Discovered 0 chips (expected 44 chips)
Mon Oct 10 20:37:10 2022 daemon.err bosminer[1603]: Oct 10 20:37:10.414 INFO bosminer_am2_s17::hashchain: CHAIN/2: Discovered 0 chips (expected 44 chips) At this point, I would stop attempting the firmware change as I don't think the results will be different, it seems like you have a bad PSU at this point, you also mentioned about a "new place" so I suspect some damage happened to the PSU or the connectors, I would double check every screw on the PSU's busbar as well as all connectors.
Title: Re: T17+ doesn`t start mining!
Post by: kungen12321 on October 10, 2022, 10:00:55 PM
Thanks, in that case I will stop trying to change back to stock firmware.
The whole story is that I had this T17+ miner in a location. It stoped hashing so I bought a new but used S17 pro miner and put it in the same location, worked some day but then it also stop hashing. Both system and kernel logs are identical.
Very strange but maybe just a coincidence?
Is there anything else I should check before buying 2 new psu?
Title: Re: T17+ doesn`t start mining!
Post by: kungen12321 on October 10, 2022, 10:07:53 PM
Is there any change that I could use psu for s9:or to each of these two miners?
I have many of these just laying around, maybe two for each miner?
Want to use around 2400w, this feautre is possible in the braiin firmware.
Title: Re: T17+ doesn`t start mining!
Post by: BitMaxz on October 10, 2022, 11:44:46 PM
According to the logs pointed by mickeywith, it shows a short circuit it could be PSU but it's pointed to chain #3.
Would you mind to try remove the hashboard the one with short circuit?
It might solve your case but only two hashboard will work.
Title: Re: T17+ doesn`t start mining!
Post by: kungen12321 on October 11, 2022, 05:24:01 AM
Thanks, I will disconnect hashboard 3 and let you know about the result.
Title: Re: T17+ doesn`t start mining!
Post by: MinerMEDIC on October 11, 2022, 03:07:34 PM
There is only ONE way to remove braiins and that is with their downloadable toolbox, Which conveniently enough also restores the factory image in one step. I hope you don’t Disconnect dashboard three but remove it completely.
Title: Re: T17+ doesn`t start mining!
Post by: kungen12321 on October 11, 2022, 03:29:19 PM
There is only ONE way to remove braiins and that is with their downloadable toolbox, Which conveniently enough also restores the factory image in one step. I hope you don’t Disconnect dashboard three but remove it completely.
That explain why it didn`t work for me to flash back to stock firmware. Do you have a link for the toolbox, easy to use?
Title: Re: T17+ doesn`t start mining!
Post by: NotFuzzyWarm on October 11, 2022, 03:29:22 PM
@OP Is there any change that I could use psu for s9:or to each of these two miners?
You cannot do that. All modern miners are using integrated PSU's which are directly controlling the Vcore level supplied to establish the string voltage that the chips need. The PSU output is set by the control board and can vary quite a bit depending how you have the miner setup. Older miners like the s9 used a 2nd stage regulator located on each hash board to take the incoming 12vdc and step it down to the Vcore level they wanted. Losing that 2nd regulator stage is just one reason modern miners are more efficient.
Title: Re: T17+ doesn`t start mining!
Post by: kungen12321 on October 11, 2022, 04:22:03 PM
http://Thanks for the explanation, helped alot about the psu. Now I have taking away one hashboard at the time and started it up, but still it doesn`t start to hash. See pictures. I open the psu and I could smell "burned electric", see picture of the burned white plastic ring. Something easy to repair? I guess the problem is the psu and not any of the hashboards? https://www.bildtagg.se/bild/zotwowofubjm076ynzp6m5g2 https://www.bildtagg.se/bild/zotwowofubjm076ynzp6m5g2 https://www.bildtagg.se/bild/bpwpqpjxta4fpi5x0wolwujd https://www.bildtagg.se/bild/6m79o0gyao4v6elsz9o08rqv https://www.bildtagg.se/bild/1ci75n79rd4u0x1de53wleg https://www.bildtagg.se/bild/gnem3b21kutdz9eajra1eka
Title: Re: T17+ doesn`t start mining!
Post by: kungen12321 on October 11, 2022, 04:33:07 PM
Sorry that I couldn`t figure out how to upload pictures correct in the thread.
Title: Re: T17+ doesn`t start mining!
Post by: BitMaxz on October 11, 2022, 11:53:34 PM
Sorry that I couldn`t figure out how to upload pictures correct in the thread.
Just put the link instead newbies do not allow yet to post images here except the link of the image. I don't get it the image shows it's running with a hash rate of 4 to 6gh/s so it's hashing but it is still low. You can try to check the auto-tuning settings and try to lower the power according to Braiins it needs 2 to 6hrs to complete. The tuning takes between 2-6 hours to complete, depending on the power limit specified and the quality of the chips in your device. About the PSU it is not clear if it's a bridge rectifier or inductor or it might be just burnt wire. What is your current outlet power? 110v or 220v? These won't run normally in 110v.
Title: Re: T17+ doesn`t start mining!
Post by: kungen12321 on October 12, 2022, 06:23:39 AM
I have tried to lower the power with the auto setting, to around 1800w. But no improvement.
My outlet power 220v.
Title: Re: T17+ doesn`t start mining!
Post by: kungen12321 on October 12, 2022, 06:40:16 PM
I decided to take a PSU from another server. I started it up and now the server is runing as it should. I am sooo happy!
Is it possible to repair the PSU by myself? Is there any guide how to measure up parts, to know what is broken?
Or is there a specific part with this kind of PSU that always get broken?
Thanks in advance!
Title: Re: T17+ doesn`t start mining!
Post by: BitMaxz on October 12, 2022, 10:21:53 PM
Is it possible to repair the PSU by myself? Is there any guide how to measure up parts, to know what is broken?
Or is there a specific part with this kind of PSU that always get broken?
Yes, you can repair it if you have the tools and knowledge but if you don't have experience then better hire a technician zeusbtc have a list of repair center maybe one of them is near in your area. Or if you don't have a budget but have tools and you want to repair it then you can use the repair guide here below. - https://www.zeusbtc.com/manuals/Antminer-APW9-plus-power-supply-repair-guide.asp
Title: Re: T17+ doesn`t start mining!
Post by: NotFuzzyWarm on October 12, 2022, 10:50:12 PM
Or is there a specific part with this kind of PSU that always get broken? I've been very curious about this also, not just Bitmain PSU's but also the ones made for Canaan and microBT. These things are not that complex and are fairly easy to design to be bulletproof. Even cutting cost to a bare minimum is no excuse for the PSU's failing so often. Being more than a little familiar with multi-kw PSU design <cough> my gut feeling is that the problem area is the power-factor correction circuits... More specifically, the MOSFET Q4, the 3 diodes around it and the inductor used in the circuit shown in that repair guide. Anyone ever have one of these repaired and gotten a report on what problem was and repair work done?
Title: Re: T17+ doesn`t start mining!
Post by: kungen12321 on October 13, 2022, 06:23:11 AM
Thanks for the link and the explanations. I will study and see if I will order spare parts or just buy new PSU.
Title: Re: T17+ doesn`t start mining!
Post by: kungen12321 on October 27, 2022, 03:48:35 PM
I bought a new PSU, now it works like it should:)
|