Topic: A4 Dominator - Pre-Order Group Buy - 280mh, roughly 1000w, $1800 + shipping - page 27. (Read 122581 times)

Hi Guys,

I have my A4 miner now for a several days. Batch 3 running V2.0.2 Beta.

I am mining @Prohashing and it drop's several times a day. I added a rule that sends ma a notify when it comes below 200 Mh/s.

 Total hashrate      190.885 MH/s   53 minutes ago 
 Total hashrate      167.024 MH/s   09:05:20 
 Total hashrate      133.619 MH/s   08:35:01 
 Total hashrate      181.340 MH/s   07:35:26 
 Total hashrate      124.075 MH/s   05:00:01

I tried different settings (low speed, higher speed and difficulty). With all settings it drops.

Does anyone knows what more i can do?

Just updated to v2.02 Beta (from v2.01 / for Batch 3 only)

** Batch 1 and 2 A4s need the MCU firmware updates **


Current setup 420MH + 420MH +420MH +280MH

From cgminer:

Controller 1 - 420MH (5s):412.3M A:13967360 R:106496 WU:290230.8/m
Controller 2 - 420MH (5s):412.4M A:21749760 R:40960 WU:368271.5/m
Controller 3 - 420MH (5s):412.1M A:610304 R:28672 WU:365610.1/m
Controller 4 - 280MH (5s):275.2M A:3678208 R:12288 WU:227760.6/m

From Poolside / Prohashing.com

(after 15 mins)




(after 30 some minutes)




Ran one of the bigger miner to Nicehash and after 10 minutes




Do we have a winner here?

Will let it run for while more to see if any drops or restarts.

Anybody knows what is the recommended password string for Prohashing?

I recall Steve@Prohashing mentioning h=50 and g=off, do we still need that?

Also on another note.... those who are near your A4s... please check closely the quality of the fans... overheating maybe result of "used" fans... please check to verify.

I just upgraded to V2.02. Although it has not run long until now, the results do not look good, I think:




After about 15 Minutes of mining at pool:


Edit:
Seems it does work now, first it took some more minutes and now, even after restart it gets around ~275MH/s:


I would like to test mining on nicehash, but it seems I set wrong pool data. Can someone help me out?
What I tried:
Pool: stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub (also tried without #xnsub)
Login: BTC Address
Pass: x

Doing so the pool is not even listed in the pool section :-(

Edit2:
Got it now, Nicehash is also working. It seems I did not "save" correctly after deleting the #xnsub. I double checked this now and after deleting that part it worked.

Nice. I've got B2 with them as well so hopefully you get some good news going forward and then I can get mine sorted out. 


hashtocoins is a pool I thought about using but I don't really have the time to trade out of each coin daily unfortunately. 

Please let us know what comes of it, I am ready to wire them some money, but not if the profit switching doesn't work.

Agreed. Once upon a time the A2 110MHs was also a "large" scrypt miner, tweaking the diff levels got it to mine easily. Some mod versions can even OC beyond specs with ease. With A4s faster chips, not able to handle large hash is not justified, rather firmware and code design are likely culprit - no pool ops can help you if board drops or restarts happens randomly. Its like buying a new windows PC and randomly reboots or gives blue screen -- 99% will point to faulty hardware etc.... until you reseat that RAM or take out that rouge GPU and installing the latest drivers.... sounds familiar?

My ISP will be doing the B3 firmware upgrade today to v2.02.

Keeping fingers crossed that this version will fix the restarts.

Will test them on Prohashing and Nicehash - these 2 pools are usually brutal in coin/profit switching so I know it will be a baptism of fire to test the new firmware.

Its past midnight my time but I have discussed with the team in my ISP on the upgrade path.

Hopefully good news in the next few hours.

Sorry but this is nonsense.  I have multiple 5 cube Titan rigs hashing away at 400MH easily at Prohashing, Nicehash and Clevermining without issue. This has nothing to do with "large hash rate" but rather bad design and manufacturing decisions.

Rather than blame the pool operators, Innosilicon should be reaching out to the major pool operators and work directly with them on behalf of the customers who are suffering.  

What kind of PSU do you use? I just wanted to test my newly arrived B3 but unfortunately my Enermax 1200W PSU stopped after around 1 minute of hashing and does not start now.

Very true, Inno could contract with someone to do the repairs.  Inno needs to step up and get these miners fixed.  Not lay it on the customer to fix it. 

I personally would like to see a compromise with someone doing warranty work on behalf of Inno in the US. I'm sure there are people here that could do the work for Inno if they were compensated in some way.

The issue for me is not the ability to do the work but the time it takes to do it all. When I made this purchase I didn't for a second think I would have to be taking apart the miner and re-soldering components on it. That's a lot of hours out of my day to do all that then set it back up for testing and what if there is an issue? Now I have to send the board back to China? -- oh wait, 45 day warranty.... now it looks like I'll be buying a new board.

which brings the question... How much are replacement boards that are already fixed? Maybe Inno can do some sort of exchange program?

This can easily go really really bad for owners but I see opportunity here for Inno to make it right. It is my belief that Inno will make things right at this time but I definitely wish they were more timely in resolving this but I understand I was an early adopter of this product. I don't mind waiting for fixes but I will mind if I'm stuck with something that should be repaired under warranty if it was shipped with a now known design flaw.

I want to see Inno offering to actually fix B1 and B2 miners.  Anything less is unacceptable.  This does not mean sending parts for us to fix your broken miners.  This means Inno is either replacing the miners, or replacing the boards.  NOT us finding an electronics shop to do repairs on our dime... 

For B3 miners please keep us updated if you try out the v2.0.2 build and let us know if it is actually working for you. 

Hi all,

Really sorry for the delay of our reply and the troubles that the bugs have brought to you.

For batch 3, v2.0.1 - > we found that miner will get stopped at some multi-pools.
So we released v2.0.2. And from our customers' feedback it fixed the bugs when dealing with multi-pools.

Here is the link of v2.0.2. If you have batch 3 miners please update.
https://www.dropbox.com/s/9umhsbtky6t1c6j/2.0.2beta.rar?dl=0

For batch 1 and 2 users, we are preparing sending the MCU/jigs for updating the MCU firmware to you recently. Just some patience please. We will fix everything for you.

It's a hard time for us to deal with the bugs and update software versions in such a short time. We know there is some bugs with the software and we tried our best to fix them for you.

We really appreciate your understanding and support as always.

The thing is not every batch 3 user know this forum. We will invite them to come here and share their experiences of using batch 3 miners.

For dealing with some multi-pools, we found that some pools cannot deal with our miners very well for the large hash rate - > hash rate always drops to around 240Msh rather than 275 or more.

Here is a mining pool that we recommend to you: hashtocoins

Also we've contacted with some pools, below is the reply from Chris at prohashing with his agreement to share the info:
“We think the cause is that since we switch coins more frequently than Litecoin only pools, the miners are stressed harder and they are more prone to overheat.  Our users have found that slightly lowering the clock speed of the miners resolves the issue.

Yesterday, we paid 30% more per MH/s than a Litecoin-only pool, so even if the miner is only getting 245 MH/s here instead of the 280 MH/s, you will still be earning 14% more on Prohashing.

I will be glad to help if you have any questions.

Thanks,

-Chris Sokolowski
Manager, Prohashing.com“

guys.... i got like 5 PMs from members asking me about where I do the solo LTC mining, what settings to use, how big of hash to get a decent chance to strike a block etc. etc. I am sorry, I cant be replying to everyone so being the good guy that I am ... I will just cut-paste my last reply in PM here :

====
set 4096 on the cgminer GUI

and in the password, set "diff_6144"

adjust accordingly.

I dont like the LTC solo at Nicehash.

I mine at tbdice.org, its solo mines LTC and merge mine DOGE at same time, so you get more rewards. Also the pool built on -ckpool so its lightning fast with cgminer - since he wrote cgminer too.

POOL: stratum+tcp://tbdice.org:13333
USER: <>
PASSWORD: diff_6144:<>

I know the top miner there has a massive 12GH/s but my A4s was able to steal 2 blocks this week with my 1.2GH .... 25 LTC x $3.51 = nice beer money 

..

..

hey, I have a great idea.... why don't we all the A4 owners crash the party at that solo pool and drown our sorrows in lottery.

Thanks @citronick for the update.  It does not sound like Batch 3 fixes the issue.  At this time I have updated the original post for this thread with a HUGE WARNING to potential buyers of the A4.  The response so far from Inno is completely unacceptable.  B3 has not fixed the issues, B1 and B2 owners have been told to pound sand at this point.  I will try to keep the OP updated as this soap opera unfolds.  Right now it is looking pretty bad.

The mining community is getting the shaft from Innosilicon at this point.  I can only hope they see the error of their ways.  This is absolutely a turn for the worse for them.  They need to fix the A4, and they need to send replacement boards out to customers at their expense.

At this point I feel I should apologize to this community for setting up the group buy.  Innosilicon HAD a good reputation here with past products.  I had no idea that they would not stand up and represent themselves with the new product. 

My batch is 3 with firmware v2.01

I confirm - mining on pure LTC or solo LTC is all good...... BUT.....

... the moment this miner goes to a multicoin pool, prohashing, nicehash - the roller coaster starts.

I may not need to power cycle like batch 1 and 2 miners.... but cgminer restarts happens randomly -- I bet when switching coins. So ... is there some diff_XXXX settings for this miner? I tried so many settings to make it stable but no luck. Some promising settings survived only a few hours.

Most of the time when I give up trying.... I just run it on a solo LTC pool for the last 1 week.

I think this investment is really going down to the dogs, so unlucky and pathetic ... that the gods must have seen how upset I am and quickly bestowed me with 2 LTC solo blocks within 48 hours!!! Yes, I was speechless when 25 x LTC rolled into my wallet TWICE in the period of 48 hours.

I should just leave it mining in the solo pool and collect something by lottery rather than nothing...

As the group buy guy who shot 50 units their way. You should be able to get a jig. Send a letter to crypto press
Coindrsk etc. that would piss in their soup. Slow further sales at least. I've so far in pm's got about 9
to pass on A4's ... one was a plus 10 order.  Dumb as way to try and sell units imho by
not honoring warranty.

I wonder how they identify their customers because mine technically came from a US reseller?  

Guess I need to get on the ball and start finding out what the next steps are

...Is Chloe only available via Skype or should I start firing off e-mails?