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

Might also be worth running 2 cgminers?

One with --gekko-compacf-detect

And the other with --gekko-newpac-detect

That way you can tune each cgminer based on the gekkos running on it.

The geeko driver uses the --gekko-start-freq for all gekko's connected,
so you may want different values for compacf vs newpac

I find that the compacf and the r606 run well together on one cgminer,
but adding in my newpacs/2pacs runs better as a separate cgminer.

Also the "--gekko-mine2 --gekko-tune2 60" tune is more exact at handling the changes.
It uses the statistical fact that averaging below 80% with 400 nonces is a 1 in 109901 chance, so shouldn't happen even once, but if it does, a reset will make it try again and the tune2 will keep trying once an hour to get to your target if it fails, then if it gets there it should just stay at your target unless the environment gets too hot.

i.e. try:
one with --gekko-compacf-detect --gekko-r606-detect --gekko-start-freq 350 --gekko-mine2 --gekko-tune2 60 --gekko-compacf-freq 400 --gekko-r606-freq 750
(an r606 should also have it's own USB port direct into the computer)

one with --gekko-newpac-detect --gekko-2pac-detect

Edit: of course if you don't have an r606 or any 2pac, you can remove those settings, but they wont affect the other miners so you can leave them in also

Okay so that in combination with Kano's recommendations (--gekko-mine2 & --gekko-tune2 60 ) gets me at 400 on 4 of 5 of the sticks. The 1 stick that wasn't happy now seems stable at 390MHZ

You're an evil f*cking genius!!!

Ty!!!

Just as a note, all sticks are tested for a minimum of 12 hours at 400MHz and must average at least 220GH (80% speed) during this test to be cleared for shipping.

These sticks don't run well at low speeds. You don't buy a Ferrari to drive Miss Daisy. These chips were made to go FAST and they tend to choke while slow. The higher the clock, if the voltage is stable, the closer they'll run to true. If you want to overclock one but it's stalling in low speeds, you need to --gekko-start-freq to a higher speed, and if it still has trouble stalling, --gekko-tune-up to a lower step threshold.

For instance, I noticed some sticks have trouble below 200MHz and some have trouble below 300. For most, 300MHz is past the breakover point where they start running well. Therefore my test script includes:

--gekko-compacf-freq 400 --gekko-start-freq 300 --gekko-tune-up 85

which means it targets 400MHz, starts ramping from 300MHz (instead of the default 200), and will step up when the measured hashrate breaks 85% of expected (instead of the default ...90-95%?)

So Sledge, it's likely that your sticks are not faulty at all. It's more likely that you need to adjust command line parameters to force it past the sluggy bottom end and into the smoother high revs. If it doesn't level out above 300-400MHz, that's when adjusting the volt screw could start to make a difference.

Well I'm convinced that I may have 2 faulty sticks out of the 7 ordered.

I cross tested to confirm I have working ports, they all have adequate power and fans right on em but they just won't stay running at stock speeds. Tweaking them slightly to the right as sidehack mentioned however 2 of the 7 just won't seem to hold 200MHz. I've spent a few hours trying to get these 2 sorted.... The other 5 of them worked perfectly. 

Also reaching out to 419Mining as well for their advice.

Thanks MacEntyre. I’m eagerly awaiting a notification for it. Hopefully I don’t miss out.

Newsletter subscribe not working:
"Could not connect to the CleverReach API. (Unauthorized: token expired)"

Dears,

I see, I need to give an update here as well regarding the availability of th Compac F for EU customers.

The Compac F is ordered with sidehack. Sidehack noticed me last week that the order is in queue but not yet due. Nevertheless I expect it End of October/ Beginning of November.

As I do not have a dediacted delivery date, I do not offer pre-sales for the Compac F. Generally I am not a friend of pre-sales, I do it only if it is necessary to fund bigger projects.

As soon as I have them in hands I’ll open sales. First come first serve. If you want to get noticed, please subscribe to our newsletter and you’ll get a notification before it goes into sales well in advance. https://www.bitshopper.de/en/newsletter/

An announcement on our website is in preparation as well as a section in our support area.

MacEntyre
bitshopper.de

May as well post this here

Running CGMiner

linux:
./cgminer -o stratum+tcp://stratum.kano.is:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr -p x --suggest-diff 442
 OR (see below for)
./cgminer -c gekko.conf

windows:
cgminer.exe -o stratum+tcp://stratum.kano.is:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr -p x --suggest-diff 442
 OR (see below for)
cgminer.exe -c gekko.conf

OS X:
cgminer -o stratum+tcp://stratum.kano.is:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr -p x --suggest-diff 442
 OR (see below for)
cgminer -c gekko.conf


Of course in all the above replace 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr with your own username.workername on the pool.


CGMiner Frequency setting

Warning running it higher than the default setting will require some cooling.
The higher the frequency you use, the greater the amount of cooling required.
It will also require a USB hub that can put out more than the standard 2.1A to go above 300MHz
Few USB hubs can do this, but of course the Gekko USB hub is designed to do this OK.

To run it at a higher frequency, add on to the commands above e.g.

 --gekko-compacf-freq 400

The latest version of the gekko driver (as of 2021-10-17) has a new mining option:

--gekko-mine2

This uses a slightly different mining loop that also reports all frequency changes to the screen,
and why they change if it stepped down.

There's a second option if you have enabled the mine2 option:

--gekko-tune2 60

that allows the miner to recover lost frequencies if it was unable to match the frequency
requested due to the environment, but it later improves e.g. gets cooler.
The '60' means check once per hour - default is don't do it.
The miner may just end up stepping up and down once per check if it can't do better,
so there's a lower limit of once per 30 minutes, range is 30-9999

--

I've seen tables floating around with incorrect info (way incorrect)
The MHz and GH/s number are pretty accurate.
These are actual numbers from various miners.
Low frequencies tend to perform worse than expected. These are ferraris people - put some power into them
I'll add more rows and columns at a later date.

Approximate performance table

--

CGMiner Git

The master git for cgminer is https://github.com/kanoi/cgminer

CGMiner README https://github.com/kanoi/cgminer/blob/master/README

That includes linux compile steps, but to repeat, on linux:

If you wish to keep a log of each run in linux, add the following on the end of the command:

OR an example shell script to run cgminer, call it cgminer.sh

For those not expert at linux, remember to chmod +x cgminer.sh

The "$@" means you can pass extra parameters to the shell script to be added onto running cgminer
e.g. ./cgminer.sh --gekko-noboost
to turn off asicboost


CGMiner Windows 10 32bit binary

https://kano.is/cgminer.zip
It will probably work on older windows, but I'm only testing it on Windows 10

See here for version information of the above latest release:
https://kano.is/cgminer.php

The instructions to compile it yourself on Windows 10 are here:
https://github.com/kanoi/cgminer/blob/master/windows-build.txt

As with all USB miners on Windows, you must install Zadig and setup the miner.
This is documented in the CGMiner README https://github.com/kanoi/cgminer/blob/master/README

In a windows bat file you can say 2> to save a log of the cgminer run as well as see it on the screen.
Example bat file below using -c gekko.conf described further down,
with a loop to sleep for 5 seconds and then restart (if cgminer exits)
The log files are date stamped, so if you get in a fast loop of start/stop/start/stop... it will create a lot of them 😛
Just removing the last line will stop it from auto-restarting cgminer when it exits

CGMiner MacOS

The instructions to build it on MacOS (tested on Big Sur) are:
https://github.com/kanoi/cgminer/blob/master/mac-build.txt

--

cgminer now has a new run option to verify it can identify shares correctly up to a hash of:
000000000000000000000000000000000000000000000000000000000000ffff

./cgminer --block-check

This is useful to check if you build cgminer yourself on your own choice of hardware,
but do not make any changes to my version.

Difficulty will of course never be that high, and no one is likely to ever find a hash that low.
That's only about 8 decimal places off the number of atoms in the universe

--

An example gekko.conf
Set "username.gekko" to match your username.gekko
and set 192.168.1.0/24 to match your local network

So you run cgminer with just: -c gekko.conf

--

WARNING: avoid https://github.com/wareck/cgminer-gekko

They removed all the git code ownership information, included a major security risk (extranonce),
and have done other various changes to the code, and released a windows binary with who knows what changes in it.

I honestly forget to check this forum anymore sadly.  I remember posting on the idea of a design, and of course I miss the batch LOL!  Hopefully next!

Okay I hate to admit but I am struggling a bit.

2 of the 7 sticks (the first 2 I am trying of the 7)  out of the box wont seem to stay at the stock speed of 200 it keeps reporting:

Peak Adjust --> Target Frequency 200MHz --> 195MHz


I have tried connecting this directly to the mobo as well as through my powered hub and even at stock 200MHz and I keep getting them going back to a reduced speed.

I do have fans directly on both but just not seeing the speed that I should be getting out of 2 sticks.

I tried adding the command --gekko-compacf-freq 300   and 400 as well but that ended up doing the same thing.

What am I doing wrong?

Update: pulled the newpacs and each Ferrari until I got the problem stick by itself it ran at 400 after taking a while to ramp up and now all the Ferrari are happy running at 500 with the newpacs on the hub again all but one of them are unable to reach their target frequencies of 600 and instead running around 500.

The sticks are tested for speed before shipping out, but one test run may not always be indicative of constant performance and environmental variables do change things. If a stick's running slowly, adjust the voltage up a little bit by turning the pot screw in the bottom corner clockwise just a little bit. These sticks are built to overclock; they're built to be tweaked.

I put a little sticker on the top of the USB connector on each Gekko saying the last few digits of the serial number,
so I can match them in cgminer with the actual device.
(like in the picture here in the first post where sidehack wrote 2 digits of the number)

To do that you need to fire each one up individually, and look on the screen to see the serial number each time.
Makes it easy to work out which one is which vs hash rates/messages on the screen.

Also there's a new version I put up yesterday - adds a different mining function if you add the option: --gekko-mine2

Edit: and it tells you each time the frequency changes - a lot of info when it first starts, but settles down to nothing except the changes you probably are looking to see why

Also in linux I run cgminer (in a script) logging to a file as well as seeing it on the screen:

./cgminer ... ... ... 2> "run.`date +%Y%m%d%H%M%S`.log"

Helps looking for info that might have scrolled past on the screen

Or cgminer.sh (after once: mkdir runlogs)

Add -fcommon to CFLAGS

That looks like the gcc10 error where they removed -fcommon on by default

I updated the git before - but only just now updated that line in the support thread.

Are there any instructions for installing cgminer?  I am getting an error.  I've previously installed the VH version for the 606 but tried installing Kano's version using the same instructions but pulling from his git.

https://pastebin.com/8qEpM49k

I have three on a gekko hub with 4 newpacs and one will only go to 250. The other 2 are at 400 the set target frequency. I tried moving the Ferraris around on the hub the problem followed the stick. I will try to figure out which one it is when I get more time so I can try running it alone.

Yes it uses the serial number in the stick
All types of Gekkos are GS-nnn

The X in the GSX cgminer says, tells you what type of miner it is.

e.g.

In linux you can see the serial number with:
lsusb -v

Just as a PSA to anyone out there that has more than one stick and wants to overclock it by serial number, the proper format is still:

--gekko-serial "GS-10019785"

When you run the Compac F's on cgminer, they come up as GSF so I was under the impression that it might have required "GSF-10019785" but if you add the "F" in, cgminer won't find the stick.

And no doubt some idjit will buy it for around that price. 

Unbelievable! Some muppet has already got there Ferrari listed on ebay for $700.