wareck/cgminer-gekko

cgminer 4.12.1 with GekkoScience (Compac , 2pac , Newpac , R606 /R909 , CompacF) Also with Extranonce/nicehash support. Compatible with OpenWrt

cgminer-gekko's Issues

NONCES with Gekko BM1387 miner

. missing nonces
' Toggling ASIC rNST to reset

I have two sticks right now. Both give the same error. Running from200-350 makes no difference. VCOR issue?

Thanks, stay healthy,

Bernie

mined coins are going to another address

while i was solo mining the miner was showing me the address that i entered but by when checking the mined block in the explorer the mined coin was going to another address as if the miner was converting the address to another one during the mining process

here is my address format: 2VMgQQsLBretQ1oZXXFFA1HiGA7X1Bxnbp

--gekko-compac-freq <freq> is not working

Hi!

Im using this repo's version of cgminer and the argument --gekko-compac-freq <freq> makes no effect. I've tried frequencies 100, 220, 300 - I always got 200Mhz in the terminal log. I wonder, if I use the command improperly, or the argument indeed does not work?

cgminer -o stratum+tcp://solo.ckpool.org:333 -u <wallet_address> -p x --gekko-compac-freq 300

Usb with Win 10 WSL

I get this error when i start cgminer on Win 10 WSL Ubuntu Gekko-NewPack:

andreas@PC-AD2:~/cgminer-gekko$ cgminer
libusb_init() failed err -99 [2020-12-31 09:54:29.631] libusb_init() failed
Segmentation fault

The error after cloning cgminer-gekko leaves me with this...

make[1]: *** [Makefile:893: cgminer] Error 1
make[1]: Leaving directory '/home/pi/mining/newpac/cgminer'
make: *** [Makefile:1837: install-recursive] Error 1

I cannot find a solution and I running RaspberryPi4 with GekkoScience Newpac.
the "make" error is daunting after so many tries following the ./configure --enable-gekko command.

Please try to help me, I would appreciate it.

Problem Last device GekkoScience CompacF Usb miner

Using the relesase 4.12 for windows we have some problem using the new GekkoScience CompacF Usb miner

Starting from frequency of 200 to go 450 Mhz.
The frequency don't rise up but decrease, seems chip not function.

The parameter WU is too low.

How to resolve problem?
What could possibly be causing this?

Thanks

Not an issue but a request

Hi mate, any chance you can add the scrypt algo and support for Futurebit Moonlander 2 ?

Thanks!

Compatibility with Ubuntu

Does this work with ubuntu? I'm running into issues saying Cgminer can not be found.

No device detected for gekko newpac

I got no device detected error with gekko newpac.

Thanks

--gekko-newpac-freq <clock> not working

I have been running the NewPac at a default 150MHz with no problems.

When I try increasing the frequency, cgminer doesn't overclock - it stays at 150. There is a value in that stays at T:150 - is there a fix?

FYI, the --gekko-newpac-boost options arent working either.

Found 0 chips

While using gekko newpac on freq 300. All usb miners have been unplugged, dusted, and plugged back in. Only these two are having issues.

What could possibly be causing this?

Frequency stuck on 106.25 MHz

I've been running cfminer fine for a few months. Using 2x Newpac and a other old mining stick Only have to restart every ones in a while. Also no problem.

Suddenly, with no changes to the cgminer software, the frequency get stuck om 106.25MHz amd the hashpower stays around 15Gh.

I did a '''apt upgrade'''. But no unusuall thing for my not-to-techinical-linux-eyes.

Any clue?

Compacf devices not detected

Been using this version of CGminer for about a month and it worked great until i plugged in a second compacf usb miner and now cgminer can't detect either of them. Pretty sure it's not a power issue. Tried on two separate computers mac and raspberry pi with same result. Just says no usb device detected. Any help would be appreciated

cgminer won't run under Raspberry pi "Bullseye" system.

cgminer work fine under Raspberry pi ARM64 "Buster" OS. But I have an issue with AMR64 "Bullseye" OS. They is 64-Bits I am used on pi 4 with 8 GB RAM and 64 GB SD. Please note: I clean-installed pi OS. No added other. I did do with Buster and no issue.

I did compile two times and get same problems. It seem missed USB devices. I am used GekkoScience NewPac. There is picture:

How to customize

This is not really an issue, more a request for help.

I am relatively new to cgminer and I'd like to customize it to be able to control the range of nonce and timestamp which are passed to the ASIC (I have a compact F device).
Could you please show me how to do it?

Thanks,
Max

Minimum Raspberry Requirements

Hi,

Sorry for opening the topic in this section "issues", i don't know here to open this, but i have 3 questions.

-What's the minimum requirements of the raspberry in terms of model, ram, memory ?

• Can i plug more than one GEKKO at the same device?
• If power/internet shuts down, does the raspberry starts automatically the mining again?

Thank you!

Problem build sorce code for windows environment

Hi
I try to compile source code for windows environment using the guide

https://github.com/wareck/cgminer-gekko/blob/master/windows-build.txt

If I use the first method : Native WIN32 setup and build instructions (on mingw32/Windows)
There are some problem with curl library.

Using this guide

https://bitcointalk.org/index.php?topic=1112039

Same problem. When installing the last curl library i not found this file

MinGW\lib\pkgconfig\libcurl.pc

this file is not present in the release build of curl library.

If I use the second method : Cross-compiling for Windows from Linux (on Ubuntu 20.04 LTS)

When I must install

sudo apt-get install mingw32

mingw32 package is not find and I must install the mingw64.

When I must install curl library the version 33 is not present. I install last version 77.
Then when I execute this command:

CPPFLAGS="-Ipwd/../../cgminer-win32-deps/include" LDFLAGS="-Lpwd/../../cgminer-win32-deps/lib -lcurldll" ../autogen.sh --prefix=/usr/local/i586-mingw32 --host=i586-mingw32msvc --build=i686-linux

The operation failed with the message

/usr/bin/ld : cannot find -lcurldll

I try run this command

CPPFLAGS="-Ipwd/../../cgminer-win32-deps/include" LDFLAGS="-Lpwd/../../cgminer-win32-deps/lib" ../autogen.sh --prefix=/usr/local/i586-mingw32 --host=i586-mingw32msvc --build=i686-linux

This command is ok but then when i try to make I have the problem with other library libjansson:

/usr/bin/ld : unrecognized option '--enable-auto-image-base'

I think the first method is more complicate because the instruction refear to old version of package and O.S.
For compile using second method how library is necessary? Or what is wrong in procedure?

No restart after lost of connection

After a lost of connectivity : Hash do not restart once the internet is back. Need to be restarted manually.

Compiler warnings in driver-gekko.c that aren't obvious how to fix.

I'm trying to get a clean build, so cleaning up warnings, but the right thing isn't so obvious on some of them.

In driver-gekko.c there are two functions that are declared to return void * but in fact don't return any value. The functions are:

static void *compac_mine(void *object)
static void *compac_listen(void *object)

More time in the code may reveal what they are supposed to return or if they're just supposed to be void functions, but at the moment I have no clue. If I'm not mistaken, the default behavior in this case is for them to return 0 (ie, NULL), and that seems like the kind of thing that could very well be a bug.

These are the warnings:

driver-gekko.c:635:1: warning: non-void function does not return a value [-Wreturn-type]
}
^
driver-gekko.c:733:1: warning: non-void function does not return a value [-Wreturn-type]
}

There are also some warnings about calling abs() on unsigned values, which is harmless, unless the values are supposed to be signed. Those are:

driver-gekko.c:300:36: warning: taking the absolute value of unsigned type 'unsigned int' has no effect [-Wabsolute-value]
        if (job_id > info->max_job_id || (abs(info->job_id - job_id) > 3 && abs(info->max_job_id - job_id + info->job_id) > 3)) {
                                          ^
driver-gekko.c:300:36: note: remove the call to 'abs' since unsigned values cannot be negative
        if (job_id > info->max_job_id || (abs(info->job_id - job_id) > 3 && abs(info->max_job_id - job_id + info->job_id) > 3)) {
                                          ^~~
driver-gekko.c:300:70: warning: taking the absolute value of unsigned type 'unsigned int' has no effect [-Wabsolute-value]
        if (job_id > info->max_job_id || (abs(info->job_id - job_id) > 3 && abs(info->max_job_id - job_id + info->job_id) > 3)) {
                                                                            ^
driver-gekko.c:300:70: note: remove the call to 'abs' since unsigned values cannot be negative
        if (job_id > info->max_job_id || (abs(info->job_id - job_id) > 3 && abs(info->max_job_id - job_id + info->job_id) > 3)) {

And then there's this:

driver-gekko.c:137:58: warning: illegal character encoding in string literal [-Winvalid-source-encoding]
                                        applog(LOG_WARNING, "%s %d: micro temp changed to %d<B0>C / %.1f<B0>F", compac->drv->name, compac->device_id, temp, info->mic...
                                                                                            ^~~~        ~~~~
./logging.h:41:35: note: expanded from macro 'applog'
                        snprintf(tmp42, sizeof(tmp42), fmt, ##__VA_ARGS__); \
                                                       ^~~

It might not be so clear, but it's complaining about the occurrences of "<B0>" in the format string. I assume those are supposed to be literally "<B0>", in which case using "%s" and passing them in as parameters rather than embedding them in the format string would silence the warning.

Interestingly this is how the line appears in Xcode, which, because of Swift, assumes source files are UTF-8 encoded while the C standard requires compilers to treat them as ASCII:

applog(LOG_WARNING, "%s %d: micro temp changed to %d∞C / %.1f∞F", compac->drv->name, compac->device_id, temp, info->micro_temp);

Is it supposed to be a degree symbol?

Probable bug in driver-gekko.c

At line 720 in driver-gekko.c there is the this case of a switch statement:

case MINER_OPEN_CORE:
    if ((info->rx[0] == 0x72 && info->rx[1] == 0x03 && info->rx[2] == 0xEA && info->rx[3] == 0x83) ||
        (info->rx[0] == 0xE1 && info->rx[0] == 0x6B && info->rx[0] == 0xF8 && info->rx[0] == 0x09)) {
        //open core nonces = healthy chips.
        info->zero_check++;
    }
    break;

Note the right side of the || expression in the if condition. That expression always evaluates to false, because it's testing that info->rx[0] is simultaneously 0xE1 and 0x6B and 0xF8 and 0x09, which of course is logically impossible. I'm thinking it's a copy-and-paste bug where the pasted versions just weren't completely edited.

Am I right in believing that it should be checking the first 4 bytes like the left-hand expression does?

case MINER_OPEN_CORE:
    if ((info->rx[0] == 0x72 && info->rx[1] == 0x03 && info->rx[2] == 0xEA && info->rx[3] == 0x83) ||
        (info->rx[0] == 0xE1 && info->rx[1] == 0x6B && info->rx[2] == 0xF8 && info->rx[3] == 0x09)) {
        //open core nonces = healthy chips.
        info->zero_check++;
    }
    break;

Autostart boot cgminer

Hi, I want launch cgminer at the start of my pi4(desktop version), how to execute this command at startup please?:

cd cgminer-gekko && ./cgminer -o stratum+tcp://solo6.ckpool.org:3333 -u bc1pxxxxx -p x --gekko-start-freq 350 --gekko-compacF-freq 465

It's possible to boot with autostart LXDE?
I can just add this command line on /etc/xdg/lxsession/LXDE-pi/autostart

@cd cgminer-gekko && ./cgminer -o stratum+tcp://solo6.ckpool.org:3333 -u bc1pxxxxx -p x --gekko-start-freq 350 --gekko-compacF-freq 465

Crash always at syncing

Hi the node is always crashing sometimes after 10min sometimes after 9 hours, but it always crash on syncing and i have no clue why. im a noob on linux for sure so i add here the debug.log maybe someone can look over i would really appreate it.

all brand new 2TB WD Gaming Drive USB 3.0 8gb Raspberyy pi 4 silicon power sd card 1gbit Lan connection to internet Passive cooling case from armor and a 3.5 lcd on top of it
temperatures is between 50-72 C max

https://l.termbin.com/9918p

Gekko NewPack 2 chip Bitmain BM1387 Different Software Version

I try to using the USB Gekko NewPack with 2 chip Bitman BM 1387 and try to work over 200 MHz frequency.

For example I try to work at 600 MHz (obviusly using a specific cooling system).

I start cgminer passing parameter --gekko-newpac-freq 600

If I mining with binary for windows build in 2019 the software start to 200 MHz frequency and try step by step to arrive to 600 MHz. The step frequency is always 6.25.

If I mining with last binary downloaded (last exe from github or building using instruction) the software start immediatly to 600 MHz.

If I try to use the parameter:

• opt_gekko_start_freq < 600 MHz
• opt_gekko_step_freq
• opt_gekko_step_delay

Start always at 600 MHz.

In effect in the file driver-gekko.c we have
case IDENT_GSH:
info->frequency_requested = opt_gekko_gsh_freq;
info->frequency_start = opt_gekko_gsh_freq;
break;

Where opt_gekko_gsh_freq is the gekko-newpac-freq parameter. The parameter opt_gekko_step_freq never use for NewPack device.

Why this change respect old binary version?.

Exist the source code (to rebuild with last fix code) referring to old binary version?
If I check the versions of the file driver-gekko.c don't find a difference about setting the start frequency.