Have to say i was honored to be invited to the same training Sky was (phillipma partner).
I'm based in South America, and my post in the spanish section should be up later today.
Thanks again Steven for considering me for this i can say unique opportunity.
Congratulations! Yes, it is very refreshing to see a miner manufacturer be so open to their customer base. Halong/Little Dragon LLC -- ya paying attention? Considering the modular design it makes sense to train people to be able to work as regional or local parts/repair-exchange depots and do it at Canaan's expense. After all - it *is* a deductible marketing cost so why not  Given the 2-year warranty there WILL be things that go bad from time to time. For me it was 1 dead fan on a 1 year old 721. Fan/shroud replaced no charge. This does wonders further building up the already pretty much sterling Brand name. To me so far Canaan's design & build quality, service, and openness with customers has been exemplary, the massive order fup last August being a prime case in-point. They handled that overload marvelously. |
|
|
|
Welp!!! After a serious windstorm, and 2.5 days of no power........I'm back!!! Thank God (or whatever you believe in) for the 5nd!!! Been fun around Redford as well. My GF got her power back on last night after being out for 21hrs. Internet back on today about noon. Had 2x 741's there that were just coming back online after her internet had been out for 5 days prior from the last blustery day here. Anywho, changed the miners there from 2x 741's to 2x 821's using command line voltage of -1. Was ~15TH from her feeding the farm now 20ish and I believe a bit lower power draw ta boot. The 741's will join their brethren in main farm at work replacing a flaky batch-1 T9 + a bit more there.. |
|
|
|
I figured out my nya issue. embarrassingly enough, there was an extra space after the 3333 .
oh boy...
Ja. Be careful when using copy/paste. Many times the selection will include a space. Same applies when c/p addresses to pay to/receive from. Always check it. Been there done that a few times before catching on. |
|
|
|
|
No matter what you will not lose credit for work done. If the values is over the dust threshold you *will* be paid for it to the address you used.
If you are registered and just first used the address as a worker name and now change the worker name to be your username (eg in my case Fuzzy.minerID), yes the ramp up will start over but because the old name is ramping down and still paying to the wallet address at the same time earnings should be the same.
|
|
|
|
snip
I hope now everything is clear. Still need answer about my Clearco ST 50 oil as a coolant.
Thanks,
If you mean ST 50's compatibility with electronic components, so far I've seen zero issues. As I posted in the original immersion cooling thread we have high voltage power supplies putting out over 10's of kw waste heat each that use it. Components in those range from epoxy encased diodes, various wiring with PVC (most common general wiring used everywhere), polyethylene, and silicon jacket wiring, nylon connectors, transformer varnish and potting epoxy, silicon rubber seals on electrolytic capacitors. Zero changes in their properties seen after so far >60k hrs on the oldest individual systems. What I would be careful of is silicon rubber glue or sealant aka RTV joints - That tends to gel then crumble so use other ways to seal and bond things. Based on that *if* I was to go with liquid cooling for a large installation I would definitely use the Clearco fluids. Again, because at least the ST50 is proven to not harm components/wiring, is water thin for easy pumping and great flow properties, has great thermal transfer specs and very high ignition point. Also, while certainly not cheap it costs about 1/10th what Novec costs and more important to me does not evaporate/require a vapor-tight system. Ja if there is a leak you have to contain/clean it up whereas even at a moderate 75F or more Novec will quickly go away on its own but there is also a chance to capture the fluid and filter/re-use it. Have I yet put any of my farm in it? No. Why is because I am at my power available limit and normal ventilation works fine. Do be aware that as an industrial fluid it is NOT sold to private individuals. Clearco and their distributors will only sell to registered companies. |
|
|
|
At least you *are* learning though Kudos for that! Too many come here just to piss and moan without learning anything from their experiences |
|
|
|
hey man thank you very much for the help! appreciate it since i just try to figure out how to move on from here with my first antminer  does flashing those firmwares mess up my warranty? The issue with the fan is weird. The intake fan wasnt working and we replaced it with a new one - still didnt work. We then switched the new (still not working intake) fan cable with the old (still working exhaust fan) --> the exhaust fan still worked // intake still didnt work .. makes no sense to me thanks guys. i might just have gotten a messed up miner from ebay. not sure.I dont think i myself broke it by simply turning it on and off 3 times?! lol <3 to everyone Where did you get the fan from and is it the correct replacement? These are not regular PC case fans... And have you now learned to never buy a miner from ebay vs only buying direct from Bitmain or in the case of Canaan's Avalons, their Authorized distributors? A little thing called Factory Warranty is very nice. |
|
|
|
<massive text wall snip>
Dude! Learn to use the code tag which looks like #That wall then becomes [ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.14.0-xilinx-ge8a2f71-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #82 SMP PREEMPT Tue May 16 19:49:53 CST 2017
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Xilinx Zynq
[ 0.000000] cma: CMA: reserved 128 MiB at 16800000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 126976
[ 0.000000] free_area_init_node: node 0, pgdat c0740a40, node_mem_map debd8000
[ 0.000000] Normal zone: 992 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 126976 pages, LIFO batch:31
[ 0.000000] PERCPU: Embedded 8 pages/cpu @debc1000 s9088 r8192 d15488 u32768
[ 0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096
[ 0.000000] pcpu-alloc:
0
1
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 125984
[ 0.000000] Kernel command line: noinitrd mem=496M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 364356K/507904K available (5032K kernel code, 283K rwdata, 1916K rodata, 204K init, 258K bss, 143548K reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xdf800000 - 0xff000000 ( 504 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xdf000000 ( 496 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc06d1374 (6949 kB)
[ 0.000000] .init : 0xc06d2000 - 0xc0705380 ( 205 kB)
[ 0.000000] .data : 0xc0706000 - 0xc074cf78 ( 284 kB)
[ 0.000000] .bss : 0xc074cf84 - 0xc078d9fc ( 259 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] ps7-slcr mapped to df802000
[ 0.000000] zynq_clock_init: clkc starts at df802100
[ 0.000000] Zynq clock init
[ 0.000015] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[ 0.000309] ps7-ttc #0 at df804000, irq=43
[ 0.000623] Console: colour dummy device 80x30
[ 0.000655] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328)
[ 0.040211] pid_max: default: 32768 minimum: 301
[ 0.040437] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.040457] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.042630] CPU: Testing write buffer coherency: ok
[ 0.042983] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.043046] Setting up static identity map for 0x4c4b00 - 0x4c4b58
[ 0.043269] L310 cache controller enabled
[ 0.043289] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[ 0.121040] CPU1: Booted secondary processor
[ 0.210230] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.210364] Brought up 2 CPUs
[ 0.210384] SMP: Total of 2 processors activated.
[ 0.210392] CPU: All CPU(s) started in SVC mode.
[ 0.211067] devtmpfs: initialized
[ 0.213492] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.214745] regulator-dummy: no parameters
[ 0.223746] NET: Registered protocol family 16
[ 0.226013] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.228344] cpuidle: using governor ladder
[ 0.228358] cpuidle: using governor menu
[ 0.235915] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[ 0.237455] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.237469] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.237591] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000
[ 0.259677] bio: create slab <bio-0> at 0
[ 0.261421] vgaarb: loaded
[ 0.262146] SCSI subsystem initialized
[ 0.263044] usbcore: registered new interface driver usbfs
[ 0.263217] usbcore: registered new interface driver hub
[ 0.263448] usbcore: registered new device driver usb
[ 0.263976] media: Linux media interface: v0.10
[ 0.264137] Linux video capture interface: v2.00
[ 0.264389] pps_core: LinuxPPS API ver. 1 registered
[ 0.264401] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.264532] PTP clock support registered
[ 0.264902] EDAC MC: Ver: 3.0.0
[ 0.265972] Advanced Linux Sound Architecture Driver Initialized.
[ 0.269004] DMA-API: preallocated 4096 debug entries
[ 0.269018] DMA-API: debugging enabled by kernel config
[ 0.269104] Switched to clocksource arm_global_timer
[ 0.290586] NET: Registered protocol family 2
[ 0.291275] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.291332] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.291417] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.291467] TCP: reno registered
[ 0.291484] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.291522] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.291775] NET: Registered protocol family 1
[ 0.292134] RPC: Registered named UNIX socket transport module.
[ 0.292147] RPC: Registered udp transport module.
[ 0.292155] RPC: Registered tcp transport module.
[ 0.292163] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.292177] PCI: CLS 0 bytes, default 64
[ 0.292644] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[ 0.294714] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.296843] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.297037] msgmni has been set to 967
[ 0.297840] io scheduler noop registered
[ 0.297854] io scheduler deadline registered
[ 0.297896] io scheduler cfq registered (default)
[ 0.310360] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[ 0.310380] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.434911] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[ 1.002826] console [ttyPS0] enabled
[ 1.007126] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000
[ 1.014797] [drm] Initialized drm 1.1.0 20060810
[ 1.032066] brd: module loaded
[ 1.041535] loop: module loaded
[ 1.051400] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[ 1.057149] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[ 1.065333] libphy: XEMACPS mii bus: probed
[ 1.069880] ------------- phy_id = 0x3625e62
[ 1.074630] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[ 1.083281] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.089947] ehci-pci: EHCI PCI platform driver
[ 1.097172] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[ 1.104006] usbcore: registered new interface driver usb-storage
[ 1.110888] mousedev: PS/2 mouse device common for all mice
[ 1.116979] i2c /dev entries driver
[ 1.123955] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[ 1.129554] cpufreq_cpu0: failed to get cpu0 regulator: -19
[ 1.135440] Xilinx Zynq CpuIdle Driver started
[ 1.140321] sdhci: Secure Digital Host Controller Interface driver
[ 1.146414] sdhci: Copyright(c) Pierre Ossman
[ 1.150826] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.157556] mmc0: no vqmmc regulator found
[ 1.161603] mmc0: no vmmc regulator found
[ 1.199126] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[ 1.207835] usbcore: registered new interface driver usbhid
[ 1.213349] usbhid: USB HID core driver
[ 1.218087] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.224385] nand: Micron MT29F2G08ABAEAWP
[ 1.228348] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[ 1.234289] Bad block table found at page 131008, version 0x01
[ 1.240518] Bad block table found at page 130944, version 0x01
[ 1.246567] 3 ofpart partitions found on MTD device pl353-nand
[ 1.252349] Creating 3 MTD partitions on "pl353-nand":
[ 1.257444] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[ 1.265535] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[ 1.272869] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[ 1.281891] TCP: cubic registered
[ 1.285126] NET: Registered protocol family 17
[ 1.289858] Registering SWP/SWPB emulation handler
[ 1.295777] regulator-dummy: disabling
[ 1.300198] UBI: attaching mtd1 to ubi0
[ 1.826211] UBI: scanning is finished
[ 1.837943] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[ 1.845028] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.851790] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.858454] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.865332] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[ 1.871312] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.878420] UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 1134783803
[ 1.887463] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[ 1.896680] UBI: background thread "ubi_bgt0d" started, PID 1080
[ 1.896685] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 1.900763] ALSA device list:
[ 1.900767] No soundcards found.
[ 1.917147] UBIFS: background thread "ubifs_bgt0_0" started, PID 1082
[ 1.946354] UBIFS: recovery needed
[ 2.024148] UBIFS: recovery completed
[ 2.027818] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 2.033798] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.042874] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[ 2.052759] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.057788] UBIFS: media format: w4/r0 (latest is w4/r0), UUID B079DD56-06BB-4E31-8F5E-A6604F480DB2, small LPT model
[ 2.069087] VFS: Mounted root (ubifs filesystem) on device 0:11.
[ 2.076280] devtmpfs: mounted
[ 2.079405] Freeing unused kernel memory: 204K (c06d2000 - c0705000)
[ 2.920815] random: dd urandom read with 0 bits of entropy available
[ 3.319125]
[ 3.319125] bcm54xx_config_init
[ 3.929142]
[ 3.929142] bcm54xx_config_init
[ 7.929971] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[ 7.936080] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[ 25.417436] In axi fpga driver!
[ 25.420536] request_mem_region OK!
[ 25.423900] AXI fpga dev virtual address is 0xdf9fc000
[ 25.429006] *base_vir_addr = 0x8c510
[ 25.444171] In fpga mem driver!
[ 25.447243] request_mem_region OK!
[ 25.450856] fpga mem virtual address is 0xe2000000
[ 26.239135]
[ 26.239135] bcm54xx_config_init
[ 26.869157]
[ 26.869157] bcm54xx_config_init
[ 30.869983] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[ 30.876088] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
This is XILINX board. Totalram: 507527168
Detect 512MB control board of XILINX
DETECT HW version=0008c510
miner ID : 802c4c8415408814
Miner Type = S9
AsicType = 1387
real AsicNum = 63
use critical mode to search freq...
get PLUG ON=0x000000e0
Find hashboard on Chain[5]
Find hashboard on Chain[6]
Find hashboard on Chain[7]
set_reset_allhashboard = 0x0000ffff
Check chain[5] PIC fw version=0x03
Check chain[6] PIC fw version=0x03
Check chain[7] PIC fw version=0x03
chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[5] has freq in PIC and will jump over...
Chain[5] has core num in PIC
Chain[5] ASIC[26] has core num=1
Check chain[5] PIC fw version=0x03
chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[6] has freq in PIC and will jump over...
Chain[6] has core num in PIC
Chain[6] ASIC[15] has core num=15
Chain[6] ASIC[16] has core num=1
Chain[6] ASIC[34] has core num=2
Chain[6] ASIC[37] has core num=1
Chain[6] ASIC[45] has core num=1
Chain[6] ASIC[55] has core num=2
Check chain[6] PIC fw version=0x03
chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[7] has freq in PIC and will jump over...
Chain[7] has core num in PIC
Check chain[7] PIC fw version=0x03
get PIC voltage=91 on chain[5], value=890
get PIC voltage=91 on chain[6], value=890
get PIC voltage=91 on chain[7], value=890
set_reset_allhashboard = 0x00000000
chain[5] temp offset record: 62,0,0,0,0,0,37,28
chain[5] temp chip I2C addr=0x98
chain[5] has no middle temp, use special fix mode.
chain[6] temp offset record: 62,0,0,0,0,0,37,28
chain[6] temp chip I2C addr=0x98
chain[6] has no middle temp, use special fix mode.
chain[7] temp offset record: 62,0,0,0,0,0,37,28
chain[7] temp chip I2C addr=0x98
chain[7] has no middle temp, use special fix mode.
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
CRC error counter=0
set command mode to VIL
--- check asic number
After Get ASIC NUM CRC error counter=0
set_baud=0
The min freq=700
set real timeout 52, need sleep=379392
After TEST CRC error counter=0
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
search freq for 1 times, completed chain = 3, total chain num = 3
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
restart Miner chance num=2
waiting for receive_func to exit!
waiting for pic heart to exit!
bmminer not found= 1516 root 0:00 grep bmminer
bmminer not found, restart bmminer ...
This is user mode for mining
Detect 512MB control board of XILINX
Miner Type = S9
Miner compile time: Fri Nov 17 17:57:49 CST 2017 type: Antminer S9set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
set_reset_allhashboard = 0x0000ffff
miner ID : 802c4c8415408814
set_reset_allhashboard = 0x0000ffff
Checking fans!get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
get fan[2] speed=5160
Fatal Error: some Fan lost or Fan speed low!
Moderator's note: This post was edited by frodocooper to fix erroneous quote formatting. |
|
|
|
Ah. As it says to the left of May 4 -- that is your local time... |
|
|
|
|
Not missing anything, that pretty sums it up.
The one thing you *are* missing though is reliability. When they 1st came out the T9 (not T9+) was more reliable than the s9, only slightly slower and slightly more power hungry the the s9. More to the point the T9 is no longer more reliable - yay Bitmain...
Personally, now the only miners I buy are the Avalons from Canaan.io
Very very few problems reported with them, 2-year warranty and even better -- if something does go bad Canaan will send you the replacement part unlike BM that requires you to send the whole miner back to them.
|
|
|
|
You don't think they have resellers that buy from them in bulk? Official or not, those relationships most likely exist. That's just good business.
Yeah, I'm sure if you emailed them and said you wanted to buy like 2000 miners ASAP, they would be happy to work with you. The guy is right that there are no official resellers, but pretty much any business out there offers bulk discounts, especially when they aren't selling out their current stock. Moderator's note: This post was edited by frodocooper to remove a nested quote. "resellers" - yes, as in those who resell them on ebay, Amazon, etc. However they are NOT Factory Authorized re-sellers such as Canaan has set up. Huge difference in that non-FA resellers means ZERO FACTORY WARRANTY if you buy from them and the miner goes titsup. Maybe the reseller will help but odds are not because Bitmain only gives support to the original purchaser/user and does not support equipment that has been resold. Factory Authorized distributors like Canaan uses means that if there is a problem both the distributor and Canaan will back you up with full support/warranty. And btw, for Avalons that is a 2-year warranty. Personally, if I'm spending several thousand $$ I damn sure want a warranty! |
|
|
|
<snip> All I can say...It must be a nightmare for the English speakers to use Celsius Why? There are many free units conversions programs. My fav is https://joshmadison.com/convert-for-windows/ that converts just about any related engineering units to another. Aside from that just google the query eg. 'convert 30C to F' and ya get the answer... |
|
|
|
|
The sorcerer's work great. The fans higher pitch is noticeable over the miners but not bad. I have 6 and so far zero problems though of course the PSU has only been out less than a year.
|
|
|
|
Curious how you went about asking cannon to be a rep/trianer. I have approx 50 asic miners with more on the way and I work with a hosting facility that manages a few thousand machines. I figure venturing into the repair business seems like a smart move being that there are only a few in the usa alone working on asics and if the training is going to be given then people who are fully invested in the field are interested like myself. Crypto is my full-time job. Actually, I never showed you the photo of my basement when I had 150 amps of power for asics... but the majority are in a new home now.
I will say my favourite thing about the Avalon's is how modular they are which is nice compared to bitmain plus they won't let you touch the damn thing if it is a sha256 miner. Downtimes for months if you got to ship it back.
Contact Canaan's Global Sales Director Steven Mosher. Info is on Canaan.io site and he is here as StevenMosher. |
|
|
|
<pyramid truncated> Yes the failover code is full of fail  Maybe "bitcoin" needs to find a programmer who can actually write a miner that works properly and takes pride in the quality of their code, instead of sitting around with $20-30mil and not giving a crap about it  After all these years, Bitmain can't do it, nor can ck Bitmain won't because that means actually writing code vs just stealing it. As for the originator of the mess -- reading through the Halong Dragonmint thread I've seen mention of it handling failover better so... Then again safe bet ck ain't working for Halong for free. I will say that he has been busy there -- he's been releasing firmware updates every week or so to get the mints closer to as-advertised spec the fools investomers believed and then threw money at Halong in typical pre-sale frenzy. God forbid things he comes up with eventually appears in the git for cgminer so Canaan/Avalons can use it... Of course soon after BM's Ants would be using it as well. |
|
|
|
As a matter of interest, does this make any sense or is it simply words? (Please only respond if you actually know what you're talking about. tia.) A unique patent in the market
Our chip is made up of tens of thousands of interconnected transistors linked by different horizontal planes. These links are both encrypted and rendered unrecognizable by approximately 120,000 binary codes and passwords generated by them.
The calculated data can only be decrypted and processed with our specially developed software. Our ASIC processor is an electronic circuit. This is permanently integrated in the circuit, so that the function of the chip can not be changed.
If an attempt were made to copy or decode these codes, the charge in the chip would be altered, which would lead to the connections becoming burnt. As someone once said, 'if you can't blind them with brilliance - baffle them with bullshit'..... Translation: Our supposed chip is 3d (stacked dies) and for whatever reason we decided to waste precious die space by encrypting the normally un-encrypted data IO between the chip and the controller. The chips is an ASIC - look it up in Wikipedia. Given the A1 tag and the 3D chip construction -- that sounds a helluva lot like Bitmine.ch's crappy A1 chip from 2014... |
|
|
|
If someone can tell me why the pictures don't show and only the links are visible... I can't get them to show.
Perhaps try reading the Rules of the Forum to find out what you can do here and when. You are brand new with zero activity history. You must earn the right to post different things. Frankly ^^ reads almost exactly many other PR releases put out by Halong themselves with the one difference being you did point out a few of its warts. Kudos for not glossing over the power concerns. You said: I got in contact with the people of Halong and they answered all the questions I had at that moment. I can only speak from my experiences but communication was a true pleasure, fast and friendly.
Oddly very different response than ANY Forum member with long term cred got from Halong when they announced this machine last November. All anyone got from them was the sound of crickets. That is until these mysterious new members showed up with glowing comments about Halong and how unfair we are to not just trust them. |
|
|
|
Avalon might use more power over 30C, specs pertain to 30C usage.
[...]
Might? as I posted in the 841 specs thread the 2x 841's in my basement right now are in a 90F ambient and ... running at those temps seems to come at a price: power usage. After running several tests, with a solid 230V coming from my always on-line UPS's both ones from Cyberpower and Tripplite reports typical power using -2 offset as 1.51KW - all long way away from much lower power reported by others when running in lower temps.
Nice to know temps could be pushed higher but ja power consumption def goes up.
Moderator's note: This post was edited by frodocooper to trim the quote from Blokforge and to correct erroneous quote formatting. |
|
|
|
I noticed this too and made a post here and spoke to Canaan about it. I spoke to Canaan and they said reversing the (sorcerer) fan should be ok if temps stay under 40c. We plan to reverse them too as you did to see as we are run cold/hot aisle setups and curious to see if there is a temp improvement. I'd like a better reply from Canaan other than 'should be' ok. Would be nice for them or their vendor to model & verify just what happens to the various hot spots in a PSU and make yay/nay based on that. Changing from blow to suck will drastically change the flow patterns inside the PSU... Perfect confirmation would be Canaan acting on this and changing the flow direction on future Sorcerer's they sell. But - that said, when I get back in-country next week think I'll give it a whirl. |
|
|
|
|
In all fairness, the deleted posts about temp range change were in the Blokforge thread so not really on-point with the topic. Which leads to my reply on it that was also deleted.
On that... 1st I have to say that so far my 841's have been happy running in up to 93F (34C) ambient leading to chip temps from 88-90C. I see similar temps on the 721's and 741's I have.
However - running at those temps seems to come at a price: power usage. After running several tests, with a solid 230V coming from my always on-line UPS's both ones from Cyberpower and Tripplite reports typical power using -2 offset as 1.51KW - all long way away from much lower power reported by others when running in lower temps.
Also hate to say it but my s9 batch-1 (no Vcore regulators) running in the same area, chip temps 99-102C only pulls 1250w...
|
|
|
|
|
Show Posts
