Bitmain Announces the Antminer R4 and APW5 Power Supply, Designed for Silence

[sarcheer]

Nice! Yah, this firmware is using the freq set in the pic from what I understand.

[VRobb]

What I've seen is that is separates the boards' clock speeds, so before both boards were running at the same speed (the fastest that both would be stable I'd guess), and now I see one board is running with a higher clock with the other basically the same as before.
Surprised it didn't do that originally. 

[Artemis3]

After updating to the newest FW my R4B2 went from 8 to 8.5TH/s and is running cooler.  So more hash for less operational cost, not too shabby...  

I just did mine and was going to write the same.
Indeed from 8th/s went up to 8.5th/s. Also its nice to have proper pcb+chip temp readings, seems much cooler now
Looking at the logs the system wants the FAN to run at 50ish percent, but nah, I'll leave it at full throttle because its so quiet anyway.
Max chip temperature went down from 110ish to 70, not bad (max i ever saw was 120...).

[DaveF]

So my last R4 lost a hash board.
Before I say screw it an sell it, can anyone see anything that looks obvious?

Log below.

Thanks,
Dave

Code:

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.0-xilinx-gb190cb0-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #57 SMP PREEMPT Fri Dec 9 14:49:22 CST 2016
[    0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Xilinx Zynq
[    0.000000] cma: CMA: reserved 128 MiB at 27800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 258048
[    0.000000] free_area_init_node: node 0, pgdat c0740a40, node_mem_map e6fd8000
[    0.000000]   Normal zone: 1520 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 194560 pages, LIFO batch:31
[    0.000000]   HighMem zone: 496 pages used for memmap
[    0.000000]   HighMem zone: 63488 pages, LIFO batch:15
[    0.000000] PERCPU: Embedded 8 pages/cpu @e6fc0000 s9088 r8192 d15488 u32768
[    0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 256528
[    0.000000] Kernel command line: noinitrd mem=1008M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 884148K/1032192K available (5032K kernel code, 283K rwdata, 1916K rodata, 204K init, 258K bss, 148044K reserved, 253952K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06d1374   (6949 kB)
[    0.000000]       .init : 0xc06d2000 - 0xc0705380   ( 205 kB)
[    0.000000]       .data : 0xc0706000 - 0xc074cf78   ( 284 kB)
[    0.000000]        .bss : 0xc074cf84 - 0xc078d9fc   ( 259 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] 	Dump stacks of tasks blocking RCU-preempt GP.
[    0.000000] 	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] ps7-slcr mapped to f0004000
[    0.000000] zynq_clock_init: clkc starts at f0004100
[    0.000000] Zynq clock init
[    0.000015] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[    0.000303] ps7-ttc #0 at f0006000, irq=43
[    0.000609] Console: colour dummy device 80x30
[    0.000647] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328)
[    0.040206] pid_max: default: 32768 minimum: 301
[    0.040428] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.040451] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.042582] CPU: Testing write buffer coherency: ok
[    0.042927] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.042987] Setting up static identity map for 0x4c4af8 - 0x4c4b50
[    0.043212] L310 cache controller enabled
[    0.043231] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[    0.121034] CPU1: Booted secondary processor
[    0.210226] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.210356] Brought up 2 CPUs
[    0.210375] SMP: Total of 2 processors activated.
[    0.210384] CPU: All CPU(s) started in SVC mode.
[    0.211034] devtmpfs: initialized
[    0.213455] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.214662] regulator-dummy: no parameters
[    0.222341] NET: Registered protocol family 16
[    0.224637] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.226906] cpuidle: using governor ladder
[    0.226919] cpuidle: using governor menu
[    0.234303] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.235808] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.235822] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.235934] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xf0080000
[    0.257355] bio: create slab <bio-0> at 0
[    0.258752] vgaarb: loaded
[    0.259448] SCSI subsystem initialized
[    0.260488] usbcore: registered new interface driver usbfs
[    0.260670] usbcore: registered new interface driver hub
[    0.260895] usbcore: registered new device driver usb
[    0.261444] media: Linux media interface: v0.10
[    0.261601] Linux video capture interface: v2.00
[    0.261841] pps_core: LinuxPPS API ver. 1 registered
[    0.261852] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.261981] PTP clock support registered
[    0.262334] EDAC MC: Ver: 3.0.0
[    0.263376] Advanced Linux Sound Architecture Driver Initialized.
[    0.266207] DMA-API: preallocated 4096 debug entries
[    0.266220] DMA-API: debugging enabled by kernel config
[    0.266302] Switched to clocksource arm_global_timer
[    0.287373] NET: Registered protocol family 2
[    0.288042] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.288138] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.288296] TCP: Hash tables configured (established 8192 bind 8192)
[    0.288356] TCP: reno registered
[    0.288375] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.288428] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.288686] NET: Registered protocol family 1
[    0.289043] RPC: Registered named UNIX socket transport module.
[    0.289055] RPC: Registered udp transport module.
[    0.289064] RPC: Registered tcp transport module.
[    0.289072] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.289085] PCI: CLS 0 bytes, default 64
[    0.289530] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.291530] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.292910] bounce pool size: 64 pages
[    0.293810] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.294011] msgmni has been set to 1486
[    0.294794] io scheduler noop registered
[    0.294807] io scheduler deadline registered
[    0.294849] io scheduler cfq registered (default)
[    0.304066] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.304086] dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.426928] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    0.999758] console [ttyPS0] enabled
[    1.004027] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to f0068000
[    1.011662] [drm] Initialized drm 1.1.0 20060810
[    1.028692] brd: module loaded
[    1.038058] loop: module loaded
[    1.047642] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.053391] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.061537] libphy: XEMACPS mii bus: probed
[    1.065909] ------------- phy_id = 0x3625e62
[    1.070894] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.079502] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.086130] ehci-pci: EHCI PCI platform driver
[    1.093363] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[    1.100198] usbcore: registered new interface driver usb-storage
[    1.107080] mousedev: PS/2 mouse device common for all mice
[    1.113170] i2c /dev entries driver
[    1.120118] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[    1.125603] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.131513] Xilinx Zynq CpuIdle Driver started
[    1.136364] sdhci: Secure Digital Host Controller Interface driver
[    1.142456] sdhci: Copyright(c) Pierre Ossman
[    1.146907] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.153640] mmc0: no vqmmc regulator found
[    1.157680] mmc0: no vmmc regulator found
[    1.196328] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.205013] usbcore: registered new interface driver usbhid
[    1.210533] usbhid: USB HID core driver
[    1.215231] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.221521] nand: Micron MT29F2G08ABAEAWP
[    1.225492] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.231452] Bad block table found at page 131008, version 0x01
[    1.237688] Bad block table found at page 130944, version 0x01
[    1.243738] 3 ofpart partitions found on MTD device pl353-nand
[    1.249507] Creating 3 MTD partitions on "pl353-nand":
[    1.254615] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.262641] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.269961] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[    1.278907] TCP: cubic registered
[    1.282138] NET: Registered protocol family 17
[    1.286858] Registering SWP/SWPB emulation handler
[    1.292796] regulator-dummy: disabling
[    1.297196] UBI: attaching mtd1 to ubi0
[    1.822727] UBI: scanning is finished
[    1.834334] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[    1.841416] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.848179] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.854843] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.861721] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[    1.867701] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.874809] UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 249466695
[    1.883765] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[    1.892981] UBI: background thread "ubi_bgt0d" started, PID 1080
[    1.892986] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.896978] ALSA device list:
[    1.896981]   No soundcards found.
[    1.913327] UBIFS: background thread "ubifs_bgt0_0" started, PID 1082
[    1.942377] UBIFS: recovery needed
[    2.039137] UBIFS: recovery completed
[    2.042806] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    2.048752] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.057857] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    2.067745] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.072774] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 8EF2DA3A-9E21-4655-9C5A-ADF1C479EA7C, small LPT model
[    2.084070] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    2.090806] devtmpfs: mounted
[    2.093910] Freeing unused kernel memory: 204K (c06d2000 - c0705000)
[    2.932293] random: dd urandom read with 0 bits of entropy available
[    3.326340] 
[    3.326340] bcm54xx_config_init
[    3.936334] 
[    3.936334] bcm54xx_config_init
[    7.937170] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[    7.943271] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[   27.883382] In axi fpga driver!
[   27.886475] request_mem_region OK!
[   27.889844] AXI fpga dev virtual address is 0xf01fe000
[   27.894949] *base_vir_addr = 0x8c510
[   27.910225] In fpga mem driver!
[   27.913314] request_mem_region OK!
[   27.916943] fpga mem virtual address is 0xf3000000
[   28.735739] 
[   28.735739] bcm54xx_config_init
[   29.365668] 
[   29.365668] bcm54xx_config_init
[   33.366123] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[   33.372230] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[  262.332395] random: nonblocking pool is initialized
This is XILINX board. Totalram:       1039794176
Detect 1GB control board of XILINX
DETECT HW version=0008c510
Miner Type = R4
AsicType = 1387
real AsicNum = 63
get PLUG ON=0x00000060
Find hashboard on Chain[5]
Find hashboard on Chain[6]
set_reset_allhashboard = 0x0000ffff
Check chain[5] PIC fw version=0x03
Check chain[6] PIC fw version=0x03
has freq in PIC, will disable freq setting.
chain[5] has freq in PIC and will jump over...
Chain[5] has core num in PIC
Check chain[5] PIC fw version=0x03
has freq in PIC, will disable freq setting.
chain[6] has freq in PIC and will jump over...
Chain[6] has core num in PIC
Check chain[6] PIC fw version=0x03
get PIC voltage=6 on chain[5], value=940
get PIC voltage=57 on chain[6], value=910
set_reset_allhashboard = 0x00000000
chain[5] temp offset record: 3,-78,4,-83,0,0,0,0
chain[6] temp offset record: 3,-14,4,-8,0,0,0,0
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
CRC error counter=0
set command mode to VIL

--- check asic number
set_baud=0
The min freq=700
set real timeout 52, need sleep=379392
After TEST CRC error counter=0
search freq for 1 times, completed chain = 2, total chain num = 2 
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
restart Miner chance num=2
waiting for receive_func to exit!
waiting for pic heart to exit!
Start bmminer ...
Detect 1GB control board of XILINX
Miner Type = R4
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x0000ffff
Chain[J6] has backup chain_voltage=910
Chain[J6] test patten OK temp=59
Check chain[5] PIC fw version=0x03
Chain[J7] has backup chain_voltage=910
Chain[J7] test patten OK temp=63
Check chain[6] PIC fw version=0x03
Chain[J6] orignal chain_voltage_pic=6 value=940
Chain[J6] will use backup chain_voltage_pic=910 [57]
Chain[J6] get working chain_voltage_pic=57
Chain[J7] orignal chain_voltage_pic=57 value=910
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
Chain[J6] has 0 asic
set_reset_hashboard = 0x00000020
set_reset_hashboard = 0x00000000
retry Chain[J6] has 0 asic
set_reset_hashboard = 0x00000020
set_reset_hashboard = 0x00000000
retry Chain[J6] has 0 asic
set_reset_hashboard = 0x00000020
set_reset_hashboard = 0x00000000
retry Chain[J6] has 0 asic
set_reset_hashboard = 0x00000020
set_reset_hashboard = 0x00000000
retry Chain[J6] has 0 asic
set_reset_hashboard = 0x00000020
set_reset_hashboard = 0x00000000
retry Chain[J6] has 0 asic
set_reset_hashboard = 0x00000020
set_reset_hashboard = 0x00000000
retry Chain[J6] has 0 asic
Chain[J7] has 63 asic
Chain[J7] has core num in PIC
miner total rate=3663GH/s fixed rate=3500GH/s
read PIC voltage=940 on chain[6]
Chain:6 chipnum=63
Chain[J7] voltage added=0.4V
Chain:6 temp offset=-3
Chain:6 base freq=441
Asic[ 0]:468 
Asic[ 1]:516 Asic[ 2]:537 Asic[ 3]:468 Asic[ 4]:516 Asic[ 5]:537 Asic[ 6]:470 Asic[ 7]:445 Asic[ 8]:537 
Asic[ 9]:475 Asic[10]:516 Asic[11]:537 Asic[12]:475 Asic[13]:516 Asic[14]:537 Asic[15]:475 Asic[16]:516 
Asic[17]:537 Asic[18]:475 Asic[19]:525 Asic[20]:537 Asic[21]:475 Asic[22]:525 Asic[23]:516 Asic[24]:475 
Asic[25]:529 Asic[26]:537 Asic[27]:441 Asic[28]:529 Asic[29]:537 Asic[30]:491 Asic[31]:518 Asic[32]:531 
Asic[33]:491 Asic[34]:529 Asic[35]:470 Asic[36]:491 Asic[37]:531 Asic[38]:537 Asic[39]:491 Asic[40]:537 
Asic[41]:495 Asic[42]:495 Asic[43]:537 Asic[44]:525 Asic[45]:506 Asic[46]:537 Asic[47]:537 Asic[48]:516 
Asic[49]:468 Asic[50]:537 Asic[51]:516 Asic[52]:537 Asic[53]:468 Asic[54]:516 Asic[55]:537 Asic[56]:537 
Asic[57]:516 Asic[58]:518 Asic[59]:506 Asic[60]:516 Asic[61]:483 Asic[62]:537 
Chain:6 max freq=537
Chain:6 min freq=441


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

max freq = 537
set baud=2
Chain[J7] PIC temp offset=3,-14,4,-8,0,0,0,0
Chain[J7] chip[8] use PIC middle temp offset=-14 typeID=55
New offset Chain[6] chip[8] local:14 remote:16 offset:27 
Chain[J7] chip[8] get middle temp offset=27 typeID=55
Chain[J7] chip[12] use PIC middle temp offset=-8 typeID=55
New offset Chain[6] chip[12] local:14 remote:17 offset:26 
Chain[J7] chip[12] get middle temp offset=26 typeID=55
Chain[J7] set working voltage=910 [57]
do heat board 8xPatten for 1 times
Check voltage total rate=3663
get PIC voltage=910 [57] on chain[6], check: must be < 910
start send works on chain[6]
get send work num :57456 on Chain[6]
wait recv nonce on chain[6]
get nonces on chain[6]
require nonce number:912
require validnonce number:57456
asic[00]=912	asic[01]=912	asic[02]=912	asic[03]=912	asic[04]=912	asic[05]=912	asic[06]=912	asic[07]=912	
asic[08]=912	asic[09]=912	asic[10]=912	asic[11]=912	asic[12]=912	asic[13]=912	asic[14]=912	asic[15]=912	
asic[16]=912	asic[17]=912	asic[18]=912	asic[19]=912	asic[20]=912	asic[21]=912	asic[22]=912	asic[23]=912	
asic[24]=912	asic[25]=912	asic[26]=912	asic[27]=912	asic[28]=912	asic[29]=912	asic[30]=912	asic[31]=912	
asic[32]=912	asic[33]=912	asic[34]=912	asic[35]=912	asic[36]=912	asic[37]=912	asic[38]=912	asic[39]=912	
asic[40]=912	asic[41]=912	asic[42]=912	asic[43]=912	asic[44]=912	asic[45]=912	asic[46]=912	asic[47]=912	
asic[48]=912	asic[49]=912	asic[50]=912	asic[51]=912	asic[52]=912	asic[53]=912	asic[54]=912	asic[55]=912	
asic[56]=912	asic[57]=912	asic[58]=912	asic[59]=912	asic[60]=912	asic[61]=912	asic[62]=912	


Below ASIC's core didn't receive all the nonce, they should receive 8 nonce each!



freq[00]=468	freq[01]=516	freq[02]=537	freq[03]=468	freq[04]=516	freq[05]=537	freq[06]=470	freq[07]=445	
freq[08]=537	freq[09]=475	freq[10]=516	freq[11]=537	freq[12]=475	freq[13]=516	freq[14]=537	freq[15]=475	
freq[16]=516	freq[17]=537	freq[18]=475	freq[19]=525	freq[20]=537	freq[21]=475	freq[22]=525	freq[23]=516	
freq[24]=475	freq[25]=529	freq[26]=537	freq[27]=441	freq[28]=529	freq[29]=537	freq[30]=491	freq[31]=518	
freq[32]=531	freq[33]=491	freq[34]=529	freq[35]=470	freq[36]=491	freq[37]=531	freq[38]=537	freq[39]=491	
freq[40]=537	freq[41]=495	freq[42]=495	freq[43]=537	freq[44]=525	freq[45]=506	freq[46]=537	freq[47]=537	
freq[48]=516	freq[49]=468	freq[50]=537	freq[51]=516	freq[52]=537	freq[53]=468	freq[54]=516	freq[55]=537	
freq[56]=537	freq[57]=516	freq[58]=518	freq[59]=506	freq[60]=516	freq[61]=483	freq[62]=537	

total valid nonce number:57456
total send work number:57456
require valid nonce number:57456
repeated_nonce_num:0
err_nonce_num:31091
last_nonce_num:32047
chain[6]: All chip cores are opened OK!
Test Patten on chain[6]: OK!
setStartTimePoint total_tv_start_sys=183 total_tv_end_sys=184
restartNum = 2 , auto-reinit enabled...
do read_temp_func once...
do check_asic_reg 0x08

get RT hashrate from Chain[6]: (asic index start from 1-63)
Asic[01]=53.9210 Asic[02]=57.2100 Asic[03]=65.2800 Asic[04]=49.9120 Asic[05]=56.3370 Asic[06]=58.4850 Asic[07]=53.5190 Asic[08]=49.0900 
Asic[09]=64.8270 Asic[10]=53.3850 Asic[11]=59.9610 Asic[12]=57.1430 Asic[13]=49.9790 Asic[14]=57.7300 Asic[15]=62.8810 Asic[16]=55.7500 
Asic[17]=60.2300 Asic[18]=56.7570 Asic[19]=51.2200 Asic[20]=53.2500 Asic[21]=61.7560 Asic[22]=55.2800 Asic[23]=61.2700 Asic[24]=57.5790 
Asic[25]=54.0220 Asic[26]=61.2200 Asic[27]=61.8570 Asic[28]=49.4590 Asic[29]=58.6690 Asic[30]=62.2260 Asic[31]=55.1130 Asic[32]=57.2940 
Asic[33]=58.3170 Asic[34]=53.8880 Asic[35]=57.7300 Asic[36]=52.5960 Asic[37]=56.8410 Asic[38]=58.5520 Asic[39]=59.4080 Asic[40]=56.0020 
Asic[41]=59.5080 Asic[42]=57.2430 Asic[43]=60.1790 Asic[44]=57.4780 Asic[45]=55.5490 Asic[46]=61.8910 Asic[47]=56.3370 Asic[48]=55.5990 
Asic[49]=57.9310 Asic[50]=52.2940 Asic[51]=55.3310 Asic[52]=60.5990 Asic[53]=57.7470 Asic[54]=54.5420 Asic[55]=60.1290 Asic[56]=62.9640 
Asic[57]=62.8300 Asic[58]=58.2500 Asic[59]=57.4110 Asic[60]=56.3370 Asic[61]=58.3000 Asic[62]=59.4410 Asic[63]=62.2260 
Check Chain[J7] ASIC RT error: (asic index start from 1-63)
Done check_asic_reg
do read temp on Chain[6]
Chain[6] Chip[3] TempTypeID=55 middle offset=27
Chain[6] Chip[3] local Temp=33
Chain[6] Chip[3] middle Temp=52
Chain[6] Chip[4] TempTypeID=55 middle offset=26
Chain[6] Chip[4] local Temp=46
Chain[6] Chip[4] middle Temp=60
Done read temp on Chain[6]
set FAN speed according to: temp_highest=46 temp_top1[PWM_T]=46 temp_change=-1
keep PWM=52
FAN PWM: 52
read_temp_func Done!
CRC error counter=1

[VRobb]

Are you running the latest, ASICboost enabled firmware?  My R4 would drop a board often enough, and rebooting usually got it back up and running, but after updating the firmware to the latest it runs better and hasn't dropped a board yet.
HTH

[DaveF]

Are you running the latest, ASICboost enabled firmware?  My R4 would drop a board often enough, and rebooting usually got it back up and running, but after updating the firmware to the latest it runs better and hasn't dropped a board yet.
HTH

It was on the ASICBoost FW, then I rolled it back to see if that helped (it didn't). Not sure if I put it back on or not.

-Dave

[HagssFIN]

I have few very basic ideas..  

Is it the same result if you change the controller board port used for that hash board?

Does removing the other hash board data cable + power temporarily and booting the miner with the one hash board make any difference?

Do you get the same result if you swap controller board ports between the two hash boards?

[DaveF]

I have few very basic ideas.. 

Is it the same result if you change the controller board port used for that hash board?

Does removing the other hash board data cable + power temporarily and booting the miner with the one hash board make any difference?

Do you get the same result if you swap controller board ports between the two hash boards?

Yes. (well the chain #s change)
No.
Yes.

I'm going to put it on the tech bench next week for a deeper look. But it's probably not worth putting in that much time.
-Dave

[sarcheer]

I have few very basic ideas.. 

Is it the same result if you change the controller board port used for that hash board?

Does removing the other hash board data cable + power temporarily and booting the miner with the one hash board make any difference?

Do you get the same result if you swap controller board ports between the two hash boards?

Yes. (well the chain #s change)
No.
Yes.

I'm going to put it on the tech bench next week for a deeper look. But it's probably not worth putting in that much time.
-Dave

Have you tried to swapping the cables between boards to see if the cable has failed?

[DaveF]

I have few very basic ideas..  

Is it the same result if you change the controller board port used for that hash board?

Does removing the other hash board data cable + power temporarily and booting the miner with the one hash board make any difference?

Do you get the same result if you swap controller board ports between the two hash boards?

Yes. (well the chain #s change)
No.
Yes.

I'm going to put it on the tech bench next week for a deeper look. But it's probably not worth putting in that much time.
-Dave

Have you tried to swapping the cables between boards to see if the cable has failed?

I *think* I did.
Where it is now is not easy to work on, so I did a bunch of tests (swapping ports, swapping power, etc) I think I did a full cable swap but I am not 100% sure, which is why I figure I'll pull it to the tech bench next week when I have time & space to work.
Thanks,
Dave

[aswithin]

Are you running the latest, ASICboost enabled firmware?  My R4 would drop a board often enough, and rebooting usually got it back up and running, but after updating the firmware to the latest it runs better and hasn't dropped a board yet.
HTH

Is this firmware Antminer-R4-xilinx-201811121649-autofreq-user-UBI-NF.tar.gz the one with ASICboost enabled, or is it another one?

[sarcheer]

Are you running the latest, ASICboost enabled firmware?  My R4 would drop a board often enough, and rebooting usually got it back up and running, but after updating the firmware to the latest it runs better and hasn't dropped a board yet.
HTH

Is this firmware Antminer-R4-xilinx-201811121649-autofreq-user-UBI-NF.tar.gz the one with ASICboost enabled, or is it another one?

That is the ASICBoost FW from Bitmain. However, if you are not on the other listed firmware:

Antminer-R4-all-201704280718-autofreq-user-Update2UBI-NF.tar.gz

The update will not work. The update listed above changes the file system to UBI or something like that which is necessary for the AB firmware to be compatible as it uses a UBI filesystem but does not contain the necessary files to changeover the existing filesystem.

[aswithin]

That is the ASICBoost FW from Bitmain. However, if you are not on the other listed firmware:

Antminer-R4-all-201704280718-autofreq-user-Update2UBI-NF.tar.gz

The update will not work. The update listed above changes the file system to UBI or something like that which is necessary for the AB firmware to be compatible as it uses a UBI filesystem but does not contain the necessary files to changeover the existing filesystem.

So if I have a stock R4, the steps would be to first install the Antminer-R4-all-201704280718-autofreq-user-Update2UBI-NF.tar.gz fw, then the Antminer-R4-xilinx-201811121649-autofreq-user-UBI-NF.tar.gz fw. Is that correct?

[sarcheer]

That is the ASICBoost FW from Bitmain. However, if you are not on the other listed firmware:

Antminer-R4-all-201704280718-autofreq-user-Update2UBI-NF.tar.gz

The update will not work. The update listed above changes the file system to UBI or something like that which is necessary for the AB firmware to be compatible as it uses a UBI filesystem but does not contain the necessary files to changeover the existing filesystem.

So if I have a stock R4, the steps would be to first install the Antminer-R4-all-201704280718-autofreq-user-Update2UBI-NF.tar.gz fw, then the Antminer-R4-xilinx-201811121649-autofreq-user-UBI-NF.tar.gz fw. Is that correct?

Yes, that would be correct! However, be aware that you will the lose the ability from the stock firmware to set your own fan speeds and freq when you upgrade to the UBI filesystem.

[Artemis3]

That is the ASICBoost FW from Bitmain. However, if you are not on the other listed firmware:

Antminer-R4-all-201704280718-autofreq-user-Update2UBI-NF.tar.gz

The update will not work. The update listed above changes the file system to UBI or something like that which is necessary for the AB firmware to be compatible as it uses a UBI filesystem but does not contain the necessary files to changeover the existing filesystem.

So if I have a stock R4, the steps would be to first install the Antminer-R4-all-201704280718-autofreq-user-Update2UBI-NF.tar.gz fw, then the Antminer-R4-xilinx-201811121649-autofreq-user-UBI-NF.tar.gz fw. Is that correct?

This is exactly what i did to mine, which had a firmware from 2016. First to the Update2UBI one, then the latest. The fan of the R4 is ridiculously silent at 100% (mine does 3240rpm, some models only do 3000rpm) and in all its life has had the fourth wire disconnected, I don't think i ever saw the option to force fan speeds or chip freqs like i remember seeing in S9s so the fan have always been running at 100%, and the chips on autofreq (600ish).

After the update the hashrate went from 8 to 8.5, and the temperatures went down. Also it reports both PCB and Chip temperatures far better than the weird two values the 2016 firmware used to give...

[VRobb]

Are you running the latest, ASICboost enabled firmware?  My R4 would drop a board often enough, and rebooting usually got it back up and running, but after updating the firmware to the latest it runs better and hasn't dropped a board yet.
HTH

Is this firmware Antminer-R4-xilinx-201811121649-autofreq-user-UBI-NF.tar.gz the one with ASICboost enabled, or is it another one?

That's the one I used when I updated the fw. Been a happy camper since.

[Pyrojason]

Any suggestions for a board with resistance to firmware updates? It's back a few notches - several releases behind but it just returns ' Invalid Firmware '  every time with any of the official Bitmain firmware updates. I was wondering if anyone else has come across a similar issue with the R4. Thanks in advance for any thoughts.

[sarcheer]

Any suggestions for a board with resistance to firmware updates? It's back a few notches - several releases behind but it just returns ' Invalid Firmware '  every time with any of the official Bitmain firmware updates. I was wondering if anyone else has come across a similar issue with the R4. Thanks in advance for any thoughts.

Just to confirm, you’ve tried the Antminer-R4-all-201704280718-autofreq-user-Update2UBI-NF.tar.gz fw, correct?

[zachj00]

Any suggestions for a board with resistance to firmware updates? It's back a few notches - several releases behind but it just returns ' Invalid Firmware '  every time with any of the official Bitmain firmware updates. I was wondering if anyone else has come across a similar issue with the R4. Thanks in advance for any thoughts.

I had the same issue with mine. Im just running the old firmware where you can pick your frequency (550-650).

[Artemis3]

Any suggestions for a board with resistance to firmware updates? It's back a few notches - several releases behind but it just returns ' Invalid Firmware '  every time with any of the official Bitmain firmware updates. I was wondering if anyone else has come across a similar issue with the R4. Thanks in advance for any thoughts.

I had the same issue with mine. Im just running the old firmware where you can pick your frequency (550-650).

Strange. Do you know what batch is yours?

If you have the 2016 firmware, You should be able to upgrade to 2017:

• Antminer-R4-all-201704280718-autofreq-user-Update2UBI-NF.tar.gz first.

If you have the 2017 firmware, then, and only then, you can upgrade to 2018:

• Antminer-R4-xilinx-201811121649-autofreq-user-UBI-NF.tar.gz second.