One of those successful cases of bitcoin hodling was a friend of a friend. They (a couple) took an important risk by investing 60k of a dismissal compensation into bitcoin and making a x100 on it before selling half. I do not know what they did with the rest. Now, these people were not rich, they took an enormous risk compared to their total wealth. They had to really believe on the project and pass though some of bitcoins usual "tests of faith".
For someone with let´s say, a net worth of 1M USD or more plus house, hodling 60k until they became 6M would have been not that much of an stress. Do you think it was easier to benefit economically from bitcoin if you were already a bit up in the ladder?
I like this question. The answer is yes. Let us pretend a 64 year girl has 1 btc in a wallet. Put it in when coins were 32k. Lets say she mines and is clearing 3k a month....... sells 2k holds 1 k Lets say she has a small pension 2k a month Lets say her wife has a good pension 4k a month. Thats right she has a wife. Lets say they have "safe" 401k and IRA worth 350K. Lets say 0 debt Lets say all gear mining is worth 100k Lets say a fixed up home in a low crime area fully paid for is worth 425K How easy is it for her to hodl that 1 btc until she turns 70? really fucking easy. And why is that? ratio of at risk is 32k/37k upside is 250k or more. ratio of safe is over 800k in 2027 In 2027 BTC is way up close to the same or ways down so 10,000 vs 37,000 vs 250,000+ IRA + 401K = 375k with shit interest Home = 500K Yes inflation may eat at the 401k+IRA And home price rise may not do well against inflation but at risk ratio of 37.5/750 is 20 to 1 Very easy to hodl Not is those lucky lesbians have 40 btc right now with the same "safe" money holding is harder since at risk is 40 x 37.5= 1,500,000 to 750,000 I would argue it is the high risk to low risk and you age that determines your hodl ability. |
|
|
|
Hi guys,
I'm from EU and electricity is pretty expensive here. I'm mining at home with 20+ asics now and pretty happy of the returns despite a 0,16€/KWH.
With a friend who is mining at home aswell we want to scale up to a small farm and I've finally managed to find a great elec deal (0,07€/KWH / 1MW) + warehouse but the issue is this place is 2h flight from where I live.
I'm seriously thinking to move on and launch this farm at this location just for my friend & I and maybe other miners.
The warehouse is fine, with cold air, secured with 24 hours guards on site. Just need to hire one or two tech to run the place. I'm just not sure what type of tech I need to recruit. I'm thinking a basic level of IT knowledge & network but maybe I'm wrong because a farm with 300+ Asic is not the same story to run compared to a basement home farm.
Same regarding electricity, as it's a gonna be more "industrial mining" does recruiting a elec tech make sense?
I would be more than happy to get your return of experiences and feelings about that?
Many thanks,
Larson311
you need a few things. a proxy maybe maybe not as it depends if every unit is pointed to 1 spot. But you need remote operations I run a mixed gear mine. I mine with 50 asics. In one location I mine with 75 gpus. In five locations soon to be six. I can access all units via my home pc. As for a direct tech you need an on call guy to manually alter gear when needed. this will be sporadic 1 or 2 times a month maybe more maybe less. He also will need to clean and inspect gear on a 3 to 9 month basis. this is an all day or 2 day job. so it could be 3 x 2 = 6 full days of work. If I recall you have roots or location in Norway. I am USA based but my Grandmother was born in Norway, Oslo. I would be willing to help with setup via PM and Emails. |
|
|
|
Hey guys I just bought a t17 from china and they shipped it over and first thing when I get it and plug it in it only hashs on 2 boards. It can detect the other board I think based off the kernel log, but asic chain 2 0. Ill post the log. Any body found a solution to this or has a idea of what to do next. I have tried new firmware, I have tried control board recovery nothing helps. This is my first 17 series asic so I am not sure if this is normal but when I turn it on both red and green lights are lite up and stay on for about 1 minute then turn off, followed a few minutes later buy a red flashing fault light for a couple minutes until finally it conects and starts flashing green. Very strange to me. Anyways any help would be greatly appriciated. 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: 203752K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25624K 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: 12584K (cceb7000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
nand_read_bbt: bad block at 0x000003200000
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: 30/12, WL threshold: 4096, image sequence number: 365118462
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 D005394B-8B3E-4DDE-A2C3-57B3DB3F6511, 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: 36/17, WL threshold: 4096, image sequence number: 1936447891
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 9ED28435-FE11-449B-88E4-B1986FE094A0, 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 = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2021-08-04 04:18:59 driver-btm-api.c:663:init_freq_mode: This is scan-user version
2021-08-04 04:18:59 driver-btm-api.c:2028:bitmain_soc_init: opt_multi_version = 1
2021-08-04 04:18:59 driver-btm-api.c:2029:bitmain_soc_init: opt_bitmain_ab = 1
2021-08-04 04:18:59 driver-btm-api.c:2030:bitmain_soc_init: opt_bitmain_work_mode = 0
2021-08-04 04:18:59 driver-btm-api.c:2031:bitmain_soc_init: Miner compile time: Thu Apr 23 16:29:07 CST 2020 type: Antminer T17
2021-08-04 04:18:59 driver-btm-api.c:2032:bitmain_soc_init: commit version: 1c5be6f 2020-04-20 16:18:14, build by: lol 2020-04-23 16:35:04
2021-08-04 04:18:59 driver-btm-api.c:1844:show_sn: no SN got, please write SN to /nvdata/sn
2021-08-04 04:18:59 driver-btm-api.c:1167:miner_device_init: Detect 256MB control board of XILINX
2021-08-04 04:18:59 driver-btm-api.c:1115:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2021-08-04 04:18:59 thread.c:885:create_read_nonce_reg_thread: create thread
2021-08-04 04:19:05 driver-btm-api.c:1099:init_miner_version: miner ID : 810865025c208854
2021-08-04 04:19:05 driver-btm-api.c:1105:init_miner_version: FPGA Version = 0xB013
2021-08-04 04:19:07 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2021-08-04 04:19:09 eeprom.c:431:check_pattern_test_level: L1 board
2021-08-04 04:19:11 eeprom.c:431:check_pattern_test_level: L1 board
2021-08-04 04:19:11 driver-btm-api.c:737:get_product_id: product_id[0] = 1
2021-08-04 04:19:11 driver-btm-api.c:737:get_product_id: product_id[1] = 1
2021-08-04 04:19:11 driver-btm-api.c:737:get_product_id: product_id[2] = 1
2021-08-04 04:19:11 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[0] = 1
2021-08-04 04:19:11 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[1] = 1
2021-08-04 04:19:11 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[2] = 1
2021-08-04 04:19:11 driver-btm-api.c:1919:bitmain_board_init: g_ccdly_opt = 1
2021-08-04 04:19:11 driver-btm-api.c:676:_set_project_type: project:2
2021-08-04 04:19:11 driver-btm-api.c:706:_set_project_type: Project type: Antminer T17
2021-08-04 04:19:11 driver-btm-api.c:717:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2021-08-04 04:19:11 driver-btm-api.c:718:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2021-08-04 04:19:11 driver-btm-api.c:717:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2021-08-04 04:19:11 driver-btm-api.c:718:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2021-08-04 04:19:11 driver-btm-api.c:717:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2021-08-04 04:19:11 driver-btm-api.c:718:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2021-08-04 04:19:12 driver-btm-api.c:1939:bitmain_board_init: Fan check passed.
2021-08-04 04:19:12 register.c:306:get_register: !!! reg crc error
2021-08-04 04:19:13 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-08-04 04:19:17 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2021-08-04 04:19:19 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-08-04 04:19:22 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2021-08-04 04:19:24 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-08-04 04:19:27 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2021-08-04 04:19:27 thread.c:880:create_pic_heart_beat_thread: create thread
2021-08-04 04:19:27 power_api.c:55:power_init: power init ...
2021-08-04 04:19:27 driver-btm-api.c:1949:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-08-04 04:19:59 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2021-08-04 04:20:05 power_api.c:124:check_voltage_multi: retry time: 0
2021-08-04 04:20:07 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.144531
2021-08-04 04:20:09 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.181269
2021-08-04 04:20:10 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.175146
2021-08-04 04:20:10 power_api.c:97:get_average_voltage: aveage voltage is: 17.166982
2021-08-04 04:20:10 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2021-08-04 04:20:10 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-08-04 04:20:22 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2021-08-04 04:20:32 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2021-08-04 04:20:42 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2021-08-04 04:20:51 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2021-08-04 04:21:01 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2021-08-04 04:21:01 driver-btm-api.c:1069:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2021-08-04 04:21:05 driver-btm-api.c:352:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2021-08-04 04:21:05 driver-btm-api.c:352:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2021-08-04 04:21:06 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0xb4
2021-08-04 04:21:06 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2021-08-04 04:21:06 driver-btm-api.c:1693:check_clock_counter: freq 50 clock_counter_limit 6
2021-08-04 04:21:06 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-08-04 04:21:06 voltage[0] = 1690
2021-08-04 04:21:06 voltage[1] = 1690
2021-08-04 04:21:06 power_api.c:140:set_working_voltage: working_voltage = 16.900000
2021-08-04 04:21:07 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2021-08-04 04:21:09 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2021-08-04 04:21:09 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2021-08-04 04:21:10 driver-btm-api.c:252:check_bringup_temp: Bring up temperature is 26
2021-08-04 04:21:10 thread.c:900:create_check_miner_status_thread: create thread
2021-08-04 04:21:10 thread.c:890:create_set_miner_status_thread: create thread
2021-08-04 04:21:10 driver-btm-api.c:613:calculate_timeout: dev->timeout = 392
2021-08-04 04:21:10 thread.c:875:create_temperature_monitor_thread: create thread
2021-08-04 04:21:10 freq_tuning.c:159:freq_tuning_get_max_freq: Max freq of tuning is 760
2021-08-04 04:21:10 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.80 ...
2021-08-04 04:21:41 power_api.c:124:check_voltage_multi: retry time: 0
2021-08-04 04:21:43 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.940527
2021-08-04 04:21:45 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.014004
2021-08-04 04:21:45 power_api.c:97:get_average_voltage: aveage voltage is: 17.977265 fixed your log you should ask for a 33% refund. let us know the seller and let us know if the seller gives a refund |
|
|
|
And back on the horse. we are up 6% https://www.bitrawr.com/difficulty-estimator... Latest Block: 694017 (2 minutes ago) Current Pace: 106.1802% (514 / 484.08 expected, 29.92 ahead)Previous Difficulty: 13672594272814.14 Current Difficulty: 14496442856349.12 Next Difficulty: between 14893536416259 and 15420537890085 Next Difficulty Change: between +2.7392% and +6.3746% Previous Retarget: last Saturday at 12:26 AM (+6.0255%) Next Retarget (earliest): August 13, 2021 at 4:53 AM (in 9d 19h 45m 46s) Next Retarget (latest): August 13, 2021 at 3:44 PM (in 10d 6h 37m 6s) Projected Epoch Length: between 13d 4h 26m 35s and 13d 15h 17m 56s ... so back to back 6% jumps may happen While I would have wanted back to back 2-4% jumps This shows some large players have some faith in mining. Even if we go to a diff of 15.4. it is way lower than the high of 25.03 So just think steady 6% for Aug 13 - Oct 25 we would be at 20.6 and tack on steady 6% oct to jan 1 we would be at a new high say 27.4 Have to watch the next 3 jumps closely. Along with price. |
|
|
|
..... gembitz is active again, is that a good or bad sign?
Rather than being either good or bad, it's probably a wee sign. ..... that made me chuckle, jay, then I almost weed. no wait...actually I grow weed.... ....Alfred farted with such force .....
This stopped my scanning in its trax and made me read the whole post.... .....
Any sm post always stops me scanning... .....
Dude seriously... get rid of that that "need 3 btc... urgently" nonsense in your avatar. Its not doing you any favors. If I had 10,000 btc to my name, I would not give you a single sat. And I'm pretty sure no one else would either in this thread. Quit begging. I have considered point 0.01 btc at ck solo pool on a rental. and giving him eXPHorizon 0.0625 btc if the block hits. but he would still most likely bitch and moan that I made 6.10 btc off him if I hit the block. |
|
|
|
Piece of advice... Don't scrimp on the fans, I learned this the hard way. Cheap extraction fans aren't designed to run 24/7 with hot airflow and they will burn out quickly, even when over-specced.
If your budget will allow, go for 3-phase fans, specced well above the airflow requirement and with a transformer-based controller.
I'm currently looking at 2x 36" 1/2HP fans from Hessaire. Has decent reviews and at 350/unit its not terrible either. They're spec'd to 11000CFM each, so should be good? are they both for out flow? 100 s9 units are about 100 x 220 = 22000 cfm on the little unit fans. So 11000 cfm in and 11000 cfm out is not enough. 22000 cfm out works. passive intake is okay if big enough and filtered. we use metal reusable filters like these: https://www.mcmaster.com/air-filters/heavy-duty-reusable-metal-panel-filters-11/or these https://www.mcmaster.com/air-filters/made-to-order-heavy-duty-reusable-metal-panel-filters/these save a fortune in replacement costs. you still may need to clean your s9's every 3 to 6 months. We have a very dirty environment out side of the mining room. So we clean the metal filters monthly and we clean the gear every 100 days. |
|
|
|
oh damn, thats a deal Thanks! Now I just gotta find 2 decent exhaust fans and I should be set  note how to access with a pc on site and anydesk oh any cheap monitor keyboard mouse for the pc is good. When you work on site and not remote. I love our remote setup we can go months with out going on site. |
|
|
|
Hey guys,
I secured a location today to set up a new farm - starting out with 100x S9 miners.
Electrical / cooling is pretty much figured out.
Setting up 2x 50 miners shelves - each has a 4ft (15000CFM) exhaust fan that airs the hot air out and each miner has a separate breaker outlet.
Only thing I'm wondering is how to best connect ethernet?
Thinking of a Asus RT-AC66U B1 that has built in VPN so I can control remotely, but how am I getting all miners connected?
TL-SG116 16-port switches are very cheap, but running 7 of them ? Setting them up as a tree?
Basically 3 switches straight to the router ... that gives me 3x16 miners (48)
On the 4th port another switch and connect (up to 16) switches there? Onto those switches the rest of the miners?
thanks
get 48 port used switches. let me find you a link I DID NOT USE THIS GUY https://www.ebay.com/itm/274885548805?BECAUSE: I grabbed 4 from the guy below. His shop is under 2 miles from my farm https://www.ebay.com/itm/292503559584?He is in New Jersey USE a pc like this https://www.ebay.com/itm/313624762269?connect with a remote desk top app like this https://anydesk.com/en |
|
|
|
I hope you guys are seeing what i am seeing. That is all i have to say and that is all is needed to be said.
Yeah I see you refusing to dca day after day. |
|
|
|
|
buddy lets get a lift please.
|
|
|
|
|
My fail is Early this year we were about 64-65 k and I guarantied 70 by may
So this is penance of a sort.
I mostly mine and btc at 41k with a difficulty of 14.3
Is better for me then 64k with a difficulty of 25.03
So I am in constant bull mode. Since last Novemeber.
|
|
|
|
One of my cards was running hot so I took it apart to see what was going on and discovered a crater maybe 2mm wide and maybe 50-100 microns deep in both the heatsink and the GPU. It's like some tiny people let off a tiny stick of dynamite and made this not-so-tiny crater.
Card works totally fine except for getting hot. How to fix? Sandpaper?
photo would help. i would not sand the gpu chip. maybe the heatsink can be buffed flat and load the groove on the gpu chip with extra heat sink paste. |
|
|
|
Well, you are both wrong.  Bitcoin price is unpredictable and it depends on the trend that will come, --sounds like if there is another institution that announced an adoption. However, my real belief is bitcoin price road to $50k with in this month, that is my opinion and there is nothing you can do.  Let us hope there is another good news will come so that the price will not have a correction by this time. yeah we could say 45k and 50k or even go all out and say 66k. But for now 40k works. Remember this is about proudhon and his btc posting. Not about my posting or beliefs at all. Aug 4 will knock out his 35k thread 🧵. ( I hope ). My 40k thread will be wrong on my 35th wedding anniversary aug 9th. [I hope]! |
|
|
|
...
Wrong. Sorry guys.
Bitcoin will not be able to stay above $45K for 10 consecutive days ever again.
Better sell. Science and maths. You know the drill.
No you have to wait for the 35k to drop. then you can do the 45k thread. my 40k thread has replaced the 30k thread since it is dead. August 4 knocks off the 35k thread. you can jump in with your 45k thread then. We must be orderly about this.  |
|
|
|
|
and buddy is starting his lift towards 45k
|
|
|
|
Soon ya will witness the Picture. And the loss will be in Trillions Edit: Sorry Arrie, i broke the Order of being Quiet Another Edit... Arrie is the type of a Guy id take orders from so respect the lad Last I looked BTC is not worth trillions. In fact the entire crypto market is worth : "The global crypto market cap is $1.64T, a 1.87% increase over the last day.Read more" a quote from coinmarket cap. ( I apoligize JJG but need to use all coins to make this point) So I guess Stocks ,precious metals, real estate and or cash are getting crushed soon. All losing trillions against BTC value. |
|
|
|
One of those successful cases of bitcoin hodling was a friend of a friend. They (a couple) took an important risk by investing 60k of a dismissal compensation into bitcoin and making a x100 on it before selling half. I do not know what they did with the rest. Now, these people were not rich, they took an enormous risk compared to their total wealth. They had to really believe on the project and pass though some of bitcoins usual "tests of faith".
For someone with let´s say, a net worth of 1M USD or more plus house, hodling 60k until they became 6M would have been not that much of an stress. Do you think it was easier to benefit economically from bitcoin if you were already a bit up in the ladder?
No I do not think that at all. I know it is easier which is always true when you are far enough ahead in any game. |
|
|
|
Now that we've proven Godwin's law....in real news, bitcoin's looking as bullish as a bovine with two dicks.
Yeah, I’m not vaccinated, I have huge doubts about the severity of covid & what the real agenda might be but FFS, can we leave that shit out of the WO. So about bitcoin, $45,000 next week, maybe? I'll wait a few more hours if the latest pump doesn't form another bart, but if not, i guess YES too late I opened this thread below: Re: Bitcoin will not be able to stay above $40K for 10 consecutive days ever again! Note in response to proudhon's
threads for 35k and 30k
I entered a preemptive strike. I did a thread for 40k
to quote him
"This is too easy"
Note this is an homage to his persistent attacks on BTC price.
My real belief is mine on! Which is what I do.
|
|
|
|
|
Note in response to proudhon's
threads for 35k and 30k
I entered a preemptive strike. I did a thread for 40k
to quote him
"This is too easy"
Note this is an homage to his persistent attacks on BTC price.
My real belief is mine on! Which is what I do.
|
|
|
|
|
Thank you I just sent an email.
|
|
|
|
|
Show Posts
