 Show Posts
|
|
Pages: [1] 2 »
|
Blockchain Hype wendet sich der Mainstream-Adoption in Multi-Milliarden-Dollar-Unternehmen: StudieVon CCN.com: Vierzig Prozent der leitenden Finanzfachleute erwarten, dass ihre Unternehmen in den nächsten zwei Jahren in Blockchain-Technologie investieren werden, so eine aktuelle Umfrage der Wirtschaftsprüfungsgesellschaft Grant Thornton LLP. Hinzu kommen die 22 Prozent, die berichten, dass ihre Unternehmen die Technologie bereits implementiert haben. Dies markiert eine dramatische Veränderung gegenüber erst vor einem Jahr, als Blockchain mehr diskutiert als praktiziert wurde, so Chris Stephenson, Business Consulting Principal bei Grant Thornton LLP und Autor des Berichts. In seiner CFO-Umfrage 2019 befragte Grant Thornton zusammen mit dem Partner CFO Research 378 leitende Finanzfachleute in Unternehmen mit einem Umsatz zwischen 100 Millionen und 20 Milliarden US-Dollar. Die meisten davon haben ihren Hauptsitz in den USA. Quelle:Deutsch: https://cryptoevo.de/index.php?threads/blockchain-hype-wendet-sich-der-mainstream-adoption-in-multi-milliarden-dollar-unternehmen-studie.468/Englisch: https://www.ccn.com/blockchain-entering-corporate-mainstream-study
|
|
|
|
It is funny that nobody seems to see a other use case then as a fork pump and dump coin. also dude, zclassics only difference is, that they don't take founders fee.. but when they just copy the code of zcash delayed... where is there any scene? Yeah for copying things you usally get not much true... We have seen why zCash has a founder fees, because people need fucking food to work well and live, and that is the reason why the hippy version just started to death. Sure doing it fore free would be better and more honest, but the first team starved to death, and the second BTCP team raped what was left. So zClassic is just a copy with no other use case then pump and dump? Lets see if it is at least doing what it is used for now  |
|
|
|
I contacted the team. The roadmap was removed because according to them unexpected situations can always come up during the development and in that case, it was creating false expectations.
It doesn't necessarily mean that the development of hardware wallet support or any other feature has stopped though.
As for the guy losing his money and in all honesty, It's clearly his fault. A computer with a desktop wallet = vulnerable, everyone knows that. If he wasn't willing to invest less then 100$ in a hardware wallet when he had 500k then when was he planning to do so?
Ok Ok very nice from you, thanks for taking your Time! Yeah its true that is to 100% his fault, but i think if it was already compatible, it would be a catalyst to adopt more comfortable. I think it was just to convenient. But i am sure and confident that one day Exodus will bring that compatibility out because it is no other option in the future then adding it. The question is only in how much time. Thank you again for taking your time to gather those informations  |
|
|
|
Yes, i did exactly, but it's not working. Nothing showed on the dashboard while the A9 was working. Please correct me. What do you see when you press on the "Workers" tab? Is there your A9 listed with red "call sign" ? If yes you just have to wait for like 1-2 hours to get proper statistics. |
|
|
|
Offizial Update you get here: http://www.innosilicon.com/html/support_en/download.htmlDon't have to bother them via mail, i guess. EDIT: Ok i see first now, that i might have difference to the older version via mail.
Are there any good reasons we're missing such that we'd pay 2% to Slushpool, when most other pools are 0.9 - 1.0% ?
We believe that our advanced worker management and device monitoring is pretty good reason and this functionality can save you more money at the end. But of course – the decision is on each miner. However we know that we are 'too expensive' for some miners and we are thinking about making changes. This is a fascinating claim. In what ways can this save money at the end? Does Slushpool have inband device configuration or adjustment options? I notice that with these Innosilicon A9 devices one can't even get into the UNIX/Linux shell to kill the irritating HTML-monitor logout tendency. It would be pleasantly surprising that your pool has some way to adjust device operation inband. I used now several pools, and Antpool was kinda the most disgusting one in the end result, endless slow, shitty app kinda strange, forces you everytime to fucking bitcoin and you have to change everytime to english from chinese before you can really use the site. I have now used slushpool for 2 days, and i can tell you simply they REALLY DESERVE THOSE 2% PROZENT !!!! It is just fucking awesome fast. Even from vacation, the app is also verified by apple and serious listed on app store. The fucking Antpool app wants first some shady verification for their shady certs. Also Antpool wants a fucking phone number and so and and it just works like shit. And besides the shity panel and feeling overall, i get also LESS!!! I got like 0,74 ZCash in one day, i get paid every 3 Hours, not like antpool once a day. I get usually now average everytime above 0,64 zCash, so i get MORE, so i do not even feel those 2% no, i only feel it that everything works fucking smooth and beautiful. (Edit: before i got like 0,4 to 0,5- like 20-40% less, when i calculate now i realise, it is like they claim, its just awesome  ) Really i am more then Happy to PAY 2%, but guess WHAT ? I got an mail, that the Fees will drop to 0%, so fuck antpool really fuck that shit hard only fucking problems. I had to restart my device every 1-2 days, it seems already kinda to my like antpool is sabotaging the A9, but for some it seems to work well. But really Slushpool has even a Support, and they wrote me even without writing them, that saw that i connected my A9 and that i can ask them any question, and that the pool god optimised for the a9. I don't know but the difference was just so kinda big, i really fucking love slushpool! Their genius dudes, specialised in pools. Their are just doing everything clean as fuck! I love kinda work like this, it is work done with love and passion, and you feel it and i am sure they have a bright future. EDIT: It may not have as many settings as antpool but it just works much cleaner, smoother and flawless and as specially i get more return, at least with my experience. |
|
|
|
Thank a lot for destroying gpu mining. I hope you make a loss on your shitty asic's. Many of the coins you mine will be asic'ed to death in a year or so anyway and end up dead.
Just open a Internet Café with your graphic cards, but please you do not need to cry here around, when we try to have a productive discussion. Look at the this table my friend: COST OF 51% ATTACK:  Source: https://www.ccn.com/website-outlines-the-cost-of-51-attack-on-altcoins-its-lower-than-you-think/What do you thing why Bitcoin is at 2%, so meand unattackable? Because of the Petahashes of mining power, caused by only asics. So those chinese's are fucking with us the govermant, and we are building a great wall, understand? You are abusing your GPUS by the way, the asics meanwhile to what there purpose is. In a way you are a pervert! |
|
|
|
I had two A9 with 30% rejects, but found a solution. If you guys still have problems with rejects - drop me a pm. I can possibly help
This great BBS won't let me send a pm, so here it is... Greetings, I have a few of these A9 devices and literally HALF of them are crap (31 to 41kSol/s avg hash at the pool.) What kind of interesting solution did you use? Kind regards, Lee --------------------- Wie geht's, Ich habe dieser A9-Mineren und die Haelfte von scheiss davon sind Muell (31 bis 41 kSol Durchschn). Was fuer eine interessante Loesung hast du benutzt? Danke. Tschuss, Lee Did you contacted support to get new firmware dated 6/30? Which pools are you using? I got stable 46 kH/s for any pools now, with 1-2% rejects max. Thank you for your comment. I did indeed update the firmware on those laggard A9 devices and indeed the reject rate went way down but the hash rate is still the same on two different pools. Seems like I got a bunch of duds. My friend bought 2 ZMaster and i bought one, and his run everytime more hashes. The only difference was, that he had bigger windows and wide open, i only had 1 windows open and not fully only tilt. And he had also put ventilator directional to the miners, which blowed the air directed to the window. His miner showed also two cards at around at around 64°-65° Celsius, and only one card at 71° Celsius. Mine ZMaster had two cards running at 72-73° and only one below ~67-68° Celsius. So i had everytime in my backhad that it might be caused by temperature 'underclocking'. We brought now the 3 ZMaster to our "Mining Hub" where we suck out the air with 3 axial fans, and with a pipe construction directly from the miners. Now the miner of him runs at 63° - 71° - 64° and mine runs at 67° - 72° - 65° and now i got steady average slightly over 50 k/Sol right now hourly 51 k/Sol, the hash numbers are from the antpool panel. Only 7,07% rejects so i am at 92,93% accepted rate, also from antpool panel. (Before i got 41-48 k/Sols, and higher temperature like mentioned before) So guys what i figured out is what you might have to optimise or what might cause the problems:
1. Pool :
Some pools have to optimise for the ASICs, since ASICs are quite new for Equihash. So look out for one which says our seems to be already adapted the ASICs.
2. Cooling:
Look at your Innosilicon Panel, it seems to be that the middle card is getting hottest, but the 2 on the side should be below 70°. Otherwise i guess there are underclocking or get to much physical electric resistance caused by heat. So watch out for your temperature and cooling.
3. Network:
I personally had network issues, some switches and some network controller of the asics, can have problems. The Symptoms are that the panels kinda loops in "tunning" but when you look in the logs, you see that he loops at connecting to the pools.
I am still in to solving that problem i ordered a new Switch and maybe some cat5 cables, will see and report how that works out, and if it proves the theory that i might be caused by automatic 100 full duplex.
For now the one originally faulty device, was put in a other network at home at a friends place. The secound one got similar problem after bringing all 3 together, but it could be fixed by just pressing "Update" other Network.
To note, the first days i run mine at home and he run his two at home, and we had no problems at all, beside my heating "problem". |
|
|
|
I had two A9 with 30% rejects, but found a solution. If you guys still have problems with rejects - drop me a pm. I can possibly help
This great BBS won't let me send a pm, so here it is... Greetings, I have a few of these A9 devices and literally HALF of them are crap (31 to 41kSol/s avg hash at the pool.) What kind of interesting solution did you use? Kind regards, Lee --------------------- Wie geht's, Ich habe dieser A9-Mineren und die Haelfte von scheiss davon sind Muell (31 bis 41 kSol Durchschn). Was fuer eine interessante Loesung hast du benutzt? Danke. Tschuss, Lee Try http://powermining.pw, there you will get 100% then you will see it is not depended on you devices, rather it is caused by the pool. Then switch to antpool.com, seems for now like the best one. |
|
|
|
Did anyone receive shipping confirmation for their $2.5K A9 for buying an early batch?
No but Support asked me about my special "notes" and she wanted me to answer quick, like i have to answer before it gets finished for shipping. I guess the coming 1-2 days you will get Tracking ID via SMS from DHL. Like last time. |
|
|
|
So i have been on cryptocompare.com for a while and noticed this morning A9 Zmaster shows payback period as "NEVER" meaning it produces less than the power consumption cost. Can anyone shed some light? Also, is it possible to see the graph or chart showing income per day starting the day it was launched, it would be pretty nice to see how soon it dropped from $150 a day to $80 or so. By the way, here's the link that shows payback period as NEVER https://www.cryptocompare.com/mining/mining-store-5111/innosilicon-a9-zmaster-50-khs/Fistful A9 can't mine Bitcoin Gold as it is stated on this site.. as this crypto forked away 4 days ago... Check this one This Asicminer has ksol like 20-30 GPUs, but wastes power like only 2 GPUS (650 Watt), so much to that. I pay at moment for now 14cent for power, which maybe is much but, i pay 67cent per day for 80-100$ in return. So it is from power consumption view of point, way better then everything else. |
|
|
|
Yeah the discord chat of powermining.pw brought me most far by now. - https://discord.gg/epFf8bFThanks guys! But it still accrues, the one got "fixed" by taking it out and plug it single in to a modem somewhere else. Now it seems like a second one got "infected". So i will watch out for a Switch witch can force 100fdx, is my last hope by now. EDIT: Ok updating netowork settings kinda helped now for now, by pressing just update. |
|
|
|
any updates on this issue and the ssh login stuff? purchased one today and am trying to get all my ducks in a row Yeah, we figured it out, it is some problem with 100fdx duplex. I got really strange symptoms. It should be caused by the "stupid" switch. So one friend took the fault device to his place, there it is plugged right away to the modem. Since then it runs like 100% without nearly 0 rejection. So if you use a switch you need one where you can switch manually 100fdx duplex. Or you can try to force it with a twisted cable, this worked, but after i took the router of it didn't helped anymore even when i put the router back. |
|
|
|
We got 3 pieces now, and they worked all well. But now after transport&network change one won't work anymore, it is looping at "tunning". Sometime later it just restart also. Here are some logs:
Jan 28 15:58:18 InnoMiner kernel: Booting Linux on physical CPU 0x0
Jan 28 15:58:18 InnoMiner kernel: Linux version 4.14.0-xilinx (yex@localhost.localdomain) (gcc version 6.4.0 (Buildroot 2018.02.1)) #1 SMP PREEMPT Sat Jun 9 09:42:21 CST 2018
Jan 28 15:58:18 InnoMiner kernel: CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
Jan 28 15:58:18 InnoMiner kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Jan 28 15:58:18 InnoMiner kernel: OF: fdt: Machine model: xlnx,zynq-7000
Jan 28 15:58:18 InnoMiner kernel: Memory policy: Data cache writealloc
Jan 28 15:58:18 InnoMiner kernel: cma: Reserved 16 MiB at 0x0f000000
Jan 28 15:58:18 InnoMiner kernel: On node 0 totalpages: 65536
Jan 28 15:58:18 InnoMiner kernel: free_area_init_node: node 0, pgdat c0a3b940, node_mem_map cedf0000
Jan 28 15:58:18 InnoMiner kernel: Normal zone: 512 pages used for memmap
Jan 28 15:58:18 InnoMiner kernel: Normal zone: 0 pages reserved
Jan 28 15:58:18 InnoMiner kernel: Normal zone: 65536 pages, LIFO batch:15
Jan 28 15:58:18 InnoMiner kernel: random: fast init done
Jan 28 15:58:18 InnoMiner kernel: percpu: Embedded 16 pages/cpu @cedc7000 s35276 r8192 d22068 u65536
Jan 28 15:58:18 InnoMiner kernel: pcpu-alloc: s35276 r8192 d22068 u65536 alloc=16*4096
Jan 28 15:58:18 InnoMiner kernel: pcpu-alloc: [0] 0 [0] 1
Jan 28 15:58:18 InnoMiner kernel: Built 1 zonelists, mobility grouping on. Total pages: 65024
n 28 15:58:18 InnoMiner kernel: Kernel command line: console=ttyPS0,115200 noinitrd root=ubi0:rootfs ro ubi.mtd=8 earlyprintk rootfstype=ubifs rootwait
Jan 28 15:58:18 InnoMiner kernel: PID hash table entries: 1024 (order: 0, 4096 bytes)
Jan 28 15:58:18 InnoMiner kernel: Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Jan 28 15:58:18 InnoMiner kernel: Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Jan 28 15:58:18 InnoMiner kernel: Memory: 233156K/262144K available (6144K kernel code, 241K rwdata, 1612K rodata, 1024K init, 156K bss, 12604K reserved, 16384K cma-reserved, 0K highmem)
Jan 28 15:58:18 InnoMiner kernel: Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xd0800000 - 0xff800000 ( 752 MB)
lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc0700000 (7136 kB)
.init : 0xc0900000 - 0xc0a00000 (1024 kB)
.data : 0xc0a00000 - 0xc0a3c540 ( 242 kB)
.bss : 0xc0a3c540 - 0xc0a63804 ( 157 kB)
Jan 28 15:58:18 InnoMiner kernel: Preemptible hierarchical RCU implementation.
Jan 28 15:58:18 InnoMiner kernel: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
Jan 28 15:58:18 InnoMiner kernel: Tasks RCU enabled.
Jan 28 15:58:18 InnoMiner kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
Jan 28 15:58:18 InnoMiner kernel: NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
Jan 28 15:58:18 InnoMiner kernel: efuse mapped to d0800000
Jan 28 15:58:18 InnoMiner kernel: slcr mapped to d0802000
Jan 28 15:58:18 InnoMiner kernel: L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
Jan 28 15:58:18 InnoMiner kernel: L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
Jan 28 15:58:18 InnoMiner kernel: L2C-310 erratum 769419 enabled
Jan 28 15:58:18 InnoMiner kernel: L2C-310 enabling early BRESP for Cortex-A9
Jan 28 15:58:18 InnoMiner kernel: L2C-310 full line of zeros enabled for Cortex-A9
Jan 28 15:58:18 InnoMiner kernel: L2C-310 ID prefetch enabled, offset 1 lines
Jan 28 15:58:18 InnoMiner kernel: L2C-310 dynamic clock gating enabled, standby mode enabled
Jan 28 15:58:18 InnoMiner kernel: L2C-310 cache controller enabled, 8 ways, 512 kB
Jan 28 15:58:18 InnoMiner kernel: L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
Jan 28 15:58:18 InnoMiner kernel: zynq_clock_init: clkc starts at d0802100
Jan 28 15:58:18 InnoMiner kernel: Zynq clock init
Jan 28 15:58:18 InnoMiner kernel: sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
Jan 28 15:58:18 InnoMiner kernel: clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Jan 28 15:58:18 InnoMiner kernel: Switching to timer-based delay loop, resolution 3ns
Jan 28 15:58:18 InnoMiner kernel: clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
Jan 28 15:58:18 InnoMiner kernel: timer #0 at d080a000, irq=17
Jan 28 15:58:18 InnoMiner kernel: Console: colour dummy device 80x30
Jan 28 15:58:18 InnoMiner kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=333333)
Jan 28 15:58:18 InnoMiner kernel: pid_max: default: 32768 minimum: 301
Jan 28 15:58:18 InnoMiner kernel: Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan 28 15:58:18 InnoMiner kernel: Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan 28 15:58:18 InnoMiner kernel: CPU: Testing write buffer coherency: ok
Jan 28 15:58:18 InnoMiner kernel: CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Jan 28 15:58:18 InnoMiner kernel: Setting up static identity map for 0x100000 - 0x100060
Jan 28 15:58:18 InnoMiner kernel: Hierarchical SRCU implementation.
Jan 28 15:58:18 InnoMiner kernel: smp: Bringing up secondary CPUs ...
Jan 28 15:58:18 InnoMiner kernel: CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
Jan 28 15:58:18 InnoMiner kernel: smp: Brought up 1 node, 2 CPUs
Jan 28 15:58:18 InnoMiner kernel: SMP: Total of 2 processors activated (1333.33 BogoMIPS).
Jan 28 15:58:18 InnoMiner kernel: CPU: All CPU(s) started in SVC mode.
Jan 28 15:58:18 InnoMiner kernel: devtmpfs: initialized
Jan 28 15:58:18 InnoMiner kernel: VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Jan 28 15:58:18 InnoMiner kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
Jan 28 15:58:18 InnoMiner kernel: futex hash table entries: 512 (order: 3, 32768 bytes)
Jan 28 15:58:18 InnoMiner kernel: pinctrl core: initialized pinctrl subsystem
Jan 28 15:58:18 InnoMiner kernel: NET: Registered protocol family 16
Jan 28 15:58:18 InnoMiner kernel: DMA: preallocated 256 KiB pool for atomic coherent allocations
Jan 28 15:58:18 InnoMiner kernel: cpuidle: using governor menu
Jan 28 15:58:18 InnoMiner kernel: hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
Jan 28 15:58:18 InnoMiner kernel: hw-breakpoint: maximum watchpoint size is 4 bytes.
oMiner kernel: zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0xd0840000
Jan 28 15:58:18 InnoMiner kernel: zynq-pinctrl 700.pinctrl: zynq pinctrl initialized
Jan 28 15:58:18 InnoMiner kernel: e0000000.serial: ttyPS1 at MMIO 0xe0000000 (irq = 26, base_baud = 6249999) is a xuartps
Jan 28 15:58:18 InnoMiner kernel: e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 27, base_baud = 6249999) is a xuartps
Jan 28 15:58:18 InnoMiner kernel: console [ttyPS0] enabled
Jan 28 15:58:18 InnoMiner kernel: vgaarb: loaded
Jan 28 15:58:18 InnoMiner kernel: SCSI subsystem initialized
Jan 28 15:58:18 InnoMiner kernel: usbcore: registered new interface driver usbfs
Jan 28 15:58:18 InnoMiner kernel: usbcore: registered new interface driver hub
Jan 28 15:58:18 InnoMiner kernel: usbcore: registered new device driver usb
Jan 28 15:58:18 InnoMiner kernel: media: Linux media interface: v0.10
Jan 28 15:58:18 InnoMiner kernel: Linux video capture interface: v2.00
Jan 28 15:58:18 InnoMiner kernel: pps_core: LinuxPPS API ver. 1 registered
Jan 28 15:58:18 InnoMiner kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
ered
Jan 28 15:58:18 InnoMiner kernel: EDAC MC: Ver: 3.0.0
Jan 28 15:58:18 InnoMiner kernel: FPGA manager framework
Jan 28 15:58:18 InnoMiner kernel: fpga-region fpga-full: FPGA Region probed
Jan 28 15:58:18 InnoMiner kernel: Advanced Linux Sound Architecture Driver Initialized.
Jan 28 15:58:18 InnoMiner kernel: clocksource: Switched to clocksource arm_global_timer
Jan 28 15:58:18 InnoMiner kernel: NET: Registered protocol family 2
Jan 28 15:58:18 InnoMiner kernel: TCP established hash table entries: 2048 (order: 1, 8192 bytes)
Jan 28 15:58:18 InnoMiner kernel: TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
Jan 28 15:58:18 InnoMiner kernel: TCP: Hash tables configured (established 2048 bind 2048)
Jan 28 15:58:18 InnoMiner kernel: UDP hash table entries: 256 (order: 1, 8192 bytes)
Jan 28 15:58:18 InnoMiner kernel: UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
Jan 28 15:58:18 InnoMiner kernel: NET: Registered protocol family 1
Jan 28 15:58:18 InnoMiner kernel: RPC: Registered named UNIX socket transport module.
Jan 28 15:58:18 InnoMiner kernel: RPC: Registered udp transport module.
Jan 28 15:58:18 InnoMiner kernel: RPC: Registered tcp transport module.
Jan 28 15:58:18 InnoMiner kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan 28 15:58:18 InnoMiner kernel: PCI: CLS 0 bytes, default 64
Jan 28 15:58:18 InnoMiner kernel: hw perfevents: no interrupt-affinity property for /pmu@f8891000, guessing.
Jan 28 15:58:18 InnoMiner kernel: hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
Jan 28 15:58:18 InnoMiner kernel: workingset: timestamp_bits=30 max_order=16 bucket_order=0
Jan 28 15:58:18 InnoMiner kernel: jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
Jan 28 15:58:18 InnoMiner kernel: io scheduler noop registered
Jan 28 15:58:18 InnoMiner kernel: io scheduler deadline registered
Jan 28 15:58:18 InnoMiner kernel: io scheduler cfq registered (default)
Jan 28 15:58:18 InnoMiner kernel: io scheduler mq-deadline registered
Jan 28 15:58:18 InnoMiner kernel: io scheduler kyber registered
Jan 28 15:58:18 InnoMiner kernel: dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
Jan 28 15:58:18 InnoMiner kernel: dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
Jan 28 15:58:18 InnoMiner kernel: brd: module loaded
Jan 28 15:58:18 InnoMiner kernel: loop: module loaded
Jan 28 15:58:18 InnoMiner kernel: libphy: Fixed MDIO Bus: probed
Jan 28 15:58:18 InnoMiner kernel: CAN device driver interface
Jan 28 15:58:18 InnoMiner kernel: libphy: MACB_mii_bus: probed
Jan 28 15:58:18 InnoMiner kernel: macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 29 (a0:b0:45:02:b5:fb)
Jan 28 15:58:18 InnoMiner kernel: RTL8211E Gigabit Ethernet e000b000.ethernet-ffffffff:00: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=e000b000.ethernet-ffffffff:00, irq=POLL)
Jan 28 15:58:18 InnoMiner kernel: e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
Jan 28 15:58:18 InnoMiner kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
Jan 28 15:58:18 InnoMiner kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jan 28 15:58:18 InnoMiner kernel: ehci-pci: EHCI PCI platform driver
Jan 28 15:58:18 InnoMiner kernel: usbcore: registered new interface driver usb-storage
Jan 28 15:58:18 InnoMiner kernel: i2c /dev entries driver
Jan 28 15:58:18 InnoMiner kernel: cdns-i2c e0004000.i2c: 100 kHz mmio e0004000 irq 23
Jan 28 15:58:18 InnoMiner kernel: IR NEC protocol handler initialized
Jan 28 15:58:18 InnoMiner kernel: IR RC5(x/sz) protocol handler initialized
Jan 28 15:58:18 InnoMiner kernel: IR RC6 protocol handler initialized
Jan 28 15:58:18 InnoMiner kernel: IR JVC protocol handler initialized
Jan 28 15:58:18 InnoMiner kernel: IR Sony protocol handler initialized
Jan 28 15:58:18 InnoMiner kernel: IR SANYO protocol handler initialized
Jan 28 15:58:18 InnoMiner kernel: IR Sharp protocol handler initialized
Jan 28 15:58:18 InnoMiner kernel: IR MCE Keyboard/mouse protocol handler initialized
Jan 28 15:58:18 InnoMiner kernel: IR XMP protocol handler initialized
Jan 28 15:58:18 InnoMiner kernel: cdns-wdt f8005000.watchdog: Xilinx Watchdog Timer at d0946000 with timeout 10s
Jan 28 15:58:18 InnoMiner kernel: EDAC MC: ECC not enabled
Jan 28 15:58:18 InnoMiner kernel: Xilinx Zynq CpuIdle Driver started
Jan 28 15:58:18 InnoMiner kernel: sdhci: Secure Digital Host Controller Interface driver
Jan 28 15:58:18 InnoMiner kernel: sdhci: Copyright(c) Pierre Ossman
Jan 28 15:58:18 InnoMiner kernel: sdhci-pltfm: SDHCI platform and OF driver helper
Jan 28 15:58:18 InnoMiner kernel: mmc0: SDHCI controller on e0100000.sdhci [e0100000.sdhci] using ADMA
Jan 28 15:58:18 InnoMiner kernel: ledtrig-cpu: registered to indicate activity on CPUs
Jan 28 15:58:18 InnoMiner kernel: usbcore: registered new interface driver usbhid
Jan 28 15:58:18 InnoMiner kernel: usbhid: USB HID core driver
Jan 28 15:58:18 InnoMiner kernel: nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
Jan 28 15:58:18 InnoMiner kernel: nand: Micron MT29F2G08ABAEAWP
Jan 28 15:58:18 InnoMiner kernel: nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Jan 28 15:58:18 InnoMiner kernel: nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Jan 28 15:58:18 InnoMiner kernel: Bad block table found at page 131008, version 0x01
Jan 28 15:58:18 InnoMiner kernel: Bad block table found at page 130944, version 0x01
Jan 28 15:58:18 InnoMiner kernel: 11 ofpart partitions found on MTD device pl35x-nand
Jan 28 15:58:18 InnoMiner kernel: Creating 11 MTD partitions on "pl35x-nand":
Jan 28 15:58:18 InnoMiner kernel: 0x000000000000-0x000000400000 : "bootloader"
Jan 28 15:58:18 InnoMiner kernel: 0x000000400000-0x000000480000 : "env"
Jan 28 15:58:18 InnoMiner kernel: 0x000000480000-0x000000500000 : "dtb-main"
Jan 28 15:58:18 InnoMiner kernel: 0x000000500000-0x000000580000 : "dtb-alt"
Jan 28 15:58:18 InnoMiner kernel: 0x000000580000-0x000000980000 : "fpga-main"
Jan 28 15:58:18 InnoMiner kernel: 0x000000980000-0x000000d80000 : "fpga-alt"
Jan 28 15:58:18 InnoMiner kernel: 0x000000d80000-0x000001280000 : "kernel-main"
Jan 28 15:58:18 InnoMiner kernel: 0x000001280000-0x000001780000 : "kernel-alt"
Jan 28 15:58:18 InnoMiner kernel: 0x000001780000-0x0000074c0000 : "rootfs-main"
Jan 28 15:58:18 InnoMiner kernel: 0x0000074c0000-0x00000d200000 : "rootfs-alt"
Jan 28 15:58:18 InnoMiner kernel: 0x00000d200000-0x00000dc00000 : "config"
Jan 28 15:58:18 InnoMiner kernel: fpga_manager fpga0: Xilinx Zynq FPGA Manager registered
Jan 28 15:58:18 InnoMiner kernel: NET: Registered protocol family 10
Jan 28 15:58:18 InnoMiner kernel: Segment Routing with IPv6
Jan 28 15:58:18 InnoMiner kernel: sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
Jan 28 15:58:18 InnoMiner kernel: NET: Registered protocol family 17
Jan 28 15:58:18 InnoMiner kernel: can: controller area network core (rev 20170425 abi 9)
Jan 28 15:58:18 InnoMiner kernel: NET: Registered protocol family 29
Jan 28 15:58:18 InnoMiner kernel: can: raw protocol (rev 20170425)
Jan 28 15:58:18 InnoMiner kernel: can: broadcast manager protocol (rev 20170425 t)
Jan 28 15:58:18 InnoMiner kernel: can: netlink gateway (rev 20170425) max_hops=1
Jan 28 15:58:18 InnoMiner kernel: Registering SWP/SWPB emulation handler
Jan 28 15:58:18 InnoMiner kernel: ubi0: attaching mtd8
Jan 28 15:58:18 InnoMiner kernel: ubi0: scanning is finished
Jan 28 15:58:18 InnoMiner kernel: ubi0: attached mtd8 (name "rootfs-main", size 93 MiB)
Jan 28 15:58:18 InnoMiner kernel: ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Jan 28 15:58:18 InnoMiner kernel: ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Jan 28 15:58:18 InnoMiner kernel: ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
Jan 28 15:58:18 InnoMiner kernel: ubi0: good PEBs: 746, bad PEBs: 0, corrupted PEBs: 0
Jan 28 15:58:18 InnoMiner kernel: ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
Jan 28 15:58:18 InnoMiner kernel: ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1752358700
Jan 28 15:58:18 InnoMiner kernel: ubi0: available PEBs: 0, total reserved PEBs: 746, PEBs reserved for bad PEB handling: 40
Jan 28 15:58:18 InnoMiner kernel: ubi0: background thread "ubi_bgt0d" started, PID 729
Jan 28 15:58:18 InnoMiner kernel: hctosys: unable to open rtc device (rtc0)
Jan 28 15:58:18 InnoMiner kernel: of_cfs_init
Jan 28 15:58:18 InnoMiner kernel: of_cfs_init: OK
Jan 28 15:58:18 InnoMiner kernel: ALSA device list:
Jan 28 15:58:18 InnoMiner kernel: No soundcards found.
Jan 28 15:58:18 InnoMiner kernel: UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs", R/O mode
Jan 28 15:58:18 InnoMiner kernel: UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Jan 28 15:58:18 InnoMiner kernel: UBIFS (ubi0:0): FS size: 87740416 bytes (83 MiB, 691 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
Jan 28 15:58:18 InnoMiner kernel: UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB)
Jan 28 15:58:18 InnoMiner kernel: UBIFS (ubi0:0): media format: w4/r0 (latest is w5/r0), UUID 5A1BAB54-0036-4152-B314-61D156E3B135, small LPT model
Jan 28 15:58:18 InnoMiner kernel: VFS: Mounted root (ubifs filesystem) readonly on device 0:12.
Jan 28 15:58:18 InnoMiner kernel: devtmpfs: mounted
Jan 28 15:58:18 InnoMiner kernel: Freeing unused kernel memory: 1024K
Jan 28 15:58:18 InnoMiner systemd[1]: System time before build time, advancing clock.
Jan 28 15:58:18 InnoMiner systemd[1]: systemd 237 running in system mode. (-PAM -AUDIT -SELINUX -IMA -APPARMOR -SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS -ACL -XZ +LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN -PCRE2 default-hierarchy=hybrid)
Jan 28 15:58:18 InnoMiner systemd[1]: Detected architecture arm.
Jan 28 15:58:18 InnoMiner systemd[1]: Set hostname to <InnoMiner>.
Jan 28 15:58:18 InnoMiner systemd[1]: Initializing machine ID from random generator.
Jan 28 15:58:18 InnoMiner systemd[1]: Installed transient /etc/machine-id file.
Jan 28 15:58:18 InnoMiner systemd[1]: File /usr/lib/systemd/system/systemd-journald.service:35 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
Jan 28 15:58:18 InnoMiner systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
Jan 28 15:58:18 InnoMiner systemd[1]: Created slice System Slice.
Jan 28 15:58:18 InnoMiner systemd[1]: Listening on udev Kernel Socket.
Jan 28 15:58:18 InnoMiner systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
Jan 28 15:58:18 InnoMiner systemd-journald[747]: Journal started
Jan 28 15:58:18 InnoMiner systemd-journald[747]: Runtime journal (/run/log/journal/9163954dcfdc48bd91b3c0124f184884) is 640.0K, max 5.0M, 4.3M free.
Jan 28 15:58:18 InnoMiner systemd-sysctl[740]: Couldn't write '16' to 'kernel/sysrq', ignoring: No such file or directory
Jan 28 15:58:18 InnoMiner systemd-sysctl[740]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory
Jan 28 15:58:18 InnoMiner systemd[1]: Starting Flush Journal to Persistent Storage...
Jan 28 15:58:18 InnoMiner systemd[1]: Started udev Kernel Device Manager.
Jan 28 15:58:18 InnoMiner systemd[1]: Started Rebuild Journal Catalog.
Jan 28 15:58:18 InnoMiner systemd[1]: Started udev Coldplug all Devices.
Jan 28 15:58:18 InnoMiner systemd-journald[747]: Runtime journal (/run/log/journal/9163954dcfdc48bd91b3c0124f184884) is 640.0K, max 5.0M, 4.3M free.
Jan 28 15:58:18 InnoMiner systemd[1]: Starting Update is Completed...
Jan 28 15:58:18 InnoMiner systemd[1]: Starting Network Service...
Jan 28 15:58:18 InnoMiner systemd[1]: Started Flush Journal to Persistent Storage.
Jan 28 15:58:18 InnoMiner systemd[1]: Started Update is Completed.
Jan 28 15:58:18 InnoMiner systemd[1]: Starting Create Volatile Files and Directories...
Jan 28 15:58:18 InnoMiner systemd-tmpfiles[1251]: [/etc/tmpfiles.d/var-factory.conf:7] Duplicate line for path "/var/lib/systemd", ignoring.
Jan 28 15:58:18 InnoMiner systemd-tmpfiles[1251]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Jan 28 15:58:18 InnoMiner systemd-tmpfiles[1251]: [/usr/lib/tmpfiles.d/var.conf:21] Duplicate line for path "/var/lib", ignoring.
Jan 28 15:58:18 InnoMiner systemd-networkd[1249]: Enumeration completed
Jan 28 15:58:18 InnoMiner systemd[1]: Started Network Service.
Jan 28 15:58:19 InnoMiner systemd[1]: Found device /dev/ttyPS0.
Jan 28 15:58:19 InnoMiner systemd-udevd[980]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 28 15:58:19 InnoMiner systemd-networkd[1249]: sit0: Link is not managed by us
Jan 28 15:58:19 InnoMiner systemd-networkd[1249]: lo: Link is not managed by us
Jan 28 15:58:19 InnoMiner systemd-networkd[1249]: eth0: IPv6 successfully enabled
Jan 28 15:58:19 InnoMiner kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 28 15:58:19 InnoMiner systemd-udevd[1257]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 28 15:58:19 InnoMiner systemd-udevd[1253]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 28 15:58:20 InnoMiner systemd[1]: Started Create Volatile Files and Directories.
Jan 28 15:58:20 InnoMiner systemd[1]: Starting Network Name Resolution...
Jan 28 15:58:20 InnoMiner systemd[1]: Starting Network Time Synchronization...
|
|
|
|
|
How could you order and got delivered?
When first delivery is - Shipping: August 24th- Sep.4th ?
Where there a first batch, and it is only 2nd batch left?
Yeah i guess so the first batch cost 2500$ or? and the new one like 875$
|
|
|
|
First, PSU is VERY VERY noisy; much more than ASIC itself. Probably a dysfunction.
And 25%(!!!) of shares are rejected! 25%! On NiceHash as nanopool.
So, not 50k at all but rather 35-40. That's a shame.
Is this trouble solved? I have same issue. A9 shows 50% reject and only 50k hashrate in some pools. Mine arrived today, and i have first tried balanced mode from the performance settings, right now i am trying factory mode and i get better accepted - 88.2% I will test tomorrow the performance mode, i guess this will get it slightly up. Right now with "Factory mode" (settings) i get hours average 48 ksol. I am sure this will flatten out, because i hav erecurring peaks with 50+ like even sometimes 60ksol. So this solves the problems with fluctuation but you have to look at average, because of the occurring peaks. Which pool are you using? Have you tried changing performance mode? Many pools are not yet configured for asic equihash! I try four different pool (f2pool, flypool, nanopool, nicehash) : strictly the same reject rate. I am not the only one with this problem. Try Powermining.pw, i get 100% and 0% rejections for testing, then you will see if it is caused by the pool or your device. But we would need more hashrate there, to get more valid blocks there. Otherwise go to Antpool, there you won't get below 88%, i have right now there 95% Interesting it dropped again to 88.3, i tried different ports. So it really depends on pool, i guess there maybe needed further adjustments. This A9 are my first ASICs, so how is that if a pool is "overloaded", isn't it maybe normal if a pool is over see or overloaded that i get more rejections? |
|
|
|
First, PSU is VERY VERY noisy; much more than ASIC itself. Probably a dysfunction.
And 25%(!!!) of shares are rejected! 25%! On NiceHash as nanopool.
So, not 50k at all but rather 35-40. That's a shame.
I think rejected shares are pool dependent. I was getting 94% accepted shares on FlyPool and getting 97% accepted shares on Antpool. Never tried NH or Nanopool. Nevertheless, 24 hour average hash rate is always over 50k sols. [spoiler]  [/spoiler] Do you still get 97%? I am getting now with performance mode 89.3%. Any ideas how i could improve that? Maybe changing router? Because i have the best internet wich is buyable for ordinary customer. I am from Europe near Germany, does it have any impact when i use a Asian Pool? I am using right now antpool. At which temperature are the 3 pieces of one Z9 running? Mine are like stady 71°, i think the air Flow of the room could be better since it gets a slight wormer. I don’t pay attention to the A9 dashboard anymore which I think is inaccurate since A9 and 2 Z9s are showing 80 k sols on the pool side 24h average steadily. Rest of my z9s are delivered today. My z9s are running at 15 ksol at 725 MHz and chip temp around 80 or less. I didn’t increase frequency up to 750 because my ambient temp is high around 100 F. Sorry i wrote Z9 but i meant the A9 xD It is really about the pool, i got now 100% so no rejections at all!  |
|
|
|
Did anyone figure out the id/pw to ssh into the Innosilicon A9?
Just use some IP Scanner, or look in to the admin panel of your router. There you will see the IP of your A9, just put that in to the adressbar of your browser. Then it pops up login panel, there you just put: Username: Admin Password: Admin Then you are in the Panel, there you have to chose your pool and you are up and running!  |
|
|
|
|
