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](https://bitcointalk.org/Smileys/default/cheesy.gif)
|
|
|
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.
|
|
|
I wonder how much it would freak out if you used an external PWM fan driver and piped through the tach line so it would still see the fan spinning?
Yup, I am thinking of something like that. Right now I have noticed that the tuning process can complete with only one fan online, while the other is unplugged. But bmminer stops immediately after tuning completes, and puts out an error message, when it detects a single fan. Since other folks have mentioned the fan speeds change from time to time, my thought is that the firmware might be trying to maintain a specific 'best' chip temp to keep it stable. IF so...
|
|
|
I will say there was some delay getting me updated datasheets because the manufacture batch had been changed from the sample batch. I don't really know what the changes were but presumably they were improvements. So if Bitfury took an extra couple months stepping things up a notch I'm pretty sure that's a good thing.
No doubt. And since BitFury has their own massive private perfect test site, I'd think all the various iterations of the chips that they got from TSMC got a pretty decent amount of testing en-mass to work out the wrinkles ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
|
|
<snip>
i replaced the psu to another one used on B600 and they both work correctly now! i hope this issue wouldn't return
Cool. Query: what PSU's are you using? I've pretty much have mostly used Bitmains 1,600W ones and some are getting very long in the tooth... At least one that was powering a s9 b3 had to be swapped out with a bit newer one (previously used on a s7). Miner seems more stable now although even at worst dropouts were maybe 1 every5-6 days.
|
|
|
As far as Bitfury goes, I'm not really sure what (from the little I know) I'm officially authorised to say or not. Pretty much all I will say is they got me samples and datasheets and I'm already started working on new stuff. I figure that PR can't possibly hurt them within the community, because it's about the first real effort any major manufacturer has done proactively to help the community in about a year. I agree 100% esp. about the PR. Truth be told, I'd leave current information to what you've released so far. Too many unknowns lie ahead for now Ja for whatever reason(s) BitFury massively missed their mark on matching chip delivery with Bitmain but OTOH that has also given them time to see what problems Bitmain have with the 16nm node and then apply that information to BitFury's chip. Since I believe historically BitFury chips were mainly used for their own let-us-build-you-a Farm sales/projects they were the only ones really hurt by the delay. It will be interesting to see how the chips work in the Real World.
|
|
|
BW LK-1402 Compac Prototype x 3 (minimum bid 0.08BTC) I assume the price is for 1 of the 3 available right? I'll start the bidding for 1 of them @ 0.1 BTC
|
|
|
I was thinking more of maybe reusing the buck inductors from the old miners more than anything. That is assuming they can the deliver the needed currents of course. Fairly easy to remove with near-zero chance of damage.
Und ja, I'm one of those who these days would prefer buying pre-built. I did 2 of the s1 > s3 upgrades and it was a surprising PITA... Mainly removing the old heatsink compound and re-pasting with new. Not mention having to wear armored gloves when doing it 'cause damn those fins are sharp! For your production I highly suggest making a frame/jig to hold the heatsinks for cleaning/re-pasting...These days, it's just not worth my time/effort/blood and I am happy to pay for someone else to do it.
|
|
|
If it is by the AC power inlet on the PSU I believe it means the PSU has a fault. Been a long time since I've ran my s4's so could be wrong...
|
|
|
i went to boot loop now every 20 minutes and before the machine start it restart by self
As others said - contact Bitmain to start the RMA process. For now -- and document all of this with screen shots --, At the bad hashboard, swap the data cable with a hashboard next to it. Restart the miner and take screen shot. Did the problem chain move? If it did the hashboard is bad. If it did NOT then either the cable or controller is bad. Odds are it's the board. Once the problem is identified I'd disconnect that 1 board/cable so the remaining 2 can work properly. DO NOT BREAK THE WARRANTY SEAL UNTIL BITMAIN SAYS YOU CAN!**TIP** unplugging the data cable can be -- difficult. You need to squeeze the long tab very firmly to disengage the hooks, then rock the connector back and forth as you pull.
|
|
|
What software is this?
If you are referring to the monitor software -- it is Awesome Miner from Awesomeminer.com. I also use it and gotta say - it's great and well worth the 1-time cost when controlling >4 miners. 4 or less is free! ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif)
|
|
|
Faboo! Glad to see that at least BitFury has started to open the door for 3rd party miners using their chip. In 1 respect it suggests that the chip should be at least reasonably stable. a cgminer driver for a 14nm Compac I won't be able to mass-produce because the chip supplier has decided not to sell to third parties.
I assume you are talking about BW's chip. In a way it doesn't surprise me that BW is keeping it to themselves or at best sharing with a very few select mega pharms. Given the problems that Bitmain has with their 16nm chips I'll bet ya BTC to beans that the 14nm chips are even more temperamental. At least this way BW gets to eat their own dog food -- and keep any issues the chips have out of the Press. ayout work has already been started on a "pod" miner that I would like to see hit 700GH, and the same framework can extend to S1 refit boards that, I'm just spitballing here, could see 4-6TH per pair depending on the chip specs and final configuration. ![Cool](https://bitcointalk.org/Smileys/default/cool.gif) I assume you still have that pile of s1's I set out to pasture with ya? Makes for a nice stable supply of cores to use. Any of the VR parts to be used from them or just the frame & heatsinks?
|
|
|
What does the HW mean, on one chip it seems higher than the others??
HW means Hardware error. As to what it can be --- many possibilities. Best to just Google "bitcoin HW error"
|
|
|
Looking through the Kernel Log raises some questions for me. For one, just how granular is the Auto-tuning that Bitmain introduced? The end of the log shows many new things... read PIC voltage=870 on chain[6] Chain:6 chipnum=63 Chain[J7] voltage added=0.1V OK: Chain[J7] is for this machine! [minerMAC: 00:13:f0:a4:b2:1b] Chain:6 temp offset=-70 Chain:6 base freq=568 Asic[ 0]:600 Asic[ 1]:650 Asic[ 2]:650 Asic[ 3]:618 Asic[ 4]:650 Asic[ 5]:650 Asic[ 6]:625 Asic[ 7]:650 Asic[ 8]:650 Asic[ 9]:650 Asic[10]:650 Asic[11]:650 Asic[12]:587 Asic[13]:650 Asic[14]:650 Asic[15]:650 Asic[16]:650 Asic[17]:575 Asic[18]:650 Asic[19]:568 Asic[20]:650 Asic[21]:650 Asic[22]:637 Asic[23]:650 Asic[24]:650 Asic[25]:650 Asic[26]:618 Asic[27]:650 Asic[28]:650 Asic[29]:637 Asic[30]:650 Asic[31]:650 Asic[32]:650 Asic[33]:650 Asic[34]:650 Asic[35]:625 Asic[36]:650 Asic[37]:631 Asic[38]:650 Asic[39]:643 Asic[40]:650 Asic[41]:650 Asic[42]:650 Asic[43]:650 Asic[44]:650 Asic[45]:650 Asic[46]:650 Asic[47]:643 Asic[48]:618 Asic[49]:650 Asic[50]:650 Asic[51]:650 Asic[52]:631 Asic[53]:650 Asic[54]:650 Asic[55]:650 Asic[56]:650 Asic[57]:650 Asic[58]:568 Asic[59]:650 Asic[60]:568 Asic[61]:650 Asic[62]:650 Chain:6 max freq=650 Chain:6 min freq=568
read PIC voltage=870 on chain[7] Chain:7 chipnum=63 Chain[J8] voltage added=0.1V OK: Chain[J8] is for this machine! [minerMAC: 00:13:f0:a4:b2:1b] Chain:7 temp offset=-70 Chain:7 base freq=537 Asic[ 0]:575 Asic[ 1]:656 Asic[ 2]:625 Asic[ 3]:575 Asic[ 4]:656 Asic[ 5]:656 Asic[ 6]:575 Asic[ 7]:656 Asic[ 8]:656 Asic[ 9]:581 Asic[10]:656 Asic[11]:656 Asic[12]:593 Asic[13]:656 Asic[14]:656 Asic[15]:656 Asic[16]:656 Asic[17]:650 Asic[18]:656 Asic[19]:650 Asic[20]:656 Asic[21]:656 Asic[22]:656 Asic[23]:537 Asic[24]:656 Asic[25]:656 Asic[26]:581 Asic[27]:656 Asic[28]:656 Asic[29]:650 Asic[30]:656 Asic[31]:550 Asic[32]:656 Asic[33]:631 Asic[34]:656 Asic[35]:656 Asic[36]:656 Asic[37]:537 Asic[38]:656 Asic[39]:656 Asic[40]:643 Asic[41]:656 Asic[42]:656 Asic[43]:643 Asic[44]:562 Asic[45]:656 Asic[46]:656 Asic[47]:650 Asic[48]:656 Asic[49]:656 Asic[50]:656 Asic[51]:656 Asic[52]:568 Asic[53]:656 Asic[54]:631 Asic[55]:625 Asic[56]:656 Asic[57]:656 Asic[58]:556 Asic[59]:656 Asic[60]:575 Asic[61]:656 Asic[62]:656 Chain:7 max freq=656 Chain:7 min freq=537
Along with the ASIC strings on the board running different frequencies, the gods forbid, is EACH ASIC's speed different as well?? Sure looks like it to me otherwise what's the point of recording per-chip speeds? Is it even possible to do that (different speed per-ASIC)? I'd think that it would raise hell with timing the data xfrs... If this is the case then the boards reported speed is the average of all speeds being used on the board.
|
|
|
@ patrike Just got a s9 batch-17 and... Bitmain has changed the firmware, is now BMminer v2.0. I will post in detail tomorrow but for a summary of changes: - They have changed the hash board channels and therefore die temp reporting channels. Now using channels 6, 7, and 8. Might need to come up with a routine to scan the die temp channels and only use ones reporting something...
- Looks like changing the frequency may be gone. In the Bitmain GUI that choice is gone. On startup, the firmware goes through several checks per-board and sets the best freq and possibly Vcore as well. When all is done, the boards report different frequencies.
Looking at the Kernel Log it shows several lists of freq and voltage it tries for each board. A note at the beginning of each list says that freq is now stored in the PIC. Now does that mean that a warm boot bypasses the testing -- dunna know but hope so. I'll post the Kernel Log tomorrow. Also fan speed no longer has a setting on the BMminer GUI. Log says is set as needed starting at 40% Oh, the fans are on different channels as well. Think fans are now reported in positions 6 an 8. I'll verify tomorrow. edit: fans in positions 3 and 6. Due to the time it takes for the new rebooting process -- around 4 min -- better set dead miner/offline/etc to wait at least that 4 maybe even 5 min before trying to issue another reboot call to the miner... Other than that, everything else works fine inc the Web access and info to it. Thanks for the update. Could you please send me an API report for one of these new miners? Then I can compare it in detail with previous batches. Many thanks! The miner is in my farm at work so will have to send the API report on Monday. I do have the Kernel log posted https://bitcointalk.org/index.php?topic=1645898.msg16564008#msg16564008and at the end of the log it shows many things I never seen reported. Thinks like range of freq's per-string and even best speeds per chip.
|
|
|
The Kernel Log from s9 b17 after finishing its's boot checks: [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 3.14.0-xilinx-gf387dab-dirty (lzq@armdev01) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #38 SMP PREEMPT Fri Jun 17 20:02:51 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 c06e4600, 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=/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.000605] Console: colour dummy device 80x30 [ 0.000641] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328) [ 0.040204] 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.042525] CPU: Testing write buffer coherency: ok [ 0.042869] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.042929] Setting up static identity map for 0x482448 - 0x4824a0 [ 0.043144] L310 cache controller enabled [ 0.043165] 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.210355] Brought up 2 CPUs [ 0.210374] SMP: Total of 2 processors activated. [ 0.210382] CPU: All CPU(s) started in SVC mode. [ 0.211039] devtmpfs: initialized [ 0.213416] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 0.214628] regulator-dummy: no parameters [ 0.221873] NET: Registered protocol family 16 [ 0.224089] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.226379] cpuidle: using governor ladder [ 0.226392] cpuidle: using governor menu [ 0.233760] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered [ 0.235261] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. [ 0.235274] hw-breakpoint: maximum watchpoint size is 4 bytes. [ 0.235380] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xf0080000 [ 0.256941] bio: create slab <bio-0> at 0 [ 0.258373] vgaarb: loaded [ 0.259073] SCSI subsystem initialized [ 0.259949] usbcore: registered new interface driver usbfs [ 0.260121] usbcore: registered new interface driver hub [ 0.260496] usbcore: registered new device driver usb [ 0.261023] media: Linux media interface: v0.10 [ 0.261213] Linux video capture interface: v2.00 [ 0.261453] pps_core: LinuxPPS API ver. 1 registered [ 0.261465] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.261587] PTP clock support registered [ 0.261959] EDAC MC: Ver: 3.0.0 [ 0.263013] Advanced Linux Sound Architecture Driver Initialized. [ 0.265839] DMA-API: preallocated 4096 debug entries [ 0.265854] DMA-API: debugging enabled by kernel config [ 0.265934] Switched to clocksource arm_global_timer [ 0.286919] NET: Registered protocol family 2 [ 0.287557] TCP established hash table entries: 8192 (order: 3, 32768 bytes) [ 0.287652] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) [ 0.287812] TCP: Hash tables configured (established 8192 bind 8192) [ 0.287873] TCP: reno registered [ 0.287891] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 0.287944] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 0.288205] NET: Registered protocol family 1 [ 0.288560] RPC: Registered named UNIX socket transport module. [ 0.288572] RPC: Registered udp transport module. [ 0.288580] RPC: Registered tcp transport module. [ 0.288588] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.288601] PCI: CLS 0 bytes, default 64 [ 0.289028] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available [ 0.291033] futex hash table entries: 512 (order: 3, 32768 bytes) [ 0.292461] bounce pool size: 64 pages [ 0.293336] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 0.293541] msgmni has been set to 1487 [ 0.294002] io scheduler noop registered [ 0.294014] io scheduler deadline registered [ 0.294050] io scheduler cfq registered (default) [ 0.308117] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208 [ 0.308138] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16 [ 0.430891] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps [ 1.002723] console [ttyPS0] enabled [ 1.007012] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to f0068000 [ 1.014638] [drm] Initialized drm 1.1.0 20060810 [ 1.031685] brd: module loaded [ 1.041071] loop: module loaded [ 1.050648] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k [ 1.056479] e1000e: Copyright(c) 1999 - 2013 Intel Corporation. [ 1.064203] libphy: XEMACPS mii bus: probed [ 1.068742] ------------- phy_id = 0x3625e62 [ 1.073490] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54 [ 1.082191] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.088852] ehci-pci: EHCI PCI platform driver [ 1.096091] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing? [ 1.102897] usbcore: registered new interface driver usb-storage [ 1.109783] mousedev: PS/2 mouse device common for all mice [ 1.115866] i2c /dev entries driver [ 1.122759] zynq-edac f8006000.ps7-ddrc: ecc not enabled [ 1.128354] cpufreq_cpu0: failed to get cpu0 regulator: -19 [ 1.134235] Xilinx Zynq CpuIdle Driver started [ 1.139113] sdhci: Secure Digital Host Controller Interface driver [ 1.145204] sdhci: Copyright(c) Pierre Ossman [ 1.149621] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.156376] mmc0: no vqmmc regulator found [ 1.160390] mmc0: no vmmc regulator found [ 1.195953] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA [ 1.204636] usbcore: registered new interface driver usbhid [ 1.210146] usbhid: USB HID core driver [ 1.214863] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda [ 1.221159] nand: Micron MT29F2G08ABAEAWP [ 1.225125] nand: 256MiB, SLC, page size: 2048, OOB size: 64 [ 1.231164] Bad block table found at page 131008, version 0x01 [ 1.237557] Bad block table found at page 130944, version 0x01 [ 1.243693] 4 ofpart partitions found on MTD device pl353-nand [ 1.249478] Creating 4 MTD partitions on "pl353-nand": [ 1.254562] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel" [ 1.262620] 0x000002000000-0x00000b000000 : "angstram-rootfs" [ 1.269928] 0x00000b000000-0x00000ec00000 : "upgrade-rootfs" [ 1.277015] 0x00000ec00000-0x000010000000 : "upgrade-tmp" [ 1.285633] TCP: cubic registered [ 1.288907] NET: Registered protocol family 17 [ 1.293543] Registering SWP/SWPB emulation handler [ 1.299182] regulator-dummy: disabling [ 1.302958] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 1.313226] ALSA device list: [ 1.316190] No soundcards found. [ 4.547906] jffs2: Empty flash at 0x023f600c ends at 0x023f6800 [ 4.599355] jffs2: jffs2_scan_inode_node(): CRC failed on node at 0x02937fc8: Read 0xffffffff, calculated 0xe89f3896 [ 4.614768] jffs2: Empty flash at 0x02938030 ends at 0x02938800 [ 5.367971] VFS: Mounted root (jffs2 filesystem) on device 31:1. [ 5.376969] devtmpfs: mounted [ 5.380078] Freeing unused kernel memory: 200K (c0676000 - c06a8000) [ 7.099695] random: dd urandom read with 1 bits of entropy available [ 7.525956] [ 7.525956] bcm54xx_config_init [ 8.135957] [ 8.135957] bcm54xx_config_init [ 12.136790] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz [ 12.142897] xemacps e000b000.ps7-ethernet: link up (1000/FULL) [ 28.638592] In axi fpga driver! [ 28.641659] request_mem_region OK! [ 28.645049] AXI fpga dev virtual address is 0xf0112000 [ 28.650195] *base_vir_addr = 0x8c504 [ 28.661345] In fpga mem driver! [ 28.664418] request_mem_region OK! [ 28.668045] fpga mem virtual address is 0xf3000000 [ 30.895159] [ 30.895159] bcm54xx_config_init [ 31.675104] [ 31.675104] bcm54xx_config_init [ 36.675419] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz [ 36.681523] xemacps e000b000.ps7-ethernet: link up (1000/FULL) [ 85.994692] jffs2: warning: (1095) jffs2_do_read_inode_internal: Truncating ino #2089 to 46292 bytes failed because it only had 27394 bytes to start with! [ 332.299897] random: nonblocking pool is initialized prepare send works thread on chain[0] prepare send works thread on chain[1] prepare send works thread on chain[2] prepare send works thread on chain[3] prepare send works thread on chain[4] prepare send works thread on chain[5] prepare send works thread on chain[6] prepare send works thread on chain[7] prepare send works thread on chain[8] prepare send works thread on chain[9] prepare send works thread on chain[10] prepare send works thread on chain[11] prepare send works thread on chain[12] prepare send works thread on chain[13] prepare send works thread on chain[14] prepare send works thread on chain[15] Find hashboard on Chain[5] Find hashboard on Chain[6] Find hashboard on Chain[7] has freq in PIC, will disable freq setting. chain[5] has freq in PIC and will jump over... has freq in PIC, will disable freq setting. chain[6] has freq in PIC and will jump over... has freq in PIC, will disable freq setting. chain[7] has freq in PIC and will jump over... set command mode to VIL
singleBoardTest: AsicType = 1387
singleBoardTest: asicNum = 64
singleBoardTest: real AsicNum = 63
--- check asic number set_baud=1 The min freq=700 set real timeout 224, need sleep=1634304 disable_pic_dac on chain[5] testDone[5]=1 disable_pic_dac on chain[6] testDone[6]=1 disable_pic_dac on chain[7] testDone[7]=1 search freq for 1 times, completed chain = 3, total chain num = 3 do 12 8xPatten test for 1 times Find hashboard on Chain[5] Find hashboard on Chain[6] Find hashboard on Chain[7]
Test Patten on Chain[5] use PIC freq
Test Patten on Chain[5] use PIC freq Freq[00]=470 Freq[01]=568 Freq[02]=606 Freq[03]=470 Freq[04]=575 Freq[05]=606 Freq[06]=481 Freq[07]=575 Freq[08]=606 Freq[09]=500 Freq[10]=581 Freq[11]=606 Freq[12]=500 Freq[13]=581 Freq[14]=612 Freq[15]=537 Freq[16]=543 Freq[17]=504 Freq[18]=537 Freq[19]=593 Freq[20]=537 Freq[21]=537 Freq[22]=593 Freq[23]=537 Freq[24]=543 Freq[25]=600 Freq[26]=568 Freq[27]=543 Freq[28]=600 Freq[29]=543 Freq[30]=550 Freq[31]=543 Freq[32]=612 Freq[33]=543 Freq[34]=537 Freq[35]=612 Freq[36]=556 Freq[37]=587 Freq[38]=531 Freq[39]=556 Freq[40]=606 Freq[41]=550 Freq[42]=543 Freq[43]=550 Freq[44]=618 Freq[45]=556 Freq[46]=606 Freq[47]=537 Freq[48]=500 Freq[49]=470 Freq[50]=618 Freq[51]=562 Freq[52]=606 Freq[53]=612 Freq[54]=562 Freq[55]=556 Freq[56]=618 Freq[57]=568 Freq[58]=606 Freq[59]=618 Freq[60]=568 Freq[61]=606 Freq[62]=606
Test Patten on Chain[6] use PIC freq
Test Patten on Chain[6] use PIC freq Freq[00]=600 Freq[01]=650 Freq[02]=650 Freq[03]=618 Freq[04]=650 Freq[05]=650 Freq[06]=625 Freq[07]=650 Freq[08]=650 Freq[09]=650 Freq[10]=650 Freq[11]=650 Freq[12]=587 Freq[13]=650 Freq[14]=650 Freq[15]=650 Freq[16]=650 Freq[17]=575 Freq[18]=650 Freq[19]=568 Freq[20]=650 Freq[21]=650 Freq[22]=637 Freq[23]=650 Freq[24]=650 Freq[25]=650 Freq[26]=618 Freq[27]=650 Freq[28]=650 Freq[29]=637 Freq[30]=650 Freq[31]=650 Freq[32]=650 Freq[33]=650 Freq[34]=650 Freq[35]=625 Freq[36]=650 Freq[37]=631 Freq[38]=650 Freq[39]=643 Freq[40]=650 Freq[41]=650 Freq[42]=650 Freq[43]=650 Freq[44]=650 Freq[45]=650 Freq[46]=650 Freq[47]=643 Freq[48]=618 Freq[49]=650 Freq[50]=650 Freq[51]=650 Freq[52]=631 Freq[53]=650 Freq[54]=650 Freq[55]=650 Freq[56]=650 Freq[57]=650 Freq[58]=568 Freq[59]=650 Freq[60]=568 Freq[61]=650 Freq[62]=650
Test Patten on Chain[7] use PIC freq
Test Patten on Chain[7] use PIC freq Freq[00]=575 Freq[01]=656 Freq[02]=625 Freq[03]=575 Freq[04]=656 Freq[05]=656 Freq[06]=575 Freq[07]=656 Freq[08]=656 Freq[09]=581 Freq[10]=656 Freq[11]=656 Freq[12]=593 Freq[13]=656 Freq[14]=656 Freq[15]=656 Freq[16]=656 Freq[17]=650 Freq[18]=656 Freq[19]=650 Freq[20]=656 Freq[21]=656 Freq[22]=656 Freq[23]=537 Freq[24]=656 Freq[25]=656 Freq[26]=581 Freq[27]=656 Freq[28]=656 Freq[29]=650 Freq[30]=656 Freq[31]=550 Freq[32]=656 Freq[33]=631 Freq[34]=656 Freq[35]=656 Freq[36]=656 Freq[37]=537 Freq[38]=656 Freq[39]=656 Freq[40]=643 Freq[41]=656 Freq[42]=656 Freq[43]=643 Freq[44]=562 Freq[45]=656 Freq[46]=656 Freq[47]=650 Freq[48]=656 Freq[49]=656 Freq[50]=656 Freq[51]=656 Freq[52]=568 Freq[53]=656 Freq[54]=631 Freq[55]=625 Freq[56]=656 Freq[57]=656 Freq[58]=556 Freq[59]=656 Freq[60]=575 Freq[61]=656 Freq[62]=656 use PIC voltage=870 on chain[5] now set pic voltage=125 on chain[5] use PIC voltage=870 on chain[6] now set pic voltage=125 on chain[6] use PIC voltage=870 on chain[7] now set pic voltage=125 on chain[7] enable_pic_dac on chain[5] enable_pic_dac on chain[6] enable_pic_dac on chain[7] set command mode to VIL
doHeatBoard: AsicType = 1387
doHeatBoard: asicNum = 64
doHeatBoard: real AsicNum = 63
--- check asic number check chain[5]: asicNum = 63 check chain[6]: asicNum = 63 check chain[7]: asicNum = 63 Set Freq of PIC for Test Patten on Chain[5] Set Freq of PIC for Test Patten on Chain[6] Set Freq of PIC for Test Patten on Chain[7] set_baud=2 The min freq=470 set real timeout 334, need sleep=2436864 start send works on chain[5] start send works on chain[6] start send works on chain[7] wait send works done on chain[5] get send work num :57456 on Chain[5] get send work num :57456 on Chain[7] get send work num :57456 on Chain[6] wait send works done on chain[6] wait send works done on chain[7] wait recv nonce on chain[5] wait recv nonce on chain[6] wait recv nonce on chain[7] get nonces on chain[5] require nonce number:912 require validnonce number:57456
freq[00]=470 freq[01]=568 freq[02]=606 freq[03]=470 freq[04]=575 freq[05]=606 freq[06]=481 freq[07]=575 freq[08]=606 freq[09]=500 freq[10]=581 freq[11]=606 freq[12]=500 freq[13]=581 freq[14]=612 freq[15]=537 freq[16]=543 freq[17]=504 freq[18]=537 freq[19]=593 freq[20]=537 freq[21]=537 freq[22]=593 freq[23]=537 freq[24]=543 freq[25]=600 freq[26]=568 freq[27]=543 freq[28]=600 freq[29]=543 freq[30]=550 freq[31]=543 freq[32]=612 freq[33]=543 freq[34]=537 freq[35]=612 freq[36]=556 freq[37]=587 freq[38]=531 freq[39]=556 freq[40]=606 freq[41]=550 freq[42]=543 freq[43]=550 freq[44]=618 freq[45]=556 freq[46]=606 freq[47]=537 freq[48]=500 freq[49]=470 freq[50]=618 freq[51]=562 freq[52]=606 freq[53]=612 freq[54]=562 freq[55]=556 freq[56]=618 freq[57]=568 freq[58]=606 freq[59]=618 freq[60]=568 freq[61]=606 freq[62]=606
total valid nonce number:57456 total send work number:57456 require valid nonce number:57456 repeated_nonce_num:0 err_nonce_num:34998 last_nonce_num:0 get nonces on chain[6] require nonce number:912 require validnonce number:57456
freq[00]=600 freq[01]=650 freq[02]=650 freq[03]=618 freq[04]=650 freq[05]=650 freq[06]=625 freq[07]=650 freq[08]=650 freq[09]=650 freq[10]=650 freq[11]=650 freq[12]=587 freq[13]=650 freq[14]=650 freq[15]=650 freq[16]=650 freq[17]=575 freq[18]=650 freq[19]=568 freq[20]=650 freq[21]=650 freq[22]=637 freq[23]=650 freq[24]=650 freq[25]=650 freq[26]=618 freq[27]=650 freq[28]=650 freq[29]=637 freq[30]=650 freq[31]=650 freq[32]=650 freq[33]=650 freq[34]=650 freq[35]=625 freq[36]=650 freq[37]=631 freq[38]=650 freq[39]=643 freq[40]=650 freq[41]=650 freq[42]=650 freq[43]=650 freq[44]=650 freq[45]=650 freq[46]=650 freq[47]=643 freq[48]=618 freq[49]=650 freq[50]=650 freq[51]=650 freq[52]=631 freq[53]=650 freq[54]=650 freq[55]=650 freq[56]=650 freq[57]=650 freq[58]=568 freq[59]=650 freq[60]=568 freq[61]=650 freq[62]=650
total valid nonce number:57456 total send work number:57456 require valid nonce number:57456 repeated_nonce_num:0 err_nonce_num:39562 last_nonce_num:0 get nonces on chain[7] require nonce number:912 require validnonce number:57456
freq[00]=575 freq[01]=656 freq[02]=625 freq[03]=575 freq[04]=656 freq[05]=656 freq[06]=575 freq[07]=656 freq[08]=656 freq[09]=581 freq[10]=656 freq[11]=656 freq[12]=593 freq[13]=656 freq[14]=656 freq[15]=656 freq[16]=656 freq[17]=650 freq[18]=656 freq[19]=650 freq[20]=656 freq[21]=656 freq[22]=656 freq[23]=537 freq[24]=656 freq[25]=656 freq[26]=581 freq[27]=656 freq[28]=656 freq[29]=650 freq[30]=656 freq[31]=550 freq[32]=656 freq[33]=631 freq[34]=656 freq[35]=656 freq[36]=656 freq[37]=537 freq[38]=656 freq[39]=656 freq[40]=643 freq[41]=656 freq[42]=656 freq[43]=643 freq[44]=562 freq[45]=656 freq[46]=656 freq[47]=650 freq[48]=656 freq[49]=656 freq[50]=656 freq[51]=656 freq[52]=568 freq[53]=656 freq[54]=631 freq[55]=625 freq[56]=656 freq[57]=656 freq[58]=556 freq[59]=656 freq[60]=575 freq[61]=656 freq[62]=656
total valid nonce number:57456 total send work number:57456 require valid nonce number:57456 repeated_nonce_num:0 err_nonce_num:39372 last_nonce_num:57 Test Patten on chain[5]: OK! Test Patten on chain[6]: OK! Test Patten on chain[7]: OK! disable_pic_dac on chain[5] disable_pic_dac on chain[6] disable_pic_dac on chain[7] waiting for send_func to exit of chain[0] waiting for send_func to exit of chain[1] waiting for send_func to exit of chain[2] waiting for send_func to exit of chain[3] waiting for send_func to exit of chain[4] waiting for send_func to exit of chain[5] waiting for send_func to exit of chain[6] waiting for send_func to exit of chain[7] waiting for send_func to exit of chain[8] waiting for send_func to exit of chain[9] waiting for send_func to exit of chain[10] waiting for send_func to exit of chain[11] waiting for send_func to exit of chain[12] waiting for send_func to exit of chain[13] waiting for send_func to exit of chain[14] waiting for send_func to exit of chain[15] waiting for receive_func to exit! waiting for pic heart to exit! Start bmminer ... miner total rate=13203GH/s fixed rate=13000GH/s read PIC voltage=870 on chain[5] Chain:5 chipnum=63 Chain[J6] voltage added=0.1V OK: Chain[J6] is for this machine! [minerMAC: 00:13:f0:a4:b2:1b] Chain:5 temp offset=-70 Chain:5 base freq=470 Asic[ 0]:470 Asic[ 1]:568 Asic[ 2]:606 Asic[ 3]:470 Asic[ 4]:575 Asic[ 5]:606 Asic[ 6]:481 Asic[ 7]:575 Asic[ 8]:606 Asic[ 9]:500 Asic[10]:581 Asic[11]:606 Asic[12]:500 Asic[13]:581 Asic[14]:612 Asic[15]:537 Asic[16]:543 Asic[17]:504 Asic[18]:537 Asic[19]:593 Asic[20]:537 Asic[21]:537 Asic[22]:593 Asic[23]:537 Asic[24]:543 Asic[25]:600 Asic[26]:568 Asic[27]:543 Asic[28]:600 Asic[29]:543 Asic[30]:550 Asic[31]:543 Asic[32]:612 Asic[33]:543 Asic[34]:537 Asic[35]:612 Asic[36]:556 Asic[37]:587 Asic[38]:531 Asic[39]:556 Asic[40]:606 Asic[41]:550 Asic[42]:543 Asic[43]:550 Asic[44]:618 Asic[45]:556 Asic[46]:606 Asic[47]:537 Asic[48]:500 Asic[49]:470 Asic[50]:618 Asic[51]:562 Asic[52]:606 Asic[53]:612 Asic[54]:562 Asic[55]:556 Asic[56]:618 Asic[57]:568 Asic[58]:606 Asic[59]:618 Asic[60]:568 Asic[61]:606 Asic[62]:606 Chain:5 max freq=618 Chain:5 min freq=470
read PIC voltage=870 on chain[6] Chain:6 chipnum=63 Chain[J7] voltage added=0.1V OK: Chain[J7] is for this machine! [minerMAC: 00:13:f0:a4:b2:1b] Chain:6 temp offset=-70 Chain:6 base freq=568 Asic[ 0]:600 Asic[ 1]:650 Asic[ 2]:650 Asic[ 3]:618 Asic[ 4]:650 Asic[ 5]:650 Asic[ 6]:625 Asic[ 7]:650 Asic[ 8]:650 Asic[ 9]:650 Asic[10]:650 Asic[11]:650 Asic[12]:587 Asic[13]:650 Asic[14]:650 Asic[15]:650 Asic[16]:650 Asic[17]:575 Asic[18]:650 Asic[19]:568 Asic[20]:650 Asic[21]:650 Asic[22]:637 Asic[23]:650 Asic[24]:650 Asic[25]:650 Asic[26]:618 Asic[27]:650 Asic[28]:650 Asic[29]:637 Asic[30]:650 Asic[31]:650 Asic[32]:650 Asic[33]:650 Asic[34]:650 Asic[35]:625 Asic[36]:650 Asic[37]:631 Asic[38]:650 Asic[39]:643 Asic[40]:650 Asic[41]:650 Asic[42]:650 Asic[43]:650 Asic[44]:650 Asic[45]:650 Asic[46]:650 Asic[47]:643 Asic[48]:618 Asic[49]:650 Asic[50]:650 Asic[51]:650 Asic[52]:631 Asic[53]:650 Asic[54]:650 Asic[55]:650 Asic[56]:650 Asic[57]:650 Asic[58]:568 Asic[59]:650 Asic[60]:568 Asic[61]:650 Asic[62]:650 Chain:6 max freq=650 Chain:6 min freq=568
read PIC voltage=870 on chain[7] Chain:7 chipnum=63 Chain[J8] voltage added=0.1V OK: Chain[J8] is for this machine! [minerMAC: 00:13:f0:a4:b2:1b] Chain:7 temp offset=-70 Chain:7 base freq=537 Asic[ 0]:575 Asic[ 1]:656 Asic[ 2]:625 Asic[ 3]:575 Asic[ 4]:656 Asic[ 5]:656 Asic[ 6]:575 Asic[ 7]:656 Asic[ 8]:656 Asic[ 9]:581 Asic[10]:656 Asic[11]:656 Asic[12]:593 Asic[13]:656 Asic[14]:656 Asic[15]:656 Asic[16]:656 Asic[17]:650 Asic[18]:656 Asic[19]:650 Asic[20]:656 Asic[21]:656 Asic[22]:656 Asic[23]:537 Asic[24]:656 Asic[25]:656 Asic[26]:581 Asic[27]:656 Asic[28]:656 Asic[29]:650 Asic[30]:656 Asic[31]:550 Asic[32]:656 Asic[33]:631 Asic[34]:656 Asic[35]:656 Asic[36]:656 Asic[37]:537 Asic[38]:656 Asic[39]:656 Asic[40]:643 Asic[41]:656 Asic[42]:656 Asic[43]:643 Asic[44]:562 Asic[45]:656 Asic[46]:656 Asic[47]:650 Asic[48]:656 Asic[49]:656 Asic[50]:656 Asic[51]:656 Asic[52]:568 Asic[53]:656 Asic[54]:631 Asic[55]:625 Asic[56]:656 Asic[57]:656 Asic[58]:556 Asic[59]:656 Asic[60]:575 Asic[61]:656 Asic[62]:656 Chain:7 max freq=656 Chain:7 min freq=537
Miner fix freq ... read PIC voltage=870 on chain[5] Chain:5 chipnum=63 Chain[J6] voltage added=0.1V OK: Chain[J6] is for this machine! [minerMAC: 00:13:f0:a4:b2:1b] Chain:5 temp offset=-70 Chain:5 base freq=470 Asic[ 0]:470 Asic[ 1]:568 Asic[ 2]:606 Asic[ 3]:470 Asic[ 4]:575 Asic[ 5]:606 Asic[ 6]:481 Asic[ 7]:575 Asic[ 8]:606 Asic[ 9]:500 Asic[10]:581 Asic[11]:606 Asic[12]:500 Asic[13]:581 Asic[14]:612 Asic[15]:537 Asic[16]:543 Asic[17]:504 Asic[18]:537 Asic[19]:593 Asic[20]:537 Asic[21]:537 Asic[22]:593 Asic[23]:537 Asic[24]:543 Asic[25]:600 Asic[26]:568 Asic[27]:543 Asic[28]:600 Asic[29]:543 Asic[30]:550 Asic[31]:543 Asic[32]:612 Asic[33]:543 Asic[34]:537 Asic[35]:612 Asic[36]:556 Asic[37]:587 Asic[38]:531 Asic[39]:556 Asic[40]:606 Asic[41]:550 Asic[42]:543 Asic[43]:550 Asic[44]:618 Asic[45]:556 Asic[46]:606 Asic[47]:537 Asic[48]:500 Asic[49]:470 Asic[50]:618 Asic[51]:562 Asic[52]:606 Asic[53]:612 Asic[54]:562 Asic[55]:556 Asic[56]:618 Asic[57]:568 Asic[58]:606 Asic[59]:618 Asic[60]:568 Asic[61]:606 Asic[62]:606 Chain:5 max freq=618 Chain:5 min freq=470
read PIC voltage=870 on chain[6] Chain:6 chipnum=63 Chain[J7] voltage added=0.1V OK: Chain[J7] is for this machine! [minerMAC: 00:13:f0:a4:b2:1b] Chain:6 temp offset=-70 Chain:6 base freq=568 Asic[ 0]:600 Asic[ 1]:631 Asic[ 2]:631 Asic[ 3]:618 Asic[ 4]:631 Asic[ 5]:631 Asic[ 6]:625 Asic[ 7]:631 Asic[ 8]:631 Asic[ 9]:631 Asic[10]:631 Asic[11]:631 Asic[12]:587 Asic[13]:631 Asic[14]:631 Asic[15]:631 Asic[16]:631 Asic[17]:575 Asic[18]:631 Asic[19]:568 Asic[20]:631 Asic[21]:631 Asic[22]:631 Asic[23]:631 Asic[24]:631 Asic[25]:631 Asic[26]:618 Asic[27]:631 Asic[28]:631 Asic[29]:631 Asic[30]:631 Asic[31]:631 Asic[32]:631 Asic[33]:631 Asic[34]:631 Asic[35]:625 Asic[36]:631 Asic[37]:631 Asic[38]:631 Asic[39]:631 Asic[40]:631 Asic[41]:631 Asic[42]:631 Asic[43]:631 Asic[44]:631 Asic[45]:631 Asic[46]:631 Asic[47]:631 Asic[48]:618 Asic[49]:631 Asic[50]:631 Asic[51]:631 Asic[52]:631 Asic[53]:631 Asic[54]:631 Asic[55]:631 Asic[56]:631 Asic[57]:631 Asic[58]:568 Asic[59]:631 Asic[60]:568 Asic[61]:631 Asic[62]:631 Chain:6 max freq=631 Chain:6 min freq=568
read PIC voltage=870 on chain[7] Chain:7 chipnum=63 Chain[J8] voltage added=0.1V OK: Chain[J8] is for this machine! [minerMAC: 00:13:f0:a4:b2:1b] Chain:7 temp offset=-70 Chain:7 base freq=537 Asic[ 0]:575 Asic[ 1]:631 Asic[ 2]:625 Asic[ 3]:575 Asic[ 4]:631 Asic[ 5]:631 Asic[ 6]:575 Asic[ 7]:631 Asic[ 8]:631 Asic[ 9]:581 Asic[10]:631 Asic[11]:637 Asic[12]:593 Asic[13]:637 Asic[14]:637 Asic[15]:637 Asic[16]:637 Asic[17]:637 Asic[18]:637 Asic[19]:637 Asic[20]:637 Asic[21]:637 Asic[22]:637 Asic[23]:537 Asic[24]:637 Asic[25]:637 Asic[26]:581 Asic[27]:637 Asic[28]:637 Asic[29]:637 Asic[30]:637 Asic[31]:550 Asic[32]:637 Asic[33]:631 Asic[34]:637 Asic[35]:637 Asic[36]:637 Asic[37]:537 Asic[38]:637 Asic[39]:637 Asic[40]:637 Asic[41]:637 Asic[42]:637 Asic[43]:637 Asic[44]:562 Asic[45]:637 Asic[46]:637 Asic[47]:637 Asic[48]:637 Asic[49]:637 Asic[50]:637 Asic[51]:637 Asic[52]:568 Asic[53]:637 Asic[54]:631 Asic[55]:625 Asic[56]:637 Asic[57]:637 Asic[58]:556 Asic[59]:637 Asic[60]:575 Asic[61]:637 Asic[62]:637 Chain:7 max freq=637 Chain:7 min freq=537
max freq = 637 Chain[5] Chip[62] local Temp=71 Chain[5] Chip[62] middle Temp=87 Chain[6] Chip[62] local Temp=71 Chain[6] Chip[62] middle Temp=90 Chain[7] Chip[62] local Temp=72 Chain[7] Chip[62] middle Temp=90 FAN PWM: 45
Frankly, I think the performance checks are a good solution to the fact that due to 16nm process variations the chips and therefore boards have a 'butter zone' that can be substantially different from one wafer to another. It also leads to an idea of looking over a stock of miners then taking the best boards and putting them in 1 'Super' miner... Wonder what a single 3-board miner could hit if all boards can run at top speed? mebe say >16THs? So far after nearly 24hrs the miner works great ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Please inform us if it is better than the previous batches because I am really considering to buy one that is reliable
For the most part with the S9's it seems it is a crap shoot. I have 8 of the s9 miners spanning batch 1 through 17 and most run fine. Yes 2 of them, a batch-1 and a batch-11 had a hash board die (which were repaired by Bitmain Warranty) but so far it looks like no single batch is better than another.
|
|
|
Just got a s9 batch-17 and... Bitmain has changed the firmware. I will post in detail tomorrow but for a summary of changes: - They have changed the board channels used and so the temp reporting channels. Now using channels 6, 7, and 8.
- Looks like changing the frequency may be gone. There is no longer a GUI option to change it. On startup, the firmware goes through several checks per-board and sets the best freq and possibly Vcore as well per-board. When all is done, the boards report different frequencies. This could turn out to be rather -- interesting.
- Looking at the Kernel Log it shows several lists of freq and voltage it tries for each board. A note at the beginning of each list says that freq is now stored in the PIC. Now does that mean that a warm boot bypasses the testing -- dunna know but hope so.
I'll post the Kernel Log tomorrow. Also fan speed no longer has a setting on the BMminer GUI. Log says is set as needed starting at 40% Oh, the fans are on different channels as well. Think fans are now reported in position 6 an 8. I'll verify tomorrow. edit: Fans in positions 3 and 6 Due to the time it takes for the new booting process -- around 4 min or more -- better set dead miner/offline/etc monitoring to wait at least that 4 maybe even 5 min before trying to issue another reboot call to the miner... Frankly, during the setup process for miner name and pool assignments the reboots needed were taking so long that I thought the miner was going to be a DOA! ![Shocked](https://bitcointalk.org/Smileys/default/shocked.gif) Folks, keep in mind that much longer time needed to come to life before you start to get miffed/worried like I was. A couple times when it was taking A LOT longer than was normal with the earlier batches I forced reboots trying to get the miner to respond. thankfully it didn't brick.
|
|
|
If you have hard rebooted it a few times and it still comes back, you just have a bad chip. No way to fix it.
Well, yes and no. Quite often dropping the miner speed down a notch or 2 will bring a weak chip back to life. It just doesn't want to run at full speed. Only drawback is that the new total hashrate will probably be less than having the 1 chip offline, so.... I'd leave it as-is.
|
|
|
@ patrike Just got a s9 batch-17 and... Bitmain has changed the firmware, is now BMminer v2.0. I will post in detail tomorrow but for a summary of changes: - They have changed the hash board channels and therefore die temp reporting channels. Now using channels 6, 7, and 8. Might need to come up with a routine to scan the die temp channels and only use ones reporting something...
- Looks like changing the frequency may be gone. In the Bitmain GUI that choice is gone. On startup, the firmware goes through several checks per-board and sets the best freq and possibly Vcore as well. When all is done, the boards report different frequencies.
Looking at the Kernel Log it shows several lists of freq and voltage it tries for each board. A note at the beginning of each list says that freq is now stored in the PIC. Now does that mean that a warm boot bypasses the testing -- dunna know but hope so. I'll post the Kernel Log tomorrow. Also fan speed no longer has a setting on the BMminer GUI. Log says is set as needed starting at 40% Oh, the fans are on different channels as well. Think fans are now reported in positions 6 an 8. I'll verify tomorrow. edit: fans in positions 3 and 6. Due to the time it takes for the new rebooting process -- around 4 min -- better set dead miner/offline/etc to wait at least that 4 maybe even 5 min before trying to issue another reboot call to the miner... Other than that, everything else works fine inc the Web access and info to it.
|
|
|
|