Hello, I've been searching a lot to find the exact product or product number for the U7 part on the S17+ hashboard.
It's almost impossible to find exaclty the specs this part has. I have my electronic suppliers where I buy all my parts, they have a lot of different specs of this part.
Anyone here knows which one it is exactly?
I'll throw in the link to the picture here below:

https://support.bitmain.com/hc/en-us/community/posts/900002830883-S17-hashboard-chip-U7

Hey guys,

Any fellow technicians here have an idea what range of surface mount capacitors and resistors to order for repairing hashboards?
I see a lot of different sizes. But they are too small to measure myself obviously. So it would be helpful if anyone would throw in what kit or ranges to buy so it would cover pretty much most of the S17 model hashboards.
Or just throw in a link and I'll look for it in local shops myself.

Thank you!

Hello guys,

I've recently been digging in to repairing my S17+ hashboards that piled up here.
What are all the possible causes for the famous 0 asic found issues other than bad chips? And I mean on the hashboard itself. Not the control boards, or psu related issues as I'm using a dc power supply and asic test fixture to test these hashboards.

Thanks!

Hey guys,

I just got my test fixture in today from Asic Repair Center in Russia.
Now what's the best way to set everything up for S17+ hashboard chip testing?

Right now I got just an original empty S17+ rig with the psu and controlboard powering my hashboard, but it doesn't seem to give anything more than about 1.3V to my hashboard...

Is it better to just order me a DC adjustable powersupply and power my hashboard with that?
Or is the original psu needed for decent testing?

Do I need to cool off my hashboards with this specific test fixture? I heard it didn't need any cooling as it doesn't let the hashboard hash.

And do I really need an oscilloscope? Is a decent multimeter not enough?

I do have a bunch of hashboards to repair, so I don't mind buying some more tools to get this done.


Thanks for the aid!

Hello

I have a bunch of S17+ hashboards piled up for repair and I've been keeping busy with figuring out as much as I can. Sadly for technicians that like to do everything themselves like me, there is not much detailed info out there on this issue. Most info I found were in Russian or some other foreign language I couldn't understand.

So to repair my hashboards I'm left with a few questions I hope you guys can help me out.
I'm an electrician myself and I have quite some tools in my workshop so that's not really an issue.

1) Until now I used the black bitmain glue to stick the heatsinks back on, but I found that the chips with the glue got hotter. Now I would like to try using soldering
    tin to fix the heatsinks back on the chips. Can anyone tell me exactly what tin I need to buy?

2) How do you guys figure out which chip exactly is malfunctioning? I got a voltmeter, I got the Zeus test fixture (but in an earlier topic a few people told me that
    test fixture is practically useless as it keeps turning off the hashboard). Is it possible to measure the malfunctioning chip by resistance? If so, does someone
    know what resistance in Ohm every measuring point needs to be approximately? Or is the only way to measure by voltage and powering on the hashboard?

3) I also see a lot of Temperature sensor errors. But sadly can't find a lot of info about how to measure it. How can I measure the temperature sensors?

4) I often use my Supersonic bath to clean the hashboards, as I find a lot of times the chip legs rusted and bridged together, this way helps a lot to get
    them nice and clean, but the heatsinks usually fall off when I do that. Does anyone know if they sell a heatsink template for hashboards so we could glue/solder
    the heatsinks much faster on the hashboard? Been looking all over google, but can't find anything. I'm thinking of buying an aluminum 3d printer just to make
    that now...


Thank you guys for responding!

Hello there,

So I have a whole bunch of pain in the ass defect S17+ hashboards.
I've been mining for years now so I got quite some equipment and tools laying around.
I also have a Zeus chip tester with the S17+ software and everything.

So I've been fooling around with it for 2 days now trying to find the defect chip.
First pain in the ass: The damn hashboards keep shutting down due to only 64 chips found (you know the regular S17+ bullcrap). This is with the Zeus tester plugged in to it. Is there any way to let the hashboard continually powered on without the automatic shut down so I get enough time to measure the chips with my volt-meter?

It's a real pain in the ass to push the test button every few seconds and wait for half a minute for the whole damn thing to power up.

Hello,

Just got me an S9 with hiveon on it. I want to flash the original bitmain fw on it using an SD but somehow it's impossible.
when I unplug the hashboards and fans, or as soon as I unplug 1 of the boards, the control board doesn't turn on for some reason.
I tried finding the option to turn off the hardware security, but can't find it anywhere.

Who can help me out?

Hello,

I have received a bunch of used S17+ miners from china with a bunch of hashboards not working due to A LOT of loose heatsinks and hashboards showing 0 Asics found.
So I'm interchanging working hashboards between the miners to make a few complete working miners.

Now the problem is a working hashboard in the original miner doesn't work when I take it out and put it in another miner.
I've read that these hashboards are coded and tied to it's original miner.
Is there a way to reset the hash board code without having to buy a 300$ hash board code editor?

Or any other tips I can use?

Hi,

I have a bunch of APW3++ PSU fans that I have to replace. I'm used to repairing these things. But now I wanna order a bunch of 2-pin female connectors online. Somebody here knows perhaps what the exact name of these connectors is? There are hundreds of types on these professional webshops. But it's so small it's hard to see on the pictures which one it is exactly...

Thanks!

So my PSU burned or blew it a while ago. I sent the PSU to bitmain for repair under warranty. When it came back, my S17+ just didn't start mining again.

It keeps saying:

ERROR: driver-btm-base.c:2156 Failed to initialize hash boards

I cleaned it all out, also did a factory Firmware reset with the SD-card firmware. Nothing, keeps giving me the same Error...

Anyone got any more ideas?

Code:

Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
  Normal zone: 480 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1 
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 202804K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 26572K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
Preemptible hierarchical RCU implementation.
	Build-time adjustment of leaf fanout to 32.
	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 13532K (ccdca000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 10/4, WL threshold: 4096, image sequence number: 237714726
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID FF09433B-E002-4C29-97EC-6220DDC4BB36, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 58/27, WL threshold: 4096, image sequence number: 3265111179
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
random: nonblocking pool is initialized
[2020/06/26 15:24:07] INFO: Detected 256 Mb of RAM
[2020/06/26 15:24:07] INFO: Switching to manual fan control (30 %)
[2020/06/26 15:24:07] INFO: Checking fans
[2020/06/26 15:24:08] INFO: fan[0] - OK
[2020/06/26 15:24:08] INFO: fan[1] - OK
[2020/06/26 15:24:08] INFO: fan[2] - OK
[2020/06/26 15:24:08] INFO: fan[3] - OK
[2020/06/26 15:24:14] INFO: Power ON
[2020/06/26 15:24:16] INFO: Starting FPGA queue
[2020/06/26 15:24:16] INFO: Initializing hash boards
[2020/06/26 15:24:16] INFO: chain[2] - Initializing
[2020/06/26 15:24:16] INFO: chain[1] - Initializing
[2020/06/26 15:24:16] INFO: chain[0] - Initializing
[2020/06/26 15:24:29] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=485 mV tgt=21000 mV
[2020/06/26 15:24:29] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/06/26 15:24:29] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:24:29] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/06/26 15:24:30] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=509 mV tgt=21000 mV
[2020/06/26 15:24:30] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/06/26 15:24:30] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:24:30] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2020/06/26 15:24:30] ERROR: driver-btm-chain.c:687 chain[0] - Voltage is different, cur=461 mV tgt=21000 mV
[2020/06/26 15:24:30] ERROR: driver-btm-chain.c:471 chain[0] - Failed to set start up voltage
[2020/06/26 15:24:30] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:24:30] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2020/06/26 15:24:30] WARN: All chains are disabled or disconnected
[2020/06/26 15:24:30] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2020/06/26 15:24:30] INFO: Shutting down the miner
[2020/06/26 15:24:30] INFO: Stopping FPGA queue
[2020/06/26 15:24:30] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:24:30] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:24:30] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:24:30] INFO: Power OFF
[2020/06/26 15:24:57] INFO: Detected 256 Mb of RAM
[2020/06/26 15:24:57] INFO: Switching to manual fan control (30 %)
[2020/06/26 15:24:57] INFO: Checking fans
[2020/06/26 15:24:58] INFO: fan[0] - OK
[2020/06/26 15:24:58] INFO: fan[1] - OK
[2020/06/26 15:24:58] INFO: fan[2] - OK
[2020/06/26 15:24:58] INFO: fan[3] - OK
[2020/06/26 15:25:04] INFO: Power ON
[2020/06/26 15:25:06] INFO: Starting FPGA queue
[2020/06/26 15:25:06] INFO: Initializing hash boards
[2020/06/26 15:25:06] INFO: chain[2] - Initializing
[2020/06/26 15:25:06] INFO: chain[1] - Initializing
[2020/06/26 15:25:06] INFO: chain[0] - Initializing
[2020/06/26 15:25:19] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=485 mV tgt=21000 mV
[2020/06/26 15:25:19] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/06/26 15:25:19] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:25:19] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/06/26 15:25:20] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=509 mV tgt=21000 mV
[2020/06/26 15:25:20] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/06/26 15:25:20] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:25:20] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2020/06/26 15:25:20] ERROR: driver-btm-chain.c:687 chain[0] - Voltage is different, cur=461 mV tgt=21000 mV
[2020/06/26 15:25:20] ERROR: driver-btm-chain.c:471 chain[0] - Failed to set start up voltage
[2020/06/26 15:25:20] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:25:20] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2020/06/26 15:25:20] WARN: All chains are disabled or disconnected
[2020/06/26 15:25:20] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2020/06/26 15:25:20] INFO: Shutting down the miner
[2020/06/26 15:25:20] INFO: Stopping FPGA queue
[2020/06/26 15:25:20] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:25:20] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:25:20] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:25:20] INFO: Power OFF
[2020/06/26 15:25:47] INFO: Detected 256 Mb of RAM
[2020/06/26 15:25:47] INFO: Switching to manual fan control (30 %)
[2020/06/26 15:25:47] INFO: Checking fans
[2020/06/26 15:25:48] INFO: fan[0] - OK
[2020/06/26 15:25:48] INFO: fan[1] - OK
[2020/06/26 15:25:48] INFO: fan[2] - OK
[2020/06/26 15:25:48] INFO: fan[3] - OK
[2020/06/26 15:25:54] INFO: Power ON
[2020/06/26 15:25:56] INFO: Starting FPGA queue
[2020/06/26 15:25:56] INFO: Initializing hash boards
[2020/06/26 15:25:56] INFO: chain[2] - Initializing
[2020/06/26 15:25:56] INFO: chain[1] - Initializing
[2020/06/26 15:25:56] INFO: chain[0] - Initializing
[2020/06/26 15:26:09] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=485 mV tgt=21000 mV
[2020/06/26 15:26:09] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/06/26 15:26:09] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:26:09] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/06/26 15:26:10] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=508 mV tgt=21000 mV
[2020/06/26 15:26:10] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/06/26 15:26:10] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:26:10] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2020/06/26 15:26:10] ERROR: driver-btm-chain.c:687 chain[0] - Voltage is different, cur=461 mV tgt=21000 mV
[2020/06/26 15:26:10] ERROR: driver-btm-chain.c:471 chain[0] - Failed to set start up voltage
[2020/06/26 15:26:10] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:26:10] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2020/06/26 15:26:10] WARN: All chains are disabled or disconnected
[2020/06/26 15:26:10] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2020/06/26 15:26:10] INFO: Shutting down the miner
[2020/06/26 15:26:11] INFO: Stopping FPGA queue
[2020/06/26 15:26:11] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:26:11] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:26:11] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:26:11] INFO: Power OFF
[2020/06/26 15:26:37] INFO: Detected 256 Mb of RAM
[2020/06/26 15:26:37] INFO: Switching to manual fan control (30 %)
[2020/06/26 15:26:37] INFO: Checking fans
[2020/06/26 15:26:38] INFO: fan[0] - OK
[2020/06/26 15:26:38] INFO: fan[1] - OK
[2020/06/26 15:26:38] INFO: fan[2] - OK
[2020/06/26 15:26:38] INFO: fan[3] - OK
[2020/06/26 15:26:44] INFO: Power ON
[2020/06/26 15:26:46] INFO: Starting FPGA queue
[2020/06/26 15:26:46] INFO: Initializing hash boards
[2020/06/26 15:26:46] INFO: chain[2] - Initializing
[2020/06/26 15:26:46] INFO: chain[1] - Initializing
[2020/06/26 15:26:46] INFO: chain[0] - Initializing
[2020/06/26 15:27:00] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=485 mV tgt=21000 mV
[2020/06/26 15:27:00] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/06/26 15:27:00] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:27:00] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/06/26 15:27:00] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=508 mV tgt=21000 mV
[2020/06/26 15:27:00] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/06/26 15:27:00] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:27:00] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2020/06/26 15:27:01] ERROR: driver-btm-chain.c:687 chain[0] - Voltage is different, cur=461 mV tgt=21000 mV
[2020/06/26 15:27:01] ERROR: driver-btm-chain.c:471 chain[0] - Failed to set start up voltage
[2020/06/26 15:27:01] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:27:01] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2020/06/26 15:27:01] WARN: All chains are disabled or disconnected
[2020/06/26 15:27:01] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2020/06/26 15:27:01] INFO: Shutting down the miner
[2020/06/26 15:27:01] INFO: Stopping FPGA queue
[2020/06/26 15:27:01] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:27:01] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:27:01] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:27:01] INFO: Power OFF
[2020/06/26 15:27:27] INFO: Detected 256 Mb of RAM
[2020/06/26 15:27:27] INFO: Switching to manual fan control (30 %)
[2020/06/26 15:27:27] INFO: Checking fans
[2020/06/26 15:27:28] INFO: fan[0] - OK
[2020/06/26 15:27:28] INFO: fan[1] - OK
[2020/06/26 15:27:28] INFO: fan[2] - OK
[2020/06/26 15:27:28] INFO: fan[3] - OK
[2020/06/26 15:27:34] INFO: Power ON
[2020/06/26 15:27:37] INFO: Starting FPGA queue
[2020/06/26 15:27:37] INFO: Initializing hash boards
[2020/06/26 15:27:37] INFO: chain[2] - Initializing
[2020/06/26 15:27:37] INFO: chain[1] - Initializing
[2020/06/26 15:27:37] INFO: chain[0] - Initializing
[2020/06/26 15:27:50] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=485 mV tgt=21000 mV
[2020/06/26 15:27:50] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/06/26 15:27:50] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:27:50] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/06/26 15:27:50] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=508 mV tgt=21000 mV
[2020/06/26 15:27:50] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/06/26 15:27:50] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:27:50] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2020/06/26 15:27:51] ERROR: driver-btm-chain.c:687 chain[0] - Voltage is different, cur=461 mV tgt=21000 mV
[2020/06/26 15:27:51] ERROR: driver-btm-chain.c:471 chain[0] - Failed to set start up voltage
[2020/06/26 15:27:51] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:27:51] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2020/06/26 15:27:51] WARN: All chains are disabled or disconnected
[2020/06/26 15:27:51] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2020/06/26 15:27:51] INFO: Shutting down the miner
[2020/06/26 15:27:51] INFO: Stopping FPGA queue
[2020/06/26 15:27:51] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:27:51] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:27:51] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:27:51] INFO: Power OFF
[2020/06/26 15:28:18] INFO: Detected 256 Mb of RAM
[2020/06/26 15:28:18] INFO: Switching to manual fan control (30 %)
[2020/06/26 15:28:18] INFO: Checking fans
[2020/06/26 15:28:19] INFO: fan[0] - OK
[2020/06/26 15:28:19] INFO: fan[1] - OK
[2020/06/26 15:28:19] INFO: fan[2] - OK
[2020/06/26 15:28:19] INFO: fan[3] - OK
[2020/06/26 15:28:25] INFO: Power ON
[2020/06/26 15:28:27] INFO: Starting FPGA queue
[2020/06/26 15:28:27] INFO: Initializing hash boards
[2020/06/26 15:28:27] INFO: chain[2] - Initializing
[2020/06/26 15:28:27] INFO: chain[1] - Initializing
[2020/06/26 15:28:27] INFO: chain[0] - Initializing
[2020/06/26 15:28:40] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=485 mV tgt=21000 mV
[2020/06/26 15:28:40] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/06/26 15:28:40] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:28:40] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/06/26 15:28:40] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=509 mV tgt=21000 mV
[2020/06/26 15:28:40] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/06/26 15:28:40] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:28:40] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2020/06/26 15:28:41] ERROR: driver-btm-chain.c:687 chain[0] - Voltage is different, cur=461 mV tgt=21000 mV
[2020/06/26 15:28:41] ERROR: driver-btm-chain.c:471 chain[0] - Failed to set start up voltage
[2020/06/26 15:28:41] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:28:41] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2020/06/26 15:28:41] WARN: All chains are disabled or disconnected
[2020/06/26 15:28:41] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2020/06/26 15:28:41] INFO: Shutting down the miner
[2020/06/26 15:28:41] INFO: Stopping FPGA queue
[2020/06/26 15:28:41] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:28:41] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:28:41] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:28:41] INFO: Power OFF
[2020/06/26 15:29:08] INFO: Detected 256 Mb of RAM
[2020/06/26 15:29:08] INFO: Switching to manual fan control (30 %)
[2020/06/26 15:29:08] INFO: Checking fans
[2020/06/26 15:29:09] INFO: fan[0] - OK
[2020/06/26 15:29:09] INFO: fan[1] - OK
[2020/06/26 15:29:09] INFO: fan[2] - OK
[2020/06/26 15:29:09] INFO: fan[3] - OK
[2020/06/26 15:29:15] INFO: Power ON
[2020/06/26 15:29:17] INFO: Starting FPGA queue
[2020/06/26 15:29:17] INFO: Initializing hash boards
[2020/06/26 15:29:17] INFO: chain[2] - Initializing
[2020/06/26 15:29:17] INFO: chain[1] - Initializing
[2020/06/26 15:29:17] INFO: chain[0] - Initializing
[2020/06/26 15:29:30] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=485 mV tgt=21000 mV
[2020/06/26 15:29:30] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/06/26 15:29:30] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:29:30] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/06/26 15:29:31] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=508 mV tgt=21000 mV
[2020/06/26 15:29:31] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/06/26 15:29:31] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:29:31] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2020/06/26 15:29:31] ERROR: driver-btm-chain.c:687 chain[0] - Voltage is different, cur=460 mV tgt=21000 mV
[2020/06/26 15:29:31] ERROR: driver-btm-chain.c:471 chain[0] - Failed to set start up voltage
[2020/06/26 15:29:31] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:29:31] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2020/06/26 15:29:31] WARN: All chains are disabled or disconnected
[2020/06/26 15:29:31] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2020/06/26 15:29:31] INFO: Shutting down the miner
[2020/06/26 15:29:31] INFO: Stopping FPGA queue
[2020/06/26 15:29:31] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:29:31] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:29:31] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:29:31] INFO: Power OFF
[2020/06/26 15:29:58] INFO: Detected 256 Mb of RAM
[2020/06/26 15:29:58] INFO: Switching to manual fan control (30 %)
[2020/06/26 15:29:58] INFO: Checking fans
[2020/06/26 15:29:59] INFO: fan[0] - OK
[2020/06/26 15:29:59] INFO: fan[1] - OK
[2020/06/26 15:29:59] INFO: fan[2] - OK
[2020/06/26 15:29:59] INFO: fan[3] - OK
[2020/06/26 15:30:05] INFO: Power ON
[2020/06/26 15:30:07] INFO: Starting FPGA queue
[2020/06/26 15:30:07] INFO: Initializing hash boards
[2020/06/26 15:30:07] INFO: chain[2] - Initializing
[2020/06/26 15:30:07] INFO: chain[1] - Initializing
[2020/06/26 15:30:07] INFO: chain[0] - Initializing
[2020/06/26 15:30:20] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=485 mV tgt=21000 mV
[2020/06/26 15:30:20] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/06/26 15:30:20] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:30:20] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/06/26 15:30:21] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=508 mV tgt=21000 mV
[2020/06/26 15:30:21] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/06/26 15:30:21] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:30:21] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2020/06/26 15:30:21] ERROR: driver-btm-chain.c:687 chain[0] - Voltage is different, cur=485 mV tgt=21000 mV
[2020/06/26 15:30:21] ERROR: driver-btm-chain.c:471 chain[0] - Failed to set start up voltage
[2020/06/26 15:30:21] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:30:21] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2020/06/26 15:30:21] WARN: All chains are disabled or disconnected
[2020/06/26 15:30:21] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2020/06/26 15:30:21] INFO: Shutting down the miner
[2020/06/26 15:30:21] INFO: Stopping FPGA queue
[2020/06/26 15:30:21] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:30:21] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:30:21] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:30:21] INFO: Power OFF
[2020/06/26 15:30:48] INFO: Detected 256 Mb of RAM
[2020/06/26 15:30:48] INFO: Switching to manual fan control (30 %)
[2020/06/26 15:30:48] INFO: Checking fans
[2020/06/26 15:30:49] INFO: fan[0] - OK
[2020/06/26 15:30:49] INFO: fan[1] - OK
[2020/06/26 15:30:49] INFO: fan[2] - OK
[2020/06/26 15:30:49] INFO: fan[3] - OK
[2020/06/26 15:30:55] INFO: Power ON
[2020/06/26 15:30:57] INFO: Starting FPGA queue
[2020/06/26 15:30:57] INFO: Initializing hash boards
[2020/06/26 15:30:57] INFO: chain[2] - Initializing
[2020/06/26 15:30:57] INFO: chain[1] - Initializing
[2020/06/26 15:30:57] INFO: chain[0] - Initializing
[2020/06/26 15:31:10] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=485 mV tgt=21000 mV
[2020/06/26 15:31:10] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/06/26 15:31:10] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:31:10] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/06/26 15:31:11] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=508 mV tgt=21000 mV
[2020/06/26 15:31:11] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/06/26 15:31:11] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:31:11] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2020/06/26 15:31:11] ERROR: driver-btm-chain.c:687 chain[0] - Voltage is different, cur=461 mV tgt=21000 mV
[2020/06/26 15:31:11] ERROR: driver-btm-chain.c:471 chain[0] - Failed to set start up voltage
[2020/06/26 15:31:11] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:31:11] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2020/06/26 15:31:11] WARN: All chains are disabled or disconnected
[2020/06/26 15:31:11] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2020/06/26 15:31:11] INFO: Shutting down the miner
[2020/06/26 15:31:12] INFO: Stopping FPGA queue
[2020/06/26 15:31:12] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:31:12] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:31:12] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:31:12] INFO: Power OFF
[2020/06/26 15:31:38] INFO: Detected 256 Mb of RAM
[2020/06/26 15:31:38] INFO: Switching to manual fan control (30 %)
[2020/06/26 15:31:38] INFO: Checking fans
[2020/06/26 15:31:39] INFO: fan[0] - OK
[2020/06/26 15:31:39] INFO: fan[1] - OK
[2020/06/26 15:31:39] INFO: fan[2] - OK
[2020/06/26 15:31:39] INFO: fan[3] - OK
[2020/06/26 15:31:45] INFO: Power ON
[2020/06/26 15:31:47] INFO: Starting FPGA queue
[2020/06/26 15:31:47] INFO: Initializing hash boards
[2020/06/26 15:31:47] INFO: chain[2] - Initializing
[2020/06/26 15:31:47] INFO: chain[1] - Initializing
[2020/06/26 15:31:47] INFO: chain[0] - Initializing
[2020/06/26 15:32:01] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=485 mV tgt=21000 mV
[2020/06/26 15:32:01] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/06/26 15:32:01] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:32:01] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/06/26 15:32:01] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=509 mV tgt=21000 mV
[2020/06/26 15:32:01] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/06/26 15:32:01] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:32:01] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2020/06/26 15:32:02] ERROR: driver-btm-chain.c:687 chain[0] - Voltage is different, cur=461 mV tgt=21000 mV
[2020/06/26 15:32:02] ERROR: driver-btm-chain.c:471 chain[0] - Failed to set start up voltage
[2020/06/26 15:32:02] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:32:02] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2020/06/26 15:32:02] WARN: All chains are disabled or disconnected
[2020/06/26 15:32:02] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2020/06/26 15:32:02] INFO: Shutting down the miner
[2020/06/26 15:32:02] INFO: Stopping FPGA queue
[2020/06/26 15:32:02] INFO: chain[0] - Shutting down the chain
[2020/06/26 15:32:02] INFO: chain[1] - Shutting down the chain
[2020/06/26 15:32:02] INFO: chain[2] - Shutting down the chain
[2020/06/26 15:32:02] INFO: Power OFF

Hi!

One of my S9's went into error and didn't hash anymore so I flashed my firmware.
After that, it started mining again but my fans don't switch to full speed even after 9TH... temperature rose above 100°C so I quickly rebooted the miner and switched off the asics so it would cool down.

Anyone have any ideas how to solve this? Been trying several firmwear versions all day, can't get it to work properly...

Hello,

I have a bunch of E10.2 miners coming in. These miners usually come with 2 original PSU's. I'm looking for a way to install them with one good quality PSU instead of 2 crappy original PSU's per miner.

What 2500+ Watts PSU do you recommend that has a long-lasting quality for these miners?

Thank you!

Hello,

I'm going to China next Friday and I'm looking for huge amounts of used Antminers.
I've seen online there are recycling centres where all the miners from the miningfarms that are closed down end up.
Does anyone know addresses where I can find these?

Thanks!

Hello,

I'm looking for used S9 antminers. As most miningfarms are shut down or went bankrupt I'm willing to buy used S9 antminers.
If any of you know people selling them, hit me up!

As a first transaction I would buy about 20 pieces. If everything goes well, big orders will be placed to expand my miningfarm.

If you have loads of antminers you want to get rid off, or you know anyone... HIT ME UP PLS!!


Thanks!

[This is something you should know!]

For all the miners using Pandaminer or are thinking about buying Pandaminers:

This is something you should know!


Not so long ago I've bought myself 10 Pandaminers and began mining ETH. I have ordered these together with the PSU's that were included.
About a month ago I was working on my computer when suddenly I noticed a burning smell coming from my mining racks. And went to look what was going on... One of my Pandaminers started melting at the PSU sockets.

Then today, my fire-alarm went off and when I hurried my ass to see what was going on, another Pandaminer was starting to do the very same thing!

This is what was waiting for me THE FIRST TIME:



















And this is what happened with ANOTHER Pandaminer today:





So for all the miners using Pandaminer:

BE VERY CAUTIOUS!

Check your PSU wirings daily and certainly at night before going to sleep!
Fire-alarm is a good investment! It can save your house!

Personally I'm not going to work with Pandaminers anymore in the future due to earlier problems with Pandaminers arriving hugely damaged and lot's more manufacturing issues...

Anyone having an idea what would cause this wires to melt. SHOOT!
I'm thinking maybe the PSU's included in the Pandaminers are worthless...

Hello,

Somehow my Pandaminer lost most of the drivers (including the GPU drivers) when I changed the system language.
Now that's a real problem considering me not having saved all the drivers on a USB before messing up...

1) Could someone help me get back all the drivers needed for the original Windows 10 enterprise version? (a list with all drivers needed is well enough so I could download them myself)

2) If someone perhaps would have a list with all drivers needed for ETH mining with Linux it would be very helpful too...


Greetings!