Latest posts of: deezhere

Show Posts
Pages: [1]

Alternate cryptocurrencies / Mining (Altcoins) / Re: Antminer D3 Blissz firmware (10/12 v1.12 update)

on: January 18, 2018, 02:33:10 AM

Quote from: bitsolutions on January 18, 2018, 02:01:04 AM Quote from: blissz on January 16, 2018, 03:52:04 PM Hi All, I wasn't aware of the GPL license, so I did some investigation last days. After reading the GPL licenses I can conclude that stangerm2 is right. So that means I do have to provide the modified sources as most of the current modifications are now build on top of a linked module in cgminer. There are some consequences in releasing the source though: - As far as I know, Bitmain is free to use these improvements in their current and their new products they will sell. I do hope they compensate these free goodies with a multi algorithm D3 firmware one day - There will probably appear modified firmware binaries which can cause damaging your miners if the maker doesn't know what he's doing... - I had plans to buy a S9 as there are a lot of requests and make a modified S9 version, but I might consider not to jump on that boat for now. (let's first see what will happen with the D3) Legit alternatives instead of releasing the sourcecode - I stop this project and take the binaries offline. I don't like this option, as the whole idea is to help improve the situations for the D3 owners. - Temporary I take the binaries offline and I will write something from scratch / not linked to the sources of cgminer. This will take away the consequences, but a lot of time and effort (at least a month or two) will be put into something that will probably not lead to any improvements for you guys. My proposal - Although these consequences I will release source of a stable version (non BETA) that allow others to investigate the voltage / fan mods / fault check improvements I did. (devfee related code will be removed from the source). This allow others to look into the changes I did to make a binary for themselves without devfee. BETA functionality will be left out of the source right now since it's not yet stable and will create dangerous situations when used in a wrong way. I might have to restrict the use of a BETA versions to a closed group instead of providing a public link to the BETA versions. Happy mining Ciao Blissz To add some encouragement to getting the source released, I'll be issuing a DMCA takedown to have bitcointalk remove this thread for copyright violations in 24 hours if the complete corresponding source code for all the distributed firmware binaries is not uploaded by then. I am a one of a number of cgminer copyright holders. Blissz, I believe everyone here is greatful for the work and effort you've done to improve upon the D3. If you haven't already looked into github I would recommend you publish your source there. It's designed for just this purpose and makes it easy to commit new changes as you go. Thanks for the improvements and I hope this work continues into the future in a manner that is open and fair to all.

Alternate cryptocurrencies / Mining (Altcoins) / Re: Antminer D3 Blissz firmware (10/12 v1.12 update)

on: January 17, 2018, 01:13:30 PM

Quote from: SimpleCoin8 on January 17, 2018, 11:43:38 AM Blissz, don’t release your source code to anyone. It’s yours. If people don’t want to support the dev fee, they can revert to the firmware provided by Bitmain. If you could introduce a better way to get the dev fee that would allow for more stable mining, that would be great though. No need to release your code to these whining people. Most of us have no problem with the dev fee or a flat fee and for those that do it's very easy to work around and disable altogether. Flat fee would be preferred though however, when you claim he shouldn't release the source and that it's his you couldn't possibly be more wrong. Ask yourself, why does Bitmain release their source instead of just claiming it as their own? Without Bitmain's source none of this would be possible. Without cgminer's source, Bitmain couldn't have made the original product. Without many other packages also included and freely sourced cgminer couldn't have made their software etc.... The GPL exists for a reason, to stop people from stealing code and repackaging it as their own and to further advancement in a free and open way. Blissz' work is great here and by releasing the source he's doing the right thing. He can continue to improve upon it and continue to leave the dev fee in if he chooses. Others should also be free to see his changes to the source and also improve upon them. If this isn't acceptable then I would encourage everyone to work together here to build a new firmware completely from scratch and license it with something like the MIT license without using any software that's currently licensed under the GPL. Without releasing the source, he would be opening himself up to multiple lawsuits should his real identity ever be discovered. Please don't encourage theft, the crypto community has enough problems to deal already. No need to throw potential lawsuits into the mix as well.

Alternate cryptocurrencies / Mining (Altcoins) / Re: Antminer D3 Blissz firmware (10/12 v1.12 update)

on: January 13, 2018, 03:22:01 PM

Quote from: cryptojacker on January 12, 2018, 11:56:09 PM Hello! Too many pages. My eyes are crossed. I have a D3 with a dead board. Is there anything I can do to bring it back to life? It worked fine at first. Nothing looks burned. Thanks for the help. Yes, open a support ticket with Bitmain and ship that hashboard back for repair.

Alternate cryptocurrencies / Mining (Altcoins) / Re: Antminer D3 Blissz firmware (10/12 v1.12 update)

on: January 12, 2018, 09:33:33 PM

Quote from: verpolt on January 12, 2018, 05:33:05 PM Thanks for the good work. Do you think it is possible for the D3 Asics to go for X13? I have no idea how different X11 and X13 algo is. But if that would be possible it would be really cool. Not possible. It should be possible to run one of the single algorithms from X11 though since they are all already fully supported.

Alternate cryptocurrencies / Mining (Altcoins) / Re: Antminer D3 Blissz firmware (10/12 v1.12 update)

on: January 10, 2018, 12:59:37 PM

Quote from: blissz on January 10, 2018, 08:29:38 AM Hi guys, I really would like to have other algorithm support on the D3 as well, so here is an update from what I've experienced so far: I tried to isolate a single algorithm / other algorithms, but not yet succeeded. There are some parameters to tweak with, which seem to change something in the ASICS, but the problem is that even if it switches to another algorithm (which I am not 100% sure), you can't know which one... It's also not that straightforward to change the linux part to support another algorithm, so it's easy to make a small mistake there as well. If I had some inside information that for example groestl is 100% for sure supported then it would be easier to go 100% for that. Now there are too many variables to play with. I still have some ideas left to try: I want to build an automated matrix test that tries all parameter combinations and tries to verify it against all known algorithms. It will be quite an effort to build this, but I think it's the only possibility to find out if it's possible. Blissz, so you can be 100% sure which algorithms are supported by x11. Here is a list. blake bmw groestl jh keccak skein luffa cubehash shavite simd echo X12, X13, X14, X15 and X17 are all exactly the same but with additional algorithms added in. Out of all the X11 algorithms listed above groestl should currently be the most profitable even at a severely reduced hash rate. If possible, I would try to focus on groestl first and then skein as a 2nd alternative. Cracking this problem of isolating a single algo is something that I believe many of us would be willing to support financially in a big way as we would all benefit in a big way.

Alternate cryptocurrencies / Mining (Altcoins) / Re: Antminer D3 Blissz firmware (10/12 v1.12 update)

on: January 09, 2018, 09:36:58 PM

Blissz, is there any way that we can move on from simply messing with fan speeds and voltage to actually trying to isolate and mine a single algo from X11? People have previously dismissed this idea but I yet to see any reason why it shouldn't be possible even if it is at a severely lower hashrate. For instance these D3's are already mining and support the groestl algorithm which is one of the 11 algorithms contained in X11. If the D3 could be modded to mine only that specific algorithm even at 500Mh/s @ 1200 watts then that would bring the profitability back to nearly $30 per 24hr. What do we need to do to look at this more seriously? Do we need to pool together and get you another D3 to test with?

Alternate cryptocurrencies / Mining (Altcoins) / Re: Antminer D3 Blissz firmware (10/12 v1.12 update)

on: December 29, 2017, 02:25:51 PM

Quote from: chapsmx on December 28, 2017, 09:18:47 PM Quote from: TenaciousJ on December 28, 2017, 05:33:21 AM 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. 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.

Alternate cryptocurrencies / Mining (Altcoins) / Re: miners down...help needed!!

on: December 28, 2017, 03:17:33 AM

Quote from: mikeingh0000 on December 28, 2017, 02:15:54 AM Hey Everyone! Big thanks to blissz!!! I have been lurking the last couple of weeks and finally took the plunge this weekend to upgrade my d3's this weekend with the v2.04 beta :: 22/12 :: test version - both machines seemed to be running great. And sometime over the course of the night I could hear what sounded like the d3's power cycling every couple of minutes... after checking on the machines I see on the miner status page that everything is blank? I have reset, reflashed stock firmware & reset, etc... Each time i get the same result - nothing in miner status page and I cant see the miners connecting to any pools. What went wrong & What should I being doing next to get them running again? screen capture of miner status page copy of log [ 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=84096 [ 0.000000] pcpu-alloc: 0 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 64768 [ 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: 238676k/238676k available, 23468k 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.000352] Calibrating delay loop... 545.07 BogoMIPS (lpj=531968) [ 0.015436] pid_max: default: 32768 minimum: 301 [ 0.015665] Security Framework initialized [ 0.015759] Mount-cache hash table entries: 512 [ 0.024584] Initializing cgroup subsys cpuacct [ 0.024617] Initializing cgroup subsys memory [ 0.024680] Initializing cgroup subsys blkio [ 0.024815] CPU: Testing write buffer coherency: ok [ 0.025390] CPU0: thread -1, cpu 0, socket -1, mpidr 0 [ 0.025464] Setting up static identity map for 0x8038c820 - 0x8038c86c [ 0.026795] Brought up 1 CPUs [ 0.026819] SMP: Total of 1 processors activated (545.07 BogoMIPS). [ 0.028115] devtmpfs: initialized [ 0.092524] pinctrl core: initialized pinctrl subsystem [ 0.092741] rstctl core: initialized rstctl subsystem [ 0.093235] regulator-dummy: no parameters [ 0.093802] NET: Registered protocol family 16 [ 0.094509] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.104167] pinctrl-single 44e10800.pinmux: prop pinctrl-0 index 0 invalid phandle [ 0.104346] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568 [ 0.105435] platform 49000000.edma: alias fck already exists [ 0.105469] platform 49000000.edma: alias fck already exists [ 0.105497] platform 49000000.edma: alias fck already exists [ 0.106646] gpiochip_add: registered GPIOs 0 to 31 on device: gpio [ 0.106829] OMAP GPIO hardware version 0.1 [ 0.108233] gpiochip_add: registered GPIOs 32 to 63 on device: gpio [ 0.109555] gpiochip_add: registered GPIOs 64 to 95 on device: gpio [ 0.110876] gpiochip_add: registered GPIOs 96 to 127 on device: gpio [ 0.111508] of_get_named_gpio_flags exited with status 52 [ 0.111540] gpio-rctrl rstctl.3: loaded OK [ 0.116644] omap-gpmc 50000000.gpmc: GPMC revision 6.0 [ 0.119851] hw-breakpoint: debug architecture 0x4 unsupported. [ 0.122039] cpsw.0: No hwaddr in dt. Using 3c:a3:08:25:29:ab from efuse [ 0.122070] cpsw.1: No hwaddr in dt. Using 3c:a3:08:25:29:ad from efuse [ 0.137625] bio: create slab <bio-0> at 0 [ 0.149761] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver [ 0.150000] of_get_named_gpio_flags: can't parse gpios property [ 0.150299] vmmcsd_fixed: 3300 mV [ 0.153414] SCSI subsystem initialized [ 0.153871] usbcore: registered new interface driver usbfs [ 0.153984] usbcore: registered new interface driver hub [ 0.154315] usbcore: registered new device driver usb [ 0.156420] omap_i2c 4819c000.i2c: bus 0 rev0.11 at 100 kHz [ 0.156454] omap_i2c 4819c000.i2c: unable to select pin group [ 0.156649] media: Linux media interface: v0.10 [ 0.156747] Linux video capture interface: v2.00 [ 0.156863] pps_core: LinuxPPS API ver. 1 registered [ 0.156879] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.157597] Advanced Linux Sound Architecture Driver Initialized. [ 0.158795] Switching to clocksource gp_timer [ 0.176796] NET: Registered protocol family 2 [ 0.177787] TCP established hash table entries: 2048 (order: 2, 16384 bytes) [ 0.177874] TCP bind hash table entries: 2048 (order: 3, 40960 bytes) [ 0.177963] TCP: Hash tables configured (established 2048 bind 2048) [ 0.178056] TCP: reno registered [ 0.178083] UDP hash table entries: 256 (order: 1, 12288 bytes) [ 0.178128] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes) [ 0.178616] NET: Registered protocol family 1 [ 0.179194] RPC: Registered named UNIX socket transport module. [ 0.179215] RPC: Registered udp transport module. [ 0.179228] RPC: Registered tcp transport module. [ 0.179242] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.179623] Trying to unpack rootfs image as initramfs... [ 1.942169] Freeing initrd memory: 12240K [ 1.942851] CPU PMU: probing PMU on CPU 0 [ 1.942885] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available [ 1.943427] omap2_mbox_probe: platform not supported [ 1.947318] VFS: Disk quotas dquot_6.5.2 [ 1.947554] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 1.948961] NFS: Registering the id_resolver key type [ 1.949077] Key type id_resolver registered [ 1.949094] Key type id_legacy registered [ 1.949160] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. [ 1.949594] msgmni has been set to 490 [ 1.952485] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249) [ 1.952511] io scheduler noop registered [ 1.952527] io scheduler deadline registered [ 1.952584] io scheduler cfq registered (default) [ 1.956658] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.959082] omap_uart 44e09000.serial: did not get pins for uart0 error: -19 [ 1.959365] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0 [ 2.620135] console [ttyO0] enabled [ 2.624669] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a OMAP UART1 [ 2.633322] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2 [ 2.642007] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a OMAP UART4 [ 2.650622] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a OMAP UART5 [ 2.659646] [drm] Initialized drm 1.1.0 20060810 [ 2.678293] brd: module loaded [ 2.688593] loop: module loaded [ 2.692811] bone-capemgr bone_capemgr.8: Failed to find baseboard eeprom node [ 2.702758] nand_get_flash_type: 2c,f1 against 2c,f1 [ 2.708284] ONFI param page 0 valid [ 2.711957] ONFI flash detected [ 2.715276] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron MT29F1G08ABAEAWP), 128MiB, page size: 2048, OOB size: 64 [ 2.727186] omap2-nand: detected x8 NAND flash [ 2.731851] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme [ 2.737432] omap2-nand: using custom ecc layout [ 2.742273] 10 ofpart partitions found on MTD device omap2-nand.0 [ 2.748668] Creating 10 MTD partitions on "omap2-nand.0": [ 2.754346] 0x000000000000-0x000000020000 : "spl" [ 2.761162] 0x000000020000-0x000000040000 : "spl_backup1" [ 2.768622] 0x000000040000-0x000000060000 : "spl_backup2" [ 2.775978] 0x000000060000-0x000000080000 : "spl_backup3" [ 2.783385] 0x000000080000-0x000000240000 : "u-boot" [ 2.791592] 0x000000240000-0x000000260000 : "bootenv" [ 2.798559] 0x000000260000-0x000000280000 : "fdt" [ 2.805149] 0x000000280000-0x000000780000 : "kernel" [ 2.816163] 0x000000800000-0x000001c00000 : "root" [ 2.839632] 0x000001c00000-0x000003000000 : "config" [ 2.863377] OneNAND driver initializing [ 2.869104] usbcore: registered new interface driver asix [ 2.874920] usbcore: registered new interface driver cdc_ether [ 2.881167] usbcore: registered new interface driver smsc95xx [ 2.887289] usbcore: registered new interface driver net1080 [ 2.893339] usbcore: registered new interface driver cdc_subset [ 2.899633] usbcore: registered new interface driver zaurus [ 2.905640] usbcore: registered new interface driver cdc_ncm [ 2.912371] usbcore: registered new interface driver cdc_acm [ 2.918331] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 2.926710] Initializing USB Mass Storage driver... [ 2.931950] usbcore: registered new interface driver usb-storage [ 2.938249] USB Mass Storage support registered. [ 2.943288] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host) [ 2.950035] musb-hdrc musb-hdrc.0.auto: pdev->id = 0 [ 2.955269] musb-hdrc musb-hdrc.0.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK [ 2.964039] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) [ 2.964062] musb-hdrc: MHDRC RTL version 2.0 [ 2.964077] musb-hdrc: setup fifo_mode 4 [ 2.964105] musb-hdrc: 28/31 max ep, 16384/16384 memory [ 2.964251] musb-hdrc musb-hdrc.0.auto: mode=3 [ 2.969294] musb-hdrc musb-hdrc.0.auto: * power=250 [ 2.975349] musb-hdrc musb-hdrc.1.auto: pdev->id = 1 [ 2.980587] musb-hdrc musb-hdrc.1.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK [ 2.989355] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) [ 2.989374] musb-hdrc: MHDRC RTL version 2.0 [ 2.989388] musb-hdrc: setup fifo_mode 4 [ 2.989411] musb-hdrc: 28/31 max ep, 16384/16384 memory [ 2.989551] musb-hdrc musb-hdrc.1.auto: * mode=1 [ 2.994593] musb-hdrc musb-hdrc.1.auto: * power=250 [ 2.999901] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver [ 3.006584] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1 [ 3.014824] musb-hdrc musb-hdrc.1.auto: supports USB remote wakeup [ 3.014929] usb usb1: default language 0x0409 [ 3.014987] usb usb1: udev 1, busnum 1, minor = 0 [ 3.015011] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 3.022137] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.029709] usb usb1: Product: MUSB HDRC host driver [ 3.034923] usb usb1: Manufacturer: Linux 3.8.13 musb-hcd [ 3.040590] usb usb1: SerialNumber: musb-hdrc.1.auto [ 3.046567] usb usb1: usb_probe_device [ 3.046595] usb usb1: configuration #1 chosen from 1 choice [ 3.046660] usb usb1: adding 1-0:1.0 (config #1, interface 0) [ 3.046861] hub 1-0:1.0: usb_probe_interface [ 3.046883] hub 1-0:1.0: usb_probe_interface - got id [ 3.046910] hub 1-0:1.0: USB hub found [ 3.050916] hub 1-0:1.0: 1 port detected [ 3.055056] hub 1-0:1.0: standalone hub [ 3.055076] hub 1-0:1.0: individual port power switching [ 3.055094] hub 1-0:1.0: no over-current protection [ 3.055111] hub 1-0:1.0: Single TT [ 3.055132] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns) [ 3.055152] hub 1-0:1.0: power on to power good time: 10ms [ 3.055208] hub 1-0:1.0: local power source is good [ 3.055324] hub 1-0:1.0: enabling power on all ports [ 3.056413] mousedev: PS/2 mouse device common for all mice [ 3.064384] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0 [ 3.072151] i2c /dev entries driver [ 3.077198] pps_ldisc: PPS line discipline registered [ 3.082665] Driver for 1-wire Dallas network protocol. [ 3.089953] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec [ 3.097518] cpuidle: using governor ladder [ 3.101844] cpuidle: using governor menu [ 3.106449] of_get_named_gpio_flags exited with status 6 [ 3.106468] of_get_named_gpio_flags: can't parse gpios property [ 3.106484] of_get_named_gpio_flags: can't parse gpios property [ 3.106521] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed [ 3.113752] omap_hsmmc mmc.4: Failed to get rstctl; not using any [ 3.120563] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25 [ 3.127780] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24 [ 3.135096] mmc.4 supply vmmc_aux not found, using dummy regulator [ 3.142057] omap_hsmmc mmc.4: pins are not configured from the driver [ 3.157051] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000 [ 3.177076] of_get_named_gpio_flags exited with status -517 [ 3.177141] platform gpio-leds.7: Driver leds-gpio requests probe deferral [ 3.184917] ledtrig-cpu: registered to indicate activity on CPUs [ 3.191705] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36 [ 3.198898] omap-sham 53100000.sham: hw accel on OMAP rev 4.3 [ 3.207003] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2 [ 3.213353] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5 [ 3.220536] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6 [ 3.232797] usbcore: registered new interface driver usbhid [ 3.238719] usbhid: USB HID core driver [ 3.245615] TCP: cubic registered [ 3.249140] Initializing XFRM netlink socket [ 3.253707] NET: Registered protocol family 17 [ 3.258581] NET: Registered protocol family 15 [ 3.263451] Key type dns_resolver registered [ 3.268085] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3 [ 3.276165] ThumbEE CPU extension supported. [ 3.280675] Registering SWP/SWPB emulation handler [ 3.286691] registered taskstats version 1 [ 3.293317] of_get_named_gpio_flags exited with status -517 [ 3.293390] platform gpio-leds.7: Driver leds-gpio requests probe deferral [ 3.350359] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [ 3.356771] davinci_mdio 4a101000.mdio: detected phy mask fffffffe [ 3.371330] libphy: 4a101000.mdio: probed [ 3.375645] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720 [ 3.385880] Detected MACID = 3c:a3:08:25:29:ab [ 3.390560] cpsw 4a100000.ethernet: NAPI disabled [ 3.395951] of_get_named_gpio_flags exited with status -517 [ 3.396016] platform gpio-leds.7: Driver leds-gpio requests probe deferral [ 3.404726] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) [ 3.414009] cpu0 supply cpu0 not found, using dummy regulator [ 3.420491] cpufreq_cpu0: failed to scale voltage up: -22 [ 3.426307] cpufreq_cpu0: failed to scale voltage up: -22 [ 3.439070] ALSA device list: [ 3.442303] No soundcards found. [ 3.446875] Freeing init memory: 264K [ 3.450924] Failed to execute /init [ 4.452923] 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.746861] net eth0: initializing cpsw version 1.12 (0) [ 5.755777] net eth0: phy found : id is : 0x7c0f1 [ 5.761202] libphy: PHY 4a101000.mdio:01 not found [ 5.766404] net eth0: phy 4a101000.mdio:01 not found on slave 1 [ 9.903560] libphy: 4a101000.mdio:00 - Link is Up - 100/Full Dec 28 02:12:09 (none) local0.err cgminer: Miner compile time: Mon Nov 20 17:06:56 CST 2017 type: Antminer D3 Dec 28 02:12:09 (none) local0.warn cgminer: Started cgminer 4.9.0 Dec 28 02:12:09 (none) local0.warn cgminer[376]: bitmain_DASH_init Dec 28 02:12:10 (none) local0.err cgminer[376]: FAN1 too slow ... Dec 28 02:12:10 (none) local0.err cgminer[376]: FAN2 too slow ... Dec 28 02:12:10 (none) local0.err cgminer[376]: FAN1 too slow ... Dec 28 02:12:10 (none) local0.err cgminer[376]: FAN2 too slow ... Dec 28 02:12:11 (none) local0.err cgminer[376]: FAN1 too slow ... Dec 28 02:12:11 (none) local0.err cgminer[376]: FAN1 too slow ... Dec 28 02:12:12 (none) local0.err cgminer[376]: FAN1 too slow ... Dec 28 02:12:12 (none) local0.err cgminer[376]: FAN1 too slow ... Dec 28 02:12:13 (none) local0.err cgminer[376]: FAN1 too slow ... Dec 28 02:12:13 (none) local0.err cgminer[376]: FAN1 too slow ... Dec 28 02:12:14 (none) local0.err cgminer[376]: FAN1 too slow ... Dec 28 02:12:14 (none) local0.warn cgminer[376]: check_fan_speed OK Dec 28 02:12:14 (none) local0.notice cgminer[376]: detected at /sys/class/gpio/gpio51/value chain 0 Dec 28 02:12:14 (none) local0.notice cgminer[376]: detected at /sys/class/gpio/gpio48/value chain 1 Dec 28 02:12:14 (none) local0.notice cgminer[376]: detected at /sys/class/gpio/gpio47/value chain 2 Dec 28 02:12:14 (none) local0.notice cgminer[376]: detect total chain num 3 Dec 28 02:12:14 (none) local0.notice cgminer[376]: i2c init ok Dec 28 02:12:14 (none) local0.notice cgminer[376]: check_whether_need_update_pic_program Dec 28 02:12:15 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok Dec 28 02:12:16 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok Dec 28 02:12:16 (none) local0.notice cgminer[376]: get_PIC16F1704_software_version_new ok, version = 0x81 Dec 28 02:12:17 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok Dec 28 02:12:18 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok Dec 28 02:12:18 (none) local0.notice cgminer[376]: get_PIC16F1704_software_version_new ok, version = 0x81 Dec 28 02:12:19 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok Dec 28 02:12:20 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok Dec 28 02:12:20 (none) local0.notice cgminer[376]: get_PIC16F1704_software_version_new ok, version = 0x81 Dec 28 02:12:20 (none) local0.notice cgminer[376]: every_chain_reset_PIC16F1704_pic_new Dec 28 02:12:22 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok Dec 28 02:12:23 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok Dec 28 02:12:24 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok Dec 28 02:12:25 (none) local0.notice cgminer[376]: every_chain_jump_from_loader_to_app_PIC16F1704_new Dec 28 02:12:25 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok Dec 28 02:12:25 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok Dec 28 02:12:26 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok Dec 28 02:12:27 (none) local0.notice cgminer[376]: every_chain_enable_PIC16F1704_dc_dc_new Dec 28 02:12:27 (none) local0.notice cgminer[376]: pic_heart_beat_func_new Dec 28 02:12:27 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok Dec 28 02:12:27 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok Dec 28 02:12:27 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok Dec 28 02:12:28 (none) local0.notice cgminer[376]: reset_all_hash_board Dec 28 02:12:29 (none) local0.notice cgminer[376]: tty_init Dec 28 02:12:29 (none) local0.notice cgminer[376]: tty_init_chain Dec 28 02:12:29 (none) local0.notice cgminer[376]: tty_init_chain chainid = 0 Dec 28 02:12:29 (none) local0.err cgminer[376]: create rx read thread for chain 0 ok Dec 28 02:12:29 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[0] Dec 28 02:12:29 (none) local0.err cgminer[376]: create tx read thread for chain 0 ok Dec 28 02:12:29 (none) local0.notice cgminer[376]: open device over Dec 28 02:12:29 (none) local0.notice cgminer[376]: tty_init_chain Dec 28 02:12:29 (none) local0.notice cgminer[376]: tty_init_chain chainid = 1 Dec 28 02:12:29 (none) local0.err cgminer[376]: create rx read thread for chain 1 ok Dec 28 02:12:29 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[1] Dec 28 02:12:29 (none) local0.err cgminer[376]: create tx read thread for chain 1 ok Dec 28 02:12:29 (none) local0.notice cgminer[376]: open device over Dec 28 02:12:29 (none) local0.notice cgminer[376]: tty_init_chain Dec 28 02:12:29 (none) local0.notice cgminer[376]: tty_init_chain chainid = 2 Dec 28 02:12:29 (none) local0.err cgminer[376]: create rx read thread for chain 2 ok Dec 28 02:12:29 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[2] Dec 28 02:12:29 (none) local0.err cgminer[376]: create tx read thread for chain 2 ok Dec 28 02:12:29 (none) local0.notice cgminer[376]: open device over Dec 28 02:12:29 (none) local0.notice cgminer[376]: tty_init_chain Dec 28 02:12:29 (none) local0.notice cgminer[376]: open device over Dec 28 02:12:30 (none) local0.notice cgminer[376]: check_every_chain_asic_number Dec 28 02:12:30 (none) local0.warn cgminer[376]: check_asic_reg: Chain0 has 60 ASICs Dec 28 02:12:30 (none) local0.warn cgminer[376]: check_asic_reg: Chain1 has 60 ASICs Dec 28 02:12:31 (none) local0.warn cgminer[376]: check_asic_reg: Chain2 has 60 ASICs Dec 28 02:12:31 (none) local0.notice cgminer[376]: calculate_address_interval: temp_asic_number = 64, addrInterval = 1 Dec 28 02:12:31 (none) local0.notice cgminer[376]: calculate_address_interval: CHIP_OFFSET = 0x04000000, CORE_OFFSET = 0x00800000 Dec 28 02:12:31 (none) local0.notice cgminer[376]: set_ticket_mask ticket_mask = 0x0000001b Dec 28 02:12:31 (none) local0.notice cgminer[376]: every_chain_get_PIC16F1704_freq_new Dec 28 02:12:34 (none) local0.notice cgminer[376]: set_frequency: frequency = 537 Dec 28 02:12:34 (none) local0.notice cgminer[376]: software_set_address_chain: chain 0 has 60 ASIC, and addrInterval is 1 Dec 28 02:12:34 (none) local0.notice cgminer[376]: Now Set Chain Address Dec 28 02:12:34 (none) local0.notice cgminer[376]: software_set_address_chain: chain 1 has 60 ASIC, and addrInterval is 1 Dec 28 02:12:34 (none) local0.notice cgminer[376]: Now Set [1] Chain Address Dec 28 02:12:35 (none) local0.notice cgminer[376]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 1 Dec 28 02:12:35 (none) local0.notice cgminer[376]: Now Set [2] Chain Address Dec 28 02:12:36 (none) local0.notice cgminer[376]: software_set_address_chain: chain 3 has 0 ASIC, and addrInterval is 1 Dec 28 02:12:36 (none) local0.notice cgminer[376]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Dec 28 02:12:36 (none) local0.notice cgminer[376]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Dec 28 02:12:36 (none) local0.notice cgminer[376]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Dec 28 02:12:36 (none) local0.notice cgminer[376]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Dec 28 02:12:36 (none) local0.notice cgminer[376]: select_core_to_check_temperature: diode_mux_sel = 4, vdd_mux_sel = 0 Dec 28 02:12:36 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Dec 28 02:12:36 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Dec 28 02:12:36 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Dec 28 02:12:36 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Dec 28 02:12:36 (none) local0.notice cgminer[376]: 0 calibration_sensor_offset_chain Dec 28 02:12:36 (none) local0.notice cgminer[376]: chain:0 local:27 remote:32 Dec 28 02:12:36 (none) local0.warn cgminer[376]: Chain 0 set_temperature_offset_value_chain_sensor Dec 28 02:12:37 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : -5, Dec 28 02:12:37 (none) local0.notice cgminer[376]: chain:0 local:27 remote:27 Dec 28 02:12:37 (none) local0.warn cgminer[376]: Chain 0 set_temperature_offset_value_chain_sensor Dec 28 02:12:37 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : -5, Dec 28 02:12:37 (none) local0.notice cgminer[376]: 1 calibration_sensor_offset_chain Dec 28 02:12:38 (none) local0.notice cgminer[376]: chain:1 local:26 remote:31 Dec 28 02:12:38 (none) local0.warn cgminer[376]: Chain 1 set_temperature_offset_value_chain_sensor Dec 28 02:12:38 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : -5, Dec 28 02:12:38 (none) local0.notice cgminer[376]: chain:1 local:26 remote:25 Dec 28 02:12:38 (none) local0.warn cgminer[376]: Chain 1 set_temperature_offset_value_chain_sensor Dec 28 02:12:38 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : -4, Dec 28 02:12:38 (none) local0.notice cgminer[376]: 2 calibration_sensor_offset_chain Dec 28 02:12:39 (none) local0.notice cgminer[376]: chain:2 local:26 remote:31 Dec 28 02:12:39 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain_sensor Dec 28 02:12:39 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -5, Dec 28 02:12:39 (none) local0.notice cgminer[376]: chain:2 local:26 remote:26 Dec 28 02:12:39 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain_sensor Dec 28 02:12:40 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -5, Dec 28 02:12:40 (none) local0.warn cgminer[376]: Chain 0 set_temperature_offset_value_chain Dec 28 02:12:40 (none) local0.warn cgminer[376]: Chain 0 set_temperature_offset_value_chain_sensor Dec 28 02:12:40 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : -5, Dec 28 02:12:40 (none) local0.warn cgminer[376]: Chain 1 set_temperature_offset_value_chain Dec 28 02:12:40 (none) local0.warn cgminer[376]: Chain 1 set_temperature_offset_value_chain_sensor Dec 28 02:12:40 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : -4, Dec 28 02:12:40 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain Dec 28 02:12:40 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain_sensor Dec 28 02:12:41 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -5, Dec 28 02:12:41 (none) local0.notice cgminer[376]: frequency = '537' Dec 28 02:12:41 (none) local0.notice cgminer[376]: dev.timeout = 562356 us Dec 28 02:12:41 (none) local0.notice cgminer[376]: open_core_chain Dec 28 02:12:41 (none) local0.notice cgminer[376]: open_core_chain Dec 28 02:12:41 (none) local0.notice cgminer[376]: open_core_chain Dec 28 02:12:41 (none) local0.notice cgminer[376]: open_core_chain Dec 28 02:12:44 (none) local0.err cgminer[376]: cgminer time error total_secs = 1514427164.591052 last_total_secs = 1.000000 Dec 28 02:12:54 (none) local0.warn cgminer[376]: Waiting for work to be available from pools. Dec 28 02:13:44 (none) local0.err cgminer[376]: No servers were found that could be used to get work from. Dec 28 02:13:44 (none) local0.err cgminer[376]: Please check the details from the list below of the servers you have input Dec 28 02:13:44 (none) local0.err cgminer[376]: Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers Dec 28 02:13:44 (none) local0.warn cgminer[376]: Pool: 0 URL: stratum+tcp://x11.eu.nicehash.com:3336 User: 3F3FMawERU9R83TSJDVpayJR6fCbzFvXUC.miner2 Password: x Dec 28 02:13:44 (none) local0.warn cgminer[376]: Pool: 1 URL: stratum+tcp://x11.eu.nicehash.com:3336 User: 3F3FMawERU9R83TSJDVpayJR6fCbzFvXUC.miner2 Password: x Dec 28 02:13:44 (none) local0.warn cgminer[376]: Pool: 2 URL: stratum+tcp://x11.eu.nicehash.com:3336 User: 3F3FMawERU9R83TSJDVpayJR6fCbzFvXUC.miner2 Password: x Dec 28 02:13:44 (none) local0.err cgminer[376]: No servers could be used! Exiting. Dec 28 02:13:50 (none) local0.err cgminer: Miner compile time: Mon Nov 20 17:06:56 CST 2017 type: Antminer D3 Dec 28 02:13:50 (none) local0.warn cgminer: Started cgminer 4.9.0 Dec 28 02:13:50 (none) local0.warn cgminer[8550]: bitmain_DASH_init Dec 28 02:13:50 (none) local0.err cgminer[8550]: FAN1 too slow ... Dec 28 02:13:50 (none) local0.err cgminer[8550]: FAN2 too slow ... Dec 28 02:13:51 (none) local0.err cgminer[8550]: FAN1 too slow ... Dec 28 02:13:51 (none) local0.err cgminer[8550]: FAN2 too slow ... Dec 28 02:13:51 (none) local0.err cgminer[8550]: FAN1 too slow ... Dec 28 02:13:52 (none) local0.err cgminer[8550]: FAN1 too slow ... Dec 28 02:13:52 (none) local0.err cgminer[8550]: FAN1 too slow ... Dec 28 02:13:53 (none) local0.err cgminer[8550]: FAN1 too slow ... Dec 28 02:13:53 (none) local0.err cgminer[8550]: FAN1 too slow ... Dec 28 02:13:54 (none) local0.err cgminer[8550]: FAN1 too slow ... Dec 28 02:13:54 (none) local0.err cgminer[8550]: FAN1 too slow ... Dec 28 02:13:55 (none) local0.warn cgminer[8550]: check_fan_speed OK Dec 28 02:13:55 (none) local0.notice cgminer[8550]: detected at /sys/class/gpio/gpio51/value chain 0 Dec 28 02:13:55 (none) local0.notice cgminer[8550]: detected at /sys/class/gpio/gpio48/value chain 1 Dec 28 02:13:55 (none) local0.notice cgminer[8550]: detected at /sys/class/gpio/gpio47/value chain 2 Dec 28 02:13:55 (none) local0.notice cgminer[8550]: detect total chain num 3 Dec 28 02:13:55 (none) local0.notice cgminer[8550]: i2c init ok Dec 28 02:13:55 (none) local0.notice cgminer[8550]: check_whether_need_update_pic_program Dec 28 02:13:56 (none) local0.notice cgminer[8550]: reset_PIC16F1704_pic_new ok Dec 28 02:13:57 (none) local0.notice cgminer[8550]: jump_from_loader_to_app_PIC16F1704_new ok Dec 28 02:13:57 (none) local0.notice cgminer[8550]: get_PIC16F1704_software_version_new ok, version = 0x81 Dec 28 02:13:58 (none) local0.notice cgminer[8550]: reset_PIC16F1704_pic_new ok Dec 28 02:13:59 (none) local0.notice cgminer[8550]: jump_from_loader_to_app_PIC16F1704_new ok Dec 28 02:13:59 (none) local0.notice cgminer[8550]: get_PIC16F1704_software_version_new ok, version = 0x81 Dec 28 02:14:00 (none) local0.notice cgminer[8550]: reset_PIC16F1704_pic_new ok Dec 28 02:14:01 (none) local0.notice cgminer[8550]: jump_from_loader_to_app_PIC16F1704_new ok Dec 28 02:14:01 (none) local0.notice cgminer[8550]: get_PIC16F1704_software_version_new ok, version = 0x81 Dec 28 02:14:01 (none) local0.notice cgminer[8550]: every_chain_reset_PIC16F1704_pic_new Dec 28 02:14:02 (none) local0.notice cgminer[8550]: reset_PIC16F1704_pic_new ok Dec 28 02:14:04 (none) local0.notice cgminer[8550]: reset_PIC16F1704_pic_new ok Dec 28 02:14:05 (none) local0.notice cgminer[8550]: reset_PIC16F1704_pic_new ok Dec 28 02:14:05 (none) local0.notice cgminer[8550]: every_chain_jump_from_loader_to_app_PIC16F1704_new Dec 28 02:14:06 (none) local0.notice cgminer[8550]: jump_from_loader_to_app_PIC16F1704_new ok Dec 28 02:14:06 (none) local0.notice cgminer[8550]: jump_from_loader_to_app_PIC16F1704_new ok Dec 28 02:14:07 (none) local0.notice cgminer[8550]: jump_from_loader_to_app_PIC16F1704_new ok Dec 28 02:14:07 (none) local0.notice cgminer[8550]: every_chain_enable_PIC16F1704_dc_dc_new Dec 28 02:14:07 (none) local0.notice cgminer[8550]: pic_heart_beat_func_new Dec 28 02:14:08 (none) local0.notice cgminer[8550]: enable_PIC16F1704_dc_dc_new ok Dec 28 02:14:08 (none) local0.notice cgminer[8550]: enable_PIC16F1704_dc_dc_new ok Dec 28 02:14:08 (none) local0.notice cgminer[8550]: enable_PIC16F1704_dc_dc_new ok Dec 28 02:14:09 (none) local0.notice cgminer[8550]: reset_all_hash_board Dec 28 02:14:09 (none) local0.notice cgminer[8550]: tty_init Dec 28 02:14:09 (none) local0.notice cgminer[8550]: tty_init_chain Dec 28 02:14:09 (none) local0.notice cgminer[8550]: tty_init_chain chainid = 0 Dec 28 02:14:09 (none) local0.err cgminer[8550]: create rx read thread for chain 0 ok Dec 28 02:14:09 (none) local0.notice cgminer[8550]: Start A New Asic Response.Chain Id:[0] Dec 28 02:14:10 (none) local0.err cgminer[8550]: create tx read thread for chain 0 ok Dec 28 02:14:10 (none) local0.notice cgminer[8550]: open device over Dec 28 02:14:10 (none) local0.notice cgminer[8550]: tty_init_chain Dec 28 02:14:10 (none) local0.notice cgminer[8550]: tty_init_chain chainid = 1 Dec 28 02:14:10 (none) local0.err cgminer[8550]: create rx read thread for chain 1 ok Dec 28 02:14:10 (none) local0.notice cgminer[8550]: Start A New Asic Response.Chain Id:[1] Dec 28 02:14:10 (none) local0.err cgminer[8550]: create tx read thread for chain 1 ok Dec 28 02:14:10 (none) local0.notice cgminer[8550]: open device over Dec 28 02:14:10 (none) local0.notice cgminer[8550]: tty_init_chain Dec 28 02:14:10 (none) local0.notice cgminer[8550]: tty_init_chain chainid = 2 Dec 28 02:14:10 (none) local0.err cgminer[8550]: create rx read thread for chain 2 ok Dec 28 02:14:10 (none) local0.notice cgminer[8550]: Start A New Asic Response.Chain Id:[2] Dec 28 02:14:10 (none) local0.err cgminer[8550]: create tx read thread for chain 2 ok Dec 28 02:14:10 (none) local0.notice cgminer[8550]: open device over Dec 28 02:14:10 (none) local0.notice cgminer[8550]: tty_init_chain Dec 28 02:14:10 (none) local0.notice cgminer[8550]: open device over Dec 28 02:14:10 (none) local0.notice cgminer[8550]: check_every_chain_asic_number Dec 28 02:14:11 (none) local0.warn cgminer[8550]: check_asic_reg: Chain0 has 60 ASICs Dec 28 02:14:11 (none) local0.warn cgminer[8550]: check_asic_reg: Chain1 has 60 ASICs Dec 28 02:14:11 (none) local0.warn cgminer[8550]: check_asic_reg: Chain2 has 60 ASICs Dec 28 02:14:12 (none) local0.notice cgminer[8550]: calculate_address_interval: temp_asic_number = 64, addrInterval = 1 Dec 28 02:14:12 (none) local0.notice cgminer[8550]: calculate_address_interval: CHIP_OFFSET = 0x04000000, CORE_OFFSET = 0x00800000 Dec 28 02:14:12 (none) local0.notice cgminer[8550]: set_ticket_mask ticket_mask = 0x0000001b Dec 28 02:14:12 (none) local0.notice cgminer[8550]: every_chain_get_PIC16F1704_freq_new Dec 28 02:14:14 (none) local0.notice cgminer[8550]: set_frequency: frequency = 537 Dec 28 02:14:14 (none) local0.notice cgminer[8550]: software_set_address_chain: chain 0 has 60 ASIC, and addrInterval is 1 Dec 28 02:14:14 (none) local0.notice cgminer[8550]: Now Set Chain Address Dec 28 02:14:15 (none) local0.notice cgminer[8550]: software_set_address_chain: chain 1 has 60 ASIC, and addrInterval is 1 Dec 28 02:14:15 (none) local0.notice cgminer[8550]: Now Set [1] Chain Address Dec 28 02:14:16 (none) local0.notice cgminer[8550]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 1 Dec 28 02:14:16 (none) local0.notice cgminer[8550]: Now Set [2] Chain Address Dec 28 02:14:17 (none) local0.notice cgminer[8550]: software_set_address_chain: chain 3 has 0 ASIC, and addrInterval is 1 Dec 28 02:14:17 (none) local0.notice cgminer[8550]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Dec 28 02:14:17 (none) local0.notice cgminer[8550]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Dec 28 02:14:17 (none) local0.notice cgminer[8550]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Dec 28 02:14:17 (none) local0.notice cgminer[8550]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Dec 28 02:14:17 (none) local0.notice cgminer[8550]: select_core_to_check_temperature: diode_mux_sel = 4, vdd_mux_sel = 0 Dec 28 02:14:17 (none) local0.notice cgminer[8550]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Dec 28 02:14:17 (none) local0.notice cgminer[8550]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Dec 28 02:14:17 (none) local0.notice cgminer[8550]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Dec 28 02:14:17 (none) local0.notice cgminer[8550]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Dec 28 02:14:17 (none) local0.notice cgminer[8550]: 0 calibration_sensor_offset_chain Dec 28 02:14:17 (none) local0.notice cgminer[8550]: chain:0 local:44 remote:43 Dec 28 02:14:17 (none) local0.warn cgminer[8550]: Chain 0 set_temperature_offset_value_chain_sensor Dec 28 02:14:17 (none) local0.notice cgminer[8550]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 01, Dec 28 02:14:17 (none) local0.notice cgminer[8550]: 1 calibration_sensor_offset_chain Dec 28 02:14:18 (none) local0.notice cgminer[8550]: chain:1 local:42 remote:42 Dec 28 02:14:18 (none) local0.warn cgminer[8550]: Chain 1 set_temperature_offset_value_chain_sensor Dec 28 02:14:18 (none) local0.notice cgminer[8550]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : 00, Dec 28 02:14:18 (none) local0.notice cgminer[8550]: 2 calibration_sensor_offset_chain Dec 28 02:14:18 (none) local0.notice cgminer[8550]: chain:2 local:45 remote:44 Dec 28 02:14:18 (none) local0.warn cgminer[8550]: Chain 2 set_temperature_offset_value_chain_sensor Dec 28 02:14:19 (none) local0.notice cgminer[8550]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : 01, Dec 28 02:14:19 (none) local0.warn cgminer[8550]: Chain 0 set_temperature_offset_value_chain Dec 28 02:14:19 (none) local0.warn cgminer[8550]: Chain 0 set_temperature_offset_value_chain_sensor Dec 28 02:14:19 (none) local0.notice cgminer[8550]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 01, Dec 28 02:14:19 (none) local0.warn cgminer[8550]: Chain 1 set_temperature_offset_value_chain Dec 28 02:14:19 (none) local0.warn cgminer[8550]: Chain 1 set_temperature_offset_value_chain_sensor Dec 28 02:14:19 (none) local0.notice cgminer[8550]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : 00, Dec 28 02:14:19 (none) local0.warn cgminer[8550]: Chain 2 set_temperature_offset_value_chain Dec 28 02:14:19 (none) local0.warn cgminer[8550]: Chain 2 set_temperature_offset_value_chain_sensor Dec 28 02:14:20 (none) local0.notice cgminer[8550]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : 01, Dec 28 02:14:20 (none) local0.notice cgminer[8550]: frequency = '537' Dec 28 02:14:20 (none) local0.notice cgminer[8550]: dev.timeout = 562356 us Dec 28 02:14:20 (none) local0.notice cgminer[8550]: open_core_chain Dec 28 02:14:20 (none) local0.notice cgminer[8550]: open_core_chain Dec 28 02:14:20 (none) local0.notice cgminer[8550]: open_core_chain Dec 28 02:14:20 (none) local0.notice cgminer[8550]: open_core_chain Dec 28 02:14:23 (none) local0.err cgminer[8550]: cgminer time error total_secs = 1514427263.549573 last_total_secs = 1.000000 Dec 28 02:14:33 (none) local0.warn cgminer[8550]: Waiting for work to be available from pools. Waiting for work to be available from pools. Are you sure you have a least one valid pool that's actually online? Not the pools website but the stratum server itself. Try putting in a known good pool and see what happens.

Alternate cryptocurrencies / Mining (Altcoins) / Re: Antminer D3 Blissz firmware (10/12 v1.12 update)

on: December 27, 2017, 03:46:43 AM

Quote from: vnish on December 27, 2017, 03:13:05 AM Quote from: deezhere on December 27, 2017, 01:24:27 AM Quote from: mikespax on December 27, 2017, 12:34:31 AM Sorry, just again bringing up the profit switching capabilities that are out there. This is from AwesomeMiner. External Profit Switching (for ASIC's and Antminers) Awesome Miner will not add or change any pools on the miner. The profit switcher will only look at the pools already defined on the miner and change the priority of them. The priority is set based on profitability. The profitability of the pool must be known to Awesome Miner, either by using one of the supported multi-pools or by using a coin listed on the Coins tab. I know this is what's quoted on the awesomeminer site but you can create your own pool groups and then assign that group to a external miner and set that up for profit switching. You just need to create a new profit switching profile. I currently have 8 pools assigned to my D3's through awesomeminer and it auto profit switches between 7 of them without any issues, prohashing is the only pool that isn't picked up by the profit switching profile. The only deal is when you reboot an external miner you have to add the pool group back to that miner once it's back online. You can meke it easier. Using awesomeminer tool bar, you can define deafult pools through api. Select asic, enter login and pass for api access choose a defult pool as a pool group, the restart your miner and you will have your 8 pools even if asic reboots. Thanks. I knew there had to be a way.

Alternate cryptocurrencies / Mining (Altcoins) / Re: Antminer D3 Blissz firmware (10/12 v1.12 update)

on: December 27, 2017, 01:24:27 AM

Quote from: mikespax on December 27, 2017, 12:34:31 AM Sorry, just again bringing up the profit switching capabilities that are out there. This is from AwesomeMiner. External Profit Switching (for ASIC's and Antminers) Awesome Miner will not add or change any pools on the miner. The profit switcher will only look at the pools already defined on the miner and change the priority of them. The priority is set based on profitability. The profitability of the pool must be known to Awesome Miner, either by using one of the supported multi-pools or by using a coin listed on the Coins tab. I know this is what's quoted on the awesomeminer site but you can create your own pool groups and then assign that group to a external miner and set that up for profit switching. You just need to create a new profit switching profile. I currently have 8 pools assigned to my D3's through awesomeminer and it auto profit switches between 7 of them without any issues, prohashing is the only pool that isn't picked up by the profit switching profile. The only deal is when you reboot an external miner you have to add the pool group back to that miner once it's back online.

Alternate cryptocurrencies / Mining (Altcoins) / Re: Antminer D3 Blissz firmware (10/12 v1.12 update)

on: December 21, 2017, 01:09:36 AM

Quote from: UnluckyD3Miner on December 20, 2017, 06:51:41 PM Has anyone had to do a warranty return/repair? I have a hashboard that doesn't show up anymore on the status page. This is what happened: I was running Blissz and it was showing me inflated hashrates on chain0 and failing with xxxx's. I rebooted and changed frequencies/voltages but nothing seemed to help. I switched back to the stock firmware and after some trial and error I was able to get chain0 to run normally. It ran for a couple of days and then just disappeared from the status page. I saw in the kernel log that it shows chain0 as having an asic count of 0 instead of 60. Also, I tried switching out the cables connecting the chain with cables that are known to work, and changing the slot it is connected to. I saw Bitmain also recommends reflashing the stock firmware and letting it run for 20 minutes, so I tried that as well. None of that worked, so it would seem the board is dead. I don't know if I need to post on their support forum first asking for help, or if I can go ahead and create a help ticket, disassemble the D3 (removing chain0) and package up the faulty hashboard. Anyone know what the standard procedure is? Yes, I've had to ship back 5 hashboards so far. Don't listen to other posters saying it's worthless. If you're in the US the repair site is in California so shipping cost through fedex isn't bad. I've already received 1 board back and have 3 more on the way already. Average turn around time seems to be 2.5 to 3 weeks. If your board is dead you should absolutely open a ticket at support.bitmain.com and wait for a response. It cost me $9 in shipping costs for a single hashboard to be fully replaced. Bitmain then gave me a $9 coupon to use on their site. Get your board fixed or replaced, there's no reason not to.

Alternate cryptocurrencies / Mining (Altcoins) / Re: Antminer D3 Blissz firmware (10/12 v1.12 update)

on: December 12, 2017, 12:51:53 PM

Quote from: LiteMine on December 12, 2017, 02:43:05 AM Quote from: deezhere on December 11, 2017, 06:25:49 PM Quote from: LiteMine on December 11, 2017, 06:16:21 PM Quote from: TEmp69 on December 11, 2017, 09:52:29 AM @Blissz I really like what you have done modifiying the firmware but i have one suggestions, which i am pretty sure will ease the issue some ppl have when configuring theire miners regarding the dev fee. I am all for it and i am pretty sure that others dont mind either that you get a fair share for your work. I have 5 D3's myself and configuring those machines aint that easy, because each of them has different settings to be applied that the HW errors disappear. The issue i have is, that after each reboot / configuration change (voltage, adresses, ....) you start mining on your dev pools (after some seconds), this makes it intense to check if my OWN settings are valid. My suggestion is, please start mining your 1.5% fair share not at each and every reboot / configuration change, but once the miner has run for its 2 hours. So i am only asking you to change the first time you mine for yourself, after 2h you start with your rotation. Thanks again. He can't set it to 2 hrs before mining to his pool or people would just reboot their miners every 1 hr 59 min and only lose 13 min per day of mining (based on a 30 sec restart), versus him mining for 22 min a day (1 min 30 sec every 2 hrs like he stated). The breakeven point is about 33 minutes, so he could set it to 20 min and people could configure miners for some time without paying any excess fees. 22 min dev mining per day / 30 sec reboot = 44 restarts/day 24 hr/day / 44 restarts/day = 0.5454 hr/restart = approx 33 min/restart If the reboot takes 90 sec, then he could set it to 1 hr 39 min, but ppl still might restart often just to spite the dev. So he sets a short amount of time before it mines to his pool. Wouldn't it be easier to just edit the hosts file of the miner to trick it into thinking the devpool address is the same as the primary pool address? My intention was not to circumvent anything, but just to explain why it's a short period of time before dev mines his pool. I fully support everything being done here, my miners are waaaay cooler and quieter, I'm very happy with the updates and responsiveness. I'm leaving the dev fee enabled as well as I also want to support the efforts. Just simply pointing out that people timing reboots to stop the dev fee is silly when there are easier methods. I do hope that eventually blissz will give the option to either pay a 1 time fee upfront rather than a lifetime of dev fee mining. I also hope that this work will soon start to focus on isolating individual algos contained within X11 with the option to pick which of the 11 we would like to mine with so the profitability of these can be recovered. I know new algos won't happen but I don't see any reason we can't isolate and use only one of the 11 that these ASIC chips are already capable of.

Alternate cryptocurrencies / Mining (Altcoins) / Re: Antminer D3 Blissz firmware (10/12 v1.12 update)

on: December 11, 2017, 06:25:49 PM

Quote from: LiteMine on December 11, 2017, 06:16:21 PM Quote from: TEmp69 on December 11, 2017, 09:52:29 AM @Blissz I really like what you have done modifiying the firmware but i have one suggestions, which i am pretty sure will ease the issue some ppl have when configuring theire miners regarding the dev fee. I am all for it and i am pretty sure that others dont mind either that you get a fair share for your work. I have 5 D3's myself and configuring those machines aint that easy, because each of them has different settings to be applied that the HW errors disappear. The issue i have is, that after each reboot / configuration change (voltage, adresses, ....) you start mining on your dev pools (after some seconds), this makes it intense to check if my OWN settings are valid. My suggestion is, please start mining your 1.5% fair share not at each and every reboot / configuration change, but once the miner has run for its 2 hours. So i am only asking you to change the first time you mine for yourself, after 2h you start with your rotation. Thanks again. He can't set it to 2 hrs before mining to his pool or people would just reboot their miners every 1 hr 59 min and only lose 13 min per day of mining (based on a 30 sec restart), versus him mining for 22 min a day (1 min 30 sec every 2 hrs like he stated). The breakeven point is about 33 minutes, so he could set it to 20 min and people could configure miners for some time without paying any excess fees. 22 min dev mining per day / 30 sec reboot = 44 restarts/day 24 hr/day / 44 restarts/day = 0.5454 hr/restart = approx 33 min/restart If the reboot takes 90 sec, then he could set it to 1 hr 39 min, but ppl still might restart often just to spite the dev. So he sets a short amount of time before it mines to his pool. Wouldn't it be easier to just edit the hosts file of the miner to trick it into thinking the devpool address is the same as the primary pool address?

Alternate cryptocurrencies / Mining (Altcoins) / Re: Antminer D3 Blissz firmware (08/12 v1.11 update)

on: December 09, 2017, 04:58:34 PM

Quote from: ruptan on December 09, 2017, 04:31:15 PM Seems like Bitmain has a backdoor to their machine. Anyone sure about The Antbleed Backdoor? http://www.antbleed.com/ Interesting. Seems like an easy fix.

Alternate cryptocurrencies / Mining (Altcoins) / Re: Antminer D3 Blissz firmware (08/12 v1.11 update)

on: December 08, 2017, 09:53:22 PM

Quote from: mtaboneweb on December 08, 2017, 05:51:11 PM Hey guys, Apologies since I'm late to the game here but hoping someone can help me out. I have a D3 (19.3G) that has been buggy to say the least over the last week. Question here would be if anyone think the firmware here may help me and what setting may be recommended as a starting point. Symptoms... It started with lots of HW errors then turned into 3rd board not showing all the chips (55/60). Thousands of errors happening in a very short timeframe. Sometimes over night that board will go to X's. Reboot used to fix it but then started showing less chips. What I tried Latest firmware from Bitmain Not powering the 3rd board. This worked fine for a few hours then sometime over night the 2nd board went to all X's. Reboot this morning and now the 2nd board is experiencing the same issues I had with the 3rd board showing 55/60 chips. It ran fine for a couple of weeks but now I've got nothing but headache with it and at $6-$7/day profits I'm really frustrated having paid $1600 for it and made less than $150 so far. This is the PSU I'm using since I bought this from a guy who claimed it was new off of craigslist. I had to buy my own PSU and this is what he suggested. I have been running the the 1200W on boards 2-3 and the 750W on board 1 and the control board. Both units run well under the max of 1950W between the 2. I power on the 1200W first then the 750W. https://www.parallelminer.com/product/now-with-rev7-board-1950watt-110v240v-80-gold-power-supply-for-antminer-d3/ Like I said, I'm new so please go easy on me. My concerns are raised because I don't know if it's something "I'm" doing to this or it's just the nature of the D3. Not to mention I have since ordered (from Bitmain) 3 new S9 ASICs. One for end of December and 2 for end of January. 6 month warranty and due to make a good amount but I'm concerned I'll have issues like with the D3. ebay is fetching a good price though so my plan was to unbox 1 S9, run it and if problems I could always dump the other 2 on ebay. Many thanks to all for your efforts and I appreciate your time. I've now had this exact same scenario happen with 5 of my D3's. I followed all trouble shooting steps including moving the non-working boards over to chain 0 on the controller which was still working and then powering the machine with on that hash board. After starting the machine with only the bad hash board connected it still wouldn't show up. So far over the last 2 weeks I've now shipped a total of 5 defective hashboards back to bitmain for repair. Firmware isn't going to fix your problem. You need to follow the troubleshooting steps outlined by bitmain, identify the defective boards, open a support ticket at support.bitmain.com and wait for a response. Then they will instruct you to open a repair ticket, remove the defective boards and ship them back for repair. Sorry this has happened to you but know you're definitely not alone. I have 8 D3's and 5 of them now have defective boards.

Alternate cryptocurrencies / Mining (Altcoins) / Re: Antminer D3 Blissz firmware (02/11 v1.1 update)

on: December 07, 2017, 01:00:05 PM

Quote from: flowerpower84 on December 07, 2017, 12:17:17 PM Quote from: JACKSEG on December 07, 2017, 11:54:51 AM Quote from: flowerpower84 on December 07, 2017, 11:45:29 AM Hi, to all Yesterday my Antminer D3 Chain #3 is disappeared! Hi, Can you control the power lines in chain 3 ? Switch with power lines in chain 2 or 1. If it works, it's a power supply problem. I have switched the power lines but same problem, in kernel log I see this: I have also switched flat cables, but same problem. In the last I have insert the chain #3 flat cable in the last free slot (address #3) [chain #1 --> is chain 0, chain #2 --> is chain 1, chain #3 -->is chain 2] but same problem, in kernel log I see this: Zero Asic for chain #3. Why? And why I have same hashrate with only 2 working chains? I don't understand I've had this same problem with 4 of my D3 miners now. I've done all of the troubleshooting, swapped power supplies with known good ones, moved hashboards, cables and even ran the miners with only the non-working hashboard connected which still showed in the global hashrate that it was hashing but the chain was showing 0 ASIC in the kernel log. I've shipped all 4 of those hashboards back to bitmain for repair.

Pages: [1]