 Show Posts
|
|
Pages: [1] 2 »
|
A lot of bad incidences happened in crypto community this year including:
1) FTX
2) Luna
3) Gemini Earn
4) Celcius
5) Voyager
6)BlockFi
All these incidences happened because of the greed of some people. It is important to control the entry of these kind of people as developers or people behind some new crypto projects. Otherwise people will have very less trust left on crypto in general and people will move to other alternatives. What do you think are the required steps to prevent these incidences from occurring in future ? Or are these unavoidable ?
Define greed. Who is not greedy? The miner trying to earn some profit? The trader trying to earn some profit? The developer trying to earn some profit? The investors trying to earn some profit? Govern officials trying to earn some profit? Small investors jumping in without understanding the basics of even bitcoin and driven by baseless propaganda? Was that not greed from people who don't understand anything and just ask in social media what to invest on? Now that it did not make them a millionaire someone else is greedy? They were being used as scapegoat to destroy whatever good is left in crypto. A fool and his money is soon parted. Not only that a fool is a liability on everybody else in the society including those who tried to give him good advise and only got insult or harm in return. These fools would have lost their money anywhere they would have invested why blame crypto market or bitcoin alone? Hint: it is not greed that brought the system down it is something else but I would not like to point it out as that makes me unpopular and someone who can't see it himself will never understand that. I can only give hints with the hope if they get it themselves they will bot abuse me and will be helpful to them and me as well. There is no point discussing with people that are brainwashed in a certain way that is so visible by their use of words like greed, profiteering, etc. This is economic forum talk in terms of economics. If you are talking about economic greed then your post does not make any sense as it is contradictory as you cannot ban or legislate away economic greed without removing people's right to property and that is why I am saying this has a may be unconscious or unintended narrow political tunnel vision. You lined up the events right. But what was the fundamental economical problem with all of these platforms? Do you have the courage to admit that? You know it if you understand bitcoin. Think clearly without political and religious bias. Biases are your enemy as a decision maker. You should be free from all biases as much as possible to be a good decision maker. Think only in terms of economics, maths and stats. You will get the stone cold right answer. I will not provide the answer. You must work to free your mind of irrational biases. The last hint is it is not bitcoin's fault but bitcoin is being blamed because all of these salesy, marketing folks knew it is only bitcoin that can shore up their shit coins. Ultimately why "people" bought these? Somebody held a gun at their head to buy any of these shit coins? If not why are they behaving like crybabies? Finally what is the harm if "People" lose trust in crypto in general and move to other alternatives? People were not interested in bitcoin say 7 years back. Did that stop us from making money in bitcoin and crypto? It is advantageous if people do not buy good technology and we get the opportunity to buy it cheap for longer period in time. The later people will return to bitcoin or crypto the better it is for early responsible investors. This is basic Warren Buffet advice and he is right here. Your "People" has no opinion of their own. A few carefully placed articles and few advertisements with big tit beautiful hosts will again bring them back to crypto or whatever. How else they invested in these shit coins? They will anyway lose their money on whatever else they invest without understanding the basics be it financial markets, real estate, business, whatever unless they are lucky enough to win a lottery ticket and do not come back for more. What is your charge against the entrepreneurs? Their ideas were flawed? They themselves also lost money. Why did not "people" understand that? Many of us did and avoided all of these shit coins as media were touting them. There are many more left that will meet the same end. Until then someone may make money in those coins but that is just winning lottery. I am not going to touch them. Some may not have started as shit but adopted shitty ideas for any touchy feely cause that can motivate "people". The fish that took the bait has no responsibility for its demise? If you believe in a cause then go volunteer for that cause do not go through 5 pass throughs. Your time is the costliest donation to a cause. Everything else is advertisement or tax dodging or something even worse. I would just add ---- It is the intention of big old money that "people" lose trust in crypto in general and move to other alternatives. Bitcoin and crypto is the only asset where intelligent retail is ahead of Big Old money. They will use all arrows in their quiver to nail retail. Examples, regulation, using dumb retail to go against intelligent retail, media, advertisements, touchy feely ideas that will make people emotional. Just study Warren Buffet's statement about crypto in last year or so. I gave him credit where he is right. But ultimately he is not a nice man. You have to differentiate image building and subtle advertisements from reality. Many big banks and financial institutions doing the same. Why is sec denying convertibility of some bitcoin ETF? Who are they protecting? Small investors or their rich old connected buddies? Think. Make a habit of thinking. |
|
|
|
|
With $400 budget the best thing you can do is buy btc.
|
|
|
|
|
With that kind of budget you should be able to buy directly from the manufacturer.
|
|
|
|
Fuck them 900 million for 110,000 s19's let btc drop to 15k screw those mojo's bigly.
True that! Assuming we are in for the long haul why should we care even if BTC goes to 10K temporarily? More buying opportunity for Fuzzy and all of us. |
|
|
|
|
Appreciate your insights wndsnb. Over the weekend I am going to take out each board and heat them up to the point so that the sinks are resoldered. If I find some are really out of place them I am going to take them out and solder them individually. Once cold, I will clean them with canned air. Finally I am going to check the signals also with multimeter. Then will put them one by one into miners and see what happens. I did not buy the test zig. Would you recommend it?
They used to work fine and were producing 75 TH @ 2728 watts each. We had a strange hot week during early Jan and that killed them. Now I think the problem is it is so cold that the boards are finding it difficult to start and of course some of them developed heat sink problem during excessive hot days.
|
|
|
|
|
The other miner was running 3 boards but board 2 was down. The boards had volatage 1940, 1960 and 1960. Since the middle board was down it was running with 1940 first and 1960 3rd board and was giving full hash rate. Thus my conclusion when there is only 2 boards the stock firmware does not stop for voltage difference.
So I started with
Miner 1
1920 - issues
1920- good
1960 - issues
Miner 2
1940 - good
1960- Issues
1960- good
I replaced the 3rd 1960 board in machine 1 with 1940 in 2nd. I switched to Hive to get around voltage check of stock firmware and to get a little more clue for chip level monitoring.
So I now have a more interesting puzzle.
Miner 1 -
1920 - good now. Had 0 asic in the same slot & same miner before. Hive on indicating a lot of bad domains but running it in low power mode. Should I re-solder the bad domains?
1920 - good. Was good same slot same miner.
1940 - now 0 asic but was good in machine 2 slot 1. Power supply or power cord issue in this slot? I am thinking about buying a new power supply and a new control board to just get them out of equation. I can't find a new control board from reliable sources. But these 2 machines ran flawlessly even a month ago.
Miner 2 -
1960 - good. had 0 asic when it was in slot 2 but good in slot 1 same machine. Hive on indicating a lot of bad domains but running it in low power mode. Should I re-solder the bad domains?
1960 - good. It was good in slot 3 as well. Same machine.
1960 - o asic. had o asic in machine 1 slot 3. send for repair?
Now I am completely confused
Can anybody confirm that in immersion mining losing connection with a heatsink is not this big a problem? I was planning for a DIY immersion setup. The sinks are visibly attached well to the board. After I soldered few that I did not feel was good from visual inspection, they are all firmly attached to the chips now.
[moderator's note: consecutive posts merged]
|
|
|
|
I pulled in the board with 1940 voltage but it does not work with the other 2. I am still getting the same error 2022-01-19 00:48:41 voltage[0] = 1920 2022-01-19 00:48:41 voltage[1] = 1920 2022-01-19 00:48:41 voltage[2] = 1940 2022-01-19 00:48:41 Voltage are different. Will exit. 2022-01-19 00:48:41 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT 2022-01-19 00:48:41 driver-btm-api.c:156:stop_mining: stop mining: soc init failed! 2022-01-19 00:48:41 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread 2022-01-19 00:48:41 driver-btm-api.c:141:killall_hashboard: ****power off hashboard**** But I think I get this error only when all 3 boards are attempted to be run that is they all detect 65 ASIC. It is not an issue when only 2 boards are running for example when 1 of them finds 0 asic, it tries to start the other two. 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: 203316K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 26060K 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: 13020K (cce49000 - 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: 2/0, WL threshold: 4096, image sequence number: 11906131
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 5C61C316-5FAD-4CFA-B280-2AFAE13C9D72, 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: 2/0, WL threshold: 4096, image sequence number: 169213079
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 6FB1BE46-BF1C-4F4C-9CA2-2F82009B82B4, 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
2022-01-19 00:46:23 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2022-01-19 00:46:23 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version = 1
2022-01-19 00:46:23 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab = 1
2022-01-19 00:46:23 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-01-19 00:46:23 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun 2 10:31:07 CST 2020 type: Antminer S17+
2022-01-19 00:46:23 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2022-01-19 00:46:23 driver-btm-api.c:2083:show_sn: len:16, 8034b4442b104814
2022-01-19 00:46:23 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2022-01-19 00:46:23 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2022-01-19 00:46:23 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 8034b4442b104814
2022-01-19 00:46:23 fan.c:284:front_fan_power_on: Note: front fan is power on!
2022-01-19 00:46:23 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2022-01-19 00:46:23 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2022-01-19 00:46:23 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2022-01-19 00:46:29 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-19 00:46:29 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-19 00:46:35 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-19 00:46:35 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-19 00:46:35 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-19 00:46:35 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2022-01-19 00:46:35 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2022-01-19 00:46:35 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2022-01-19 00:46:35 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2022-01-19 00:46:35 thread.c:1363:create_read_nonce_reg_thread: create thread
2022-01-19 00:46:41 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-19 00:46:41 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-19 00:46:46 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-19 00:46:46 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-19 00:46:46 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-19 00:46:46 driver-btm-api.c:792:_set_project_type: project:0
2022-01-19 00:46:46 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2022-01-19 00:46:46 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-01-19 00:46:46 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-01-19 00:46:46 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-01-19 00:46:46 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-01-19 00:46:46 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-01-19 00:46:46 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-01-19 00:46:48 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2022-01-19 00:46:49 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-01-19 00:46:51 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2022-01-19 00:46:52 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-01-19 00:46:54 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-01-19 00:46:55 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-01-19 00:46:57 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-01-19 00:46:57 thread.c:1358:create_pic_heart_beat_thread: create thread
2022-01-19 00:46:57 power_api.c:213:power_init: Power init:
2022-01-19 00:46:57 power_api.c:214:power_init: current_voltage_raw = 0
2022-01-19 00:46:57 power_api.c:215:power_init: highest_voltage_raw = 2100
2022-01-19 00:46:57 power_api.c:216:power_init: working_voltage_raw = 1950
2022-01-19 00:46:57 power_api.c:217:power_init: higher_voltage_raw = 2040
2022-01-19 00:46:57 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2022-01-19 00:46:57 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-01-19 00:47:29 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2022-01-19 00:47:55 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-19 00:47:56 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.094872
2022-01-19 00:47:57 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.097560
2022-01-19 00:47:58 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.170731
2022-01-19 00:47:58 power_api.c:53:_get_avg_voltage: average_voltage = 21.121054
2022-01-19 00:47:58 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.12, check voltage passed.
2022-01-19 00:47:58 uart.c:72:set_baud: set fpga_baud to 115200
2022-01-19 00:48:10 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2022-01-19 00:48:21 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2022-01-19 00:48:32 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2022-01-19 00:48:40 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2022-01-19 00:48:40 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2022-01-19 00:48:40 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2022-01-19 00:48:40 driver-btm-api.c:435:set_order_clock: chain[2]: set order clock, stragegy 3
2022-01-19 00:48:41 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2022-01-19 00:48:41 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2022-01-19 00:48:41 voltage[0] = 1920
2022-01-19 00:48:41 voltage[1] = 1920
2022-01-19 00:48:41 voltage[2] = 1940
2022-01-19 00:48:41 Voltage are different. Will exit.
2022-01-19 00:48:41 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2022-01-19 00:48:41 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2022-01-19 00:48:41 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2022-01-19 00:48:41 driver-btm-api.c:141:killall_hashboard: ****power off hashboard****
|
|
|
|
Looks like chain[2] was originally from a different miner. That voltage is the setting in the eeprom on the hashboard. The miner will not operate if the 3 hashboards don't have the same voltage setting. So you'll either need to buy a programmer to burn the eeprom with compatible settings or use aftermarket firmware.
Thank you so much for helping me again. You are absolutely correct. I bought this miner 2nd hand and it came with bosminer. It ran fine for few months. When it started to give trouble I switched to stock firmware to troubleshoot. I believe eeprom has a finite reprogramming life. May be the previous owner has already exhausted that. So he was using bosminer to get away with it. It is also possible that I misplaced this 3rd board from another s17+ miner while cleaning or trouble shooting. In this S17+ I have boards with 1920, 1920 and 1960. The board with 1960 being kicked out. In another s17+ cards are running with stock firmware with voltages 1940 & 1960. So it looks like a difference of 40 is unacceptable but a difference of 20 is acceptable? I am thinking if I exchange this board with the one having 1940 in the other s17+ then may be it will run with 1960 there and may be the board with 1940 will be acceptable in this s17+ where others boards are at 1920. I will do that and report back after the day job. I am also thinking about trying vniche and awesome miner if they are better at troubleshooting. While bosminer works fine for running them efficiently it is not good for trouble shooting or I am not good enough to trouble shoot with bosminer. Really appreciate your insight and guidance wndsnb! I gave you a few merits. Being a newbie I don't have much to give. |
|
|
|
I rebooted one more time as only one hash-board was running. Now it finds all asics on all boards but shuts down due to votage being different!. 2022-01-17 22:27:12 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2022-01-17 22:27:23 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2022-01-17 22:27:34 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
-----------------------------------
2022-01-17 22:27:44 voltage[0] = 1920
2022-01-17 22:27:44 voltage[1] = 1920
2022-01-17 22:27:44 voltage[2] = 1960
2022-01-17 22:27:44 Voltage are different. Will exit.
2022-01-17 22:27:44 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2022-01-17 22:27:44 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2022-01-17 22:27:44 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2022-01-17 22:27:44 driver-btm-api.c:141:killall_hashboard: ****power off hashboard**** But voltages were 1920 on chain0 and chain1 even when it did not find all asics on chain2 and it started hashing with chain0 and chain1. Why this time despite finding all asics in chain2 it is shutting down Chain0 and chain1 just because chqin2 has a different voltage? Is this the real problem? Any clues about what to do? Chain2 is where I re-soldered the capacitor. Full log below:
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: 203316K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 26060K 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: 13020K (cce49000 - 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: 1/0, WL threshold: 4096, image sequence number: 11906131
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 5C61C316-5FAD-4CFA-B280-2AFAE13C9D72, 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: 2/0, WL threshold: 4096, image sequence number: 169213079
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 6FB1BE46-BF1C-4F4C-9CA2-2F82009B82B4, 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
2022-01-17 22:25:26 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2022-01-17 22:25:26 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version = 1
2022-01-17 22:25:26 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab = 1
2022-01-17 22:25:26 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-01-17 22:25:26 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun 2 10:31:07 CST 2020 type: Antminer S17+
2022-01-17 22:25:26 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2022-01-17 22:25:26 driver-btm-api.c:2083:show_sn: len:16, 8034b4442b104814
2022-01-17 22:25:26 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2022-01-17 22:25:26 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2022-01-17 22:25:26 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 8034b4442b104814
2022-01-17 22:25:26 fan.c:284:front_fan_power_on: Note: front fan is power on!
2022-01-17 22:25:26 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2022-01-17 22:25:26 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2022-01-17 22:25:26 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2022-01-17 22:25:32 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-17 22:25:32 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-17 22:25:37 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-17 22:25:37 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-17 22:25:37 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-17 22:25:37 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2022-01-17 22:25:37 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2022-01-17 22:25:37 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2022-01-17 22:25:37 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2022-01-17 22:25:37 thread.c:1363:create_read_nonce_reg_thread: create thread
2022-01-17 22:25:43 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-17 22:25:43 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-17 22:25:49 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-17 22:25:49 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-17 22:25:49 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-17 22:25:49 driver-btm-api.c:792:_set_project_type: project:0
2022-01-17 22:25:49 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2022-01-17 22:25:49 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-01-17 22:25:49 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-01-17 22:25:49 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-01-17 22:25:49 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-01-17 22:25:49 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-01-17 22:25:49 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-01-17 22:25:51 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2022-01-17 22:25:52 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-01-17 22:25:54 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2022-01-17 22:25:55 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-01-17 22:25:57 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-01-17 22:25:58 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-01-17 22:26:00 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-01-17 22:26:00 thread.c:1358:create_pic_heart_beat_thread: create thread
2022-01-17 22:26:00 power_api.c:213:power_init: Power init:
2022-01-17 22:26:00 power_api.c:214:power_init: current_voltage_raw = 0
2022-01-17 22:26:00 power_api.c:215:power_init: highest_voltage_raw = 2100
2022-01-17 22:26:00 power_api.c:216:power_init: working_voltage_raw = 1950
2022-01-17 22:26:00 power_api.c:217:power_init: higher_voltage_raw = 2040
2022-01-17 22:26:00 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2022-01-17 22:26:00 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-01-17 22:26:00 power_api.c:186:power_off: init gpio907
2022-01-17 22:26:32 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2022-01-17 22:26:58 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-17 22:26:59 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.094872
2022-01-17 22:27:00 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.124679
2022-01-17 22:27:01 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.295630
2022-01-17 22:27:01 power_api.c:53:_get_avg_voltage: average_voltage = 21.171727
2022-01-17 22:27:01 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.17, check voltage passed.
2022-01-17 22:27:01 uart.c:72:set_baud: set fpga_baud to 115200
2022-01-17 22:27:12 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2022-01-17 22:27:23 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2022-01-17 22:27:34 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2022-01-17 22:27:43 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2022-01-17 22:27:43 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2022-01-17 22:27:43 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2022-01-17 22:27:43 driver-btm-api.c:435:set_order_clock: chain[2]: set order clock, stragegy 3
2022-01-17 22:27:43 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2022-01-17 22:27:43 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2022-01-17 22:27:44 voltage[0] = 1920
2022-01-17 22:27:44 voltage[1] = 1920
2022-01-17 22:27:44 voltage[2] = 1960
2022-01-17 22:27:44 Voltage are different. Will exit.
2022-01-17 22:27:44 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2022-01-17 22:27:44 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2022-01-17 22:27:44 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2022-01-17 22:27:44 driver-btm-api.c:141:killall_hashboard: ****power off hashboard****
|
|
|
|
My question is do you think the problem with chain 2 is the capacitor that the 63rd chip? Would you do something different that re-soldering if you faced these errors?
I assume you're talking about one of the large electrolytic caps? I doubt it would cause the issue you are seeing. If it was one of the caps in the boost circuit that generates the 1.8V signal for the last voltage domain, maybe the regulator could go unstable, so that would mess up all the chips in the last voltage domain though. Also, just re-soldering those chips is a bit of a shot in the dark. The problem could be those chips, or the chips after, or sometimes even just another chip in the same voltage domain. Thanks wndsnb for responding. You are right. it is the large 330mf and 30v cap just besides, what I think is, the 63rd chip. Incidentally this board is finding only 62 chip. I encircled the cap and the 63rd chip in black oval in the picture that I borrowed from Zeus manual. https://imgur.com/a/RaQXtuSAnother strange thing is after another reboot the error message changed a bit "Chain 2 only find 0 asic, will power off hash board 2" compared to last time "Chain 2 only find 62 asic, will power off hash board 2" So why did it find 62 Asic last time but 0 this time? Outside temperature is sub zero after a round of snow and I don't have insulation / heating in the place where the miner is so excess temperature is ruled out. This is the board where I reinstated the capacitor. i agree with you that the problem may be in chip # 62, 61, 63 or in the entire last column 61 through 65 which is the voltage domain if I am not wrong. I agree that just re-soldering is a shot in the dark but I lack expertise and probably equipment to do anything more. Chain 0 is now saying "chain 0 get hashrate_reg_counter 63, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxooo" compared to last time chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx" This board seem to have done slightly better. If I am reading it right last time chips #59 through 65 failed but this time only chip#61 and 62 failed. Am I reading it right? |
|
|
|
Hi Guys, I am having trouble with an S17+. This one used to run well and suddenly stopped working. I opened up, cleaned the power supply and the hash-boards. While putting the hash-boards back a capacitor from 3rd hash-board(Chain2) got detached from the board. I soldered it back. Now, Chain 0: starts hashing but is shutoff with the following error "ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx chain 0 can't get enough hashrate reg val for 30 times, power off." Chain1: working fine. Chain2: is powered off with error: "Chain 2 only find 62 asic, will power off hash board 2". This is the board that lost the capacitor that i have resoldered. - I am thinking I have to re-solder chip 59 on chain 0 and resolder chip 63 on Chain 2. Do you think the problem with chain 2 is the capacitor rather than the 63rd chip? Would you do something different if you faced these errors? I notice that with bosminer all 3 boards start and shut off. 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: 203316K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 26060K 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: 13020K (cce49000 - 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: 1/0, WL threshold: 4096, image sequence number: 11906131
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 5C61C316-5FAD-4CFA-B280-2AFAE13C9D72, 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: 1/0, WL threshold: 4096, image sequence number: 169213079
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): default file-system created
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 6FB1BE46-BF1C-4F4C-9CA2-2F82009B82B4, 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 0xcfb58000
*base_vir_addr = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2022-01-16 22:43:51 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2022-01-16 22:43:51 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version = 1
2022-01-16 22:43:51 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab = 1
2022-01-16 22:43:51 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-01-16 22:43:51 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun 2 10:31:07 CST 2020 type: Antminer S17+
2022-01-16 22:43:51 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2022-01-16 22:43:51 driver-btm-api.c:2083:show_sn: len:16, 8034b4442b104814
2022-01-16 22:43:51 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2022-01-16 22:43:51 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2022-01-16 22:43:51 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 8034b4442b104814
2022-01-16 22:43:51 fan.c:284:front_fan_power_on: Note: front fan is power on!
2022-01-16 22:43:51 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2022-01-16 22:43:51 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2022-01-16 22:43:51 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2022-01-16 22:43:57 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-16 22:43:57 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-16 22:44:02 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-16 22:44:02 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-16 22:44:02 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-16 22:44:02 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2022-01-16 22:44:02 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2022-01-16 22:44:02 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2022-01-16 22:44:02 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2022-01-16 22:44:02 thread.c:1363:create_read_nonce_reg_thread: create thread
2022-01-16 22:44:08 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-16 22:44:08 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-16 22:44:14 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-16 22:44:14 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-16 22:44:14 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-16 22:44:14 driver-btm-api.c:792:_set_project_type: project:0
2022-01-16 22:44:14 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2022-01-16 22:44:14 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2022-01-16 22:44:15 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-01-16 22:44:17 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2022-01-16 22:44:18 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-01-16 22:44:20 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-01-16 22:44:21 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-01-16 22:44:23 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-01-16 22:44:23 thread.c:1358:create_pic_heart_beat_thread: create thread
2022-01-16 22:44:23 power_api.c:213:power_init: Power init:
2022-01-16 22:44:23 power_api.c:214:power_init: current_voltage_raw = 0
2022-01-16 22:44:23 power_api.c:215:power_init: highest_voltage_raw = 2100
2022-01-16 22:44:23 power_api.c:216:power_init: working_voltage_raw = 1950
2022-01-16 22:44:23 power_api.c:217:power_init: higher_voltage_raw = 2040
2022-01-16 22:44:23 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2022-01-16 22:44:23 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-01-16 22:44:55 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2022-01-16 22:45:21 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:45:22 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.070513
2022-01-16 22:45:23 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.100258
2022-01-16 22:45:24 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.271209
2022-01-16 22:45:24 power_api.c:53:_get_avg_voltage: average_voltage = 21.147326
2022-01-16 22:45:24 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.15, check voltage passed.
2022-01-16 22:45:24 uart.c:72:set_baud: set fpga_baud to 115200
2022-01-16 22:45:35 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2022-01-16 22:45:46 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 8 asic, times 0
2022-01-16 22:45:57 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 8 asic, times 1
2022-01-16 22:46:08 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 8 asic, times 2
2022-01-16 22:46:08 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-01-16 22:46:17 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 63 asic, times 3
2022-01-16 22:46:17 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2050
2022-01-16 22:46:17 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2022-01-16 22:46:21 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:46:23 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.556977
2022-01-16 22:46:24 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.560975
2022-01-16 22:46:25 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.758355
2022-01-16 22:46:25 power_api.c:53:_get_avg_voltage: average_voltage = 20.625436
2022-01-16 22:46:25 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.63, check voltage passed.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-01-16 22:46:34 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 4
2022-01-16 22:46:34 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2022-01-16 22:46:37 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:46:39 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.019205
2022-01-16 22:46:40 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.048780
2022-01-16 22:46:41 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.246787
2022-01-16 22:46:41 power_api.c:53:_get_avg_voltage: average_voltage = 21.104924
2022-01-16 22:46:41 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.10, check voltage passed.
2022-01-16 22:46:52 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 0
2022-01-16 22:47:03 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 1
2022-01-16 22:47:14 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 2
2022-01-16 22:47:14 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-01-16 22:47:23 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 3
2022-01-16 22:47:23 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2050
2022-01-16 22:47:23 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2022-01-16 22:47:27 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:47:28 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.556977
2022-01-16 22:47:29 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.560975
2022-01-16 22:47:30 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.731706
2022-01-16 22:47:30 power_api.c:53:_get_avg_voltage: average_voltage = 20.616553
2022-01-16 22:47:30 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.62, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-01-16 22:47:39 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 4
2022-01-16 22:47:39 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2000
2022-01-16 22:47:39 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2022-01-16 22:47:42 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:47:43 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.046094
2022-01-16 22:47:44 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.048780
2022-01-16 22:47:45 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.219511
2022-01-16 22:47:45 power_api.c:53:_get_avg_voltage: average_voltage = 20.104795
2022-01-16 22:47:45 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.10, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-01-16 22:47:55 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 5
2022-01-16 22:47:55 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
2022-01-16 22:47:55 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2022-01-16 22:48:00 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:48:01 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.043533
2022-01-16 22:48:02 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.048780
2022-01-16 22:48:03 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.219511
2022-01-16 22:48:03 power_api.c:53:_get_avg_voltage: average_voltage = 21.103941
2022-01-16 22:48:03 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.10, check voltage passed.
2022-01-16 22:48:03 driver-btm-api.c:1193:check_asic_number: Chain 2 only find 62 asic, will power off hash board 2
2022-01-16 22:48:04 driver-btm-api.c:1195:check_asic_number: Chain 2 voltage: an0 = 2.787097, an2 2.806452, an6 2.512903.
2022-01-16 22:48:11 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2022-01-16 22:48:11 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2022-01-16 22:48:11 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2022-01-16 22:48:11 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2022-01-16 22:48:11 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2022-01-16 22:48:12 voltage[0] = 1920
2022-01-16 22:48:12 voltage[1] = 1920
2022-01-16 22:48:12 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1920
2022-01-16 22:48:13 temperature.c:340:calibrate_temp_sensor_one_chain: chain 0 temp sensor NCT218
2022-01-16 22:48:14 temperature.c:340:calibrate_temp_sensor_one_chain: chain 1 temp sensor NCT218
2022-01-16 22:48:14 uart.c:72:set_baud: set fpga_baud to 12000000
2022-01-16 22:48:15 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 23
2022-01-16 22:48:15 thread.c:1378:create_check_miner_status_thread: create thread
2022-01-16 22:48:15 thread.c:1368:create_show_miner_status_thread: create thread
2022-01-16 22:48:15 thread.c:1348:create_temperature_monitor_thread: create thread
2022-01-16 22:48:15 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 23 dec_freq_index=0
2022-01-16 22:48:15 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2022-01-16 22:48:15 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2022-01-16 22:48:15 thread.c:1338:create_asic_status_monitor_thread: create thread
2022-01-16 22:48:15 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 560, is_higher_voltage = true
2022-01-16 22:49:47 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2022-01-16 22:49:48 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:49:49 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.897566
2022-01-16 22:49:51 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.926828
2022-01-16 22:49:51 power_api.c:53:_get_avg_voltage: average_voltage = 20.912197
2022-01-16 22:49:51 power_api.c:71:check_voltage: target_vol = 20.90, actural_vol = 20.91, check voltage passed.
2022-01-16 22:52:02 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2080, step by step.
2022-01-16 22:52:03 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:52:04 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.775927
2022-01-16 22:52:05 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.780487
2022-01-16 22:52:05 power_api.c:53:_get_avg_voltage: average_voltage = 20.778207
2022-01-16 22:52:05 power_api.c:71:check_voltage: target_vol = 20.80, actural_vol = 20.78, check voltage passed.
2022-01-16 22:54:29 frequency.c:1152:inc_freq_with_fixed_step: chain = 0, freq_start = 560, freq_end = 570, freq_step = 5, is_higher_voltage = true
2022-01-16 22:54:33 frequency.c:1181:inc_asic_diff_freq_by_steps: chain = 1, start = 560, freq_step = 5
2022-01-16 22:54:35 driver-btm-api.c:765:set_timeout: freq = 570, percent = 90, hcn = 44236, timeout = 77
2022-01-16 22:54:35 power_api.c:310:set_to_working_voltage_by_steps: Set to voltage raw 1920, step by step.
2022-01-16 22:54:42 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:54:43 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 19.218949
2022-01-16 22:54:44 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 19.219511
2022-01-16 22:54:44 power_api.c:53:_get_avg_voltage: average_voltage = 19.219230
2022-01-16 22:54:44 power_api.c:71:check_voltage: target_vol = 19.20, actural_vol = 19.22, check voltage passed.
2022-01-16 22:54:44 thread.c:1373:create_check_system_status_thread: create thread
2022-01-16 22:54:44 driver-btm-api.c:2618:bitmain_soc_init: Init done!
2022-01-16 22:54:44 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2022-01-16 22:54:49 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2022-01-16 22:54:50 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 48464
2022-01-16 22:54:50 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 46000
2022-01-16 22:54:54 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2022-01-16 22:54:54 driver-btm-api.c:1644:dhash_chip_send_job: stime.tv_sec 1642373694, block_ntime 1642373688
2022-01-16 23:05:51 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:05:53 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 0 times.
2022-01-16 23:05:53 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:05:55 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 1 times.
2022-01-16 23:05:55 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:05:57 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 2 times.
2022-01-16 23:05:57 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:05:59 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 3 times.
2022-01-16 23:05:59 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:01 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 4 times.
2022-01-16 23:06:01 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:03 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 5 times.
2022-01-16 23:06:03 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:05 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 6 times.
2022-01-16 23:06:05 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:07 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 7 times.
2022-01-16 23:06:07 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:09 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 8 times.
2022-01-16 23:06:09 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:11 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 9 times.
2022-01-16 23:06:11 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:13 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 10 times.
2022-01-16 23:06:13 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:15 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 11 times.
2022-01-16 23:06:15 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:17 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 12 times.
2022-01-16 23:06:17 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:19 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 13 times.
2022-01-16 23:06:19 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:21 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 14 times.
2022-01-16 23:06:21 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:23 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 15 times.
2022-01-16 23:06:23 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:25 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 16 times.
2022-01-16 23:06:25 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:27 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 17 times.
2022-01-16 23:06:27 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:29 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 18 times.
2022-01-16 23:06:29 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:31 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 19 times.
2022-01-16 23:06:31 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:33 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 20 times.
2022-01-16 23:06:33 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:35 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 21 times.
2022-01-16 23:06:35 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:37 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 22 times.
2022-01-16 23:06:37 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:39 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 23 times.
2022-01-16 23:06:39 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:41 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 24 times.
2022-01-16 23:06:41 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:43 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 25 times.
2022-01-16 23:06:43 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:45 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 26 times.
2022-01-16 23:06:45 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:47 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 27 times.
2022-01-16 23:06:47 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:49 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 28 times.
2022-01-16 23:06:49 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:51 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 29 times.
2022-01-16 23:06:51 thread.c:1297:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 30 times, power off.
2022-01-16 23:06:52 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 24189
2022-01-16 23:06:52 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 22000
|
|
|
|
|
Nothing in this post is a financial / tax advice and I am not a financial / tax adviser. That being said,
I agree with phillipma here that we are trying to compare 2 activities that are not comparable to begin with.
Bitcoin mining and buying and holding bitcoin are not the same thing. One is a business the other is just investment.
Just like
1. Gold mining and investing in holding gold are 2 different activities.
2. Being an apartment owner yourself/ through your company and buying stock in REIT and holding real estate expecting it to increase in value are 3 different things. Although REIT passes on nearly all of its cash flow it is still not same as actively being involved in apartment business.
Bitcoin mining is a business. The business is to mine and sell bitcoin, pay for the expenses and earn profit if possible. If bitcoin is retained after mining then that is an investment decision made by the business. Why are you expecting accounting profit from this business every day? Did gold miners make accounting profit everyday in their existence? How about iron ore miners? Do all companies generating income produce accounting profit? Do you have any small business? Do your other businesses always make profit every month and year? Why are you stopping mining the moment the mining is not profitable? If your rental property is vacant or earning lower rent than expenses or in repair for few months do you sell it? If prices go down after you bought bitcoin from exchange will you immediately sell it? This whole comparison makes no sense to me.
Investment gains / loss / financing/ taxes and business gains / loss / financing/ taxes are 2 completely different things and are treated differently by the regulatory authorities as well.
|
|
|
|
|
I run them in 120 V 20A lines to heat my house during winter w modified BIOS at low watt depending on where and how much heat I need and how much sound can be tolerated. YMMV. Before I started mining I checked with electrician that the line that has 20A plug really had 20 amp wiring behind them.
|
|
|
|
|
Just wanted to say that I really like your calculator. It knows the difference between NPV and IRR, Differentiates between Capex & Opex, Infra cost, capital, allows difficulty, price, hardware appreciations / depreciation rates, cost of capital, revenue, operating profit and net profit. It saves me creation of a spreadsheet for a quick reality check. Most other bitcoin mining calculators and some celebrity youtubers just dumbly repeat the current difficulty and price MoM and confuses between NPV/IRR, Don't understand difference between revenue and profit forget about cost of capital. Good job guys and girls. I really appreciate your effort into making this calculator though it does not earn you money directly. It shows your love for doing things right and the best you can even for a free tool.
|
|
|
|
|
I have bought or mined altcoin for the same reason I have mined and bought bitcoin.
The process had been the same every time. I come to know about bitcoin. read the whitepaper and decided whether it is of value. Mined it. Then mined more and bought it at opportune moment or some time were forced as old exchanges closed on me. I usually don't buy POS unless there is an arbitrage opportunity. For example, when it was not possible to mine bitcoin anymore with cpu / gpu I used my cpu / gpu s to mine altcoins. Even at that time I expanded my cpu farm and gpu farm during the whole of 2016-2019 until GPU shortage made the price go to moon. When 1 altcoin is not mineable anymore I used the GPUs to mine the next alt coin depending on the objective of the alt coin. When bitcoin was not possible to mine by gpu I bought asics. Similarly when altcoins were not mineable anymore I bought asics. I am not influenced by Elon to buy a particular alt coin. Because i don't think elon has as much understanding of crypto as I have just like I don't have his vision in electric vehicle and space voyage. I respect him hold tesla stock for long time but I do not blindly follow him. Actually when he tweets about a failed alt coin that may be the time to sell it. If I had one of those coins then I would evaluate selling it after Elon tweets about such a shit coin. I basically buy an altcoin that has a promise which bitcoin did not have or may be bitcoin did have that promise but the feature is bit compromised in case of bitcoin but is implemented better in that altcoin. I rarely ever buy a coin without mining it, holding a personal wallet and doing some real transaction with it just to validate the use case.
|
|
|
|
This portal does not appear to be a rational un-biased source to base your intellectual discussion or business or investment decisions on. I did not know about this website before your post. I just went to their home page and following are the headlines of their recent articles i saw. 1. "How Bitcoin mining disproportionally impacts vulnerable communities." - how about existing fiat printing system? They are having really great impacts on "vulnerable communities"? 2. Bitcoin’s growing e-waste problem - I don't even know where to begin on this one. Height of dumbness. 3. Bitcoin may consume as much energy as all data centers globally - so what? Why is the data center that is spending 80% of its energy to power useless gossip is not waste? 4. How China’s Bitcoin mining ban affects energy consumption estimates - basically celebrating China's bitcoin ban as positive for the environment. As if the Chinese power plants are shut down now that bitcoin mining is banned? 5. Bitcoin now negating a decade of progress in deploying electric vehicles -huh! 6. A solution to Bitcoin’s Environmental Impact - basically promoting POS as the first solution, then "green energy", blah blah blah. Summary: 6 articles in 1st page published since June. 4 are straight out negative to bitcoin. Remaining 2 are also negative to bitcoin in not so subtle way. What kind of publication cannot recognize a single positive aspect of bitcoin? We know the reserve banks do not like bitcoins because it is robbing them of their monopolies on minting money. We know the cronies that are dependent on central bank and the big 4 and many of their friends badmouthed bitcoin for years. Then they said blockchain will survive but not bit coin. Finally some of them started buying bitcoin, started building their blockchain teams, even their own coins. Yet at the same time continued misinformation campaign against bitcoin to get more of it. We know even within crypto community there are lobbies that want to destroy all pow coins not only bitcoin. Given that we are investors, miners of bitcoin and therefore share at least some vision and thinking process of Satoshi. We absolutely don't need to waste our time reading such biased portals by paid shills or dumb reporters whatever the case may be. Energy to mine bitcoin is not "wasted". That way energy to produce and procure special type of paper, watermark, printing is also wasted. The energy to melt metals and create amalgams and seals to mint is also wasted with the same logic. How about the energy to build and secure mints run by government? I am not even getting into the energy used to keep this system going and the energy this kind of shill media is using just to run misinformation campaign. Why don't these shills talk about that? |
|
|
|
You are missing one line, there should be TWO lines in /etc/crontabs/root so add it back:
*/1 * * * * /usr/sbin/logrotate /etc/logrotate.conf 2>&1 | logger -t logrotate
0 0 * * * /usr/sbin/bos_upgrade_at 2>&1 | logger -t upgrade
Stop mining with /etc/init.d/bosminer stop
But this will ramp up the fans for protection, so also edit /usr/sbin/bosminer_monitor.lua
Search and replace fan_set_duty(i, 100) with fan_set_duty(i, 0)
Some fans don't like it to be set to 0% (they would spin to 100% instead), in that case try higher values until you find the min one.
Then your added lines should look something like this:
0 11 * * 1-5 /etc/init.d/bosminer stop && sleep 300 && /etc/init.d/bosminer_monitor stop && sed -i 's/fan_set_duty(i, 100)/fan_set_duty(i, 0)/g' /usr/sbin/bosminer_monitor.lua && /etc/init.d/bosminer_monitor start
0 14 * * 1-5 /etc/init.d/bosminer start && /etc/init.d/bosminer_monitor stop && sed -i 's/fan_set_duty(i, 0)/fan_set_duty(i, 100)/g' /usr/sbin/bosminer_monitor.lua && /etc/init.d/bosminer_monitor start
Yes, your first * is wrong, that would make it run every single minute, so no, you only run it at minute 0.
The sleep 300 is critical for the x17 family, it is meant to cool down the boards before stopping or slowing the fans. You may shorten the number of seconds if you use the S9 family.
Thanks a ton! Really appreciate your help. I learned a lot from your response. I am going to try tonight. Update: It is working perfectly for s9s but not working for s17s. I tried to telnet into S17s and tried to issue the command /etc/init.d/bosminer stop && sleep 300 && /etc/init.d/bosminer_monitor stop && sed -i 's/fan_set_duty(i, 100)/fan_set_duty(i, 0)/g' /usr/sbin/bosminer_monitor.lua && /etc/init.d/bosminer_monitor start It said command failed: not found I tried to navigate to /etc/init.d/ and tried to issue bosminer stop it looks like it did not recognize the stop after bosminer. |
|
|
|
|
I want to stop mining at 11 am and start again at 2 pm. I have added the following 2 lines to the scheduler to do that under "system"->"scheduled tasks" assuming that will put them in cron file. But it is not working. Can one of you please help me to tweak this so that they work?
*/1 * * * * /usr/sbin/logrotate /etc/logrotate.conf 2>&1 | logger -t logrotate
* 11 * * 1-5 pause
* 14 * * 1-5 resume
The first line was existing. I added line #2 and 3. Thanks in advance.
|
|
|
|
|
Without help from outside cold you can't mine in finished areas like a home or carpeted and insulated office space. In hot area you may be able to mine in unfinished area like an industrial warehouse where you can install large industrial fans to improve airflow. I still don't understand how people mine at home in Florida or Texas where they have no winter. But then people are mining in Dubai. they must have a solution if they are mining at home. For me the a/c cannot help the moment outside reaches 80.
|
|
|
|
Are they all just simply scams? or are there actually some legit ones out there ?
The majority of cloud mining companies are nothing but scam, the rest are overpriced, Viabtc offers a legit cloud mining service, I have not tried it but I use viabtc for mining and they are indeed trusted so it's highly unlikely that such a large pool will turn out to be selling scam mining contracts. Also, IIRC bitdeer has a partnership with Bitmain which makes them somehow trustworthy, but again, the legit ones are overpriced, the fake ones are just ... fake. IF they are legit ... doesnt the "overpricedness" really depend on what the market is going to do ... or would btc going up not really matter, as you would also me mining less and less, as time goes on, due to difficulty etc ... how hard do you think btc would have to go up, to actually make it worth while, to buy like a 2 year contract now? what would btc (or eth for that matter, depending on the contract) have to move to, for it to have been a good decision? Mining gold and holding gold are 2 different business or trade. Similarly mining bitcoin and holding bitcoin are also 2 different business or trade. I understand some people and business do both sometimes in some situations but still they are different business. When we look at a cloud mining contracts we basically compare the production cost of the contract vs in-house production cost. I am yet to come across any cloud contract that has lesser cost of production than me doing in-house over the last several years. It does not matter what bitcoin price does, my cost of production do not become more than the contract unless my opex/ overhead/ cost of capital changes. If in-house mining is unprofitable then of course could mining will also be unprofitable. So, from that perspective, most of the cloud contracts are "over priced". I agree with Mikey.
I think you guys are answering this question a bit to the extreme, choosing a good mining platform is very important. I don't endorse all the cloud mining scams you guys are talking about, I now do my own defi mining. http://www.biki-eth.comI feel very good about it myself, and the daily earnings are paid out in four installments. No. Legendary members are not extreme. I quickly glanced through the whitepaper. It is so full of marketing catch phrases that my alarm for scam went on. I hate sales and marketing materials and don't have much time to waste. No way this is bitcoin mining in my humble opinion. I understand yield farming, liquidity farming, etc., are sold/marketed as mining nowadays but this is not really mining. Think of fiat. Government minting a $1 coin is not the same as you getting $1 as a salary or interest. What you described at best should belong to alt coin section. [moderator's note: consecutive posts merged] |
|
|
|
|
