question about an S9 I picked up really cheap

MoparMiningLLC

legendary

Activity: 2254

Merit: 2419

EIN: 82-3893490

Thanks for the tips - I have about 3 weeks before the parts come in

wndsnb

hero member

Activity: 544

Merit: 589

Quote from: MoparMiningLLC on September 27, 2019, 10:04:14 PM

I have never soldered a day in my life.

It can be pretty tricky to remove power connectors like that because the traces on the board are big and are typically connected to large areas of copper that act like a heat sink. The guide mikeywith shared has some good advice. The key is to get the whole board or most of it around the connector pretty hot before trying to use a soldering iron to melt the solder on the pins. If you don't, you can end up damaging the board to the point where it will be unusable. A pre-heater is nice, but you can also get away with a heat gun if you are careful. Or just put the whole board in your oven at 275 degrees F for 20 minutes or so and then work quickly after you take it out. Might be a good idea to wrap any other plastic connectors on the board with aluminum foil to protect them.

This stuff for removing surface mount parts can help, but is pretty expensive. It is a very low melting point solder.

https://www.chipquik.com/store/product_info.php?products_id=220001

For a general intro to soldering, I like this guy. They are pretty long videos though.

https://www.youtube.com/watch?v=J5Sb21qbpEQ
https://www.youtube.com/watch?v=fYz5nIHH0iY
https://www.youtube.com/watch?v=b9FC9fAlfQE

MoparMiningLLC

legendary

Activity: 2254

Merit: 2419

EIN: 82-3893490

I ordered the PSU wire harnesses and the Molex 39-30-1060 Shrouded Header

I should have the Molex 39-30-1060 Shrouded Header by Oct 11 or 12 so I will have 2 weeks time to get them replaced on the miner before the cables come in.

I will update once I have parts and miner gets repaired and again once I get the harness and set the miner to workin!

thanks to both of you for your assist!

mikeywith

legendary

Activity: 2436

Merit: 6643

be constructive or S.T.F.U

Quote from: MoparMiningLLC on September 27, 2019, 09:45:02 PM

thanks for this!! I was searching all over - I kept finding sets where only 2 wires fed into the 6pin

Usually searching for these keywords on alibaba/aliexpress will give you better word suggestions, sellers on those sites include as much description as possible in the tittle, and then when you find the product, copy paste the product name in Amazon and bingo !

Quote from: MoparMiningLLC on September 27, 2019, 09:45:02 PM

do they remove easily? I have never had to swap these out in the past and I hope I never have to in the future.

Should be an easy take, you need a few tools those, because those are not plug and play, they need soldering , if you don't have the tools take it to anyone who fixes mobile phones or type of electronics, they should be able to do it in 5 mins.

if you want to do it yourself, i found a guide for you >https://steemit.com/antminer/@qctechno/miner-repair-replace-your-pcie-power-connector-on-antminer-s9-r4-d3-s7 in this guide he also includes a link where you can buy the connectors might be cheaper and faster to deliever than those from Ali express so make sure you check that out too.

Quote from: MoparMiningLLC on September 27, 2019, 09:45:02 PM

I did test the PSU - it tested fine on 110v and on 220v - I just put a meter right where I removed the old wire harness.

That is how you should test it anyway, so good news, you got yourself a 90% working miner, another 20-30$ at most and your miner should be functioning perfectly, this puts you on 1 month to ROI but that still is an excellent deal.

Quote from: DaveF on September 27, 2019, 09:52:01 PM

Yes you can get the connectors @ Amazon:

https://www.amazon.com/gp/product/B005T8SQ9K/

I didn't see that "lot of 6" , price isn't bad at all, go for it, nice catch Dave.

MoparMiningLLC

legendary

Activity: 2254

Merit: 2419

EIN: 82-3893490

Quote from: DaveF on September 27, 2019, 09:52:01 PM

Yes you can get the connectors @ Amazon:

https://www.amazon.com/gp/product/B005T8SQ9K/

How good are you with a soldering iron? Do you have solder / flux / etc?

You can get them off but it's not always easy. There are people on the forum who do the work. But, then you wind up in the loop of buying the parts, paying for shipping, adding a bit of labor costs. Or you can just buy another used one and have a spare one for parts that only cost you $20....

-Dave

ahh yes those are the ones, thanks for finding on Amazon - they are a bit more expensive but I have never used aliexpress and lost 10k on a deal on alibaba so I prefer vendors I have used before.

I have never soldered a day in my life.

I have thought about just using it tell it fries itself - but with my luck it would catch the building on fire and I would lose all my miners lol

I ordered the wires already thanks to @mikeywith but they wont be here till the end of October. Could get a week or so earlier but that was for extra $30

DaveF

legendary

Activity: 3500

Merit: 6320

Crypto Swap Exchange

Yes you can get the connectors @ Amazon:

https://www.amazon.com/gp/product/B005T8SQ9K/

How good are you with a soldering iron? Do you have solder / flux / etc?

You can get them off but it's not always easy. There are people on the forum who do the work. But, then you wind up in the loop of buying the parts, paying for shipping, adding a bit of labor costs. Or you can just buy another used one and have a spare one for parts that only cost you $20....

-Dave

MoparMiningLLC

legendary

Activity: 2254

Merit: 2419

EIN: 82-3893490

Quote from: mikeywith on September 27, 2019, 09:19:53 PM

You got yourself a 2 weeks to ROI miner, that is impressive.

Yep - pure luck!

Quote from: mikeywith on September 27, 2019, 09:19:53 PM

For the PSU 6*pin cables you can buy this product on Amazon:

https://www.amazon.com/gp/offer-listing/B07QSF198K

thanks for this!! I was searching all over - I kept finding sets where only 2 wires fed into the 6pin

Quote from: mikeywith on September 27, 2019, 09:19:53 PM

You also need to change those connectors on the hash board they look bad and they might damage the hash board or the PSU connectors, I couldn't find any on Amazon, but here is a link on

aliexpress > https://www.aliexpress.com/item/32985270707.html

And before you buy the PSU wires, make sure you test it, the PSU might be dead and there would be no point in changing the cables on it.

as for the connectors - yea, I was leary about just testing it for 20 mins or so with the way they looked. do they remove easily? I have never had to swap these out in the past and I hope I never have to in the future.

I did test the PSU - it tested fine on 110v and on 220v - I just put a meter right where I removed the old wire harness.

mikeywith

legendary

Activity: 2436

Merit: 6643

be constructive or S.T.F.U

You got yourself a 2 weeks to ROI miner, that is impressive.

For the PSU 6*pin cables you can buy this product on Amazon:

https://www.amazon.com/gp/offer-listing/B07QSF198K

You also need to change those connectors on the hash board they look bad and they might damage the hash board or the PSU connectors, I couldn't find any on Amazon, but here is a link on

aliexpress > https://www.aliexpress.com/item/32985270707.html

And before you buy the PSU wires, make sure you test it, the PSU might be dead and there would be no point in changing the cables on it.

MoparMiningLLC

legendary

Activity: 2254

Merit: 2419

EIN: 82-3893490

anyone know where I can get these wires? I tested the psu with a meter and it is putting out the correct voltage so just needs new wires. I am going to be testing the miner with an alternative miner in a little bit to see if I can add the pools and get it to work.

update:

by using one of my others miners PSU's and adding the pool info, the miner was up and running! gotta say this was probably the best $20 I ever spent.

here is in the miner GUI (this is a 13.5 Th/s S9) I did update to the latest S9 firmware. no bad chips and running at just over 14 Th/s

and here is it on the pool side:

I ended up putting the PSU back on the S9J as it gets just over 16 Th/s

All that is needed is for me to find a new wiring harness and I should be good! If anyone knows a reputable supplier of them, please let me know. Meanwhile, I will go back to google in my search.

MoparMiningLLC

legendary

Activity: 2254

Merit: 2419

EIN: 82-3893490

I got an S9 for $20 at a yard sale, of all places, the guy claimed that the miner was still good but that due to it's diminished profitability he did not want to buy a new PSU. I figured for $20 it was no real big loss.

So, the S9 has some "burnt" looking pin receptacles on the hashboards, the PSU has melted wires and quite a few burnt looking pin connectors.

I was brave and risked another PSU from one of my known working S9's and plugged in the S9 I bought - the green leds on the controller lit up and eventually the red led's on the hashboards lit up. Here is what the kernel log said (I left it powered for about 5 mins, at which time the fault light came on):

Code:

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.0-xilinx-g16220c3 (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #83 SMP PREEMPT Thu Jul 12 11:42:53 CST 2018
[    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 16800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 126976
[    0.000000] free_area_init_node: node 0, pgdat c074ac00, node_mem_map debd8000
[    0.000000]   Normal zone: 992 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 126976 pages, LIFO batch:31
[    0.000000] PERCPU: Embedded 8 pages/cpu @debc1000 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: 125984
[    0.000000] Kernel command line: noinitrd mem=496M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 364316K/507904K available (5057K kernel code, 284K rwdata, 1928K rodata, 204K init, 258K bss, 143588K 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 : 0xdf800000 - 0xff000000   ( 504 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xdf000000   ( 496 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06da8ac   (6987 kB)
[    0.000000]       .init : 0xc06db000 - 0xc070e380   ( 205 kB)
[    0.000000]       .data : 0xc0710000 - 0xc0757138   ( 285 kB)
[    0.000000]        .bss : 0xc0757144 - 0xc0797bfc   ( 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 df802000
[    0.000000] zynq_clock_init: clkc starts at df802100
[    0.000000] Zynq clock init
[    0.000014] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[    0.000289] ps7-ttc #0 at df804000, irq=43
[    0.000589] Console: colour dummy device 80x30
[    0.000619] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[    0.090241] pid_max: default: 32768 minimum: 301
[    0.090445] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090465] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.092620] CPU: Testing write buffer coherency: ok
[    0.092928] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.092985] Setting up static identity map for 0x4cb118 - 0x4cb170
[    0.093205] L310 cache controller enabled
[    0.093226] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[    0.170985] CPU1: Booted secondary processor
[    0.260217] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.260345] Brought up 2 CPUs
[    0.260363] SMP: Total of 2 processors activated.
[    0.260371] CPU: All CPU(s) started in SVC mode.
[    0.261039] devtmpfs: initialized
[    0.263461] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.264645] regulator-dummy: no parameters
[    0.271496] NET: Registered protocol family 16
[    0.273757] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.276023] cpuidle: using governor ladder
[    0.276036] cpuidle: using governor menu
[    0.283418] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.284929] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.284943] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.285053] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000
[    0.306497] bio: create slab  at 0
[    0.307859] vgaarb: loaded
[    0.308565] SCSI subsystem initialized
[    0.309428] usbcore: registered new interface driver usbfs
[    0.309613] usbcore: registered new interface driver hub
[    0.309833] usbcore: registered new device driver usb
[    0.310673] media: Linux media interface: v0.10
[    0.310833] Linux video capture interface: v2.00
[    0.311813] pps_core: LinuxPPS API ver. 1 registered
[    0.311826] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti 
[    0.311964] PTP clock support registered
[    0.312320] EDAC MC: Ver: 3.0.0
[    0.313523] Advanced Linux Sound Architecture Driver Initialized.
[    0.316218] DMA-API: preallocated 4096 debug entries
[    0.316230] DMA-API: debugging enabled by kernel config
[    0.316300] Switched to clocksource arm_global_timer
[    0.336153] NET: Registered protocol family 2
[    0.337151] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.337208] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.337293] TCP: Hash tables configured (established 4096 bind 4096)
[    0.337340] TCP: reno registered
[    0.337356] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.337386] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.337640] NET: Registered protocol family 1
[    0.337986] RPC: Registered named UNIX socket transport module.
[    0.337999] RPC: Registered udp transport module.
[    0.338007] RPC: Registered tcp transport module.
[    0.338015] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.338027] PCI: CLS 0 bytes, default 64
[    0.338445] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.340437] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.342507] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.342691] msgmni has been set to 967
[    0.343440] io scheduler noop registered
[    0.343453] io scheduler deadline registered
[    0.343494] io scheduler cfq registered (default)
[    0.359023] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.359043] dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.480618] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    1.047395] console [ttyPS0] enabled
[    1.051649] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000
[    1.059251] [drm] Initialized drm 1.1.0 20060810
[    1.076188] brd: module loaded
[    1.085581] loop: module loaded
[    1.094958] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.100774] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.108678] libphy: XEMACPS mii bus: probed
[    1.113052] ------------- phy_id = 0x3625e62
[    1.118077] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.126893] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.133509] ehci-pci: EHCI PCI platform driver
[    1.140762] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[    1.147597] usbcore: registered new interface driver usb-storage
[    1.154429] mousedev: PS/2 mouse device common for all mice
[    1.160542] i2c /dev entries driver
[    1.167506] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[    1.172985] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.178883] Xilinx Zynq CpuIdle Driver started
[    1.183739] sdhci: Secure Digital Host Controller Interface driver
[    1.189880] sdhci: Copyright(c) Pierre Ossman
[    1.194174] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.201047] mmc0: no vqmmc regulator found
[    1.205062] mmc0: no vmmc regulator found
[    1.246319] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.255003] usbcore: registered new interface driver usbhid
[    1.260511] usbhid: USB HID core driver
[    1.265213] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.271509] nand: Micron MT29F2G08ABAEAWP
[    1.275474] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.281417] Bad block table found at page 131008, version 0x01
[    1.287643] Bad block table found at page 130944, version 0x01
[    1.293690] 3 ofpart partitions found on MTD device pl353-nand
[    1.299474] Creating 3 MTD partitions on "pl353-nand":
[    1.304564] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.312611] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.319928] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[    1.330652] TCP: cubic registered
[    1.333891] NET: Registered protocol family 17
[    1.338586] Registering SWP/SWPB emulation handler
[    1.344426] regulator-dummy: disabling
[    1.348733] UBI: attaching mtd1 to ubi0
[    1.875340] UBI: scanning is finished
[    1.886946] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[    1.894002] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.900790] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.907474] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.914312] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[    1.920322] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.927434] UBI: max/mean erase counter: 10/5, WL threshold: 4096, image sequence number: 1113221046
[    1.936550] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[    1.945747] UBI: background thread "ubi_bgt0d" started, PID 1084
[    1.945752] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.949668] ALSA device list:
[    1.949671]   No soundcards found.
[    1.966002] UBIFS: background thread "ubifs_bgt0_0" started, PID 1086
[    1.995029] UBIFS: recovery needed
[    2.072256] UBIFS: recovery completed
[    2.075932] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    2.081876] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.090990] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    2.100874] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.105903] UBIFS: media format: w4/r0 (latest is w4/r0), UUID E8A4479F-B15D-4C7A-964D-0F246E2BB6ED, small LPT model
[    2.117427] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    2.124605] devtmpfs: mounted
[    2.127736] Freeing unused kernel memory: 204K (c06db000 - c070e000)
[    2.959536] random: dd urandom read with 1 bits of entropy available
[    3.366333] 
[    3.366333] bcm54xx_config_init
[    4.426335] 
[    4.426335] bcm54xx_config_init
[    7.427174] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[    7.433258] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[   43.805163] In axi fpga driver!
[   43.808267] request_mem_region OK!
[   43.811621] AXI fpga dev virtual address is 0xdf9fe000
[   43.816781] *base_vir_addr = 0xc51e
[   43.831326] In fpga mem driver!
[   43.834646] request_mem_region OK!
[   43.838261] fpga mem virtual address is 0xe2000000
[   44.625549] 
[   44.625549] bcm54xx_config_init
[   45.725399] 
[   45.725399] bcm54xx_config_init
[   48.725881] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[   48.731906] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[  145.535459] random: nonblocking pool is initialized
main.c:13992: log_level = 4
main.c:14019: This is XILINX board. Totalram:       507486208
main.c:14031: Detect 512MB control board of XILINX
driver-bitmain.c:1776: mmap axi_fpga_addr = 0xb6f36000
driver-bitmain.c:1781: axi_fpga_addr data = 0xc51e
driver-bitmain.c:1797: mmap fpga_mem_addr = 0xb5d2f000
driver-bitmain.c:994: forceFreq=-1 forceFlag=0
driver-bitmain.c:1696: min work minertest[0]:912


main.c:8570: DETECT HW version=0000c51e
main.c:14064: miner ID : 8008c44a5c208814
main.c:14089: Miner Type = S9
main.c:14101: AsicType = 1387
main.c:14104: real AsicNum = 63
main.c:14197: use critical mode to search freq...
driver-bitmain.c:1876: get PLUG ON=0x000000e0
driver-bitmain.c:1946: Find hashboard on Chain[5]
driver-bitmain.c:1946: Find hashboard on Chain[6]
driver-bitmain.c:1946: Find hashboard on Chain[7]
main.c:2282: Check chain[5] PIC fw version=0x03
main.c:2282: Check chain[6] PIC fw version=0x03
main.c:2282: Check chain[7] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[5] has freq in PIC and will jump over...
main.c:9103: Chain[5] has core num in PIC
main.c:9113: Chain[5] ASIC[17] has core num=7
main.c:2282: Check chain[5] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[6] has freq in PIC and will jump over...
main.c:9103: Chain[6] has core num in PIC
main.c:9113: Chain[6] ASIC[0] has core num=5
main.c:9113: Chain[6] ASIC[14] has core num=1
main.c:9113: Chain[6] ASIC[15] has core num=1
main.c:9113: Chain[6] ASIC[25] has core num=2
main.c:9113: Chain[6] ASIC[38] has core num=1
main.c:9113: Chain[6] ASIC[43] has core num=3
main.c:9113: Chain[6] ASIC[44] has core num=15
main.c:9113: Chain[6] ASIC[47] has core num=15
main.c:9113: Chain[6] ASIC[56] has core num=15
main.c:2282: Check chain[6] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[7] has freq in PIC and will jump over...
main.c:9103: Chain[7] has core num in PIC
main.c:9113: Chain[7] ASIC[35] has core num=15
main.c:9113: Chain[7] ASIC[37] has core num=15
main.c:9113: Chain[7] ASIC[40] has core num=1
main.c:2282: Check chain[7] PIC fw version=0x03
main.c:9183: get PIC voltage=91 on chain[5], value=890
main.c:9183: get PIC voltage=125 on chain[6], value=870
main.c:9183: get PIC voltage=125 on chain[7], value=870
main.c:9349: chain[5] temp offset record: 62,-75,0,0,0,0,33,0
main.c:9366: chain[5] temp chip I2C addr=0x98
main.c:9349: chain[6] temp offset record: 62,-79,0,0,0,0,33,0
main.c:9366: chain[6] temp chip I2C addr=0x98
main.c:9349: chain[7] temp offset record: 62,-97,0,0,0,0,33,0
main.c:9366: chain[7] temp chip I2C addr=0x98
main.c:13956: total_exist_chain_num = 3
main.c:9562: CRC error counter=0
main.c:9577: set command mode to VIL
main.c:9649: 
--- check asic number
main.c:9745: After Get ASIC NUM CRC error counter=0
main.c:9768: set_baud=0
main.c:10693: The min freq=700
main.c:10695: set real timeout 52, need sleep=379392
main.c:12825: After TEST CRC error counter=0
main.c:14236: search freq for 1 times, completed chain = 3, total chain num = 3 
board_frq_tuning.c:628: single_board_frq_tuning enter
board_frq_tuning.c:629: min_rate, des_rate, fix_volt:13800, 14000, 880
board_frq_tuning.c:254: force_freq not set, don't need tuning
main.c:14645: restart Miner chance num=2
main.c:14685: waiting for receive_func to exit!
main.c:14699: waiting for pic heart to exit!
main.c:14741:  calling the get rate, writing rate:13500
main.c:13927: bmminer not found= 1829 root       0:00 grep bmminer

main.c:14758: bmminer not found, restart bmminer ...
main.c:13927: bmminer not found=28038 root       0:00 grep bmminer

main.c:14758: bmminer not found, restart bmminer ...
driver-btm-c5.c:12243:bitmain_c5_init: This is user mode for mining
driver-btm-c5.c:12292:bitmain_c5_init: Detect 512MB control board of XILINX
driver-btm-c5.c:12313:bitmain_c5_init: Miner Type = S9
driver-btm-c5.c:12324:bitmain_c5_init: Miner compile time: Wed Jul 31 16:18:27 CST 2019 type: Antminer S9
mp_test_fw.c:64:check_pool_worker: No valid pools, please configure them first!

I am not really versed in what the kernel log should say - I do see the following "errors"

1. "Unable to init USB phy, missing?"
2. "no vqmmc regulator found"
3. multiple instances of "bmminer not found, restart bmminer ..."
4. "No valid pools, please configure them first!" --- this I know how to fix

The first 3 I also see in the kernel logs for my other working S9's and they still work. I was not wanting to leave the miner hooked up to my good psu for long so I powered it down and disconnected it at this point.

My plan is:

1. To remove the 6pin wires from the PSU and use a meter to test the PSU - though, to be honest, I am no electrician I would not know which 2 of the 4 connections in the PSU to test - I assume I need to test it as two sets. At this location:

2. If it tests as being good - to replace the wires and then try the miner again.

My questions are this:

1. Can anyone point me to a source for the wires? I have googled them and see sets but none exactly as the PSU has.
2. Do I need to replace the connections on the hashboards first? If so, does anyone know anyone that does this - and is it worth even doing?
3. Based on the kernel log above, is there something else I am missing or are there other areas of concern within the log that would give reason to assume the miner is toast?

Topic: question about an S9 I picked up really cheap (Read 227 times)