|
Title: AVALON 6 CURRENTLY Post by: stugots2 on October 26, 2017, 07:29:03 PM FINALLY, I got my A6 running, with alot of help from many forum members.
BUT I have 1 bad hash board (other ones fine) anyone know where I can buy one? or does someone have one laying around? OR someone know who can repair it? I put alot of time and energy into this thing I just wanna see her run LOL Thanks Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on October 27, 2017, 03:16:05 PM The fact that parts are so hard to find makes me very scared to buy an Avalon 7
Title: Re: AVALON 6 CURRENTLY Post by: fanatic26 on October 27, 2017, 03:53:54 PM The manufacturers normally only sell replacement accessories and not the actual hashboards themselves. You are now asking about parts for an out of production last generation miner. You will probably have to do a little more than throw up a single post on a forum to find the parts you need.
Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on October 27, 2017, 03:54:45 PM I contacted all the trusted people about it.
any suggestions? Title: Re: AVALON 6 CURRENTLY Post by: philipma1957 on October 27, 2017, 05:02:27 PM I contacted all the trusted people about it. any suggestions? THE six has no new parts. all you can do is buy old ones and piece it together. Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on October 27, 2017, 05:24:05 PM guess I'll hunt for a decent deal on one.
maybe someone here?? Title: Re: AVALON 6 CURRENTLY Post by: wavelengthsf on October 27, 2017, 07:23:00 PM guess I'll hunt for a decent deal on one. maybe someone here?? $299 is a pretty good price (compared to eBay) at miner-warez: https://minerwarez.com/collections/used-equipment Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on October 27, 2017, 07:52:39 PM for sure not bad, just wont wanna rip a new one apart lol
anyone repair these boards? Title: Re: AVALON 6 CURRENTLY Post by: HagssFIN on October 27, 2017, 08:00:29 PM You could ask lightfoot if he is interested in fixing it.
Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on October 27, 2017, 08:13:30 PM I actually just did that @lightfoot
Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on October 27, 2017, 09:12:48 PM meantime a dumb question.
the Pi nor settings etc can make only 1 board hash right?? Title: Re: AVALON 6 CURRENTLY Post by: wavelengthsf on October 27, 2017, 09:42:13 PM meantime a dumb question. the Pi nor settings etc can make only 1 board hash right?? You could check the power to the other board - make sure your cables are good. But there's no way (that I know of) to disable a board in the controller. Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on October 27, 2017, 10:23:00 PM I have tried 3 different PSU's lol
ok cool thats what I needed to know. Title: Re: AVALON 6 CURRENTLY Post by: fanatic26 on October 27, 2017, 10:31:20 PM Under the advanced version of the Avalon dashboard it will give you error codes so you can diagnose the board problem.
Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on October 27, 2017, 10:40:27 PM hmmm I'm gonna check into that one.
that way maybe we can see whats exactly wrong. you know where that is in advanced? Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on October 27, 2017, 11:52:04 PM Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.005001] Brought up 4 CPUs
Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.005091] SMP: Total of 4 processors activated (153.60 BogoMIPS). Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.005117] CPU: All CPU(s) started in HYP mode. Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.005141] CPU: Virtualization extensions available. Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.013151] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.013464] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.014134] pinctrl core: initialized pinctrl subsystem Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.014620] NET: Registered protocol family 16 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.019592] DMA: preallocated 4096 KiB pool for atomic coherent allocations Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.049950] cpuidle: using governor ladder Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.079969] cpuidle: using governor menu Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.085032] Serial: AMBA PL011 UART driver Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.085246] 3f201000.uart: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.085659] bcm2835-mbox 3f00b880.mailbox: mailbox enabled Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.140883] bcm2835-dma 3f007000.dma: DMA legacy API manager at f3007000, dmachans=0x1 Fri Oct 27 23:45:50 2017 kern.notice kernel: [ 0.142209] SCSI subsystem initialized Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.142383] usbcore: registered new interface driver usbfs Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.142478] usbcore: registered new interface driver hub Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.142561] usbcore: registered new device driver usb Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.150047] raspberrypi-firmware soc:firmware: Attached to firmware from 2016-03-04 17:53 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.177022] clocksource: Switched to clocksource arch_sys_counter Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.184818] NET: Registered protocol family 2 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.185390] TCP established hash table entries: 8192 (order: 3, 32768 bytes) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.185524] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.185731] TCP: Hash tables configured (established 8192 bind 8192) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.185834] UDP hash table entries: 512 (order: 2, 16384 bytes) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.185898] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.186099] NET: Registered protocol family 1 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.187746] futex hash table entries: 1024 (order: 4, 65536 bytes) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.196478] io scheduler noop registered Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.196518] io scheduler deadline registered Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.196576] io scheduler cfq registered (default) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.198652] BCM2708FB: allocated DMA memory fa400000 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.198698] BCM2708FB: allocated DMA channel 0 @ f3007000 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.203447] Console: switching to colour frame buffer device 82x26 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.207779] vc-cma: Videocore CMA driver Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.208946] vc-cma: vc_cma_base = 0x00000000 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.210139] vc-cma: vc_cma_size = 0x00000000 (0 MiB) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.211334] vc-cma: vc_cma_initial = 0x00000000 (0 MiB) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.212606] vc-mem: phys_addr:0x00000000 mem_base=0x3dc00000 mem_size:0x3f000000(1008 MiB) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.225776] brd: module loaded Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.233839] loop: module loaded Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.235668] vchiq: vchiq_init_state: slot_zero = 0xba480000, is_master = 0 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.238369] usbcore: registered new interface driver smsc95xx Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.239503] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.440792] Core Release: 2.80a Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.441857] Setting default values for core params Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.442937] Finished setting default values for core params Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.644266] Using Buffer DMA mode Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.645298] Periodic Transfer Interrupt Enhancement - disabled Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.646387] Multiprocessor Interrupt Enhancement - disabled Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.647512] OTG VER PARAM: 0, OTG VER FLAG: 0 Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.648622] Dedicated Tx FIFOs mode Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.649962] WARN::dwc_otg_hcd_init:1047: FIQ DMA bounce buffers: virt = 0xba414000 dma = 0xfa414000 len=9024 Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.652264] FIQ FSM acceleration enabled for : Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.652264] Non-periodic Split Transactions Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.652264] Periodic Split Transactions Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.652264] High-Speed Isochronous Endpoints Fri Oct 27 23:45:50 2017 kern.debug kernel: [ 0.656929] dwc_otg: Microframe scheduler enabled Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.656976] WARN::hcd_init_fiq:413: FIQ on core 1 at 0x80295efc Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.658149] WARN::hcd_init_fiq:414: FIQ ASM at 0x8000ee78 length 36 Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.659318] WARN::hcd_init_fiq:439: MPHI regs_base at 0xbb87c000 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.660537] dwc_otg 3f980000.usb: DWC OTG Controller Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.661719] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.662910] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000 Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.664092] Init: Port Power? op_state=1 Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.665207] Init: Power Port (0) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.666480] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.667653] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.668804] usb usb1: Product: DWC OTG Controller Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.669929] usb usb1: Manufacturer: Linux 4.4.7 dwc_otg_hcd Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.671050] usb usb1: SerialNumber: 3f980000.usb Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.672720] hub 1-0:1.0: USB hub found Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.673846] hub 1-0:1.0: 1 port detected Fri Oct 27 23:45:50 2017 kern.debug kernel: [ 0.675375] dwc_otg: FIQ enabled Fri Oct 27 23:45:50 2017 kern.debug kernel: [ 0.675383] dwc_otg: NAK holdoff enabled Fri Oct 27 23:45:50 2017 kern.debug kernel: [ 0.675390] dwc_otg: FIQ split-transaction FSM enabled Fri Oct 27 23:45:50 2017 kern.debug kernel: [ 0.675418] Module dwc_common_port init Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.675577] usbcore: registered new interface driver uas Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.676720] usbcore: registered new interface driver usb-storage Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.677865] mousedev: PS/2 mouse device common for all mice Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.679683] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.680877] sdhci: Secure Digital Host Controller Interface driver Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.681974] sdhci: Copyright(c) Pierre Ossman Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.683298] sdhost: log_buf @ ba413000 (fa413000) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.757037] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.758306] sdhci-pltfm: SDHCI platform and OF driver helper Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.761023] NET: Registered protocol family 10 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.762946] NET: Registered protocol family 17 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.764040] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.766269] 8021q: 802.1Q VLAN Support v1.8 Fri Oct 27 23:45:50 2017 kern.notice kernel: [ 0.767841] Registering SWP/SWPB emulation handler Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.769571] vc-sm: Videocore shared memory driver Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.770676] [vc_sm_connected_init]: start Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.777399] [vc_sm_connected_init]: end - returning 0 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.779403] Waiting for root device /dev/mmcblk0p2... Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.862483] mmc0: host does not support reading read-only switch, assuming write-enable Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 0.867184] Indeed it is in host mode hprt0 = 00021501 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.868669] mmc0: new high speed SDHC card at address e624 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.870396] mmcblk0: mmc0:e624 SS08G 7.40 GiB Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.874110] mmcblk0: p1 p2 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.894303] EXT4-fs (mmcblk0p2): mounted filesystem without journal. Opts: (null) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.896710] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.898338] Freeing unused kernel memory: 220K (8053d000 - 80574000) Fri Oct 27 23:45:50 2017 user.info kernel: [ 0.998301] init: Console is alive Fri Oct 27 23:45:50 2017 user.info kernel: [ 0.999736] init: - watchdog - Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.047064] usb 1-1: new high-speed USB device number 2 using dwc_otg Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 1.048519] Indeed it is in host mode hprt0 = 00001101 Fri Oct 27 23:45:50 2017 user.info kernel: [ 1.132264] init: - preinit - Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.247310] usb 1-1: New USB device found, idVendor=0424, idProduct=9514 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.248693] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.250807] hub 1-1:1.0: USB hub found Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.252226] hub 1-1:1.0: 5 ports detected Fri Oct 27 23:45:50 2017 kern.notice kernel: [ 1.254451] random: procd urandom read with 36 bits of entropy available Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.527038] usb 1-1.1: new high-speed USB device number 3 using dwc_otg Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.627233] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.628559] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.632539] smsc95xx v1.0.4 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.689935] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:f2:d4:29 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.787037] usb 1-1.2: new full-speed USB device number 4 using dwc_otg Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.890562] usb 1-1.2: New USB device found, idVendor=29f1, idProduct=33f2 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.891903] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.893225] usb 1-1.2: Product: USB2IIC Converter Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.894553] usb 1-1.2: Manufacturer: CANAAN Fri Oct 27 23:45:50 2017 kern.info kernel: [ 1.895841] usb 1-1.2: SerialNumber: 20141122 Fri Oct 27 23:45:50 2017 user.notice kernel: [ 4.272318] mount_root: mounting /dev/root Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 4.274025] EXT4-fs (mmcblk0p2): warning: mounting unchecked fs, running e2fsck is recommended Fri Oct 27 23:45:50 2017 kern.info kernel: [ 4.279440] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) Fri Oct 27 23:45:50 2017 kern.warn kernel: [ 4.319926] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Fri Oct 27 23:45:50 2017 user.info kernel: [ 4.335874] procd: - early - Fri Oct 27 23:45:50 2017 user.info kernel: [ 4.337305] procd: - watchdog - Fri Oct 27 23:45:50 2017 user.info kernel: [ 4.933209] procd: - ubus - Fri Oct 27 23:45:50 2017 user.info kernel: [ 4.989624] procd: - init - Fri Oct 27 23:45:50 2017 kern.info kernel: [ 5.367833] ip6_tables: (C) 2000-2006 Netfilter Core Team Fri Oct 27 23:45:50 2017 kern.info kernel: [ 5.375248] i2c /dev entries driver Fri Oct 27 23:45:50 2017 kern.info kernel: [ 5.378258] bcm2708_i2c 3f205000.i2c: BSC0 Controller at 0x3f205000 (irq 83) (baudrate 100000) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 5.380931] bcm2708_i2c 3f804000.i2c: BSC1 Controller at 0x3f804000 (irq 83) (baudrate 100000) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 5.391215] hidraw: raw HID events driver (C) Jiri Kosina Fri Oct 27 23:45:50 2017 kern.info kernel: [ 5.406825] ip_tables: (C) 2000-2006 Netfilter Core Team Fri Oct 27 23:45:50 2017 kern.info kernel: [ 5.412766] nf_conntrack version 0.5.0 (14877 buckets, 59508 max) Fri Oct 27 23:45:50 2017 kern.info kernel: [ 5.510113] usbcore: registered new interface driver usbhid Fri Oct 27 23:45:50 2017 kern.info kernel: [ 5.511442] usbhid: USB HID core driver Fri Oct 27 23:45:50 2017 kern.info kernel: [ 5.519064] xt_time: kernel timezone is -0000 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 5.525186] PPP generic driver version 2.4.2 Fri Oct 27 23:45:50 2017 kern.info kernel: [ 5.527198] NET: Registered protocol family 24 Fri Oct 27 23:45:51 2017 cron.info crond[396]: crond (busybox 1.24.2) started, log level 5 Fri Oct 27 23:45:51 2017 authpriv.info dropbear[419]: Not backgrounding Fri Oct 27 23:45:51 2017 daemon.notice netifd: Interface 'lan' is enabled Fri Oct 27 23:45:51 2017 daemon.notice netifd: Interface 'lan' is setting up now Fri Oct 27 23:45:51 2017 kern.info kernel: [ 7.528911] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup Fri Oct 27 23:45:51 2017 kern.info kernel: [ 7.532101] device eth0 entered promiscuous mode Fri Oct 27 23:45:51 2017 kern.info kernel: [ 7.535175] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready Fri Oct 27 23:45:51 2017 daemon.notice netifd: Interface 'lan' is now up Fri Oct 27 23:45:51 2017 daemon.notice netifd: Interface 'loopback' is enabled Fri Oct 27 23:45:51 2017 daemon.notice netifd: Interface 'loopback' is setting up now Fri Oct 27 23:45:51 2017 daemon.notice netifd: Interface 'loopback' is now up Fri Oct 27 23:45:51 2017 daemon.notice netifd: Network device 'lo' link is up Fri Oct 27 23:45:51 2017 daemon.notice netifd: Interface 'loopback' has link connectivity Fri Oct 27 23:45:51 2017 user.notice firewall: Reloading firewall due to ifup of lan (br-lan) Fri Oct 27 23:45:51 2017 daemon.info dnsmasq[545]: started, version 2.75 cachesize 150 Fri Oct 27 23:45:51 2017 daemon.info dnsmasq[545]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify Fri Oct 27 23:45:51 2017 daemon.info dnsmasq[545]: using local addresses only for domain lan Fri Oct 27 23:45:51 2017 daemon.info dnsmasq[545]: reading /tmp/resolv.conf.auto Fri Oct 27 23:45:51 2017 daemon.info dnsmasq[545]: using local addresses only for domain lan Fri Oct 27 23:45:51 2017 daemon.info dnsmasq[545]: using nameserver 192.168.0.1#53 Fri Oct 27 23:45:51 2017 daemon.info dnsmasq[545]: read /etc/hosts - 4 addresses Fri Oct 27 23:45:51 2017 daemon.info dnsmasq[545]: read /tmp/hosts/dhcp - 1 addresses Fri Oct 27 23:45:51 2017 daemon.info kernel: [ 7.976291] udevd[539]: starting version 3.2 Fri Oct 27 23:45:51 2017 daemon.err kernel: [ 7.982213] udevd[539]: specified group 'tty' unknown Fri Oct 27 23:45:51 2017 daemon.err kernel: [ 7.984072] udevd[539]: specified group 'dialout' unknown Fri Oct 27 23:45:51 2017 daemon.err kernel: [ 7.985744] udevd[539]: specified group 'kmem' unknown Fri Oct 27 23:45:51 2017 daemon.err kernel: [ 7.987633] udevd[539]: specified group 'input' unknown Fri Oct 27 23:45:51 2017 daemon.err kernel: [ 7.989225] udevd[539]: specified group 'video' unknown Fri Oct 27 23:45:51 2017 daemon.err kernel: [ 7.990886] udevd[539]: specified group 'lp' unknown Fri Oct 27 23:45:51 2017 daemon.err kernel: [ 7.992246] udevd[539]: specified group 'disk' unknown Fri Oct 27 23:45:51 2017 daemon.err kernel: [ 7.993684] udevd[539]: specified group 'cdrom' unknown Fri Oct 27 23:45:51 2017 daemon.err kernel: [ 7.994880] udevd[539]: specified group 'tape' unknown Fri Oct 27 23:45:51 2017 daemon.info kernel: [ 8.015819] udevd[560]: starting eudev-3.2 Fri Oct 27 23:45:52 2017 kern.info kernel: [ 9.092878] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1 Fri Oct 27 23:45:52 2017 daemon.notice netifd: Network device 'eth0' link is up Fri Oct 27 23:45:52 2017 daemon.notice netifd: Bridge 'br-lan' link is up Fri Oct 27 23:45:52 2017 daemon.notice netifd: Interface 'lan' has link connectivity Fri Oct 27 23:45:52 2017 kern.info kernel: [ 9.097282] br-lan: port 1(eth0) entered forwarding state Fri Oct 27 23:45:52 2017 kern.info kernel: [ 9.098276] br-lan: port 1(eth0) entered forwarding state Fri Oct 27 23:45:52 2017 kern.info kernel: [ 9.099296] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready Fri Oct 27 23:45:53 2017 daemon.info procd: - init complete - Fri Oct 27 23:45:54 2017 kern.info kernel: [ 11.097026] br-lan: port 1(eth0) entered forwarding state Fri Oct 27 23:45:56 2017 kern.notice kernel: [ 12.459625] random: nonblocking pool is initialized Fri Oct 27 23:50:00 2017 cron.info crond[396]: USER root pid 1166 cmd /usr/bin/cgminer-monitor Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on October 29, 2017, 06:47:13 AM anyone know how to read that?
whats it mean lol Title: Re: AVALON 6 CURRENTLY Post by: alexcos20 on October 29, 2017, 07:59:24 AM anyone know how to read that? this is the system log, nothing related to the boards here.whats it mean lol try posting CGMINER API Log here Title: Re: AVALON 6 CURRENTLY Post by: Steamtyme on October 29, 2017, 03:11:39 PM The error code you would be looking for is on the
https://en.bitcoin.it/wiki/Avalon6#MM_Error_Codes Just go to the error code heading. Hope this helps Edit: fixing up an old post. You find the code under ECHU in the api log Title: Re: AVALON 6 CURRENTLY Post by: AniceInovation on October 31, 2017, 01:09:43 AM Does anyone know where i could buy the internal controller for a Avalon 6?
Had 1 broken board but with testing i fried the controller too... If i'm able to get the good board hashing i''ll sell it to ya Title: Re: AVALON 6 CURRENTLY Post by: NotFuzzyWarm on October 31, 2017, 01:24:10 AM anyone know how to read that? !!! Good God man !!! Learn to use the Code function here! Looks like # Using it your text wall of a log becomeswhats it mean lol Code: Fri Oct 27 23:45:50 2017 kern.info kernel: [ 0.005001] Brought up 4 CPUs Sooo much easier to deal with... ;) Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 04, 2017, 07:14:43 PM The Daughter Board?
Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 04, 2017, 07:16:04 PM AKA MCU?
Title: Re: AVALON 6 CURRENTLY Post by: AniceInovation on November 04, 2017, 10:33:00 PM Yeah that one.
But never mind, another one burned, got to see if i can build one out of 2 defect ones. Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on November 05, 2017, 02:33:22 PM Hi! Just found this thread, and yes the unit is in the shop here for review. Hopefully I'll be able to add some knowledge as to what causes Avalons to go bad and see if there are ways to fix them.
In this case, the unit apparently was sold to the current owner, who needed one of the AUC (UART to USB) connectors. Once procured, the unit failed to hash. The internal daughterboard was replaced and the right side board would come up intermittently. At that time it was noted that the left side ribbon cable servicing the left side board was burned (will post a pic at some point), and when the good cable was swapped to the left side the unit stopped working completely. However the unit does report the right side board, just with a temp of 85c all the time, and a voltage reading on the +12 line of 3v. Both of which I do not think are true :-) What I think is going on is this: 1) A short to +12 on a signal line on the left side developed and faulted the first daughter board. Will see if I can identify the component. 2) Same happened to the second daughter board when the ribbon cable was plugged in again. Drat. I'll see if I can isolate which component is the a/d converter (doubtful) or the i2c interface (possible) on the daughter board. I doubt there are schematics out there but one can always hope. If the lines feed straight into the MCU on that board it could be a problem since although that processor could be swapped they probably have an IPL loader routine that allows it to be reflashed. We'll see. Second line of attack will be to review the left side and see if there's any components obviously out on that side and where the short to ground might be. It could be in the sensor to detect +12 rail voltage, if that went to shorted I could see enough current going through to burn the wire. Interesting problem.... If anyone has a contact at Cannan or knows where parts can be procured drop me a line. Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 05, 2017, 05:23:00 PM Thats awesome, Thanks so much!!!
Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on November 06, 2017, 01:33:04 AM No problem. This is a weird issue, and I enjoy a bit of a challenge. No guarantee I can fix it of course, but I will give it a shot.
C Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 06, 2017, 05:40:32 PM leave it to me to have the weird case LOL
Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on November 07, 2017, 08:23:19 PM Well it is interesting. What happened is there is a direct 12 volt hard short between +12 on the bad side of the miner through the line that burned to the MCU. Granted, no schematics but it looks like the chip in question that shorted may be the voltage detector for the 12v rail. This would explain why the MCU now sees locked values on the other side.
Next question is can I flash a new Spartan with enough firmware to allow a load of bootstrap code. Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 07, 2017, 08:25:21 PM ahhhhhhhhhhhhhhh OK that makes sense!!!
Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 08, 2017, 02:17:21 PM its kind of cool this is like a "public repair"
can be archived for people to look at when they make have an issue like this Title: Re: AVALON 6 CURRENTLY Post by: toptek on November 08, 2017, 02:35:09 PM Hey stugots2
Found this in the US for A6's it's temping my only problem my house can't handle that many A6's at once i have a room sound proofed for noise it's the Electricity that would be a bitch for me . i can't draw that much in my house with out the Electricity company sticking there nose in plus id have to up grade my service ... I'm happy at 200 amp service for now ... https://www.parallelminer.com/product/35th-a6-kit-bitcoin-miner-2-avalon6/ @ lightfoot i told him a few times to hit you up glad you found him.... I'm a ware some one made a post about MinerWarez but with Parallelminer no custom fees or dealing with customs and there out in CA .... i think you get free shipping or less then if you order else were like out of the US ... NO EU tax etc ... no tax unless your state has that kind of tax mine doesn't for out of state internet buys for instate online buys I have to pay sales taxes . . or any thing bought in my state as most states do . stugots2 also like i said before be careful you can brick the MCU , I bricked two of them an unless you have the right tools to un brick them your F**** so don't update the MCU unless you need two and then be real care full which MCU file update you use it has to be at least 2 mb size :) just a tip ... Last thought my A6 hashes better with a 1400 watt or higher Psu running it . that was advice i was given in one of the other A6 posts and it's true or mine does ... it seems using a 1200 watt Psu really won't cut it ..with my A6 on a 110 or 220 line i tested it on both with a few 1200 watt psu's ....so i plug into a 2400 watt psu an it hashes @ 3.5 th or higher volts stay around 11.9 to 12 V unlike using a 1200 watter it hashes at 3.0 th or lower with lower voltage . temps seem to stay the same no mater what Psu i use 29 to 31 C. Soon BTC dust will be worth a lot .so keep those old out dated S5 C1 or AVALON 4 if they work still, once BTC hit 10 k or higher they might be worth firing up .... Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 09, 2017, 01:05:53 PM I'll tell you this, alot of you guys really back Avalon's and this issue has NOT left a bad taste in my mouth in fact I just bought another Avalon 6 (PLEASEEEEEE no issues on this new one lol)
Title: Re: AVALON 6 CURRENTLY Post by: toptek on November 09, 2017, 04:32:18 PM I'll tell you this, alot of you guys really back Avalon's and this issue has NOT left a bad taste in my mouth in fact I just bought another Avalon 6 (PLEASEEEEEE no issues on this new one lol) why not Avalon is as good as it gets right now compared to bitmain or anything else at this moment in time at least till next year and they seem a lot nicer then bit main ... I'm hoping Japan will be able to make things better and we start getting a better deal but that's next year if it's gonna happen . https://bitcoinmagazine.com/articles/japanese-company-will-launch-new-bitcoin-mining-operation-7-nm-chips/ Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 09, 2017, 07:43:44 PM in some ways, the S9 smokes it but, I have both now lol
Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 11, 2017, 08:49:23 AM if you hunt enough you can get good deals n Avalons
Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 12, 2017, 02:25:37 PM OMFG what a weird turn of events!!!!
Just realized the guy I bought some of the replacement parts to TRY and fix this avalon is the same place I bought this Lemon on Amazon from!!!!!!!!!! and hes a member here!!!!!!!!!! Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 15, 2017, 02:54:00 PM ANDDDDDDDDD their not responding lol
Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on November 15, 2017, 09:52:57 PM Ask if they have another board. Also does anyone know anyone at Cannan who can share a schematic for this bridgeboard. I'm fuzzing it out now, but it is of course slow going...
Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 15, 2017, 10:03:16 PM BTW Avalon # is on the way to you LOL
Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on November 18, 2017, 01:34:21 AM Stugot: I'll post thoughts here. Micro-summary:
Mess. Summary: Fucking mess :-) Seriously, the miner has one of its' header pins literally ripped off the hashing board. As in traces were pulled up, if this was sold as anything close to working it never was. That would happen if someone was upset beyond normal parameters and yanked it. The MCU appears to be in better shape than the one on your first unit, but it will not bring up either that board or the board on your first miner, loop errors. So either both boards have failed loops (quite possible) or the second MCU is screwed up in some way as well (not unbelievable) In the meantime, your first MCU board has a blown U7 chip, that's the LPC11U1 chip. It's a 8-16 bit microcontroller with 32k of Flash RAM, my guess is this is the housekeeping module that deals with the power and such. It's way bad (gets hot=bad) my guess is the short in the power measuring circuits on board M1 faulted to ground through this chip. No wonder it flunks diagnostics. Anyway, if this latest unit was sold as anything other than scrap get your money back, it's toast. I won't do anything else with it until this is figured out. Meantime I'll look into replacing this chip on your first MCU to see if that brings it back to life. C Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 18, 2017, 11:13:45 AM Sadly it was sold as working!!!!!
Does Avalon just hate me??? LOL I do have a spare MCU board here if you need? Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on November 18, 2017, 06:38:55 PM Sadly it was sold as working!!!!! Hm. This would never qualify as "working". Maybe they made a mistake and sold you a broken one. I would recommend sending them this picture, then saying it is broken and you would like a working one as agreed.https://i.imgur.com/Y0OsXCr.jpg In the picture you can see where the pads were literally ripped off. Did you get the cable at least? Quote I do have a spare MCU board here if you need? Does it work? If so drop it in the mail and I will confirm the board statuses.C Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 18, 2017, 07:08:12 PM I believe the MCU works.
Nope no cable came with that one LOL Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on November 18, 2017, 10:19:18 PM And in the meantime I've solved the mystery of your other unit's side 0. As mentioned it comes up with a Loop failure, which probably matches your description of "it would work sometimes then drop out". Taking the board apart and looking at it with the 15x loupes reveals the problem:
https://i.imgur.com/1Zc9v4R.jpg Anyway the issue is that one of the chips has a solder bridge along several of the connection points. Avalons do the same thing as the Antminers in that the power for the chip comes in on the top and bottom sides with signals coming in on the sides. In this case the chip overheated and melted the solder enough to make a nice little 3 wide bridge. I'm guessing that is the problem. Now to see if I can fix it. Hm..... C Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 18, 2017, 10:22:16 PM ohhhhhh wowwwwwwwwwww.
Since they never responded I guess I'll name the company that sold me that DOA one also, it came from oregon mines. (thats the first one) Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on November 18, 2017, 10:58:24 PM ohhhhhh wowwwwwwwwwww. If you bought it from Ebay, then do a return request. I'm going to take off the second board, anyone know of a source for these chips?Since they never responded I guess I'll name the company that sold me that DOA one also, it came from oregon mines. (thats the first one) C Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 18, 2017, 11:07:03 PM second one you mean? with the pins ripped?
Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on November 18, 2017, 11:23:41 PM Likewise you should see the other side of the first unit. At least 4 chips have either bridges or solder extrusions, my guess is these were run way too hot and eventually blew up. When blew up they were sold. This side shorted +12 over to the signal lines blowing the MCU.
Fix.... Hm. Have other things to do so will put this aside (I have not touched unit 2, but I'm expecting similar things). But anyway that's one way to blow a board. C Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on November 18, 2017, 11:28:25 PM second one you mean? with the pins ripped? Right. That is what I am calling the second unit you sent over. I'm not fiddling with that at all in case you want to return it. The board work is being done on the first unit.C Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 19, 2017, 02:16:13 AM gonna be filing a scam report if I don't hear back by monday since they are on these forums
Title: Re: AVALON 6 CURRENTLY Post by: Steamtyme on November 19, 2017, 02:34:33 AM gonna be filing a scam report if I don't hear back by monday since they are on these forums That's crazy I'm sorry to hear about that, no one wants to be sold bunk equipment. I'm kinda floored that they didn't get back to you through their company website. Also wondering how did you find their used equipment for sale? How did you pay for the units? if it was credit card at least they will offer purchase protection. Hope so, but at least you found them on the forum. Best of luck. Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 19, 2017, 11:53:49 AM was on their amazon store
Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on November 19, 2017, 02:17:40 PM Meantime I took one chip off the bad board to try and get the good board to pass loop tests. Still not coming up, it's possible the problem is in the MCU; if you have a spare you would like to send over I can do a cross-check.
I'll post a few pictures from the second board; there are at least 5 chips on there that have solder balls or shorts on them, what is making me wonder is how a unit could operate long enough with a single short in order to burn up additional chips. I wonder if the unit only self tests the loops on startup, and not while running. If so there may be a flag or option I can set in cgminer to ignore bad chips and continue, then I could figure out which chips are good/bad. Researching..... In the meantime didn't see them on Amazon, but Amazon may have a return policy for the second unit. Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 19, 2017, 02:48:32 PM second was ebay, I'm looking into that now.
I already printed a label for the MCU to be sent, will go out tomorrow am. Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 21, 2017, 04:02:00 PM looks like the art will arrive to you tomorrow
Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on November 22, 2017, 01:08:51 AM looks like the art will arrive to you tomorrow Sounds good, will be able to work on it over T-Day. Also just bought another A6 to use as a test platform, gotta spend the money for the tools. :-)C Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 25, 2017, 01:33:30 PM maybe some Turkey gravy will do the trick LOL
Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on November 25, 2017, 01:55:09 PM maybe some Turkey gravy will do the trick LOL Burp. Just got it last night, along with a nice reference A6 that I need to test. Also pulled the microcontroller from the first MCU board that was on the first A6 (labelled "A") the chip was running super hot which indicates shorts. Will try a new chip once I verify location of pin 1.Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 25, 2017, 02:22:21 PM Sweet.
With BTC up, it will be nice to see those babies mining lol Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on November 25, 2017, 06:11:43 PM Maybe....
Did some research here. For purposes of keeping things baseline and cool, I'm running all tests at speed 100. That should give a nice 400-500mh per blade with little temp difference. My new unit here works fine; two blades run great at up to 3.5th at speed 350. Room to grow there, but work well. Test 1: Run with one blade. Works, flashes red, blade 1 is down, error is 18440, Loop 1 failed PG1 failed, ADC1_err. Temps are 32,47,273. Ok, fair enough. One important thing, the plug on the blade side was exceptionally tight. Pull hard and you *will* rip off the socket. I think they glued them, keep this in mind. Test 2: Run with second blade on controller 2 (stux's controller from second Avalon). Goal is to establish a working MCU if possible. Plugged it into my blade, his cable, his controller, my auc, my Pi. Works fine, with same errors and 400-500gh hashing rate. Ergo his second MCU is good. No need to test third MCU, leave in box. Test 3: Put his MCU on blade 1 of his Avalon. Fails with both loops down. Ergo that blade is bad, problem is in blade. It is also to note that the ripped off plug matches the fact that the seller was retarded and probably thought he could pull the good blade and put it in another box. So he ripped off the plug, replacing the plug (bitch on wheels) could get things to work on that blade. Will think about that. Meantime will take apart blade 1 from unit 1 and see if there are any solder bridges that can be fixed. Leaving unit 2 alone unit stux says he isn't getting his money back evah.... Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 26, 2017, 02:36:31 AM no money back on either sadly... no justice so your my only hope lol
Title: Re: AVALON 6 CURRENTLY Post by: Steamtyme on November 26, 2017, 03:15:21 AM no money back on either sadly... no justice so your my only hope lol Really through eBay and PayPal protection, you aren't getting refunded for DOA unit. That's crazy. Sorry to hear about that crapshoot of an experience. Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on November 26, 2017, 05:05:14 PM Ok. In which case I'll take off the left side and see what's going on.
C Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on November 29, 2017, 11:17:58 PM oregonmines.com (people that sold me the fist one I sent you) simply will NOT respond so it's time for the scam report
Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on December 04, 2017, 05:12:04 AM More bad news on the second one. I took the board apart from side 0 (the one that didn't have the plug ripped out); it has a um... well let's say one chip is burned and several others show signs of the chips delaminating from the carriers....
That would definitely shut down the loop. Next up will be to try and remove the ribbon cable socket from this board (it's never going anywhere again) and hard-wire it into the one that had the socket ripped off.... C Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on December 05, 2017, 01:26:18 PM ohhh wowwww.
I surely sent you 2 beauties huh??? LOL Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on December 05, 2017, 02:49:46 PM ohhh wowwww. Duds. Let's look at some pictures....I surely sent you 2 beauties huh??? LOL This is bad.... https://i.imgur.com/9quVq41.jpg This is worse.... https://i.imgur.com/iiEAFh5.jpg Not the only chip either, others were on the way out.... https://i.imgur.com/IVnAv2j.jpg C Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on December 05, 2017, 09:28:08 PM lmfaoooo Sure glad I set my pride aside enough and realized I should not tackle this one myself LOL
Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on December 08, 2017, 12:53:47 AM question is: does it have you pulling your hair out just yet???? LOL
Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on December 08, 2017, 02:14:34 AM question is: does it have you pulling your hair out just yet???? LOL No not at all, this is fascinating. I'm just putting it in between other paying work, it's good research.Title: Re: AVALON 6 CURRENTLY Post by: Leszek on December 08, 2017, 04:34:50 AM Hi lightfoot,
I have similar problem I have 2 AVALON6 one is running steady at 3495GHs, another (purchased from another saler) fluctuate between 19xx and 38xx with avg about 26xx. Any idea or sugestion? Thank you, Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on December 08, 2017, 12:20:37 PM Hi lightfoot, First check the temps. In the advanced tabs under CGMiner_Status, the first temp is inlet and the second and third are temps on each side of the unit. Are temps on sides 2 and 3 about the same?I have similar problem I have 2 AVALON6 one is running steady at 3495GHs, another (purchased from another saler) fluctuate between 19xx and 38xx with avg about 26xx. Any idea or sugestion? Thank you, Check for power supply issues, maybe one side is running with an undersized supply. What is your 12v input voltage? Try throttling down the max frequency to 100. What do you see performance-wise, is it stable? Set the max frequency speed to 400. You should get around 3.2th or so. See if that is stable. Title: Re: AVALON 6 CURRENTLY Post by: Leszek on December 08, 2017, 07:32:01 PM https://plus.google.com/u/0/photos/116111157305357625600/album/6497260299740327761/6497260300394056018?authkey=CP-r_7PD_vP3swE https://plus.google.com/u/0/photos/116111157305357625600/album/6497260299740327761/6497260300394056018?authkey=CP-r_7PD_vP3swE
Thank you, I lower frequency to 400 and I will check in one hour how is running. I hope my attached pictures work Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on December 13, 2017, 01:34:28 AM I did buy a new fan for one of em, do you need that? I'd assume thats not an issue right?
Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on December 13, 2017, 04:22:27 AM I did buy a new fan for one of em, do you need that? I'd assume thats not an issue right? No it's not a fan issue. The chips have just been baked.C Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on December 27, 2017, 03:59:49 PM find any more bad news? LOL
Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on December 29, 2017, 02:03:04 AM Nothing works and I had to put it aside for a bit to fix some titan boards. And enjoy Christmas. And eggnog. And stuff like that.....
Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on December 30, 2017, 12:09:02 AM However that doesn't mean I give up: I just bought a reflow oven before the end of the year, will use that to try and re-seat all of the hashing chips before throwing in the beer when it arrives.
Just an excuse to buy bigger tools. Title: Re: AVALON 6 CURRENTLY Post by: stugots2 on January 06, 2018, 03:19:51 PM lmfaooooo
bigger the better Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on January 07, 2018, 09:01:43 PM Yeah it should be interesting to get this set up. Should be here by next weekend.
The big problem with these A6 boards is that there are a lot of parts on the underside of the board, thus it is very difficult to pre-heat them enough to use hot air to reflow the chips without having components fall off. An oven will allow me to reflow far more evenly with the chips down and the various heavier components on the top. We'll see how it works. C Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on February 04, 2018, 10:34:31 PM Reflow oven is a bitch on wheels. I have been reflowing old broken Titan and Neptune boards, problem is the soft components (caps and plugs) melt. Working on ways to fix that.
Meantime I have something equally cool, predator vision. I'll post a pic in a bit. C Title: Re: AVALON 6 CURRENTLY Post by: AniceInovation on February 05, 2018, 01:28:05 AM Hey C,
Interested in a broken Avalon A6? Control board and one hashing board definitely burned, the other hashing board i can't say. I'll sell it to you for the cost of shipping if interested. I like your repair attempts, i feel like eating popcorns waiting for updates :) Title: Re: AVALON 6 CURRENTLY Post by: lightfoot on February 05, 2018, 03:23:36 AM Sure, that would be great, I'll PM you with shipping details.
Been working on the A6 boards, they're weird: If the controller board in the box becomes unplugged from the boards they go into thermal overdrive, you can see at least one chip on each side going low resistance and heating up a *LOT*. The problem with the A6's at the core is that they built the boards without any sort of compensators. For example on the Antminers (with one exception) the boards have a set of FETs, a choke, and a programmed voltage of between 9.6 (Antminer S9) to 10.5 (Antminer S7) then they run the chips off that. Stable, and can handle chips that might go slightly off in terms of resistance. On the weird S7's with lots of chips, and the Avalon A6's they run them straight off the power supply, 20 chips per string on the A6. Thus each chip normally gets .6 volts, but if a chip gets warmer than its neighbors, the resistance on that chip goes down and very bad things happen. Bad means the chip has a lower resistance meaning it gets more volts+current=more watts=more heat which means more current. Thus they can get hot enough to melt the solder, make balls, and short out/shut down. Bitch. Moral: Ensure your chips are ballasted. |
