Bitcoin Forum
March 22, 2019, 07:31:58 AM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: S9 hardware version  (Read 198 times)
RasyadRidwan
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
March 10, 2019, 07:23:45 AM
Last edit: March 10, 2019, 11:37:42 PM by frodocooper
 #1

i have S9 14Ths. last week my miner is not working its because the following:-

Hardware Version   Socket connect failed: Connection refused
Kernel Version   Linux 3.14.0-xilinx-gb190cb0-dirty #57 SMP PREEMPT Fri Dec 9 14:49:22 CST 2016 (is this correct?)
File System Version   Wed May 3 18:38:52 CST 2017
BMminer Version   (empty)

why its not upgraded even though i already downloaded the firmware and upgraded it?
1553239918
Hero Member
*
Offline Offline

Posts: 1553239918

View Profile Personal Message (Offline)

Ignore
1553239918
Reply with quote  #2

1553239918
Report to moderator
1553239918
Hero Member
*
Offline Offline

Posts: 1553239918

View Profile Personal Message (Offline)

Ignore
1553239918
Reply with quote  #2

1553239918
Report to moderator
100% New Software
PC, Mac, Android, & HTML5 Clients
Krill Rakeback
Low Rake
Bitcoin Poker 3.0
Bad Beat Jackpot
SwC Poker Relaunch
PLAY NOW
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1553239918
Hero Member
*
Offline Offline

Posts: 1553239918

View Profile Personal Message (Offline)

Ignore
1553239918
Reply with quote  #2

1553239918
Report to moderator
mikeywith
Sr. Member
****
Offline Offline

Activity: 350
Merit: 621

be constructive or S.T.F.U


View Profile
March 10, 2019, 01:28:03 PM
 #2

Most likely you made a mistake in your worker/pool.
Make sure you have no spaces in it, also try a different pool.

This error usually means cgminer has not started correctly, in many cases a simple reboot fixes it.
Artemis3
Full Member
***
Offline Offline

Activity: 224
Merit: 268


★777Coin.com★ Fun BTC Casino!


View Profile
March 11, 2019, 12:11:50 AM
 #3

i have S9 14Ths. last week my miner is not working its because the following:-

Hardware Version   Socket connect failed: Connection refused
Kernel Version   Linux 3.14.0-xilinx-gb190cb0-dirty #57 SMP PREEMPT Fri Dec 9 14:49:22 CST 2016 (is this correct?)
File System Version   Wed May 3 18:38:52 CST 2017
BMminer Version   (empty)

why its not upgraded even though i already downloaded the firmware and upgraded it?

One thing i do is ssh to the miner and ping a known server on the internet to verify things are working properly. This could be a configuration mistake. But do wait at least 20~30 minutes, if your local network is sub optimal, it might take that long...

s_falahati
Newbie
*
Offline Offline

Activity: 16
Merit: 40


View Profile
March 11, 2019, 09:05:59 AM
Merited by frodocooper (1)
 #4

Read the logs to see why CGMiner crashed. This is not about the connection to the internet but rather the connection between the UI and the CGMiner's API.
tim-bc
Member
**
Offline Offline

Activity: 350
Merit: 94


View Profile
March 11, 2019, 01:11:23 PM
Merited by frodocooper (1)
 #5

Your bmminer is not running. If you would kindly copy and paste your kernel log here, we can probably figure out why.

Ignore scammers on Skype, Telegram, etc. I will only ever contact you via forum PMs. See profile for fingerprint.
BitMaxz
Legendary
*
Offline Offline

Activity: 1372
Merit: 1132

Bitmain miners is getting worst.


View Profile WWW
March 11, 2019, 08:26:57 PM
 #6

Less info less answer you can get from your problem you must provide a detailed problem or complete kernel logs.

Your problem is both hardware version and Bmminer this usually happen every first boot of the miner so I'd like you to try first to let it run for 20 minutes. If still doesn't work try the troubleshooting guide below.

- Do a hard reset if you don't know how to do the hard reset follow this guide How to reset miner to factory settings
If resetting it to factory default does not work do the next step below

- Flash the miner with this firmware "Antminer-S9-all-201711171757-autofreq-user-Update2UBI-NF.tar.gz"

If this still doesn't work try to follow the troubleshooting guide from Bitmain step by step from here "S9 & T9 series miners: no hardware version found or BMMiner"

RasyadRidwan
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
March 12, 2019, 08:00:36 AM
Last edit: March 12, 2019, 10:04:41 AM by frodocooper
 #7

THIS IS MY 13.5Ths entire kernel log.

Code:
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.0-xilinx-ge8a2f71-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #82 SMP PREEMPT Tue May 16 19:49:53 CST 2017
[    0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Xilinx Zynq
[    0.000000] cma: CMA: reserved 128 MiB at 27800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 258048
[    0.000000] free_area_init_node: node 0, pgdat c0740a40, node_mem_map e6fd8000
[    0.000000]   Normal zone: 1520 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 194560 pages, LIFO batch:31
[    0.000000]   HighMem zone: 496 pages used for memmap
[    0.000000]   HighMem zone: 63488 pages, LIFO batch:15
[    0.000000] PERCPU: Embedded 8 pages/cpu @e6fc0000 s9088 r8192 d15488 u32768
[    0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 256528
[    0.000000] Kernel command line: noinitrd mem=1008M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 884148K/1032192K available (5032K kernel code, 283K rwdata, 1916K rodata, 204K init, 258K bss, 148044K reserved, 253952K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06d1374   (6949 kB)
[    0.000000]       .init : 0xc06d2000 - 0xc0705380   ( 205 kB)
[    0.000000]       .data : 0xc0706000 - 0xc074cf78   ( 284 kB)
[    0.000000]        .bss : 0xc074cf84 - 0xc078d9fc   ( 259 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[    0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] ps7-slcr mapped to f0004000
[    0.000000] zynq_clock_init: clkc starts at f0004100
[    0.000000] Zynq clock init
[    0.000015] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[    0.000307] ps7-ttc #0 at f0006000, irq=43
[    0.000616] Console: colour dummy device 80x30
[    0.000653] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[    0.100252] pid_max: default: 32768 minimum: 301
[    0.100472] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.100494] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.102617] CPU: Testing write buffer coherency: ok
[    0.102967] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.103026] Setting up static identity map for 0x4c4b00 - 0x4c4b58
[    0.103253] L310 cache controller enabled
[    0.103272] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[    0.181034] CPU1: Booted secondary processor
[    0.270227] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.270359] Brought up 2 CPUs
[    0.270379] SMP: Total of 2 processors activated.
[    0.270387] CPU: All CPU(s) started in SVC mode.
[    0.271035] devtmpfs: initialized
[    0.273446] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.274654] regulator-dummy: no parameters
[    0.282351] NET: Registered protocol family 16
[    0.284542] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.286823] cpuidle: using governor ladder
[    0.286837] cpuidle: using governor menu
[    0.294272] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.295792] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.295805] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.295919] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xf0080000
[    0.317622] bio: create slab <bio-0> at 0
[    0.319078] vgaarb: loaded
[    0.319792] SCSI subsystem initialized
[    0.320825] usbcore: registered new interface driver usbfs
[    0.320996] usbcore: registered new interface driver hub
[    0.321347] usbcore: registered new device driver usb
[    0.321867] media: Linux media interface: v0.10
[    0.322023] Linux video capture interface: v2.00
[    0.322260] pps_core: LinuxPPS API ver. 1 registered
[    0.322272] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.322394] PTP clock support registered
[    0.322752] EDAC MC: Ver: 3.0.0
[    0.323786] Advanced Linux Sound Architecture Driver Initialized.
[    0.326634] DMA-API: preallocated 4096 debug entries
[    0.326647] DMA-API: debugging enabled by kernel config
[    0.326731] Switched to clocksource arm_global_timer
[    0.347738] NET: Registered protocol family 2
[    0.348393] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.348489] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.348648] TCP: Hash tables configured (established 8192 bind 8192)
[    0.348710] TCP: reno registered
[    0.348727] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.348778] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.349031] NET: Registered protocol family 1
[    0.349380] RPC: Registered named UNIX socket transport module.
[    0.349392] RPC: Registered udp transport module.
[    0.349400] RPC: Registered tcp transport module.
[    0.349409] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.349422] PCI: CLS 0 bytes, default 64
[    0.349857] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.351870] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.353253] bounce pool size: 64 pages
[    0.354144] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.354348] msgmni has been set to 1486
[    0.355131] io scheduler noop registered
[    0.355144] io scheduler deadline registered
[    0.355182] io scheduler cfq registered (default)
[    0.367472] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.367493] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.491405] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    1.064391] console [ttyPS0] enabled
[    1.068681] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to f0068000
[    1.076296] [drm] Initialized drm 1.1.0 20060810
[    1.093225] brd: module loaded
[    1.102629] loop: module loaded
[    1.112054] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.117884] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.125633] libphy: XEMACPS mii bus: probed
[    1.130033] ------------- phy_id = 0x3625e62
[    1.134746] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.143706] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.150530] ehci-pci: EHCI PCI platform driver
[    1.157772] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[    1.164566] usbcore: registered new interface driver usb-storage
[    1.171445] mousedev: PS/2 mouse device common for all mice
[    1.177570] i2c /dev entries driver
[    1.184480] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[    1.190008] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.195882] Xilinx Zynq CpuIdle Driver started
[    1.200774] sdhci: Secure Digital Host Controller Interface driver
[    1.206887] sdhci: Copyright(c) Pierre Ossman
[    1.211204] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.218087] mmc0: no vqmmc regulator found
[    1.222101] mmc0: no vmmc regulator found
[    1.266768] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.275455] usbcore: registered new interface driver usbhid
[    1.280971] usbhid: USB HID core driver
[    1.285680] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.291966] nand: Micron MT29F2G08ABAEAWP
[    1.295942] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.301891] Bad block table found at page 131008, version 0x01
[    1.308127] Bad block table found at page 130944, version 0x01
[    1.314182] 3 ofpart partitions found on MTD device pl353-nand
[    1.319954] Creating 3 MTD partitions on "pl353-nand":
[    1.325058] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.333108] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.340422] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[    1.349377] TCP: cubic registered
[    1.352614] NET: Registered protocol family 17
[    1.357349] Registering SWP/SWPB emulation handler
[    1.363245] regulator-dummy: disabling
[    1.367584] UBI: attaching mtd1 to ubi0
[    1.895287] UBI: scanning is finished
[    1.906949] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[    1.914001] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.920787] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.927472] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.934311] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[    1.940324] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.947432] UBI: max/mean erase counter: 136/80, WL threshold: 4096, image sequence number: 1134783803
[    1.956706] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[    1.965937] UBI: background thread "ubi_bgt0d" started, PID 1080
[    1.965943] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.969881] ALSA device list:
[    1.969884]   No soundcards found.
[    1.986280] UBIFS: background thread "ubifs_bgt0_0" started, PID 1082
[    2.053151] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    2.059108] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.068209] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    2.078095] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.083123] UBIFS: media format: w4/r0 (latest is w4/r0), UUID B079DD56-06BB-4E31-8F5E-A6604F480DB2, small LPT model
[    2.094662] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    2.102094] devtmpfs: mounted
[    2.105204] Freeing unused kernel memory: 204K (c06d2000 - c0705000)
[    2.943343] random: dd urandom read with 0 bits of entropy available
[    3.336750]
[    3.336750] bcm54xx_config_init
[    3.946766]
[    3.946766] bcm54xx_config_init
[    7.947598] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[    7.953704] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[   21.950589] In axi fpga driver!
[   21.953660] request_mem_region OK!
[   21.957082] AXI fpga dev virtual address is 0xf01fe000
[   21.962158] *base_vir_addr = 0x8c510
[   21.977970] In fpga mem driver!
[   21.981037] request_mem_region OK!
[   21.984607] fpga mem virtual address is 0xf3000000
[   22.786776]
[   22.786776] bcm54xx_config_init
[   23.426755]
[   23.426755] bcm54xx_config_init
[   27.427605] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[   27.433707] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[   97.893921] random: nonblocking pool is initialized
This is XILINX board. Totalram:       1039794176
Detect 1GB control board of XILINX
DETECT HW version=0008c510
miner ID : 80080d2c6880881c
Miner Type = S9
AsicType = 1387
real AsicNum = 63
use critical mode to search freq...
get PLUG ON=0x000000e0
Find hashboard on Chain[5]
Find hashboard on Chain[6]
Find hashboard on Chain[7]
set_reset_allhashboard = 0x0000ffff
Check chain[5] PIC fw version=0x03
Check chain[6] PIC fw version=0x03
Check chain[7] PIC fw version=0x03
chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[5] has freq in PIC and will jump over...
Chain[5] has core num in PIC
Chain[5] ASIC[12] has core num=15
Check chain[5] PIC fw version=0x03
chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[6] has freq in PIC and will jump over...
Chain[6] has core num in PIC
Chain[6] ASIC[20] has core num=1
Chain[6] ASIC[29] has core num=1
Check chain[6] PIC fw version=0x03
chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[7] has freq in PIC and will jump over...
Chain[7] has core num in PIC
Chain[7] ASIC[48] has core num=1
Chain[7] ASIC[50] has core num=4
Chain[7] ASIC[51] has core num=1
Check chain[7] PIC fw version=0x03
get PIC voltage=91 on chain[5], value=890
get PIC voltage=125 on chain[6], value=870
get PIC voltage=125 on chain[7], value=870
set_reset_allhashboard = 0x00000000
chain[5] temp offset record: 62,-5,0,0,0,0,34,0
chain[5] temp chip I2C addr=0x98
chain[6] temp offset record: 62,-5,0,0,0,0,34,0
chain[6] temp chip I2C addr=0x98
chain[7] temp offset record: 62,-6,0,0,0,0,34,0
chain[7] temp chip I2C addr=0x98
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
CRC error counter=0
set command mode to VIL

--- check asic number
After Get ASIC NUM CRC error counter=0
set_baud=0
The min freq=700
set real timeout 52, need sleep=379392
After TEST CRC error counter=0
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
search freq for 1 times, completed chain = 3, total chain num = 3
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
restart Miner chance num=2
waiting for receive_func to exit!
waiting for pic heart to exit!
bmminer not found= 1376 root       0:00 grep bmminer

bmminer not found, restart bmminer ...
This is user mode for mining
Detect 1GB control board of XILINX
Miner Type = S9
Miner compile time: Fri Nov 17 17:57:49 CST 2017 type: Antminer S9set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
set_reset_allhashboard = 0x0000ffff
miner ID : 80080d2c6880881c
set_reset_allhashboard = 0x0000ffff
Checking fans!get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[5] speed=5520
get fan[2] speed=5160
get fan[5] speed=5520
get fan[2] speed=5160
get fan[5] speed=5520
chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
Detect: use voltage limit rules on single board!
Detect: S9_63 use voltage level=1 : 1
Chain[J6] has backup chain_voltage=890
Check chain[5] PIC fw version=0x03
chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
Detect: use voltage limit rules on single board!
Detect: S9_63 use voltage level=1 : 1
Chain[J7] has backup chain_voltage=870
Check chain[6] PIC fw version=0x03
chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
Detect: use voltage limit rules on single board!
Detect: S9_63 use voltage level=1 : 1
Chain[J8] has backup chain_voltage=870
Check chain[7] PIC fw version=0x03
Chain[J6] orignal chain_voltage_pic=91 value=890
Chain[J7] orignal chain_voltage_pic=125 value=870
Chain[J8] orignal chain_voltage_pic=125 value=870
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
Chain[J6] has 63 asic
Chain[J7] has 63 asic
Chain[J8] has 63 asic
Chain[J6] has core num in PIC
Chain[J6] ASIC[12] has core num=15
Chain[J7] has core num in PIC
Chain[J7] ASIC[20] has core num=1
Chain[J7] ASIC[29] has core num=1
Chain[J8] has core num in PIC
Chain[J8] ASIC[48] has core num=1
Chain[J8] ASIC[50] has core num=4
Chain[J8] ASIC[51] has core num=1
miner total rate=13919GH/s fixed rate=13500GH/s
read PIC voltage=940 on chain[5]
Chain:5 chipnum=63
Chain[J6] voltage added=0.0V
Chain:5 temp offset=-5
Chain:5 base freq=637
Asic[ 0]:637
Asic[ 1]:637 Asic[ 2]:637 Asic[ 3]:637 Asic[ 4]:637 Asic[ 5]:637 Asic[ 6]:637 Asic[ 7]:637 Asic[ 8]:637
Asic[ 9]:637 Asic[10]:637 Asic[11]:637 Asic[12]:637 Asic[13]:637 Asic[14]:637 Asic[15]:637 Asic[16]:637
Asic[17]:637 Asic[18]:637 Asic[19]:637 Asic[20]:637 Asic[21]:637 Asic[22]:637 Asic[23]:637 Asic[24]:637
Asic[25]:637 Asic[26]:637 Asic[27]:637 Asic[28]:637 Asic[29]:637 Asic[30]:637 Asic[31]:637 Asic[32]:637
Asic[33]:637 Asic[34]:637 Asic[35]:637 Asic[36]:637 Asic[37]:637 Asic[38]:637 Asic[39]:637 Asic[40]:637
Asic[41]:637 Asic[42]:637 Asic[43]:637 Asic[44]:637 Asic[45]:637 Asic[46]:637 Asic[47]:637 Asic[48]:637
Asic[49]:637 Asic[50]:637 Asic[51]:637 Asic[52]:637 Asic[53]:637 Asic[54]:637 Asic[55]:637 Asic[56]:637
Asic[57]:637 Asic[58]:637 Asic[59]:637 Asic[60]:637 Asic[61]:637 Asic[62]:637
Chain:5 max freq=637
Chain:5 min freq=637

read PIC voltage=940 on chain[6]
Chain:6 chipnum=63
Chain[J7] voltage added=0.0V
Chain:6 temp offset=-5
Chain:6 base freq=656
Asic[ 0]:656
Asic[ 1]:656 Asic[ 2]:656 Asic[ 3]:656 Asic[ 4]:656 Asic[ 5]:656 Asic[ 6]:656 Asic[ 7]:656 Asic[ 8]:656
Asic[ 9]:656 Asic[10]:656 Asic[11]:656 Asic[12]:656 Asic[13]:656 Asic[14]:656 Asic[15]:656 Asic[16]:656
Asic[17]:656 Asic[18]:656 Asic[19]:656 Asic[20]:656 Asic[21]:656 Asic[22]:656 Asic[23]:656 Asic[24]:656
Asic[25]:656 Asic[26]:656 Asic[27]:656 Asic[28]:656 Asic[29]:656 Asic[30]:656 Asic[31]:656 Asic[32]:656
Asic[33]:656 Asic[34]:656 Asic[35]:656 Asic[36]:656 Asic[37]:656 Asic[38]:656 Asic[39]:656 Asic[40]:656
Asic[41]:656 Asic[42]:656 Asic[43]:656 Asic[44]:656 Asic[45]:656 Asic[46]:656 Asic[47]:656 Asic[48]:656
Asic[49]:656 Asic[50]:656 Asic[51]:656 Asic[52]:656 Asic[53]:656 Asic[54]:656 Asic[55]:656 Asic[56]:656
Asic[57]:656 Asic[58]:656 Asic[59]:656 Asic[60]:656 Asic[61]:656 Asic[62]:656
Chain:6 max freq=656
Chain:6 min freq=656

read PIC voltage=940 on chain[7]
Chain:7 chipnum=63
Chain[J8] voltage added=0.0V
Chain:7 temp offset=-6
Chain:7 base freq=656
Asic[ 0]:656
Asic[ 1]:656 Asic[ 2]:656 Asic[ 3]:656 Asic[ 4]:656 Asic[ 5]:656 Asic[ 6]:656 Asic[ 7]:656 Asic[ 8]:656
Asic[ 9]:656 Asic[10]:656 Asic[11]:656 Asic[12]:656 Asic[13]:656 Asic[14]:656 Asic[15]:656 Asic[16]:656
Asic[17]:656 Asic[18]:656 Asic[19]:656 Asic[20]:656 Asic[21]:656 Asic[22]:656 Asic[23]:656 Asic[24]:656
Asic[25]:656 Asic[26]:656 Asic[27]:656 Asic[28]:656 Asic[29]:656 Asic[30]:656 Asic[31]:656 Asic[32]:656
Asic[33]:656 Asic[34]:656 Asic[35]:656 Asic[36]:656 Asic[37]:656 Asic[38]:656 Asic[39]:656 Asic[40]:656
Asic[41]:656 Asic[42]:656 Asic[43]:656 Asic[44]:656 Asic[45]:656 Asic[46]:656 Asic[47]:656 Asic[48]:656
Asic[49]:656 Asic[50]:656 Asic[51]:656 Asic[52]:656 Asic[53]:656 Asic[54]:656 Asic[55]:656 Asic[56]:656
Asic[57]:656 Asic[58]:656 Asic[59]:656 Asic[60]:656 Asic[61]:656 Asic[62]:656
Chain:7 max freq=656
Chain:7 min freq=656


Miner fix freq ...
read PIC voltage=940 on chain[5]
Chain:5 chipnum=63
Chain[J6] voltage added=0.0V
Chain:5 temp offset=-5
Chain:5 base freq=637
Asic[ 0]:637
Asic[ 1]:637 Asic[ 2]:637 Asic[ 3]:637 Asic[ 4]:637 Asic[ 5]:637 Asic[ 6]:637 Asic[ 7]:637 Asic[ 8]:637
Asic[ 9]:637 Asic[10]:637 Asic[11]:637 Detect a bad chip=12 on chain[5], fixed to 400M
Asic[12]:637 Asic[13]:637 Asic[14]:637 Asic[15]:637 Asic[16]:637
Asic[17]:637 Asic[18]:637 Asic[19]:637 Asic[20]:637 Asic[21]:637 Asic[22]:637 Asic[23]:637 Asic[24]:637
Asic[25]:637 Asic[26]:637 Asic[27]:637 Asic[28]:637 Asic[29]:637 Asic[30]:637 Asic[31]:637 Asic[32]:637
Asic[33]:637 Asic[34]:637 Asic[35]:637 Asic[36]:637 Asic[37]:637 Asic[38]:637 Asic[39]:637 Asic[40]:637
Asic[41]:637 Asic[42]:637 Asic[43]:637 Asic[44]:637 Asic[45]:637 Asic[46]:637 Asic[47]:637 Asic[48]:637
Asic[49]:637 Asic[50]:637 Asic[51]:637 Asic[52]:637 Asic[53]:637 Asic[54]:637 Asic[55]:637 Asic[56]:637
Asic[57]:637 Asic[58]:637 Asic[59]:637 Asic[60]:637 Asic[61]:637 Asic[62]:637
Chain:5 max freq=637
Chain:5 min freq=637

read PIC voltage=940 on chain[6]
Chain:6 chipnum=63
Chain[J7] voltage added=0.0V
Chain:6 temp offset=-5
Chain:6 base freq=656
Asic[ 0]:631
Asic[ 1]:631 Asic[ 2]:631 Asic[ 3]:631 Asic[ 4]:631 Asic[ 5]:631 Asic[ 6]:631 Asic[ 7]:631 Asic[ 8]:631
Asic[ 9]:631 Asic[10]:637 Asic[11]:637 Asic[12]:637 Asic[13]:637 Asic[14]:637 Asic[15]:637 Asic[16]:637
Asic[17]:637 Asic[18]:637 Asic[19]:637 Asic[20]:637 Asic[21]:637 Asic[22]:637 Asic[23]:637 Asic[24]:637
Asic[25]:637 Asic[26]:637 Asic[27]:637 Asic[28]:637 Asic[29]:637 Asic[30]:637 Asic[31]:637 Asic[32]:637
Asic[33]:637 Asic[34]:637 Asic[35]:637 Asic[36]:637 Asic[37]:637 Asic[38]:637 Asic[39]:637 Asic[40]:637
Asic[41]:637 Asic[42]:637 Asic[43]:637 Asic[44]:637 Asic[45]:637 Asic[46]:637 Asic[47]:637 Asic[48]:637
Asic[49]:637 Asic[50]:637 Asic[51]:637 Asic[52]:637 Asic[53]:637 Asic[54]:637 Asic[55]:637 Asic[56]:637
Asic[57]:637 Asic[58]:637 Asic[59]:637 Asic[60]:637 Asic[61]:637 Asic[62]:637
Chain:6 max freq=637
Chain:6 min freq=631

read PIC voltage=940 on chain[7]
Chain:7 chipnum=63
Chain[J8] voltage added=0.0V
Chain:7 temp offset=-6
Chain:7 base freq=656
Asic[ 0]:631
Asic[ 1]:631 Asic[ 2]:631 Asic[ 3]:631 Asic[ 4]:631 Asic[ 5]:631 Asic[ 6]:637 Asic[ 7]:637 Asic[ 8]:637
Asic[ 9]:637 Asic[10]:637 Asic[11]:637 Asic[12]:637 Asic[13]:637 Asic[14]:637 Asic[15]:637 Asic[16]:637
Asic[17]:637 Asic[18]:637 Asic[19]:637 Asic[20]:637 Asic[21]:637 Asic[22]:637 Asic[23]:637 Asic[24]:637
Asic[25]:637 Asic[26]:637 Asic[27]:637 Asic[28]:637 Asic[29]:637 Asic[30]:637 Asic[31]:637 Asic[32]:637
Asic[33]:637 Asic[34]:637 Asic[35]:637 Asic[36]:637 Asic[37]:637 Asic[38]:637 Asic[39]:637 Asic[40]:637
Asic[41]:637 Asic[42]:637 Asic[43]:637 Asic[44]:637 Asic[45]:637 Asic[46]:637 Asic[47]:637 Asic[48]:637
Asic[49]:637 Asic[50]:637 Asic[51]:637 Asic[52]:637 Asic[53]:637 Asic[54]:637 Asic[55]:637 Asic[56]:637
Asic[57]:637 Asic[58]:637 Asic[59]:637 Asic[60]:637 Asic[61]:637 Asic[62]:637
Chain:7 max freq=637
Chain:7 min freq=631

max freq = 637
set baud=1
Chain[J6] PIC temp offset=62,-5,0,0,0,0,34,0
chain[5] temp chip I2C addr=0x98
Chain[J6] chip[244] use PIC middle temp offset=-5 typeID=55
New offset Chain[5] chip[244] local:34 remote:37 offset:28
Chain[J6] chip[244] get middle temp offset=28 typeID=55
Chain[J7] PIC temp offset=62,-5,0,0,0,0,34,0
chain[6] temp chip I2C addr=0x98
Chain[J7] chip[244] use PIC middle temp offset=-5 typeID=55
New offset Chain[6] chip[244] local:33 remote:37 offset:26
Chain[J7] chip[244] get middle temp offset=26 typeID=55
Chain[J8] PIC temp offset=62,-6,0,0,0,0,34,0
chain[7] temp chip I2C addr=0x98
Chain[J8] chip[244] use PIC middle temp offset=-6 typeID=55
New offset Chain[7] chip[244] local:34 remote:38 offset:27
Chain[J8] chip[244] get middle temp offset=27 typeID=55
single board rate=4502 voltage limit=890 on chain[5]
get PIC voltage=890 on chain[5], check: must be < 890
single board rate=4566 voltage limit=890 on chain[6]
get PIC voltage=870 on chain[6], check: must be < 890
single board rate=4567 voltage limit=890 on chain[7]
get PIC voltage=870 on chain[7], check: must be < 890
Chain[J6] set working voltage=890 [91]
Chain[J7] set working voltage=870 [125]
Chain[J8] set working voltage=870 [125]
do heat board 8xPatten for 1 times
start send works on chain[5]
start send works on chain[6]
start send works on chain[7]
do read_temp_func once...
do check_asic_reg 0x08
Done check_asic_reg
do read temp on Chain[5]
Chain[5] Chip[62] TempTypeID=55 middle offset=28
Chain[5] Chip[62] local Temp=50
Chain[5] Chip[62] middle Temp=62
Done read temp on Chain[5]
do read temp on Chain[6]
Chain[6] Chip[62] TempTypeID=55 middle offset=26
Chain[6] Chip[62] local Temp=48
Chain[6] Chip[62] middle Temp=59
Done read temp on Chain[6]
do read temp on Chain[7]
Chain[7] Chip[62] TempTypeID=55 middle offset=27
Chain[7] Chip[62] local Temp=50
Chain[7] Chip[62] middle Temp=62
Done read temp on Chain[7]
set FAN speed according to: temp_highest=50 temp_top1[PWM_T]=50 temp_top1[TEMP_POS_LOCAL]=50 temp_change=3 fix_fan_steps=0
set normal FAN speed...
FAN PWM: 50
read_temp_func Done!
CRC error counter=0
tim-bc
Member
**
Offline Offline

Activity: 350
Merit: 94


View Profile
March 12, 2019, 03:36:56 PM
 #8

According to your kernel log it looks like bmminer is starting without any issues. Hashboards look OK too. I would double-check that you entered your pool details correctly. You can also try pinging the pool from your miner's Network > Diagnostics section.

Most likely you made a mistake in your worker/pool.
Make sure you have no spaces in it, also try a different pool.

Ignore scammers on Skype, Telegram, etc. I will only ever contact you via forum PMs. See profile for fingerprint.
mikeywith
Sr. Member
****
Offline Offline

Activity: 350
Merit: 621

be constructive or S.T.F.U


View Profile
March 12, 2019, 10:47:53 PM
Last edit: March 12, 2019, 11:15:40 PM by frodocooper
 #9

I am almost certain that he either has a typo somewhere in his worker/pool details or all the 3 pools are dead , this problem is most often related to what i just mentioned, he however completely ignored that, and he did not update the status of whether or not he double checked those information.

It's a bit hard to help people when they do not follow everybody's answer closely and update their findings.
RasyadRidwan
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
March 13, 2019, 03:32:29 AM
Last edit: March 14, 2019, 12:34:53 AM by frodocooper
 #10

To BitMaxz:
if i do the hard reset, should i leave the power supply to the hash board or just leave it be?

to: tim-bc/ Artemis3:
i tried your solution to pinging the pool from your miner's Network > Diagnostics section and the answer from it is 6 packet data sent and none received (100% loss)
is there any data packet entry involved with the problem I'm facing?

To mikeywith:
sorry for not keeping update, its is because of my time zone is different than your i think and i'm new to this bitcointalk.org still getting use to it.
i did check the pool and the wallet address and plus i register other pool other than i usually use and still it wont mine. (i did double check it)
Before this happens, usually i upgrade the firmware and then set the URL pool and wallet add then reboot it.. within 2 minutes the miner is running like usual. after i switch to 3 phase electrical wiring
this things happen. its not causing 1 or 2 miners.. all 20 of my miner down at the same time. (i'm looking alternative if the electricity is the cause of it whether the voltage is exceeding the max volt)
the pool i am using is f2pool, slushpool, nicehash pool.
mikeywith
Sr. Member
****
Offline Offline

Activity: 350
Merit: 621

be constructive or S.T.F.U


View Profile
March 13, 2019, 03:47:25 AM
Last edit: March 14, 2019, 12:36:00 AM by frodocooper
 #11

if i do the hard reset, should i leave the power supply to the hash board or just leave it be?

no need to disconnect the hash boards, just reset as BitMaxz's guide.

i tried your solution to pinging the pool from your miner's Network > Diagnostics section and the answer from it is 6 packet data sent and none received (100% loss)
is there any data packet entry involved with the problem I'm facing?

maybe you are pinging the wrong url, try to ping this

Code:
de.ckpool.org

after i switch to 3 phase electrical wiring
this things happen. its not causing 1 or 2 miners.. all 20 of my miner down at the same time. (i'm looking alternative if the electricity is the cause of it whether the voltage is exceeding the max volt)
the pool i am using is f2pool, slushpool, nicehash pool.

it's okay, no need to say sorry, if the voltage was exceeding then your miner would probably not even power on, get a voltameter and try to check it, i doubt it's anything to do with voltage, but check to be sure.

have you recently changed your router or ISP ?
RasyadRidwan
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
March 13, 2019, 11:47:55 AM
Last edit: March 14, 2019, 12:38:55 AM by frodocooper
 #12

maybe you are pinging the wrong url, try to ping this

Code:
de.ckpool.org

i will check the ping with this

it's okay, no need to say sorry, if the voltage was exceeding then your miner would probably not even power on, get a voltameter and try to check it, i doubt it's anything to do with voltage, but check to be sure.

have you recently changed your router or ISP ?

i bought a 24 hub router but the ISP is still the same. after that i use the 24hub router to run 10 of my miner and it working perfectly. as i mention earlier after i did the 3 phase wiring everything going down.

i will update as soon as possible after do the URL ping.



Code:
PING de.ckpool.org (88.99.146.100): 56 data bytes
64 bytes from 88.99.146.100: seq=0 ttl=58 time=203.301 ms
64 bytes from 88.99.146.100: seq=1 ttl=58 time=202.876 ms
64 bytes from 88.99.146.100: seq=2 ttl=58 time=202.899 ms
64 bytes from 88.99.146.100: seq=3 ttl=58 time=202.490 ms
64 bytes from 88.99.146.100: seq=4 ttl=58 time=202.395 ms
64 bytes from 88.99.146.100: seq=5 ttl=58 time=201.959 ms

--- de.ckpool.org ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 201.959/202.653/203.301 ms

so it means my address pool is right?

i dont change ISP it still the same but i buy a 24hub router to connect all my miner. as i mention earlier i already use the 24hub router to connect 6 miner, after the upgrade on the 3phase wiring and i connect all the miner with the same router all the miner face same problem.

https://shopee.com.my/TP-LINK-TL-SF1024D-10-100-24-PORT-Desktop-Rackmount-Switch-i.42575106.1180428662
mikeywith
Sr. Member
****
Offline Offline

Activity: 350
Merit: 621

be constructive or S.T.F.U


View Profile
March 13, 2019, 05:37:33 PM
Last edit: March 14, 2019, 12:40:14 AM by frodocooper
 #13

your ping results show that it does have a conection to the internet, despite the long time it took which was about 200ms but that's find because the server i gave you is in Europe and you could be far away from that location, but overall you do have connection to the internet.

i am starting to think that something is up with your router , not the switch which you posted an image for, did you manage to ping the other pools?

i suggest you try pointing the miner to ck pool just to see if it works, use the following

Code:
de.ckpool.org:3333
a valid btc address
x

* in the worker field enter only btc address, nothing else
* make sure there are no spaces in any of the 3 fields.

make sure it looks like this



after you hit save , wait for 2 mins, check if it's working, if not, reboot the miner and wait for 30 mins, then post your results.
s_falahati
Newbie
*
Offline Offline

Activity: 16
Merit: 40


View Profile
March 14, 2019, 12:13:07 AM
Last edit: March 14, 2019, 12:25:43 AM by s_falahati
Merited by frodocooper (2)
 #14

How did you wire your place with three phases? Something similar might happen if the PSU can't provide enough power to the miner. I heard trying to run the miner off 120v input, for example, can cause a similar problem as the PSU is able to provide enough power to turn the miner on but not enough to keep mining.

Please get a multimeter and put it in AC voltage mode (1000V) and check the power input at the plug. It should be in the range of 210v-240v anything more or less (especially less) can cause a similar problem. Then put your multimeter in DC voltage mode (200v) and check the output of the power supply to the miner. It should be like 12v to 12.8v, anything less shows that either power supply can't get enough from the plug and wirings or that the power supply itself is faulty.

If this happened after you upgraded your power wiring and happened to all of the devices, I believe you should try checking if this is in fact caused by this change or not. Maybe move one of the bad devices to your home and check it there.

I personally keep a power meter around to check the connections. This is especially useful to see how much voltage you lose due to the resistance of wirings when the miner is running. I suggest you also keep one around if you have like 10 or 20 miners. It's super useful. Something like this (I never had nor did I ever tested this specific brand and model tho):

https://www.amazon.com/ETbotu-Consumption-Electricity-Analyzer-regulations/dp/B07MMLJ9S3/
RasyadRidwan
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
March 14, 2019, 12:27:55 PM
Last edit: March 15, 2019, 12:04:06 AM by frodocooper
 #15

To mikeywith:
I have tried your suggestion. the result remains the same. (do you need my kernel log?)
I have been researching some youtube videos. is it possible that the Control Board is damaged cause by the electricity? i already ordered 1 S9 Control board just in case, and the bitmain said it will take 2~3 weeks to received. i will keep update when i received it.
one more thing, could it possible to be infected by malware?

To s_falahati:
i will consider to get one.. i believe someone told me its call Volumeter.
mikeywith
Sr. Member
****
Offline Offline

Activity: 350
Merit: 621

be constructive or S.T.F.U


View Profile
March 14, 2019, 03:40:55 PM
Last edit: March 15, 2019, 12:04:29 AM by frodocooper
 #16

it's not possible that all control boards will be damaged by electricity at the same time, plus most of the time anything that has to do with damage when comes to low or high voltage usually takes down the PSU first, not all the time but at least most of the time.

it's really strange.

ok here are a few more things to try

1- try every possible firmware on bitmain website ( make sure you chose the correct firmware s9/s9i/s9j) also make sure the you uncheck the keep-setting when flushing the new firmware.

2- try resetting using all 3 methods mentioned above by BitMaxz

3- try a different firmware like Braiins'  https://bitcointalk.org/index.php?topic=5036844.0
Artemis3
Full Member
***
Offline Offline

Activity: 224
Merit: 268


★777Coin.com★ Fun BTC Casino!


View Profile
March 14, 2019, 07:56:14 PM
Last edit: March 15, 2019, 12:05:29 AM by frodocooper
Merited by frodocooper (2)
 #17

There are various pools you can use without registering, such as kanopool or ckpool where your user is your Bitcoin address.
You can try setting your miner to one of those pools and see if it makes a difference (after 30 mins).

My ping is similar to yours, and my unit can take 20 minutes before showing that its working. I have seen S9s from other people start much faster, but some are slow to start like this.

Your miner has to connect to servers outside, but the pool doesn't connect back to the miner.
With kano pool you can try different ports such as 80 or 443, maybe try those. Your configuration should read like this:

URL:stratum+tcp://stratum.kano.is:3333
Worker:yourbitcoinaddress.workername
Password:x
URL:stratum+tcp://stratum.kano.is:80
Worker:yourbitcoinaddress.workername
Password:x
URL:stratum+tcp://stratum.kano.space:443
Worker:yourbitcoinaddress.workername
Password:x

You must be careful not to add spaces anywhere, and never omit stratum+tcp://

You can try pinging all kano servers and pick the fastest three:

stratum+tcp://or.kano.is:3333 (Oregon)
stratum+tcp://nya.kano.is:3333 (NewYork)
stratum+tcp://nl.kano.is:3333 (Netherlands)
stratum+tcp://de.kano.is:3333 (Germany)
stratum+tcp://jp.kano.is:3333 (Japan)
stratum+tcp://sg.kano.is:3333 (Singapore)

All can take ports 3333, 80, 81, 443 and 8080, and all can replace .is with .space.

BitMaxz
Legendary
*
Offline Offline

Activity: 1372
Merit: 1132

Bitmain miners is getting worst.


View Profile WWW
March 14, 2019, 11:29:11 PM
Last edit: March 15, 2019, 12:06:56 AM by frodocooper
 #18

THIS IS MY 13.5Ths entire kernel log.

[...]

Your kernel logs look fine I don't see any issue in this logs. The only that I noticed in the miner is the temp which is low but it should be fine.

Can you give some screenshot of the dashboard overview and network? It seems that your incoming or outgoing connections are blocked that is why it's not mining.

Can you try to connect 1 miner and try to set the miner to static IP as the image below?



Replace the gateway IP with your ISP IP.

Make sure that you set the DNS with Google DNS because sometimes the miner is blocked by ISP DNS.

If changing Network type and DNS still doesn't work this is not a miner's issue and it might be a wrong router config. Can you do some screenshot on your router status?

Let's check if the router setup is properly set.

RasyadRidwan
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
March 16, 2019, 06:53:05 AM
Last edit: March 16, 2019, 11:18:27 AM by frodocooper
 #19

There are various pools you can use without registering, such as kanopool or ckpool where your user is your Bitcoin address.
You can try setting your miner to one of those pools and see if it makes a difference (after 30 mins)...

hi Artemis3

i have tried to use the stratum and my worker is my bitcoin wallet, the problem still there (hardware version and BMminer version is empty). i will do as Bitmaxz and Mikeywith suggestion then i will come back with the result.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!