Pages:
Author

Topic: GekkoScience NewPac / Terminus R606 (BM1387) Official Support Thread - page 20. (Read 61918 times)

newbie
Activity: 2
Merit: 0
I set 200 freq on my new pac but he work only at 10gh/s, can help me?

ps: in 100 freq work at 10 gh/s, at 200 freq work at 1 gh/s
member
Activity: 100
Merit: 29
Great! I will create a PR then on vh's repo.
joz
newbie
Activity: 9
Merit: 1
Verified that works!  Yay solo mining with newpacs on bitcoind v0.21!  Thanks 100knot2dae!

Do you want to submit this patch to vh's cgminer?  I can also do so if you'd like.
member
Activity: 100
Merit: 29
Try something like this:

Code:
diff --git a/cgminer.c b/cgminer.c
index ece7ce10..ab52e30a 100644
--- a/cgminer.c
+++ b/cgminer.c
@@ -2960,7 +2960,7 @@ static bool gbt_solo_decode(struct pool *pool, json_t *res_val)
        flags = json_string_value(json_object_get(coinbase_aux, "flags"));
        default_witness_commitment = json_string_value(json_object_get(res_val, "default_witness_commitment"));
 
-       if (!previousblockhash || !target || !version || !curtime || !bits || !coinbase_aux || !flags) {
+       if (!previousblockhash || !target || !version || !curtime || !bits) {
                applog(LOG_ERR, "Pool %d JSON failed to decode GBT", pool->pool_no);
                return false;
        }
@@ -3039,10 +3039,12 @@ static bool gbt_solo_decode(struct pool *pool, json_t *res_val)
        ofs += ser_number(pool->scriptsig_base + ofs, height); // max 5
 
        /* Followed by flags */
-       len = strlen(flags) / 2;
-       pool->scriptsig_base[ofs++] = len;
-       hex2bin(pool->scriptsig_base + ofs, flags, len);
-       ofs += len;
+       if (flags) {
+               len = strlen(flags) / 2;
+               pool->scriptsig_base[ofs++] = len;
+               hex2bin(pool->scriptsig_base + ofs, flags, len);
+               ofs += len;
+       }
 
        /* Followed by timestamp */
        cgtime(&now);

Compiles clean, and should work just fine. Didn't test myself, since not running a node.
joz
newbie
Activity: 9
Merit: 1
Yes, you are right, I can confirm, core did a change in response of gbt.
This afect not only cgminer (vh) also the original and ckpool.
I switched back to 19.1 and wait for core 0.20.01  Tongue

I've also been mining solo with NewPacs for a long time.  Finally went to upgrade my 0.19.1 node to 0.21 and ran into this.  It's still a thing, and core doesn't see it as something to fix on their side (rightfully so, as described in issue 19182).  So, I guess the cgminer fork supporting GS miners needs to be updated.  @vh is this something you can do?  Looks like we just need to not require the coinbaseaux flag in the GBT response.
newbie
Activity: 3
Merit: 0
I had used netcat to confirm port 3333 open.

BUT it turned out to be aiprotection in my ASUS router!  Not blocking ports, nor name.. but was definitely blocking! Thanks for your inputs.
member
Activity: 100
Merit: 29
Check if your router is blocking outbound communication to destination port 3333.

Try a

Code:
telnet solo.ckpool.org 3333

and see if it gets connected.

Other than that, the command itself looks good. So If the telnet works, a line break (as indicated by the \n) might have slipped in by copy and pasting the command.
newbie
Activity: 3
Merit: 0
Debian 10 (buster)
 - compiled cgminer from git source 4.11.1

Yes I installed WinUSB using zadig

Downloaded 4.11.1 from this forum

Code:
cgminer.exe -o stratum+tcp://solo.ckpool.org:3333 -u mYBTCAddress  -p x
legendary
Activity: 3583
Merit: 1094
Think for yourself
So frustrated..
I have a newPac USB and tried in both linux and windows 10.

What version of Linux?

On Windoze did you install the WinUSB driver using the Zadig utility?

What's your full command line?
newbie
Activity: 3
Merit: 0
So frustrated. I have a newPac USB and tried in both linux and windows 10. Seems to be recognized as a valid USB device on both platforms.

Code:
PS E:\btc> gwmi Win32_USBControllerDevice |%{[wmi]($_.Dependent)} | ? { $_.DeviceId -match "GS-" } | sort Manufacturer,Description,DeviceID | ft -groupby Manufacturer Description,Service,DeviceId -auto
   Manufacturer: Future Technology Devices International, Ltd
Description          Service DeviceId
-----------          ------- --------
NewPac Bitcoin Miner WinUSB  USB\VID_0403&PID_6015\GS-10037777

cgminer -n
 [2021-02-26 18:01:33.745] USB all: found 12 devices - listing known devices
.USB dev 0: Bus 3 Device 4 ID: 0403:6015
  Manufacturer: 'GekkoScience'
  Product: 'NewPac Bitcoin Miner'
 [2021-02-26 18:01:33.746] 1 known USB devices

Trying the highly recommended solo.ckpool.org, but also two other mining pools.

ALL I EVER GET IS: No servers were found that could be used to get work from!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Code:
 [2021-02-26 17:38:38.618] Global quota greatest common denominator set to 1
 [2021-02-26 17:38:38.622] Started cgminer 4.11.1
 [2021-02-26 17:38:38.626] Probing for an alive pool
 [2021-02-26 17:38:38.626] RES: thread starting
 [2021-02-26 17:38:38.626] Testing pool stratum+tcp://solo.ckpool.org:3333
 [2021-02-26 17:38:38.668] Succeeded delayed connect
 [2021-02-26 17:38:57.812] Failed to recv sock in recv_line
 [2021-02-26 17:38:57.812] Closing socket for stratum pool 0
 [2021-02-26 17:38:57.812] Failed to parse a \n terminated string in recv_line
 [2021-02-26 17:38:57.881] Succeeded delayed connect
 [2021-02-26 17:39:17.033] Failed to recv sock in recv_line
 [2021-02-26 17:39:17.033] Closing socket for stratum pool 0
 [2021-02-26 17:39:17.033] Failed to parse a \n terminated string in recv_line
 [2021-02-26 17:39:17.033] Initiate stratum failed
 [2021-02-26 17:39:17.033] Closing socket for stratum pool 0
 [2021-02-26 17:39:22.034] Testing pool stratum+tcp://solo.ckpool.org:3333
 [2021-02-26 17:39:22.077] Succeeded delayed connect
 [2021-02-26 17:39:38.659] No servers were found that could be used to get work from.

Clearly the recv sock network is the issue.  Connects but cannot "talk". But I also see some references and pics  mentioning a serial COM port - but I see no mention on either platform, chalking that up to older versions. So I have sort of ruled out a bad newpac board. But that leaves me with exactly zero ideas.

Anyone have any thoughts?  Or any diagnostics for just board-level functions?
legendary
Activity: 3374
Merit: 1859
Curmudgeonly hardware guy
Well I've never tried, but it's entirely possible the driver is auto-installing for both devices. There might be a way to force it to recognize them as distinct but having no MacOS machines or Futurebit hardware to play with, I can't really say anything for sure.

Anyone else messed around with this?
newbie
Activity: 8
Merit: 0
Yep, it's a driver thing. NewPacs require the winUSB driver and sometimes it's not possible to distinguish between the two devices in the OS.

So as long as VCPdriver is on the computer, even if the ML2 is no longer auto-scanning, there is no way to run both together on MacOS?
legendary
Activity: 3374
Merit: 1859
Curmudgeonly hardware guy
Yep, it's a driver thing. NewPacs require the winUSB driver and sometimes it's not possible to distinguish between the two devices in the OS.
newbie
Activity: 8
Merit: 0
@sidehack

I'm on MacOS 10.15 and I know that Moonlanders and NewPacs don't play well together.

I did find an instance on the other support thread of a user that managed to get both working together on Ubuntu by pointing each to their specific USB bus : port.

I now have the ML2's set to their corresponding UART addresses. No longer are they set to 'ALL'.

Still, CGminer doesn't show the NewPacs after booting and entering the command to [L]ist all devices.

Does the VCP driver make this conceptually impossible? Even if I could direct the NewPacs to their correct --usb bus address : port address? And if I could, do you know the Terminal command that would show me that information?

I'm new to this world. Thanks for making such a cool product. And thanks in advance for your help.
newbie
Activity: 24
Merit: 8
Thank you, I'll do that 😊.
legendary
Activity: 3583
Merit: 1094
Think for yourself
But what about "--usb :1 2>%LOGFILE%" do I leave that in??

Without knowing why you put them in there in the first place it's hard to tell you to take it out.

If you have just one device and you want to mine to it then you probably don't need the usb argument to limit it to one device.  If you don't want the log file then take that out.

But it's up to you.

If it were me I would take out all the extra crap and just leave the basic

Code:
cgminer.exe -o stratum+tcp://solo.ckpool.org:3333 --gekko-newpac-freq 200 --suggest-diff 128 -u bc1mybitcoinaddress123456789 -p x
newbie
Activity: 24
Merit: 8
2pac freq is not for the NEWPAC stick.

Sorry meant to say  --gekko-newpac-freq 200

But what about "--usb :1 2>%LOGFILE%" do I leave that in??
hero member
Activity: 2534
Merit: 623
2pac freq is not for the NEWPAC stick.
newbie
Activity: 24
Merit: 8
Thank you for pointing that out,  so I know to include --gekko-2pac-freq 150. but what do I do about this part: --usb :1 2>%LOGFILE%.

Thank you.
legendary
Activity: 3374
Merit: 1859
Curmudgeonly hardware guy
Take a look at the first post of this thread. There's even charts!
Pages:
Jump to: