Can you please put the voltage in the status section? It's hard to calculate efficiency with that missing in the status area.
Thanks.
Topic: Antminer D3 Blissz firmware (10/12 v1.12 update) - page 14. (Read 125923 times)
blissz can you add option to easily change pool priority like in one or two clicks?
Exactly, I been suggesting this useful feature already long time a go
(page 21)We have poll on top of the page and auto tune will be the feature I wish to see first.
Also one more option I believe will save everyone some frustration when comes to the pools.
I think very handy will be option to setup priority instead of rewriting or copy/paste all pool details when want to change them, something like iBeLink have. I find this very useful
Also one more option I believe will save everyone some frustration when comes to the pools.
I think very handy will be option to setup priority instead of rewriting or copy/paste all pool details when want to change them, something like iBeLink have. I find this very useful
thx not really payed attention on that poll thought it was some kind of survey poll, and following this tread after page 80 not really read anything poster before that
Thats fine, don't worry about that poll. I quote my post regarding that pool switching possibilities which I mentioned there after that poll info
Just saying, will be realy good have some kind of pool management available.
blissz can you add option to easily change pool priority like in one or two clicks?
Exactly, I been suggesting this useful feature already long time a go
(page 21)We have poll on top of the page and auto tune will be the feature I wish to see first.
Also one more option I believe will save everyone some frustration when comes to the pools.
I think very handy will be option to setup priority instead of rewriting or copy/paste all pool details when want to change them, something like iBeLink have. I find this very useful
Also one more option I believe will save everyone some frustration when comes to the pools.
I think very handy will be option to setup priority instead of rewriting or copy/paste all pool details when want to change them, something like iBeLink have. I find this very useful
thx not really payed attention on that poll thought it was some kind of survey poll, and following this tread after page 80 not really read anything poster before that
blissz can you add option to easily change pool priority like in one or two clicks?
Exactly, I been suggesting this useful feature already long time a go
(page 21)We have poll on top of the page and auto tune will be the feature I wish to see first.
Also one more option I believe will save everyone some frustration when comes to the pools.
I think very handy will be option to setup priority instead of rewriting or copy/paste all pool details when want to change them, something like iBeLink have. I find this very useful
Also one more option I believe will save everyone some frustration when comes to the pools.
I think very handy will be option to setup priority instead of rewriting or copy/paste all pool details when want to change them, something like iBeLink have. I find this very useful
blissz can you add option to easily change pool priority like in one or two clicks?
any idea why this is happening?
https://i.imgur.com/Dx30uIw.jpg
my d3 ran for 24 hours @ 500 freq without hw errors or reboots, but still that chart looks insane and doesnt make any sense...
https://i.imgur.com/dFOOd6h.jpg
any idea?
After this update for my D3 September Batch i did those confs:
Manual fan: 45%
Frequency: 475M
ASIC Voltage: Lowest
And i have a HW of 7384 in last 1hr
is this ok?
Manual fan: 45%
Frequency: 475M
ASIC Voltage: Lowest
And i have a HW of 7384 in last 1hr
is this ok?
i would say its definitely not ok.
7384 per hour is to much...
actually i also working with the lowest voltage and i can run my d3's only with 400Mhz and one or two chains with 406Mhz with nearly no error 24/7, but thats it.
and i just want that these are living long and with that much hw errors i think they will not
After this update for my D3 September Batch i did those confs:
Manual fan: 45%
Frequency: 475M
ASIC Voltage: Lowest
And i have a HW of 7384 in last 1hr
is this ok?
Manual fan: 45%
Frequency: 475M
ASIC Voltage: Lowest
And i have a HW of 7384 in last 1hr
is this ok?
Like blissz mentioned, there is some amount of normal fluctuation in difficulty that will cause low points and spikes in the hashrate chart. Your chart, however, looks more extreme to me. It looks like your miners might be constantly restarting. The first 3/4 of the chart is mostly normal, but the last part (where the hashrate is bouncing between 0 and a high number) looks like something is wrong.
I'd check the status page on your firmware to see how long they've been running. If the time is low, then they're probably rebooting.
v2.04 beta :: 22/12 :: test version
Download:
https://mega.nz/#!ulYlTB4D!nEymzPvujO17EXa95q9_oRHAQOxZUZvxu_bulZ8_wUA
Changes 22/12:
- reboots the D3 on high temperatures (> 85 deg PCB temp). This feature will save your unit in case your fans will fail.
- improved auto tune algorithm stability
- Increased the chip starting frequency of the autotune algorithm for higher voltages.
Changes 14/12:
- fixed auto recover from xxxx
- cleaned up kernel logging
- a bit more aggressive tuning
- tunes down faster now when too many HW errors are detected
Changes 13/12:
- Totally rewritten code base, based from latest available bitmain / cgminer sources
- ASIC's now automatically recovers from xxxxx errors without restarting (The auto reboot options are still in there in case it doesn't succeed)
- blazing fast mining status overview in the webinterface
- as requested: the dev mining starts later now (after 5 minutes)
- as requested: dev pools status is now visible in the miner status
Important: The autotune feature is not completely finished and the startup is a bit slow now.. Therefore I need your help. So what do you need to do:
set your advanced settings the same as displayed bellow
let it run for at least 20 minutes
PM your (complete) kernel log
By doing so I can get to a conclusion what the starting frequency of the auto tune algorithm should be.
In case you want to help more: increase the voltage a bit and do the steps above again as it will give some more information
Thank you!
https://img15.hostingpics.net/pics/453940Untitled.jpg
Download:
https://mega.nz/#!ulYlTB4D!nEymzPvujO17EXa95q9_oRHAQOxZUZvxu_bulZ8_wUA
Changes 22/12:
- reboots the D3 on high temperatures (> 85 deg PCB temp). This feature will save your unit in case your fans will fail.
- improved auto tune algorithm stability
- Increased the chip starting frequency of the autotune algorithm for higher voltages.
Changes 14/12:
- fixed auto recover from xxxx
- cleaned up kernel logging
- a bit more aggressive tuning
- tunes down faster now when too many HW errors are detected
Changes 13/12:
- Totally rewritten code base, based from latest available bitmain / cgminer sources
- ASIC's now automatically recovers from xxxxx errors without restarting (The auto reboot options are still in there in case it doesn't succeed)
- blazing fast mining status overview in the webinterface
- as requested: the dev mining starts later now (after 5 minutes)
- as requested: dev pools status is now visible in the miner status
Important: The autotune feature is not completely finished and the startup is a bit slow now.. Therefore I need your help. So what do you need to do:
set your advanced settings the same as displayed bellow
let it run for at least 20 minutes
PM your (complete) kernel log
By doing so I can get to a conclusion what the starting frequency of the auto tune algorithm should be.
In case you want to help more: increase the voltage a bit and do the steps above again as it will give some more information
Thank you!
https://img15.hostingpics.net/pics/453940Untitled.jpg
Here is my log if it helps
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.8.13 (xxl@armdev01) (gcc version 4.7.4 20130626 (prerelease) (Linaro GCC 4.7-2013.07) ) #22 SMP Tue Dec 2 15:26:11 CST 2014
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=50c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: Generic AM33XX (Flattened Device Tree), model: TI AM335x BeagleBone
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] On node 0 totalpages: 65280
[ 0.000000] free_area_init_node: node 0, pgdat c06cb100, node_mem_map c0726000
[ 0.000000] Normal zone: 512 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 64768 pages, LIFO batch:15
[ 0.000000] AM335X ES1.0 (neon )
[ 0.000000] PERCPU: Embedded 8 pages/cpu @c0933000 s9408 r8192 d15168 u32768
[ 0.000000] pcpu-alloc: s9408 r8192 d15168 u32768 alloc=8*4096
[ 0.000000] pcpu-alloc:
- 0
[ 0.000000] Kernel command line: console=ttyO0,115200n8 init=/sbin/init
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] __ex_table already sorted, skipping sort
[ 0.000000] allocated 524288 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] Memory: 255MB = 255MB total
[ 0.000000] Memory: 238536k/238536k available, 23608k 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 : 0xd0800000 - 0xff000000 ( 744 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf800000 - 0xbfe00000 ( 6 MB)
[ 0.000000] .text : 0xc0008000 - 0xc0612cf0 (6188 kB)
[ 0.000000] .init : 0xc0613000 - 0xc06554c0 ( 266 kB)
[ 0.000000] .data : 0xc0656000 - 0xc06cc020 ( 473 kB)
[ 0.000000] .bss : 0xc06cc020 - 0xc0725e3c ( 360 kB)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[ 0.000000] Total of 128 interrupts on 1 active controller
[ 0.000000] OMAP clockevent source: GPTIMER1 at 24000000 Hz
[ 0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[ 0.000000] OMAP clocksource: GPTIMER2 at 24000000 Hz
[ 0.000000] Console: colour dummy device 80x30
[ 0.000356] Calibrating delay loop... 545.07 BogoMIPS (lpj=531968)
[ 0.015441] pid_max: default: 32768 minimum: 301
[ 0.015673] Security Framework initialized
[ 0.015767] Mount-cache hash table entries: 512
[ 0.024591] Initializing cgroup subsys cpuacct
[ 0.024625] Initializing cgroup subsys memory
[ 0.024687] Initializing cgroup subsys blkio
[ 0.024825] CPU: Testing write buffer coherency: ok
[ 0.025403] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[ 0.025477] Setting up static identity map for 0x8038c820 - 0x8038c86c
[ 0.026807] Brought up 1 CPUs
[ 0.026831] SMP: Total of 1 processors activated (545.07 BogoMIPS).
[ 0.028128] devtmpfs: initialized
[ 0.092492] pinctrl core: initialized pinctrl subsystem
[ 0.092709] rstctl core: initialized rstctl subsystem
[ 0.093202] regulator-dummy: no parameters
[ 0.093771] NET: Registered protocol family 16
[ 0.094478] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.104155] pinctrl-single 44e10800.pinmux: prop pinctrl-0 index 0 invalid phandle
[ 0.104336] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[ 0.105423] platform 49000000.edma: alias fck already exists
[ 0.105456] platform 49000000.edma: alias fck already exists
[ 0.105484] platform 49000000.edma: alias fck already exists
[ 0.106635] gpiochip_add: registered GPIOs 0 to 31 on device: gpio
[ 0.106815] OMAP GPIO hardware version 0.1
[ 0.108226] gpiochip_add: registered GPIOs 32 to 63 on device: gpio
[ 0.109546] gpiochip_add: registered GPIOs 64 to 95 on device: gpio
[ 0.110862] gpiochip_add: registered GPIOs 96 to 127 on device: gpio
[ 0.111501] of_get_named_gpio_flags exited with status 52
[ 0.111533] gpio-rctrl rstctl.3: loaded OK
[ 0.116646] omap-gpmc 50000000.gpmc: GPMC revision 6.0
[ 0.119862] hw-breakpoint: debug architecture 0x4 unsupported.
[ 0.122050] cpsw.0: No hwaddr in dt. Using 9c:1d:58:ec:ec:2d from efuse
[ 0.122082] cpsw.1: No hwaddr in dt. Using 9c:1d:58:ec:ec:2f from efuse
[ 0.137651] bio: create slab
[ 0.149776] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver
[ 0.150018] of_get_named_gpio_flags: can't parse gpios property
[ 0.150312] vmmcsd_fixed: 3300 mV
[ 0.153422] SCSI subsystem initialized
[ 0.153873] usbcore: registered new interface driver usbfs
[ 0.153988] usbcore: registered new interface driver hub
[ 0.154320] usbcore: registered new device driver usb
[ 0.156431] omap_i2c 4819c000.i2c: bus 0 rev0.11 at 100 kHz
[ 0.156465] omap_i2c 4819c000.i2c: unable to select pin group
[ 0.156661] media: Linux media interface: v0.10
[ 0.156757] Linux video capture interface: v2.00
[ 0.156875] pps_core: LinuxPPS API ver. 1 registered
[ 0.156891] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[ 0.157607] Advanced Linux Sound Architecture Driver Initialized.
[ 0.158794] Switching to clocksource gp_timer
[ 0.176810] NET: Registered protocol family 2
[ 0.177798] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.177888] TCP bind hash table entries: 2048 (order: 3, 40960 bytes)
[ 0.177977] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.178071] TCP: reno registered
[ 0.178098] UDP hash table entries: 256 (order: 1, 12288 bytes)
[ 0.178144] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes)
[ 0.178637] NET: Registered protocol family 1
[ 0.179228] RPC: Registered named UNIX socket transport module.
[ 0.179249] RPC: Registered udp transport module.
[ 0.179262] RPC: Registered tcp transport module.
[ 0.179276] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.179662] Trying to unpack rootfs image as initramfs...
[ 1.965876] Freeing initrd memory: 12380K
[ 1.966561] CPU PMU: probing PMU on CPU 0
[ 1.966595] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
[ 1.967128] omap2_mbox_probe: platform not supported
[ 1.971048] VFS: Disk quotas dquot_6.5.2
[ 1.971286] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.972688] NFS: Registering the id_resolver key type
[ 1.972792] Key type id_resolver registered
[ 1.972809] Key type id_legacy registered
[ 1.972875] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 1.973309] msgmni has been set to 490
[ 1.976169] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[ 1.976195] io scheduler noop registered
[ 1.976211] io scheduler deadline registered
[ 1.976269] io scheduler cfq registered (default)
[ 1.980307] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 1.982738] omap_uart 44e09000.serial: did not get pins for uart0 error: -19
[ 1.983031] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0
[ 2.643924] console [ttyO0] enabled
[ 2.648460] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a OMAP UART1
[ 2.657214] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2
[ 2.665845] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a OMAP UART4
[ 2.674456] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a OMAP UART5
[ 2.683477] [drm] Initialized drm 1.1.0 20060810
[ 2.702123] brd: module loaded
[ 2.712391] loop: module loaded
[ 2.716564] bone-capemgr bone_capemgr.8: Failed to find baseboard eeprom node
[ 2.726496] nand_get_flash_type: 2c,f1 against 2c,f1
[ 2.732019] ONFI param page 0 valid
[ 2.735692] ONFI flash detected
[ 2.739011] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron MT29F1G08ABAEAWP), 128MiB, page size: 2048, OOB size: 64
[ 2.750922] omap2-nand: detected x8 NAND flash
[ 2.755585] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme
[ 2.761166] omap2-nand: using custom ecc layout
[ 2.766000] 10 ofpart partitions found on MTD device omap2-nand.0
[ 2.772392] Creating 10 MTD partitions on "omap2-nand.0":
[ 2.778068] 0x000000000000-0x000000020000 : "spl"
[ 2.784891] 0x000000020000-0x000000040000 : "spl_backup1"
[ 2.792346] 0x000000040000-0x000000060000 : "spl_backup2"
[ 2.799744] 0x000000060000-0x000000080000 : "spl_backup3"
[ 2.807089] 0x000000080000-0x000000240000 : "u-boot"
[ 2.815352] 0x000000240000-0x000000260000 : "bootenv"
[ 2.822281] 0x000000260000-0x000000280000 : "fdt"
[ 2.828906] 0x000000280000-0x000000780000 : "kernel"
[ 2.839882] 0x000000800000-0x000001c00000 : "root"
[ 2.863333] 0x000001c00000-0x000003000000 : "config"
[ 2.887068] OneNAND driver initializing
[ 2.892794] usbcore: registered new interface driver asix
[ 2.898607] usbcore: registered new interface driver cdc_ether
[ 2.904841] usbcore: registered new interface driver smsc95xx
[ 2.910952] usbcore: registered new interface driver net1080
[ 2.916973] usbcore: registered new interface driver cdc_subset
[ 2.923260] usbcore: registered new interface driver zaurus
[ 2.929261] usbcore: registered new interface driver cdc_ncm
[ 2.935982] usbcore: registered new interface driver cdc_acm
[ 2.941945] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 2.950324] Initializing USB Mass Storage driver...
[ 2.955558] usbcore: registered new interface driver usb-storage
[ 2.961857] USB Mass Storage support registered.
[ 2.966889] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[ 2.973627] musb-hdrc musb-hdrc.0.auto: pdev->id = 0
[ 2.978864] musb-hdrc musb-hdrc.0.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[ 2.987630] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[ 2.987652] musb-hdrc: MHDRC RTL version 2.0
[ 2.987666] musb-hdrc: setup fifo_mode 4
[ 2.987695] musb-hdrc: 28/31 max ep, 16384/16384 memory
[ 2.987843] musb-hdrc musb-hdrc.0.auto: *** mode=3
[ 2.992888] musb-hdrc musb-hdrc.0.auto: *** power=250
[ 2.998953] musb-hdrc musb-hdrc.1.auto: pdev->id = 1
[ 3.004218] musb-hdrc musb-hdrc.1.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[ 3.013201] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[ 3.013223] musb-hdrc: MHDRC RTL version 2.0
[ 3.013238] musb-hdrc: setup fifo_mode 4
[ 3.013260] musb-hdrc: 28/31 max ep, 16384/16384 memory
[ 3.013412] musb-hdrc musb-hdrc.1.auto: *** mode=1
[ 3.018469] musb-hdrc musb-hdrc.1.auto: *** power=250
[ 3.023776] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[ 3.030229] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1
[ 3.038466] musb-hdrc musb-hdrc.1.auto: supports USB remote wakeup
[ 3.038571] usb usb1: default language 0x0409
[ 3.038630] usb usb1: udev 1, busnum 1, minor = 0
[ 3.038654] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 3.045782] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.053353] usb usb1: Product: MUSB HDRC host driver
[ 3.058568] usb usb1: Manufacturer: Linux 3.8.13 musb-hcd
[ 3.064234] usb usb1: SerialNumber: musb-hdrc.1.auto
[ 3.070194] usb usb1: usb_probe_device
[ 3.070224] usb usb1: configuration #1 chosen from 1 choice
[ 3.070289] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[ 3.070491] hub 1-0:1.0: usb_probe_interface
[ 3.070514] hub 1-0:1.0: usb_probe_interface - got id
[ 3.070541] hub 1-0:1.0: USB hub found
[ 3.074595] hub 1-0:1.0: 1 port detected
[ 3.078763] hub 1-0:1.0: standalone hub
[ 3.078816] hub 1-0:1.0: individual port power switching
[ 3.078837] hub 1-0:1.0: no over-current protection
[ 3.078854] hub 1-0:1.0: Single TT
[ 3.078875] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
[ 3.078895] hub 1-0:1.0: power on to power good time: 10ms
[ 3.078953] hub 1-0:1.0: local power source is good
[ 3.079069] hub 1-0:1.0: enabling power on all ports
[ 3.080107] mousedev: PS/2 mouse device common for all mice
[ 3.088145] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[ 3.095647] 44e3e000.rtc: already running
[ 3.100151] i2c /dev entries driver
[ 3.105192] pps_ldisc: PPS line discipline registered
[ 3.110664] Driver for 1-wire Dallas network protocol.
[ 3.117942] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[ 3.125496] cpuidle: using governor ladder
[ 3.129816] cpuidle: using governor menu
[ 3.134384] of_get_named_gpio_flags exited with status 6
[ 3.134404] of_get_named_gpio_flags: can't parse gpios property
[ 3.134420] of_get_named_gpio_flags: can't parse gpios property
[ 3.134458] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed
[ 3.141681] omap_hsmmc mmc.4: Failed to get rstctl; not using any
[ 3.148483] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25
[ 3.155695] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24
[ 3.163005] mmc.4 supply vmmc_aux not found, using dummy regulator
[ 3.169952] omap_hsmmc mmc.4: pins are not configured from the driver
[ 3.180526] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
[ 3.204542] of_get_named_gpio_flags exited with status -517
[ 3.204611] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[ 3.212270] ledtrig-cpu: registered to indicate activity on CPUs
[ 3.219031] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36
[ 3.226227] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[ 3.234395] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[ 3.240687] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5
[ 3.247869] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6
[ 3.260138] usbcore: registered new interface driver usbhid
[ 3.266060] usbhid: USB HID core driver
[ 3.272962] TCP: cubic registered
[ 3.276483] Initializing XFRM netlink socket
[ 3.281060] NET: Registered protocol family 17
[ 3.285948] NET: Registered protocol family 15
[ 3.290877] Key type dns_resolver registered
[ 3.295511] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[ 3.303591] ThumbEE CPU extension supported.
[ 3.308102] Registering SWP/SWPB emulation handler
[ 3.314113] registered taskstats version 1
[ 3.320720] of_get_named_gpio_flags exited with status -517
[ 3.320795] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[ 3.377708] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[ 3.384157] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[ 3.398646] libphy: 4a101000.mdio: probed
[ 3.402971] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[ 3.413206] Detected MACID = 9c:1d:58:ec:ec:2d
[ 3.417890] cpsw 4a100000.ethernet: NAPI disabled
[ 3.423279] of_get_named_gpio_flags exited with status -517
[ 3.423345] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[ 3.432066] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[ 3.441349] cpu0 supply cpu0 not found, using dummy regulator
[ 3.447862] cpufreq_cpu0: failed to scale voltage up: -22
[ 3.453683] cpufreq_cpu0: failed to scale voltage up: -22
[ 3.466446] ALSA device list:
[ 3.469677] No soundcards found.
[ 3.474222] Freeing init memory: 264K
[ 3.478274] Failed to execute /init
[ 4.451039] jffs2: notice: (122) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[ 5.793354] net eth0: initializing cpsw version 1.12 (0)
[ 5.802359] net eth0: phy found : id is : 0x7c0f1
[ 5.807836] libphy: PHY 4a101000.mdio:01 not found
[ 5.813042] net eth0: phy 4a101000.mdio:01 not found on slave 1
[ 9.950466] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
Dec 29 17:10:44 (none) local0.err cgminer: Miner compile time: Fri Dec 22 16:38:56 CST 2017 type: Antminer D3 Blissz v2.04 beta
Dec 29 17:10:44 (none) local0.warn cgminer: Started cgminer 4.10.0
Dec 29 17:10:44 (none) local0.warn cgminer[376]: bitmain_DASH_init
Dec 29 17:10:44 (none) local0.warn cgminer[376]: check_fan_speed OK
Dec 29 17:10:44 (none) local0.notice cgminer[376]: detected at /sys/class/gpio/gpio51/value chain 0
Dec 29 17:10:44 (none) local0.notice cgminer[376]: detected at /sys/class/gpio/gpio48/value chain 1
Dec 29 17:10:44 (none) local0.notice cgminer[376]: detected at /sys/class/gpio/gpio47/value chain 2
Dec 29 17:10:44 (none) local0.notice cgminer[376]: detect total chain num 3
Dec 29 17:10:44 (none) local0.notice cgminer[376]: i2c init ok
Dec 29 17:10:44 (none) local0.notice cgminer[376]: check_whether_need_update_pic_program
Dec 29 17:10:46 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok
Dec 29 17:10:47 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 29 17:10:47 (none) local0.notice cgminer[376]: get_PIC16F1704_software_version_new ok, version = 0x81
Dec 29 17:10:49 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok
Dec 29 17:10:50 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 29 17:10:51 (none) local0.notice cgminer[376]: get_PIC16F1704_software_version_new ok, version = 0x81
Dec 29 17:10:52 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok
Dec 29 17:10:53 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 29 17:10:54 (none) local0.notice cgminer[376]: get_PIC16F1704_software_version_new ok, version = 0x81
Dec 29 17:10:54 (none) local0.notice cgminer[376]: every_chain_reset_PIC16F1704_pic_new
Dec 29 17:10:55 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok
Dec 29 17:10:57 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok
Dec 29 17:10:59 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok
Dec 29 17:10:59 (none) local0.notice cgminer[376]: every_chain_jump_from_loader_to_app_PIC16F1704_new
Dec 29 17:10:59 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 29 17:11:00 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 29 17:11:01 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 29 17:11:01 (none) local0.notice cgminer[376]: every_chain_enable_PIC16F1704_dc_dc_new
Dec 29 17:11:01 (none) local0.notice cgminer[376]: pic_heart_beat_func_new
Dec 29 17:11:01 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok
Dec 29 17:11:01 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok
Dec 29 17:11:01 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok
Dec 29 17:11:02 (none) local0.notice cgminer[376]: reset_all_hash_board
Dec 29 17:11:02 (none) local0.notice cgminer[376]: tty_init
Dec 29 17:11:02 (none) local0.notice cgminer[376]: tty_init_chain
Dec 29 17:11:02 (none) local0.notice cgminer[376]: tty_init_chain chainid = 0
Dec 29 17:11:02 (none) local0.err cgminer[376]: create rx read thread for chain 0 ok
Dec 29 17:11:02 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[0]
Dec 29 17:11:02 (none) local0.err cgminer[376]: create tx read thread for chain 0 ok
Dec 29 17:11:02 (none) local0.notice cgminer[376]: open device over
Dec 29 17:11:02 (none) local0.notice cgminer[376]: tty_init_chain
Dec 29 17:11:02 (none) local0.notice cgminer[376]: tty_init_chain chainid = 1
Dec 29 17:11:02 (none) local0.err cgminer[376]: create rx read thread for chain 1 ok
Dec 29 17:11:02 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[1]
Dec 29 17:11:02 (none) local0.err cgminer[376]: create tx read thread for chain 1 ok
Dec 29 17:11:02 (none) local0.notice cgminer[376]: open device over
Dec 29 17:11:02 (none) local0.notice cgminer[376]: tty_init_chain
Dec 29 17:11:02 (none) local0.notice cgminer[376]: tty_init_chain chainid = 2
Dec 29 17:11:02 (none) local0.err cgminer[376]: create rx read thread for chain 2 ok
Dec 29 17:11:02 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[2]
Dec 29 17:11:02 (none) local0.err cgminer[376]: create tx read thread for chain 2 ok
Dec 29 17:11:02 (none) local0.notice cgminer[376]: open device over
Dec 29 17:11:02 (none) local0.notice cgminer[376]: tty_init_chain
Dec 29 17:11:02 (none) local0.notice cgminer[376]: open device over
Dec 29 17:11:02 (none) local0.notice cgminer[376]: check_every_chain_asic_number
Dec 29 17:11:02 (none) local0.warn cgminer[376]: check_asic_reg: Chain0 has 60 ASICs
Dec 29 17:11:03 (none) local0.warn cgminer[376]: check_asic_reg: Chain1 has 60 ASICs
Dec 29 17:11:03 (none) local0.warn cgminer[376]: check_asic_reg: Chain2 has 60 ASICs
Dec 29 17:11:03 (none) local0.notice cgminer[376]: calculate_address_interval: temp_asic_number = 64, addrInterval = 1
Dec 29 17:11:03 (none) local0.notice cgminer[376]: calculate_address_interval: CHIP_OFFSET = 0x04000000, CORE_OFFSET = 0x00800000
Dec 29 17:11:03 (none) local0.notice cgminer[376]: set_ticket_mask ticket_mask = 0x0000001b
Dec 29 17:11:03 (none) local0.notice cgminer[376]: set_frequency: frequency = 400
Dec 29 17:11:03 (none) local0.notice cgminer[376]: set_frequency_chain: frequency = 400
Dec 29 17:11:03 (none) local0.notice cgminer[376]: set_frequency_chain: frequency = 400
Dec 29 17:11:03 (none) local0.notice cgminer[376]: set_frequency_chain: frequency = 400
Dec 29 17:11:03 (none) local0.warn cgminer[376]: error freq,set default freq(200M) instead
Dec 29 17:11:03 (none) local0.notice cgminer[376]: set_frequency_chain: frequency = 0
Dec 29 17:11:03 (none) local0.notice cgminer[376]: software_set_address_chain: chain 0 has 60 ASIC, and addrInterval is 1
Dec 29 17:11:03 (none) local0.notice cgminer[376]: Now Set
- Chain Address
Dec 29 17:11:04 (none) local0.notice cgminer[376]: Now Set [1] Chain Address
Dec 29 17:11:05 (none) local0.notice cgminer[376]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 1
Dec 29 17:11:05 (none) local0.notice cgminer[376]: Now Set [2] Chain Address
Dec 29 17:11:06 (none) local0.notice cgminer[376]: software_set_address_chain: chain 3 has 0 ASIC, and addrInterval is 1
Dec 29 17:11:06 (none) local0.notice cgminer[376]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61
Dec 29 17:11:06 (none) local0.notice cgminer[376]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61
Dec 29 17:11:06 (none) local0.notice cgminer[376]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61
Dec 29 17:11:06 (none) local0.notice cgminer[376]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61
Dec 29 17:11:06 (none) local0.notice cgminer[376]: select_core_to_check_temperature: diode_mux_sel = 4, vdd_mux_sel = 0
Dec 29 17:11:06 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0
Dec 29 17:11:06 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0
Dec 29 17:11:06 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0
Dec 29 17:11:06 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0
Dec 29 17:11:06 (none) local0.notice cgminer[376]: 0 calibration_sensor_offset_chain
Dec 29 17:11:06 (none) local0.notice cgminer[376]: chain:0 local:32 remote:35
Dec 29 17:11:06 (none) local0.warn cgminer[376]: Chain 0 set_temperature_offset_value_chain_sensor
Dec 29 17:11:06 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : -3,
Dec 29 17:11:07 (none) local0.notice cgminer[376]: chain:0 local:32 remote:32
Dec 29 17:11:07 (none) local0.warn cgminer[376]: Chain 0 set_temperature_offset_value_chain_sensor
Dec 29 17:11:07 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : -3,
Dec 29 17:11:07 (none) local0.notice cgminer[376]: 1 calibration_sensor_offset_chain
Dec 29 17:11:07 (none) local0.notice cgminer[376]: chain:1 local:30 remote:32
Dec 29 17:11:07 (none) local0.warn cgminer[376]: Chain 1 set_temperature_offset_value_chain_sensor
Dec 29 17:11:08 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : -2,
Dec 29 17:11:08 (none) local0.notice cgminer[376]: 2 calibration_sensor_offset_chain
Dec 29 17:11:08 (none) local0.notice cgminer[376]: chain:2 local:30 remote:33
Dec 29 17:11:08 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain_sensor
Dec 29 17:11:09 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -3,
Dec 29 17:11:09 (none) local0.notice cgminer[376]: chain:2 local:30 remote:30
Dec 29 17:11:09 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain_sensor
Dec 29 17:11:09 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -3,
Dec 29 17:11:09 (none) local0.warn cgminer[376]: Chain 0 set_temperature_offset_value_chain
Dec 29 17:11:09 (none) local0.warn cgminer[376]: Chain 0 set_temperature_offset_value_chain_sensor
Dec 29 17:11:10 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : -3,
Dec 29 17:11:10 (none) local0.warn cgminer[376]: Chain 1 set_temperature_offset_value_chain
Dec 29 17:11:10 (none) local0.warn cgminer[376]: Chain 1 set_temperature_offset_value_chain_sensor
Dec 29 17:11:10 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : -2,
Dec 29 17:11:10 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain
Dec 29 17:11:10 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain_sensor
Dec 29 17:11:10 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -3,
Dec 29 17:11:10 (none) local0.notice cgminer[376]: frequency = '400'
Dec 29 17:11:10 (none) local0.notice cgminer[376]: dev.timeout = 754956 us
Dec 29 17:11:10 (none) local0.notice cgminer[376]: open_core_chain
Dec 29 17:11:11 (none) local0.notice cgminer[376]: open_core_chain
Dec 29 17:11:11 (none) local0.notice cgminer[376]: open_core_chain
Dec 29 17:11:11 (none) local0.notice cgminer[376]: open_core_chain
Dec 29 17:11:12 (none) local0.err cgminer[376]: low hashrate detection trigger: 12585.600000 Gh/s
Dec 29 17:11:12 (none) local0.notice cgminer[376]: set voltage = 1143.942031 real:255 mv
Dec 29 17:11:13 (none) local0.notice cgminer[376]: set_PIC16F1704_voltage_new ok, voltage = 0xff
Dec 29 17:11:13 (none) local0.notice cgminer[376]: set_PIC16F1704_voltage_new ok, voltage = 0xff
Dec 29 17:11:13 (none) local0.notice cgminer[376]: set_PIC16F1704_voltage_new ok, voltage = 0xff
Dec 29 17:11:14 (none) local0.err cgminer[376]: cgminer time error total_secs = 1514567474.017350 last_total_secs = 1.000000
Dec 29 17:11:14 (none) local0.warn cgminer[376]: Pool 1 stratum+tcp://dash-us.coinmine.pl:6099 alive, testing stability
Dec 29 17:11:14 (none) local0.warn cgminer[376]: Switching to pool 1 stratum+tcp://dash-us.coinmine.pl:6099
Dec 29 17:11:14 (none) local0.warn cgminer[376]: Pool 0 stratum+tcp://dash.suprnova.cc:9991 alive, testing stability
Dec 29 17:11:14 (none) local0.warn cgminer[376]: Switching to pool 0 stratum+tcp://dash.suprnova.cc:9991
Dec 29 17:11:20 (none) local0.warn cgminer[376]: API running in IP access mode on port 4028 (15)
Hey thanks for the fantastic firmware upgrades, they really make a big difference in keeping these profitable until there's something to mine with them lol.
I noticed something in my farm. I have 9 D3's, all on 1.12 version. And when I change the settings across the board to identical freq. and voltage, almost invariably, the 3rd hash board will get immediately more hardware faults than the other two boards. By a ton. (hundreds if not thousands in a few minutes) I'm just wondering if there may be something in the code that is treating board 3 differently than the other two voltage wise, because it seems to possibly be a deficiency in the voltage causing the escalated hardware fault levels, since as i raise them the problem goes away. This is obviously to be expected, but the disparity between the boards being so consistent is unusual.
Anyway, thanks for the work, looking forward to a stable release of v. 2.0!
T.J.
I noticed something in my farm. I have 9 D3's, all on 1.12 version. And when I change the settings across the board to identical freq. and voltage, almost invariably, the 3rd hash board will get immediately more hardware faults than the other two boards. By a ton. (hundreds if not thousands in a few minutes) I'm just wondering if there may be something in the code that is treating board 3 differently than the other two voltage wise, because it seems to possibly be a deficiency in the voltage causing the escalated hardware fault levels, since as i raise them the problem goes away. This is obviously to be expected, but the disparity between the boards being so consistent is unusual.
Anyway, thanks for the work, looking forward to a stable release of v. 2.0!
T.J.
d3 is the most expensive and noisy piece of trash available on the net...
i have a couple, both with hashing boards 2 & 3 not working. actually i had to paid an extra 200 bucks to send 4 hashing boards to hong kong in warranty... its been two weeks and still waiting for them.
Cheaper to send them to California. Same turnaround time in my experience.
Thx Man! your firmware is AWESOME!!! Working like charm!
Still missing some features!
- Day / Night - fan / boards profiles is - a must have
- agree with wedwo - target temp threshold adjustment - a must have
- Individual fan control front / back in percentage lvl.
- fan reaction speed - fast / slow / adaptive (meaning that it will change the speed within some time not meaning slower than slow)
- automatic emergency shutdown - enter sleep state - fans running low if protective temp threshold is reached.
Currently out of ides
PS. Donated <3
Still missing some features!
- Day / Night - fan / boards profiles is - a must have
- agree with wedwo - target temp threshold adjustment - a must have
- Individual fan control front / back in percentage lvl.
- fan reaction speed - fast / slow / adaptive (meaning that it will change the speed within some time not meaning slower than slow
) - automatic emergency shutdown - enter sleep state - fans running low if protective temp threshold is reached.
Currently out of ides
PS. Donated <3
Thanks for the good ideas! All should be possible except the individual fan speed. They are somehow both hard wired to one pwm controller
Thx Man! your firmware is AWESOME!!! Working like charm!
Still missing some features!
- Day / Night - fan / boards profiles is - a must have
- agree with wedwo - target temp threshold adjustment - a must have
- Individual fan control front / back in percentage lvl.
- fan reaction speed - fast / slow / adaptive (meaning that it will change the speed within some time not meaning slower than slow)
- automatic emergency shutdown - enter sleep state - fans running low if protective temp threshold is reached.
Currently out of ides
PS. Donated <3
Still missing some features!
- Day / Night - fan / boards profiles is - a must have
- agree with wedwo - target temp threshold adjustment - a must have
- Individual fan control front / back in percentage lvl.
- fan reaction speed - fast / slow / adaptive (meaning that it will change the speed within some time not meaning slower than slow
) - automatic emergency shutdown - enter sleep state - fans running low if protective temp threshold is reached.
Currently out of ides
PS. Donated <3
I would like to see a target chip temperature for fan control.
e.g. If I set the target chip temperature to 70 C and the hottest chip reaches 70C, the fan speeds up until it's down to 69 or 68 and then slows down again to keep the chip temperature within a certain range instead of just guessing what the best fan speed range is to maintain a certain temperature.
e.g. If I set the target chip temperature to 70 C and the hottest chip reaches 70C, the fan speeds up until it's down to 69 or 68 and then slows down again to keep the chip temperature within a certain range instead of just guessing what the best fan speed range is to maintain a certain temperature.
Start with 444 freq and voltage 5. If HW errors raise the voltage until you see 1-2 per minute.
Do the same for all 3 asics.
Of course Fan Silet and 25%
thanks for thatDo the same for all 3 asics.
Of course Fan Silet and 25%
I think I will do it
what will affect fan silent? I have no issue with noise, or it will affect some other aspects?
so put it auto performance.. it will keep your d3 temp lower.. in the long run it is better....
But dont put it 100 % ,, its like putting your brain to work on 100 percents load, it will burn... right.
Start with 444 freq and voltage 5. If HW errors raise the voltage until you see 1-2 per minute.
Do the same for all 3 asics.
Of course Fan Silet and 25%
thanks for thatDo the same for all 3 asics.
Of course Fan Silet and 25%
I think I will do it
what will affect fan silent? I have no issue with noise, or it will affect some other aspects?
Start with 444 freq and voltage 5. If HW errors raise the voltage until you see 1-2 per minute.
Do the same for all 3 asics.
Of course Fan Silet and 25%
Do the same for all 3 asics.
Of course Fan Silet and 25%
ok so I did try upgrading, lowering the freq, turning off for hours but nothing
3 out of 44 miners aren't stable, from my experience this is not a good number
before sending them back to China I would like to try this firmware out and as I was surfing in thread found out that in some cases it helps
in fact I don't want more hashrate or lower power consumption, I just want them to work and +- 10-15% of hashrate would stop me sending them back to bitmain
I need just one more advice to try this out, my main issue with those 3 miners are HW errors and after some time 0 hashrate
3 out of 44 miners aren't stable, from my experience this is not a good number
before sending them back to China I would like to try this firmware out and as I was surfing in thread found out that in some cases it helps
in fact I don't want more hashrate or lower power consumption, I just want them to work and +- 10-15% of hashrate would stop me sending them back to bitmain
I need just one more advice to try this out, my main issue with those 3 miners are HW errors and after some time 0 hashrate
any idea why this is happening? Doesn't make sense....
It's running fine, but the pool gives you work with high difficulty, so you find a share not so often, that's why you see those spikes and dips. On average your hashrate is good I would say.
Jump to: