Hello My friends, I recently heard that there are some devices that work on the Bitcoin Lightning network.The operation of Lightning network devices is that by connecting and config to payment channels in this network, they confirm transactions and receive fees!! The calculation process of the device is based on the number of transactions, each transaction is 0.0025 dollars, and every 10,000 transactions is 25 dollars. The device must reach the quorum of deposit which is 25 dollars and then automatically send it to your wallet!! Because the activity of the devices is in the form of transaction confirmation, it does not consume much electricity and you can easily turn it on at home. They work without sound and heat!!
The amount of electricity and internet consumption of devices:- The power consumption of the device is 100 watts, which is equivalent to a 100-watt lamp, and it is powered by a laptop adapter (12 V - 5 A). - Due to the low power consumption of the device, there are no restrictions on the use of household electricity at home. - The device's monthly internet usage is between 3 and 5 gigabytes. Devices income - currencies it outputs 1- Two channels: every 12 days there is a deposit of 25 dollars. (income is 60 dollars per month)- Currencies that output: BTC ETH LTC DOGE MATIC TRX DOT LINK 2- Four channels: every 7 days there is a deposit of 25 dollars. (monthly income of 100 dollars)- Currencies that output: BTC ETH LTC DOGE MATIC TRX 3- Six channels: every 9 days there is a deposit of 100 dollars (income of 300 dollars per month)- Currencies that output: BTC ETH LTC SOL XRP DOT AVAX DOGE TRX MATIC The income of the device is fixed in dollars
A sample image of one of these devices: https://www.imghippo.com/i/gZiD4361ZAI.jpgif you have more information about it and company and website , please discussion about them in this post  |
|
|
|
Hello My friends, I recently heard that there are a number of devices that work on the Bitcoin Lightning network. The operation of Lightning network devices is that by connecting and confing to payment channels in this network, they confirm transactions and receive fees!! The calculation process of the device is based on the number of transactions, each transaction is 0.0025 dollars, and every 10,000 transactions is 25 dollars. The device must reach the quorum of deposit which is 25 dollars and then automatically send it to your wallet!! Because the activity of the devices is in the form of transaction confirmation, it does not consume much electricity and you can easily turn it on at home. They work without sound and heat!! The amount of electricity and internet consumption of devices:- The power consumption of the device is 100 watts, which is equivalent to a 100-watt lamp, and it is powered by a laptop adapter (12 V - 5 A). - Due to the low power consumption of the device, there are no restrictions on the use of household electricity at home. - The device's monthly internet usage is between 3 and 5 gigabytes. Devices income - currencies it outputs1- Two channels: every 12 days there is a deposit of 25 dollars. (income is 60 dollars per month)- Currencies that output: BTC ETH LTC DOGE MATIC TRX DOT LINK 2- Four channels: every 7 days there is a deposit of 25 dollars. (monthly income of 100 dollars)- Currencies that output: BTC ETH LTC DOGE MATIC TRX 3- Six channels: every 9 days there is a deposit of 100 dollars (income of 300 dollars per month)- Currencies that output: BTC ETH LTC SOL XRP DOT AVAX DOGE TRX MATIC The income of the device is fixed in dollars A sample image of one of these devices:  https://www.imghippo.com/i/gZiD4361ZAI.jpgif you have more information about it and company and website , please discussion about them in this post  |
|
|
|
Black Friday Special Offer! Use Code: BLACKFRIDAY150 copy for 150% Bonus! What is BlockDAG? BlockDAG, inspired by Bitcoin, is the world’s most advanced layer 1 blockchain. A cutting-edge Proof-of-Work (PoW) algorithm that delivers industry-leading speeds, unbeatable security, and high decentralization. BlockDAG BlockDAG is a Layer 1 proof of work consensus mechanism that evolves the crypto sphere with a cutting-edge Directed Acyclic Graph structure building on the foundations of Bitcoin Total Coin Supply 150,000,000,000 BlockDAG Coin (BDAG) stands out with a total supply of 150 billion coins, underscoring its rarity and commitment to maintaining value. At BlockDAG Network, we've implemented a halving event every 12 months, further solidifying our commitment to maintaining scarcity and value. Setting a limit on our coin supply helps us manage growth responsibly, avoid excessive inflation and create a stable environment for our community. Presale Allocation 50,000,000,000 ANNOUNCEMENT The next keynote update release will be December 15th 2024 To purchase coins, navigate to the BUY section on our website. Click on BUY, then connect your wallet here: https://purchase.blockdag.network/ . Refer anyone to purchase BDAG coins and receive a 10% referral bonus. By connecting your wallet, you can verify your token balance, Referrals and Referral Earnings on the purchase page. The shipment of BDAG miners is scheduled to begin towards the end of 2024 and the start of 2025. For comprehensive shipping details, please refer to https://blockdag.network/shipping-policy. Should you require assistance with returns, our support team at support@blockdag.network is at your service. Upon purchasing, the BDAG coins will be deposited into the same wallet used for the transaction. You can calculate your earning potential on calculator page. You can view the number of BDAG coins you own in "Coin Balance" after your connect your wallet on the BUY page. Moreover, to view the number of miners in your possession, connect your wallet and navigate to "Owned Devices" on the buy page https://purchase.blockdag.network/Our X30 and X100 miners employ the SHA-256 algorithm, enabling you to mine both BTC and BDAG coins. The development of the X1 model is underway, with its application expected to be available on the Google Play and Apple App Store following the launch of the main net. The X1 miner is now available on the Apple App Store. For Android users, the app can be downloaded from the Huawei App Gallery, the Amazon App Store, or directly via the Android APK. We will also release a technical whitepaper and provide an updates section on GitHub to continuously track our project's development. Please use the validator tool to verify you are using the original links/channels. Stay tuned for the next keynote release. The cryptocurrency presale scene is currently brimming with exciting investment opportunities as 2024 continues to usher in innovative blockchain projects. These presales not only introduce investors to groundbreaking technologies but also offer an early stake in tokens poised for potential exponential growth upon their market debut. Here, we highlight the top six presales that remain open for investment, providing you with an opportunity to get involved in the upcoming wave of blockchain innovations. 1. BlockDAG (BDAG) - Enhancing Blockchain Scalability BlockDAG stands out in the crypto landscape by incorporating Directed Acyclic Graph (DAG) technology to boost transaction scalability and speed. This innovative setup facilitates parallel processing of transactions, tackling the typical congestion and high fees seen in traditional blockchains. This presale has attracted significant interest, amassing almost $150 million from 26 batches. Early adopters have seen their holdings surge by 2,240%, highlighting the project's robust market appeal. To date, BlockDAG has distributed 16.4 billion BDAG coins at $0.0234 each, indicating strong buyer enthusiasm. With a core focus on scalability and efficiency, BlockDAG is poised to significantly influence the blockchain sector. Its successful presale and forward-thinking technology forecast a bright future as it continues to grow and develop its ecosystem. 2. Pepe Unchained ($PEPU) - Enhancing Meme Coin Trading & Staking Pepe Unchained introduces a Layer-2 solution on Ethereum designed to enhance the trading and staking dynamics within the meme coin community. The project aims to boost transaction speeds and slash costs, addressing the common challenges faced by meme coin enthusiasts on the Ethereum network. By adopting Layer-2 technology, Pepe Unchained allows for quicker, more affordable transactions, presenting a viable solution for frequent traders. The project has rapidly garnered strong community backing, particularly appealing to meme coin users attracted by its promise of reduced fees and enhanced transaction speeds. Moreover, the platform rewards those who stake $PEPU tokens, adding an extra incentive for long-term engagement. With meme coins consistently in demand and a clear need for improved trading infrastructure, Pepe Unchained is well-placed to secure a significant niche in the 2024 market. 3. Crypto All-Stars ($STARS) - Consolidating the Meme Coin Arena Crypto All-Stars seeks to unify various meme coins under one umbrella, enabling users to stake their tokens and earn rewards in one centralized location. This model is particularly appealing to investors looking to streamline their staking activities without juggling multiple platforms. The presale has drawn considerable attention with its innovative staking model that rewards holders across various meme coins. Crypto All-Stars is set to enhance its ecosystem by integrating additional meme tokens and introducing DeFi features, potentially boosting demand for its $STARS token. This expansion could attract investors eager to maximize their staking returns while diversifying their meme coin investments. 4. FreeDum Fighters ($DUM) - Blending Memes with Political Satire FreeDum Fighters takes a distinctive approach by integrating political satire into its meme coin framework. Operating across multiple chains, it allows users to stake their tokens and participate in mock elections within its ecosystem. This blend of humor and decentralized finance has cultivated a dedicated following interested in both entertainment and financial returns. Its multi-chain functionality ensures scalability and extensive reach, providing investors with opportunities to engage in governance while enjoying the platform's ongoing satirical content. The ongoing presale stages offer early access to $DUM tokens at competitive prices, appealing to those who appreciate the interplay between memes and politics. 5. Flockerz ($FLOCK) - Pioneering Community Governance Flockerz is redefining decentralized governance by rewarding token holders for participating in decision-making processes. Operating as a Decentralized Autonomous Organization (DAO), it enables users to vote on proposals and influence the platform’s strategic direction. This vote-to-earn model has attracted a growing community interested in earning rewards while actively shaping the project's future. Beyond governance, Flockerz aims to broaden its offerings to include NFT staking and DeFi lending, creating additional utility for its tokens. This project is particularly attractive to investors passionate about community-driven initiatives with clear expansion plans. 6. SpacePay ($SPY) - Simplifying Retail Crypto Transactions SpacePay is dedicated to closing the gap between traditional retail payments and cryptocurrency transactions. The project is developing a protocol that facilitates crypto payments in physical stores, simplifying the use of digital assets in everyday purchases. This practical application tackles a major hurdle in cryptocurrency adoption—its integration into daily consumer activities. |
|
|
|
Every person who lives with cryptos know that cryptocurrencies will dump in 2023 and in 2024 we will more grow...
so in this topic, we discuss which coin is better to buy for more gains about 10X to 1000X!
my idea : 1- ETH---10X  2- ADA---20X 3- MATIC---10X 4-SHIBA--100X 5-NEAR---50X 6-DOT--20X what's your idea?
|
|
|
|
In this topic, please recommend the best metaverse coin and token that will be huge growth in 2022, 2023. Please send the reason and related link and topic too. Best Wishes my first Idea is ENJ (Enjin-Coin) Enjin Coin Price Prediction in 2022 - Up to $10 USD Enjin Coin (CCC:ENJ-USD) is up almost 20% on the day as metaverse rumors heat up the red-hot cryptocurrency market. The videogame crypto platform, Enjin, has received particular attention for having all the makings to launch a thriving, crypto-based metaverse. |
|
|
|
go to site FBI and all members that have account with QTY send it to follow with them we follow bitconnect with FBI and FBI created a link for all people to add their losing money |
|
|
|
|
Which Pool is better for mining dual LTC+Dog ?
For example viabtc rate 1:2000 for doge?
Any pool is different with this rate for doge and LTC together or all pool is 1:2000 range??
|
|
|
|
with firmware original bitmain T17+ 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: 203436K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25940K 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: 12900K (cce67000 - cdb00000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
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: 7/4, WL threshold: 4096, image sequence number: 475803952
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 4C8E2A96-53AB-438A-A7F5-E9FDFE38F3F1, 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: 404/64, WL threshold: 4096, image sequence number: 3563076859
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 A21581E4-693A-4BBF-A66A-FCE5ACD2EF7F, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2021-07-01 06:33:22 driver-btm-api.c:723:init_freq_mode: This is scan-user version
2021-07-01 06:33:22 driver-btm-api.c:2514:bitmain_soc_init: opt_multi_version = 1
2021-07-01 06:33:22 driver-btm-api.c:2515:bitmain_soc_init: opt_bitmain_ab = 1
2021-07-01 06:33:22 driver-btm-api.c:2516:bitmain_soc_init: opt_bitmain_work_mode = 0
2021-07-01 06:33:22 driver-btm-api.c:2517:bitmain_soc_init: Miner compile time: Wed Apr 8 11:27:07 CST 2020 type: Antminer T17+
2021-07-01 06:33:22 driver-btm-api.c:2518:bitmain_soc_init: commit version: fc44955 2020-04-08 11:23:26, build by: lol 2020-04-08 11:32:55
2021-07-01 06:33:22 driver-btm-api.c:2126:show_sn: no SN got, please write SN to /config/sn
2021-07-01 06:33:22 driver-btm-api.c:2181:handle_sn_for_factory_mode: read sn failed, use fpga-id to replace sn
2021-07-01 06:33:22 driver-btm-api.c:2187:handle_sn_for_factory_mode: read fpga id success 807c250c2b10481c
2021-07-01 06:33:22 fan.c:258:front_fan_power_on: Note: front fan is power on!
2021-07-01 06:33:22 fan.c:268:rear_fan_power_on: Note: rear fan is power on!
2021-07-01 06:33:22 driver-btm-api.c:1318:miner_device_init: Detect 256MB control board of XILINX
2021-07-01 06:33:22 driver-btm-api.c:1259:init_fan_parameter: fan_eft : 1 fan_pwm : 100
2021-07-01 06:33:28 driver-btm-api.c:1242:init_miner_version: miner ID : 807c250c2b10481c
2021-07-01 06:33:28 driver-btm-api.c:1248:init_miner_version: FPGA Version = 0xB023
2021-07-01 06:33:34 driver-btm-api.c:775:get_product_id: product_id[0] = 0
2021-07-01 06:33:34 driver-btm-api.c:775:get_product_id: product_id[1] = 0
2021-07-01 06:33:34 driver-btm-api.c:775:get_product_id: product_id[2] = 0
2021-07-01 06:33:34 driver-btm-api.c:806:get_chip_version: chip_version[0] = 1
2021-07-01 06:33:34 driver-btm-api.c:806:get_chip_version: chip_version[1] = 1
2021-07-01 06:33:34 driver-btm-api.c:806:get_chip_version: chip_version[2] = 1
2021-07-01 06:33:34 driver-btm-api.c:2254:update_conf_by_power_feedback: Power feedback is disabled
2021-07-01 06:33:34 driver-btm-api.c:2258:update_conf_by_power_feedback: get_calibration_voltage, vol:1850.
2021-07-01 06:33:34 frequency.c:1290:adjust_higer_max_vol_table: adjust_higer_max_vol_table, ideal_hashrate = 57926, index = 2, adjust_vol = 40
2021-07-01 06:33:34 thread.c:1166:create_read_nonce_reg_thread: create thread
2021-07-01 06:33:40 driver-btm-api.c:1242:init_miner_version: miner ID : 807c250c2b10481c
2021-07-01 06:33:40 driver-btm-api.c:1248:init_miner_version: FPGA Version = 0xB023
2021-07-01 06:33:45 driver-btm-api.c:775:get_product_id: product_id[0] = 0
2021-07-01 06:33:45 driver-btm-api.c:775:get_product_id: product_id[1] = 0
2021-07-01 06:33:45 driver-btm-api.c:775:get_product_id: product_id[2] = 0
2021-07-01 06:33:45 driver-btm-api.c:806:get_chip_version: chip_version[0] = 1
2021-07-01 06:33:45 driver-btm-api.c:806:get_chip_version: chip_version[1] = 1
2021-07-01 06:33:45 driver-btm-api.c:806:get_chip_version: chip_version[2] = 1
2021-07-01 06:33:45 driver-btm-api.c:1905:get_ccdly_opt: ccdly_opt[0] = 0
2021-07-01 06:33:45 driver-btm-api.c:1905:get_ccdly_opt: ccdly_opt[1] = 0
2021-07-01 06:33:45 driver-btm-api.c:1905:get_ccdly_opt: ccdly_opt[2] = 0
2021-07-01 06:33:45 driver-btm-api.c:2400:bitmain_board_init: g_ccdly_opt = 0
2021-07-01 06:33:45 driver-btm-api.c:736:_set_project_type: project:0, set to T17Plus always
2021-07-01 06:33:45 driver-btm-api.c:751:_set_project_type: Project type: Antminer T17+
2021-07-01 06:33:45 driver-btm-api.c:762:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2021-07-01 06:33:45 driver-btm-api.c:763:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2021-07-01 06:33:45 driver-btm-api.c:762:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2021-07-01 06:33:45 driver-btm-api.c:763:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2021-07-01 06:33:45 driver-btm-api.c:762:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2021-07-01 06:33:45 driver-btm-api.c:763:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2021-07-01 06:33:45 driver-btm-api.c:2422:bitmain_board_init: Fan check passed.
2021-07-01 06:33:46 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-07-01 06:33:48 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2021-07-01 06:33:49 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-07-01 06:33:51 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2021-07-01 06:33:52 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-07-01 06:33:54 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2021-07-01 06:33:54 thread.c:1161:create_pic_heart_beat_thread: create thread
2021-07-01 06:33:56 power_api.c:231:power_init: power type version: 0x0042
2021-07-01 06:33:56 power_api.c:249:power_init: Power init:
2021-07-01 06:33:56 power_api.c:250:power_init: current_voltage_raw = 0
2021-07-01 06:33:56 power_api.c:251:power_init: highest_voltage_raw = 1950
2021-07-01 06:33:56 power_api.c:252:power_init: working_voltage_raw = 1900
2021-07-01 06:33:56 power_api.c:253:power_init: higher_voltage_raw = 1930
2021-07-01 06:33:56 power_api.c:254:power_init: check_asic_voltage_raw = 2000
2021-07-01 06:33:56 driver-btm-api.c:2432:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-07-01 06:33:56 power_api.c:218:power_off: init gpio907
2021-07-01 06:33:56 power_api.c:221:power_off: set gpio907 to 1
2021-07-01 06:34:27 power_api.c:206:power_on: set gpio907 to 0
2021-07-01 06:34:28 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1850, step by step.
2021-07-01 06:34:46 power_api.c:120:check_voltage_multi: retry time: 0
2021-07-01 06:34:47 power_api.c:56:_get_avg_voltage: an6 raw = 2.519355, factor = 1.007742
2021-07-01 06:34:47 power_api.c:60:_get_avg_voltage: chain 0, an0 = 0.632522, an2 18.732394, an6 2.500000.
2021-07-01 06:34:48 power_api.c:56:_get_avg_voltage: an6 raw = 2.525806, factor = 1.010323
2021-07-01 06:34:48 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.679438, an2 18.660282, an6 2.500000.
2021-07-01 06:34:50 power_api.c:56:_get_avg_voltage: an6 raw = 2.519355, factor = 1.007742
2021-07-01 06:34:50 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.559539, an2 18.708066, an6 2.500000.
2021-07-01 06:34:50 power_api.c:85:_get_avg_voltage: average_voltage = 18.700247
2021-07-01 06:34:50 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.70, check voltage passed.
2021-07-01 06:34:52 power_api.c:56:_get_avg_voltage: an6 raw = 2.519355, factor = 1.007742
2021-07-01 06:34:52 power_api.c:60:_get_avg_voltage: chain 0, an0 = 0.632522, an2 18.732394, an6 2.500000.
2021-07-01 06:34:53 power_api.c:56:_get_avg_voltage: an6 raw = 2.525806, factor = 1.010323
2021-07-01 06:34:53 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.679438, an2 18.660282, an6 2.500000.
2021-07-01 06:34:54 power_api.c:56:_get_avg_voltage: an6 raw = 2.519355, factor = 1.007742
2021-07-01 06:34:54 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.559539, an2 18.708066, an6 2.500000.
2021-07-01 06:34:54 power_api.c:85:_get_avg_voltage: average_voltage = 18.700247
2021-07-01 06:34:54 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.70, check voltage passed.
2021-07-01 06:34:54 uart.c:81:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-07-01 06:35:03 driver-btm-api.c:1123:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 0
2021-07-01 06:35:11 driver-btm-api.c:1124:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 1
2021-07-01 06:35:23 driver-btm-api.c:1125:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2
2021-07-01 06:35:23 power_api.c:400:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2021-07-01 06:35:40 power_api.c:120:check_voltage_multi: retry time: 0
2021-07-01 06:35:41 power_api.c:56:_get_avg_voltage: an6 raw = 2.519355, factor = 1.007742
2021-07-01 06:35:41 power_api.c:60:_get_avg_voltage: chain 0, an0 = 0.656850, an2 20.192061, an6 2.500000.
2021-07-01 06:35:42 power_api.c:56:_get_avg_voltage: an6 raw = 2.525806, factor = 1.010323
2021-07-01 06:35:42 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.679438, an2 20.116221, an6 2.500000.
2021-07-01 06:35:43 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2021-07-01 06:35:43 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.584615, an2 20.217949, an6 2.500000.
2021-07-01 06:35:43 power_api.c:85:_get_avg_voltage: average_voltage = 20.175410
2021-07-01 06:35:43 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.18, check voltage passed.
2021-07-01 06:35:46 power_api.c:56:_get_avg_voltage: an6 raw = 2.519355, factor = 1.007742
2021-07-01 06:35:46 power_api.c:60:_get_avg_voltage: chain 0, an0 = 0.656850, an2 20.192061, an6 2.500000.
2021-07-01 06:35:47 power_api.c:56:_get_avg_voltage: an6 raw = 2.525806, factor = 1.010323
2021-07-01 06:35:47 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.679438, an2 20.140487, an6 2.500000.
2021-07-01 06:35:48 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2021-07-01 06:35:48 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.584615, an2 20.217949, an6 2.500000.
2021-07-01 06:35:48 power_api.c:85:_get_avg_voltage: average_voltage = 20.183499
2021-07-01 06:35:48 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.18, check voltage passed.
2021-07-01 06:35:57 driver-btm-api.c:1128:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 3
2021-07-01 06:36:08 driver-btm-api.c:1129:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 4
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-07-01 06:36:16 driver-btm-api.c:1130:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 5
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-07-01 06:36:25 driver-btm-api.c:1131:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 6
2021-07-01 06:36:25 driver-btm-api.c:1196:check_asic_number: Chain 0 only find 0 asic, will power off hash board 0
2021-07-01 06:36:26 driver-btm-api.c:1199:check_asic_number: Chain 0 voltage: an0 = 20.372904, an2 20.348387, an6 2.522581.
2021-07-01 06:36:27 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1850, step by step.
2021-07-01 06:36:42 power_api.c:120:check_voltage_multi: retry time: 0
2021-07-01 06:36:44 power_api.c:56:_get_avg_voltage: an6 raw = 2.522581, factor = 1.009032
2021-07-01 06:36:44 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.680307, an2 18.684143, an6 2.500000.
2021-07-01 06:36:45 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2021-07-01 06:36:45 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.560256, an2 18.756411, an6 2.500000.
2021-07-01 06:36:45 power_api.c:85:_get_avg_voltage: average_voltage = 18.720277
2021-07-01 06:36:45 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.72, check voltage passed.
2021-07-01 06:36:47 power_api.c:56:_get_avg_voltage: an6 raw = 2.522581, factor = 1.009032
2021-07-01 06:36:47 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.680307, an2 18.708440, an6 2.500000.
2021-07-01 06:36:48 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2021-07-01 06:36:48 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.560256, an2 18.732052, an6 2.500000.
2021-07-01 06:36:48 power_api.c:85:_get_avg_voltage: average_voltage = 18.720246
2021-07-01 06:36:48 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.72, check voltage passed.
2021-07-01 06:36:57 driver-btm-api.c:1123:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2021-07-01 06:37:05 driver-btm-api.c:1124:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2021-07-01 06:37:17 driver-btm-api.c:1125:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2021-07-01 06:37:17 power_api.c:400:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2021-07-01 06:37:32 power_api.c:120:check_voltage_multi: retry time: 0
2021-07-01 06:37:33 power_api.c:56:_get_avg_voltage: an6 raw = 2.525806, factor = 1.010323
2021-07-01 06:37:33 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.679438, an2 20.116221, an6 2.500000.
2021-07-01 06:37:34 power_api.c:56:_get_avg_voltage: an6 raw = 2.519355, factor = 1.007742
2021-07-01 06:37:34 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.583867, an2 20.192061, an6 2.500000.
2021-07-01 06:37:34 power_api.c:85:_get_avg_voltage: average_voltage = 20.154140
2021-07-01 06:37:34 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.15, check voltage passed.
2021-07-01 06:37:37 power_api.c:56:_get_avg_voltage: an6 raw = 2.525806, factor = 1.010323
2021-07-01 06:37:37 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.679438, an2 20.116221, an6 2.500000.
2021-07-01 06:37:38 power_api.c:56:_get_avg_voltage: an6 raw = 2.519355, factor = 1.007742
2021-07-01 06:37:38 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.583867, an2 20.192061, an6 2.500000.
2021-07-01 06:37:38 power_api.c:85:_get_avg_voltage: average_voltage = 20.154140
2021-07-01 06:37:38 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.15, check voltage passed.
2021-07-01 06:37:46 driver-btm-api.c:1128:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 3
2021-07-01 06:37:57 driver-btm-api.c:1129:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 4
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-07-01 06:38:06 driver-btm-api.c:1130:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 5
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-07-01 06:38:15 driver-btm-api.c:1131:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 6
2021-07-01 06:38:15 driver-btm-api.c:1196:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2021-07-01 06:38:16 driver-btm-api.c:1199:check_asic_number: Chain 1 voltage: an0 = 20.323871, an2 20.323871, an6 2.529032.
2021-07-01 06:38:17 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1850, step by step.
2021-07-01 06:38:32 power_api.c:120:check_voltage_multi: retry time: 0
2021-07-01 06:38:33 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2021-07-01 06:38:33 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.560256, an2 18.732052, an6 2.500000.
2021-07-01 06:38:33 power_api.c:85:_get_avg_voltage: average_voltage = 18.732051
2021-07-01 06:38:33 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.73, check voltage passed.
2021-07-01 06:38:35 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2021-07-01 06:38:35 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.560256, an2 18.732052, an6 2.500000.
2021-07-01 06:38:35 power_api.c:85:_get_avg_voltage: average_voltage = 18.732051
2021-07-01 06:38:35 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.73, check voltage passed.
2021-07-01 06:38:44 driver-btm-api.c:1123:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2021-07-01 06:38:53 driver-btm-api.c:1124:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2021-07-01 06:39:03 driver-btm-api.c:1125:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2021-07-01 06:39:03 power_api.c:400:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2021-07-01 06:39:17 power_api.c:120:check_voltage_multi: retry time: 0
2021-07-01 06:39:18 power_api.c:56:_get_avg_voltage: an6 raw = 2.519355, factor = 1.007742
2021-07-01 06:39:18 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.583867, an2 20.167733, an6 2.500000.
2021-07-01 06:39:18 power_api.c:85:_get_avg_voltage: average_voltage = 20.167733
2021-07-01 06:39:18 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.17, check voltage passed.
2021-07-01 06:39:20 power_api.c:56:_get_avg_voltage: an6 raw = 2.519355, factor = 1.007742
2021-07-01 06:39:20 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.583867, an2 20.192061, an6 2.500000.
2021-07-01 06:39:20 power_api.c:85:_get_avg_voltage: average_voltage = 20.192060
2021-07-01 06:39:20 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.19, check voltage passed.
2021-07-01 06:39:29 driver-btm-api.c:1128:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 3
2021-07-01 06:39:40 driver-btm-api.c:1129:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 4
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-07-01 06:39:48 driver-btm-api.c:1130:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 5
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2021-07-01 06:39:57 driver-btm-api.c:1131:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 6
2021-07-01 06:39:57 driver-btm-api.c:1196:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2021-07-01 06:39:58 driver-btm-api.c:1199:check_asic_number: Chain 2 voltage: an0 = 20.250323, an2 20.323871, an6 2.522581.
2021-07-01 06:39:59 driver-btm-api.c:216:set_miner_status: ERROR_SOC_INIT
2021-07-01 06:39:59 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2021-07-01 06:39:59 thread.c:1201:cancel_read_nonce_reg_thread: cancel thread
2021-07-01 06:39:59 driver-btm-api.c:142:killall_hashboard: ****power off hashboard**** |
|
|
|
what's the problem of this miner T17+ 55 th/s  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: 202820K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 26556K 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: 13516K (ccdcd000 - cdb00000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
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: 7/3, WL threshold: 4096, image sequence number: 475803952
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 4C8E2A96-53AB-438A-A7F5-E9FDFE38F3F1, 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: 404/64, WL threshold: 4096, image sequence number: 3563076859
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID A21581E4-693A-4BBF-A66A-FCE5ACD2EF7F, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
random: nonblocking pool is initialized
[2021/07/01 06:03:52] ERROR: src/chip139x.c:1044 chain[0] - Failed to receive chip replies
[2021/07/01 06:03:53] ERROR: src/chip139x.c:1044 chain[0] - Failed to receive chip replies
[2021/07/01 06:03:54] ERROR: src/chip139x.c:1044 chain[0] - Failed to receive chip replies
[2021/07/01 06:03:54] WARN: chain[0] - 0 of 44 chips detected
[2021/07/01 06:03:55] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies
[2021/07/01 06:03:56] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies
[2021/07/01 06:03:57] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies
[2021/07/01 06:03:57] WARN: chain[1] - 0 of 44 chips detected
[2021/07/01 06:03:58] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies
[2021/07/01 06:03:59] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies
[2021/07/01 06:04:00] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies
[2021/07/01 06:04:00] WARN: chain[2] - 0 of 44 chips detected
[2021/07/01 06:04:04] ERROR: src/chip139x.c:1044 chain[0] - Failed to receive chip replies
[2021/07/01 06:04:05] ERROR: src/chip139x.c:1044 chain[0] - Failed to receive chip replies
[2021/07/01 06:04:06] ERROR: src/chip139x.c:1044 chain[0] - Failed to receive chip replies
[2021/07/01 06:04:06] WARN: chain[0] - 0 of 44 chips detected
[2021/07/01 06:04:07] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies
[2021/07/01 06:04:08] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies
[2021/07/01 06:04:09] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies
[2021/07/01 06:04:09] WARN: chain[1] - 0 of 44 chips detected
[2021/07/01 06:04:10] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies
[2021/07/01 06:04:11] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies
[2021/07/01 06:04:12] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies
[2021/07/01 06:04:12] WARN: chain[2] - 0 of 44 chips detected
[2021/07/01 06:04:15] ERROR: src/chip139x.c:1044 chain[0] - Failed to receive chip replies
[2021/07/01 06:04:16] ERROR: src/chip139x.c:1044 chain[0] - Failed to receive chip replies
[2021/07/01 06:04:17] ERROR: src/chip139x.c:1044 chain[0] - Failed to receive chip replies
[2021/07/01 06:04:17] WARN: chain[0] - 0 of 44 chips detected
[2021/07/01 06:04:17] ERROR: driver-btm-chain.c:488 chain[0] - Failed to detect ASIC chips
[2021/07/01 06:04:17] INFO: chain[0] - Shutting down the chain
[2021/07/01 06:04:18] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2021/07/01 06:04:18] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies
[2021/07/01 06:04:19] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies
[2021/07/01 06:04:20] ERROR: src/chip139x.c:1044 chain[1] - Failed to receive chip replies
[2021/07/01 06:04:20] WARN: chain[1] - 0 of 44 chips detected
[2021/07/01 06:04:20] ERROR: driver-btm-chain.c:488 chain[1] - Failed to detect ASIC chips
[2021/07/01 06:04:20] INFO: chain[1] - Shutting down the chain
[2021/07/01 06:04:21] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2021/07/01 06:04:22] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies
[2021/07/01 06:04:23] ERROR: src/chip139x.c:1044 chain[2] - Failed to receive chip replies
[2021/07/01 06:04:23] WARN: chain[2] - 0 of 44 chips detected
[2021/07/01 06:04:23] ERROR: driver-btm-chain.c:488 chain[2] - Failed to detect ASIC chips
[2021/07/01 06:04:23] INFO: chain[2] - Shutting down the chain
[2021/07/01 06:04:24] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2021/07/01 06:04:24] WARN: All chains are disabled or disconnected
[2021/07/01 06:04:24] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2021/07/01 06:04:24] INFO: Shutting down the miner
[2021/07/01 06:04:24] INFO: Stopping FPGA queue
[2021/07/01 06:04:24] INFO: chain[0] - Shutting down the chain
[2021/07/01 06:04:24] INFO: chain[1] - Shutting down the chain
[2021/07/01 06:04:24] INFO: chain[2] - Shutting down the chain
[2021/07/01 06:04:24] INFO: Power OFF
[2021/07/01 06:04:24] ERROR: driver-btm-base.c:2360 Miner initialization failed |
|
|
|
From what I can tell from the log, the miner starts mining and it takes about 3 minutes for the chip to overheat. AntMiner
Chain# ASIC# Frequency(avg) Voltage Consumption (W) GH/S(ideal) GH/S(RT) Errors(HW) Temp(PCB) Temp(Chip)
3 44 450 16.5 494 13,305.60 7,857.16 0 43-49-47-53 71-61-80-62 Auto-tuning
I'm assuming that was captured during the 3 minutes, and one chip temp is already up to 80 dec, significantly higher than the others. So it looks like it runs for a little bit, and that chip just keeps getting hotter until it hits the 90Deg limit and shuts down. You could confirm this by just looking at the status page and refreshing constantly during bootup, monitoring the temperature. If it just gradually rises to failure, then I don't think it looks like a faulty sensor, but just a bad ASIC or a bad connection to its heatsink. These miners have a lot of issues with heat sinks, many times the copper plating that interfaces the chip to the solder that holds the heatsinks on delaminates, which can cause a little gap that will kill the efficiency of the heatsink. It is very possible that if you shake that miner a bit, or if you push on that heatsink, it will just fall right off. I assume you've already checked that there isn't a loose or missing heatsink? And that the heatsinks are clogged up with anything? You may be able to limp along if you block the 2 empty slots somehow. With them blocked, a lot more air will be forced through the heatsinks and it might be enough to keep it below 90. Dear wndsnb this status is with one hashboard and two other hashboard was removed Chain# ASIC# Frequency(avg) Voltage Consumption (W) GH/S(ideal) GH/S(RT) Errors(HW) Temp(PCB) Temp(Chip) 3 44 450 16.5 494 13,305.60 7,857.16 0 43-49-47-53 71-61-80-62 |
|
|
|
2021-04-27 11:37:34 thread.c:1161:check_temperature: over max temp, pcb temp 68 (max 80), chip temp 105(max 103)
2021-04-27 11:37:34 driver-btm-api.c:222:set_miner_status: ERROR_TEMP_TOO_HIGH
I see you created another thread just for this problem, which IMO isn't needed at all, in my last post I asked you to set fans to full RPMs using static fan speed of 100%, and then to report back on the finding, you said you flashed bitmain firmware but you didn't mention anything about the fan speed. Dear mikeywith I tested with fan 100% and this error is exist yet |
|
|
|
I changed framework to bitmain framework and give this error too 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: 203416K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25960K 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: 12920K (cce62000 - cdb00000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
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: 24/12, WL threshold: 4096, image sequence number: 2881768101
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 2AF94D23-0760-4801-8C27-532C11A81FC1, 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: 383/61, WL threshold: 4096, image sequence number: 3563076859
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 A21581E4-693A-4BBF-A66A-FCE5ACD2EF7F, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2021-04-27 11:31:48 driver-btm-api.c:762:init_freq_mode: This is scan-user version
2021-04-27 11:31:48 driver-btm-api.c:2553:bitmain_soc_init: opt_multi_version = 1
2021-04-27 11:31:48 driver-btm-api.c:2554:bitmain_soc_init: opt_bitmain_ab = 1
2021-04-27 11:31:48 driver-btm-api.c:2555:bitmain_soc_init: opt_bitmain_work_mode = 0
2021-04-27 11:31:48 driver-btm-api.c:2556:bitmain_soc_init: Miner compile time: Tue Jun 2 10:11:10 CST 2020 type: Antminer T17+
2021-04-27 11:31:48 driver-btm-api.c:2557:bitmain_soc_init: commit version: 9e9a5bf 2020-06-01 18:48:14, build by: lol 2020-06-02 10:21:50
2021-04-27 11:31:48 driver-btm-api.c:2165:show_sn: no SN got, please write SN to /config/sn
2021-04-27 11:31:48 driver-btm-api.c:2220:handle_sn_for_factory_mode: read sn failed, use fpga-id to replace sn
2021-04-27 11:31:48 driver-btm-api.c:2226:handle_sn_for_factory_mode: read fpga id success 807c250c2b10481c
2021-04-27 11:31:48 fan.c:263:front_fan_power_on: Note: front fan is power on!
2021-04-27 11:31:48 fan.c:273:rear_fan_power_on: Note: rear fan is power on!
2021-04-27 11:31:48 driver-btm-api.c:1357:miner_device_init: Detect 256MB control board of XILINX
2021-04-27 11:31:48 driver-btm-api.c:1298:init_fan_parameter: fan_eft : 1 fan_pwm : 100
2021-04-27 11:31:54 driver-btm-api.c:1281:init_miner_version: miner ID : 807c250c2b10481c
2021-04-27 11:31:54 driver-btm-api.c:1287:init_miner_version: FPGA Version = 0xB023
2021-04-27 11:31:56 driver-btm-api.c:814:get_product_id: product_id[0] = 0
2021-04-27 11:31:56 driver-btm-api.c:845:get_chip_version: chip_version[0] = 1
2021-04-27 11:31:56 driver-btm-api.c:2293:update_conf_by_power_feedback: Power feedback is disabled
2021-04-27 11:31:56 driver-btm-api.c:2297:update_conf_by_power_feedback: get_calibration_voltage, vol:1850.
2021-04-27 11:31:56 frequency.c:1389:adjust_higer_max_vol_table: adjust_higer_max_vol_table, ideal_hashrate = 19019, index = 0, adjust_vol = 50
2021-04-27 11:31:56 thread.c:1462:create_read_nonce_reg_thread: create thread
2021-04-27 11:32:02 driver-btm-api.c:1281:init_miner_version: miner ID : 807c250c2b10481c
2021-04-27 11:32:02 driver-btm-api.c:1287:init_miner_version: FPGA Version = 0xB023
2021-04-27 11:32:04 driver-btm-api.c:814:get_product_id: product_id[0] = 0
2021-04-27 11:32:04 driver-btm-api.c:845:get_chip_version: chip_version[0] = 1
2021-04-27 11:32:04 driver-btm-api.c:1944:get_ccdly_opt: ccdly_opt[0] = 0
2021-04-27 11:32:04 driver-btm-api.c:2439:bitmain_board_init: g_ccdly_opt = 0
2021-04-27 11:32:04 driver-btm-api.c:775:_set_project_type: project:0, set to T17Plus always
2021-04-27 11:32:04 driver-btm-api.c:790:_set_project_type: Project type: Antminer T17+
2021-04-27 11:32:04 driver-btm-api.c:801:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2021-04-27 11:32:04 driver-btm-api.c:802:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2021-04-27 11:32:09 driver-btm-api.c:2461:bitmain_board_init: Fan check passed.
2021-04-27 11:32:10 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-04-27 11:32:12 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2021-04-27 11:32:12 thread.c:1457:create_pic_heart_beat_thread: create thread
2021-04-27 11:32:13 power_api.c:231:power_init: power type version: 0x0042
2021-04-27 11:32:13 power_api.c:249:power_init: Power init:
2021-04-27 11:32:13 power_api.c:250:power_init: current_voltage_raw = 0
2021-04-27 11:32:13 power_api.c:251:power_init: highest_voltage_raw = 1950
2021-04-27 11:32:13 power_api.c:252:power_init: working_voltage_raw = 1900
2021-04-27 11:32:13 power_api.c:253:power_init: higher_voltage_raw = 1930
2021-04-27 11:32:13 power_api.c:254:power_init: check_asic_voltage_raw = 2000
2021-04-27 11:32:13 driver-btm-api.c:2471:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-04-27 11:32:13 power_api.c:218:power_off: init gpio907
2021-04-27 11:32:13 power_api.c:221:power_off: set gpio907 to 1
2021-04-27 11:32:44 power_api.c:206:power_on: set gpio907 to 0
2021-04-27 11:32:45 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1850, step by step.
2021-04-27 11:33:02 power_api.c:120:check_voltage_multi: retry time: 0
2021-04-27 11:33:03 power_api.c:56:_get_avg_voltage: an6 raw = 2.516129, factor = 1.006452
2021-04-27 11:33:03 power_api.c:60:_get_avg_voltage: chain 0, an0 = 0.584615, an2 18.732052, an6 2.500000.
2021-04-27 11:33:03 power_api.c:85:_get_avg_voltage: average_voltage = 18.732051
2021-04-27 11:33:03 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.73, check voltage passed.
2021-04-27 11:33:05 power_api.c:56:_get_avg_voltage: an6 raw = 2.519355, factor = 1.007742
2021-04-27 11:33:05 power_api.c:60:_get_avg_voltage: chain 0, an0 = 0.583867, an2 18.732394, an6 2.500000.
2021-04-27 11:33:05 power_api.c:85:_get_avg_voltage: average_voltage = 18.732393
2021-04-27 11:33:05 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.73, check voltage passed.
2021-04-27 11:33:05 uart.c:81:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-04-27 11:33:14 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[0]: find 44 asic, times 0
2021-04-27 11:33:16 driver-btm-api.c:425:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2021-04-27 11:33:16 driver-btm-api.c:1931:get_core_clock_delay_setting: PWTH_SEL 3, CCDLY_SEL 0
2021-04-27 11:33:16 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2021-04-27 11:33:16 driver-btm-api.c:1972:check_clock_counter: freq 50 clock_counter_limit 6
2021-04-27 11:33:24 voltage[0] = 1790
2021-04-27 11:33:24 power_api.c:262:set_working_voltage_raw: working_voltage_raw = 1790
2021-04-27 11:33:25 temperature.c:313:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success. NCT218
2021-04-27 11:33:25 uart.c:81:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2021-04-27 11:33:26 driver-btm-api.c:294:check_bringup_temp: Bring up temperature is 34
2021-04-27 11:33:26 thread.c:1477:create_check_miner_status_thread: create thread
2021-04-27 11:33:26 thread.c:1467:create_set_miner_status_thread: create thread
2021-04-27 11:33:26 driver-btm-api.c:712:calculate_timeout: dev->timeout = 245
2021-04-27 11:33:26 thread.c:1447:create_temperature_monitor_thread: create thread
2021-04-27 11:33:26 frequency.c:527:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 34 dec_freq_index=0
2021-04-27 11:33:26 freq_tuning.c:184:freq_tuning_get_max_freq: Max freq of tuning is 790
2021-04-27 11:33:26 driver-btm-api.c:1802:send_null_work: [DEBUG] Send null work.
2021-04-27 11:33:26 thread.c:1437:create_asic_status_monitor_thread: create thread
2021-04-27 11:33:26 frequency.c:1194:inc_freq_with_fixed_vco: chain = 255, freq = 640, is_higher_voltage = true
2021-04-27 11:33:26 frequency.c:1210:inc_freq_with_fixed_vco: [0] _POSTDIV1 = 7, _POSTDIV2 = 7, USER_DIV = 1, freq = 52
2021-04-27 11:33:26 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1870, step by step.
2021-04-27 11:33:42 power_api.c:120:check_voltage_multi: retry time: 0
2021-04-27 11:33:43 power_api.c:56:_get_avg_voltage: an6 raw = 2.522581, factor = 1.009032
2021-04-27 11:33:43 power_api.c:60:_get_avg_voltage: chain 0, an0 = 18.805627, an2 18.854220, an6 2.500000.
2021-04-27 11:33:43 power_api.c:85:_get_avg_voltage: average_voltage = 18.854220
2021-04-27 11:33:43 power_api.c:106:check_voltage: target_vol = 18.70, actural_vol = 18.85, check voltage passed.
2021-04-27 11:33:45 power_api.c:56:_get_avg_voltage: an6 raw = 2.519355, factor = 1.007742
2021-04-27 11:33:45 power_api.c:60:_get_avg_voltage: chain 0, an0 = 18.829705, an2 18.902688, an6 2.500000.
2021-04-27 11:33:45 power_api.c:85:_get_avg_voltage: average_voltage = 18.902688
2021-04-27 11:33:45 power_api.c:106:check_voltage: target_vol = 18.70, actural_vol = 18.90, check voltage passed.
2021-04-27 11:33:47 frequency.c:1210:inc_freq_with_fixed_vco: [1] _POSTDIV1 = 7, _POSTDIV2 = 6, USER_DIV = 1, freq = 61
2021-04-27 11:33:49 frequency.c:1210:inc_freq_with_fixed_vco: [2] _POSTDIV1 = 6, _POSTDIV2 = 6, USER_DIV = 1, freq = 71
2021-04-27 11:33:51 frequency.c:1210:inc_freq_with_fixed_vco: [3] _POSTDIV1 = 7, _POSTDIV2 = 5, USER_DIV = 1, freq = 73
2021-04-27 11:33:53 frequency.c:1210:inc_freq_with_fixed_vco: [4] _POSTDIV1 = 6, _POSTDIV2 = 5, USER_DIV = 1, freq = 85
2021-04-27 11:33:55 frequency.c:1210:inc_freq_with_fixed_vco: [5] _POSTDIV1 = 7, _POSTDIV2 = 4, USER_DIV = 1, freq = 91
2021-04-27 11:33:57 frequency.c:1210:inc_freq_with_fixed_vco: [6] _POSTDIV1 = 5, _POSTDIV2 = 5, USER_DIV = 1, freq = 102
2021-04-27 11:34:02 frequency.c:1210:inc_freq_with_fixed_vco: [7] _POSTDIV1 = 6, _POSTDIV2 = 4, USER_DIV = 1, freq = 106
2021-04-27 11:34:06 frequency.c:1210:inc_freq_with_fixed_vco: [8] _POSTDIV1 = 7, _POSTDIV2 = 3, USER_DIV = 1, freq = 122
2021-04-27 11:34:11 frequency.c:1210:inc_freq_with_fixed_vco: [9] _POSTDIV1 = 5, _POSTDIV2 = 4, USER_DIV = 1, freq = 128
2021-04-27 11:34:15 frequency.c:1210:inc_freq_with_fixed_vco: [10] _POSTDIV1 = 6, _POSTDIV2 = 3, USER_DIV = 1, freq = 142
2021-04-27 11:34:20 frequency.c:1210:inc_freq_with_fixed_vco: [11] _POSTDIV1 = 4, _POSTDIV2 = 4, USER_DIV = 1, freq = 160
2021-04-27 11:34:28 frequency.c:1210:inc_freq_with_fixed_vco: [12] _POSTDIV1 = 5, _POSTDIV2 = 3, USER_DIV = 1, freq = 170
2021-04-27 11:34:28 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1850, step by step.
2021-04-27 11:34:44 power_api.c:120:check_voltage_multi: retry time: 0
2021-04-27 11:34:46 power_api.c:56:_get_avg_voltage: an6 raw = 2.522581, factor = 1.009032
2021-04-27 11:34:46 power_api.c:60:_get_avg_voltage: chain 0, an0 = 18.586957, an2 18.659847, an6 2.500000.
2021-04-27 11:34:46 power_api.c:85:_get_avg_voltage: average_voltage = 18.659846
2021-04-27 11:34:46 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.66, check voltage passed.
2021-04-27 11:34:48 power_api.c:56:_get_avg_voltage: an6 raw = 2.519355, factor = 1.007742
2021-04-27 11:34:48 power_api.c:60:_get_avg_voltage: chain 0, an0 = 18.610755, an2 18.708066, an6 2.500000.
2021-04-27 11:34:48 power_api.c:85:_get_avg_voltage: average_voltage = 18.708066
2021-04-27 11:34:48 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.71, check voltage passed.
2021-04-27 11:34:56 frequency.c:1210:inc_freq_with_fixed_vco: [13] _POSTDIV1 = 7, _POSTDIV2 = 2, USER_DIV = 1, freq = 183
2021-04-27 11:35:04 frequency.c:1210:inc_freq_with_fixed_vco: [14] _POSTDIV1 = 4, _POSTDIV2 = 3, USER_DIV = 1, freq = 213
2021-04-27 11:35:16 frequency.c:1210:inc_freq_with_fixed_vco: [15] _POSTDIV1 = 6, _POSTDIV2 = 2, USER_DIV = 1, freq = 213
2021-04-27 11:35:29 frequency.c:1210:inc_freq_with_fixed_vco: [16] _POSTDIV1 = 5, _POSTDIV2 = 2, USER_DIV = 1, freq = 256
2021-04-27 11:35:47 frequency.c:1210:inc_freq_with_fixed_vco: [17] _POSTDIV1 = 4, _POSTDIV2 = 2, USER_DIV = 1, freq = 320
2021-04-27 11:36:11 frequency.c:1210:inc_freq_with_fixed_vco: [18] _POSTDIV1 = 7, _POSTDIV2 = 1, USER_DIV = 1, freq = 366
2021-04-27 11:36:43 frequency.c:1210:inc_freq_with_fixed_vco: [19] _POSTDIV1 = 6, _POSTDIV2 = 1, USER_DIV = 1, freq = 427
2021-04-27 11:37:24 frequency.c:1210:inc_freq_with_fixed_vco: [20] _POSTDIV1 = 5, _POSTDIV2 = 1, USER_DIV = 1, freq = 512
2021-04-27 11:37:34 thread.c:1161:check_temperature: over max temp, pcb temp 68 (max 80), chip temp 105(max 103)
2021-04-27 11:37:34 driver-btm-api.c:222:set_miner_status: ERROR_TEMP_TOO_HIGH
2021-04-27 11:37:34 driver-btm-api.c:156:stop_mining: stop mining: over max temp
2021-04-27 11:37:34 thread.c:1487:cancel_temperature_monitor_thread: cancel thread
2021-04-27 11:37:34 thread.c:1502:cancel_read_nonce_reg_thread: cancel thread
2021-04-27 11:37:34 thread.c:1442:cancel_asic_status_monitor_thread: cancel thread
2021-04-27 11:37:34 driver-btm-api.c:142:killall_hashboard: ****power off hashboard**** |
|
|
|
|
this site is safe and payout?
Kyc needs for withdrawing winners?
|
|
|
|
|
AntMiner
Chain# ASIC# Frequency(avg) Voltage Consumption (W) GH/S(ideal) GH/S(RT) Errors(HW) Temp(PCB) Temp(Chip)
3 44 450 16.5 494 13,305.60 7,857.16 0 43-49-47-53 71-61-80-62 Auto-tuning
|
|
|
|
|
[2021/04/21 17:34:25] INFO: fan[0] - OK
[2021/04/21 17:34:25] INFO: fan[1] - OK
[2021/04/21 17:34:25] INFO: fan[2] - OK
[2021/04/21 17:34:25] INFO: fan[3] - OK
[2021/04/21 17:34:31] INFO: Power ON
[2021/04/21 17:34:33] INFO: Starting FPGA queue
[2021/04/21 17:34:33] INFO: Initializing hash boards
[2021/04/21 17:34:33] INFO: chain[2] - Initializing
[2021/04/21 17:34:46] INFO: chain[2] - 44 chips detected
[2021/04/21 17:34:51] INFO: Start-up temperature is 32 C (min -15 C)
[2021/04/21 17:34:51] INFO: Activating silent start-up mode
[2021/04/21 17:34:51] INFO: Switching to warm-up fan control (60 C)
[2021/04/21 17:34:51] INFO: Changing voltage from 19500 to 16500 mV gradually
[2021/04/21 17:35:31] INFO: Raising freq from 50 to 450 Mhz gradually
[2021/04/21 17:35:40] INFO: Switching to automatic fan control (75 C)
[2021/04/21 17:35:40] INFO: Start mining!
[2021/04/21 17:36:40] INFO: Changing voltage from 16500 to 16300 mV gradually
[2021/04/21 17:37:01] INFO: Changing voltage from 16300 to 16200 mV gradually
[2021/04/21 17:38:29] WARN: chain[2] - Overheated, chip temp=90
[2021/04/21 17:38:29] WARN: Switching to emergency fan control
[2021/04/21 17:38:29] INFO: chain[2] - Shutting down the chain
[2021/04/21 17:38:32] WARN: No working chains
[2021/04/21 17:38:32] INFO: Shutting down the miner
[2021/04/21 17:38:34] INFO: Stopping FPGA queue
|
|
|
|
|
I have a antminer t17+55 .
It worked until I changed the place of one hashboad that worked correctly in other place of hashboard miner ( 2 hashboards removed for maintenance).
now I get this error ..... (chain2 -overheated, chip temp=90)
what's problem?
-----------------------------------------------------------
fan(0) - ok
fan(1) - ok
fan(2) - ok
fan(3) - ok
Power On
chain2 ...initializing
chain 2...44 chips detected
start mining!
chain2 -overheated, chip temp=90
switching to emergency fan control
chain2 - shutting down the chain.
shutting down the miner
Power off
--------------------------------------------------------
|
|
|
|
I think the 2021 year will be great year for bitcoin and Cryptocurrency because the World Economic will have very bad status in end of 2020 and 2021 with this impact of Corona and other thing I read some paper that said America and China just can recover their Economic recovery at least in next 1 year in America and 2-3 Year in China so it is my predict of price ...do you agree? get have a discussion about my idea coin April2020 Mar2021Bitcoin 6800$ 25000$ Ethereum 155$ 600$ XRP 0.18$ 0.5$ Bitcoin Cash 230$ 1200$ Bitcoin SV 185$ 600$ Litecoin 42$ 200$ EOS 2.5$ 15$ Binance Coin 13.85$ 100$ Tezos 1.95$ 12$ Cardano 0.033$ 0.05$ TRON 0.012$ 15$ Ethereum Classic 5.26$ 25$ Neo 7.25$ 24$ IOTA 0.15$ 0.56$ Cosmos 2.29$ 10$ Zcash 36.15$ 150$ NEM 0.036$ 1$ Ontology 0.4$ 2$ Do you remember this my post... just now see ! we are in March 2021! What's your prediction for March 2025 so I can double it and know the real price   If you can predict end of 2021 then you can say true man ! in next post i will send it and you can follow it... not for next 4 years just 9 month! |
|
|
|
I think the 2021 year will be great year for bitcoin and Cryptocurrency because the World Economic will have very bad status in end of 2020 and 2021 with this impact of Corona and other thing I read some paper that said America and China just can recover their Economic recovery at least in next 1 year in America and 2-3 Year in China so it is my predict of price ...do you agree? get have a discussion about my idea coin April2020 Mar2021Bitcoin 6800$ 25000$ Ethereum 155$ 600$ XRP 0.18$ 0.5$ Bitcoin Cash 230$ 1200$ Bitcoin SV 185$ 600$ Litecoin 42$ 200$ EOS 2.5$ 15$ Binance Coin 13.85$ 100$ Tezos 1.95$ 12$ Cardano 0.033$ 0.05$ TRON 0.012$ 15$ Ethereum Classic 5.26$ 25$ Neo 7.25$ 24$ IOTA 0.15$ 0.56$ Cosmos 2.29$ 10$ Zcash 36.15$ 150$ NEM 0.036$ 1$ Ontology 0.4$ 2$ Do you remember this my post... just now see ! we are in March 2021! |
|
|
|
for example : First News[/b
21 September 2020: Tezos is selected for digital euro experiment by France
|
|
|
|
|
Show Posts
