there will not be a 2th gen. The diff rise too quickly and no one pay 5k $ for non ROI miner (a month waiting + month mning + 2-3x diff rise) in 2014 will bfl red flag earn less then 2k $ in feb 
Topic: Swedish ASIC miner company kncminer.com - page 1236. (Read 3049528 times)
there will not be a 2th gen. The diff rise too quickly and no one pay 5k $ for non ROI miner (a month waiting + month mning + 2-3x diff rise) in 2014 will bfl red flag earn less then 2k $ in feb
I've enabled all params CGMiner API Enabled
CGMiner Remote Management Enabled
and restarted
but v0.97 says
Mining Status
CGMiner Status Running (Connect to CGMiner API failed)
Last Checked
Avg. Hash Rate
WU
Difficulty Accepted
HW Status
No data shown ?
CGMiner Remote Management Enabled
and restarted
but v0.97 says
Mining Status
CGMiner Status Running (Connect to CGMiner API failed)
Last Checked
Avg. Hash Rate
WU
Difficulty Accepted
HW Status
No data shown ?
I think everybody has to start somewhere. There are always issues what you can't see in the future.
They made a good product, they hadn't stole our money, they had shipped close to time.
Show me an asic company how made the same.....
Of course they learned a lot and won't make the same issues at gen 2.
That my 2 c.
They made a good product, they hadn't stole our money, they had shipped close to time.
Show me an asic company how made the same.....
Of course they learned a lot and won't make the same issues at gen 2.
That my 2 c.
I assume you have received your miner?
I think everybody has to start somewhere. There are always issues what you can't see in the future.
They made a good product, they hadn't stole our money, they had shipped close to time.
Show me an asic company how made the same.....
Of course they learned a lot and won't make the same issues at gen 2.
That my 2 c.
They made a good product, they hadn't stole our money, they had shipped close to time.
Show me an asic company how made the same.....
Of course they learned a lot and won't make the same issues at gen 2.
That my 2 c.
I see network hashrate that was 3.25PH/s when I looked late yesterday was a moment ago only 2.72 and now is 2.9. I wonder if it's KnC miner users shutting down and restarting with the new firmware.
KNC Pool (https://portal.kncminer.com/) speed already 70 +TH/s (from about 25 TH/s for 24 hrs ). What it mean?
The firmware worked in the datacentre. It was tested on the hosting facility last night, then released today as it was deemed stable.
Hi, Bitcoinorama!
While we have you here and since you mention the hosting facility. Any news from there? Any fires or other disasters preventing new units from being added to it?
Only my and several other people's orders are skipped, while later non-hosted orders are being shipped. You said earlier that the queue was sacred...
The responses I got from support were non-commital, along the lines of "we know there are problems with the data centre, our engineers are working on it." I haven't heard any single existing hosted customer reporting any problems with their equipment that is already running there.
Any specific information would be welcome.
Thank you.
Yes, Bitcoinorama, please enlighten us! Have they run out of power/space or something? What is going on
https://www.kncminer.com/news/news-57
This sounds like: Thank you for being our guinea pigs.
Quote
All,
Ok so after a weekend of producing boards and over 600 boxes shipped in the last few days I have imported the last of the October orders into the production Queue, If the factory have a good day tomorrow they should be able to completely finish the Order queue for all orders that had an October shipment.
We know it’s been a long road with quite a lot of bumps in it but the end is near.
Thanks again for your understanding during this time. We have indeed learnt a lot form this experience and we will be using all of those lessons in our future products
Thanks
KnCMiner team
Ok so after a weekend of producing boards and over 600 boxes shipped in the last few days I have imported the last of the October orders into the production Queue, If the factory have a good day tomorrow they should be able to completely finish the Order queue for all orders that had an October shipment.
We know it’s been a long road with quite a lot of bumps in it but the end is near.
Thanks again for your understanding during this time. We have indeed learnt a lot form this experience and we will be using all of those lessons in our future products
Thanks
KnCMiner team
Quote
We have indeed learnt a lot form this experience and we will be using all of those lessons in our future products.
This sounds like: Thank you for being our guinea pigs.
BTW - with .97 P2Pool works like a charm.
That is great to hear!
BTW - with .97 P2Pool works like a charm.
I want to sell one of my jepiter
i have three of them and they are all running over 555ghs
pm if interested for more info or pic
accept bitcoin payment only (bank transfer to oversea costing too many time which is reducing you profit)
i have three of them and they are all running over 555ghs
pm if interested for more info or pic
accept bitcoin payment only (bank transfer to oversea costing too many time which is reducing you profit)
I see network hashrate that was 3.25PH/s when I looked late yesterday was a moment ago only 2.72 and now is 2.9. I wonder if it's KnC miner users shutting down and restarting with the new firmware.
KNC Pool (https://portal.kncminer.com/) speed already 70 +TH/s (from about 25 TH/s for 24 hrs ). What it mean?
The firmware worked in the datacentre. It was tested on the hosting facility last night, then released today as it was deemed stable.
Hi, Bitcoinorama!
While we have you here and since you mention the hosting facility. Any news from there? Any fires or other disasters preventing new units from being added to it?
Only my and several other people's orders are skipped, while later non-hosted orders are being shipped. You said earlier that the queue was sacred...
The responses I got from support were non-commital, along the lines of "we know there are problems with the data centre, our engineers are working on it." I haven't heard any single existing hosted customer reporting any problems with their equipment that is already running there.
Any specific information would be welcome.
Thank you.
Any1 tried enablecores.bin on .97?
I get:
I get:
Code:
root@Jupiter-E8F:/config# ./enablecores.bin
./enablecores.bin: ./enablecores.bin: line 1: �bǎPi�-uP: not found
��M��^�: Invalid argument
./enablecores.bin: line 1: aR�Z
TSW�: not found
JR��֚�7���3k�������f��}���9���Ϲ�{��0h��CY�ɢ���)��Ǎ�2#{��+�T���,��Re*UJ�2
)32U�وR����j�6����J�M��F�����Қi�i�: not found
./enablecores.bin: line 2: syntax error: unexpected "("
root@Jupiter-E8F:/config#
Don't do that!
You have to follow the nromal fw upgrade procedure using enablecore.bin instead of kncminer-0.9x.bin
Any1 tried enablecores.bin on .97?
I get:
I get:
Code:
root@Jupiter-E8F:/config# ./enablecores.bin
./enablecores.bin: ./enablecores.bin: line 1: �bǎPi�-uP: not found
��M��^�: Invalid argument
./enablecores.bin: line 1: aR�Z
TSW�: not found
JR��֚�7���3k�������f��}���9���Ϲ�{��0h��CY�ɢ���)��Ǎ�2#{��+�T���,��Re*UJ�2
)32U�وR����j�6����J�M��F�����Қi�i�: not found
./enablecores.bin: line 2: syntax error: unexpected "("
root@Jupiter-E8F:/config#
Don't do that!
You have to follow the nromal fw upgrade procedure using enablecore.bin instead of kncminer-0.9x.bin
Any1 tried enablecores.bin on .97?
I get:
I get:
Code:
root@Jupiter-E8F:/config# ./enablecores.bin
./enablecores.bin: ./enablecores.bin: line 1: �bǎPi�-uP: not found
��M��^�: Invalid argument
./enablecores.bin: line 1: aR�Z
TSW�: not found
JR��֚�7���3k�������f��}���9���Ϲ�{��0h��CY�ɢ���)��Ǎ�2#{��+�T���,��Re*UJ�2
)32U�وR����j�6����J�M��F�����Қi�i�: not found
./enablecores.bin: line 2: syntax error: unexpected "("
root@Jupiter-E8F:/config#
The 0.97 firmware doesn't worked for me. The hashrate dropped down from 550 to 540, the HW rate went up to 10%.
Now I'm back to 0.96 with hashrate between 557-560, HW error 4,4%.
What do you guys think?
Now I'm back to 0.96 with hashrate between 557-560, HW error 4,4%.
What do you guys think?
you have to give .96/.97 longer time to see their real hashrate
about 15mins to see if it increases, and about an two hours to see how it stabilizes
I gave more then 2 hours for 0.97. 0.96 was runing before at 500 for long. There is a picture about it a few post ago. After half an hour since I back to 0.96 it's runing 555 rock solid... with 4,5% HW.
The 0.97 firmware doesn't worked for me. The hashrate dropped down from 550 to 540, the HW rate went up to 10%.
Now I'm back to 0.96 with hashrate between 557-560, HW error 4,4%.
What do you guys think?
Now I'm back to 0.96 with hashrate between 557-560, HW error 4,4%.
What do you guys think?
you have to give .96/.97 longer time to see their real hashrate
about 15mins to see if it increases, and about an two hours to see how it stabilizes
The 0.97 firmware doesn't worked for me. The hashrate dropped down from 550 to 540, the HW rate went up to 10%.
Now I'm back to 0.96 with hashrate between 557-560, HW error 4,4%.
What do you guys think?
Now I'm back to 0.96 with hashrate between 557-560, HW error 4,4%.
What do you guys think?
The hardware error rate is killing me, seems that no matter what firmware I use, some firmware lowers the WU but improves the error rate, and others raise the WU but increase the error rate......most of my cores are running and flushwork is better.
Any ideas on why such a high error rate??
I don't really care about the error rate. I only look my hash rate @ the pool.
what kills the hashrate the most seems to be the enabling and disabling of cores (besides flushwork of course)
bfgminer removes that and gives control to the user (aided by asic_test to map the really bad ones off for you)
cgminer .96/.97 is doing better since it maps asic_test to ignore the bad ones and plays with ones that shouldn't be much trouble. It usually takes at least 10-15 mins for these to ramp up and you will see your HW error % go down low if you have good modules
I am tempted to run .93/bfgminer on my good miner to see if can avg 600Gh stable but think that is a bit risky/greedy at this time
was happy with 0.97 until my average just dropped to 1.344 Mh/s
i enabled CGminer API and restarted CGminer - touch wood its picking up again
Mining Status
CGMiner Status Running (pid=14460)
Last Checked Wed Oct 23 16:21:05 UTC 2013
Avg. Hash Rate 520 Gh/s
WU 7908
Difficulty Accepted 145920
HW Status
ASIC slot #1 44.0 ℃
ASIC slot #2 -
ASIC slot #3 51.0 ℃
ASIC slot #4 45.0 ℃
ASIC slot #5 41.0 ℃
ASIC slot #6 -
i enabled CGminer API and restarted CGminer - touch wood its picking up again
Mining Status
CGMiner Status Running (pid=14460)
Last Checked Wed Oct 23 16:21:05 UTC 2013
Avg. Hash Rate 520 Gh/s
WU 7908
Difficulty Accepted 145920
HW Status
ASIC slot #1 44.0 ℃
ASIC slot #2 -
ASIC slot #3 51.0 ℃
ASIC slot #4 45.0 ℃
ASIC slot #5 41.0 ℃
ASIC slot #6 -
I see network hashrate that was 3.25PH/s when I looked late yesterday was a moment ago only 2.72 and now is 2.9. I wonder if it's KnC miner users shutting down and restarting with the new firmware.
KNC Pool (https://portal.kncminer.com/) speed already 70 +TH/s (from about 25 TH/s for 24 hrs ). What it mean?
The firmware worked in the datacentre. It was tested on the hosting facility last night, then released today as it was deemed stable.
Hey Bitcoinorama, any ideas as to why my Saturn has such a high error rate, I don't see others with such?
Jump to: