Latest posts of: mikeywith

Show Posts
Pages: « 1 ... 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 [232] 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 ... 408 »

4621

Bitcoin / Mining support / Re: Antminer S9 SE 17TH

on: February 18, 2020, 02:52:21 AM

Below is the kernel log of one of my S9E 16Th version

Code:


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: 198656K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 30720K 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: 17680K (cc9bc000 - 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)
Broadcom BCM5241 e000b000.etherne:00: attached PHY driver [Broadcom BCM5241] (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: 16/7, WL threshold: 4096, image sequence number: 416762856
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 84A07273-7DB4-4D10-BFAD-008C5D5B6CDF, 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: 725/194, WL threshold: 4096, image sequence number: 1746335632
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 92A8FA43-575C-4006-B303-EDE1C509283D, 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 0xcfb34000
*base_vir_addr = 0xab00d
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
 [1970-01-01 00:00:53.733] httpListenThread start ret=0
 [1970-01-01 00:01:23.733] start listen on 6060 ...
 [1970-01-01 00:05:54.563] setStartTimePoint total_tv_start_sys=355 total_tv_end_sys=356

1970-01-01 00:00:53 driver-btm-soc.c:6490:bitmain_soc_init: This is Antminer S9 SE scan user version
1970-01-01 00:00:53 driver-btm-soc.c:6496:bitmain_soc_init: special mode: disabled
1970-01-01 00:00:53 driver-btm-soc.c:6503:bitmain_soc_init: This is high performance mode
1970-01-01 00:00:53 driver-btm-soc.c:6508:bitmain_soc_init: last commit version: a70ae17 commit time: 2019-07-10 21:53:39 build: 2019-07-11 11:18:49
1970-01-01 00:00:53 driver-btm-soc.c:6529:bitmain_soc_init: Detect 256MB control board of XILINX
1970-01-01 00:00:53 driver-btm-soc.c:6532:bitmain_soc_init: Miner compile time: Thu Jul 11 11:11:08 CST 2019 type: Antminer S9 SE
1970-01-01 00:00:53 driver-btm-soc.c:838:check_chain: get_hash_on_plug is 0x7
1970-01-01 00:00:53 driver-btm-soc.c:850:check_chain: !! chain[0]is exist
1970-01-01 00:00:53 driver-btm-soc.c:850:check_chain: !! chain[1]is exist
1970-01-01 00:00:53 driver-btm-soc.c:850:check_chain: !! chain[2]is exist
         00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
00000000 7e ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000010 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000020 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000030 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000040 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000050 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000060 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000070 ff ff ff ff ff ff ff ff   ff 01 02 1f fc 28 fc ff
00000080 ff ff ff ff ff ff ff a5   57 57 57 57 57 57 57 57
00000090 54 52 52 57 57 54 57 57   57 57 57 57 57 57 57 57
000000a0 57 57 57 57 54 52 52 54   57 57 57 57 57 57 57 57
000000b0 57 57 57 57 57 57 57 57   54 52 52 54 57 57 57 57
000000c0 57 57 57 57 00 ff ff ff   ff ff ff ff ff ff ff ff
000000d0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000e0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000f0 ff ff ff ff 00 15 00 00   60 ff ff ff 39 10 87 4a
         00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
00000000 7e ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000010 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000020 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000030 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000040 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000050 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000060 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000070 ff ff ff ff ff ff ff ff   ff 01 02 1f fc 28 fc ff
00000080 ff ff ff ff ff ff ff a5   57 57 57 57 57 57 54 4c
00000090 54 52 4c 54 54 57 57 52   57 57 57 57 57 57 57 57
000000a0 57 57 54 54 52 4c 4c 52   54 54 57 57 57 57 57 57
000000b0 52 57 57 57 57 54 57 57   54 4c 4c 52 54 54 57 57
000000c0 57 57 57 57 00 ff ff ff   ff ff ff ff ff ff ff ff
000000d0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000e0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000f0 ff ff ff ff a9 14 00 00   60 ff ff ff 39 10 c9 cc
         00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
00000000 7e ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000010 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000020 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000030 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000040 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000050 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000060 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000070 ff ff ff ff ff ff ff ff   ff 01 02 1f fc 28 fd ff
00000080 ff ff ff ff ff ff ff a5   58 58 58 58 58 58 58 58
00000090 58 55 55 58 58 58 58 58   58 58 58 58 58 58 58 58
000000a0 58 58 58 58 58 55 55 58   58 58 58 58 58 58 58 58
000000b0 58 58 58 58 58 58 58 58   58 55 55 58 58 58 58 58
000000c0 58 58 58 58 00 ff ff ff   ff ff ff ff ff ff ff ff
000000d0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000e0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000f0 ff ff ff ff 5e 15 00 00   60 ff ff ff 39 10 a3 23

read chain[0] hardware info:
major type: 0
minor type: 4
chip level: 1
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

read chain[1] hardware info:
major type: 0
minor type: 4
chip level: 1
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

read chain[2] hardware info:
major type: 0
minor type: 4
chip level: 1
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

sweep config for eco mode: 
sweep_start_voltage: 8.60
max_aging_voltage:   8.90
sweep_min_freq:      300M
sweep_max_freq:      380M

sweep config for hpf mode: 
sweep_start_voltage: 9.30
max_aging_voltage:   9.60
sweep_min_freq:      415M
sweep_max_freq:      465M
1970-01-01 00:01:05 driver-btm-soc.c:838:check_chain: get_hash_on_plug is 0x7
1970-01-01 00:01:05 driver-btm-soc.c:850:check_chain: !! chain[0]is exist
1970-01-01 00:01:05 driver-btm-soc.c:850:check_chain: !! chain[1]is exist
1970-01-01 00:01:05 driver-btm-soc.c:850:check_chain: !! chain[2]is exist
1970-01-01 00:01:05 driver-btm-soc.c:5935:get_freq_result_from_eeprom: orginal chip freq: 
chain 0 freq:
435 435 435 435 435 435 435 435 420 410 
410 435 435 420 435 435 435 435 435 435 
435 435 435 435 435 435 435 435 420 410 
410 420 435 435 435 435 435 435 435 435 
435 435 435 435 435 435 435 435 420 410 
410 420 435 435 435 435 435 435 435 435 

chain 1 freq:
435 435 435 435 435 435 420 380 420 410 
380 420 420 435 435 410 435 435 435 435 
435 435 435 435 435 435 420 420 410 380 
380 410 420 420 435 435 435 435 435 435 
410 435 435 435 435 420 435 435 420 380 
380 410 420 420 435 435 435 435 435 435 

chain 2 freq:
440 440 440 440 440 440 440 440 440 425 
425 440 440 440 440 440 440 440 440 440 
440 440 440 440 440 440 440 440 440 425 
425 440 440 440 440 440 440 440 440 440 
440 440 440 440 440 440 440 440 440 425 
425 440 440 440 440 440 440 440 440 440 

1970-01-01 00:01:05 driver-btm-soc.c:6618:bitmain_soc_init: reset all...
1970-01-01 00:01:07 driver-btm-soc.c:6626:bitmain_soc_init: miner ID : 807875c81540885c
1970-01-01 00:01:07 driver-btm-soc.c:6329:init_miner_version: FPGA Version = 0xB00D
1970-01-01 00:01:26 dspic33ep16gs202.c:486:get_pic_software_version_all_chain: chain[0] PIC software version: 177
1970-01-01 00:01:27 dspic33ep16gs202.c:486:get_pic_software_version_all_chain: chain[1] PIC software version: 177
1970-01-01 00:01:28 dspic33ep16gs202.c:486:get_pic_software_version_all_chain: chain[2] PIC software version: 177
1970-01-01 00:01:28 power.c:183:power_init: power init ... 
1970-01-01 00:01:28 driver-btm-soc.c:5048:get_working_voltage_from_eeprom: get working vol [ 9.60] from chain[0] eeprom
1970-01-01 00:01:28 power.c:230:set_working_voltage_by_chain: chain[0] working_voltage = 9.600000
1970-01-01 00:01:28 driver-btm-soc.c:5048:get_working_voltage_from_eeprom: get working vol [ 9.60] from chain[1] eeprom
1970-01-01 00:01:28 power.c:230:set_working_voltage_by_chain: chain[1] working_voltage = 9.600000
1970-01-01 00:01:28 driver-btm-soc.c:5048:get_working_voltage_from_eeprom: get working vol [ 9.60] from chain[2] eeprom
1970-01-01 00:01:28 power.c:230:set_working_voltage_by_chain: chain[2] working_voltage = 9.600000
1970-01-01 00:01:28 driver-btm-soc.c:5724:update_highest_voltage: chain 0 hpf working voltage 9.30
1970-01-01 00:01:28 driver-btm-soc.c:5724:update_highest_voltage: chain 1 hpf working voltage 9.30
1970-01-01 00:01:28 driver-btm-soc.c:5724:update_highest_voltage: chain 2 hpf working voltage 9.30
1970-01-01 00:01:28 driver-btm-soc.c:5733:update_highest_voltage: open core at max voltage 10.04
1970-01-01 00:01:28 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[0] setting to hightest voltage: 10.04 ...
1970-01-01 00:01:28 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.044000 
1970-01-01 00:01:29 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[1] setting to hightest voltage: 10.04 ...
1970-01-01 00:01:31 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.044000 
1970-01-01 00:01:31 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[2] setting to hightest voltage: 10.04 ...
1970-01-01 00:01:32 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.044000 
1970-01-01 00:01:32 driver-btm-soc.c:1186:get_eeprom_total_hash_rate: chain[0] hash rate = 5376
1970-01-01 00:01:32 driver-btm-soc.c:1186:get_eeprom_total_hash_rate: chain[1] hash rate = 5289
1970-01-01 00:01:32 driver-btm-soc.c:1186:get_eeprom_total_hash_rate: chain[2] hash rate = 5470
1970-01-01 00:01:32 driver-btm-soc.c:1190:get_eeprom_total_hash_rate: total rate = 16135
1970-01-01 00:01:32 driver-btm-soc.c:1198:get_ideal_hash_rate: get ideal hash rate 16000
1970-01-01 00:01:32 eeprom.c:665:travel_eeprom_store: chain[0] data in eeprom is:
magic number: 0x7e
freq data per ASIC:
IC[000]:1275 IC[001]:1275 IC[002]:1275 IC[003]:1275 IC[004]:1275 IC[005]:1275 IC[006]:1275 IC[007]:1275 IC[008]:1275 IC[009]:1275 
IC[010]:1275 IC[011]:1275 IC[012]:1275 IC[013]:1275 IC[014]:1275 IC[015]:1275 IC[016]:1275 IC[017]:1275 IC[018]:1275 IC[019]:1275 
IC[020]:1275 IC[021]:1275 IC[022]:1275 IC[023]:1275 IC[024]:1275 IC[025]:1275 IC[026]:1275 IC[027]:1275 IC[028]:1275 IC[029]:1275 
IC[030]:1275 IC[031]:1275 IC[032]:1275 IC[033]:1275 IC[034]:1275 IC[035]:1275 IC[036]:1275 IC[037]:1275 IC[038]:1275 IC[039]:1275 
IC[040]:1275 IC[041]:1275 IC[042]:1275 IC[043]:1275 IC[044]:1275 IC[045]:1275 IC[046]:1275 IC[047]:1275 IC[048]:1275 IC[049]:1275 
IC[050]:1275 IC[051]:1275 IC[052]:1275 IC[053]:1275 IC[054]:1275 IC[055]:1275 IC[056]:1275 IC[057]:1275 IC[058]:1275 IC[059]:1275 
voltage: 11.10 V
hash rate: -0001 GH/s

freq data per ASIC in mode2:
IC[000]:435 IC[001]:435 IC[002]:435 IC[003]:435 IC[004]:435 IC[005]:435 IC[006]:435 IC[007]:435 IC[008]:420 IC[009]:410 
IC[010]:410 IC[011]:435 IC[012]:435 IC[013]:420 IC[014]:435 IC[015]:435 IC[016]:435 IC[017]:435 IC[018]:435 IC[019]:435 
IC[020]:435 IC[021]:435 IC[022]:435 IC[023]:435 IC[024]:435 IC[025]:435 IC[026]:435 IC[027]:435 IC[028]:420 IC[029]:410 
IC[030]:410 IC[031]:420 IC[032]:435 IC[033]:435 IC[034]:435 IC[035]:435 IC[036]:435 IC[037]:435 IC[038]:435 IC[039]:435 
IC[040]:435 IC[041]:435 IC[042]:435 IC[043]:435 IC[044]:435 IC[045]:435 IC[046]:435 IC[047]:435 IC[048]:420 IC[049]:410 
IC[050]:410 IC[051]:420 IC[052]:435 IC[053]:435 IC[054]:435 IC[055]:435 IC[056]:435 IC[057]:435 IC[058]:435 IC[059]:435 
voltage in mode2: 9.30 V
hash rate in mode2: 05376 GH/s

1970-01-01 00:01:32 eeprom.c:665:travel_eeprom_store: chain[1] data in eeprom is:
magic number: 0x7e
freq data per ASIC:
IC[000]:1275 IC[001]:1275 IC[002]:1275 IC[003]:1275 IC[004]:1275 IC[005]:1275 IC[006]:1275 IC[007]:1275 IC[008]:1275 IC[009]:1275 
IC[010]:1275 IC[011]:1275 IC[012]:1275 IC[013]:1275 IC[014]:1275 IC[015]:1275 IC[016]:1275 IC[017]:1275 IC[018]:1275 IC[019]:1275 
IC[020]:1275 IC[021]:1275 IC[022]:1275 IC[023]:1275 IC[024]:1275 IC[025]:1275 IC[026]:1275 IC[027]:1275 IC[028]:1275 IC[029]:1275 
IC[030]:1275 IC[031]:1275 IC[032]:1275 IC[033]:1275 IC[034]:1275 IC[035]:1275 IC[036]:1275 IC[037]:1275 IC[038]:1275 IC[039]:1275 
IC[040]:1275 IC[041]:1275 IC[042]:1275 IC[043]:1275 IC[044]:1275 IC[045]:1275 IC[046]:1275 IC[047]:1275 IC[048]:1275 IC[049]:1275 
IC[050]:1275 IC[051]:1275 IC[052]:1275 IC[053]:1275 IC[054]:1275 IC[055]:1275 IC[056]:1275 IC[057]:1275 IC[058]:1275 IC[059]:1275 
voltage: 11.10 V
hash rate: -0001 GH/s

freq data per ASIC in mode2:
IC[000]:435 IC[001]:435 IC[002]:435 IC[003]:435 IC[004]:435 IC[005]:435 IC[006]:420 IC[007]:380 IC[008]:420 IC[009]:410 
IC[010]:380 IC[011]:420 IC[012]:420 IC[013]:435 IC[014]:435 IC[015]:410 IC[016]:435 IC[017]:435 IC[018]:435 IC[019]:435 
IC[020]:435 IC[021]:435 IC[022]:435 IC[023]:435 IC[024]:435 IC[025]:435 IC[026]:420 IC[027]:420 IC[028]:410 IC[029]:380 
IC[030]:380 IC[031]:410 IC[032]:420 IC[033]:420 IC[034]:435 IC[035]:435 IC[036]:435 IC[037]:435 IC[038]:435 IC[039]:435 
IC[040]:410 IC[041]:435 IC[042]:435 IC[043]:435 IC[044]:435 IC[045]:420 IC[046]:435 IC[047]:435 IC[048]:420 IC[049]:380 
IC[050]:380 IC[051]:410 IC[052]:420 IC[053]:420 IC[054]:435 IC[055]:435 IC[056]:435 IC[057]:435 IC[058]:435 IC[059]:435 
voltage in mode2: 9.30 V
hash rate in mode2: 05289 GH/s

1970-01-01 00:01:32 eeprom.c:665:travel_eeprom_store: chain[2] data in eeprom is:
magic number: 0x7e
freq data per ASIC:
IC[000]:1275 IC[001]:1275 IC[002]:1275 IC[003]:1275 IC[004]:1275 IC[005]:1275 IC[006]:1275 IC[007]:1275 IC[008]:1275 IC[009]:1275 
IC[010]:1275 IC[011]:1275 IC[012]:1275 IC[013]:1275 IC[014]:1275 IC[015]:1275 IC[016]:1275 IC[017]:1275 IC[018]:1275 IC[019]:1275 
IC[020]:1275 IC[021]:1275 IC[022]:1275 IC[023]:1275 IC[024]:1275 IC[025]:1275 IC[026]:1275 IC[027]:1275 IC[028]:1275 IC[029]:1275 
IC[030]:1275 IC[031]:1275 IC[032]:1275 IC[033]:1275 IC[034]:1275 IC[035]:1275 IC[036]:1275 IC[037]:1275 IC[038]:1275 IC[039]:1275 
IC[040]:1275 IC[041]:1275 IC[042]:1275 IC[043]:1275 IC[044]:1275 IC[045]:1275 IC[046]:1275 IC[047]:1275 IC[048]:1275 IC[049]:1275 
IC[050]:1275 IC[051]:1275 IC[052]:1275 IC[053]:1275 IC[054]:1275 IC[055]:1275 IC[056]:1275 IC[057]:1275 IC[058]:1275 IC[059]:1275 
voltage: 11.10 V
hash rate: -0001 GH/s

freq data per ASIC in mode2:
IC[000]:440 IC[001]:440 IC[002]:440 IC[003]:440 IC[004]:440 IC[005]:440 IC[006]:440 IC[007]:440 IC[008]:440 IC[009]:425 
IC[010]:425 IC[011]:440 IC[012]:440 IC[013]:440 IC[014]:440 IC[015]:440 IC[016]:440 IC[017]:440 IC[018]:440 IC[019]:440 
IC[020]:440 IC[021]:440 IC[022]:440 IC[023]:440 IC[024]:440 IC[025]:440 IC[026]:440 IC[027]:440 IC[028]:440 IC[029]:425 
IC[030]:425 IC[031]:440 IC[032]:440 IC[033]:440 IC[034]:440 IC[035]:440 IC[036]:440 IC[037]:440 IC[038]:440 IC[039]:440 
IC[040]:440 IC[041]:440 IC[042]:440 IC[043]:440 IC[044]:440 IC[045]:440 IC[046]:440 IC[047]:440 IC[048]:440 IC[049]:425 
IC[050]:425 IC[051]:440 IC[052]:440 IC[053]:440 IC[054]:440 IC[055]:440 IC[056]:440 IC[057]:440 IC[058]:440 IC[059]:440 
voltage in mode2: 9.30 V
hash rate in mode2: 05470 GH/s

1970-01-01 00:01:32 driver-btm-soc.c:6669:bitmain_soc_init: fan_eft : 1  fan_pwm : 90
1970-01-01 00:01:32 driver-btm-soc.c:6358:bring_up_chain: 

bring up chain 0
1970-01-01 00:01:33 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000ffff
1970-01-01 00:02:04 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
1970-01-01 00:02:06 driver-btm-soc.c:3991:check_asic_num: without pre_open_core chain 0, find asic num = 60
1970-01-01 00:02:09 driver-btm-soc.c:4804:set_freq_by_chain: chain[0] set freq:100.00
1970-01-01 00:02:10 driver-btm-soc.c:3917:pre_open_core_one_chain: for chain 0
1970-01-01 00:02:10 driver-btm-soc.c:4078:set_clock_delay_control: core_data = 0x06
1970-01-01 00:02:10 temperature.c:604:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
1970-01-01 00:02:10 temperature.c:513:is_tempsensor_data_correct: Bad,temp_info.type = 0
1970-01-01 00:02:10 temperature.c:741:calibration_sensor_offset: chain[0] temp info is bad, reload from eeprom..
sensor type = 1,sensor num = 2
sensor pos: 31  40  0  0  0  0 
sensor offset: -4  -4  0  0  0  0 
1970-01-01 00:02:10 temperature.c:791:calibration_sensor_offset: Chain[0] chip[31] middle temp offset=-4, typeID=55
1970-01-01 00:02:11 temperature.c:791:calibration_sensor_offset: Chain[0] chip[40] middle temp offset=-4, typeID=55
1970-01-01 00:02:11 driver-btm-soc.c:6358:bring_up_chain: 

bring up chain 1
1970-01-01 00:02:12 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
1970-01-01 00:02:44 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
1970-01-01 00:02:45 driver-btm-soc.c:3991:check_asic_num: without pre_open_core chain 1, find asic num = 60
1970-01-01 00:02:48 driver-btm-soc.c:4804:set_freq_by_chain: chain[1] set freq:100.00
1970-01-01 00:02:49 driver-btm-soc.c:3917:pre_open_core_one_chain: for chain 1
1970-01-01 00:02:49 driver-btm-soc.c:4078:set_clock_delay_control: core_data = 0x06
1970-01-01 00:02:49 temperature.c:604:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
1970-01-01 00:02:49 temperature.c:513:is_tempsensor_data_correct: Bad,temp_info.type = 0
1970-01-01 00:02:49 temperature.c:741:calibration_sensor_offset: chain[1] temp info is bad, reload from eeprom..
sensor type = 1,sensor num = 2
sensor pos: 31  40  0  0  0  0 
sensor offset: -4  -4  0  0  0  0 
1970-01-01 00:02:49 temperature.c:791:calibration_sensor_offset: Chain[1] chip[31] middle temp offset=-4, typeID=55
1970-01-01 00:02:50 temperature.c:791:calibration_sensor_offset: Chain[1] chip[40] middle temp offset=-4, typeID=55
1970-01-01 00:02:50 driver-btm-soc.c:6358:bring_up_chain: 

bring up chain 2
1970-01-01 00:02:51 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
1970-01-01 00:03:23 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
1970-01-01 00:03:24 driver-btm-soc.c:3991:check_asic_num: without pre_open_core chain 2, find asic num = 60
1970-01-01 00:03:27 driver-btm-soc.c:4804:set_freq_by_chain: chain[2] set freq:100.00
1970-01-01 00:03:28 driver-btm-soc.c:3917:pre_open_core_one_chain: for chain 2
1970-01-01 00:03:28 driver-btm-soc.c:4078:set_clock_delay_control: core_data = 0x06
1970-01-01 00:03:28 temperature.c:604:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
1970-01-01 00:03:28 temperature.c:513:is_tempsensor_data_correct: Bad,temp_info.type = 0
1970-01-01 00:03:28 temperature.c:741:calibration_sensor_offset: chain[2] temp info is bad, reload from eeprom..
sensor type = 1,sensor num = 2
sensor pos: 31  40  0  0  0  0 
sensor offset: -4  -3  0  0  0  0 
1970-01-01 00:03:29 temperature.c:791:calibration_sensor_offset: Chain[2] chip[31] middle temp offset=-4, typeID=55
1970-01-01 00:03:29 temperature.c:791:calibration_sensor_offset: Chain[2] chip[40] middle temp offset=-3, typeID=55
1970-01-01 00:03:29 asic.c:1153:set_baud: set baud=1
1970-01-01 00:03:30 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
1970-01-01 00:03:31 temperature.c:1933:detect_startup_environment_temperature: Environment temperature: [12]
1970-01-01 00:03:31 driver-btm-soc.c:4148:open_core_bm1393: Start Open Core!!
1970-01-01 00:03:37 driver-btm-soc.c:4215:open_core_bm1393: End Open Core!!
1970-01-01 00:03:37 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 125
1970-01-01 00:03:38 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 150
1970-01-01 00:03:39 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 175
1970-01-01 00:03:40 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 200
1970-01-01 00:03:41 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 225
1970-01-01 00:03:42 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 250
1970-01-01 00:03:43 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 275
1970-01-01 00:03:44 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 300
1970-01-01 00:03:45 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 325
1970-01-01 00:03:46 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 350
1970-01-01 00:03:47 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 375
1970-01-01 00:03:48 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 400
1970-01-01 00:03:49 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 410
1970-01-01 00:03:50 driver-btm-soc.c:5365:increase_freq_by_eeprom_slowly_by_chain: max = 435 ,min = 410
1970-01-01 00:03:50 driver-btm-soc.c:5371:increase_freq_by_eeprom_slowly_by_chain: chain[0] increaseing the diff freq ...
1970-01-01 00:03:54 driver-btm-soc.c:5400:increase_freq_by_eeprom_slowly_by_chain: chain 0 final freq setting:
435 435 435 435 435 435 435 435 420 410 
410 435 435 420 435 435 435 435 435 435 
435 435 435 435 435 435 435 435 420 410 
410 420 435 435 435 435 435 435 435 435 
435 435 435 435 435 435 435 435 420 410 
410 420 435 435 435 435 435 435 435 435 
1970-01-01 00:03:54 power.c:1303:slowly_set_working_power_t11: set chain 0 to working voltage:
now setting chain[0]-volt[10.04]-data[014] 
now setting chain[0]-volt[09.99]-data[015] 
now setting chain[0]-volt[09.94]-data[016] 
now setting chain[0]-volt[09.89]-data[017] 
now setting chain[0]-volt[09.85]-data[018] 
now setting chain[0]-volt[09.76]-data[020] 
now setting chain[0]-volt[09.68]-data[022] 
now setting chain[0]-volt[09.65]-data[023] 
now setting chain[0]-volt[09.61]-data[024] 
1970-01-01 00:04:20 power.c:1318:slowly_set_working_power_t11: done!
1970-01-01 00:04:20 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 125
1970-01-01 00:04:21 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 150
1970-01-01 00:04:22 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 175
1970-01-01 00:04:23 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 200
1970-01-01 00:04:24 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 225
1970-01-01 00:04:25 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 250
1970-01-01 00:04:26 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 275
1970-01-01 00:04:27 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 300
1970-01-01 00:04:28 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 325
1970-01-01 00:04:29 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 350
1970-01-01 00:04:30 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 375
1970-01-01 00:04:31 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[1] increase to 380
1970-01-01 00:04:32 driver-btm-soc.c:5365:increase_freq_by_eeprom_slowly_by_chain: max = 435 ,min = 380
1970-01-01 00:04:32 driver-btm-soc.c:5371:increase_freq_by_eeprom_slowly_by_chain: chain[1] increaseing the diff freq ...
1970-01-01 00:04:43 driver-btm-soc.c:5400:increase_freq_by_eeprom_slowly_by_chain: chain 1 final freq setting:
435 435 435 435 435 435 420 380 420 410 
380 420 420 435 435 410 435 435 435 435 
435 435 435 435 435 435 420 420 410 380 
380 410 420 420 435 435 435 435 435 435 
410 435 435 435 435 420 435 435 420 380 
380 410 420 420 435 435 435 435 435 435 
1970-01-01 00:04:43 power.c:1303:slowly_set_working_power_t11: set chain 1 to working voltage:
now setting chain[1]-volt[10.04]-data[014] 
now setting 1970-01-01 00:04:48 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[1] after 3 times try!
chain[1]-volt[09.99]-data[015] 
now setting chain[1]-volt[09.94]-data[016] 
now setting chain[1]-volt[09.89]-data[017] 
now setting chain[1]-volt[09.85]-data[018] 
now setting chain[1]-volt[09.76]-data[020] 
now setting chain[1]-volt[09.68]-data[022] 
now setting chain[1]-volt[09.65]-data[023] 
now setting chain[1]-volt[09.61]-data[024] 
1970-01-01 00:05:10 power.c:1318:slowly_set_working_power_t11: done!
1970-01-01 00:05:10 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 125
1970-01-01 00:05:11 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 150
1970-01-01 00:05:12 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 175
1970-01-01 00:05:13 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 200
1970-01-01 00:05:14 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 225
1970-01-01 00:05:15 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 250
1970-01-01 00:05:16 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 275
1970-01-01 00:05:17 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 300
1970-01-01 00:05:18 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 325
1970-01-01 00:05:19 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 350
1970-01-01 00:05:21 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 375
1970-01-01 00:05:22 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 400
1970-01-01 00:05:23 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[2] increase to 425
1970-01-01 00:05:24 driver-btm-soc.c:5365:increase_freq_by_eeprom_slowly_by_chain: max = 440 ,min = 425
1970-01-01 00:05:24 driver-btm-soc.c:5371:increase_freq_by_eeprom_slowly_by_chain: chain[2] increaseing the diff freq ...
1970-01-01 00:05:27 driver-btm-soc.c:5400:increase_freq_by_eeprom_slowly_by_chain: chain 2 final freq setting:
440 440 440 440 440 440 440 440 440 425 
425 440 440 440 440 440 440 440 440 440 
440 440 440 440 440 440 440 440 440 425 
425 440 440 440 440 440 440 440 440 440 
440 440 440 440 440 440 440 440 440 425 
425 440 440 440 440 440 440 440 440 440 
1970-01-01 00:05:27 power.c:1303:slowly_set_working_power_t11: set chain 2 to working voltage:
now setting chain[2]-volt[10.04]-data[014] 
now setting chain[2]-volt[09.99]-data[015] 
now setting chain[2]-volt[09.94]-data[016] 
now setting chain[2]-volt[09.89]-data[017] 
now setting 1970-01-01 00:05:41 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[2] after 3 times try!
chain[2]-volt[09.85]-data[018] 
now setting chain[2]-volt[09.76]-data[020] 
now setting chain[2]-volt[09.68]-data[022] 
now setting chain[2]-volt[09.65]-data[023] 
now setting 1970-01-01 00:05:53 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[2] after 3 times try!
chain[2]-volt[09.61]-data[024] 
1970-01-01 00:05:54 power.c:1318:slowly_set_working_power_t11: done!
1970-01-01 00:05:54 driver-btm-soc.c:5100:set_timeout: freq 440 final timeout=297
1970-01-01 00:05:54 driver-btm-soc.c:2918:low_temp_process_parm_init: chip miner_type = [4]
1970-01-01 00:05:54 driver-btm-soc.c:2918:low_temp_process_parm_init: chip miner_type = [4]
1970-01-01 00:05:54 driver-btm-soc.c:2918:low_temp_process_parm_init: chip miner_type = [4]
1970-01-01 00:05:54 driver-btm-soc.c:3357:check_system_work: check system thread start...
1970-01-01 00:05:54 driver-btm-soc.c:3374:check_system_work: low_bringup_pcb_temp_threshhold = 28
1970-01-01 00:05:54 driver-btm-soc.c:3375:check_system_work: recovery_working_vol_low_temp = 30, recovery_working_vol_high_temp = 35
1970-01-01 00:05:54 driver-btm-soc.c:3376:check_system_work: delta_voltage = 0.10
1970-01-01 00:05:54 driver-btm-soc.c:6771:bitmain_soc_init: Init done!
1970-01-01 00:05:54 driver-btm-soc.c:7478:bitmain_soc_prepare: bitmain soc init success.
1970-01-01 00:05:55 temperature.c:1402:read_temp_func: bring_up_pcb_temp = 18
1970-01-01 00:05:55 util.c:2178:process_version_mask: Pool 0 Version num is 2
1970-01-01 00:05:55 util.c:2178:process_version_mask: Pool 0 Version num is 2
1970-01-01 00:05:55 driver-btm-soc.c:7153:send_job: Version num 2
1970-01-01 00:06:15 driver-btm-soc.c:3529:check_system_work: set reopen algorith parameters...
1970-01-01 00:10:59 eeprom.c:913:eeprom_get_inbalance_info: error: chain[0] inbalance num is 255, more than MAX_OFFSET 4
1970-01-01 00:10:59 driver-btm-soc.c:2498:is_domain_imbalance: eeprom info not correct! ret = 0, len = 0
1970-01-01 00:10:59 eeprom.c:913:eeprom_get_inbalance_info: error: chain[1] inbalance num is 255, more than MAX_OFFSET 4
1970-01-01 00:10:59 driver-btm-soc.c:2498:is_domain_imbalance: eeprom info not correct! ret = 0, len = 0
1970-01-01 00:10:59 eeprom.c:913:eeprom_get_inbalance_info: error: chain[2] inbalance num is 255, more than MAX_OFFSET 4
1970-01-01 00:10:59 driver-btm-soc.c:2498:is_domain_imbalance: eeprom info not correct! ret = 0, len = 0
1970-01-01 00:10:59 driver-btm-soc.c:2511:is_domain_imbalance: dumping inbalance domain info...
0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  
0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  0 0 0 0  
2020-02-17 18:29:28 temperature.c:1225:process_status_value: Fatal Error: network connection lost!
2020-02-17 18:29:42 log.c:101:_log_update_name: _log_update_name
2020-02-17 18:29:42 log.c:101:_log_update_name: _log_update_name
2020-02-17 18:31:46 driver-btm-soc.c:3711:check_system_work: bring_up_pcb_temp = 18, low_bringup_pcb_temp_threshhold = 28
2020-02-17 18:31:46 driver-btm-soc.c:3712:check_system_work: detecting at 15 minutes
2020-02-17 18:31:46 driver-btm-soc.c:3713:check_system_work: target hash rate = 15840, 5mins avg hash rate = 15587

2020-02-17 18:31:46 driver-btm-soc.c:3734:check_system_work: low temp bing up:[Yes]
2020-02-17 18:31:46 driver-btm-soc.c:3735:check_system_work: low temp running:[No]

2020-02-17 18:31:46 driver-btm-soc.c:3738:check_system_work: Temp Low! Entering Low Environment Handler...
2020-02-17 18:31:46 driver-btm-soc.c:3018:get_compensation_voltage: chip miner_type = [4]
2020-02-17 18:31:46 driver-btm-soc.c:3018:get_compensation_voltage: chip miner_type = [4]
2020-02-17 18:31:46 driver-btm-soc.c:3018:get_compensation_voltage: chip miner_type = [4]
2020-02-17 18:31:46 driver-btm-soc.c:3026:get_compensation_voltage: last_testpatten_lowest_pcb_temp = 20
2020-02-17 18:31:46 driver-btm-soc.c:3027:get_compensation_voltage: max_delta_vol =  0.10
2020-02-17 18:31:46 driver-btm-soc.c:3190:get_compensation_voltage: chain[0] working vol =  9.60, add vol =  0.10... 
2020-02-17 18:31:46 driver-btm-soc.c:3190:get_compensation_voltage: chain[1] working vol =  9.60, add vol =  0.10... 
2020-02-17 18:31:46 driver-btm-soc.c:3190:get_compensation_voltage: chain[2] working vol =  9.60, add vol =  0.10... 
2020-02-17 18:31:46 driver-btm-soc.c:6960:re_open_core_by_chain: 

reopen chain 0, current pwm 90
2020-02-17 18:31:48 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[0] setting to hightest voltage: 10.04 ...
2020-02-17 18:31:50 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.044000 
2020-02-17 18:31:50 asic.c:1176:set_baud_by_chain: chain 0 set baud=26
2020-02-17 18:31:50 driver-btm-soc.c:6358:bring_up_chain: 

bring up chain 0
2020-02-17 18:31:50 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2020-02-17 18:31:51 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-02-17 18:31:53 driver-btm-soc.c:3991:check_asic_num: without pre_open_core chain 0, find asic num = 60
2020-02-17 18:31:56 driver-btm-soc.c:4804:set_freq_by_chain: chain[0] set freq:100.00
2020-02-17 18:31:57 driver-btm-soc.c:3917:pre_open_core_one_chain: for chain 0
2020-02-17 18:31:57 driver-btm-soc.c:4078:set_clock_delay_control: core_data = 0x06
2020-02-17 18:31:57 temperature.c:604:is_eeprom_tempsensor_data_correct: sensor_num 2, sensor pos = 31, 40, 0, 0
2020-02-17 18:31:57 temperature.c:791:calibration_sensor_offset: Chain[0] chip[31] middle temp offset=-4, typeID=55
2020-02-17 18:31:58 temperature.c:791:calibration_sensor_offset: Chain[0] chip[40] middle temp offset=-4, typeID=55
2020-02-17 18:31:58 asic.c:1176:set_baud_by_chain: chain 0 set baud=1
2020-02-17 18:31:58 asic.c:1269:set_asic_ticket_mask: set ticket mask 63
2020-02-17 18:31:58 driver-btm-soc.c:4148:open_core_bm1393: Start Open Core!!
2020-02-17 18:32:00 driver-btm-soc.c:4215:open_core_bm1393: End Open Core!!
2020-02-17 18:32:01 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 125
2020-02-17 18:32:02 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 150
2020-02-17 18:32:03 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 175
2020-02-17 18:32:04 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 200
2020-02-17 18:32:05 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 225
2020-02-17 18:32:06 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 250
2020-02-17 18:32:07 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 275
2020-02-17 18:32:08 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 300
2020-02-17 18:32:09 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 325
2020-02-17 18:32:10 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 350
2020-02-17 18:32:11 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 375
2020-02-17 18:32:12 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 400
2020-02-17 18:32:13 driver-btm-soc.c:5355:increase_freq_by_eeprom_slowly_by_chain: chain[0] increase to 410
2020-02-17 18:32:14 driver-btm-soc.c:5365:increase_freq_by_eeprom_slowly_by_chain: max = 435 ,min = 410
2020-02-17 18:32:14 driver-btm-soc.c:5371:increase_freq_by_eeprom_slowly_by_chain: chain[0] increaseing the diff freq ...
2020-02-17 18:32:18 driver-btm-soc.c:5400:increase_freq_by_eeprom_slowly_by_chain: chain 0 final freq setting:
435 435 435 435 435 435 435 435 420 410 
410 435 435 420 435 435 435 435 435 435 
435 435 435 435 435 435 435 435 420 410 
410 420 435 435 435 435 435 435 435 435 
435 435 435 435 435 435 435 435 420 410 
410 420 435 435 435 435 435 435 435 435 
2020-02-17 18:32:18 driver-btm-soc.c:5100:set_timeout: freq 440 final timeout=297
2020-02-17 18:32:19 driver-btm-soc.c:6987:re_open_core_by_chain: reopen chain 0 finished, chain 0 chip temp 41 - 60
2020-02-17 18:32:19 driver-btm-soc.c:6988:re_open_core_by_chain: all chain chip temp 41 - 63
2020-02-17 18:32:19 driver-btm-soc.c:7004:re_open_core_by_chain: re_open_core done!
2020-02-17 18:32:49 driver-btm-soc.c:6960:re_open_core_by_chain:

4622

Local / العربية (Arabic) / Re: موقع لحجز الطيران والفنادق

on: February 18, 2020, 01:39:02 AM

Quote from: OmegaStarScream on February 15, 2020, 06:38:14 PM بخصوص ال Virtual credit cards فأنا أنصح بموقع Coinsbee. بعد شراء البطاقة, سوف يتوجب عليك اعطاء سوف اقوم بتحديث مشاركتي ووضع شرح مفصل لاحقا. اتفق من هيوج, موضوع مخصص سكيون افضل , حسب ماقرات في الموقع الذي قمت بنشره هوا انهم يعطوك prepaid Visa Gift Card , والمشكلة مع هده البطاقات انها لا يتم قبولها في كل المواقع, لقد قمت بتجربة prepaid Visa Gift Card كنت قد اشتريتها من امازون, وتم رفضها من بعض المواقع, اتذكر ان تم قبولها في موقع aliexpress ورفضها في اعلان ممول على Facebook تم رفضها ايضا من موقع اخر نسيت اسمه لان الموضوع مر عليه فترة. لا ادري ان كانت البطاقات الافتراضية التي يعطيها هدا الموقع تختلف عن تلك الموجودة في امازون ام لا, على العموم انا جدا مهتم بقراءة الموضوع عند كتابته.

4623

Bitcoin / Development & Technical Discussion / Re: 51% Attack

on: February 18, 2020, 01:11:19 AM

Quote from: stompix on February 17, 2020, 03:38:29 AM Gdp means nothing...sspecially when it is : I find it amusing how you take a measurement scale that is well known and considered and say it means nothing, GDP PPP is not less important than nominal GDP, Quote GDP comparisons using PPP are arguably more useful than those using nominal GDP when assessing a nation's domestic market because PPP takes into account the relative cost of local goods, services and inflation rates of the country, rather than using international market exchange rates which may distort the real differences in per capita income. https://en.wikipedia.org/wiki/List_of_countries_by_GDP_(PPP) Quote In 2007 US coughed twice., it sent the entire global economy to its deathbed. Using GDP PPP china surpasses the U.S using the Nominal GDP China is not far from the U.S, taking share in world exports china has a much larger share, I don't understand why are you underestimating the economic strength of China. If China coughs twice it will also send the entire global economy to hell. Quote As others have said also, I stand by my opinion, why would be something that technical? Raid coinbase with a SWAT team and from 3 billion in equipment you can do it with 10 million worth of it. We are kind of going off-topic here ( a lot of economics) but I have a better argument to put us back on track, the U.S does not ban Bitcoin, they don't have a problem with it, China performs a 51%: or both China and the U.S have no problem with Bitcoin but UAE, Saudi, Iran does, or even any other prince/king decides to play with 2-5 Billion Dollars (because he can) Current hashrate is about 120 million TH , half that is 60 million TH that is 4,285,714 Antminer S9 or 428571480$ = $342,857,120 , or 1,090,909 T17+ (55th) 1000$ = $1,090,909,090 (slightly higher than 1 billion) and just about 2,000 megawatts worth of power, I am pretty sure a king or prince can spare 1 billion + maybe half a billion for infrastructure and 2,000 megawatt worth of electricity. Attacking bitcoin for economic profit does not make sense, but attacking it for fun, experimental purposes or protecting one's economy makes a lot of sense, the above calculation is just an estimate, of course, if someone decides to buy that many gears they will cause gears prices to rise, but to what extent? another billion dollars? two? that much money is still pretty affordable to many countries and individuals around the globe, after the halving a huge chunk of that hash rate will leave the network for good and if the price does not moon, the attack will be a lot cheaper. I find it really naive to think that X person won't do something in one way because Z person can do it in another way, ignoring the possibility of something happening is a terrible idea, IMO anything that has the slightest chance of happening must be discussed seriously and not ignored.

4624

Local / العربية (Arabic) / Re: بعض من روبوتات التداول الآلي

on: February 17, 2020, 01:10:48 AM

Quote from: Heroshema on February 17, 2020, 12:46:42 AM ( أن أستأجر مبرمج يعمل عمل حر بأن يصمم لي روبوت قائم على إستراتيجيتي الخاصة المبتكرة أو المقتبسة على مقاييسي الخاصة .. و هكذا أضمن أن لا يتم التلاعب في حال كان وارداً حدوث هذا الشيء و بالتالي أمان محفظتي أو حساباتي الشخصية .. فكرة اكثر من رائعة ولكن كيف لك ان تظمن ان الشخص التي تقوم بالتعاقد معه والدفع له لكي يقوم بتصميم البوت الخاص بك بأن لا يقوم بسرقته او بيع نفس الكود لاشخاص اخرين دون علمك؟ لا اعتقد انه من السهل ايجاد حل لهده المشكلة والامر يتطلب من المستتمر بان يكون لديه خبرة كافية في مجال البرمجة ليجعل المبرمج يكتب له الكود بدون اي يعلم ماذا يكون وماذا يعمل, لايجد الوثوق في ان المصمم او المبرمج لن يقوم بسرقة مايعتقده "مجهوداته" حتى لو تقاضى اتعابه عليها مسبقا.

4625

Local / العربية (Arabic) / Re: بعض من روبوتات التداول الآلي

on: February 16, 2020, 10:27:26 PM

Quote from: yhiaali3 on February 16, 2020, 09:53:15 PM يعني حسبما أعرف حتى تستخدم الربوت يجب ان تعطيه صلاحيات للوصول لكل حساباتك المختلفة في المنصات وهذا الموضوع يعتبر خطير جدا وغير آمن لأنه لو تعرض الربوت للاختراق مثلا أو كان الربوتوت نفسه غير موثوق فسوف يتم اختراق كامل حساباتك. معظم المنصات ان لم يكن جميعها سواء كانت متخصصة بالكريبتو او الفوركس او البورصة تمنحك نوعان من الصلاحيات فيما يتعلق بالبوتات الخاصة بالتداول, ومعظها يكون الخيار الافتراضي فيها (تداول فقط) بحيث انه لايمكن باي حال من الاحوال للبوت ان يقوم بسحب اموالك الا ان سمحت له انت بذلك وهده الخاصية يستخدمها بعض الناس لاسباب قد يطول شرحها, ولكن يكفي ان تعرف ان استخدام البوت لايعرض اموالك للخسارة بطريقة سرقة الاموال في معظم الاحوال. ولكن وبالرغم من هدا فان البوتات وخوصوصا في الكريبتو تعرضك للخسارة الغير مباشرة والتي تأتي من استخدام اموالك في عمليات ال pump and dump حيت ان مصمم البوت يقوم باستخدام حسابات الضحايا لشراء عملة ذات ماركت كاب منخفض بعد ان يكون قد اشتراها هوا بارخص الاثمان, ويبدا في رفع سعرها تدريجا عن طريق شراءها باستخدام البوت ومن ثم يبيع الكميات التي اشتراها للبوت ويخرج بمكسب كبير ويسبب خسارة للباقين. طبعا هدا لايعني باي حال من الاحوال ان التداول باستخدام البوت غير مجدي , ولكن من وجهة نظري الاطريقة الوحيدة التي قد يكون فيها البوت ناجح هي عند تصميمه ليتماشى مع استراجيتك انت, اما البوتات التي يتم بيعها في العلن فمعضمها تخسر الاموال على المدى الطويل ولا انصح باستخدامها.

4626

Bitcoin / Development & Technical Discussion / Re: 51% Attack

on: February 16, 2020, 08:16:35 PM

Quote from: stompix on February 15, 2020, 07:46:05 PM You're underestimating the power of the US and its influence, and this comes from an EU citizen, not some 2nd amendment freak. I am not sure if I am underestimating their power or you are overestimating it, the U.S has been slapping sanctions on Russia, North Korea, Iran, China, Syria, well you name it, and the results are not as bad, the earth has not stopped spinning. The projected results are even worse But what do I know? I might be really "underestimating the power of the US" Quote Let's cut China out of the picture because you know that if the US sees BTC as a threat the Chinese would have gone with the ban already. BTC could be more like a threat to the U.S dollar, this does not mean it has to be at the same level of threat to any other economy. Quote And since we're at 51% scenario, imagine how this "ban" or whatever it is called would affect the chain security... We would be lucky if we would drop only to 1k in the first phase. So you really think if the U.S bans bitcoin mining for an example, the rest of the world will do the same? Also, I would like to hear your comment about how would the U.S government go about banning bitcoin anyway, does their constitution give the government enough rights to do that? Quote How can you be prepared for this? First of all by admitting that a 51% attack on BTC is very possible, and is IMO the most powerful way to fight bitcoin, way more effective than simply trying to ban it. As far as being technically prepared for such an attack, well I might be the worst person to be asked , but some interesting idea's like "the delayed block submission penalty." or "Komodo’s Delayed Proof of Work". Other methods like increasing confirmations required by merchants and individuals, perhaps someone might make an automated system that sensors the migration of a large enough portion of hashrate (assuming the hash power that is used to perform the 51% has already been on the main blockchain), community consensus to change the mining algothroim to a GPU-Only algthorim so if the attack happens it won't last long. I don't know, those are off the top of my head, I am sure more intelligent people like yourself have better ways to prepare for such an attack rather than thinking that it simply won't happen:

4627

Bitcoin / Mining speculation / Re: ANTBLEED VIRUS!!! CLONE

on: February 15, 2020, 11:29:50 AM

Quote from: kano on February 15, 2020, 10:43:12 AM Edit: I've sent them a message about it also, referencing this thread. Edit2: I got a reply, they have suspended the server. That was quick, well done Kano. as a general rule, one should always SDcard any used gear they buy BEFORE plugging it to the network, these viruses affect every other miner on the same network, so once you make that mistake of installing an infected miner, you will later have to fix every other miner, specifically those who don't bother with changing the default root/root username and password or use words that are easy to brute force. The same or similar viruses exist in most of these "Boost Firmware" you find online.

4628

Bitcoin / Development & Technical Discussion / Re: 51% Attack

on: February 15, 2020, 10:35:13 AM

Quote from: stompix on February 10, 2020, 11:09:46 AM If a government would want that much to get bitcoin eliminated from the economy they will not target the chain or nodes or the hash rate, they will go after users. As I said before and others did, if they would make holding cryptocurrencies a felony with mandatory 25 years, would you still use it? That makes sense, however, there is an essential factor you seem to be missing, a single government can only enforce rules upon its citizens, if the U.S bans crypto altogether, the Russians, Chinese, Iranians and perhaps some European countries would want to buy it more than anything, banning crypto is a risky move to any government if done individually because jumping out of the train does not make it stop, it could simply keep moving and you will be left behind, you need to actually STOP the train, and that would be by "destroying" bitcoin and not just ban it. I pretty much like Saifedean Ammous's (the author of The Bitcoin Standard) statement where he talks about killing bitcoin Quote “The way for them to kill Bitcoin is for them to make the economic incentive to use Bitcoin irrelevant — to make the demand for using Bitcoin go away at the source,”, “They need to offer a technology that is better than Bitcoin — that can obviate the need for Bitcoin. Or, at least, they need to try.” Whenever there are incentives to using bitcoin, people will use it, some countries have up to the death penalty for smoking weed and a mandatory 10 years for owning 1 gram of weed, I have personally lived in a country with such rules, and almost half of them smoke weed on the daily. Another problem in banning bitcoin is that in most countries law amendment can only be adopted by the national legislature and not the government. In a democracy-based country, the legislature represents the people, if the people want bitcoin you can't ban it that easily, it won't work. I could go on and on forever explaining how banning bitcoin is not easy, in fact, a 51% attack would be easier in terms of the government's limitations, but even that might end up ugly for them. With that said, a 51% attack by government/s is doable and we as a community should be prepared for such attacks rather than completely ignoring them, just my thought!.

4629

Local / العربية (Arabic) / Re: موقع لحجز الطيران والفنادق

on: February 15, 2020, 10:04:50 AM

Quote from: hugeblack on February 15, 2020, 09:04:12 AM عموما، من الافضل شراء بطاقات الهدايا باستعمال البيتكوين ومن ثم الدفع للمواقع نظرا للكثير من التعقيدات عن الدفع مباشره ماذا تقصد ببطاقات الهدايا؟ هل تقصد Virtual Credit Card ؟ ام ان الموقع نفسه يمتلك Gift cards يمكن شرائها بالبتكوين؟ ان كان القصد هوا بطاقات الائتمان الافتراضية ارجو ان تشاركنا تجربتك مع بطاقة معينة خصوصا لو كانت لا تطلب KYC وما الى ذلك. Quote ايضا بعض المواقع لا تظهر خيار الدفع بالبيتكوين استنادا للدوله التي انت بها فمثلا لوكنت في الهند لن تظهر لة الدفع حتي لو كان الموقع يقبل ربما يكون هدا السبب لعدم ظهور البتكوين كخيار دفع لي اذا, لا ادري بناء على اي اساس يقومون باخفاء البتكوين كخيار دفع, حاولت البحث في موقعهم ولكنه رديء جدا والبحث عن معلومة معينة فيه صعب جدا.

4630

Local / التعدين / Re: كيف تبدأ بالتعدين؟ شرح نظري + عملي

on: February 14, 2020, 11:24:06 PM

Quote from: yhiaali3 on February 14, 2020, 07:34:29 PM خطر ببالي سؤال من شرح الاخ هيوج حول حجم المشاركة بالبايت وهو هل هناك علاقة لحجم الصورة بالمشكلة يعني إذا قمت مثلا بتصغير حجم الصور ممكن ان تنحل المشكلة لا اعتقد ذلك, الصورة لايتم تخزينها في الموقع, وبمجرد مسحها من الموقع التي يخزنها تختفي من هنا, مما يعني ان كل ماتستهلكه الصورة هنا هوا عدد البايتس , بعد قراءة تعليق الاخ Ryutaro اعتقد انك فعلا بحاجة لاضافة بعض الفراغات مما يعني انه سيكون من شبه المستحيل تقليص الموضوع اقل, لذلك يبدو ان الحل الانسب هوا ان تطلب من Ulven ان يقوم بمسح تعليقه وان تكمل باقي موضوعك في تعليقك انت الذي سيكون تحت الموضوع الاصلي مباشرة, وبذلك يكون المظهر العام جيد, لا اعتقد ان الاخ Ulven سيمانع. Quote from: Ryutaro on February 14, 2020, 09:11:34 PM يشاع أن الحصول على أجهزة التعدين AntMiner التي تتميز بربح عالي أصبح صعب جدا لأن المخزون سرعان ما ينفد, ما صحة ذالك؟ الموضوع موسمي لا غير, احيانا يكون الطلب اعلى من الانتاج, ويكون عليك الانتظار لمدة شهر او شهرين بعد الدفع لاستلام جهازك من الموقع الرسمي, طبعا يمكن شراءه من البائعة الاخرين بثمن اكثر بقليل, واحيانا اخرى تكون الاجهزة متاحة ويتم شحنها فورا بعد الدفع, الموضوع يتعلق بالفترة التي تحاول فيها الحصول على الاجهزة ومدى قوة الطلب وكمية العرض المتاحة, ولكن في العادة شراء اجهزة التعدين ليس صعب كثيرا. Quote أيضا مدى صعوبة التحصل على الكروت الجيدة؟ حاليا شراء الكروت متاح وبسيط جدا, كل الكروت المعروفة متوفرة على المواقع العالمية مثل امازون و Newegg ويتم ارسالها خلال ايام Quote كم يلزم من الوقت للأستعادة رأس المار و البدء في الربح الصافي و ماذا لو طالت المدة و بما أن صعوبة التعدين في إزدياد متواصل و الأجهزة تتطوز بسزعة هل سأتمكن من الربح؟ الموضوع يعتمد على تكلفة الكهرباء وسعر الجهاز, الاخ يحى قام بشرح الموضوع وكيف تقوم باحتساب الدخل الشهري, كل ماعليك هوا معرفة سعر الجهاز الذي تخطط لشرائه ومن تم قسمة سعره على الدخل لتحصل على المدة التقريبية الازمة لاستعادة رأس المال. لايوجد ضمانة للربح, الصعوبة في زيادة في العادة بسبب السعر, مما يعني ان المكسب لا يتنهي بمجرد زيادة الصعوبة, احيانا تزيد الصعوبة ويزيد السعر اكثر فيصبح المكسب اكبر, والعكس صحيح ايضا, يمكن ان تصل لمرحلة انك لم تسترد رأس مالك ويصل جهازك لمرحلة انه يستهلك طاقة كهربائية اكتر من دخله, لذلك بالمجمل التعدين يعتمد بنسبة كبيرة جدا جدا جدا على سعر الكهرباء في بلدك, متوسط الدول الكبرى في التعدين لديها معدل سعر طاقة حوالي 5 سنت دولار لكل كيلو واط, ان كنت تمتلك نفس التكلفة فأنت نسبيا في امان, ان كنت تمتلك اقل من ذلك, فوضعك افضل من الاغلبية, ان كان سعر الطاقة اغلى من ذلك, فموقفك اصعب من غيرك.

4631

Economy / Digital goods / Re: WTB bitmain coupons

on: February 14, 2020, 11:14:34 PM

BUMP.

4632

Local / العربية (Arabic) / Re: موقع لحجز الطيران والفنادق

on: February 14, 2020, 10:48:56 PM

لقد قمت بمحاولة حجز (للتجربة) وجربت حجز هوتيل وتدكرة طياران وفي كلتا الحالتين لم يظهر لي خيار الدفع بالبتكوين, مايقوم به الموقع هوا البحث عن النتائج من مواقع حجز اخرى مثل Booking.com , hotels.com وعرضها عليك, وعندك محاولة الحجز يأخدك الى الموقع الرسمي عبر رابط شبيه برابط الاحلة ليأخد عمولته وهناك تكون مجبر على اختيار احد طرق الدفع التي يقبلها الموقع الاخر, فلا اعرف كيف ظهر لك خيار الدفع بالتكوين! ثم ان تقيم هدا الموقع سيء جدا فهده احدى تعليقات الزبائن عليه في موقع Trustpilot Quote Putting scam agencies on their website without checking their history I had booked a ticket using Wego app last November they were adding SWINGI in the search engines ( which i discovered later they are a scam ). After Wego removed after took more than 45 victim !! Result after 2 month ..no ticket + money deducted twice . https://www.trustpilot.com/review/www.wego.com الموقع الاصلي طبعا هوا www.wego.com ويتغير الرابط بمجرد اختيار البلد فالموقع التي اخترته انت هوا خاص بالأمارات, مبدئيا لا انصح باستخدامه, ولكن ان كانت لك تجربة شخصية معه ارجو ان تخبرنا بها. شكرا جدا على مجهوداتك اخي ياعرب.

4633

Bitcoin / Mining speculation / Re: It is 2020 time for a new diff thread.

on: February 14, 2020, 09:02:37 PM

Quote from: philipma1957 on February 14, 2020, 05:57:36 PM I see a shake up in 46 to 60 days due to BSV and BCH ½ ings. Let us do some calculations, I love Maths. BCH hashrate =4.8E (Current and highest in 12 months) BSV hashrate =3.7E (Current and highest in 12 months) BTC hashrate =106.2E (Current and NOT highest) 4.8+3.7= 8.5E 8.5E is 8% of 106.2E In the grand scheme of things, nobody actually mines those two coins, so even if they were to vanish for whatever reason, and every gear pointed towards those coins joins the Bitcoin blockchain, it's just a matter of 8% added to the network, 106.2E + 8.5E = 114.7E, Bitcoin has done higher than that just a month ago. So let's assume the following, those coin's profitably drops by half while their prices do nothing, half the hashrate migrates to BTC, and then what? I really see nothing coming up in 60 days, it's the 87 days that actually matter.

4634

Bitcoin / Mining speculation / Re: Bitmain Points ( A new feature, What is it) ?

on: February 14, 2020, 08:44:30 PM

Quote from: Artemis3 on February 14, 2020, 03:09:37 PM So Bitmain is finally going to put an end to the resale discount coupon market? By switching to "points" (like flying miles) and tie them to each customer account, they don't need to bother with the coupons anymore... I highly doubt that. What makes you think that Bitmain is actually worried/upset about the resale of coupons? I highly doubt this, first of all, they could simply disable the "Donate" button, takes a second to implement, there is no need for an alternative, the second and more important reason is the fact that it does not matter if I use the coupon or give/sell it to you, from Bitmain's perspective it's $$ coming in, it does not matter who brings it. Quote from: Artemis3 on February 14, 2020, 03:09:37 PM ... I thought for a moment they were going to issue a token too Don't they have one already called BCH?

4635

Local / التعدين / Re: كيف تبدأ بالتعدين؟ شرح نظري + عملي

on: February 14, 2020, 02:36:41 PM

Quote from: yhiaali3 on February 14, 2020, 12:25:00 AM يمكن ان تطلق فكرة هيوج, او ان كنت تريد الموضوع ان يكون منسق بطريقة اقل تعيدا لديك 3 خيارات الان 1- محاولة تلخيص جزء من الموضوع لتتمكن من اضافة الاسطر التي اختفت. 2- اطلب من الاخ Ulven ان يقوم بوضع تلك السطور التي اختفت في تعليقه لانه اول تعليق, وان يقوم بوضعها فوق كلامه ويشير الى انها تكملة للموضوع. 3- اطلب من الاخ Ulven ان يمسح تعليقه, ليكون تعليقك الثالث هوا التاني, قم باستكمال الموضوع في ذلك التعليق , يمكنك اتقباس منشور Ulven في نهاية منشورك التاني حتى لا يضيع.

4636

Bitcoin / Mining speculation / Re: It is 2020 time for a new diff thread.

on: February 14, 2020, 02:23:18 PM

Quote from: stompix on February 14, 2020, 02:01:13 PM Of course, I was talking about an extreme situation where by luck you have all the stars aligned. Aligned enough to hit a block solo? Quote But, don't you think that the current situation with cheap old gear (which can still be plugged in a home) is more advantageous to bring back the truly decentralized home mining that we were discussing in another thread? A cheap miner (what's 80$) it consumes as much as the air conditioning and it does pay something back.... a great point Indeed, when I talked about home miners I did not imagine a situation similar to this, I was imagining that new gears would be geared towards home miners but turns out that old gears could also be used at home, especially with geat ideas like Phill s9 heater version (can't find the link) and thierry4wd amazing idea of altering the miner's case by making a hole on each side of the miner to allow for better cooling with much less noise, and with the right firmware, you can get the setting to as low as 70-75w/th, which is good enough for many home miners given the price of the gear is below 100$ and the miner consumes less than 1kw.

4637

Bitcoin / Mining speculation / Re: Bitmain Points ( A new feature, What is it) ?

on: February 14, 2020, 10:26:43 AM

Quote from: adamjamal on February 14, 2020, 08:57:55 AM I have 18 points, as for the new miners will be 5nm what is the main difference between them and the current miners Well obviously they will be more efficienct (more hashrate for the same power consumption / same hashrate for less power) and of course more expensive and probably less durable judging by S9 vs S11 vs 15 vs S17.

4638

Bitcoin / Mining speculation / Re: Bitmain Points ( A new feature, What is it) ?

on: February 14, 2020, 12:11:45 AM

Quote from: philipma1957 on February 13, 2020, 11:02:11 PM ... my guess these points will discount a 5nm preorder item. I have not thought of such a thing, but honestly makes a lot of sense now that you mentioned it. Since it costs nothing to dream, I would like to think of it as 1 point = 1 Terahash free of charge. Anyway, let's try to keep this thread updated, I am trying to collect information regarding this matter from my Chinese friends, so far nobody seems to know anything about it, however, they usually get the news beforehand.

4639

Bitcoin / Mining speculation / Bitmain Points ( A new feature, What is it) ?

on: February 13, 2020, 10:20:20 PM

This topic will be for discussion on the new "My Points" thing Bitmain has released. It says Quote Bitmain points are calculated based on the history purchase amount after oct 29 2019. As for specific usage rules, please wait for further notifications. Can everyone check their accounts and see if the "my points" appears under "my account" tab? and what do you think that will be? some special discount after reaching x number of points?

4640

Local / التعدين / Re: كيف تبدأ بالتعدين؟ شرح نظري + عملي

on: February 13, 2020, 09:59:38 PM

Quote from: Ya3rob on February 13, 2020, 08:38:57 PM بالنسبة لمواصفات الجهاز ، عندما تكون مواصفات الجهاز سيئة او قديمة مالذي سيؤثر بالنسبة للتعدين؟ التأثير لن يكون مباشر في معظم الاحوال, ولكن مع هدا فلو استخدمت جهاز بمواصفات سيئة جدا فلن يتحمل كروت الشاشة وبرامج التعدين التي تضعها عليه وقد يحتاج الجهاز لعمل restart او يدخل في وضع الجمود , ايضا في حال اعادة التشغيل او انقطاع الكهرباء ورجوعها الجهاز القديم سيحتاج لوقت طويل لان يعمل بينما الجهاز المتوسط يعود للعمل بسرعة, مع ذلك لايوجد اي داعي لشراء معالج معين يكفي ان يكون من الفئة "الجيدة" وليس حتى المتوسطة. Quote بالنسبة لحوض التعدين ، كنظرة من بعيد عن هذا المصطلح أو بشكل مبسّط وعام ماهو بالضبط؟ ، مثلا هل هو تجمع اجهزة تعدين او كروت لانجاز كمية معينة من التعدين ! في التعدين لايمكن ان تتحصل على المكافاءة الا عند ايجادك للبلوك, البلوك تشين لايكترت بعدد الاجهزة الي تمتلكها ولا قوتها ولااي شي اخر وليس مجبر على ان يكون منصف معك, فكل مايعرفه البلوكتشين هوا من يجد البلوك, حسننا ماهي فرصة اياجدك لبلوك باستخدام جهاز يبلغ ثمنه 1000$ وقوته مثلا 50 تيرا هاش؟ http://solochance.com/ تحتاج الى 42 سنة لايجاد بلوك واحد ان كان حظك طبيعي بحيث انك لست محظوظ ولست منحوس , طبعا هدا غير منطقي ! اذا مالحل؟ تقوم بالانظمام الى حوض ولنقل انه يحتوي على 999 جهاز تعدين وكان جهازك هوا رقم 1000, فتكون قوتكم مجتمعة 50,000 تيرا هاش مما يعني انكم ستجدون بلوك في 15 يوم فقط كما موضع في الاسفل عند ايجاد البلوك سياخد الحوض او البوول 12.5 بتكوين + التحويلات (ستنجاهل التحويلات في هدا الشرح) ويقوم بتوزيعها بالتساوي بناء على النسبة التي يمتلها جهازك من حوض وهي 1 من 1000 يعني 12.5 بتكوين قسمة 1000 هي نصيبك كل 15 يوم وهي 0.0125 بتكوين , يعني شهريا دخلك يساوي 0.025 بتكوين مما يعني في 42 عام والتي تعادل 503 شهر ستتحصل على 503*0.025 = 12.5 بتكوين ! يعني نفس النتيجة النهائية ولكن بدل الانتظار 42 سنة لتساخد 12.5 بتكوين تأخدها على دفعات يوميا , اسبوعيا وهكدا , طبعا كل ماكبر حجم الحوض كانت القسمة اكبر يعني بدل من 1000 جهاز لو يوجد 15000 سيكون الدفع يومي بقيمة 0.0125 قسمة 15 يوم. هدا السبب الرئيسي التي جعل احواض التعدين تظهر للوجود, في بداية البتكوين كان بضع من الناس فقط يقومو بالتعدين ويمكن ان تعدن بنفسك وخلال يوم او يومين تجد بلوك اما الان الوضع تغير واصبح التعدين منفردا غير مجدي , هده الفكرة العامة لاحواض التعدين, اما الفرق بينهم وانواعها فتحتاج لشرح اخر مفضل.

Pages: « 1 ... 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 [232] 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 ... 408 »