Swedish ASIC miner company kncminer.com

[Biffa]

• as ckolivas says its purportedly due to the web interface, which makes me think its a memory leak in the API calls? ck, maybe you could clarify, would using miner.php have the same issue?

Miner.php wouldn't have this issue. It's allegedly due to using the json commands to the cgminer RPC API instead of the standard API calls as in use by miner.php and elsewhere.

Cool, I hate memory leaks, tricky to track down, especially if theres multiple suspects. All I can say is that 3.4.0 with their firmware 0.96 doesn't seem to suffer from the same problem.

[-ck]

• as ckolivas says its purportedly due to the web interface, which makes me think its a memory leak in the API calls? ck, maybe you could clarify, would using miner.php have the same issue?

Miner.php wouldn't have this issue. It's allegedly due to using the json commands to the cgminer RPC API instead of the standard API calls as in use by miner.php and elsewhere.

Cool, I hate memory leaks, tricky to track down, especially if theres multiple suspects. All I can say is that 3.4.0 with their firmware 0.96 doesn't seem to suffer from the same problem.

That's because that version reported nothing via API for the device since that predates when I wrote code for it, and they never wrote any code for the device specific information.

[djcoin]

From the very beginning I wished they used FedEx. There are much less mistakes with FedEx and if you pay $300 for shipping on anything with FedEx they'll buy lunch for you that day. I want my god damn shipping charges refunded back to me. Pathetic.

Really?? Do you know how close KnC were to being over a week late in being able to create any machines?

FedEx delivered the majority and all of the first batch of Beaglebones to the wrong country and then spent three days lying about the whereabouts in the final week of September. Marcus refuses to use Fedex ever again, for anything ever again. He hates them with a passion for this.

It was only because Beaglebone themselves worked through the day and night for three days solid and paid DHL to deliver expedited that there was any. Even though FedEx were well aware of the problem and Beaglebone found out and restarted manufacture, DHL still beat them.

The Beaglebones arrived Saturday, the chips Sunday, that's how close to line this project was!!

My UPS tracking shows my boards left Sweden, arrived in Germany and there were sent back to Sweden. As others are in the same position we'd appreciate it if you could you provide a clear indication if this is dodgy UPS tracking or if there is another issue?

cheers

[Searing]

enablecores just turns on any cores that were turned off from hardware errors, not sure how useful it is if using latest firmware as cgminer turns the cores on and off itself, but if going back to earlier firmware (pre 0.98) then is a must[/li]

[/quote]

ok ...I thought enablecores turned them all ON all the time....if enablecores just copies cgminer turning them off and on as needed I guess I don't need the enablecores.bin patch

thanks

Searing

[Biffa]

• as ckolivas says its purportedly due to the web interface, which makes me think its a memory leak in the API calls? ck, maybe you could clarify, would using miner.php have the same issue?

Miner.php wouldn't have this issue. It's allegedly due to using the json commands to the cgminer RPC API instead of the standard API calls as in use by miner.php and elsewhere.

Cool, I hate memory leaks, tricky to track down, especially if theres multiple suspects. All I can say is that 3.4.0 with their firmware 0.96 doesn't seem to suffer from the same problem.

That's because that version reported nothing via API for the device since that predates when I wrote code for it, and they never wrote any code for the device specific information.

Ok so I've replaced the 3.4.0 with the latest 3.8.2 and I'll run with that for 24-48 hours and see how it goes, same miner firmware that seems to work well for me, but just replace cgminer.

[Biffa]

    enablecores just turns on any cores that were turned off from hardware errors, not sure how useful it is if using latest firmware as cgminer turns the cores on and off itself, but if going back to earlier firmware (pre 0.98) then is a must[/li][/list]

ok ...I thought enablecores turned them all ON all the time....if enablecores just copies cgminer turning them off and on as needed I guess I don't need the enablecores.bin patch

thanks

Searing
[/quote]

My understanding is that the enablecores just turns them all back on as a one time shot in the arm type of thing, they can still be turned off afterwards through either the later firmwares or via a version of cgminer that supports that facility.

[Biomech]

Guess we shall see Mota...because I'm on an aggressive re-investment strategy....

I have exactly one problem with your strategy. Pure jealousy. I missed out, due to not being able to raise the money.

I think reinvesting in the mining equipment is a great long term strategy. I also think that if it were me, my first reinvestment would be in off grid power. Probably a combination of solar and hydro, since here in Idaho you can get remote land for very little money that has a stream or more running through it. Water wheels are cheap, and alternators aren't much more expensive. Batteries are the biggest investment, and they have a pretty good life these days. Getting the electric cost to near zero would make even the initial miners valuable for a long time, as they would simply continue to add to your hashpower as you added in more equipment 9both miners and electric generation).

This is the strategy I want to follow, assuming I can turn the financial disaster that is my current life around.

[Searing]

    enablecores just turns on any cores that were turned off from hardware errors, not sure how useful it is if using latest firmware as cgminer turns the cores on and off itself, but if going back to earlier firmware (pre 0.98) then is a must[/li][/list]

ok ...I thought enablecores turned them all ON all the time....if enablecores just copies cgminer turning them off and on as needed I guess I don't need the enablecores.bin patch

thanks

Searing

My understanding is that the enablecores just turns them all back on as a one time shot in the arm type of thing, they can still be turned off afterwards through either the later firmwares or via a version of cgminer that supports that facility.
[/quote]

so no way to change the number of error before this happens it always says "detected 10 errors shutting off core"  kinda thing

would be nice if you could set it for like 20 errors (or maybe I'm missing something on cgminer

anyway if it just turns them all on for a time not needed for me they just toggle on/off fine on their own whim now and it is only 2 that do so every few hours and another 2 that maybe do it 2 or 3x a day

anway thanks
Searing

[gravito]

I just got off the phone with UPS. The lady told me that the shipment is very (very) unlikely to be delivered today (Germany) and I shall take this up with KNC (which I just did). The sender is the only one able to get UPS to investigate the issue. She said it seems the paperwork got shipped but the actual boxes were left behind.

It's sad that KNC has not already responded to the issue (it's noon in Sweden). Their decision to not sending the upgrades out Friday will result in half a week of lost mining. All I can say to this (from the bottom of my heart) is: Thank you SO much KNC. You really, REALLY rock. This is by far the fairest solution for all miners.

Totally unrelated: Congrats to those who decided not to trust KNC with the delivery and pick the boards up locally. I should have done the same.

[-ck]

• as ckolivas says its purportedly due to the web interface, which makes me think its a memory leak in the API calls? ck, maybe you could clarify, would using miner.php have the same issue?

Miner.php wouldn't have this issue. It's allegedly due to using the json commands to the cgminer RPC API instead of the standard API calls as in use by miner.php and elsewhere.

Cool, I hate memory leaks, tricky to track down, especially if theres multiple suspects. All I can say is that 3.4.0 with their firmware 0.96 doesn't seem to suffer from the same problem.

That's because that version reported nothing via API for the device since that predates when I wrote code for it, and they never wrote any code for the device specific information.

Ok so I've replaced the 3.4.0 with the latest 3.8.2 and I'll run with that for 24-48 hours and see how it goes, same miner firmware that seems to work well for me, but just replace cgminer.

But that will keep using the API which causes the problem if you're using the web interface... that's not a solution unless you move to ssh/putty monitoring.

[Bitcoinorama]

I just got off the phone with UPS. The lady told me that the shipment is very (very) unlikely to be delivered today (Germany) and I shall take this up with KNC (which I just did). The sender is the only one able to get UPS to investigate the issue. She said it seems the paperwork got shipped but the actual boxes were left behind.

It's sad that KNC has not already responded to the issue (it's noon in Sweden). Their decision to not sending the upgrades out Friday will result in half a week of lost mining. All I can say to this (from the bottom of my heart) is: Thank you SO much KNC. You really, REALLY rock. This is by far the fairest solution for all miners.

Totally unrelated: Congrats to those who decided not to trust KNC with the delivery and pick the boards up locally. I should have done the same.

Because this is KnC's fault, how?! ALL boxes were collected by UPS yesterday. They took them all in plastic packaging crates. UPS arrived here at 4pm. The boxes were ready, so no delay from us whatsoever.

[Searing]

I just got off the phone with UPS. The lady told me that the shipment is very (very) unlikely to be delivered today (Germany) and I shall take this up with KNC (which I just did). The sender is the only one able to get UPS to investigate the issue. She said it seems the paperwork got shipped but the actual boxes were left behind.

It's sad that KNC has not already responded to the issue (it's noon in Sweden). Their decision to not sending the upgrades out Friday will result in half a week of lost mining. All I can say to this (from the bottom of my heart) is: Thank you SO much KNC. You really, REALLY rock. This is by far the fairest solution for all miners.

Totally unrelated: Congrats to those who decided not to trust KNC with the delivery and pick the boards up locally. I should have done the same.

Because this is KnC's fault, how?! ALL boxes were collected by UPS yesterday. They took them all in plastic packaging crates. UPS arrived here at 4pm. The boxes were ready, so no delay from us whatsoever.

Because of this it is your fault:

to be fair to everybody that ordered within those 7 minutes, they are all being shipped at the same time on Monday.

You could have shipped them last week (maybe not all...but a significant number). They were advertised that way you know....

prob would not matter whatever the issue with UPS and the boxes would probably have happened then as well...of course may have saved a day in untangling the mess but then again the weekend so probably not  imho just saying (like I really know anything about this  but seems likely)

[ElGabo]

I think it was not Knc's fault.

But 'Orama, could somebody call Ups from Knc and ask what happened? They give info only for Knc....

This is only history but I'd only like to know what happened.

[-ck]

Well, here's a binary which should hopefully address the known memory leak from cgminer itself based on the latest git master 009511c995458c00a5f46426c8e80ddb94c20cbb.

http://ck.kolivas.org/apps/cgminer/kncminer/cgminer

[Bitcoinorama]

I think it was not Knc's fault.

But 'Orama, could somebody call Ups from Knc and ask what happened? They give info only for Knc....

This is only history but I'd only like to know what happened.

I've only been in the office for an hour as I was working all through last night whilst watching the US Senate deliberate over Bitcoin, and watching the BTC price and volume simultaneously. Give me a bit and i'll grab an answer from Emilia, she's chasing now.

[ElGabo]

I think it was not Knc's fault.

But 'Orama, could somebody call Ups from Knc and ask what happened? They give info only for Knc....

This is only history but I'd only like to know what happened.

I've only been in the office for an hour as I was working all through last night whilst watching the US Senate deliberate over Bitcoin, and watching the BTC price and volume simultaneously. Give me a bit and i'll grab an answer from Emilia, she's chasing now.

Thanks a lot!

[Bitcoinorama]

OK UPS had a technical error, hence 'exception', so UPS couldn't ship their packages last night, but nothing to fear they're on their way now according to UPS. The guy that had a package appear in Germany and then back in Sweden, the confusion there is apparently due to the manifest (customs docket) appearing on the German UPS system ahead of physical delivery of the package. So his package (and presumably every heading to Germany) was still in Sweden presumably and is now en route to Germany, if not there already.

EDIT: 'the guy' = DJcoin, sorry bud!

[ElGabo]

OK UPS had a technical error, hence 'exception', so UPS couldn't ship their packages last night, but nothing to fear they're on their way now according to UPS. The guy that had a package appear in Germany and then back in Sweden, the confusion there is apparently due to the manifest (customs docket) appearing on the German UPS system ahead of physical delivery of the package. So his package (and presumably every heading to Germany) was still in Sweden presumably and is now en route to Germany, if not there already.

Great! Thanks!

[Searing]

Well, here's a binary which should hopefully address the known memory leak from cgminer itself based on the latest git master 009511c995458c00a5f46426c8e80ddb94c20cbb.

http://ck.kolivas.org/apps/cgminer/kncminer/cgminer

heh I know nothing about how to install something like this I'll wait for the next release and take it as an update then

but again we appreciate your efforts and also your time on this forum

Searing

[thorvald]

Well, here's a binary which should hopefully address the known memory leak from cgminer itself based on the latest git master 009511c995458c00a5f46426c8e80ddb94c20cbb.

http://ck.kolivas.org/apps/cgminer/kncminer/cgminer

heh I know nothing about how to install something like this I'll wait for the next release and take it as an update then

but again we appreciate your efforts and also your time on this forum

Searing

wget http://ck.kolivas.org/apps/cgminer/kncminer/cgminer
chmod +x cgminer

screen -dm ./cgminer -c /config/cgminer.conf