Pages:
Author

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

sr. member
Activity: 1078
Merit: 255
Yep refering to minning only LTC. Even GAME should give you at least 30% more income if not more. And that is not counting minning some new shitcoins. Like MILO or what hot is at that moment.
hero member
Activity: 952
Merit: 508
You should mine some proper coins not LTC
Im the same boat, even using nicehash and other coinswapping mining sites, cant generate squat for income compared to electric.
Can you suggest any "proper" coins?

I think he was assuming I was referring to mining only LTC for $8-9 a day out of 413MH
legendary
Activity: 1109
Merit: 1000
You should mine some proper coins not LTC
Im the same boat, even using nicehash and other coinswapping mining sites, cant generate squat for income compared to electric.
Can you suggest any "proper" coins?
sr. member
Activity: 1078
Merit: 255
You should mine some proper coins not LTC
hero member
Activity: 952
Merit: 508
Nice price got reduced to 1600. Might think later about buying one or 2 more.

That's because of difficulty, my 3 cube A4 when working only makes about $8-9 a day right now for 413MH.

newbie
Activity: 39
Merit: 0
Nice price got reduced to 1600. Might think later about buying one or 2 more.
full member
Activity: 243
Merit: 108
Innosilicon ASIC official representative
Where do you buy your A4s?

I need to do some asics shopping, anyone know a good place? I am in EU.

Thanks for your interest. You can go to the A4 online store at http://www.innosilicon.com/html/a4-miner/ to make your order.

Innosilicon A4 Team
hero member
Activity: 952
Merit: 508

So in summary you are saying that this reboot issue isn't going to be fixed by a new version of the SD Card software and clearly Inno knows about this issue because they coded the boards this way, is that correct?

I've done everything short of creating a youtube video demonstrating the problem and so far the only response I get from Inno is denial of the problem or to completely ignore it and blame something else.

Thanks again for your work and efforts on this, I hope you can bring something to the table that fixes or improves the operation of these A4's for all of us.

No it is going to be fixed, the latest version has the reboot thing commented out so it was there , a lot of this is speculation as to why on my part but oh well. I can say it will be a lot better that is for sure, the latest version we are working with is a lot better off, right now doing some side by side comparisons to see over time making a judgement over a short time of hashing can be misleading.
Jarrid

This is some very exciting news! -- I would love to test this new version if/when you think its ready.

Thanks for the clarification
full member
Activity: 188
Merit: 100
I have been running with a local proxy as well  mostly so I can get a good hash rate graph. I have been working with Inno to improve the driver along with others. So far I have made some progress with both prohashing and nicehash, although the fixes for nicehash require hardware mods at least with what information I have on the hash board MCU firmware.

I was testing just one hash board but I was able to get 68-72Mh/s on Prohash and mid 60s on nicehash. The problem with nicehash is all the pool changes and stratum disconnects causes the hash board to loose it and some times they don't come back.

I have not heard out of Inno in over a week so I don't know any of their thoughts on the process, I finally got the jig two months later than expected but it was broke but I had already figured out how to flash the new firmware from one board to the another anyway so not as big of a deal.

Anyway just asking does anyone have and odd behaviors I need to look at, I know most of them but I will try to answer what I can and any feature requests, might as well try all of the above Smiley

While they let me have access to the cgminer code I am pretty sure it is not what is on 2.0.2 beta, there is no shutdown routine in there and they tried to fix a slow down issue that I don't see a fix for but that is not a problem already worked around it.

I have been using a proxy but that is mostly for switching pools which seems to break them easily and getting a graph on hash rate.

Thanks
Jarrid




Thanks for your work on this, do you have a solution to stop the A4 from rebooting itself any time it sees a get failure?

This issue is really my only issue with it.


Actually the code they shared with me didn't have the shutdown routine in it which shocked me , for some reason had a sleep(9) in the main function, i think they tried the reboot plan is this, when it gets a pool disconnect the boards gets reset during that time the program cant communicate and just goes into almost always a situation it can't recover from so they do a reboot. The hash boards must have some kind of watchdog type thing that after it gets communicated with and stops it resets it's self and by that time the pi should be back up not an efficient plan. I have solved that but it has two outcomes at this point , another flashing for the boards or hardware mods and board flashing which are not super hard but does require soldering.

Since I have made the mods I have been mining Nicehash for 3 days now with no user intervention required, I had been trying to handle different errors differently but now I am thinking any error just reset the board after a little firmware mod instead of taking the board 2~3 seconds to get started it now takes like 0.1 seconds. I dont have access to the MCU firmware code so I dont know if a software update fix only is possible and I may have went overkill but something causes the board to stop talking and from the logic analyzer point of view it *looks* like the hash board is the issue. I dont know if a command is locking the board up I need to look into that a bit more.

My 1 day average on nicehash for 10 hash boards is 642 MH/s so that would make 128.4 MH/s for a 136 unit and 256.8 for a 270. on prohashing it was a bit better , the diff I think gets way to high on nicehash to quickly ,I am seeing 65K on mine I think that is to high and setting it doesn't make any difference.





So in summary you are saying that this reboot issue isn't going to be fixed by a new version of the SD Card software and clearly Inno knows about this issue because they coded the boards this way, is that correct?

I've done everything short of creating a youtube video demonstrating the problem and so far the only response I get from Inno is denial of the problem or to completely ignore it and blame something else.

Thanks again for your work and efforts on this, I hope you can bring something to the table that fixes or improves the operation of these A4's for all of us.

No it is going to be fixed, the latest version has the reboot thing commented out so it was there , a lot of this is speculation as to why on my part but oh well. I can say it will be a lot better that is for sure, the latest version we are working with is a lot better off, right now doing some side by side comparisons to see over time making a judgement over a short time of hashing can be misleading.
Jarrid
newbie
Activity: 39
Merit: 0
really looking forward updated firmware and increased hashrate on nicehash.
hero member
Activity: 952
Merit: 508
I have been running with a local proxy as well  mostly so I can get a good hash rate graph. I have been working with Inno to improve the driver along with others. So far I have made some progress with both prohashing and nicehash, although the fixes for nicehash require hardware mods at least with what information I have on the hash board MCU firmware.

I was testing just one hash board but I was able to get 68-72Mh/s on Prohash and mid 60s on nicehash. The problem with nicehash is all the pool changes and stratum disconnects causes the hash board to loose it and some times they don't come back.

I have not heard out of Inno in over a week so I don't know any of their thoughts on the process, I finally got the jig two months later than expected but it was broke but I had already figured out how to flash the new firmware from one board to the another anyway so not as big of a deal.

Anyway just asking does anyone have and odd behaviors I need to look at, I know most of them but I will try to answer what I can and any feature requests, might as well try all of the above Smiley

While they let me have access to the cgminer code I am pretty sure it is not what is on 2.0.2 beta, there is no shutdown routine in there and they tried to fix a slow down issue that I don't see a fix for but that is not a problem already worked around it.

I have been using a proxy but that is mostly for switching pools which seems to break them easily and getting a graph on hash rate.

Thanks
Jarrid




Thanks for your work on this, do you have a solution to stop the A4 from rebooting itself any time it sees a get failure?

This issue is really my only issue with it.


Actually the code they shared with me didn't have the shutdown routine in it which shocked me , for some reason had a sleep(9) in the main function, i think they tried the reboot plan is this, when it gets a pool disconnect the boards gets reset during that time the program cant communicate and just goes into almost always a situation it can't recover from so they do a reboot. The hash boards must have some kind of watchdog type thing that after it gets communicated with and stops it resets it's self and by that time the pi should be back up not an efficient plan. I have solved that but it has two outcomes at this point , another flashing for the boards or hardware mods and board flashing which are not super hard but does require soldering.

Since I have made the mods I have been mining Nicehash for 3 days now with no user intervention required, I had been trying to handle different errors differently but now I am thinking any error just reset the board after a little firmware mod instead of taking the board 2~3 seconds to get started it now takes like 0.1 seconds. I dont have access to the MCU firmware code so I dont know if a software update fix only is possible and I may have went overkill but something causes the board to stop talking and from the logic analyzer point of view it *looks* like the hash board is the issue. I dont know if a command is locking the board up I need to look into that a bit more.

My 1 day average on nicehash for 10 hash boards is 642 MH/s so that would make 128.4 MH/s for a 136 unit and 256.8 for a 270. on prohashing it was a bit better , the diff I think gets way to high on nicehash to quickly ,I am seeing 65K on mine I think that is to high and setting it doesn't make any difference.





So in summary you are saying that this reboot issue isn't going to be fixed by a new version of the SD Card software and clearly Inno knows about this issue because they coded the boards this way, is that correct?

I've done everything short of creating a youtube video demonstrating the problem and so far the only response I get from Inno is denial of the problem or to completely ignore it and blame something else.

Thanks again for your work and efforts on this, I hope you can bring something to the table that fixes or improves the operation of these A4's for all of us.
member
Activity: 97
Merit: 10
Actually the code they shared with me didn't have the shutdown routine in it which shocked me , for some reason had a sleep(9) in the main function, i
My 1 day average on nicehash for 10 hash boards is 642 MH/s so that would make 128.4 MH/s for a 136 unit and 256.8 for a 270. on prohashing it was a bit better , the diff I think gets way to high on nicehash to quickly ,I am seeing 65K on mine I think that is to high and setting it doesn't make any difference.

So do you have any idea when we can expect a new software release from Inno with these fixes in it?
Any improvements would be great.
full member
Activity: 188
Merit: 100
I have been running with a local proxy as well  mostly so I can get a good hash rate graph. I have been working with Inno to improve the driver along with others. So far I have made some progress with both prohashing and nicehash, although the fixes for nicehash require hardware mods at least with what information I have on the hash board MCU firmware.

I was testing just one hash board but I was able to get 68-72Mh/s on Prohash and mid 60s on nicehash. The problem with nicehash is all the pool changes and stratum disconnects causes the hash board to loose it and some times they don't come back.

I have not heard out of Inno in over a week so I don't know any of their thoughts on the process, I finally got the jig two months later than expected but it was broke but I had already figured out how to flash the new firmware from one board to the another anyway so not as big of a deal.

Anyway just asking does anyone have and odd behaviors I need to look at, I know most of them but I will try to answer what I can and any feature requests, might as well try all of the above Smiley

While they let me have access to the cgminer code I am pretty sure it is not what is on 2.0.2 beta, there is no shutdown routine in there and they tried to fix a slow down issue that I don't see a fix for but that is not a problem already worked around it.

I have been using a proxy but that is mostly for switching pools which seems to break them easily and getting a graph on hash rate.

Thanks
Jarrid




Thanks for your work on this, do you have a solution to stop the A4 from rebooting itself any time it sees a get failure?

This issue is really my only issue with it.


Actually the code they shared with me didn't have the shutdown routine in it which shocked me , for some reason had a sleep(9) in the main function, i think they tried the reboot plan is this, when it gets a pool disconnect the boards gets reset during that time the program cant communicate and just goes into almost always a situation it can't recover from so they do a reboot. The hash boards must have some kind of watchdog type thing that after it gets communicated with and stops it resets it's self and by that time the pi should be back up not an efficient plan. I have solved that but it has two outcomes at this point , another flashing for the boards or hardware mods and board flashing which are not super hard but does require soldering.

Since I have made the mods I have been mining Nicehash for 3 days now with no user intervention required, I had been trying to handle different errors differently but now I am thinking any error just reset the board after a little firmware mod instead of taking the board 2~3 seconds to get started it now takes like 0.1 seconds. I dont have access to the MCU firmware code so I dont know if a software update fix only is possible and I may have went overkill but something causes the board to stop talking and from the logic analyzer point of view it *looks* like the hash board is the issue. I dont know if a command is locking the board up I need to look into that a bit more.

My 1 day average on nicehash for 10 hash boards is 642 MH/s so that would make 128.4 MH/s for a 136 unit and 256.8 for a 270. on prohashing it was a bit better , the diff I think gets way to high on nicehash to quickly ,I am seeing 65K on mine I think that is to high and setting it doesn't make any difference.


legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
Hello, I am having trouble with my a4 dominator. Everything looks right but when i try to run it. The real time monitoring page takes me Socket error page. I have spent days and reached out but no one can seem to address the issue. Please help. PM me if you know anything. thanks

Which batch is your miner?  What version of the mining software do you have? 

Socket errors usually is due to incorrect settings, ie. starting diff too high, password settings contains invalid chars etc.
hero member
Activity: 868
Merit: 517
Hello, I am having trouble with my a4 dominator. Everything looks right but when i try to run it. The real time monitoring page takes me Socket error page. I have spent days and reached out but no one can seem to address the issue. Please help. PM me if you know anything. thanks

Which batch is your miner?  What version of the mining software do you have? 
hero member
Activity: 952
Merit: 508
I have been running with a local proxy as well  mostly so I can get a good hash rate graph. I have been working with Inno to improve the driver along with others. So far I have made some progress with both prohashing and nicehash, although the fixes for nicehash require hardware mods at least with what information I have on the hash board MCU firmware.

I was testing just one hash board but I was able to get 68-72Mh/s on Prohash and mid 60s on nicehash. The problem with nicehash is all the pool changes and stratum disconnects causes the hash board to loose it and some times they don't come back.

I have not heard out of Inno in over a week so I don't know any of their thoughts on the process, I finally got the jig two months later than expected but it was broke but I had already figured out how to flash the new firmware from one board to the another anyway so not as big of a deal.

Anyway just asking does anyone have and odd behaviors I need to look at, I know most of them but I will try to answer what I can and any feature requests, might as well try all of the above Smiley

While they let me have access to the cgminer code I am pretty sure it is not what is on 2.0.2 beta, there is no shutdown routine in there and they tried to fix a slow down issue that I don't see a fix for but that is not a problem already worked around it.

I have been using a proxy but that is mostly for switching pools which seems to break them easily and getting a graph on hash rate.

Thanks
Jarrid


Thanks for your work on this, do you have a solution to stop the A4 from rebooting itself any time it sees a get failure?

This issue is really my only issue with it.

newbie
Activity: 5
Merit: 0
Hello, I am having trouble with my a4 dominator. Everything looks right but when i try to run it. The real time monitoring page takes me Socket error page. I have spent days and reached out but no one can seem to address the issue. Please help. PM me if you know anything. thanks
full member
Activity: 135
Merit: 100
Business models change. Its the mindset that stays
Where do you buy your A4s?

I need to do some asics shopping, anyone know a good place? I am in EU.
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
If you want to use without a proxy, you can set scan time to 15, I had a small improvement in performance, but it's better to check and tell you if the difference is between 120 and 15 for nicehash.

I forgot to mention the main advantage of the proxy. XnSub On. [img]http://imgur.com/qX3dbD6[img]

Ok will try this tonight.

Got it on the #xnsub. Thanks

For now, I am just learning how to setup a proxy server using NH guide, I will run the A4s without proxy using "-p d=32768 --scan-time=15 --expiry=1" in the password field - that way, i dont have to edit run.sh directly -- that seems to work too.

Anybody can advise me if the scan time 15 is OK for a standard A4 rig (280MH)?
full member
Activity: 188
Merit: 100
I have been running with a local proxy as well  mostly so I can get a good hash rate graph. I have been working with Inno to improve the driver along with others. So far I have made some progress with both prohashing and nicehash, although the fixes for nicehash require hardware mods at least with what information I have on the hash board MCU firmware.

I was testing just one hash board but I was able to get 68-72Mh/s on Prohash and mid 60s on nicehash. The problem with nicehash is all the pool changes and stratum disconnects causes the hash board to loose it and some times they don't come back.

I have not heard out of Inno in over a week so I don't know any of their thoughts on the process, I finally got the jig two months later than expected but it was broke but I had already figured out how to flash the new firmware from one board to the another anyway so not as big of a deal.

Anyway just asking does anyone have and odd behaviors I need to look at, I know most of them but I will try to answer what I can and any feature requests, might as well try all of the above Smiley

While they let me have access to the cgminer code I am pretty sure it is not what is on 2.0.2 beta, there is no shutdown routine in there and they tried to fix a slow down issue that I don't see a fix for but that is not a problem already worked around it.

I have been using a proxy but that is mostly for switching pools which seems to break them easily and getting a graph on hash rate.

Thanks
Jarrid


Pages:
Jump to: