[...]
i dont know why in my kernel log still show
[...]
i restore original t9+ firmware but what realy happened to my miner
what you think? i try to revert back to original firmware but fails
Try to flash this then your t9+ firmware: https://file.bitmain.com/shop-bitmain/download/s9_fix_upgrade.tar.gzit is the fix for when you cant flash proper firmware on the s9 but it should flash on all models. Then try to flash proper t9+ software. |
|
|
|
ok where should i copy this file it seems you forgot to include the Path  Check the main post on the thread you have to follow those same instructions to replace the stock bmminer on your miner. The T9 and S9 are VERY similar. I think the main difference between them is bmminer and of course the number of ships. That bmminer is modified for your t9+. |
|
|
|
Hi,
I tried today to start your firmware on 800M(bmminer880) the temperature sensor on the third Board stopped working, gave an error. As the temperature jumped to 88, 103 degrees, like lags. I'm stopping at 750M. Before that, a few days I tested 725M.
What about your meter?
What is the power consumption board for 800M and 8.8v?
And what about the setup for each board? I noticed (as I said before) some boards are able to take a good overclocking, some are not. For example, one board can take 700M only, the other 750M.
Yeah so Temperature sensor not working is common. More often than not if it doesn't work any of them work. I found it funny only 1 of yours stopped working. Could you send me your kernal log when it does that again? Yeah 95-105ish is normal for 800mhz the factory defaults on the s9 thermal throttle at 120 but I have this set to the new bitmain firmware setting of 110. I am going to use the meter today. I got to figure out how to properly do this haha... Since dc you can't just clamp you have to probe it and I am trying to figure out the best way to probe it. Or if I can use a clamp if anyone knows how let me know. |
|
|
|
Here we go mate
[...]
Here you go buddy I am sorry it took me so long to get this done this is good for the T9+ 18 chip version that you have. Please give this a stest and let me know how it works for you. I locked it to 8.8v so expect an increased power draw over stock but your overclock limit should increase quiet a bit because of this but you need to do trial an error and work it up slowly since I couldn't find public data for the T9+ Please report your results https://github.com/taserz/S9-Volt-Rocket-Ship/raw/master/bmminer880_T9%2B |
|
|
|
|
Turn it on while holdinh down the ip report button for 10-15 seconds so it reboots and flashes itself back to stock settings just to make sure any bmminer edits are removed from that other guys frimware.
|
|
|
|
Beautiful job with this and thank you for sharing it! I'm testing it on a 13.5TH S9 and am curious, how many errors are too many?
I've gradually stepped up the frequency from 675 Mhz and have found that some are dramatically less efficient than others. I let the machine sit for 1-2 hours on the pool to get comparative hash reports. If pool and S9 gui are 2+ TH off from each other (pool always less), I immediately try the next frequency. What else should I be watching?
It's luck of the draw with the s9 some can run at faster speeds with less power draw some run like crap at high frequency. If the pool is off by over 2 th you probably have a lot of hw errors that or the pool takes a long time to get the speed like slushs pool it takes 1 hour to get the proper reported speed. I will try to make a firmware for you guys and get it done today if I can. Are all your hashboard still working? Also are you able to ssh into it to replace the bmminer. |
|
|
|
dude i lost my hashing power after that damn dolemaze upgrade.
i have T9+ can you help me to bring back my miner to live?
Flashback to factory first. S9 firmware doesn't run on T9's they are different. |
|
|
|
Yes. I am watching it on the pool side too. Those HW errors seem to kill a lot of shares.
hw errors don't really make much of a difference unless you're getting them every second. |
|
|
|
OK. I am at 750MHZ, 91C, 15,309.53 RT. HW errors are about 2 per minute. Too high I think.
Check that. HW error rate decreasing. Looks stable now. 22 minutes in.
HMM. HW error rate back to 2 per minute. 27 minutes in. 2 per minute is right around where you want to keep it. Anything more you should tune it down. But let it run for a while the hw errors tend to stop after it gets going for a bit. I have had stock s9's do 200 hw errors in an hour. But I found once you get it running for a bit it tends to slow down. 725 isa what many were finding is best for 13.5 and 14 s9. Some 14th s9 were going pretty high. |
|
|
|
I'll try to bump it up more tomorrow when I have a 2nd power supply. Electric is sketchy in my country too, so I don't want to tempt fate.
You don't have to worry about sketchy electricity. The bitmain psu is actually really good and if the miner causes itself to surge and draw more than 1600w of power it will turn off the miner and go in protect mode so you will have to unplug it for a little bit. if you use more then 1 psu then you can end up drawing more than 1600w. |
|
|
|
Right. Great news. I'll be sure to use that one on the S9i.
In the mean time, I used the bmminer880 on a s9 14 T, set to 725 Mhz. I am getting 15,084.28 RT, and the temps are reporting fine. Highest temp is 88. I am happy with that number because today isn't particularly hot, and I live in a hot country. I need to probably not go any higher with the OC.
I'll run it for a few hours and report back. I will be getting my other machines back from hosting tomorrow and I'll test them out. All on the 1600W Bitmain PSU. So far I am very pleased though.
Thank you so much!
If you get adventurous can you see what mhz you 14t can run stable on 8.8v I have a feeling those can go up to 800mhz but my units are being hosted. Could you try increasing it slowly until it starts getting HW errors. I think it will trip the PSU and draw to much power @ around 800mhz thought since the chip is less efficient but it's a gamble since not all hashboards are made equal. |
|
|
|
What are the main differences, if you don't mind me asking?
Small changes I think I fixed the temp not reporting on s9i. I am not sure if it also fixed it for the S9. It was hit and miss before if it would read the temp. |
|
|
|
I probably should. But yours is not a true firmware unless I missed something. It's simply a miner replacement. I will have to write my own management script to modify my little 7 machine farm. It's not a huge deal I just don't have tons of time to work on it at the moment.
It will take you less than 10 minutes to do it to 7 machines. I am working on making it flashable but I rather make it better before making it flashable. Currently mine does everything this one does and more with no dev fee. Hell if there was to be a feed it would be so much smaller than this dude hijacking everyone's machines. Also this guys firmware is only a modification of bmminer and your ssh password I took a look  |
|
|
|
Hi taserz,
So I noticed on your Github the bmminer880New entry. Is this going to be something I should wait for? Because I am about to start playing with my machines.
Best,
MrMaxwell
Yes You can start using the 880New. I am going to eventually replace the 880 with it and remove the word new. But I am testing it right now and things seem to be going better than the previous revision. |
|
|
|
I am trying to build the firmware but it is only 40mb... The real firmware is 60mb... Anyone got any ideas it won't run. I am working on a firmware flash verse all the manual edits. This is the kernel log: [ 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 16800000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 126976
[ 0.000000] free_area_init_node: node 0, pgdat c0740a40, node_mem_map debd8000
[ 0.000000] Normal zone: 992 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 126976 pages, LIFO batch:31
[ 0.000000] PERCPU: Embedded 8 pages/cpu @debc1000 s9088 r8192 d15488 u32768
[ 0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 125984
[ 0.000000] Kernel command line: noinitrd mem=496M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 364356K/507904K available (5032K kernel code, 283K rwdata, 1916K rodata, 204K init, 258K bss, 143548K reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xdf800000 - 0xff000000 ( 504 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xdf000000 ( 496 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 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 df802000
[ 0.000000] zynq_clock_init: clkc starts at df802100
[ 0.000000] Zynq clock init
[ 0.000014] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[ 0.000304] ps7-ttc #0 at df804000, irq=43
[ 0.000613] Console: colour dummy device 80x30
[ 0.000645] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328)
[ 0.040205] pid_max: default: 32768 minimum: 301
[ 0.040428] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.040447] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.042635] CPU: Testing write buffer coherency: ok
[ 0.042984] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.043045] Setting up static identity map for 0x4c4af8 - 0x4c4b50
[ 0.043269] L310 cache controller enabled
[ 0.043289] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[ 0.121034] CPU1: Booted secondary processor
[ 0.210224] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.210356] Brought up 2 CPUs
[ 0.210376] SMP: Total of 2 processors activated.
[ 0.210384] CPU: All CPU(s) started in SVC mode.
[ 0.211058] devtmpfs: initialized
[ 0.213494] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.214737] regulator-dummy: no parameters
[ 0.223272] NET: Registered protocol family 16
[ 0.225586] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.227907] cpuidle: using governor ladder
[ 0.227921] cpuidle: using governor menu
[ 0.235409] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[ 0.236944] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.236959] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.237077] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000
[ 0.259338] bio: create slab <bio-0> at 0
[ 0.260907] vgaarb: loaded
[ 0.261684] SCSI subsystem initialized
[ 0.262566] usbcore: registered new interface driver usbfs
[ 0.262743] usbcore: registered new interface driver hub
[ 0.262976] usbcore: registered new device driver usb
[ 0.263518] media: Linux media interface: v0.10
[ 0.263678] Linux video capture interface: v2.00
[ 0.263921] pps_core: LinuxPPS API ver. 1 registered
[ 0.263933] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.264057] PTP clock support registered
[ 0.264416] EDAC MC: Ver: 3.0.0
[ 0.265493] Advanced Linux Sound Architecture Driver Initialized.
[ 0.268486] DMA-API: preallocated 4096 debug entries
[ 0.268501] DMA-API: debugging enabled by kernel config
[ 0.268589] Switched to clocksource arm_global_timer
[ 0.289916] NET: Registered protocol family 2
[ 0.290589] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.290646] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.290731] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.290780] TCP: reno registered
[ 0.290798] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.290830] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.291086] NET: Registered protocol family 1
[ 0.291402] RPC: Registered named UNIX socket transport module.
[ 0.291415] RPC: Registered udp transport module.
[ 0.291424] RPC: Registered tcp transport module.
[ 0.291432] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.291445] PCI: CLS 0 bytes, default 64
[ 0.291900] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[ 0.293942] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.296144] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.296335] msgmni has been set to 967
[ 0.297141] io scheduler noop registered
[ 0.297155] io scheduler deadline registered
[ 0.297194] io scheduler cfq registered (default)
[ 0.309474] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[ 0.309495] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.434807] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[ 1.002104] console [ttyPS0] enabled
[ 1.006411] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000
[ 1.014067] [drm] Initialized drm 1.1.0 20060810
[ 1.031369] brd: module loaded
[ 1.040834] loop: module loaded
[ 1.050515] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[ 1.056266] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[ 1.064144] libphy: XEMACPS mii bus: probed
[ 1.068515] ------------- phy_id = 0x3625e62
[ 1.073486] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[ 1.082136] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.088990] ehci-pci: EHCI PCI platform driver
[ 1.096222] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[ 1.103094] usbcore: registered new interface driver usb-storage
[ 1.109998] mousedev: PS/2 mouse device common for all mice
[ 1.116102] i2c /dev entries driver
[ 1.123095] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[ 1.128626] cpufreq_cpu0: failed to get cpu0 regulator: -19
[ 1.134530] Xilinx Zynq CpuIdle Driver started
[ 1.139403] sdhci: Secure Digital Host Controller Interface driver
[ 1.145495] sdhci: Copyright(c) Pierre Ossman
[ 1.149910] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.156656] mmc0: no vqmmc regulator found
[ 1.160699] mmc0: no vmmc regulator found
[ 1.198608] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[ 1.207302] usbcore: registered new interface driver usbhid
[ 1.212817] usbhid: USB HID core driver
[ 1.217540] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.223835] nand: Micron MT29F2G08ABAEAWP
[ 1.227802] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[ 1.233744] Bad block table found at page 131008, version 0x01
[ 1.239969] Bad block table found at page 130944, version 0x01
[ 1.246025] 3 ofpart partitions found on MTD device pl353-nand
[ 1.251809] Creating 3 MTD partitions on "pl353-nand":
[ 1.256901] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[ 1.264978] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[ 1.272310] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[ 1.281313] TCP: cubic registered
[ 1.284545] NET: Registered protocol family 17
[ 1.289275] Registering SWP/SWPB emulation handler
[ 1.295198] regulator-dummy: disabling
[ 1.299597] UBI: attaching mtd1 to ubi0
[ 1.674740] UBI: scanning is finished
[ 1.686654] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[ 1.693736] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.700498] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.707163] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.714041] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[ 1.720021] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.727129] UBI: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 227368296
[ 1.736084] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[ 1.745302] UBI: background thread "ubi_bgt0d" started, PID 1080
[ 1.745307] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 1.749420] ALSA device list:
[ 1.749424] No soundcards found.
[ 1.765844] UBIFS: background thread "ubifs_bgt0_0" started, PID 1082
[ 1.912100] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 1.918028] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 1.927160] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[ 1.937044] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 1.942083] UBIFS: media format: w4/r0 (latest is w4/r0), UUID A1445D82-E6B9-445B-AD23-685FEDA102F2, small LPT model
[ 1.960857] VFS: Mounted root (ubifs filesystem) on device 0:11.
[ 1.974068] devtmpfs: mounted
[ 1.977180] Freeing unused kernel memory: 204K (c06d2000 - c0705000)
[ 3.070199] random: dd urandom read with 0 bits of entropy available
[ 3.678655]
[ 3.678655] bcm54xx_config_init
[ 4.288600]
[ 4.288600] bcm54xx_config_init
[ 7.289471] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[ 7.295561] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[ 36.248600]
[ 36.248600] bcm54xx_config_init
[ 36.878602]
[ 36.878602] bcm54xx_config_init
[ 39.879473] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[ 39.885493] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[ 389.699317] random: nonblocking pool is initialized
Figure someone here might be able to tell from the kernal log since I think whatever it is is obvious. |
|
|
|
|
@zeus
I am going to try to compile one for the T9+ tonight.
|
|
|
|
The second is 8.8 correct. 800 if you have an s9i 14th/ and possibly s9 version as well. You got to do some trial an error as I don't have all my machines to play with since they are being hosted so I am having the community help me figure out the best preset for the S9's I would start at 700Mhz and work your way up. Most people have 725Mh/z work on all S9 models so that might be a good starting point too. |
|
|
|
I have: 2 x S9 14T, 1 x S9 13.5, and 1 x S9i 13.5T. All 4 have the 1600w Bitmain PSUs. What firmware and settings should I use to get about 10% or more performance boost? TIA
The 8.8v right now is running the best on the bitmain 1600w PSU. For the S9i I would try 800Mhz and see what temps your getting should be 90-100c. This will be like a 20% boost For the 13.5 I would Try 725Mhz. For the 14th I would try somewhere between 725 and 800mhz and check your hw errors and see what runs best once warmed up. If your machines power off and don't reboot unplug the psu for a little bit. That means it drew to much power and the psu went into protect mode so lower the frequency if that happens although I have not had that issues with 8.8v only 8.9v and 9v on the 1600w. |
|
|
|
flagging thread! also running T9+ im prepared to run/test the script and supply logs if it helps
Can you do me a favor and post a copy of your kernal log of you t9+ running so I can see what it's factory settings are. |
|
|
|
I actually installed the firmware on a few different machines and never has the ssh password get changed. I'm not sure what the point would even be for them to change the ssh password... its a piece of cake to change back to stock. My guess is if people are getting the ssh password changed it was a bug.
I'm more concerned about the methodology for pool swapping to mine the dev fee.
Just use my firmware no dev fee and it does the exact same thing. |
|
|
|
|
Show Posts
