Swedish ASIC miner company kncminer.com

[CYPER]

Just figured I would report my results with the .99 firmware. It's been running stable since yesterday when I upgraded.

My mercury was running .96 prior, ~141GH most of the time.

With .99 it's been averaging ~155GH with dips into the high 140's.

Awesome work KNCMiner, thanks! I wonder if I will see 175 or 200 in the future? Lol

Where do you take these speeds from? Can you post a screenshot please.

Thank you.

[1714174460]

1714174460

[1714174460]

1714174460

[1714174460]

1714174460

[-ck]

Now this is new. cgminer is reporting ~2Mh/s on avg but the 5s is normal and pool speed is normal. This is with 0.99, but everything was fine from yesterday until i had to shut the miner off. It started normal, but after 30 mins i got this 2Mh/s. I don't care so much about cgminer as long as it's hashing, but this is interesting.

The beaglebone does not have a battery backed up clock in it. That means when you first start it, the clock is set to the year 2000. Then it does a time update from an ntp server and knows what the real time is, and cgminer thinks you've been hashing for almost 14 years...

[idee2013]

Just figured I would report my results with the .99 firmware. It's been running stable since yesterday when I upgraded.

My mercury was running .96 prior, ~141GH most of the time.

With .99 it's been averaging ~155GH with dips into the high 140's.

Awesome work KNCMiner, thanks! I wonder if I will see 175 or 200 in the future? Lol

Where do you take these speeds from? Can you post a screenshot please.

Thank you.

would like to see it, too

[The Avenger]

I thought getwork-based solo mining didn't work well or at all anymore, and that you needed a stratum proxy of some kind to achieve reasonable efficiency, especially with a large amount of hashpower.

I solo mined alts for 10 minutes one day as an experiment and kept getting "pool is not providing work fast enough" error.

No idea if the same goes for btc solo mining.

Would be interested if anyone has set up stratum proxy for solo mining and how they did it.

I'm pretty sure you need a stratum pool, not a proxy for solo mining:
https://bitcointalk.org/index.php?topic=162788.0

Damn that's a complex post  

You could be right about needing a stratum pool, or how else will you be able to set the difficulty? It's not something you can set in cgminer, so it has to be somewhere further down the food chain  

Again, just use BFGMiner and your problems will be solved.  It uses GBT for solo mining, so you don't need stratum.

How do you tell it what difficulty to use?

In solo mining, the difficulty is the network difficulty.  The only accepted share you will see is when you solve a block.

Cool, thanks for explaining that.

[h438dlk34]

I thought getwork-based solo mining didn't work well or at all anymore, and that you needed a stratum proxy of some kind to achieve reasonable efficiency, especially with a large amount of hashpower.

I solo mined alts for 10 minutes one day as an experiment and kept getting "pool is not providing work fast enough" error.

No idea if the same goes for btc solo mining.

Would be interested if anyone has set up stratum proxy for solo mining and how they did it.

I'm pretty sure you need a stratum pool, not a proxy for solo mining:
https://bitcointalk.org/index.php?topic=162788.0

Damn that's a complex post  

You could be right about needing a stratum pool, or how else will you be able to set the difficulty? It's not something you can set in cgminer, so it has to be somewhere further down the food chain  

Again, just use BFGMiner and your problems will be solved.  It uses GBT for solo mining, so you don't need stratum.

How do you tell it what difficulty to use?

In solo mining, the difficulty is the network difficulty.  The only accepted share you will see is when you solve a block.

Cool, thanks for explaining that.

There's a few settings under the stratum pool config file:
Vardiff = True/False #enable vardiff
Target difficulty = 16 #min share difficulty, int >=1
Share target = 2 #try to get a share every 2 seconds
Etc

These aren't the exact names for the settings, but they're close. I can check my config file for the exact settings if you really want to know.

[RoadStress]

Now this is new. cgminer is reporting ~2Mh/s on avg but the 5s is normal and pool speed is normal. This is with 0.99, but everything was fine from yesterday until i had to shut the miner off. It started normal, but after 30 mins i got this 2Mh/s. I don't care so much about cgminer as long as it's hashing, but this is interesting.

The beaglebone does not have a battery backed up clock in it. That means when you first start it, the clock is set to the year 2000. Then it does a time update from an ntp server and knows what the real time is, and cgminer thinks you've been hashing for almost 14 years...

Heh interesting. I'm seeing now that the date is 2000 in cgminer. Any idea when it's updating? Or should i just reboot it?

Edit: Restarted cgminer and it's updated now!

[soy]

Just figured I would report my results with the .99 firmware. It's been running stable since yesterday when I upgraded.

My mercury was running .96 prior, ~141GH most of the time.

With .99 it's been averaging ~155GH with dips into the high 140's.

Awesome work KNCMiner, thanks! I wonder if I will see 175 or 200 in the future? Lol

Where do you take these speeds from? Can you post a screenshot please.

Thank you.

May I ask your WU's?

[soy]

Now this is new. cgminer is reporting ~2Mh/s on avg but the 5s is normal and pool speed is normal. This is with 0.99, but everything was fine from yesterday until i had to shut the miner off. It started normal, but after 30 mins i got this 2Mh/s. I don't care so much about cgminer as long as it's hashing, but this is interesting.

The beaglebone does not have a battery backed up clock in it. That means when you first start it, the clock is set to the year 2000. Then it does a time update from an ntp server and knows what the real time is, and cgminer thinks you've been hashing for almost 14 years...

And no tzconfig.  Time zone setting seems non-existent but I don't know much about Angstrom Linux.

[Phoenix1969]

one of my machines went bzerk on 0.99 with disabling cores & errors....rebooted & ok so far...

[CYPER]

one of my machines went bzerk on 0.99 with disabling cores & errors....rebooted & ok so far...

What is the average speed reported by each in CGMiner/web interface?

[The Avenger]

15? The range seems to indicate a max val of 10, no?

  you're totally right.

just looked up what the mentioned value was and then I though let's add the line from the documentation
should have read my own post before sending it  

So I tried messing with the queue setting in cgminer. Set my miner to solo mine btc.

What happens is all the other backup pools kick in and get some of the work. I get quite a few "pool is not providing work fast enough" errors.

I tried difficulty of 10, 15, 40, 75, 90. Higher numbers seemed to get less "fast enough" errors, but it's seems to farm out more work to failover pools.

Probably would need to run everything a lot longer to see how the values settle over time, but don't want to waste good hashing time experimenting
But the fact it was balancing the work with all the backup pools means it isn't strictly solo mining and it doesn't seem to be able to keep up.

[Phoenix1969]

3 boards normally 420+, was the 3  board norm... this was around 280's, with almost nothing but errors & disablecores showing on cgminer...quick-scroll style...so most likely one asic board...

[xyzzy099]

15? The range seems to indicate a max val of 10, no?

  you're totally right.

just looked up what the mentioned value was and then I though let's add the line from the documentation
should have read my own post before sending it  

So I tried messing with the queue setting in cgminer. Set my miner to solo mine btc.

What happens is all the other backup pools kick in and get some of the work. I get quite a few "pool is not providing work fast enough" errors.

I tried difficulty of 10, 15, 40, 75, 90. Higher numbers seemed to get less "fast enough" errors, but it's seems to farm out more work to failover pools.

Probably would need to run everything a lot longer to see how the values settle over time, but don't want to waste good hashing time experimenting
But the fact it was balancing the work with all the backup pools means it isn't strictly solo mining and it doesn't seem to be able to keep up.

No matter how big you make your queue, it will always overrun it eventually if you are using getwork with an ASIC miner.  Getwork is simply not fast enough to keep up, and that is one of the main reasons why stratum was invented.  If you are mining with ASICs, you have to use either GBT or stratum.

If you want to use stratum, you will have to set up a stratum pool with yourself as the only miner, which is a major pain.  BFGMiner is the only simple solution I know of, since it explicitly solves the problem by using GBT directly to bitcoind/bitcoin-qt.  Read the 'Solo Mining' section in the BFGMiner readme to learn more.

[Bogart]

I thought getwork-based solo mining didn't work well or at all anymore, and that you needed a stratum proxy of some kind to achieve reasonable efficiency, especially with a large amount of hashpower.

I solo mined alts for 10 minutes one day as an experiment and kept getting "pool is not providing work fast enough" error.

No idea if the same goes for btc solo mining.

Would be interested if anyone has set up stratum proxy for solo mining and how they did it.

I'm pretty sure you need a stratum pool, not a proxy for solo mining:
https://bitcointalk.org/index.php?topic=162788.0

When I was solo mining TRC with an avalon I set up eloipool to sit in the middle.  I followed jgarzik's guide: https://bitcointalk.org/index.php?topic=158105.0

To mine on a network other than Bitcoin mainnet I had to change some "magic numbers" in the eloipool config: https://bitcointalk.org/index.php?topic=162765.msg1711931#msg1711931

I tried to use the same setup for solo-mining PPC, but it didn't work for some reason.  I guess something is a little too different about it.

[CeeCee]

New cgminer binary based on cgminer 3.8.2 up

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

Note that we may have tracked down at least one of the causes of the memory leak that leads to cgminer being killed for being out of memory and it involves frequently using the API. This means that if you are not actively monitoring its performance on the web interface, you are better off closing the web interface window for it to not repeatedly keep using it.

how can we put the cgminer into the system?

thx a lot

wget http://ck.kolivas.org/apps/cgminer/kncminer/cgminer
chmod +x cgminer
mv cgminer /usr/bin/
/etc/init.d/cgminer.sh restart
screen -rx

[Bogart]

New cgminer binary based on cgminer 3.8.2 up

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

ckolivas, can you outline the procedure for building a new cgminer binary for a KnC BBB from the source?

Last night I tried building one on my regular BBB running Angstrom.  It ran fine on the build host, but would not run on the KnC BBB, saying "file not found".  I think some of the libraries may be different.  Maybe I need to statically link them?

[sickpig]

New cgminer binary based on cgminer 3.8.2 up

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

Note that we may have tracked down at least one of the causes of the memory leak that leads to cgminer being killed for being out of memory and it involves frequently using the API. This means that if you are not actively monitoring its performance on the web interface, you are better off closing the web interface window for it to not repeatedly keep using it.

how can we put the cgminer into the system?

thx a lot

wget http://ck.kolivas.org/apps/cgminer/kncminer/cgminer
chmod +x cgminer
mv cgminer /usr/bin/
/etc/init.d/cgminer.sh restart
screen -rx

make a backup copy of the original cgminer, just in case

[Phoenix1969]

New cgminer binary based on cgminer 3.8.2 up

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

ckolivas, can you outline the procedure for building a new cgminer binary for a KnC BBB from the source?

Last night I tried building one on my regular BBB running Angstrom.  It ran fine on the build host, but would not run on the KnC BBB, saying "file not found".  I think some of the libraries may be different.  Maybe I need to statically link them?

Here...

I've just created a kncminer branch on my github and have imported their most current code and built my first binary for this. It is not a full firmware and the only thing users may note is the hashrate won't lie with this one, as it won't count hardware errors as hashrate. Also my hardware error count is significantly lower with this on the Saturn dev machine I was sent.

Here's a direct link to the binary:
http://ck.kolivas.org/apps/cgminer/kncminer/cgminer

You'll have to ssh into the kncminer and copy and use that file directly. Hopefully the libraries all match between my dev environment and the default kncminer operating system which means the binary should just work if you run it like on any other OS.

I'm still learning linux, but would love to try this... 
I'll let someone post a clear procedure before I try... ug.Thank you cklovas!

I second this.

ssh into your kncminer if you know its IP address is 192.168.1.X:

Code:

ssh -l root 192.168.1.X
screen -d -r
q
wget http://ck.kolivas.org/apps/cgminer/kncminer/cgminer
chmod +x cgminer
./cgminer -c /config/cgminer.conf

q is to quit the already running cgminer

[vesperwillow]

For those asking:

Here's a screenshot from a little bit ago, the chip is running at 56.5*C



I've seen it spike a few times into the low 200 range, after a few spikes over 200 it kills my putty session, but it's still mining and I can re-ssh into it without issue.

The high and averages have gone up 10GH for me with .99 firmware.

[Bogart]

@Phoenix1969: Thanks, but I'm asking about building a new binary from the source, not installing a built binary onto the miner.