Title: S19jPro abnormal network - (Will not connect to Pool) Post by: Newbie59 on February 24, 2023, 03:37:21 PM Driving me nuts... after changing pool address to IP and restarting I get Normal Network for 15 seconds on Miner Dashboard. Latest CurrentLog below...any help greatly appreciated. New miner, 12/26/22 firmware (posted 12/29/22)
[ 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.000346] Calibrating delay loop... 545.07 BogoMIPS (lpj=531968) [ 0.015443] pid_max: default: 32768 minimum: 301 [ 0.015668] Security Framework initialized [ 0.015761] Mount-cache hash table entries: 512 [ 0.024275] Initializing cgroup subsys cpuacct [ 0.024308] Initializing cgroup subsys memory [ 0.024368] Initializing cgroup subsys blkio [ 0.024499] CPU: Testing write buffer coherency: ok [ 0.025008] CPU0: thread -1, cpu 0, socket -1, mpidr 0 [ 0.025082] Setting up static identity map for 0x8030a500 - 0x8030a54c [ 0.026441] Brought up 1 CPUs [ 0.026464] SMP: Total of 1 processors activated (545.07 BogoMIPS). [ 0.027745] devtmpfs: initialized [ 0.091394] pinctrl core: initialized pinctrl subsystem [ 0.091645] rstctl core: initialized rstctl subsystem [ 0.092116] regulator-dummy: no parameters [ 0.092616] NET: Registered protocol family 16 [ 0.093273] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.102692] pinctrl-single 44e10800.pinmux: prop pinctrl-0 index 0 invalid phandle [ 0.102864] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568 [ 0.103910] platform 49000000.edma: alias fck already exists [ 0.103940] platform 49000000.edma: alias fck already exists [ 0.103965] platform 49000000.edma: alias fck already exists [ 0.105077] gpiochip_add: registered GPIOs 0 to 31 on device: gpio [ 0.105256] OMAP GPIO hardware version 0.1 [ 0.106638] gpiochip_add: registered GPIOs 32 to 63 on device: gpio [ 0.107938] gpiochip_add: registered GPIOs 64 to 95 on device: gpio [ 0.109398] gpiochip_add: registered GPIOs 96 to 127 on device: gpio [ 0.109913] of_get_named_gpio_flags exited with status 52 [ 0.109943] gpio-rctrl rstctl.3: loaded OK [ 0.114810] omap-gpmc 50000000.gpmc: GPMC revision 6.0 [ 0.118069] hw-breakpoint: debug architecture 0x4 unsupported. [ 0.119963] cpsw.0: No hwaddr in dt. Using 0c:ae:7d:65:65:86 from efuse [ 0.128845] bio: create slab <bio-0> at 0 [ 0.140277] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver [ 0.140561] of_get_named_gpio_flags: can't parse gpios property [ 0.140785] vmmcsd_fixed: 3300 mV [ 0.143898] SCSI subsystem initialized [ 0.145130] omap_i2c 4819c000.i2c: bus 0 rev0.11 at 100 kHz [ 0.145163] omap_i2c 4819c000.i2c: unable to select pin group [ 0.145397] pps_core: LinuxPPS API ver. 1 registered [ 0.145414] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.146996] Switching to clocksource gp_timer [ 0.164203] NET: Registered protocol family 2 [ 0.165255] TCP established hash table entries: 2048 (order: 2, 16384 bytes) [ 0.165344] TCP bind hash table entries: 2048 (order: 3, 40960 bytes) [ 0.165437] TCP: Hash tables configured (established 2048 bind 2048) [ 0.165531] TCP: reno registered [ 0.165556] UDP hash table entries: 256 (order: 1, 12288 bytes) [ 0.165600] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes) [ 0.166013] NET: Registered protocol family 1 [ 0.166567] RPC: Registered named UNIX socket transport module. [ 0.166586] RPC: Registered udp transport module. [ 0.166656] RPC: Registered tcp transport module. [ 0.166672] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.167052] Trying to unpack rootfs image as initramfs... [ 1.064861] Freeing initrd memory: 6496K [ 1.065564] CPU PMU: probing PMU on CPU 0 [ 1.065595] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available [ 1.066107] omap2_mbox_probe: platform not supported [ 1.069815] VFS: Disk quotas dquot_6.5.2 [ 1.070059] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 1.071435] NFS: Registering the id_resolver key type [ 1.071557] Key type id_resolver registered [ 1.071574] Key type id_legacy registered [ 1.071638] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. [ 1.072078] msgmni has been set to 491 [ 1.074914] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250) [ 1.074940] io scheduler noop registered [ 1.074956] io scheduler deadline registered [ 1.075014] io scheduler cfq registered (default) [ 1.078582] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.081027] omap_uart 44e09000.serial: did not get pins for uart0 error: -19 [ 1.081054] of_get_named_gpio_flags: can't parse gpios property [ 1.081324] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0 [ 1.702539] console [ttyO0] enabled [ 1.706794] of_get_named_gpio_flags: can't parse gpios property [ 1.707048] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a OMAP UART1 [ 1.715510] of_get_named_gpio_flags: can't parse gpios property [ 1.715737] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2 [ 1.724129] of_get_named_gpio_flags: can't parse gpios property [ 1.724341] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a OMAP UART4 [ 1.732742] of_get_named_gpio_flags: can't parse gpios property [ 1.732961] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a OMAP UART5 [ 1.754896] brd: module loaded [ 1.765176] loop: module loaded [ 1.769210] bone-capemgr bone_capemgr.8: Failed to find baseboard eeprom node [ 1.779254] ONFI param page 0 valid [ 1.782964] ONFI flash detected [ 1.786290] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron MT29F1G08ABAEAWP), 128MiB, page size: 2048, OOB size: 64 [ 1.798216] omap2-nand: detected x8 NAND flash [ 1.802884] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme [ 1.808472] omap2-nand: using custom ecc layout [ 1.813324] 12 ofpart partitions found on MTD device omap2-nand.0 [ 1.819723] Creating 12 MTD partitions on "omap2-nand.0": [ 1.825405] 0x000000000000-0x000000020000 : "spl" [ 1.832103] 0x000000020000-0x000000040000 : "spl_backup1" [ 1.839468] 0x000000040000-0x000000060000 : "spl_backup2" [ 1.846814] 0x000000060000-0x000000080000 : "spl_backup3" [ 1.854088] 0x000000080000-0x000000240000 : "u-boot" [ 1.862410] 0x000000240000-0x000000260000 : "bootenv" [ 1.869396] 0x000000260000-0x000000280000 : "fdt" [ 1.876032] 0x000000280000-0x000000780000 : "kernel" [ 1.886926] 0x000000800000-0x000001c00000 : "root" [ 1.910254] 0x000001c00000-0x000001e00000 : "config" [ 1.918679] 0x000001e00000-0x000002000000 : "sig" [ 1.926845] 0x000002000000-0x000008000000 : "nvdata" [ 2.014579] OneNAND driver initializing [ 2.020977] mousedev: PS/2 mouse device common for all mice [ 2.028673] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0 [ 2.036170] 44e3e000.rtc: already running [ 2.040672] i2c /dev entries driver [ 2.044981] pps_ldisc: PPS line discipline registered [ 2.050468] Driver for 1-wire Dallas network protocol. [ 2.057725] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec [ 2.065326] cpuidle: using governor ladder [ 2.069652] cpuidle: using governor menu [ 2.074221] of_get_named_gpio_flags exited with status 6 [ 2.074239] of_get_named_gpio_flags: can't parse gpios property [ 2.074255] of_get_named_gpio_flags: can't parse gpios property [ 2.074289] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed [ 2.081515] omap_hsmmc mmc.4: Failed to get rstctl; not using any [ 2.088326] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25 [ 2.095554] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24 [ 2.102873] mmc.4 supply vmmc_aux not found, using dummy regulator [ 2.109842] omap_hsmmc mmc.4: pins are not configured from the driver [ 2.143779] of_get_named_gpio_flags exited with status -517 [ 2.143843] platform gpio-leds.7: Driver leds-gpio requests probe deferral [ 2.151627] ledtrig-cpu: registered to indicate activity on CPUs [ 2.158429] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36 [ 2.165627] omap-sham 53100000.sham: hw accel on OMAP rev 4.3 [ 2.173692] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2 [ 2.179979] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5 [ 2.187165] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6 [ 2.195476] nf_conntrack version 0.5.0 (3935 buckets, 15740 max) [ 2.202952] ip_tables: (C) 2000-2006 Netfilter Core Team [ 2.208732] TCP: cubic registered [ 2.212275] Initializing XFRM netlink socket [ 2.216906] NET: Registered protocol family 10 [ 2.223000] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 2.228947] NET: Registered protocol family 17 [ 2.233721] NET: Registered protocol family 15 [ 2.238568] Key type dns_resolver registered [ 2.243149] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3 [ 2.251228] ThumbEE CPU extension supported. [ 2.255749] Registering SWP/SWPB emulation handler [ 2.261854] registered taskstats version 1 [ 2.267632] of_get_named_gpio_flags exited with status -517 [ 2.267701] platform gpio-leds.7: Driver leds-gpio requests probe deferral [ 2.324888] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [ 2.331308] davinci_mdio 4a101000.mdio: detected phy mask fffffffe [ 2.346087] libphy: 4a101000.mdio: probed [ 2.350434] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720 [ 2.360529] of_get_named_gpio_flags exited with status -517 [ 2.360592] platform gpio-leds.7: Driver leds-gpio requests probe deferral [ 2.368085] Detected MACID = 0c:ae:7d:65:65:86 [ 2.372767] cpsw 4a100000.ethernet: NAPI disabled [ 2.379748] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) [ 2.388929] cpu0 supply cpu0 not found, using dummy regulator [ 2.395413] cpufreq_cpu0: failed to scale voltage up: -22 [ 2.401236] cpufreq_cpu0: failed to scale voltage up: -22 [ 2.414952] Freeing init memory: 196K [ 2.495698] devpts: called with bogus options [ 2.934440] 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. [ 5.361791] 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. [ 5.800051] net eth0: initializing cpsw version 1.12 (0) [ 5.808388] net eth0: phy found : id is : 0x7c0f1 [ 5.820732] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 8.884014] libphy: 4a101000.mdio:00 - Link is Up - 100/Full [ 8.892227] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 11.466377] register uart_trans chrdev success. [ 11.471875] tty port open success [/dev/ttyO1]! [ 11.476922] init sucess for tty struct (249:1) [/dev/ttyO1] [ 11.483343] tty port open success [/dev/ttyO2]! [ 11.488338] init sucess for tty struct (249:2) [/dev/ttyO2] [ 11.494699] tty port open success [/dev/ttyO4]! [ 11.500749] init sucess for tty struct (249:4) [/dev/ttyO4] [ 11.511262] tty port open success [/dev/ttyO5]! [ 11.516305] init sucess for tty struct (249:5) [/dev/ttyO5] [ 27.983477] uart trans dev open. [ 27.988423] uart_buf virt addr = 0xcce00000 [ 27.993031] uart_buf phys addr = 0x8ce00000 [ 27.997575] uart_buf pfn = 0x0008ce00 [ 28.004149] uart trans stop send work timer. [ 28.009715] uart trans set chain exist bits:0x7. [ 28.016426] uart trans set work queue count 768. [54288.342036] libphy: 4a101000.mdio:00 - Link is Down [54297.913037] libphy: 4a101000.mdio:00 - Link is Up - 100/Full [54297.919498] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready ===========================================Miner log=========================================== 2000-01-01 00:00:10 Open miner sn file /config/sn error 2000-01-01 00:00:10 Miner compile time: Mon Dec 26 17:19:30 CST 2022 type: Antminer BHB42XXX sn : 2000-01-01 00:00:10 This is fix-freq version 2000-01-01 00:00:10 Miner compile time: Mon Dec 26 17:19:30 CST 2022 type: Antminer BHB42XXX 2000-01-01 00:00:10 commit version: f2ab6bc 2022-12-26 17:08:34, build by: jenkins 2022-12-26 17:32:52 2000-01-01 00:00:10 opt_multi_version = 1 2000-01-01 00:00:10 opt_bitmain_ab = 1 2000-01-01 00:00:10 mid_auto_gen = 1 2000-01-01 00:00:10 opt_bitmain_work_mode = 0 2000-01-01 00:00:10 port 51 already exported 2000-01-01 00:00:10 port 49 already exported 2000-01-01 00:00:10 port 48 already exported 2000-01-01 00:00:10 port 60 already exported 2000-01-01 00:00:10 port 47 already exported 2000-01-01 00:00:10 port 27 already exported 2000-01-01 00:00:10 port 44 already exported 2000-01-01 00:00:10 port 22 already exported 2000-01-01 00:00:10 no board pluged in socket 44 2000-01-01 00:00:10 port 23 already exported 2000-01-01 00:00:10 port 45 already exported 2000-01-01 00:00:10 port 46 already exported 2000-01-01 00:00:11 port 26 already exported 2000-01-01 00:00:11 Note: front fan is power on! 2000-01-01 00:00:11 Note: rear fan is power on! 2000-01-01 00:00:11 start the http log. 2000-01-01 00:00:11 httpListenThread start ret=0 2000-01-01 00:00:11 start listen on 6060 ... 2000-01-01 00:00:16 ==========================capability start========================== 2000-01-01 00:00:16 board num = 3 2000-01-01 00:00:16 board id = 0, chain num = 1 2000-01-01 00:00:16 chain id = 0 2000-01-01 00:00:16 board id = 1, chain num = 1 2000-01-01 00:00:16 chain id = 1 2000-01-01 00:00:16 board id = 2, chain num = 1 2000-01-01 00:00:16 chain id = 2 2000-01-01 00:00:16 ==========================capability end============================ 2000-01-01 00:00:16 chain num = 3 2000-01-01 00:00:16 skip loading levels for now 2000-01-01 00:00:17 load chain 0 eeprom data 2000-01-01 00:00:18 load chain 1 eeprom data 2000-01-01 00:00:19 load chain 2 eeprom data 2000-01-01 00:00:19 i2c_sim_init start 2000-01-01 00:00:19 i2c_sim_init end 2000-01-01 00:00:21 power open power_version = 0x71 2023-02-23 22:02:06 power is not Calibrated 2023-02-23 22:02:07 miner type: Antminer S19j Pro 2023-02-23 22:02:07 multi machine mode 2023-02-23 22:02:07 load machine BHB42601 conf 2023-02-23 22:02:07 machine : BHB42601 2023-02-23 22:02:07 chain_num 4, chain_domain_num 42, chain_asic_num 126, domain_asic_num 3 2023-02-23 22:02:07 abandon mix board! 2023-02-23 22:02:07 abandon mix board! 2023-02-23 22:02:07 fan_eft : 0 fan_pwm : 100 2023-02-23 22:02:07 create thread get_nonce_and_register_thread 2023-02-23 22:02:07 fixed working voltage = 1360 2023-02-23 22:02:07 fixed frequency is 545 2023-02-23 22:02:07 Chain
2023-02-23 22:02:07 Chain [1] BOM Version: 0x0010 2023-02-23 22:02:07 Chain [2] PCB Version: 0x0130 2023-02-23 22:02:07 Chain [2] BOM Version: 0x0010 2023-02-23 22:02:07 Fan check passed. 2023-02-23 22:02:07 uart_trans addr:0xb6c9f000. 2023-02-23 22:02:08 chain[0] PIC jump to app 2023-02-23 22:02:10 Check chain[0] PIC fw version=0x89 2023-02-23 22:02:11 chain[1] PIC jump to app 2023-02-23 22:02:12 Check chain[1] PIC fw version=0x89 2023-02-23 22:02:13 chain[2] PIC jump to app 2023-02-23 22:02:15 Check chain[2] PIC fw version=0x89 2023-02-23 22:02:15 create thread pic_heart_beat_thread 2023-02-23 22:02:15 max sensor num = 4 2023-02-23 22:02:15 STATUS_INITED: soc init done! 2023-02-23 22:02:15 temperature_monitor_thread start... 2023-02-23 22:14:21 reload pool, need recalculate 2023-02-23 22:14:21 set_start_time_point total_tv_start_sys=762 total_tv_end_sys=763 2023-02-23 22:23:02 reload pool, need recalculate 2023-02-23 22:23:02 set_start_time_point total_tv_start_sys=1283 total_tv_end_sys=1284 2023-02-23 23:18:58 reload pool, need recalculate 2023-02-23 23:18:58 set_start_time_point total_tv_start_sys=4639 total_tv_end_sys=4640 2023-02-23 23:21:13 reload pool, need recalculate 2023-02-23 23:21:13 set_start_time_point total_tv_start_sys=4774 total_tv_end_sys=4775 2023-02-23 23:23:54 reload pool, need recalculate 2023-02-23 23:23:54 set_start_time_point total_tv_start_sys=4935 total_tv_end_sys=4936 2023-02-23 23:40:52 reload pool, need recalculate 2023-02-23 23:40:52 set_start_time_point total_tv_start_sys=5953 total_tv_end_sys=5954 Title: Re: S19jPro abnormal network - (Will not connect to Pool) Post by: philipma1957 on February 24, 2023, 03:59:12 PM Driving me nuts... after changing pool address to IP and restarting I get Normal Network for 15 seconds on Miner Dashboard. Latest CurrentLog below...any help greatly appreciated. New miner, 12/26/22 firmware (posted 12/29/22) Code: [ 0.000000] Booting Linux on physical CPU 0x0 first put logs in code Next put in a different pool pool = btc.viabtc.io:3333 miner = philskysteve.888 password = 123 enter the one above for all 3 pools. see if it works if it works you have a bad pool for the pool you are using. do not mine for any long time with the pool I gave you as it is my test pool you would be mining for me. if you mine for 1 day with the address above I would earn about 7 bucks. you only need test for 1 hour to be sure it works I would earn 7/24 = 29 cents Title: Re: S19jPro abnormal network - (Will not connect to Pool) Post by: BitMaxz on February 24, 2023, 04:31:35 PM Have you replaced a new hashboard?
According to your logs, it shows a mixed hashboard, and looks like the problem is related to the serial number according to this logs below Code: 2000-01-01 00:00:10 Open miner sn file /config/sn error Did you replace the hashboard with a new one? or did you buy this unit as used? I hope that next time use the # button to properly put all logs on insert code tag. Title: Re: S19jPro abnormal network - (Will not connect to Pool) Post by: Newbie59 on February 24, 2023, 05:05:20 PM OK thank you both, think I see how to use #. Have tried several pools already. The machine was supposedly new, came from China via HC, bought on NewEgg... Having difficulty navigating this on my cell. Will come back on laptop.
Thank you again Title: Re: S19jPro abnormal network - (Will not connect to Pool) Post by: BitMaxz on February 24, 2023, 10:50:54 PM OK thank you both, think I see how to use #. Have tried several pools already. The machine was supposedly new, came from China via HC, bought on NewEgg... Having difficulty navigating this on my cell. Will come back on laptop. Thank you again Who is the seller on Newegg did you buy this unit? If it's from other sellers there is a possibility they sent you a defective unit with a different hashboard. About the # button, you can find it when editing your post like what we did from our posts above try to edit your thread and put them all under the code tag, or use pastebin.com and paste the URL here. I think you can burn Braiins OS to try if all hashboard are working fine it can bypass mixed hashboard. Title: Re: S19jPro abnormal network - (Will not connect to Pool) Post by: mikeywith on February 24, 2023, 11:50:05 PM Driving me nuts... after changing pool address to IP and restarting I get Normal Network for 15 seconds on Miner Dashboard. What IP? do you mean putting the pool's IP address instead of the stratum URL? please post some pictures of the pool details you entered and the status page/dashboard. as for this line in the kernel log Code: 2000-01-01 00:00:10 Open miner sn file /config/sn error You can just ignore it for now, I don't see anything critically wrong in the kernel log you posted, and I also think it's incomplete for some reason. **To post pictures, simply upload them to this website https://imgbb.com/ and paste the links. Title: Re: S19jPro abnormal network - (Will not connect to Pool) Post by: Newbie59 on February 26, 2023, 04:36:58 PM Thank you All! Newbie error, had a security feature in my router blocking the connection. All good now. So I hear ANTPOOL is bad and I should mine on another pool...
Title: Re: S19jPro abnormal network - (Will not connect to Pool) Post by: BitMaxz on February 26, 2023, 11:31:23 PM Thank you All! Newbie error, had a security feature in my router blocking the connection. All good now. So I hear ANTPOOL is bad and I should mine on another pool... Antpool is not bad since they are pool related to Bitcoin mining most of the Antivirus/malware block this even ISP/routers. Changing DNS or dropping down the router firewall or switching to another pool should fix any network-related issue. It's weird it looks like it works even with mixed hashboard. Title: Re: S19jPro abnormal network - (Will not connect to Pool) Post by: askmannn on May 17, 2023, 05:21:51 AM Thank you All! Newbie error, had a security feature in my router blocking the connection. All good now. So I hear ANTPOOL is bad and I should mine on another pool... Hello . I'm newbie too. i am having the same problem right now. Can you explain in detail how you solved the problem? thanks for your help.Title: Re: S19jPro abnormal network - (Will not connect to Pool) Post by: BitMaxz on May 17, 2023, 06:35:41 AM Thank you All! Newbie error, had a security feature in my router blocking the connection. All good now. So I hear ANTPOOL is bad and I should mine on another pool... Hello . I'm newbie too. i am having the same problem right now. Can you explain in detail how you solved the problem? thanks for your help.Based on what he said the issue comes from the router that prevents the miner to connect to mining pool. You can also try to switch your miner to static IP and then add DNS to bypass those firewall on the router or setup your router to disable firewall. Title: Re: S19jPro abnormal network - (Will not connect to Pool) Post by: mikeywith on May 18, 2023, 12:05:31 AM Hello . I'm newbie too. i am having the same problem right now. Can you explain in detail how you solved the problem? thanks for your help. You are not having the same issue, you are having a similar issue, and thus the solution is probably different, it's very uncommon to have a router that would block mining pools for no apparent reason, so OP's case was very special and you shouldn't follow his path without having done your own troubleshooting, so go ahead and start your own topic, make sure you provide the following: -Image of the status page. -Image of pool settings. -Kernel log. Title: Re: S19jPro abnormal network - (Will not connect to Pool) Post by: digital.manjam on October 21, 2023, 05:16:08 PM Hello Guys, i m having same issue,
5 new unboxed miners S19j PRO won't connect to mining pool through my 4g Box router, log stops in " 2023-02-23 22:02:15 temperature_monitor_thread start... " As well , I tried to change my connection by sharing a wifi hotspot to my desktop then my desktop shares internet through LAN network, it workes for 1 day (i stopped to enhance air ventilation), after that i stopped working keeps showing Network abnormal, even thus i tried to change DNS in my router, also in my asics settings to cloudflares one 1.1.1.1 rather that 8.8.8.8, i also used a VPN on my hotspot phone, nothing i used a VPN on my desktop not a chance as well I tried to use stratum-ping to ping my mining pools from the desktop, it works fine 0% loss this makes no sense for me as IT engineer ??? ??? ??? Any help please ? i m stuck with 5 miner and have no clue how to fix this, Title: Re: S19jPro abnormal network - (Will not connect to Pool) Post by: BitMaxz on October 22, 2023, 02:25:28 PM ~snip~ Can you share the whole miner logs here don't forget to put them inside the insert code tag and post them hereWould you confirm on the miner's logs if it's "Antminer BHB42XXX" Because Bitmain said it is an abnormal firmware you will need to flash it with the right firmware. To know how to flash it with the right firmware follow this guide below. - https://support.bitmain.com/hc/en-us/articles/21427190625945-Factory-firmware-problem-handling-The-miner-of-the-mining-pool-is-TEST-and-cannot-be-modified- Title: Re: S19jPro abnormal network - (Will not connect to Pool) Post by: digital.manjam on October 24, 2023, 07:38:39 AM ~snip~ Can you share the whole miner logs here don't forget to put them inside the insert code tag and post them hereWould you confirm on the miner's logs if it's "Antminer BHB42XXX" Because Bitmain said it is an abnormal firmware you will need to flash it with the right firmware. To know how to flash it with the right firmware follow this guide below. - https://support.bitmain.com/hc/en-us/articles/21427190625945-Factory-firmware-problem-handling-The-miner-of-the-mining-pool-is-TEST-and-cannot-be-modified- Hi , here is the full log bellow, I flashed firmware with SD card, and from Web Gui with latest releases with no a chance as well. NB : using my phone hotspot+ VPN , then sharing internet from wifi to lan with a laptop , it worked fine for almost 24H , then stopped working. this is the exact same situation for all 5 brand new miners so i think it's due to ISP blocking mining traffic, using f2pool , qntpool and even binance pool, not a chance stratum ping to mining pool throjgh my laptop works fine, but the asic couldn't reach it so it maybe due to ISP, if this could help anyone having same issue. Code: [ 0.000000@0] Booting Linux on physical CPU 0x0 Title: Re: S19jPro abnormal network - (Will not connect to Pool) Post by: mikeywith on October 24, 2023, 11:28:27 AM NB : using my phone hotspot+ VPN , then sharing internet from wifi to lan with a laptop , it worked fine for almost 24H , then stopped working. this is the exact same situation for all 5 brand new miners So they ran just fine behind that VPN for 24 hours and then what happened? your ISP magically decryption the connection and found out that you were connecting to a mining pool and then they did what? it doesn't add up, if your ISP blocked your connection to the VPN then nothing would be accessible not just the mining pools. I would start by using a different mining pool to make sure it isn't the other way around, i.e. it's not the pool that's blocking you. Title: Re: S19jPro abnormal network - (Will not connect to Pool) Post by: BitMaxz on October 24, 2023, 02:00:23 PM NB : using my phone hotspot+ VPN , then sharing internet from wifi to lan with a laptop , it worked fine for almost 24H , then stopped working. If you've successfully flashed them then the issue is in your network or router setup.this is the exact same situation for all 5 brand new miners so i think it's due to ISP blocking mining traffic, using f2pool , qntpool and even binance pool, not a chance stratum ping to mining pool throjgh my laptop works fine, but the asic couldn't reach it so it maybe due to ISP, if this could help anyone having same issue. As you said in your previous post these units are connected from the desktop there might IP problem between the 4g box to the desktop and then the desktop to these units. Since your internet on the desktop is working then the desktop to share internet through the LAN network where these 5 units are connected might have a problem. What I see here is an IP conflict or maybe the PC might have a limit restriction. Better check the network and sharing center of your desktop and maybe the sharing connection to other users is disabled. Or for easy fix why not buy a router instead and connect it directly to your 4g box and connect all miners to the router just don't forget to set all units to DHCP mode. |