Ok too much information in this thread which I find hard to follow, it would have been easier if you put all the info (summarised version of your issue) in one post, so tell me if this is correct:
You have a few Antminers of different models all running stock firmware and pointed to slush pool aka Braiins Pool, some of these miners are working fine right now, and some are not.
If that is correct, then you need to point the non-working miners to a different mining pool to ensure this is isn't a pool related issue, don't just take their words for it, if their logs are not showing any errors and they can't reproduce the error -- they will always tell you (nothing is wrong on our side), this is true for ALL other pools and services, so assuming that there is nothing wrong with their pool is a naive mistake, they could have had an update to their pool software which somehow screwed things up.
Different miners use different firmware, and thus it's perfectly normal for miner "A" to work fine on pool "Y" while miner "B" does not, so long story short, point them to a different pool and report your results.
Ok, so here is the complete history: 0) I have rebuild some S17pro, S17+ and S17e miners from spare parts and run them for testing reasons to sell them afterwards. I want to sell them with stock FW, most recent versions. 1) On the site, S19 and S17 miners mine to Braiins. 2) S17 pro models stopped all together one day while all others worked. 3) S17e and S17+ stopped working, S19 still hashing well. 4) All S17 models drew power and the share cound went up, but they produced 0 hash because all shares were discarded. 5) Tried reboot and reset and reflash withot success. 6) Tried different servers and braiins /slushpool adresses without success. 7) Checked the network, changed DNS, tried a mobile router. No success.  Braiins OS worked on Braiins, also with the V1 stratum servers. 9) Tried different pools, stopped at Luxor because there the stock FW runs fine. I have no idea what the problem is. |
|
|
|
The S17+ also stopped working. The strange thing is, that I can not find anything about this anywhere. Does nobody use the stock fw on S17 anymore? |
|
|
|
|
Braiins says there is no problem.
In the meantime, all S17, also the S17e are not able to mine. They produce only discarded shares.
Any other ideas?
|
|
|
|
If other pools works fine then the issue is the Braiins pool.
Have you set up your all s17 in static mode?
If not try to set them into static mode and make sure to add Cloudflare or Google DNS.
If it's already set up in static mode but it's not hashing try to set them all to DHCP mode.
If it still does not work then you don't have other choice but to mine in other pools.
Changing to static did not help. It makes no sense. Why only the S17 pro? Why not S19 or S17e? There must be something wrong. They worked before... |
|
|
|
What do you mean "produce deiscarded"?
Are you talking about rejected shares? Or are you talking about flashing it to stock firmware but rejected? Because Braiins is not a stock firmware of Bitmain.
If you talking about rejected shares can you share your miner's logs here so that we can analyze the issue?
The reason might be overheating which causes a high rejection rate.
Sometimes high rejected shares is due to high ping or due to other hardware issue.
You can try to reduce the power limit on the Braiins dashboard and then update here if it fixes your issue.
Let me rephrase and add infos, I wrote it not clear enough: I run S17 on stock firmware mining to Braiins pool. For some reason, all the S17 models, but not the S17e, stopped hashing and show 0 hash. All work shows as "discarded" in the miner status. The kernel log is fine. I will attach it below. The miner stopped hashing some days ago. Every other model I own works fine. I tried reflashing the firmware and also tried different stratum servers. Some other ppl I talked to had the same problem. Other pools seem to work.
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: 203608K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25768K 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: 12728K (cce93000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 58/24, 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): 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: 2585/625, 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): 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
alloc_contig_range: [e043, e044) PFNs busy
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
alloc_contig_range: [e043, e044) PFNs busy
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
Oct 1 10:19:47 (none) local0.notice bmminer: set_start_time_point total_tv_start_sys=299 total_tv_end_sys=300
Oct 1 10:19:49 (none) local0.notice cgminer: cgminer_socket_init reg bitmain_api_detect return: 0
Oct 1 10:19:49 (none) local0.notice cgminer: cgminer_socket_init reg bitmain_update_job return: 0
Oct 1 10:19:50 (none) local0.notice cgminer: cgminer_socket_init reg bitmain_shutdown return: 0
Oct 1 10:19:50 (none) local0.err cgminer: Miner compile time: Mon Apr 27 13:25:08 CST 2020 type: Antminer X17
Oct 1 10:19:50 (none) local0.notice cgminer[996]: about to send detect
Oct 1 10:19:50 (none) local0.notice cgminer[996]: set_start_time_point total_tv_start_sys=302 total_tv_end_sys=303
Oct 1 10:19:50 (none) local0.notice cgminer[996]: Probing for an alive pool
Oct 1 10:19:50 (none) local0.warn cgminer[996]: No Stratum, GBT or Solo support in pool 2 unable to use
Oct 1 10:19:50 (none) local0.warn cgminer[996]: No Stratum, GBT or Solo support in pool 1 unable to use
Oct 1 10:19:50 (none) local0.notice cgminer[996]: LOW POWER MODE!
Oct 1 10:19:50 (none) local0.notice cgminer[996]: in stratum_sthread
Oct 1 10:19:50 (none) local0.notice cgminer[996]: Rejected untracked stratum share from pool 0
Oct 1 10:19:52 (none) local0.notice cgminer[996]: Pool 0 difficulty changed to 8192
Oct 1 10:19:52 (none) local0.notice cgminer[996]: Network diff set to 57.1T
Oct 1 10:19:52 (none) local0.notice cgminer[996]: update job
Oct 1 10:19:52 (none) local0.notice cgminer[996]: job buf total len:2554, offset:2554
Oct 1 10:19:52 (none) local0.notice cgminer[996]: about to send job, size is 2554
Oct 1 10:19:52 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000628 size: 2554
Oct 1 10:19:52 (none) local0.notice bmminer: parse job buf len:2554
Oct 1 10:19:53 (none) local0.notice cgminer[996]: update job
Oct 1 10:19:53 (none) local0.notice cgminer[996]: job buf total len:2522, offset:2522
Oct 1 10:19:53 (none) local0.notice cgminer[996]: about to send job, size is 2522
Oct 1 10:19:53 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000628 size: 2522
Oct 1 10:19:53 (none) local0.notice bmminer: parse job buf len:2522
Oct 1 10:19:55 (none) local0.notice cgminer[996]: Stratum from pool 0 requested work restart
Oct 1 10:19:55 (none) local0.notice cgminer[996]: update job
Oct 1 10:19:55 (none) local0.notice cgminer[996]: job buf total len:2554, offset:2554
Oct 1 10:19:55 (none) local0.notice cgminer[996]: about to send job, size is 2554
Oct 1 10:19:55 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000628 size: 2554
Oct 1 10:19:55 (none) local0.notice bmminer: parse job buf len:2554
Oct 1 10:19:56 (none) local0.warn cgminer[996]: API running in IP access mode on port 4028 (15)
Oct 1 10:19:59 (none) local0.notice cgminer[996]: update job
Oct 1 10:19:59 (none) local0.notice cgminer[996]: job buf total len:2522, offset:2522
Oct 1 10:19:59 (none) local0.notice cgminer[996]: about to send job, size is 2522
Oct 1 10:19:59 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000628 size: 2522
Oct 1 10:19:59 (none) local0.notice bmminer: parse job buf len:2522
2023-10-01 10:15:39 driver-btm-api.c:542:init_freq_mode: This is scan-user version
2023-10-01 10:15:39 driver-btm-api.c:1877:bitmain_soc_init: opt_multi_version = 1
2023-10-01 10:15:39 driver-btm-api.c:1878:bitmain_soc_init: opt_bitmain_ab = 1
2023-10-01 10:15:39 driver-btm-api.c:1879:bitmain_soc_init: opt_bitmain_work_mode = 2
2023-10-01 10:15:39 driver-btm-api.c:1880:bitmain_soc_init: Miner compile time: Mon Apr 27 13:25:08 CST 2020 type: Antminer S17
2023-10-01 10:15:39 driver-btm-api.c:1881:bitmain_soc_init: commit version: d22f356 2020-04-24 18:30:49, build by: lol 2020-04-27 13:31:45
2023-10-01 10:15:39 driver-btm-api.c:1691:show_sn: no SN got, please write SN to /nvdata/sn
2023-10-01 10:15:39 driver-btm-api.c:1040:miner_device_init: Detect 256MB control board of XILINX
2023-10-01 10:15:39 driver-btm-api.c:988:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2023-10-01 10:15:39 thread.c:783:create_read_nonce_reg_thread: create thread
2023-10-01 10:15:45 driver-btm-api.c:972:init_miner_version: miner ID : 8108f5ca79104814
2023-10-01 10:15:45 driver-btm-api.c:978:init_miner_version: FPGA Version = 0xB013
2023-10-01 10:15:47 Cgminer CRC check fail.
2023-10-01 10:15:51 Cgminer CRC check fail.
2023-10-01 10:15:51 driver-btm-api.c:616:get_product_id: product_id[0] = 0
2023-10-01 10:15:51 driver-btm-api.c:616:get_product_id: product_id[1] = 0
2023-10-01 10:15:51 driver-btm-api.c:616:get_product_id: product_id[2] = 0
2023-10-01 10:15:51 Cgminer crc check is not pass.
2023-10-01 10:15:51 Cgminer crc check is not pass.
2023-10-01 10:15:51 Project type is X17.
2023-10-01 10:15:51 driver-btm-api.c:560:_set_project_type: project:2
2023-10-01 10:15:51 driver-btm-api.c:585:_set_project_type: Project type: Antminer X17
2023-10-01 10:15:51 driver-btm-api.c:596:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2023-10-01 10:15:51 driver-btm-api.c:597:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2023-10-01 10:15:51 driver-btm-api.c:596:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2023-10-01 10:15:51 driver-btm-api.c:597:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2023-10-01 10:15:51 driver-btm-api.c:596:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2023-10-01 10:15:51 driver-btm-api.c:597:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2023-10-01 10:15:55 driver-btm-api.c:1802:bitmain_board_init: Fan check passed.
2023-10-01 10:15:56 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2023-10-01 10:15:58 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2023-10-01 10:15:59 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2023-10-01 10:16:01 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2023-10-01 10:16:02 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2023-10-01 10:16:04 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2023-10-01 10:16:04 thread.c:778:create_pic_heart_beat_thread: create thread
2023-10-01 10:16:04 power_api.c:207:power_init: Power init:
2023-10-01 10:16:04 power_api.c:208:power_init: current_voltage_raw = 0
2023-10-01 10:16:04 power_api.c:209:power_init: highest_voltage_raw = 2100
2023-10-01 10:16:04 power_api.c:210:power_init: working_voltage_raw = 1830
2023-10-01 10:16:04 power_api.c:211:power_init: higher_voltage_raw = 1950
2023-10-01 10:16:04 driver-btm-api.c:1812:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2023-10-01 10:16:04 power_api.c:181:power_off: init gpio907
2023-10-01 10:16:36 power_api.c:251:set_to_highest_voltage: Set to voltage raw 2100, one step.
2023-10-01 10:16:38 power_api.c:87:check_voltage_multi: retry time: 0
2023-10-01 10:16:39 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 21.289834
2023-10-01 10:16:40 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.369433
2023-10-01 10:16:41 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 21.308203
2023-10-01 10:16:41 power_api.c:50:_get_avg_voltage: average_voltage = 21.322490
2023-10-01 10:16:41 power_api.c:68:check_voltage: target_vol = 21.00, actural_vol = 21.32, check voltage passed.
2023-10-01 10:16:41 uart.c:71:set_baud: set fpga_baud to 115200
2023-10-01 10:16:53 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
2023-10-01 10:17:04 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2023-10-01 10:17:15 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2023-10-01 10:17:20 driver-btm-api.c:345:set_order_clock: chain[0]: set order clock, stragegy 3
2023-10-01 10:17:20 driver-btm-api.c:345:set_order_clock: chain[1]: set order clock, stragegy 3
2023-10-01 10:17:20 driver-btm-api.c:345:set_order_clock: chain[2]: set order clock, stragegy 3
2023-10-01 10:17:20 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2023-10-01 10:17:20 uart.c:71:set_baud: set fpga_baud to 3000000
2023-10-01 10:17:20 driver-btm-api.c:1574:check_clock_counter: freq 50 clock_counter_limit 6
2023-10-01 10:17:22 uart.c:71:set_baud: set fpga_baud to 115200
2023-10-01 10:17:22 voltage[0] = 1830
2023-10-01 10:17:22 voltage[1] = 1830
2023-10-01 10:17:22 voltage[2] = 1830
2023-10-01 10:17:22 power_api.c:219:set_working_voltage_raw: working_voltage_raw = 1830
2023-10-01 10:17:24 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2023-10-01 10:17:25 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2023-10-01 10:17:26 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2023-10-01 10:17:27 uart.c:71:set_baud: set fpga_baud to 6000000
2023-10-01 10:17:28 driver-btm-api.c:245:check_bringup_temp: Bring up temperature is 31
2023-10-01 10:17:28 thread.c:798:create_check_miner_status_thread: create thread
2023-10-01 10:17:28 thread.c:788:create_set_miner_status_thread: create thread
2023-10-01 10:17:28 thread.c:773:create_temperature_monitor_thread: create thread
2023-10-01 10:17:28 frequency.c:749:inc_freq_with_fixed_vco: chain = 255, freq = 565, is_higher_voltage = true
2023-10-01 10:17:28 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 2020, step by step.
2023-10-01 10:17:47 power_api.c:87:check_voltage_multi: retry time: 0
2023-10-01 10:17:48 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 20.469345
2023-10-01 10:17:49 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 20.555068
2023-10-01 10:17:50 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 20.481592
2023-10-01 10:17:50 power_api.c:50:_get_avg_voltage: average_voltage = 20.502002
2023-10-01 10:17:50 power_api.c:68:check_voltage: target_vol = 20.20, actural_vol = 20.50, check voltage passed.
2023-10-01 10:18:20 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1880, step by step.
2023-10-01 10:18:40 power_api.c:87:check_voltage_multi: retry time: 0
2023-10-01 10:18:41 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 19.067168
2023-10-01 10:18:42 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 19.220244
2023-10-01 10:18:43 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 19.073291
2023-10-01 10:18:43 power_api.c:50:_get_avg_voltage: average_voltage = 19.120234
2023-10-01 10:18:43 power_api.c:68:check_voltage: target_vol = 18.80, actural_vol = 19.12, check voltage passed.
2023-10-01 10:18:49 frequency.c:801:inc_freq_with_fixed_step: chain = 1, freq_start = 565, freq_end = 595, freq_step = 5, is_higher_voltage = true
2023-10-01 10:18:52 frequency.c:801:inc_freq_with_fixed_step: chain = 2, freq_start = 565, freq_end = 595, freq_step = 5, is_higher_voltage = true
2023-10-01 10:18:55 frequency.c:801:inc_freq_with_fixed_step: chain = 1, freq_start = 595, freq_end = 595, freq_step = 5, is_higher_voltage = true
2023-10-01 10:18:55 frequency.c:801:inc_freq_with_fixed_step: chain = 2, freq_start = 595, freq_end = 595, freq_step = 5, is_higher_voltage = true
2023-10-01 10:18:55 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1830, step by step.
2023-10-01 10:19:11 power_api.c:87:check_voltage_multi: retry time: 0
2023-10-01 10:19:12 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 18.540586
2023-10-01 10:19:13 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 18.718154
2023-10-01 10:19:14 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 18.546709
2023-10-01 10:19:14 power_api.c:50:_get_avg_voltage: average_voltage = 18.601816
2023-10-01 10:19:14 power_api.c:68:check_voltage: target_vol = 18.30, actural_vol = 18.60, check voltage passed.
2023-10-01 10:19:14 frequency.c:618:inc_asic_diff_freq_by_steps: chain = 0, start = 565, freq_step = 5
2023-10-01 10:19:15 frequency.c:618:inc_asic_diff_freq_by_steps: chain = 1, start = 595, freq_step = 5
2023-10-01 10:19:18 frequency.c:618:inc_asic_diff_freq_by_steps: chain = 2, start = 595, freq_step = 5
2023-10-01 10:19:22 driver-btm-api.c:528:set_timeout: freq = 625, percent = 90, hcn = 73728, timeout = 117
2023-10-01 10:19:22 power_api.c:269:set_to_working_voltage_by_steps: Set to voltage raw 1830, step by step.
2023-10-01 10:19:38 power_api.c:87:check_voltage_multi: retry time: 0
2023-10-01 10:19:39 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 18.565078
2023-10-01 10:19:40 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 18.705908
2023-10-01 10:19:41 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 18.534463
2023-10-01 10:19:41 power_api.c:50:_get_avg_voltage: average_voltage = 18.601816
2023-10-01 10:19:41 power_api.c:68:check_voltage: target_vol = 18.30, actural_vol = 18.60, check voltage passed.
2023-10-01 10:19:41 thread.c:793:create_check_system_status_thread: create thread
2023-10-01 10:19:41 driver-btm-api.c:1988:bitmain_soc_init: Init done!
2023-10-01 10:19:41 driver-btm-api.c:198:set_miner_status: STATUS_INIT
2023-10-01 10:19:47 driver-btm-api.c:198:set_miner_status: STATUS_OKAY
2023-10-01 10:19:48 frequency.c:216:get_ideal_hash_rate_GH: ideal_hash_rate = 56083
2023-10-01 10:19:48 frequency.c:236:get_sale_hash_rate_GH: sale_hash_rate = 56000
2023-10-01 10:19:52 driver-btm-api.c:1199:dhash_chip_send_job: Version num 1
|
|
|
|
|
Hi,
some of my S17 suddenly only produce deiscarded shares on braiins. I tried different servers, I reflashed, nothing helped. The miners work fine.
Is there a bug on the Braiins side? Every other miner runs fine, even the S17e.
|
|
|
|
|
If you have the stock heatsinks, i would keep them below 85°C. You will risk the heatsinks and or chips falling off.
|
|
|
|
[...]
When you say if you switch them off locally, I was under the impression they didn’t have an on/off switch, you just unplugged them? So would a load shedding breaker tripping be a safe off method for a miner?
They do not have switches on them. Regarding the switch, I can not tell you. As long as there is no sudden peak in current to the miners it should be fine. |
|
|
|
To switch the miner on and of regularly does not affect it at all. I have miners that are used as heaters and they are turned on and of several times per day. Also rental miners turn on and Off, depending if they are rented or not.
The humidity could be more of an issue, but from what I have heard bitcoin miners are operated in every climate zone of the world and often even in warehouses/shipping containers where there is also a high humidity.
This is what I was thinking when I saw the news about variable load grids and bitcoin miners being shut down to help manage power, surely it can't damage them too much otherwise no one would be putting there miners at risk for this? If you switch them off locally, it is not a problem. Damages are possible, when they cut power on the whole line. Or on a general blackout. |
|
|
|
[...]
The miner will have free solar + very cheap grid electricity but regular power cuts, so I was wondering if anyone had experience with the miner switching off at least once per day for a few hours. The environment will also be quite high humidity. Will this make my project completely unfeasible, or can Antminers handle this?
[...]
It is not that simple: For the longevity of the miner, it is better to have it shut down when it is cooled a bit. For that, the fans should run while the hashboards stop mining. You can use the "Sleep" or "Standby" mode on some miners. Although everyone will tell you, it does not matter - and they are right in general. Physically you will do your miners good, I can not tell you how big of a factor it is. I have experience in regular blackouts. You need to make sure that the miners do not get overcurrent. In my area sometimes the power goes on and off several times in seconds before it comes back. That fried several miner until I installed a switch, that keeps them off until you physically turn them on again, once the energy is safe again. So the message for you here should be, that you make sure your miners only get "good" power. Humidity is a problem, but it is more of a problem, when your ambient is cold and it condensates. I often have high humidity, but if the miners run and are hot and the ambient inside the room or chamber or whereever they are is hot, it should not be a problem. In your case, if you have them run with solar and they turn off in the evening, it might get cold over night and there might be condesate in your miners in the morning, if your ambient is too low. You can prevent this by having e.g. a miner run permanently to heat the ambient a bit. I would install a humidity sensor to check, so you can find a good solution for this. Regarding the heatsinks: I am courious, too. I have S19XP incoming. |
|
|
|
|
I am wondering why I can not find any comparison between this and other custom FW.
|
|
|
|
|
Can we somehow get absolute core clock setting for NVIDIA?
|
|
|
|
Hi, so I found a possible solution for the said problem. ProblemGigabyte Fintech 12 GPU B250 mining mainboard does not boot / post after connecting more than 9 GPUs. It does not depend on which PCIe slots you use, just disconnecting any card helps, as long as there are no more than 9 connected. Intro.. As stated, if the problem solves by disconnecting any of the cards so that there are only 9 connected, you can quickly check if you have that specific problem. There is still a possibility, that your PSU is the problem, especially, if you built a new rig and boot up for the first time. Maybe your rig just draws too much power. .. It still might be a riser, although you ruled that one nearly out by confirming it is not related to specific GPUs. .. Might still be a defective component on the board. Steps done before in no particular order, that were not related to the solution and did not solve the problem.. Switched RAM and CPU .. Switched RAM slots .. Loaded defaults in BIOS .. Reflashed recent BIOS .. Flashed old v3 BIOS .. Checked every setting and deactivated all unneccessary devices .. Mining mode is enabled, 4G decodeing is enabled, primary video device is integrated GPU etc... SolutionThere seems to be a problem with some boards and also with the new 4a BIOS version. In one case it helped to just flash back version 3, but in another case, that did not help. The solution was to flash all BIOS versions from the beginning in the right order. You need to download all the files from Gigabyte and just put the BIOS files on a USB stick in order to use the on board flash tool EZ Flash from within the BIOS. Important: Make sure to always chose the "full" upgrade of the BIOS, if given a choice by EZ flash! So I started with 9 cards connected because I was lazy and did not want to disconnect every card. Flashed F1, then rebooted into OS, shut down. Flash F2b. F2b for some reason did not boot at all with GPUs attached. So I needed to disconnect all cards to have it boot into OS. Shut down. Flash F3. At this point your board should work fine with 12 cards again with the right settings. Do not flash F4a! This will bring back the problem. For science I did. If you do not mess up with a lot of things, flashing back to F3 fixes this again at this point. ConclusionSeems that there goes something wrong in the BIOS that gets solved only, if you flash all versions in correct order until V3 (always chose complete flash!). F4a seems to be one cause of the problem. But also boards that do not have F4a installed seem to have this problem, also fixed with the provided solution. At least for boards I had so far. I hope this helps and I would appreciate feedback! Btw. 300 posts  |
|
|
|
I should have become a dev for miner software................. Fair enough for me, I will continue using Phoenix miner. |
|
|
|
|
We need proof, that the Phoenix account here is not hijacked. Imagine someone setting up new accounts with malicious software and the real Phoenix guy is still gone.
This is just a thought I have, no evidence! I dont want to spread FUD, but I will only use new Phoenix versions released here, after I get some proof. Someone mentioned moving a specific amount of the dev funds announcing it here, so we can verify on chain that the real developer is here.
On the other hand one can say, Nicehash is not credible. But since it is such a big entity in this space, if they give out an official warning, it is hard to ignore. So Nicehash should be more careful, if this was just FUD, otherwise the users will ensure it wont be a big entity in the space anymore in the future.
|
|
|
|
The main question is who actually downloaded the phoenix miner from the unofficial sources and then included it in their nicehash software package for everyone to download? Answer: nicehash employees  So don't blame the Phoenix now as he is not here to defend himself. So far it has proven to be stable software so I'll keep using it myself. Also, there is no proof it is malicious so I'd advise nicehash against spreading the fud based on a single fact that it was removed from Mega. Claymore was also removed from Mega and no one panicked about it. I know they're working on their excavator and they don't need/want phoenix anymore, but that's not the way to handle such transition. Very unprofessional, classic nicehash. I agree with you. The only point I am a bit concerned is, that it is one thing to state there is a problem or a bug or some inconsistency, but a very different other thing, to advice users to reinstall their OS and consider all their data, wallets, logins compromised on PCs that ran phoenix. You know what I mean? It would be a bit insane to spread FUD on this level for marketing reasons. |
|
|
|
|
Hi,
I reactivate this thread since my issue fits quite well. I am using several Gigabte Fintech boards and got my first one with problems now. It works well, but as soon as I put in a 10th GPU, it does not post anymore. To make it a bit shorter: I switched the boards with a working 12 GPU Rig with the same board and suddenly the rig posted and hashed. The "defective" on the other hand did not even post in the 12 GPU rig. And as soon as I disconnected 3 GPUs, it booted normally. It is not bound to specific PCIe ports, it does not matter which are connected, as soon as it is more than 9, it does not post. So its not the PSU, riser etc. it seems to be the board. All my other Fintechs work fine woith 12 GPUs.
Do I have a defective board?
What I tried, without success:
-Loaded defaults in BIOS
-Reflashed recent BIOS
-Flashed old v3 BIOS
-Checked every setting and deactivated all unneccessary devices
-Mining mode is enabled, 4G decodeing is enabled, primary video device is integrated GPU etc...
Is Link Speed Gen2 fixed, when mining mode is active? Because I was not able to change it to Gen1, it kept resetting after reboot.
I also swapped the CPU and RAM an checked all the cables.
Is there anything I can do or is my board just faulty and not able to run with more than 9 GPUs? It seems strange because this board worked for months with 6GPUs now and I would not expect it th just be fine except for the last 3 GPUs.
Thank you in advance for any help!
|
|
|
|
Hello, due to a really stupid chain of events, I ended up with a corrupted wallet.dat file of a Zcash wallet after a worst case scenario with data loss. Please do not ask about the seed phrases, I know they should have been backed up and with this exception my seed phrases are very safe for every other wallet - except this. Now, I am trying to dump the wallet.dat for the private keys with pywallet. But when trying to dump the wallet with python pywallet.py --dumpwallet --wallet=C:\*pathtowallet*\wallet.dat > wallet.txt into a txt, I am getting (22, 'Invalid argument -- BDB2509 the log files from a database environment') Maybe there is another way to do this? Thank you in advance! |
|
|
|
|
Show Posts
