Topic: GekkoScience has a new stickminer that does 300+GH - page 54. (Read 22553 times)

Thank you!
The gbt parsing will not be to complicated, but the rest is, so I know what work you dealing with.

There are some cosmetical things, wich would be great if you put them in(I did not do a comit on github, because it is nothing what affect mining)

That is for not leaving the K or M at the end of the bestshare, when a '[Z]ero statistic' has been pressed.

I put it in to prevend the cursor moving all around, that was allways anoying me.
I switched the cursor back on on if you press Q for 'quit', so the cursor is visible in the console after exit.

I know, those where simple things, I just want to improve a bit.

So Thank you Kano for keeping cgminer alive!
 

T: - Target
P: - Plateau or Peak, I forget which.

Check the R606 threads.  There's allot of information there on these new values.

So in the latest cgminer I see a T:  and a P: they seem to correlate to the frequency timer but...

Can anyone shed some light on what the T: and P: actually mean?

It would be ideal if someone wrote a guide on how to interpret these readings so that we can mine more efficiently!

Thanks in advance.

There's already another fix on the todo list for cgminer - the fact that failover hasn't worker almost forever
(since someone added stratum - yes that long ago)
I'll look into solo working with 0.21 when I get to doing that - give it a little while

But no, it's far from ideal to use a version of bitcoin prior to 0.21, since when taproot activates next month, you must be running 0.21 or later.

awesome, will update the pdf

again, the gbt format string did change from 0.19.2 up.
That result in a gbt error in cgminer.
This can be fixed by adapting it to the new format and cgminer will work and not come up with a gbt paring error.
All pools mine against the core version, so you got two possible ways to fix that, changing bitcoind (kano did that as well).
For small miners it will be impossible to solo mine without a working cgminer, wich is against the non decentralised idea of bitcoin.
I am pretty sure that kano will come up with a working version, because he does not do "half" of a thing.


 

Which is different than cgminer. Does the stick solo mine to an older version of Core or are you just trying .22? The change Kano did for solo mining are accounting changes in KDB -- both his solo and main pool all use the same front-end he has used for ages.

Thats bullshit, the gbt format just changed, you can still solomine with the 0.18 / 0.19 version.
I pointed that out in the bitcoin core thread long ago.
Ask kano, he knows what to do, he did the changes in his pool.

AFAIK the problem is with Core - not cgminer. Core dropped support for direct mining to it long ago shortly after ASIC's hit the market and sent CPU mining the way of the dinosaurs.

I could order one today (with discount), but that only works by clicking the basket icon on top of the page.
Inside a basket (with the Icon "next step", it was not possible to fullfill the order process).
I payed allready and wait for the miner to arrive, meanwhile  I tested the cgminer version from Kano.
It was not possible to mine to a bitcoind 0.22.0 solo. The gbt format is not changed acourding bitcoind 0.22.0.
So there is a bit work left for kano to do, so we will be able to real solo mine (without any kind of pool).

Yea sorry, saw them listed as "out of stock" then received the newsletter and checked again and they were available so snapped up what I needed   

Thanks for the announcement 
For existing customers, there is a special discount. Use this coupon code: bitxo-compac-f-customers
And let me know if the coupon does not work as expected.

Bitshopper Compac-F sales are live if anyone from the UK/EU wants them.

I've added a very simple page with links to the versions https://kano.is/cgminer.php
However, the zip will always point to the current windows, binary only, gekko release.

--

All new accounts require registration now (for a few of years)

Simply requires an email address, nothing more, to get vastly superior mining data
(and superior reward and payment data vs any other pool)

Certain old address accounts, like sidehack's, still work.

As it says on the home page, registration is required for both the solo and main pool. Address only was stopped several years ago and only folks who set it up that way before the change can still use their legacy address(s).

sure thing, will use this link:

https://kano.is/cgminer.zip

Might be a good idea to publish the hash for that exe file so people can independently verify it.

BTW, do users have to register to receive rewards on KanoPool? Or can they just mine to BTC address without registration?

Please provide a link to the binary I built, not a copy of it.

word!

I put together this pdf guide for beginners...still needs work (part 6 is not accurate yet), but please check it out:

https://bit.ly/FS7-pdf-guide

Will be doing more tests and updating accordingly.
Any feedback is welcome.

Using --gekko-mine2 --gekko-start-freq 300 will do the initial tune up pretty quickly.

I strongly recommend getting the USB testers. I used this one:

https://www.amazon.com/dp/B01HXU1PGC

I was able to tune most of mine to a stable 340+ GH/s at 525 MHz at around 12.5-13W (4.8V x 2.7A). All i did was adjust the voltage screw clockwise a bit to match the volts/amps of the faster running sticks. Looks like I'm getting nearly S19j levels of efficiency at 36-38W per TH out of these which is kinda wild.

I did have some finicky sticks under hashing around 40-70 GH/s. i thought they were defective as well but thanks to sidehack & kano's tips i got them out of that range into the 150 GH/s+ range. They eventually dropped back down but I will test on a separate hub & instance of cgminer and report back. I think I should be able to get them to run right with the correct settings & frequency. I've noticed w/ the newpacs some sticks do like to run a bit lower than others.

One of the sticks was running fine at 400 MHz over 200GH/s for a bit but now gets 0 chips/zombie and seems to be pulling little to no amps. Any tips on adjusting the voltage screw? I didn't want to mess with it too much or over torque it. It was always properly cooled.

Note, these seem to take a bit to ramp up to max speed when compared to the Newpacs. It took like 2-3 hours to work its way up to 340+ GH/s so def don't think there's something wrong with it if it doesn't immediately hit the higher hash rates.