Search content
Sort by
Showing 20 of 68 results by Tsub
Has anyone seen anything like this before? What has me confused is the across all the hashboard nature of this, so it has me completely stumped with where to begin. Any ideas?
I cut some of the read / write fail. What is weird is repeats chain0, but then at the end is errors on Chain1 and Chain2 as well.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.8.13+ (jenkins@nomd-nomd-fwc-bj) (gcc version 4.9.4 (Linaro GCC 4.9-2017.01) ) #36 SMP Mon Dec 26 17:10:49 CST 2022
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=50c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: Generic AM33XX (Flattened Device Tree), model: TI AM335x BeagleBone
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] On node 0 totalpages: 65280
[ 0.000000] free_area_init_node: node 0, pgdat c05d9000, node_mem_map c0631000
[ 0.000000] Normal zone: 512 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 64768 pages, LIFO batch:15
[ 0.000000] AM335X ES1.0 (neon )
[ 0.000000] PERCPU: Embedded 8 pages/cpu @c083e000 s9856 r8192 d14720 u32768
[ 0.000000] pcpu-alloc: s9856 r8192 d14720 u32768 alloc=8*4096
[ 0.000000] pcpu-alloc:
[ 0.000000] Kernel command line: console=ttyO0,115200n8 init=/sbin/init
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] __ex_table already sorted, skipping sort
[ 0.000000] allocated 524288 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] Memory: 255MB = 255MB total
[ 0.000000] Memory: 245400k/245400k available, 16744k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xd0800000 - 0xff000000 ( 744 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf800000 - 0xbfe00000 ( 6 MB)
[ 0.000000] .text : 0xc0008000 - 0xc053f674 (5342 kB)
[ 0.000000] .init : 0xc0540000 - 0xc0571680 ( 198 kB)
[ 0.000000] .data : 0xc0572000 - 0xc05d9ee0 ( 416 kB)
[ 0.000000] .bss : 0xc05d9ee0 - 0xc0630448 ( 346 kB)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[ 0.000000] Total of 128 interrupts on 1 active controller
[ 0.000000] OMAP clockevent source: GPTIMER1 at 24000000 Hz
[ 0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[ 0.000000] OMAP clocksource: GPTIMER2 at 24000000 Hz
[ 0.000000] Console: colour dummy device 80x30
[ 0.000344] Calibrating delay loop... 545.07 BogoMIPS (lpj=531968)
[ 0.015445] pid_max: default: 32768 minimum: 301
[ 0.015670] Security Framework initialized
[ 0.015762] Mount-cache hash table entries: 512
[ 0.024264] Initializing cgroup subsys cpuacct
[ 0.024297] Initializing cgroup subsys memory
[ 0.024360] Initializing cgroup subsys blkio
[ 0.024491] CPU: Testing write buffer coherency: ok
[ 0.024998] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[ 0.025073] Setting up static identity map for 0x8030a500 - 0x8030a54c
[ 0.026443] Brought up 1 CPUs
[ 0.026468] SMP: Total of 1 processors activated (545.07 BogoMIPS).
[ 0.027736] devtmpfs: initialized
[ 0.091404] pinctrl core: initialized pinctrl subsystem
[ 0.091653] rstctl core: initialized rstctl subsystem
[ 0.092120] regulator-dummy: no parameters
[ 0.092619] NET: Registered protocol family 16
[ 0.093281] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.102700] pinctrl-single 44e10800.pinmux: prop pinctrl-0 index 0 invalid phandle
[ 0.102875] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[ 0.103926] platform 49000000.edma: alias fck already exists
[ 0.103955] platform 49000000.edma: alias fck already exists
[ 0.103979] platform 49000000.edma: alias fck already exists
[ 0.105097] gpiochip_add: registered GPIOs 0 to 31 on device: gpio
[ 0.105321] OMAP GPIO hardware version 0.1
[ 0.106651] gpiochip_add: registered GPIOs 32 to 63 on device: gpio
[ 0.107952] gpiochip_add: registered GPIOs 64 to 95 on device: gpio
[ 0.109407] gpiochip_add: registered GPIOs 96 to 127 on device: gpio
[ 0.109927] of_get_named_gpio_flags exited with status 52
[ 0.109957] gpio-rctrl rstctl.3: loaded OK
[ 0.114827] omap-gpmc 50000000.gpmc: GPMC revision 6.0
[ 0.118075] hw-breakpoint: debug architecture 0x4 unsupported.
[ 0.119971] cpsw.0: No hwaddr in dt. Using 64:cf:d9:e2:85:2d from efuse
[ 0.128861] bio: create slab <bio-0> at 0
[ 0.140293] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver
[ 0.140582] of_get_named_gpio_flags: can't parse gpios property
[ 0.140807] vmmcsd_fixed: 3300 mV
[ 0.143920] SCSI subsystem initialized
[ 0.145156] omap_i2c 4819c000.i2c: bus 0 rev0.11 at 100 kHz
[ 0.145188] omap_i2c 4819c000.i2c: unable to select pin group
[ 0.145420] pps_core: LinuxPPS API ver. 1 registered
[ 0.145437] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.147024] Switching to clocksource gp_timer
[ 0.164196] NET: Registered protocol family 2
[ 0.165267] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.165355] TCP bind hash table entries: 2048 (order: 3, 40960 bytes)
[ 0.165448] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.165542] TCP: reno registered
[ 0.165567] UDP hash table entries: 256 (order: 1, 12288 bytes)
[ 0.165612] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes)
[ 0.166021] NET: Registered protocol family 1
[ 0.166578] RPC: Registered named UNIX socket transport module.
[ 0.166598] RPC: Registered udp transport module.
[ 0.166611] RPC: Registered tcp transport module.
[ 0.166679] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.167063] Trying to unpack rootfs image as initramfs...
[ 1.065503] Freeing initrd memory: 6496K
[ 1.066128] CPU PMU: probing PMU on CPU 0
[ 1.066157] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
[ 1.066667] omap2_mbox_probe: platform not supported
[ 1.070399] VFS: Disk quotas dquot_6.5.2
[ 1.070643] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.072066] NFS: Registering the id_resolver key type
[ 1.072178] Key type id_resolver registered
[ 1.072195] Key type id_legacy registered
[ 1.072259] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 1.072699] msgmni has been set to 491
[ 1.075541] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[ 1.075568] io scheduler noop registered
[ 1.075584] io scheduler deadline registered
[ 1.075640] io scheduler cfq registered (default)
[ 1.079335] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 1.081608] omap_uart 44e09000.serial: did not get pins for uart0 error: -19
[ 1.081633] of_get_named_gpio_flags: can't parse gpios property
[ 1.081911] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0
[ 1.703023] console [ttyO0] enabled
[ 1.707288] of_get_named_gpio_flags: can't parse gpios property
[ 1.707540] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a OMAP UART1
[ 1.715988] of_get_named_gpio_flags: can't parse gpios property
[ 1.716200] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2
[ 1.724589] of_get_named_gpio_flags: can't parse gpios property
[ 1.724804] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a OMAP UART4
[ 1.733240] of_get_named_gpio_flags: can't parse gpios property
[ 1.733456] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a OMAP UART5
[ 1.755354] brd: module loaded
[ 1.765605] loop: module loaded
[ 1.769650] bone-capemgr bone_capemgr.8: Failed to find baseboard eeprom node
[ 1.779728] ONFI param page 0 valid
[ 1.783441] ONFI flash detected
[ 1.786765] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron MT29F1G08ABAEAWP), 128MiB, page size: 2048, OOB size: 64
[ 1.798690] omap2-nand: detected x8 NAND flash
[ 1.803360] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme
[ 1.808943] omap2-nand: using custom ecc layout
[ 1.813795] 12 ofpart partitions found on MTD device omap2-nand.0
[ 1.820195] Creating 12 MTD partitions on "omap2-nand.0":
[ 1.825878] 0x000000000000-0x000000020000 : "spl"
[ 1.832533] 0x000000020000-0x000000040000 : "spl_backup1"
[ 1.839891] 0x000000040000-0x000000060000 : "spl_backup2"
[ 1.847233] 0x000000060000-0x000000080000 : "spl_backup3"
[ 1.854563] 0x000000080000-0x000000240000 : "u-boot"
[ 1.862874] 0x000000240000-0x000000260000 : "bootenv"
[ 1.869882] 0x000000260000-0x000000280000 : "fdt"
[ 1.876513] 0x000000280000-0x000000780000 : "kernel"
[ 1.887451] 0x000000800000-0x000001c00000 : "root"
[ 1.910751] 0x000001c00000-0x000001e00000 : "config"
[ 1.919176] 0x000001e00000-0x000002000000 : "sig"
[ 1.927354] 0x000002000000-0x000008000000 : "nvdata"
[ 2.015068] OneNAND driver initializing
[ 2.021478] mousedev: PS/2 mouse device common for all mice
[ 2.029185] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[ 2.036683] 44e3e000.rtc: already running
[ 2.041184] i2c /dev entries driver
[ 2.045492] pps_ldisc: PPS line discipline registered
[ 2.050981] Driver for 1-wire Dallas network protocol.
[ 2.058238] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[ 2.065813] cpuidle: using governor ladder
[ 2.070145] cpuidle: using governor menu
[ 2.074718] of_get_named_gpio_flags exited with status 6
[ 2.074737] of_get_named_gpio_flags: can't parse gpios property
[ 2.074752] of_get_named_gpio_flags: can't parse gpios property
[ 2.074786] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed
[ 2.082012] omap_hsmmc mmc.4: Failed to get rstctl; not using any
[ 2.088848] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25
[ 2.096072] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24
[ 2.103388] mmc.4 supply vmmc_aux not found, using dummy regulator
[ 2.110392] omap_hsmmc mmc.4: pins are not configured from the driver
[ 2.143809] of_get_named_gpio_flags exited with status -517
[ 2.143873] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[ 2.151652] ledtrig-cpu: registered to indicate activity on CPUs
[ 2.158426] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36
[ 2.165649] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[ 2.173724] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[ 2.180005] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5
[ 2.187192] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6
[ 2.195502] nf_conntrack version 0.5.0 (3935 buckets, 15740 max)
[ 2.202973] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 2.208751] TCP: cubic registered
[ 2.212295] Initializing XFRM netlink socket
[ 2.216931] NET: Registered protocol family 10
[ 2.223021] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 2.228974] NET: Registered protocol family 17
[ 2.233748] NET: Registered protocol family 15
[ 2.238592] Key type dns_resolver registered
[ 2.243172] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[ 2.251249] ThumbEE CPU extension supported.
[ 2.255766] Registering SWP/SWPB emulation handler
[ 2.261869] registered taskstats version 1
[ 2.267656] of_get_named_gpio_flags exited with status -517
[ 2.267727] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[ 2.324913] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[ 2.331327] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[ 2.346098] libphy: 4a101000.mdio: probed
[ 2.350441] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[ 2.360527] of_get_named_gpio_flags exited with status -517
[ 2.360594] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[ 2.368073] Detected MACID = 64:cf:d9:e2:85:2d
[ 2.372754] cpsw 4a100000.ethernet: NAPI disabled
[ 2.379718] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[ 2.388897] cpu0 supply cpu0 not found, using dummy regulator
[ 2.395385] cpufreq_cpu0: failed to scale voltage up: -22
[ 2.401206] cpufreq_cpu0: failed to scale voltage up: -22
[ 2.414917] Freeing init memory: 196K
[ 2.495619] devpts: called with bogus options
[ 2.986669] jffs2: notice: (109) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[ 6.036910] jffs2: notice: (115) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[ 6.806171] net eth0: initializing cpsw version 1.12 (0)
[ 6.816487] net eth0: phy found : id is : 0x7c0f1
[ 6.828868] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 9.891852] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
[ 9.900026] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 12.481784] register uart_trans chrdev success.
[ 12.487303] tty port open success [/dev/ttyO1]!
[ 12.492325] init sucess for tty struct (249:1) [/dev/ttyO1]
[ 12.498749] tty port open success [/dev/ttyO2]!
[ 12.504810] init sucess for tty struct (249:2) [/dev/ttyO2]
[ 12.511200] tty port open success [/dev/ttyO4]!
[ 12.516210] init sucess for tty struct (249:4) [/dev/ttyO4]
[ 12.524511] tty port open success [/dev/ttyO5]!
[ 12.530858] init sucess for tty struct (249:5) [/dev/ttyO5]
===========================================Miner log===========================================
2000-01-01 00:00:11 Open miner sn file /config/sn error
2000-01-01 00:00:11 Miner compile time: Mon Dec 26 17:19:30 CST 2022 type: Antminer BHB42XXX sn :
2000-01-01 00:00:11 This is fix-freq version
2000-01-01 00:00:12 Miner compile time: Mon Dec 26 17:19:30 CST 2022 type: Antminer BHB42XXX
2000-01-01 00:00:12 commit version: f2ab6bc 2022-12-26 17:08:34, build by: jenkins 2022-12-26 17:32:52
2000-01-01 00:00:12 opt_multi_version = 1
2000-01-01 00:00:12 opt_bitmain_ab = 1
2000-01-01 00:00:12 mid_auto_gen = 1
2000-01-01 00:00:12 opt_bitmain_work_mode = 0
2000-01-01 00:00:12 port 51 already exported
2000-01-01 00:00:12 port 49 already exported
2000-01-01 00:00:12 port 48 already exported
2000-01-01 00:00:12 port 60 already exported
2000-01-01 00:00:12 port 47 already exported
2000-01-01 00:00:12 port 27 already exported
2000-01-01 00:00:12 port 44 already exported
2000-01-01 00:00:12 port 22 already exported
2000-01-01 00:00:12 no board pluged in socket 44
2000-01-01 00:00:12 port 23 already exported
2000-01-01 00:00:12 port 45 already exported
2000-01-01 00:00:12 port 46 already exported
2000-01-01 00:00:12 port 26 already exported
2000-01-01 00:00:13 Note: front fan is power on!
2000-01-01 00:00:13 Note: rear fan is power on!
2000-01-01 00:00:13 start the http log.
2000-01-01 00:00:13 httpListenThread start ret=0
2000-01-01 00:00:13 start listen on 6060 ...
2023-03-09 02:24:02 ==========================capability start==========================
2023-03-09 02:24:02 board num = 3
2023-03-09 02:24:02 board id = 0, chain num = 1
2023-03-09 02:24:02 chain id = 0
2023-03-09 02:24:03 board id = 1, chain num = 1
2023-03-09 02:24:03 chain id = 1
2023-03-09 02:24:03 board id = 2, chain num = 1
2023-03-09 02:24:03 chain id = 2
2023-03-09 02:24:03 ==========================capability end============================
2023-03-09 02:24:03 chain num = 3
2023-03-09 02:24:03 skip loading levels for now
2023-03-09 02:24:04 fail to write 0:1
2023-03-09 02:24:04 fail to read 0:1
2023-03-09 02:24:48 fail to write 0:1
2023-03-09 02:24:48 fail to read 0:1
2023-03-09 02:24:48 fail to write 0:1
2023-03-09 02:24:48 fail to read 0:1
2023-03-09 02:24:48 fail to write 0:1
2023-03-09 02:24:48 fail to read 0:1
2023-03-09 02:24:48 fail to write 0:1
2023-03-09 02:24:48 fail to read 0:1
2023-03-09 02:24:49 fail to write 0:1
2023-03-09 02:24:49 fail to read 0:1
2023-03-09 02:25:16 load chain 0 eeprom data
2023-03-09 02:25:16 version invalid 61!=4
2023-03-09 02:25:16 version invalid 61!=4
2023-03-09 02:25:16 got nothing
2023-03-09 02:25:16 fail to write 0:1
2023-03-09 02:25:16 fail to read 0:1
2023-03-09 02:25:16 fail to write 0:1
2023-03-09 02:25:16 fail to read 0:1
2023-03-09 02:25:16 fail to write 0:1
2023-03-09 02:25:16 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:31 load chain 0 eeprom data
2023-03-09 02:25:31 version invalid 61!=4
2023-03-09 02:25:31 version invalid 61!=4
2023-03-09 02:25:31 got nothing
2023-03-09 02:25:31 Data load fail for chain 0.
2023-03-09 02:25:31 load chain 1 eeprom data
2023-03-09 02:25:32 load chain 2 eeprom data
2023-03-09 02:25:32 EEPROM error: CRC 1ST REGION
2023-03-09 02:25:32 got nothing
2023-03-09 02:25:33 load chain 2 eeprom data
2023-03-09 02:25:33 EEPROM error: CRC 1ST REGION
2023-03-09 02:25:33 got nothing
2023-03-09 02:25:33 load chain 2 eeprom data
2023-03-09 02:25:33 EEPROM error: CRC 1ST REGION
2023-03-09 02:25:33 got nothing
2023-03-09 02:25:33 Data load fail for chain 2.
2023-03-09 02:25:33 Sweep error string = J5:4.
2023-03-09 02:25:33 Fixture data load failed, exit.
2023-03-09 02:25:33 get board name failed for chain:0
2023-03-09 02:25:33 ERROR_SOC_INIT: basic init failed!
2023-03-09 02:25:33 stop_mining: basic init failed!
2023-03-09 02:25:33 ****power off hashboard****
I cut some of the read / write fail. What is weird is repeats chain0, but then at the end is errors on Chain1 and Chain2 as well.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.8.13+ (jenkins@nomd-nomd-fwc-bj) (gcc version 4.9.4 (Linaro GCC 4.9-2017.01) ) #36 SMP Mon Dec 26 17:10:49 CST 2022
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=50c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: Generic AM33XX (Flattened Device Tree), model: TI AM335x BeagleBone
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] On node 0 totalpages: 65280
[ 0.000000] free_area_init_node: node 0, pgdat c05d9000, node_mem_map c0631000
[ 0.000000] Normal zone: 512 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 64768 pages, LIFO batch:15
[ 0.000000] AM335X ES1.0 (neon )
[ 0.000000] PERCPU: Embedded 8 pages/cpu @c083e000 s9856 r8192 d14720 u32768
[ 0.000000] pcpu-alloc: s9856 r8192 d14720 u32768 alloc=8*4096
[ 0.000000] pcpu-alloc:
- 0
[ 0.000000] Kernel command line: console=ttyO0,115200n8 init=/sbin/init
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] __ex_table already sorted, skipping sort
[ 0.000000] allocated 524288 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] Memory: 255MB = 255MB total
[ 0.000000] Memory: 245400k/245400k available, 16744k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xd0800000 - 0xff000000 ( 744 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf800000 - 0xbfe00000 ( 6 MB)
[ 0.000000] .text : 0xc0008000 - 0xc053f674 (5342 kB)
[ 0.000000] .init : 0xc0540000 - 0xc0571680 ( 198 kB)
[ 0.000000] .data : 0xc0572000 - 0xc05d9ee0 ( 416 kB)
[ 0.000000] .bss : 0xc05d9ee0 - 0xc0630448 ( 346 kB)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[ 0.000000] Total of 128 interrupts on 1 active controller
[ 0.000000] OMAP clockevent source: GPTIMER1 at 24000000 Hz
[ 0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[ 0.000000] OMAP clocksource: GPTIMER2 at 24000000 Hz
[ 0.000000] Console: colour dummy device 80x30
[ 0.000344] Calibrating delay loop... 545.07 BogoMIPS (lpj=531968)
[ 0.015445] pid_max: default: 32768 minimum: 301
[ 0.015670] Security Framework initialized
[ 0.015762] Mount-cache hash table entries: 512
[ 0.024264] Initializing cgroup subsys cpuacct
[ 0.024297] Initializing cgroup subsys memory
[ 0.024360] Initializing cgroup subsys blkio
[ 0.024491] CPU: Testing write buffer coherency: ok
[ 0.024998] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[ 0.025073] Setting up static identity map for 0x8030a500 - 0x8030a54c
[ 0.026443] Brought up 1 CPUs
[ 0.026468] SMP: Total of 1 processors activated (545.07 BogoMIPS).
[ 0.027736] devtmpfs: initialized
[ 0.091404] pinctrl core: initialized pinctrl subsystem
[ 0.091653] rstctl core: initialized rstctl subsystem
[ 0.092120] regulator-dummy: no parameters
[ 0.092619] NET: Registered protocol family 16
[ 0.093281] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.102700] pinctrl-single 44e10800.pinmux: prop pinctrl-0 index 0 invalid phandle
[ 0.102875] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[ 0.103926] platform 49000000.edma: alias fck already exists
[ 0.103955] platform 49000000.edma: alias fck already exists
[ 0.103979] platform 49000000.edma: alias fck already exists
[ 0.105097] gpiochip_add: registered GPIOs 0 to 31 on device: gpio
[ 0.105321] OMAP GPIO hardware version 0.1
[ 0.106651] gpiochip_add: registered GPIOs 32 to 63 on device: gpio
[ 0.107952] gpiochip_add: registered GPIOs 64 to 95 on device: gpio
[ 0.109407] gpiochip_add: registered GPIOs 96 to 127 on device: gpio
[ 0.109927] of_get_named_gpio_flags exited with status 52
[ 0.109957] gpio-rctrl rstctl.3: loaded OK
[ 0.114827] omap-gpmc 50000000.gpmc: GPMC revision 6.0
[ 0.118075] hw-breakpoint: debug architecture 0x4 unsupported.
[ 0.119971] cpsw.0: No hwaddr in dt. Using 64:cf:d9:e2:85:2d from efuse
[ 0.128861] bio: create slab <bio-0> at 0
[ 0.140293] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver
[ 0.140582] of_get_named_gpio_flags: can't parse gpios property
[ 0.140807] vmmcsd_fixed: 3300 mV
[ 0.143920] SCSI subsystem initialized
[ 0.145156] omap_i2c 4819c000.i2c: bus 0 rev0.11 at 100 kHz
[ 0.145188] omap_i2c 4819c000.i2c: unable to select pin group
[ 0.145420] pps_core: LinuxPPS API ver. 1 registered
[ 0.145437] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.147024] Switching to clocksource gp_timer
[ 0.164196] NET: Registered protocol family 2
[ 0.165267] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.165355] TCP bind hash table entries: 2048 (order: 3, 40960 bytes)
[ 0.165448] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.165542] TCP: reno registered
[ 0.165567] UDP hash table entries: 256 (order: 1, 12288 bytes)
[ 0.165612] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes)
[ 0.166021] NET: Registered protocol family 1
[ 0.166578] RPC: Registered named UNIX socket transport module.
[ 0.166598] RPC: Registered udp transport module.
[ 0.166611] RPC: Registered tcp transport module.
[ 0.166679] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.167063] Trying to unpack rootfs image as initramfs...
[ 1.065503] Freeing initrd memory: 6496K
[ 1.066128] CPU PMU: probing PMU on CPU 0
[ 1.066157] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
[ 1.066667] omap2_mbox_probe: platform not supported
[ 1.070399] VFS: Disk quotas dquot_6.5.2
[ 1.070643] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.072066] NFS: Registering the id_resolver key type
[ 1.072178] Key type id_resolver registered
[ 1.072195] Key type id_legacy registered
[ 1.072259] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 1.072699] msgmni has been set to 491
[ 1.075541] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[ 1.075568] io scheduler noop registered
[ 1.075584] io scheduler deadline registered
[ 1.075640] io scheduler cfq registered (default)
[ 1.079335] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 1.081608] omap_uart 44e09000.serial: did not get pins for uart0 error: -19
[ 1.081633] of_get_named_gpio_flags: can't parse gpios property
[ 1.081911] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0
[ 1.703023] console [ttyO0] enabled
[ 1.707288] of_get_named_gpio_flags: can't parse gpios property
[ 1.707540] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a OMAP UART1
[ 1.715988] of_get_named_gpio_flags: can't parse gpios property
[ 1.716200] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2
[ 1.724589] of_get_named_gpio_flags: can't parse gpios property
[ 1.724804] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a OMAP UART4
[ 1.733240] of_get_named_gpio_flags: can't parse gpios property
[ 1.733456] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a OMAP UART5
[ 1.755354] brd: module loaded
[ 1.765605] loop: module loaded
[ 1.769650] bone-capemgr bone_capemgr.8: Failed to find baseboard eeprom node
[ 1.779728] ONFI param page 0 valid
[ 1.783441] ONFI flash detected
[ 1.786765] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron MT29F1G08ABAEAWP), 128MiB, page size: 2048, OOB size: 64
[ 1.798690] omap2-nand: detected x8 NAND flash
[ 1.803360] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme
[ 1.808943] omap2-nand: using custom ecc layout
[ 1.813795] 12 ofpart partitions found on MTD device omap2-nand.0
[ 1.820195] Creating 12 MTD partitions on "omap2-nand.0":
[ 1.825878] 0x000000000000-0x000000020000 : "spl"
[ 1.832533] 0x000000020000-0x000000040000 : "spl_backup1"
[ 1.839891] 0x000000040000-0x000000060000 : "spl_backup2"
[ 1.847233] 0x000000060000-0x000000080000 : "spl_backup3"
[ 1.854563] 0x000000080000-0x000000240000 : "u-boot"
[ 1.862874] 0x000000240000-0x000000260000 : "bootenv"
[ 1.869882] 0x000000260000-0x000000280000 : "fdt"
[ 1.876513] 0x000000280000-0x000000780000 : "kernel"
[ 1.887451] 0x000000800000-0x000001c00000 : "root"
[ 1.910751] 0x000001c00000-0x000001e00000 : "config"
[ 1.919176] 0x000001e00000-0x000002000000 : "sig"
[ 1.927354] 0x000002000000-0x000008000000 : "nvdata"
[ 2.015068] OneNAND driver initializing
[ 2.021478] mousedev: PS/2 mouse device common for all mice
[ 2.029185] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[ 2.036683] 44e3e000.rtc: already running
[ 2.041184] i2c /dev entries driver
[ 2.045492] pps_ldisc: PPS line discipline registered
[ 2.050981] Driver for 1-wire Dallas network protocol.
[ 2.058238] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[ 2.065813] cpuidle: using governor ladder
[ 2.070145] cpuidle: using governor menu
[ 2.074718] of_get_named_gpio_flags exited with status 6
[ 2.074737] of_get_named_gpio_flags: can't parse gpios property
[ 2.074752] of_get_named_gpio_flags: can't parse gpios property
[ 2.074786] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed
[ 2.082012] omap_hsmmc mmc.4: Failed to get rstctl; not using any
[ 2.088848] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25
[ 2.096072] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24
[ 2.103388] mmc.4 supply vmmc_aux not found, using dummy regulator
[ 2.110392] omap_hsmmc mmc.4: pins are not configured from the driver
[ 2.143809] of_get_named_gpio_flags exited with status -517
[ 2.143873] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[ 2.151652] ledtrig-cpu: registered to indicate activity on CPUs
[ 2.158426] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36
[ 2.165649] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[ 2.173724] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[ 2.180005] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5
[ 2.187192] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6
[ 2.195502] nf_conntrack version 0.5.0 (3935 buckets, 15740 max)
[ 2.202973] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 2.208751] TCP: cubic registered
[ 2.212295] Initializing XFRM netlink socket
[ 2.216931] NET: Registered protocol family 10
[ 2.223021] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 2.228974] NET: Registered protocol family 17
[ 2.233748] NET: Registered protocol family 15
[ 2.238592] Key type dns_resolver registered
[ 2.243172] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[ 2.251249] ThumbEE CPU extension supported.
[ 2.255766] Registering SWP/SWPB emulation handler
[ 2.261869] registered taskstats version 1
[ 2.267656] of_get_named_gpio_flags exited with status -517
[ 2.267727] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[ 2.324913] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[ 2.331327] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[ 2.346098] libphy: 4a101000.mdio: probed
[ 2.350441] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[ 2.360527] of_get_named_gpio_flags exited with status -517
[ 2.360594] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[ 2.368073] Detected MACID = 64:cf:d9:e2:85:2d
[ 2.372754] cpsw 4a100000.ethernet: NAPI disabled
[ 2.379718] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[ 2.388897] cpu0 supply cpu0 not found, using dummy regulator
[ 2.395385] cpufreq_cpu0: failed to scale voltage up: -22
[ 2.401206] cpufreq_cpu0: failed to scale voltage up: -22
[ 2.414917] Freeing init memory: 196K
[ 2.495619] devpts: called with bogus options
[ 2.986669] jffs2: notice: (109) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[ 6.036910] jffs2: notice: (115) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[ 6.806171] net eth0: initializing cpsw version 1.12 (0)
[ 6.816487] net eth0: phy found : id is : 0x7c0f1
[ 6.828868] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 9.891852] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
[ 9.900026] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 12.481784] register uart_trans chrdev success.
[ 12.487303] tty port open success [/dev/ttyO1]!
[ 12.492325] init sucess for tty struct (249:1) [/dev/ttyO1]
[ 12.498749] tty port open success [/dev/ttyO2]!
[ 12.504810] init sucess for tty struct (249:2) [/dev/ttyO2]
[ 12.511200] tty port open success [/dev/ttyO4]!
[ 12.516210] init sucess for tty struct (249:4) [/dev/ttyO4]
[ 12.524511] tty port open success [/dev/ttyO5]!
[ 12.530858] init sucess for tty struct (249:5) [/dev/ttyO5]
===========================================Miner log===========================================
2000-01-01 00:00:11 Open miner sn file /config/sn error
2000-01-01 00:00:11 Miner compile time: Mon Dec 26 17:19:30 CST 2022 type: Antminer BHB42XXX sn :
2000-01-01 00:00:11 This is fix-freq version
2000-01-01 00:00:12 Miner compile time: Mon Dec 26 17:19:30 CST 2022 type: Antminer BHB42XXX
2000-01-01 00:00:12 commit version: f2ab6bc 2022-12-26 17:08:34, build by: jenkins 2022-12-26 17:32:52
2000-01-01 00:00:12 opt_multi_version = 1
2000-01-01 00:00:12 opt_bitmain_ab = 1
2000-01-01 00:00:12 mid_auto_gen = 1
2000-01-01 00:00:12 opt_bitmain_work_mode = 0
2000-01-01 00:00:12 port 51 already exported
2000-01-01 00:00:12 port 49 already exported
2000-01-01 00:00:12 port 48 already exported
2000-01-01 00:00:12 port 60 already exported
2000-01-01 00:00:12 port 47 already exported
2000-01-01 00:00:12 port 27 already exported
2000-01-01 00:00:12 port 44 already exported
2000-01-01 00:00:12 port 22 already exported
2000-01-01 00:00:12 no board pluged in socket 44
2000-01-01 00:00:12 port 23 already exported
2000-01-01 00:00:12 port 45 already exported
2000-01-01 00:00:12 port 46 already exported
2000-01-01 00:00:12 port 26 already exported
2000-01-01 00:00:13 Note: front fan is power on!
2000-01-01 00:00:13 Note: rear fan is power on!
2000-01-01 00:00:13 start the http log.
2000-01-01 00:00:13 httpListenThread start ret=0
2000-01-01 00:00:13 start listen on 6060 ...
2023-03-09 02:24:02 ==========================capability start==========================
2023-03-09 02:24:02 board num = 3
2023-03-09 02:24:02 board id = 0, chain num = 1
2023-03-09 02:24:02 chain id = 0
2023-03-09 02:24:03 board id = 1, chain num = 1
2023-03-09 02:24:03 chain id = 1
2023-03-09 02:24:03 board id = 2, chain num = 1
2023-03-09 02:24:03 chain id = 2
2023-03-09 02:24:03 ==========================capability end============================
2023-03-09 02:24:03 chain num = 3
2023-03-09 02:24:03 skip loading levels for now
2023-03-09 02:24:04 fail to write 0:1
2023-03-09 02:24:04 fail to read 0:1
2023-03-09 02:24:48 fail to write 0:1
2023-03-09 02:24:48 fail to read 0:1
2023-03-09 02:24:48 fail to write 0:1
2023-03-09 02:24:48 fail to read 0:1
2023-03-09 02:24:48 fail to write 0:1
2023-03-09 02:24:48 fail to read 0:1
2023-03-09 02:24:48 fail to write 0:1
2023-03-09 02:24:48 fail to read 0:1
2023-03-09 02:24:49 fail to write 0:1
2023-03-09 02:24:49 fail to read 0:1
2023-03-09 02:25:16 load chain 0 eeprom data
2023-03-09 02:25:16 version invalid 61!=4
2023-03-09 02:25:16 version invalid 61!=4
2023-03-09 02:25:16 got nothing
2023-03-09 02:25:16 fail to write 0:1
2023-03-09 02:25:16 fail to read 0:1
2023-03-09 02:25:16 fail to write 0:1
2023-03-09 02:25:16 fail to read 0:1
2023-03-09 02:25:16 fail to write 0:1
2023-03-09 02:25:16 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:30 fail to write 0:1
2023-03-09 02:25:30 fail to read 0:1
2023-03-09 02:25:31 load chain 0 eeprom data
2023-03-09 02:25:31 version invalid 61!=4
2023-03-09 02:25:31 version invalid 61!=4
2023-03-09 02:25:31 got nothing
2023-03-09 02:25:31 Data load fail for chain 0.
2023-03-09 02:25:31 load chain 1 eeprom data
2023-03-09 02:25:32 load chain 2 eeprom data
2023-03-09 02:25:32 EEPROM error: CRC 1ST REGION
2023-03-09 02:25:32 got nothing
2023-03-09 02:25:33 load chain 2 eeprom data
2023-03-09 02:25:33 EEPROM error: CRC 1ST REGION
2023-03-09 02:25:33 got nothing
2023-03-09 02:25:33 load chain 2 eeprom data
2023-03-09 02:25:33 EEPROM error: CRC 1ST REGION
2023-03-09 02:25:33 got nothing
2023-03-09 02:25:33 Data load fail for chain 2.
2023-03-09 02:25:33 Sweep error string = J5:4.
2023-03-09 02:25:33 Fixture data load failed, exit.
2023-03-09 02:25:33 get board name failed for chain:0
2023-03-09 02:25:33 ERROR_SOC_INIT: basic init failed!
2023-03-09 02:25:33 stop_mining: basic init failed!
2023-03-09 02:25:33 ****power off hashboard****
I am looking for the best asic miner I can order online, brand new and with 1500$ max price per one, I want two, I've seen Avalon and Bitmain with 50+ TH to 60+TH but I want to know which are safer for a newbie to avoid buying problematic one.
Bitmain doesn't have units with a price of $1500 or below, the current cheapest available units right now from Bitmain is s19 pro with a price of $1900. So you don't have any other option than buying units from Canaan as suggested above the available cheapest unit they have is 1126 pro with a price of $882.
What do you mean you want two units? Do you mean that if you want 2 units with a maximum price of $1500 then you have around $3000 budget?
If yes then you can have 3 units with that amount with their cheapest unit(1126pro) from Canaan.
Why would you focus on that level? To learn about mining and experiment? You can do that cheaper. Plus, you need to watch your j/Th (joules per Terahash) ratio so that this doesn't end up costing you money given energy prices.
Efficiency is the name of the game over time. If you plan on running them a while, remember, low efficiency is like buying a cheap truck and paying for that every time you have to fill up the tank. That initial savings catches up with you quick over time.
Bitcoin mining difficulty has been increasing and will continue to increase:
live chart here: https://www.coinwarz.com/mining/bitcoin/difficulty-chart
I don't see any reason why it would decrease. It's the best money ever invented, so it makes sense that more and more miners are interested in it over time.
You mentioned graphic cards, so I guess you're referring to mining alt coins. In that case this should be moved to the appropriate section of the forum.
live chart here: https://www.coinwarz.com/mining/bitcoin/difficulty-chart
I don't see any reason why it would decrease. It's the best money ever invented, so it makes sense that more and more miners are interested in it over time.
You mentioned graphic cards, so I guess you're referring to mining alt coins. In that case this should be moved to the appropriate section of the forum.
I think it's also worth mentioning the ASIC miners on the BTC blockchain continue to get faster and are readily available.
Hell Bitmain is now selling a 100TH miner for $1900 plus 25% customs charge for those in the US.
I saw that too, but unless you have really great per kWh rates, it doesn't seem worth the capital. The XP's are about 3X more but are about 4X more profitable per day given a normal per kWh price range. Plus, I think energy prices are going back up a bit so whatever is there will be squeezed a bit more.
Still needing one?
YES, do you have a recommendation?
Quick question. Are you talking about alot of machines, because when you say mining machine, is that just like 1 or 2 or even 10? or like 200?
If you are talking 10 or so, just let the seller arrange through a local shipping house. They usually use DHL or UPS and air freight it. I get ASIC miners via air cargo all the time.
If you are talking about a full container, or even a partial container, then you need a freight coordinator. I moved a 40' container with a transformer this way. I can give you the contact but clarify at which scale you are talking.
If its different from the old s19 units then he can just point the blower or hotair on the front of the heatsink near on that chip just to give a bit heat because some parts is not fully soldered there some parts have cold solder joint. So giving them a heat can melt it and gives more contact from chips to the board.
You need to understand that solder issues and heatsink issues are completely different, and they result in different logs regardless of the miner model, if there is an issue with the solder whereby the chip is not in contact with the hashboard, it will cause a board failure such as missing asics or no asics at all.
On the other hand, a loose heatsink will not display any error, in fact, the miner will read all Asics and will run just fine for a few seconds and then stop after throwing a temp error, many people (myself included) thought the issue with the 17 series was about heatsinks losing contact to the chip, but no, it turns out that it's the actual chip, you can confirm that yourself by taking out a few heatsinks and the miner will still get full asic count, mine for a while and those chips without heatsink will without a doubt pass the max temp in a few seconds and will display "over-temp on chain x" power off.
The interesting thing about the XP's is that instead of 50 small heatsinks, it uses one giant heatsink with screws to attach it.
Thanks - I swapped cables / hashboards from another XP on Chain 2 (one of the 3 hashboards) and it cleared the error.
I have another one with the same error on Chain 0 so I know what to do now.
I will need to send these hashboards off for testing / repair but at least I have a whole rig running. Thanks for the suggestion!
Great news, have you actually swapped the hashboard from another miner? It was not possible to mix and match on the previous generation, hopefully the XP works differently.
@Bitmaxz, this is not possible with the new gen miners, the heatsink on the chip front is one whole large block attached with solder/thermal and screws, no way it would do anything like that.
Yes, I moved the hashboard from another XP. That other one is having a different issue. Waiting for parts on it.
Feels like I will be sending that one off to have repaired with 2 broken hashboards and a broken PSU!
With these 3 lines
The software insists that it can still see Chain[2] and that chain 2 has missing chips, so until the line goes away, it will be hard to troubleshoot any further, can you try to swap the data cables between the hashboards and see if this part of the kernel changes?
Also, please use code tag when posting kernel log.
Code:
2022-09-24 02:28:41 Chain[2]: find 3 asic, times 0
2022-09-24 02:28:43 Chain[2]: find 3 asic, times 1
2022-09-24 02:28:45 Chain[2]: find 3 asic, times 2
2022-09-24 02:28:43 Chain[2]: find 3 asic, times 1
2022-09-24 02:28:45 Chain[2]: find 3 asic, times 2
The software insists that it can still see Chain[2] and that chain 2 has missing chips, so until the line goes away, it will be hard to troubleshoot any further, can you try to swap the data cables between the hashboards and see if this part of the kernel changes?
Also, please use code tag when posting kernel log.
Thanks - I swapped cables / hashboards from another XP on Chain 2 (one of the 3 hashboards) and it cleared the error.
I have another one with the same error on Chain 0 so I know what to do now.
I will need to send these hashboards off for testing / repair but at least I have a whole rig running. Thanks for the suggestion!
Anyone know where I can get (or do you have) Z15 hashboards that are broken?
I need the heat sinks off of them (the small ones specifically).
If you have any broken ones, I would be willing to buy them off of you.
I need the heat sinks off of them (the small ones specifically).
If you have any broken ones, I would be willing to buy them off of you.
I am running BraiinsOS on 10 S19 Pros 100Th and find it pretty nice. Beware that you use smaller SD cards (not larger than 8gb) as they don't play well. Also, if you get a low quality SD card, you will be pulling them out and replacing them, so in an immersion cooling situation, that is annoyingly messy.
I use stock PSU's and do not overclock alot (3100W) and find them really stable, absent the SD issue. The immersion mode helps avoid fan simulators if you go that way.
I use stock PSU's and do not overclock alot (3100W) and find them really stable, absent the SD issue. The immersion mode helps avoid fan simulators if you go that way.
I am troubleshooting an issue with 2 of my XP's.
What is weird is that usually, if you have a hashboard issue, you can unplug it and the S19 will run with 2. With an XP, when you unplug it, it throws a different error.
Here is the part that throws the error. I can post the full log if you really need it.
Any insight / best guesses / etc would be appreciated.
2022-09-24 02:27:49 Initializing the power, please wait, this may take up to 2 minutes...
2022-09-24 02:28:19 Slept 30 seconds, diff = 2.
2022-09-24 02:28:29 set_voltage_by_steps to 1500.
2022-09-24 02:28:31 bad chain id = 3
2022-09-24 02:28:35 start up min temp by 75a = 45
2022-09-24 02:28:37 Chain[0]: find 110 asic, times 0
2022-09-24 02:28:39 Chain[1]: find 110 asic, times 0
2022-09-24 02:28:41 Chain[2]: find 3 asic, times 0
2022-09-24 02:28:43 Chain[2]: find 3 asic, times 1
2022-09-24 02:28:45 Chain[2]: find 3 asic, times 2
2022-09-24 02:28:45 Chain 2 only find 3 asic, will power off hash board 2
2022-09-24 02:28:45 ERROR_SOC_INIT: soc init failed!
2022-09-24 02:28:45 stop_mining: soc init failed!
2022-09-24 02:28:45 uninit_temp_info
2022-09-24 02:28:45 do not read temp anymore...
2022-09-24 02:28:45 cancel thread
2022-09-24 02:28:45 ****power off hashboard****
2022-09-24 02:28:45 power off
2022-09-24 02:28:46 temp monitor thread exit
2022-09-24 02:28:56 Version num 65536
2022-09-24 02:28:56 Mask num 0x1fffe000
2022-09-24 02:28:56 Note: addrInterval or corenum is not initialized.
What is weird is that usually, if you have a hashboard issue, you can unplug it and the S19 will run with 2. With an XP, when you unplug it, it throws a different error.
Here is the part that throws the error. I can post the full log if you really need it.
Any insight / best guesses / etc would be appreciated.
2022-09-24 02:27:49 Initializing the power, please wait, this may take up to 2 minutes...
2022-09-24 02:28:19 Slept 30 seconds, diff = 2.
2022-09-24 02:28:29 set_voltage_by_steps to 1500.
2022-09-24 02:28:31 bad chain id = 3
2022-09-24 02:28:35 start up min temp by 75a = 45
2022-09-24 02:28:37 Chain[0]: find 110 asic, times 0
2022-09-24 02:28:39 Chain[1]: find 110 asic, times 0
2022-09-24 02:28:41 Chain[2]: find 3 asic, times 0
2022-09-24 02:28:43 Chain[2]: find 3 asic, times 1
2022-09-24 02:28:45 Chain[2]: find 3 asic, times 2
2022-09-24 02:28:45 Chain 2 only find 3 asic, will power off hash board 2
2022-09-24 02:28:45 ERROR_SOC_INIT: soc init failed!
2022-09-24 02:28:45 stop_mining: soc init failed!
2022-09-24 02:28:45 uninit_temp_info
2022-09-24 02:28:45 do not read temp anymore...
2022-09-24 02:28:45 cancel thread
2022-09-24 02:28:45 ****power off hashboard****
2022-09-24 02:28:45 power off
2022-09-24 02:28:46 temp monitor thread exit
2022-09-24 02:28:56 Version num 65536
2022-09-24 02:28:56 Mask num 0x1fffe000
2022-09-24 02:28:56 Note: addrInterval or corenum is not initialized.
Most of today's miners usually buy and sell ASIC miners through Ebay and Amazon. In the e-commerce market, these are the 2 largest e-commerce sites in the world, but the prices are very high.
Alternatively, you can also order an ASIC miner at the Bitmain homepage. The types of coin miners here are sold at a much cheaper price.
Despite being the 2 largest e-commerce sites, I still wouldn't trust the ASICs sold in them, just like those sold in Alibaba/AliExpress. They could be faulty or not what you expect.Alternatively, you can also order an ASIC miner at the Bitmain homepage. The types of coin miners here are sold at a much cheaper price.
In most official sites like Bitmain, the miners are already sold out.
If you buy any miner through a seller on Ebay, Amazon et al always:
1. First download the latest firmware directly from Bitmain, Canaan or whoever made the miner onto a laptop or other PC that can later be isolated from your network and the internet. After getting the firmware, disconnect the laptop/PC from your network and using either a hub or crossover cable connect it to the miner.
2. Follow instructions on how to flash the new firmware onto the miner. This should remove any chance of malware.
3. Input your pool and workername settings, save & apply. When the miner reboots, make sure the pool and worker information is the same as you put in.
4. Only after all of that should you put the miner onto your network and have it access the internet to start mining.
Not sure where you buy your miners from. I got scammed because I went for the "cheaper price" and then found a few sources that I have successfully bought many ASIC miners from (so far about 40 ASICs). Most new, a few used. Agree on the new firmware update the moment you get them.
Wondering if anyone knows how reliable these machines are.
I'm looking at purchasing a new one through kaboomracks and have heard many horror stories about the S17's - are these ones supposed to be much better?
I'm looking at purchasing a new one through kaboomracks and have heard many horror stories about the S17's - are these ones supposed to be much better?
I am running 20 S19J 100 / 104Th units. They can be finicky (reboots) but only 1 had a power supply blown. No other issues so far (knock on wood).
I have heard others who have had more issues so I count myself lucky.
Thanks everyone. I'll look into this a bit more and possibly send one or two of you a PM for additional information.
Agreed. I've thought about it some more, and even if I'm "mining at a loss" (electricity is costing more than I'm earning), it's still worth it to continue running the miner because I'm heating at a profit (spending about the same amount as I would have on running an electric heater, but gaining revenue, which a normal space heeateer would never do).
Since the primary goal is heating the garage, I'm starting to think that what I want is the ASIC that draws the most amps. That will be most effective at heating the space, and at that point ANY revenue is just a bonus.
The next step here is going to be figuring out where/how to purchase the equipment and how to avoid getting scammed.
You're probably right. If it works well enough, I might even convince some friends and/or family to heat normally unheated spaces this way.
I suspect that it's going to get way too hot in that garage in the summer to run an ASIC. I'm not interested in running extra c and let thooling just to keep the ASIC running year round. Too much effort for too little profit.
My recommendation is that you need a "heater" not necessarily BTC.
Agreed. I've thought about it some more, and even if I'm "mining at a loss" (electricity is costing more than I'm earning), it's still worth it to continue running the miner because I'm heating at a profit (spending about the same amount as I would have on running an electric heater, but gaining revenue, which a normal space heeateer would never do).
Go for a highly profitable model.
Since the primary goal is heating the garage, I'm starting to think that what I want is the ASIC that draws the most amps. That will be most effective at heating the space, and at that point ANY revenue is just a bonus.
The next step here is going to be figuring out where/how to purchase the equipment and how to avoid getting scammed.
The other thing is, once you start seeing the profits, you probably won't sell it.
You're probably right. If it works well enough, I might even convince some friends and/or family to heat normally unheated spaces this way.
Keep it running and enjoy the profits year round! 
I suspect that it's going to get way too hot in that garage in the summer to run an ASIC. I'm not interested in running extra c and let thooling just to keep the ASIC running year round. Too much effort for too little profit.
Here is the thing. You don't want to go off of just "amp pull". You want to look at profit and how you want to leverage it. The other thing is, profit per amp is important, because once you get bit by the mining bug, you may want to buy another. So take watt / volt (240) = amps. Then divide the daily revenue by amps and get a $/amp ratio.
My most protifable miner right now is mid pack on the amp pull, so I actually bought another one last week. You will find your house to be amp constrained really really fast. Go for $ per amp ratio and let that be a guide for you.
You don't, just raise the garage door and put a box fan behind it. I live in Texas, the garage is 99 degrees so I flush out the heat (but I am moving to immersion cooling). You want the heater. If it gets "too hot" then just unplug it for a few months and come back!
Re: New website to monitor CryptoCurrency Correlation. What do you think?
I have Created website where you can monitor real time prices and other important info in a convenient way.
The core idea is to display data from all exchanges (popular) at the same time. I've spend a lot of time and want you to review my work!
My website url: www.cryptocorrelator.com I sure, this project will become popular!
The core idea is to display data from all exchanges (popular) at the same time. I've spend a lot of time and want you to review my work!
My website url: www.cryptocorrelator.com I sure, this project will become popular!
On the Buy Volume and Sell Volume graphs, what is the difference between the blue lines and the red lines?
Re: [11.2kW SOLAR/WIND/MAN] NastyMining Green Energy Project ☀️💨💪🔋
Hello everyone ) I lost all my Bitcoin ,
Can you donate me BTC bitcoin:bc1q7ruwtjwn3ng3gdz3s2kx835p0kt5eds8ft4330
Can you donate me BTC bitcoin:bc1q7ruwtjwn3ng3gdz3s2kx835p0kt5eds8ft4330
What did you learn when you bought your bitcoin? Describe the lesson so you don't repeat it and others can share in your painfully learned wisdom.
Re: Mineitor|Big Update - Powerful Monitoring|Management - New Firmware Available!!
My pool blocks firmware that I can detect violates the license.
It's well known that I do that.
Even in bold red on the home page ...
If you distribute a firmware, you are required to supply the source code upon request.
That's how the GPLv3 license works (and has for more than 10 years)
Since we are discussing this subject in two topics I will continue this discussion on following topic. Seems to me it is off-topic. It's well known that I do that.
Even in bold red on the home page ...
If you distribute a firmware, you are required to supply the source code upon request.
That's how the GPLv3 license works (and has for more than 10 years)
https://bitcointalk.org/index.php?topic=5346051.0
https://mineitor.com/downloads
This is, by definition, 'distributing' firmware.
It is a violation of the cgminer license to distribute this firmware and not supply source code on request.
I am the 2nd main developer of cgminer.
So I'm not at all sure why you think I wouldn't know how the license for cgminer works, nor why I wouldn't feel the need to point out you are violating the license.
You also advertise that people should use this firmware on your site, sounds like a bad idea to advertise to people to violate a license.
[/quote
Kano,
Does this license have a paid license option that doesn't require you to reveal any of the sourcecode? I find these types of "reveal all source code" at times to be excessive. Especially if what is added might be competitive in nature. Are you trying to support the open nature of open source or drive revenue? If you are standing on principle, I get it, but to say "reveal all source code" for the sake of that in a license is a bit tough. Especially in a commercial situation as I have run into that before in a different context and it was such broad overreach that we eliminated its use completely.
I respect the work you do although I am not a consumer of it, I am just a bit curious behind this.
That is why we have one month free subscription for Mineitor! just test it and find out your self.
We have 24/7 support. and also we have features that is unique to Mineitor.
E.g. Remote-browser or Maintenance-Management or Customer-management , ...
This one violates the cgminer license also since they provide a firmware without the miner source code. just test it and find out your self.We have 24/7 support. and also we have features that is unique to Mineitor.
E.g. Remote-browser or Maintenance-Management or Customer-management , ...
Kano,
I think most of the folks running higher end miners don't use custom ASIC code given that it violates warranty, etc. Feels like custom ASIC code is a way to extend the useful life of an old miner and try to make it worth running at a profit.
I use Mineitor as a farm management system to query my stock rigs and give me performance history, temp, etc. So honestly I am not violating anything.
I do wish the old inefficient miners would just die and force folks to buy the newer, highly efficient miners (lowest joule / hash ratio).
Its like trying to keep that old v8 Plymouth going. Let it die, buy something more fuel efficient. The ecosystem is not in that much desperate need of those Th.