Braiins OS & Braiins OS+ custom ASIC firmware: optimize performance & efficiency - page 19.

studio_mining

jr. member

Activity: 33

Merit: 10

Receiving the following error:

Code:

Last cgminer quit reason: not enough fans

Have tried disabling sensors and fans at start with:

Code:

"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?

Artemis3

legendary

Activity: 2030

Merit: 1569

CLEAN non GPL infringing code made in Rust lang

Quote from: balla69 on September 16, 2019, 10:00:49 AM

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.

balla69

newbie

Activity: 75

Merit: 0

someone have tested if braiins work on T model?

Artemis3

legendary

Activity: 2030

Merit: 1569

CLEAN non GPL infringing code made in Rust lang

Quote from: minefarmbuy on September 04, 2019, 12:40:53 PM

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.

yatta

member

Activity: 93

Merit: 10

Hi,

I'm trying to flash dragonmint T1 16TH, but getting error:

Error log:
Unsupported miner NAND partitioning

Any chance for it?

minefarmbuy

full member

Activity: 1022

Merit: 221

We are not retail.

Quote from: philipma1957 on August 31, 2019, 08:05:09 AM

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.

Behnam fahimi

newbie

Activity: 3

Merit: 0

hello all dears,
I did every thing you said but did not work !!

Code:

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
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

BitcoinIntern

full member

Activity: 210

Merit: 100

Quote from: minefarmbuy on August 30, 2019, 09:07:51 AM

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?

Quote from: philipma1957 on August 31, 2019, 08:05:09 AM

I did 10025gh and 815 - 825 watts

Not sure anyone can do 600 watts.

What frequency did you use?

BitMaxz

legendary

Activity: 3374

Merit: 3095

BTC price road to $80k

Quote from: Behnam fahimi on August 31, 2019, 01:45:47 AM

Code:

"--no-sensor-scan": true,

As I said above this code will not work you need to replace it with this below

Code:

"no-sensor-scan" : true

This is already been discussed here check this post: https://bitcointalk.org/index.php?topic=5036844.380

philipma1957

legendary

Activity: 4256

Merit: 8551

'The right to privacy matters'

Quote from: minefarmbuy on August 30, 2019, 09:07:51 AM

What are some high efficiency settings for the s9 people are using? Hearing of 10th about 600W is possible.

I did 10025gh and 815 - 825 watts

Not sure anyone can do 600 watts.

Behnam fahimi

newbie

Activity: 3

Merit: 0

hello all dears,
I did every thing you said but did not work !!

here is the code i used :

Code:

cgminer.conf
***************************
"api-listen" : true,
"api-network" : true,
"api-groups" : "A:stats:pools:devs:summary:version",
"api-allow" : "A:0/0,W:*",
"--no-sensor-scan": true,
"bitmain-use-vil" : true,
"bitmain-work-mode" : "0",
"bitmain-freq" : "O",
"bitmain-voltage" : "1900"
*************************************

2019-08-31 06:41:17 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 21.167373
2019-08-31 06:41:18 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.136758
2019-08-31 06:41:20 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 21.228603
2019-08-31 06:41:20 power_api.c:50:_get_avg_voltage: average_voltage = 21.177578
2019-08-31 06:41:20 power_api.c:68:check_voltage: target_vol = 21.00, actural_vol = 21.18, check voltage passed.
2019-08-31 06:41:20 uart.c:71:set_baud: set fpga_baud to 115200
2019-08-31 06:41:20 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2019-08-31 06:41:20 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2019-08-31 06:41:20 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2019-08-31 06:41:33 driver-btm-api.c:1111:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
2019-08-31 06:41:45 driver-btm-api.c:1111:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2019-08-31 06:41:56 driver-btm-api.c:1111:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2019-08-31 06:42:01 driver-btm-api.c:333:set_order_clock: chain[0]: set order clock, stragegy 3
2019-08-31 06:42:02 driver-btm-api.c:333:set_order_clock: chain[1]: set order clock, stragegy 3
2019-08-31 06:42:02 driver-btm-api.c:333:set_order_clock: chain[2]: set order clock, stragegy 3
2019-08-31 06:42:02 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0x34
2019-08-31 06:42:02 voltage[0] = 1700
2019-08-31 06:42:02 voltage[1] = 1700
2019-08-31 06:42:02 voltage[2] = 1700
2019-08-31 06:42:02 power_api.c:214:set_working_voltage_raw: working_voltage_raw = 1700
2019-08-31 06:42:03 temperature.c:202:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-31 06:42:03 temperature.c:202:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-31 06:42:03 temperature.c:202:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-31 06:42:03 temperature.c:202:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-31 06:42:03 driver-btm-api.c:191:set_miner_status: ERROR_TEMP_LOST_1ST
2019-08-31 06:42:03 driver-btm-api.c:145:stop_mining_and_reboot: stop mining: Re-run cgminer to check temerature sensor type again!
2019-08-31 06:42:03 thread.c:698:cancel_read_nonce_reg_thread: cancel thread
2019-08-31 06:42:03 driver-btm-api.c:118:killall_hashboard: ****power off hashboard****
2019-08-31 06:42:08

 Assert fail!! driver-btm-api.c:150: reboot

minefarmbuy

full member

Activity: 1022

Merit: 221

We are not retail.

What are some high efficiency settings for the s9 people are using? Hearing of 10th about 600W is possible.

BitMaxz

legendary

Activity: 3374

Merit: 3095

BTC price road to $80k

Replace it with this code below:

Code:

"no-sensor-scan" : true

Just remove the Bitmain from your code under cgminer.conf

Another sample below add this.

Code:

"no-sensor-scan" : true
"fan-mode" : "speed"
"fan-speed" : "95"

Let me know if it works or not.

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: Behnam fahimi on August 28, 2019, 05:08:49 AM

i added (( "bitmain-no-sensor-scan" : true , )) to cgminer.conf but temp sensor still has error .
i want the system to ignore temperature error of specific Chain .
please help

this is error log :
2019-08-28 09:03:44 temperature.c:188:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-28 09:03:44 temperature.c:188:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-28 09:03:44 driver-btm-api.c:189:set_miner_status: ERROR_TEMP_LOST_1ST
2019-08-28 09:03:44 driver-btm-api.c:143:stop_mining_and_reboot: stop mining: Re-run cgminer to check temerature sensor type again!

if it's the last config no "," after it
And it should be --no-sensor-scan not what you used as below

Code:

"--no-sensor-scan":true

Behnam fahimi

newbie

Activity: 3

Merit: 0

i added (( "bitmain-no-sensor-scan" : true , )) to cgminer.conf but temp sensor still has error .
i want the system to ignore temperature error of specific Chain .
please help

this is error log :
2019-08-28 09:03:44 temperature.c:188:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-28 09:03:44 temperature.c:188:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry.
2019-08-28 09:03:44 driver-btm-api.c:189:set_miner_status: ERROR_TEMP_LOST_1ST
2019-08-28 09:03:44 driver-btm-api.c:143:stop_mining_and_reboot: stop mining: Re-run cgminer to check temerature sensor type again!

Artemis3

legendary

Activity: 2030

Merit: 1569

CLEAN non GPL infringing code made in Rust lang

Well Philipma here did 7.8volts at 475 mhz, so i think you should be able to do better, either increase speed while keeping that voltage, or lower that voltage by keeping that speed until the hashrate values (ideal / actual) differ too much.

Shad0wSmurf

jr. member

Activity: 59

Merit: 10

Quote from: percy_tc on August 24, 2019, 10:49:43 AM

With Braiins OS, is there 100% fan speed upon start?

Is itpossible to downCLOCK miner, to be able to use it in home envirmonet (noise issues)?

Thanks

8.3volts, 450 mhz, auto fan. start up is abi***, but it levels out

Artemis3

legendary

Activity: 2030

Merit: 1569

CLEAN non GPL infringing code made in Rust lang

Quote from: percy_tc on August 24, 2019, 10:49:43 AM

With Braiins OS, is there 100% fan speed upon start?

Is itpossible to downCLOCK miner, to be able to use it in home envirmonet (noise issues)?

Thanks

Yes, when you turn it on because the firmware isn't controlling anything yet. After it boots it can slow down the speeds. If you downclock the hashboards it will naturally slowdown the fans. You can also force it but you have to be very careful to not overheat the unit.

Another trick is reduce the number of hashboards, 2 or 1 need less air than 3.

percy_tc

full member

Activity: 583

Merit: 106

With Braiins OS, is there 100% fan speed upon start?

Is itpossible to downCLOCK miner, to be able to use it in home envirmonet (noise issues)?

Thanks

balla69

newbie

Activity: 75

Merit: 0

yes, I think I have waited too little after each reboot ...... and given too much importance to errors.
I was wondering why with the default values, instead of about 625-6 Mhz on all 3 with bitmain, it starts with values like 631-658-675, I thought that maybe the firmware increases the frequencies of the best cards .... but it is strange ..... because the order is always similar (the first the worst and the last the best, strange not?).
ckpool results should coincide with the actual hashrate no? maybe after 1 hour of mining ...

Questions:
the default configuration of braiins set the frequency different for every card, Is this difference good to maintain to optimize mining?

Topic: Braiins OS & Braiins OS+ custom ASIC firmware: optimize performance & efficiency - page 19. (Read 45351 times)