Author

Topic: Bitmain's Released Antminer S9, World's First 16nm Miner Ready to Order - page 224. (Read 531173 times)

hero member
Activity: 2534
Merit: 623
I just received my S9 and I got it up and mining. I noticed in that in the Firmware version that came with my S9, i don't have the option to adjust fan speed. This results in an annoying increase and decrease of fan speeds, kind of like a breeze with a slight whistle.

Is there anyway to downgrade the firmware so i can have access to customize fan speed percentage under the "Miner Configuration" page?

Model   GNU/Linux
Hardware Version   4.8.1.3
Kernel Version   Linux 3.14.0-xilinx-gf387dab-dirty #38 SMP PREEMPT Fri Jun 17 20:02:51 CST 2016
BMminer Version   2.0.0

Have a read through the last couple of pages of this thread. You will find your answers  Wink
donator
Activity: 4760
Merit: 4323
Leading Crypto Sports Betting & Casino Platform
New firmware seems a bit scary.
Trying to auto detect frequency? Nah.
No fan control? Nah.

I agree.  I liked the option of being able to underclock and lower the fan speed.  This new firmware might force home miners to go with the quieter R4 option in the future.
hero member
Activity: 770
Merit: 523
One board on S9 (two month old) does not work anymore. It is still under warranty, but is it even worth it sending it to hong kong?
What is the cost to do that from US, approximately? Instructions are peculiar and I have no ability to photograph anything as the miner is in hosting. What did you guys use, UPS or FEDEX?
I would use UPS.

You 'can' open a ticket on bitmainwarranty.com. Just say "no warranty". Their techs may be able to fix. They are pretty good.
Had them fix one of my s9 boards, $175.

Thanks. Still deciding, but leaning toward bitmainwarranty.
In US, I can send priority mail.

Does  your fixed board work OK now?

Yep, cost $13 ups to send there from east coast, they charge $25 ups for return.
I fully expect to have a dead board at some point for my museum. Can't hurt to try out Denver.
Comes tomorrow, they SAID their tech fixed it. I'll let you know tomorrow when I kick it in the unit that is only running two boards at the moment.


There really isn't a reason to skip sending boards to Denver, what we've seen, has always come back , and for under the estimate to ultimate card owner.
Agreed. Have been dealing with them since the S3 days. Always good.
full member
Activity: 219
Merit: 100
Bitcoin Mining Hosting
One board on S9 (two month old) does not work anymore. It is still under warranty, but is it even worth it sending it to hong kong?
What is the cost to do that from US, approximately? Instructions are peculiar and I have no ability to photograph anything as the miner is in hosting. What did you guys use, UPS or FEDEX?
I would use UPS.

You 'can' open a ticket on bitmainwarranty.com. Just say "no warranty". Their techs may be able to fix. They are pretty good.
Had them fix one of my s9 boards, $175.

Thanks. Still deciding, but leaning toward bitmainwarranty.
In US, I can send priority mail.

Does  your fixed board work OK now?

Yep, cost $13 ups to send there from east coast, they charge $25 ups for return.
I fully expect to have a dead board at some point for my museum. Can't hurt to try out Denver.
Comes tomorrow, they SAID their tech fixed it. I'll let you know tomorrow when I kick it in the unit that is only running two boards at the moment.


There really isn't a reason to skip sending boards to Denver, what we've seen, has always come back , and for under the estimate to ultimate card owner.
legendary
Activity: 3892
Merit: 4331
OT: 100 min without a block...wow

what are the random chances of a 100 min block instead of 10min?
this is 10 times longer than an average block.
finally, after 103 min, two in a row
hero member
Activity: 770
Merit: 523
One board on S9 (two month old) does not work anymore. It is still under warranty, but is it even worth it sending it to hong kong?
What is the cost to do that from US, approximately? Instructions are peculiar and I have no ability to photograph anything as the miner is in hosting. What did you guys use, UPS or FEDEX?
I would use UPS.

You 'can' open a ticket on bitmainwarranty.com. Just say "no warranty". Their techs may be able to fix. They are pretty good.
Had them fix one of my s9 boards, $175.

Thanks. Still deciding, but leaning toward bitmainwarranty.
In US, I can send priority mail.

Does  your fixed board work OK now?

Yep, cost $13 ups to send there from east coast, they charge $25 ups for return.
I fully expect to have a dead board at some point for my museum. Can't hurt to try out Denver.
Comes tomorrow, they SAID their tech fixed it. I'll let you know tomorrow when I kick it in the unit that is only running two boards at the moment.
legendary
Activity: 3892
Merit: 4331
One board on S9 (two month old) does not work anymore. It is still under warranty, but is it even worth it sending it to hong kong?
What is the cost to do that from US, approximately? Instructions are peculiar and I have no ability to photograph anything as the miner is in hosting. What did you guys use, UPS or FEDEX?
I would use UPS.

You 'can' open a ticket on bitmainwarranty.com. Just say "no warranty". Their techs may be able to fix. They are pretty good.
Had them fix one of my s9 boards, $175.

Thanks. Still deciding, but leaning toward bitmainwarranty.
In US, I can send priority mail.

Does  your fixed board work OK now?

One board on S9 (two month old) does not work anymore. It is still under warranty, but is it even worth it sending it to hong kong?
What is the cost to do that from US, approximately? Instructions are peculiar and I have no ability to photograph anything as the miner is in hosting. What did you guys use, UPS or FEDEX?
Philipma1957 here in forum has had good experience with BitmainWarranty.
In US it might be a good idea to deal with them.
www.bitmainwarranty.com

thanks. this is probably true re US repair, although typically you have to pay for it.
However, apart from sending cost, you are not supposed to pay for warranty repair in Hong Kong.
What if repair cost close to board cost when you do it in US? Then, it does not make sense.

I would appreciate if someone post re cost of sending a board from US to HK. Thanks.

About 110 via ups.

And you have to claim it to,be 44 usd or lower in value.

So 110 and if it is less lost or damaged you can only collect 44 bucks.

A boards value is around 450.

If you send to Colorado in a small usps flat rate it is 15 and you can insure it for 200 spend 18 total then spend 25 for return so 43 out of pocket and repair is 100 to 225.

So it can be a case of pick your ur poison.

Right now the solar array has 30-38 amps idle power due to my fear of using s9s.

It took me years to get a good power deal and now the gear has become very unreliable.
If s9s worked better I would have six or seven more. Instead I sold most off and I am down to three units.

Thanks, Philip.
hero member
Activity: 770
Merit: 523
One board on S9 (two month old) does not work anymore. It is still under warranty, but is it even worth it sending it to hong kong?
What is the cost to do that from US, approximately? Instructions are peculiar and I have no ability to photograph anything as the miner is in hosting. What did you guys use, UPS or FEDEX?
I would use UPS.

You 'can' open a ticket on bitmainwarranty.com. Just say "no warranty". Their techs may be able to fix. They are pretty good/attentive.
Had them fix one of my s9 boards without Denver warranty, $175. Only one week turnaround/downtime.
hero member
Activity: 770
Merit: 523
Just shut down another s9 scam artist on ebay yesterday. Kept trying to get money after ebay shut it down, said they had stacks of them.
Put their email in the auction not in text, but in a jpg.
Careful folks.

New firmware seems a bit scary.
Trying to auto detect frequency? Nah.
If you could set the freq manually for each board that would be cool.
I like to kick down the freq when the boards act up.


No fan control? Nah.
full member
Activity: 197
Merit: 100
it seem like they solved this problem on the new firmware
last hour i lost my internet connection 2 times ( they still fixing it in my ISP )
first time and when the internet backup all miners start to hash with full hash rate except Batch 17 hash with 9.8TH/s for about 5 minutes then lowered to 6TH/s for 5 minutes then lowered to 3.8 for minutes then return by self to full hash rate ( in the past firmware this non happen until i restart it )

in the second internet cut they all return to full hash rate including B17
sr. member
Activity: 387
Merit: 254
i installed the new firmware and it start and work on 2 minuts only
i hope this issue not returned again

ya it looks like you didnt wait long enough. the miner would take an upwards of 40 minutes to finally start hashing because of all the freq checks it does.
full member
Activity: 197
Merit: 100
i installed the new firmware and it start and work on 2 minuts only
i hope this issue not returned again
full member
Activity: 197
Merit: 100
after fixing my internet i get same error again and after that my miner stop working any more
i reset it but it not help
i think this issue controller related from the beginning
all boards lamp not light and front lamp also not light
just the fans working



here is kernel log i googled this error and it's kernal issue
====================================
[    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
  • 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=/dev/mtdblock1 rootfstype=jffs2 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: 884528K/1032192K available (4764K kernel code, 271K rwdata, 1816K rodata, 200K init, 257K bss, 147664K 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 - 0xc06752f8   (6581 kB)
[    0.000000]       .init : 0xc0676000 - 0xc06a8380   ( 201 kB)
[    0.000000]       .data : 0xc06aa000 - 0xc06edd00   ( 272 kB)
[    0.000000]        .bss : 0xc06edd0c - 0xc072e4fc   ( 258 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.000301] ps7-ttc #0 at f0006000, irq=43
[    0.000603] Console: colour dummy device 80x30
[    0.000640] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328)
[    0.040202] pid_max: default: 32768 minimum: 301
[    0.040412] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.040434] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.042515] CPU: Testing write buffer coherency: ok
[    0.042858] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.042918] Setting up static identity map for 0x482448 - 0x4824a0
[    0.043135] L310 cache controller enabled
[    0.043155] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[    0.121023] CPU1: Booted secondary processor
[    0.210224] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.210353] Brought up 2 CPUs
[    0.210372] SMP: Total of 2 processors activated.
[    0.210380] CPU: All CPU(s) started in SVC mode.
[    0.211027] devtmpfs: initialized
[    0.213405] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.214614] regulator-dummy: no parameters
[    0.221846] NET: Registered protocol family 16
[    0.224026] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.226322] cpuidle: using governor ladder
[    0.226336] cpuidle: using governor menu
[    0.233706] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.235214] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.235227] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.235331] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xf0080000
[    0.256614] bio: create slab at 0
[    0.258029] vgaarb: loaded
[    0.258736] SCSI subsystem initialized
[    0.259620] usbcore: registered new interface driver usbfs
[    0.259800] usbcore: registered new interface driver hub
[    0.260027] usbcore: registered new device driver usb
[    0.260765] media: Linux media interface: v0.10
[    0.260924] Linux video capture interface: v2.00
[    0.261779] pps_core: LinuxPPS API ver. 1 registered
[    0.261793] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[    0.261951] PTP clock support registered
[    0.262312] EDAC MC: Ver: 3.0.0
[    0.263368] Advanced Linux Sound Architecture Driver Initialized.
[    0.266198] DMA-API: preallocated 4096 debug entries
[    0.266212] DMA-API: debugging enabled by kernel config
[    0.266287] Switched to clocksource arm_global_timer
[    0.286360] NET: Registered protocol family 2
[    0.287013] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.287109] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.287268] TCP: Hash tables configured (established 8192 bind 8192)
[    0.287335] TCP: reno registered
[    0.287352] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.287404] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.287663] NET: Registered protocol family 1
[    0.288021] RPC: Registered named UNIX socket transport module.
[    0.288033] RPC: Registered udp transport module.
[    0.288041] RPC: Registered tcp transport module.
[    0.288050] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.288063] PCI: CLS 0 bytes, default 64
[    0.288495] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.290516] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.291911] bounce pool size: 64 pages
[    0.292797] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.292996] msgmni has been set to 1487
[    0.293448] io scheduler noop registered
[    0.293461] io scheduler deadline registered
[    0.293501] io scheduler cfq registered (default)
[    0.305791] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.305811] dma-pl330 f8003000.ps7-dma:    DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.430161] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    1.002553] console [ttyPS0] enabled
[    1.006858] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to f0068000
[    1.014459] [drm] Initialized drm 1.1.0 20060810
[    1.031410] brd: module loaded
[    1.040787] loop: module loaded
[    1.050575] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.056522] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.064203] libphy: XEMACPS mii bus: probed
[    1.068667] ------------- phy_id = 0x3625e62
[    1.073396] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.082103] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.088838] ehci-pci: EHCI PCI platform driver
[    1.096044] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[    1.102868] usbcore: registered new interface driver usb-storage
[    1.109766] mousedev: PS/2 mouse device common for all mice
[    1.115858] i2c /dev entries driver
[    1.122768] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[    1.128350] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.134241] Xilinx Zynq CpuIdle Driver started
[    1.139102] sdhci: Secure Digital Host Controller Interface driver
[    1.145194] sdhci: Copyright(c) Pierre Ossman
[    1.149606] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.156371] mmc0: no vqmmc regulator found
[    1.160388] mmc0: no vmmc regulator found
[    1.196304] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.204968] usbcore: registered new interface driver usbhid
[    1.210482] usbhid: USB HID core driver
[    1.215214] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.221513] nand: Micron MT29F2G08ABAEAWP
[    1.225479] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.231506] Bad block table found at page 131008, version 0x01
[    1.237904] Bad block table found at page 130944, version 0x01
[    1.244046] 4 ofpart partitions found on MTD device pl353-nand
[    1.249828] Creating 4 MTD partitions on "pl353-nand":
[    1.254922] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.262977] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.270304] 0x00000b000000-0x00000ec00000 : "upgrade-rootfs"
[    1.277394] 0x00000ec00000-0x000010000000 : "upgrade-tmp"
[    1.285998] TCP: cubic registered
[    1.289270] NET: Registered protocol family 17
[    1.293903] Registering SWP/SWPB emulation handler
[    1.299568] regulator-dummy: disabling
[    1.303347] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.313610] ALSA device list:
[    1.316569]   No soundcards found.
[    3.348967] jffs2: jffs2_scan_eraseblock(): Node at 0x00d4a7fc {0x1985, 0xe002, 0xe0021985) has invalid CRC 0x00000044 (calculated 0xd7cd6a7b)
[    3.372399] jffs2: Empty flash at 0x00d4f030 ends at 0x00d4f800
[    3.387020] jffs2: Empty flash at 0x00d523f8 ends at 0x00d52800
[    3.393313] jffs2: jffs2_scan_inode_node(): CRC failed on node at 0x00d5dfe8: Read 0xffffffff, calculated 0x031866bc
[    4.739357] jffs2: jffs2_scan_inode_node(): CRC failed on node at 0x04a04ff4: Read 0xffffffff, calculated 0x1490a44b
[    4.766533] jffs2: Empty flash at 0x04a05038 ends at 0x04a05800
[    4.772578] jffs2: jffs2_scan_inode_node(): CRC failed on node at 0x04a09fec: Read 0xffffffff, calculated 0xd8c3bd7e
[    4.796662] jffs2: Empty flash at 0x04a0a068 ends at 0x04a0a800
[    4.802869] jffs2: jffs2_scan_inode_node(): CRC failed on node at 0x04a117d8: Read 0xffffffff, calculated 0xc4ef7290
[    4.822300] jffs2: Empty flash at 0x04a1181c ends at 0x04a12000
[    5.164996] jffs2: jffs2_scan_dirent_node(): Node CRC failed on node at 0x05320254: Read 0x6f471992, calculated 0x783c0dd1
[    5.497103] jffs2: Empty flash at 0x069d8070 ends at 0x069d8800
[    5.687186] VFS: Mounted root (jffs2 filesystem) on device 31:1.
[    5.698359] devtmpfs: mounted
[    5.701467] Freeing unused kernel memory: 200K (c0676000 - c06a8000)
[    7.456716] random: dd urandom read with 1 bits of entropy available
[    7.876315]
[    7.876315] bcm54xx_config_init
[    8.486305]
[    8.486305] bcm54xx_config_init
[   11.487156] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[   11.493245] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[   16.717573] jffs2: notice: (1095) check_node_data: wrong data CRC in data node at 0x053202b0: read 0xf790bd23, calculated 0x142225be.
[   28.067124] In axi fpga driver!
[   28.070200] request_mem_region OK!
[   28.073587] AXI fpga dev virtual address is 0xf0112000
[   28.078789] *base_vir_addr = 0x8c504
[   28.090075] In fpga mem driver!
[   28.093152] request_mem_region OK!
[   28.096768] fpga mem virtual address is 0xf3000000
[   29.005579]
[   29.005579] bcm54xx_config_init
[   29.645528]
[   29.645528] bcm54xx_config_init
[   32.646070] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[   32.652085] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[   94.553462] jffs2: warning: (1095) jffs2_do_read_inode_internal: Truncating ino #2089 to 46292 bytes failed because it only had 27394 bytes to start with!
[  410.307522] random: nonblocking pool is initialized
legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
Since you are using Awesome miner to monitor/control, try editing the Miner Offline rule to use 'Start Miner" Instead of "Restart Miner. I just started trying that and so far it seems to give the miner a kick in the pants without doing a full restart/warm boot.

Sometimes a miner shows offline in awesome and I managed to kick start them through putty: reboot -f -p
That works in many cases when miner shows offline in awesome and even when you cant browse the miner through the GUI.
How do you make this start command in Awesome you are talking about ?
Be on the Main tab, select Options > Rules. You get a menu with pre-defined tick boxes as well as an area below to write your own rules..

From the pre-defined list double click on Offline Detection to edit what it does. Same applies to Dead Device Detection -- you can edit how many chips report bad before choosing what to do about it.

Like I said, for Offline the default was restert which rebooted the entire miner. Changing to Start miner I think just restarts cgminer itself. There is prolly a description of what the API calls do in ck/Kanos github...

So far looking at the logged stats, since changing Offline Detection to just Notify and to Start Miner (vs Restart) none of my miners have rebooted since! Ja the Notifications are logged but looking at the performance loge for times involved show no hash rate lost and miner uptime reflects happy running as well.

With the 8 s9's I have and several s7's as well I'd see at least one per-day reboot due to offline timeout. Now - zero Cheesy
legendary
Activity: 922
Merit: 1003
It took me years to get a good power deal and now the gear has become very unreliable.
If s9s worked better I would have six or seven more. Instead I sold most off and I am down to three units.
I agree; S9's in general have been very problematic compared to the scores of S1's, S3's, S5's, and S7's I've purchased. A significant drop in quality overall, which is disappointing and frustrating to see. I've had to RMA a large percentage of S9 boards already, some of the replacements have failed as well, and still have out-of-warranty dead boards to deal with. I'm not purchasing additional S9's, even though I have capacity for them ... hoping that something more reliable will show up at some point.
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
One board on S9 (two month old) does not work anymore. It is still under warranty, but is it even worth it sending it to hong kong?
What is the cost to do that from US, approximately? Instructions are peculiar and I have no ability to photograph anything as the miner is in hosting. What did you guys use, UPS or FEDEX?
Philipma1957 here in forum has had good experience with BitmainWarranty.
In US it might be a good idea to deal with them.
www.bitmainwarranty.com

thanks. this is probably true re US repair, although typically you have to pay for it.
However, apart from sending cost, you are not supposed to pay for warranty repair in Hong Kong.
What if repair cost close to board cost when you do it in US? Then, it does not make sense.

I would appreciate if someone post re cost of sending a board from US to HK. Thanks.

About 110 via ups.

And you have to claim it to,be 44 usd or lower in value.

So 110 and if it is less lost or damaged you can only collect 44 bucks.

A boards value is around 450.

If you send to Colorado in a small usps flat rate it is 15 and you can insure it for 200 spend 18 total then spend 25 for return so 43 out of pocket and repair is 100 to 225.

So it can be a case of pick your ur poison.

Right now the solar array has 30-38 amps idle power due to my fear of using s9s.

It took me years to get a good power deal and now the gear has become very unreliable.
If s9s worked better I would have six or seven more. Instead I sold most off and I am down to three units.
sr. member
Activity: 387
Merit: 254
New firmware released today.  Not sure if it's the same as what came with Batch 16/17 or if newer (has the same date).  Description says "This package can make startup faster." fwiw

That is interesting how it works on all batches. anyone try it yet?

Installed and it did seem to start up quicker (< 2 minutes in my case).  Still has the oscillating fan speeds and no way to control.

Installed it on 1 of mine. I don't like the loss of fan control. My chip temp is now 15-20C higher than my others.

the temps are probably higher because the new firmware automatically overclocks the miner to the highest freq for each board. i much rather have each board at the same freq. one of my miners has a freq of 477 while another board in the same miner has a freq of over 600...that board is also hotter than the other 2. this will probably cause more failed boards than the old firmware did. afterall bitmain said "overclocking voids your warranty" because it puts the miner under more stress that wears it out faster...now it overclocks itself which will cause premature failures....not a good look bitmain...

has anyone tried the old firmware versions on b17 and 18?? im not sure what makes this batch any different. my 12th miners had 12th stickers placed over top of the 11.83th stickers and both stickers had the same serial number so im wondering if they are just saying that so people dont downgrade their firmware.

we're rolling it out on some 17s today and earlier problem miners.

keep us posted for sure because this new firmware sucks.

like the other guy said...the temps r probably high because of that auto fan stuff. if it doesnt ramp up the freq like it does with batch 17/18 then thats the only other reason really. idk y they change the fan profiles for the miner. u cant make these machines quiet. if they were worried about the sound they should have adopted the full size larger fan heatsink like they used before. tons of these shallow tiny heatsinks just blows. i would much rather lose some space where i run my miners and have larger heatsink vs this small compact miner that runs hot.

people abuse their miners alot though. im one of few that runs them properly (aka not in a barn or a shed in the dead of summer) so im surprised bitmain would release such a temp sensitive miner to the general public knowing how many run them. they could have released it but with a better cooling design.
legendary
Activity: 938
Merit: 1000
Since you are using Awesome miner to monitor/control, try editing the Miner Offline rule to use 'Start Miner" Instead of "Restart Miner. I just started trying that and so far it seems to give the miner a kick in the pants without doing a full restart/warm boot.

Sometimes a miner shows offline in awesome and I managed to kick start them through putty: reboot -f -p
That works in many cases when miner shows offline in awesome and even when you cant browse the miner through the GUI.
How do you make this start command in Awesome you are talking about ?
legendary
Activity: 938
Merit: 1000
I tried to roll out on some S9´s today, that did not hash at promised hash rate....... disaster struck.
Bitmain says its for all S9`s in the file name: Antminer-S9-all-201610180851-autofreq-user.tar

But some of my S9`s went mental and Chip temp (132-150 degree celcius) was showing up, just after a few min of mining. I reflashed the miners with old firmware to prevent burning the boards. Something is completely wrong with this firmware.

full member
Activity: 219
Merit: 100
Bitcoin Mining Hosting
New firmware released today.  Not sure if it's the same as what came with Batch 16/17 or if newer (has the same date).  Description says "This package can make startup faster." fwiw

That is interesting how it works on all batches. anyone try it yet?

Installed and it did seem to start up quicker (< 2 minutes in my case).  Still has the oscillating fan speeds and no way to control.

Installed it on 1 of mine. I don't like the loss of fan control. My chip temp is now 15-20C higher than my others.

the temps are probably higher because the new firmware automatically overclocks the miner to the highest freq for each board. i much rather have each board at the same freq. one of my miners has a freq of 477 while another board in the same miner has a freq of over 600...that board is also hotter than the other 2. this will probably cause more failed boards than the old firmware did. afterall bitmain said "overclocking voids your warranty" because it puts the miner under more stress that wears it out faster...now it overclocks itself which will cause premature failures....not a good look bitmain...

has anyone tried the old firmware versions on b17 and 18?? im not sure what makes this batch any different. my 12th miners had 12th stickers placed over top of the 11.83th stickers and both stickers had the same serial number so im wondering if they are just saying that so people dont downgrade their firmware.

we're rolling it out on some 17s today and earlier problem miners.

I actually flashed it on a B14. Frequency has stayed at 550 on all boards. Chip temps still much higher than other S9's due to fan speed.

can confirm, earlier batches are running hotter, but it could be they weren't reporting properly before. None of the early batches seem to change freq , 550s , 600s etc.
Jump to: