NotFuzzyWarm
Legendary
Online
Activity: 3738
Merit: 2663
Evil beware: We have waffles!
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 14, 2021, 08:55:43 PM |
|
|
|
|
|
gt_addict
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 15, 2021, 12:46:57 PM |
|
Unbelievable! Some muppet has already got there Ferrari listed on ebay for $700.
|
**SUPPORT SIDEHACK** Miner Development Donations to: 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
Donations/Tips to:- 1GTADDicTXD1uachKKgW24DZDxDGhSMdRa
Join Bitconnect: https://bitconnect.co/?ref=gtaddict
|
|
|
NotFuzzyWarm
Legendary
Online
Activity: 3738
Merit: 2663
Evil beware: We have waffles!
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 15, 2021, 01:00:17 PM |
|
And no doubt some idjit will buy it for around that price. ![Angry](https://bitcointalk.org/Smileys/default/angry.gif)
|
|
|
|
jeyzeus
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 82
Merit: 52
|
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.
|
|
|
|
kano
Legendary
Offline
Activity: 4578
Merit: 1851
Linux since 1997 RedHat 4
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 15, 2021, 07:04:16 PM |
|
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. 0: GSH 10032174: BM1387:02+ 250.00MHz T:250 P:248 (151:75) | 99.2% WU:^95% | 60.52G / 54.03Gh/s WU: 1: GSF 10008346: BM1397:01+ 400.00MHz T:400 P:399 (32:16) | 100% WU:100% | 270.5G / 211.2Gh/s WU: 2: GSI 10040115: BM1387:12+ 750.00MHz T:750 P:750 (8:4) | 98.4% WU:^86% | 1.044T / 881.1Gh/s WU:
In linux you can see the serial number with: lsusb -v
|
|
|
|
slurfius
Jr. Member
Offline
Activity: 107
Merit: 7
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 16, 2021, 12:38:53 PM |
|
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.
|
|
|
|
zsmith
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 142
Merit: 60
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 16, 2021, 06:42:51 PM |
|
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
|
|
|
|
kano
Legendary
Offline
Activity: 4578
Merit: 1851
Linux since 1997 RedHat 4
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 16, 2021, 07:30:53 PM |
|
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.
|
|
|
|
kano
Legendary
Offline
Activity: 4578
Merit: 1851
Linux since 1997 RedHat 4
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 16, 2021, 07:36:39 PM Last edit: October 16, 2021, 09:32:09 PM by kano |
|
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.
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) #!/bin/sh # ulimit -c 2097152 # now="`date +%Y%m%d%H%M%S`" # ./cgminer "$@" 2> ./runlogs/run.$now.$$.log
|
|
|
|
sidehack (OP)
Legendary
Offline
Activity: 3360
Merit: 1859
Curmudgeonly hardware guy
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 16, 2021, 09:56:47 PM |
|
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.
|
|
|
|
slurfius
Jr. Member
Offline
Activity: 107
Merit: 7
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 17, 2021, 12:21:04 AM Last edit: October 17, 2021, 01:04:22 AM by slurfius |
|
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.
|
|
|
|
Sledge0001
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 17, 2021, 02:58:47 AM |
|
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?
|
|
|
|
Powell
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 486
Merit: 262
rm -rf stupidity
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 17, 2021, 03:49:17 AM |
|
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!
|
|
|
|
kano
Legendary
Offline
Activity: 4578
Merit: 1851
Linux since 1997 RedHat 4
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 17, 2021, 08:43:39 AM Last edit: January 14, 2023, 09:13:58 AM by kano Merited by NotFuzzyWarm (2), cygan (1) |
|
BETA release of cgminer for the new R909 and CompacF. The 'beta' comment is that there's quite a few changes, so we'll see how it goes, I've moved this, since it allows me to edit it more easily, and also gives me full HTML markup to make it easier to read. Here: https://kano.is/gekko.phpI'll comment here if there are any major updates. 2022-12-11 R606 performance issues have been resolved. 2022-12-13 Windows binary for v4.12.1 is available now at https://kano.is/cgminer.php2022-12-17 Git updated to add per chip tuning information. Windows binary updated. https://kano.is/gekko.php updated. 2022-12-21 Update to improve performance and tuning. Windows binary updated. https://kano.is/gekko.php updated. 2023-01-14 Update only necessary for the old R808 miner.
|
|
|
|
MacEntyre
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 17, 2021, 12:06:47 PM |
|
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 No sign of them on the bitshopper.de site ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) I'm checking every day and no update yet. If they are due to 419 around now I'm expecting another few days for them to get over to us in the UK/EU. But it would be handy to get our orders in now. I really don't want to miss out now my R606 has died. I emailed them and their reply was "We’re a bit late. I expect them to arrive here still in October. " To which I asked if we could pre-order or did we have to wait till they are in stock.
|
MacEntyre bitshopper.de
|
|
|
Biffa
Legendary
Offline
Activity: 3220
Merit: 1220
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 17, 2021, 01:03:59 PM |
|
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/Newsletter subscribe not working: "Could not connect to the CleverReach API. (Unauthorized: token expired)"
|
|
|
|
gt_addict
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 17, 2021, 05:18:24 PM |
|
Thanks MacEntyre. I’m eagerly awaiting a notification for it. Hopefully I don’t miss out.
|
**SUPPORT SIDEHACK** Miner Development Donations to: 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
Donations/Tips to:- 1GTADDicTXD1uachKKgW24DZDxDGhSMdRa
Join Bitconnect: https://bitconnect.co/?ref=gtaddict
|
|
|
Sledge0001
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 17, 2021, 07:18:05 PM |
|
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. 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?
|
|
|
|
sidehack (OP)
Legendary
Offline
Activity: 3360
Merit: 1859
Curmudgeonly hardware guy
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 17, 2021, 09:16:46 PM |
|
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.
|
|
|
|
Sledge0001
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 17, 2021, 09:42:27 PM |
|
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 ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) 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.
|
|
|
|
|