BitcoinIntern
|
|
September 03, 2019, 03:49:31 AM Last edit: September 05, 2019, 12:13:28 AM by frodocooper |
|
What are some high efficiency settings for the s9 people are using? Hearing of 10th about 600W is possible.
This would be a game changer. Have you tried this? I did 10025gh and 815 - 825 watts
Not sure anyone can do 600 watts.
What frequency did you use?
|
|
|
|
Behnam fahimi
Newbie
Offline
Activity: 3
Merit: 0
|
|
September 04, 2019, 04:42:46 PM Last edit: September 05, 2019, 12:14:09 AM by frodocooper |
|
hello all dears, I did every thing you said but did not work !! Booting Linux on physical CPU 0x0 Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018 CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Machine model: Xilinx Zynq cma: Reserved 16 MiB at 0x0e000000 Memory policy: Data cache writealloc On node 0 totalpages: 61440 free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000 Normal zone: 480 pages used for memmap Normal zone: 0 pages reserved Normal zone: 61440 pages, LIFO batch:15 percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152 pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096 pcpu-alloc: [0] 0 [0] 1 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960 Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk PID hash table entries: 1024 (order: 0, 4096 bytes) Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 190264K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 39112K reserved, 16384K cma-reserved, 0K highmem) Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0xcf800000 - 0xff800000 ( 768 MB) lowmem : 0xc0000000 - 0xcf000000 ( 240 MB) pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) modules : 0xbf000000 - 0xbfe00000 ( 14 MB) .text : 0xc0008000 - 0xc090c424 (9234 kB) .init : 0xc0a00000 - 0xc0b00000 (1024 kB) .data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB) .bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB) Preemptible hierarchical RCU implementation. Build-time adjustment of leaf fanout to 32. RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2 NR_IRQS:16 nr_irqs:16 16 efuse mapped to cf800000 ps7-slcr mapped to cf802000 L2C: platform modifies aux control register: 0x72360000 -> 0x72760000 L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000 L2C-310 erratum 769419 enabled L2C-310 enabling early BRESP for Cortex-A9 L2C-310 full line of zeros enabled for Cortex-A9 L2C-310 ID prefetch enabled, offset 1 lines L2C-310 dynamic clock gating enabled, standby mode enabled L2C-310 cache controller enabled, 8 ways, 512 kB L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001 zynq_clock_init: clkc starts at cf802100 Zynq clock init sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns Switching to timer-based delay loop, resolution 3ns clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns ps7-ttc #0 at cf80a000, irq=18 Console: colour dummy device 80x30 Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Setting up static identity map for 0x100000 - 0x100058 CPU1: failed to boot: -1 Brought up 1 CPUs SMP: Total of 1 processors activated (666.66 BogoMIPS). CPU: All CPU(s) started in SVC mode. devtmpfs: initialized VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns pinctrl core: initialized pinctrl subsystem NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations cpuidle: using governor menu hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. hw-breakpoint: maximum watchpoint size is 4 bytes. zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000 vgaarb: loaded SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb media: Linux media interface: v0.10 Linux video capture interface: v2.00 pps_core: LinuxPPS API ver. 1 registered pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> PTP clock support registered EDAC MC: Ver: 3.0.0 Advanced Linux Sound Architecture Driver Initialized. clocksource: Switched to clocksource arm_global_timer NET: Registered protocol family 2 TCP established hash table entries: 2048 (order: 1, 8192 bytes) TCP bind hash table entries: 2048 (order: 2, 16384 bytes) TCP: Hash tables configured (established 2048 bind 2048) UDP hash table entries: 256 (order: 1, 8192 bytes) UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. PCI: CLS 0 bytes, default 64 Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (no cpio magic); looks like an initrd Freeing initrd memory: 26072K (cc18b000 - cdb01000) hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available futex hash table entries: 512 (order: 3, 32768 bytes) workingset: timestamp_bits=28 max_order=16 bucket_order=0 jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330 dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16 e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps console [ttyPS0] enabled xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000 [drm] Initialized drm 1.1.0 20060810 brd: module loaded loop: module loaded CAN device driver interface gpiod_set_value: invalid GPIO libphy: MACB_mii_bus: probed macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00) Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1) e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k e1000e: Copyright(c) 1999 - 2015 Intel Corporation. ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-pci: EHCI PCI platform driver usbcore: registered new interface driver usb-storage mousedev: PS/2 mouse device common for all mice i2c /dev entries driver Xilinx Zynq CpuIdle Driver started sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman sdhci-pltfm: SDHCI platform and OF driver helper mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA ledtrig-cpu: registered to indicate activity on CPUs usbcore: registered new interface driver usbhid usbhid: USB HID core driver nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda nand: Micron MT29F2G08ABAGAWP nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128 nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip Bad block table found at page 131008, version 0x01 Bad block table found at page 130944, version 0x01 6 ofpart partitions found on MTD device pl35x-nand Creating 6 MTD partitions on "pl35x-nand": 0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel" 0x000002800000-0x000004800000 : "ramfs" 0x000004800000-0x000005000000 : "configs" 0x000005000000-0x000006000000 : "reserve" 0x000006000000-0x000008000000 : "ramfs-bak" 0x000008000000-0x000010000000 : "reserve1" NET: Registered protocol family 10 sit: IPv6 over IPv4 tunneling driver NET: Registered protocol family 17 can: controller area network core (rev 20120528 abi 9) NET: Registered protocol family 29 can: raw protocol (rev 20120528) can: broadcast manager protocol (rev 20120528 t) can: netlink gateway (rev 20130117) max_hops=1 zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05' zynq_pm_late_init: Unable to map DDRC IO memory. Registering SWP/SWPB emulation handler hctosys: unable to open rtc device (rtc0) ALSA device list: No soundcards found. RAMDISK: gzip image found at block 0 EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) VFS: Mounted root (ext4 filesystem) on device 1:0. devtmpfs: mounted Freeing unused kernel memory: 1024K (c0a00000 - c0b00000) EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr random: dd urandom read with 0 bits of entropy available ubi0: attaching mtd2 ubi0: scanning is finished ubi0: attached mtd2 (name "configs", size 8 MiB) ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096 ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0 ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128 ubi0: max/mean erase counter: 13/5, WL threshold: 4096, image sequence number: 237714726 ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40 ubi0: background thread "ubi_bgt0d" started, PID 708 UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711 UBIFS (ubi0:0): recovery needed UBIFS (ubi0:0): recovery completed UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs" UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs) UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB) UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID FF09433B-E002-4C29-97EC-6220DDC4BB36, small LPT model ubi1: attaching mtd5 ubi1: scanning is finished ubi1: attached mtd5 (name "reserve1", size 128 MiB) ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096 ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0 ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128 ubi1: max/mean erase counter: 115/76, WL threshold: 4096, image sequence number: 914180297 ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36 ubi1: background thread "ubi_bgt1d" started, PID 720 UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723 UBIFS (ubi1:0): recovery needed UBIFS (ubi1:0): recovery completed UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1" UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs) UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB) UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID BCBDE5E0-4C0B-4978-9734-FC58D9F68227, small LPT model IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz macb e000b000.ethernet eth0: link up (100/Full) IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready In axi fpga driver! request_mem_region OK! AXI fpga dev virtual address is 0xcfb38000 *base_vir_addr = 0xab011 In fpga mem driver! request_mem_region OK! fpga mem virtual address is 0xd2000000 2019-08-28 03:19:51 driver-btm-api.c:773:init_freq_mode: This is scan-user version 2019-08-28 03:19:51 driver-btm-api.c:1891:bitmain_soc_init: opt_multi_version = 1 2019-08-28 03:19:51 driver-btm-api.c:1892:bitmain_soc_init: opt_bitmain_ab = 1 2019-08-28 03:19:51 driver-btm-api.c:1893:bitmain_soc_init: opt_bitmain_work_mode = 0 2019-08-28 03:19:51 driver-btm-api.c:1894:bitmain_soc_init: Miner compile time: Mon May 27 10:57:13 CST 2019 type: Antminer S17 2019-08-28 03:19:51 driver-btm-api.c:1895:bitmain_soc_init: commit version: c0bb7cc 2019-05-23 10:59:44, build by: lol 2019-05-27 11:08:02 2019-08-28 03:19:51 driver-btm-api.c:1778:show_sn: no SN got, please write SN to /nvdata/sn 2019-08-28 03:19:51 driver-btm-api.c:1251:miner_device_init: Detect 256MB control board of XILINX 2019-08-28 03:19:51 driver-btm-api.c:1199:init_fan_parameter: fan_eft : 0 fan_pwm : 0 2019-08-28 03:19:51 thread.c:627:create_read_nonce_reg_thread: create thread 2019-08-28 03:19:57 driver-btm-api.c:1183:init_miner_version: miner ID : 8002844815408854 2019-08-28 03:19:57 driver-btm-api.c:1189:init_miner_version: FPGA Version = 0xB011 2019-08-28 03:20:03 driver-btm-api.c:835:get_product_id: product_id[0] = 0 2019-08-28 03:20:03 driver-btm-api.c:835:get_product_id: product_id[1] = 0 2019-08-28 03:20:03 driver-btm-api.c:835:get_product_id: product_id[2] = 0 2019-08-28 03:20:03 driver-btm-api.c:786:_set_project_type: project:0 2019-08-28 03:20:03 driver-btm-api.c:811:_set_project_type: Project type: Antminer S17 Pro 2019-08-28 03:20:03 driver-btm-api.c:822:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101 2019-08-28 03:20:03 driver-btm-api.c:823:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103 2019-08-28 03:20:03 driver-btm-api.c:822:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101 2019-08-28 03:20:03 driver-btm-api.c:823:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103 2019-08-28 03:20:03 driver-btm-api.c:822:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101 2019-08-28 03:20:03 driver-btm-api.c:823:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103 2019-08-28 03:20:05 driver-btm-api.c:1841:bitmain_board_init: Fan check passed. 2019-08-28 03:20:06 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app 2019-08-28 03:20:10 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9 2019-08-28 03:20:12 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app 2019-08-28 03:20:15 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9 2019-08-28 03:20:17 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app 2019-08-28 03:20:20 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9 2019-08-28 03:20:20 thread.c:622:create_pic_heart_beat_thread: create thread 2019-08-28 03:20:20 power_api.c:55:power_init: power init ... 2019-08-28 03:20:20 driver-btm-api.c:1851:bitmain_board_init: Enter 30s sleep to make sure power release finish. 2019-08-28 03:20:20 power_api.c:46:power_off: init gpio907 2019-08-28 03:20:52 power_api.c:164:set_iic_power_to_highest_voltage: setting to voltage: 21.00 ... 2019-08-28 03:20:58 power_api.c:113:set_iic_power_by_voltage: now setting voltage to : 21.000000 2019-08-28 03:21:10 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0 2019-08-28 03:21:22 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0 2019-08-28 03:21:34 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0 2019-08-28 03:21:34 driver-btm-api.c:336:set_order_clock: chain[0]: set order clock, stragegy 3 2019-08-28 03:21:34 driver-btm-api.c:336:set_order_clock: chain[1]: set order clock, stragegy 3 2019-08-28 03:21:34 driver-btm-api.c:336:set_order_clock: chain[2]: set order clock, stragegy 3 2019-08-28 03:21:39 driver-hash-chip.c:453:set_clock_delay_control: core_data = 0x34 2019-08-28 03:21:39 voltage[0] = 1700 2019-08-28 03:21:39 voltage[1] = 1700 2019-08-28 03:21:39 voltage[2] = 1700 2019-08-28 03:21:39 power_api.c:76:set_working_voltage: working_voltage = 17.000000 2019-08-28 03:21:40 temperature.c:188:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry. 2019-08-28 03:21:40 temperature.c:188:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry. 2019-08-28 03:21:40 temperature.c:188:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry. 2019-08-28 03:21:40 temperature.c:188:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry. 2019-08-28 03:21:40 driver-btm-api.c:194:set_miner_status: ERROR_TEMP_LOST_1ST 2019-08-28 03:21:40 driver-btm-api.c:148:stop_mining_and_reboot: stop mining: Re-run cgminer to check temerature sensor type again! 2019-08-28 03:21:40 thread.c:672:cancel_read_nonce_reg_thread: cancel thread 2019-08-28 03:21:40 driver-btm-api.c:121:killall_hashboard: ****power off hashboard**** 2019-08-28 03:21:48 Assert fail!! driver-btm-api.c:153: reboot
|
|
|
|
minefarmbuy
Full Member
Offline
Activity: 1022
Merit: 221
We are not retail.
|
|
September 04, 2019, 05:40:53 PM Last edit: September 05, 2019, 12:14:43 AM by frodocooper |
|
I did 10025gh and 815 - 825 watts
Not sure anyone can do 600 watts.
There's a 3rd party FW that claims they can do 10ths at 600W but they take a 2% fee. Looking to avoid that.
|
|
|
|
yatta
Member
Offline
Activity: 93
Merit: 10
|
|
September 05, 2019, 07:41:40 PM |
|
Hi,
I'm trying to flash dragonmint T1 16TH, but getting error:
Error log: Unsupported miner NAND partitioning
Any chance for it?
|
ETH 0xe3c8d2587e03ac3bdcb86794b8227c000db54d25
|
|
|
Artemis3
Legendary
Offline
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
|
|
September 06, 2019, 03:28:19 PM Last edit: September 07, 2019, 03:05:31 AM by frodocooper |
|
There's a 3rd party FW that claims they can do 10ths at 600W but they take a 2% fee. Looking to avoid that.
There is also cheating firmware with false hashrate claims intended to lure victims into using them... My personal opinion is: if you cannot make it with bOS, its fake. There is no magic mojo, you get asic chips, speed in mhz and voltage, and optionally overt asicboost which has been available to bOS for nearly a year. I believe results such as those reproducible by forum members here, ie. Phillipma's 810W @ 10TH. The other thing is closed software can do things on your back, not necessarily when you are paying attention... They might advertise 2%, only to later do 4%, or overclock your chips every so often (not continuously). And yes they want you to use them, and will make outrageous claims to lure you in. I'd say, stay away from anything not open source. Trust no one.
|
█████████████████████████ ██████████████████████████ ██████████████████████████ ███████████████████████████ | BRAIINS OS+| | AUTOTUNING MINING FIRMWARE| | Increase hashrate on your Bitcoin ASICs, improve efficiency as much as 25%, and get 0% pool fees on Braiins Pool | |
|
|
|
balla69
Newbie
Offline
Activity: 75
Merit: 0
|
|
September 16, 2019, 03:00:49 PM |
|
someone have tested if braiins work on T model?
|
|
|
|
Artemis3
Legendary
Offline
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
|
|
September 16, 2019, 08:07:30 PM |
|
someone have tested if braiins work on T model?
Its tested that it doesn't work. Please wait for future development. With the cgminer replacement (bOSminer), support for new hardware is expected to come.
|
█████████████████████████ ██████████████████████████ ██████████████████████████ ███████████████████████████ | BRAIINS OS+| | AUTOTUNING MINING FIRMWARE| | Increase hashrate on your Bitcoin ASICs, improve efficiency as much as 25%, and get 0% pool fees on Braiins Pool | |
|
|
|
studio_mining
Jr. Member
Offline
Activity: 33
Merit: 10
|
|
September 19, 2019, 09:04:52 PM |
|
Receiving the following error: Last cgminer quit reason: not enough fans Have tried disabling sensors and fans at start with: "no-sensor-scan" : true "min-fans": 0 Will test this machine for immersion so if the fans sensors are broken, don't care. Any ideas how to fix?
|
|
|
|
BitMaxz
Legendary
Offline
Activity: 3416
Merit: 3160
Is the $100k BTC possible?
|
|
September 19, 2019, 10:45:16 PM Last edit: September 21, 2019, 10:25:52 AM by frodocooper |
|
Try to replace the "true" to "false" to disable check. It looks like this "no-sensor-scan" : false "min-fans": 0
min-fans should be zero if you want to skip checking the working fan. If not try to check this changes and new commands from this link below. - Quit when not enough fans are running
|
BTC Road to $80k...
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
September 21, 2019, 08:32:54 AM |
|
Where do I find older images for s9? My miners get hung on rebooting after Upgrade was successful! I never had this issue on older image Here is the log: python3 upgrade2bos.py --no-nand-backup 192.168.1.9 Connecting to remote host... /home/m1/Downloads/braiins/braiins-os_am1-s9_ssh_2019-06-05-0-0de55997/.env/lib/python3.5/site-packages/paramiko/ecdsakey.py:164: CryptographyDeprecationWarning: Support for unsafe construction of public numbers from encoded data will be removed in a future version. Please use EllipticCurvePublicKey.from_encoded_point self.ecdsa_curve.curve_class(), pointinfo /home/m1/Downloads/braiins/braiins-os_am1-s9_ssh_2019-06-05-0-0de55997/.env/lib/python3.5/site-packages/paramiko/client.py:822: UserWarning: Unknown ssh-rsa host key for 192.168.1.9: b'd1b9a53ccf18f8c71135b9d44adf6ad1' key.get_name(), hostname, hexlify(key.get_fingerprint()) Password: Preparing system for backup... Backuping configuration files... Backuping miner NAND... Preparing remote system... Copy ld-musl-armhf.so.1 to /lib/ld-musl-armhf.so.1 Copy sftp-server to /usr/lib/openssh/sftp-server Copy fw_printenv to /usr/sbin/fw_printenv
Uploading firmware... firmware/stage2.tgz: |################################| 17495127/17495127 firmware/u-boot.img: |################################| 573700/573700 firmware/uboot_env.bin: |################################| 131072/131072 firmware/boot.bin: |################################| 79647/79647 firmware/stage1.sh: |################################| 4069/4069 firmware/fit.itb: |################################| 7036220/7036220 firmware/system.bit.gz: |################################| 477812/477812 firmware/uboot_env.config: |################################| 382/382 firmware/CONTROL: |################################| 3081/3081 Upgrading firmware... total 25212 -rw-r--r-- 1 root root 3081 Sep 21 07:51 CONTROL -rw-r--r-- 1 root root 79647 Sep 21 07:51 boot.bin -rw-r--r-- 1 root root 7036220 Sep 21 07:51 fit.itb -rw-r--r-- 1 root root 4069 Sep 21 07:51 stage1.sh -rw-r--r-- 1 root root 17495127 Sep 21 07:51 stage2.tgz -rw-r--r-- 1 root root 477812 Sep 21 07:51 system.bit.gz -rw-r--r-- 1 root root 573700 Sep 21 07:51 u-boot.img -rw-r--r-- 1 root root 131072 Sep 21 07:51 uboot_env.bin -rw-r--r-- 1 root root 382 Sep 21 07:51 uboot_env.config Erasing 128 Kibyte @ 1fe0000 -- 100 % complete Writing U-Boot images with FPGA bitstream... Writing data to block 0 at offset 0x0 Writing data to block 4 at offset 0x80000 Writing data to block 5 at offset 0xa0000 Writing data to block 6 at offset 0xc0000 Writing data to block 7 at offset 0xe0000 Writing data to block 8 at offset 0x100000 Writing data to block 24 at offset 0x300000 Writing data to block 25 at offset 0x320000 Writing data to block 26 at offset 0x340000 Writing data to block 27 at offset 0x360000 Writing U-Boot environment... Writing data to block 56 at offset 0x700000 Writing data to block 57 at offset 0x720000 Erasing 128 Kibyte @ 2ec0000 -- 58 % complete flash_erase: Skipping bad block at 02ee0000 Erasing 128 Kibyte @ 3aa0000 -- 73 % complete flash_erase: Skipping bad block at 03ac0000 Erasing 128 Kibyte @ 4f40000 -- 99 % complete flash_erase: Skipping bad block at 04f60000 flash_erase: Skipping bad block at 04f80000 flash_erase: Skipping bad block at 04fa0000 flash_erase: Skipping bad block at 04fc0000 flash_erase: Skipping bad block at 04fe0000 Erasing 128 Kibyte @ 4fe0000 -- 100 % complete Writing kernel image... Writing data to block 0 at offset 0x0 Writing data to block 1 at offset 0x20000 Writing data to block 2 at offset 0x40000 Writing data to block 3 at offset 0x60000 Writing data to block 4 at offset 0x80000 Writing data to block 5 at offset 0xa0000 Writing data to block 6 at offset 0xc0000 Writing data to block 7 at offset 0xe0000 Writing data to block 8 at offset 0x100000 Writing data to block 9 at offset 0x120000 Writing data to block 10 at offset 0x140000 Writing data to block 11 at offset 0x160000 Writing data to block 12 at offset 0x180000 Writing data to block 13 at offset 0x1a0000 Writing data to block 14 at offset 0x1c0000 Writing data to block 15 at offset 0x1e0000 Writing data to block 16 at offset 0x200000 Writing data to block 17 at offset 0x220000 Writing data to block 18 at offset 0x240000 Writing data to block 19 at offset 0x260000 Writing data to block 20 at offset 0x280000 Writing data to block 21 at offset 0x2a0000 Writing data to block 22 at offset 0x2c0000 Writing data to block 23 at offset 0x2e0000 Writing data to block 24 at offset 0x300000 Writing data to block 25 at offset 0x320000 Writing data to block 26 at offset 0x340000 Writing data to block 27 at offset 0x360000 Writing data to block 28 at offset 0x380000 Writing data to block 29 at offset 0x3a0000 Writing data to block 30 at offset 0x3c0000 Writing data to block 31 at offset 0x3e0000 Writing data to block 32 at offset 0x400000 Writing data to block 33 at offset 0x420000 Writing data to block 34 at offset 0x440000 Writing data to block 35 at offset 0x460000 Writing data to block 36 at offset 0x480000 Writing data to block 37 at offset 0x4a0000 Writing data to block 38 at offset 0x4c0000 Writing data to block 39 at offset 0x4e0000 Writing data to block 40 at offset 0x500000 Writing data to block 41 at offset 0x520000 Writing data to block 42 at offset 0x540000 Writing data to block 43 at offset 0x560000 Writing data to block 44 at offset 0x580000 Writing data to block 45 at offset 0x5a0000 Writing data to block 46 at offset 0x5c0000 Writing data to block 47 at offset 0x5e0000 Writing data to block 48 at offset 0x600000 Writing data to block 49 at offset 0x620000 Writing data to block 50 at offset 0x640000 Writing data to block 51 at offset 0x660000 Writing data to block 52 at offset 0x680000 Writing data to block 53 at offset 0x6a0000 Writing stage2 tarball... Writing data to block 80 at offset 0xa00000 Writing data to block 81 at offset 0xa20000 Writing data to block 82 at offset 0xa40000 Writing data to block 83 at offset 0xa60000 Writing data to block 84 at offset 0xa80000 Writing data to block 85 at offset 0xaa0000 Writing data to block 86 at offset 0xac0000 Writing data to block 87 at offset 0xae0000 Writing data to block 88 at offset 0xb00000 Writing data to block 89 at offset 0xb20000 Writing data to block 90 at offset 0xb40000 Writing data to block 91 at offset 0xb60000 Writing data to block 92 at offset 0xb80000 Writing data to block 93 at offset 0xba0000 Writing data to block 94 at offset 0xbc0000 Writing data to block 95 at offset 0xbe0000 Writing data to block 96 at offset 0xc00000 Writing data to block 97 at offset 0xc20000 Writing data to block 98 at offset 0xc40000 Writing data to block 99 at offset 0xc60000 Writing data to block 100 at offset 0xc80000 Writing data to block 101 at offset 0xca0000 Writing data to block 102 at offset 0xcc0000 Writing data to block 103 at offset 0xce0000 Writing data to block 104 at offset 0xd00000 Writing data to block 105 at offset 0xd20000 Writing data to block 106 at offset 0xd40000 Writing data to block 107 at offset 0xd60000 Writing data to block 108 at offset 0xd80000 Writing data to block 109 at offset 0xda0000 Writing data to block 110 at offset 0xdc0000 Writing data to block 111 at offset 0xde0000 Writing data to block 112 at offset 0xe00000 Writing data to block 113 at offset 0xe20000 Writing data to block 114 at offset 0xe40000 Writing data to block 115 at offset 0xe60000 Writing data to block 116 at offset 0xe80000 Writing data to block 117 at offset 0xea0000 Writing data to block 118 at offset 0xec0000 Writing data to block 119 at offset 0xee0000 Writing data to block 120 at offset 0xf00000 Writing data to block 121 at offset 0xf20000 Writing data to block 122 at offset 0xf40000 Writing data to block 123 at offset 0xf60000 Writing data to block 124 at offset 0xf80000 Writing data to block 125 at offset 0xfa0000 Writing data to block 126 at offset 0xfc0000 Writing data to block 127 at offset 0xfe0000 Writing data to block 128 at offset 0x1000000 Writing data to block 129 at offset 0x1020000 Writing data to block 130 at offset 0x1040000 Writing data to block 131 at offset 0x1060000 Writing data to block 132 at offset 0x1080000 Writing data to block 133 at offset 0x10a0000 Writing data to block 134 at offset 0x10c0000 Writing data to block 135 at offset 0x10e0000 Writing data to block 136 at offset 0x1100000 Writing data to block 137 at offset 0x1120000 Writing data to block 138 at offset 0x1140000 Writing data to block 139 at offset 0x1160000 Writing data to block 140 at offset 0x1180000 Writing data to block 141 at offset 0x11a0000 Writing data to block 142 at offset 0x11c0000 Writing data to block 143 at offset 0x11e0000 Writing data to block 144 at offset 0x1200000 Writing data to block 145 at offset 0x1220000 Writing data to block 146 at offset 0x1240000 Writing data to block 147 at offset 0x1260000 Writing data to block 148 at offset 0x1280000 Writing data to block 149 at offset 0x12a0000 Writing data to block 150 at offset 0x12c0000 Writing data to block 151 at offset 0x12e0000 Writing data to block 152 at offset 0x1300000 Writing data to block 153 at offset 0x1320000 Writing data to block 154 at offset 0x1340000 Writing data to block 155 at offset 0x1360000 Writing data to block 156 at offset 0x1380000 Writing data to block 157 at offset 0x13a0000 Writing data to block 158 at offset 0x13c0000 Writing data to block 159 at offset 0x13e0000 Writing data to block 160 at offset 0x1400000 Writing data to block 161 at offset 0x1420000 Writing data to block 162 at offset 0x1440000 Writing data to block 163 at offset 0x1460000 Writing data to block 164 at offset 0x1480000 Writing data to block 165 at offset 0x14a0000 Writing data to block 166 at offset 0x14c0000 Writing data to block 167 at offset 0x14e0000 Writing data to block 168 at offset 0x1500000 Writing data to block 169 at offset 0x1520000 Writing data to block 170 at offset 0x1540000 Writing data to block 171 at offset 0x1560000 Writing data to block 172 at offset 0x1580000 Writing data to block 173 at offset 0x15a0000 Writing data to block 174 at offset 0x15c0000 Writing data to block 175 at offset 0x15e0000 Writing data to block 176 at offset 0x1600000 Writing data to block 177 at offset 0x1620000 Writing data to block 178 at offset 0x1640000 Writing data to block 179 at offset 0x1660000 Writing data to block 180 at offset 0x1680000 Writing data to block 181 at offset 0x16a0000 Writing data to block 182 at offset 0x16c0000 Writing data to block 183 at offset 0x16e0000 Writing data to block 184 at offset 0x1700000 Writing data to block 185 at offset 0x1720000 Writing data to block 186 at offset 0x1740000 Writing data to block 187 at offset 0x1760000 Writing data to block 188 at offset 0x1780000 Writing data to block 189 at offset 0x17a0000 Writing data to block 190 at offset 0x17c0000 Writing data to block 191 at offset 0x17e0000 Writing data to block 192 at offset 0x1800000 Writing data to block 193 at offset 0x1820000 Writing data to block 194 at offset 0x1840000 Writing data to block 195 at offset 0x1860000 Writing data to block 196 at offset 0x1880000 Writing data to block 197 at offset 0x18a0000 Writing data to block 198 at offset 0x18c0000 Writing data to block 199 at offset 0x18e0000 Writing data to block 200 at offset 0x1900000 Writing data to block 201 at offset 0x1920000 Writing data to block 202 at offset 0x1940000 Writing data to block 203 at offset 0x1960000 Writing data to block 204 at offset 0x1980000 Writing data to block 205 at offset 0x19a0000 Writing data to block 206 at offset 0x19c0000 Writing data to block 207 at offset 0x19e0000 Writing data to block 208 at offset 0x1a00000 Writing data to block 209 at offset 0x1a20000 Writing data to block 210 at offset 0x1a40000 Writing data to block 211 at offset 0x1a60000 Writing data to block 212 at offset 0x1a80000 Writing data to block 213 at offset 0x1aa0000 U-Boot configuration...
Content of U-Boot configuration: miner_pool_host=stratum+tcp://stratum.slushpool.com miner_pool_port=3333 miner_pool_user=!non-existent-user! load_addr=0x2000000 fdt_high=0x7FFFFFF initrd_high=0x7FFFFFF bitstream_addr=0x2100000 bootenv=uEnv.txt set_bootargs=setenv bootargs console=ttyPS0,115200 root=/dev/ram0 r rootfstype=squashfs ${mtdparts} earlyprintk uenv_load=load mmc 0 ${load_addr} ${bootenv} && echo Loaded environment from ${bootenv} && env import -t ${load_addr} ${filesize} load_fpga=nand read ${load_addr} ${bitstream_off} ${bitstream_size} && unzip ${load_addr} ${bitstream_addr} && fpga loadb 0 ${bitstream_addr} ${bitstream_size} nandboot=echo Copying FIT from NAND flash to RAM... && run uenv_load; test x${sd_boot} = xyes && run sdboot; run set_bootargs && run load_fpga && nand read ${load_addr} ${kernel_off} ${kernel_size} && bootm ${load_addr} sdboot=echo Copying FIT from SD to RAM... && run set_bootargs && run uenv_load; load mmc 0 ${load_addr} fit.itb && bootm ${load_addr} mtdids=nand0=pl35x-nand mtdparts=mtdparts=pl35x-nand:512k(boot),2560k(uboot),2m(fpga1),2m(fpga2),512k(uboot_env),512k(miner_cfg),22m(recovery),95m(firmware1),95m(firmware2) bootcmd=run $modeboot bitstream_off=0x300000 bitstream_size=0x74a74 kernel_off=0xB000000 kernel_size=0x6b5d3c stage2_off=0x3D00000 stage2_size=0x10af457 stage2_mtd=8 ethaddr=08:7d:20:56:db:72 miner_hwid=e6CrehyC3cSvWqql miner_freq=550 miner_voltage=0706 Upgrade was successful! Rebooting...
|
|
|
|
BitMaxz
Legendary
Offline
Activity: 3416
Merit: 3160
Is the $100k BTC possible?
|
|
September 21, 2019, 11:49:00 PM |
|
Where do I find older images for s9?
Check this link for old image for Braiins OS below. - https://github.com/braiins/braiins/releasesOr you can check this one. https://feeds.braiins-os.org/In the feeds page, they mostly removed older than June 2019 firmware image.
|
BTC Road to $80k...
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
September 22, 2019, 06:03:17 PM Last edit: September 23, 2019, 09:35:28 AM by frodocooper |
|
Thanks Already checked those before asking, GitHub only has source code and no specific images and feed only has the latest.
So after an unsuccessful attempt I boot from sd card. Flashing to nand goes ok and it gives the successful message to change jumpers and reboot, but it wont boot, just keeps rebooting. Tried to restore to factory and gave me this error: Could not open mtd device: BOOT.bin-env-dts-kernel Can't open device for writing! full restore log: python3 restore2factory.py --factory-image Antminer-S9j-all-201811071118-autofreq-user-Update2UBI-NF.tar.gz 192.168.1.180 Connecting to remote host... /home/payam/Desktop/braiins/braiins-os_am1-s9_ssh_2019-06-05-0-0de55997/.env/lib/python3.6/site-packages/paramiko/ecdsakey.py:164: CryptographyDeprecationWarning: Support for unsafe construction of public numbers from encoded data will be removed in a future version. Please use EllipticCurvePublicKey.from_encoded_point self.ecdsa_curve.curve_class(), pointinfo Password: Detected bOS mode: sd Creating configuration files... Uploading firmware... Skipping 'c5/soc_system.rbf' Skipping 'c5/upgrade-marker.bin' Skipping 'c5/angstrom_rootfs.jffs2' Skipping 'runme.sh' Skipping 'ubi_info' rootfs.jffs2: |################################| 48889856/48889856 upgrade-marker.bin: |################################| 16/16 devicetree.dtb: |################################| 7631/7631 BOOT.bin: |################################| 2559872/2559872 uImage: |################################| 3799480/3799480 Uploading restore scripts... /tmp/tmpvab5fhbe/config.tar.gz: |################################| 253/253 upgrade/restore.sh: |################################| 1305/1305 Restoring firmware... Could not open mtd device: BOOT.bin-env-dts-kernel Can't open device for writing!
Any helps would be much appreciated.
|
|
|
|
Artemis3
Legendary
Offline
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
|
|
September 22, 2019, 07:03:38 PM |
|
So after an unsuccessful attempt I boot from sd card. Flashing to nand goes ok and it gives the successful message to change jumpers and reboot, but it wont boot, just keeps rebooting.
Any helps would be much appreciated
Then try with the "official" method which involves flashing to the T9+ firmware (that's Bitmain "quality" support) and then enter the ui of that to "upgrade" to the actual S9 firmware of theirs (2017 or 2018 should work). If that also doesn't cure it, you might have a damaged nand, and you will be forced to either replace the controller, or permanently use an sd card with bOS in it.
BTW Just looking at the feeds page i spotted a newer experimental bOSminer version... There are no release notes of this 14th September "bosminer preview" release and i don't know if people should upgrade to it, perhaps waiting for release details would be prudent. bOSminer is probably not feature complete at this point, they were saying by the beginning of next year it would be ready... bosminer is a cgminer replacement written in rust language.
|
█████████████████████████ ██████████████████████████ ██████████████████████████ ███████████████████████████ | BRAIINS OS+| | AUTOTUNING MINING FIRMWARE| | Increase hashrate on your Bitcoin ASICs, improve efficiency as much as 25%, and get 0% pool fees on Braiins Pool | |
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
September 22, 2019, 07:19:16 PM Last edit: September 23, 2019, 09:36:18 AM by frodocooper |
|
[...]
Thanks a lot, will try it out.
So just like others it shows no errors, green and red light start blinking, but no ip after reboot. Looks like sd card is the way to go ...
|
|
|
|
an7h
Newbie
Offline
Activity: 12
Merit: 0
|
|
September 23, 2019, 09:59:41 AM |
|
Will Braiins OS work with newer Antminer S9k revisions?
|
|
|
|
Artemis3
Legendary
Offline
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
|
|
September 23, 2019, 03:22:42 PM Merited by frodocooper (3) |
|
It turns out there is some little bit of information about this September (bOSminer) release: The project is intended as a replacement for the existing cgminer software. However, it has been designed from scratch and written in a more modern Rust programming language. bOSminer natively supports Stratum V2 and can be used in combination with V2->V1 mining proxy. Currently, the project is early preview stage. Its Antminer S9 provides the following features: - AsicBoost
- clock speed is fixed @ 650 MHz which results in ~ 4.6 Th/s per hashboard
- only single hashboard is currently supported
- fans run @ 100% speed (can be lowered by set_fans.sh tool)
Further Work Below is a list of domains that are to be implemented in the MVP phase of the project: - cgminer compatible API
- fan control
- clock and voltage configuration
As you can see its a work in progress, unless you want to play with a single board S9 fixed at 650 MHz, don't bother downloading it. Oh yes, interestingly they also have a mining proxy also made in rust, but its meant to translate V2 to V1. My guess is they intend miners to use this within their LAN for regular pools. To reiterate: do not use this unless you want to help test development using a single S9 hash board fixed at 650mhz...
Will Braiins OS work with newer Antminer S9k revisions? After they finish bOSminer (First stable release expected in the beginning of next year), they plan to add support for more hardware. I don't really know if current bOS works there, i don't think so due to the different controller like the hydro etc.
|
█████████████████████████ ██████████████████████████ ██████████████████████████ ███████████████████████████ | BRAIINS OS+| | AUTOTUNING MINING FIRMWARE| | Increase hashrate on your Bitcoin ASICs, improve efficiency as much as 25%, and get 0% pool fees on Braiins Pool | |
|
|
|
minefarmbuy
Full Member
Offline
Activity: 1022
Merit: 221
We are not retail.
|
|
September 24, 2019, 12:39:56 PM |
|
What's the low down with braiins and core scientific?
|
|
|
|
taserz
Sr. Member
Offline
Activity: 800
Merit: 294
Created AutoTune to saved the planet! ~USA
|
|
September 24, 2019, 04:41:18 PM |
|
What's the low down with braiins and core scientific?
Word on the street is they are using mineority app for deployment...
|
|
|
|
Freemine-001010
Member
Offline
Activity: 139
Merit: 46
|
|
October 03, 2019, 10:49:19 PM |
|
so just flashed braiins os , i can ssh in but cant get to the web interface,
can anyone advise me of what to do, at the moment the control board is not in the miner as i was flashing it , booted from sd , ran the ssh install command , completed still cant get into it from browser, i can ping it and ssh ,
are there some commands i can run and post the results to get a better understanding why it wont let me in, this is my 6th miner flashing braiins , all the other 5 were able to boot and access through browser, using the same image
|
|
|
|
Artemis3
Legendary
Offline
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
|
|
October 04, 2019, 09:59:28 PM |
|
so just flashed braiins os , i can ssh in but cant get to the web interface,
can anyone advise me of what to do, at the moment the control board is not in the miner as i was flashing it , booted from sd , ran the ssh install command , completed still cant get into it from browser, i can ping it and ssh ,
are there some commands i can run and post the results to get a better understanding why it wont let me in, this is my 6th miner flashing braiins , all the other 5 were able to boot and access through browser, using the same image
But can you boot using the sd fine there? Then there could be a problem flashing into nand. You can try flashing it again, or revert the nand to factory firmware and see if its still working normally (the nand). Normally you don't have to do anything else. And you can install into nand using the Web UI, but your command is supposed to do the exact same thing. Try force reinstalling the package firmware (opkg update ; opkg install --force-reinstall firmware) and see if that makes any difference. "Removing" the firmware package should in theory reset it as well (you will find its reinstalled with reset values). Is this an s9j ? Some of those are exhibiting issues when flashing into nand, but work perfectly fine using the sd card. You don't have to flash into nand to use bOS, you can always let it run from SD.
|
█████████████████████████ ██████████████████████████ ██████████████████████████ ███████████████████████████ | BRAIINS OS+| | AUTOTUNING MINING FIRMWARE| | Increase hashrate on your Bitcoin ASICs, improve efficiency as much as 25%, and get 0% pool fees on Braiins Pool | |
|
|
|
|