After Unplug reset, the device is back to normal at 150MHz but again stops within 20-30 minutes of work showing it's active but disabled..
How do I adjust the pot meter?
Topic: GekkoScience 2Pac/Compac BM1384 Stickminer Official Support Thread - page 36. (Read 177410 times)
February 12, 2018, 07:15:58 AM
February 11, 2018, 11:15:33 AM
I did unplug and power cycled the machine, still the same.
Which jack is overloaded, the Stickminer's or the Mac Pro itself?
Which jack is overloaded, the Stickminer's or the Mac Pro itself?
February 11, 2018, 11:08:05 AM
After "brew reinstall cgminer" the Stick is showing with "OFF" (as in OFF = Needs some physical attention. Previously reported ZOMBIE state.)
What's meant by physical attention?
What's meant by physical attention?
It means software (restarting) can't resolve the issue.
At a minimum, you'll need to unplug and plug the miner back in to reset it to initial hardware state.
February 11, 2018, 10:50:06 AM
Stop running it at 150MHz then. You've probably overloaded the jack.
February 11, 2018, 10:48:37 AM
After "brew reinstall cgminer" the Stick is showing with "OFF" (as in OFF = Needs some physical attention. Previously reported ZOMBIE state.)
What's meant by physical attention? Is it voltage up?
Note that it's directly plugged into Mac Pro which able to give up to 1.1 Amps.
Your help is much appreciated.
What's meant by physical attention? Is it voltage up?
Note that it's directly plugged into Mac Pro which able to give up to 1.1 Amps.
Your help is much appreciated.
February 11, 2018, 10:34:21 AM
Double check the first post for links to troubleshooting including voltage adjustment photos and notes...
A couple of initial things to try:
1) as mentioned above, bump up voltage
2) if you use brew to install, do a "brew reinstall cgminer", to grab the latest code.
instructions are on the first post to install with brew.
More in depth checking, before concluding the chip is dead:
1) check if you can get the miner to run on a different machine.
2) give the miner more power using a powered hub.
A couple of initial things to try:
1) as mentioned above, bump up voltage
2) if you use brew to install, do a "brew reinstall cgminer", to grab the latest code.
instructions are on the first post to install with brew.
More in depth checking, before concluding the chip is dead:
1) check if you can get the miner to run on a different machine.
2) give the miner more power using a powered hub.
February 11, 2018, 10:27:58 AM
Turn up the voltage through the screw on the side?
And where do I request a warranty repair?
And where do I request a warranty repair?
February 11, 2018, 10:20:21 AM
Okay so we know the USB jack (wherever it is) is at least getting some power. Either the string is locking up (in which case you should turn up the voltage) or one of your chips is damaged (in which case you should consider warranty repair).
February 11, 2018, 10:01:44 AM
Thanks for the reply, it's listed but as inactive, it was running at 150 Mhz with cooling fan on it.. as shown in the screenshot
https://imgur.com/a/8aeO0
https://imgur.com/a/8aeO0
February 11, 2018, 09:05:48 AM
Depends on how "absolutely" you mean. That would imply it's not picked up on the USB bus at all, rather than "cgminer sees it but won't mine" which is actually the lowest level of "not detected". So how "not detected" is it? Because "absolutely" isn't very diagnostically useful.
Then you've got questions like "are you using a hub or plugged into the PC directly", followed by "does the hub still work" or "did your hub come unplugged" or "does the USB jack on your computer still work" or "were you overclocking it" and "did you have cooling".
Long story short - I prefer to help people who do their own homework. So my advice is, give us more information.
Then you've got questions like "are you using a hub or plugged into the PC directly", followed by "does the hub still work" or "did your hub come unplugged" or "does the USB jack on your computer still work" or "were you overclocking it" and "did you have cooling".
Long story short - I prefer to help people who do their own homework. So my advice is, give us more information.
February 11, 2018, 08:48:33 AM
I got the 2pac running on Mac Pro, usually, when it goes ZOMBIE I replug it and it's fine, but now it's absolutely not detected, any advice?
February 11, 2018, 12:46:57 AM
My potentiometer is a little glitchy and jumps straight from 1.26V to 1.64V.....nothing in between. I did manage to get 1.29 once. I haven't sprayed air to it to attempt to clean. What about contact cleaner (no power to it of course). I'm guessing 1.64V will be harmful to the stick? The 2 charts I saw both stopped at 1.5V.
I've had this for 2 days and having fun. Had an issue with a usb extension cable but figured that out. Running 1 at 200Mhz solid at 1.29V with 3 HW errors in the past 20 minutes. If I can't get the pot deal worked out I'll back it down a bit.
I've had this for 2 days and having fun. Had an issue with a usb extension cable but figured that out. Running 1 at 200Mhz solid at 1.29V with 3 HW errors in the past 20 minutes. If I can't get the pot deal worked out I'll back it down a bit.
February 10, 2018, 07:18:22 PM
Ticket mask is only 4 bytes whereas hash is 32 byte,
So does that means this device only masking last 4 bytes and will return any nonce that results in last 4 bytes with 0's ?
So does that means this device only masking last 4 bytes and will return any nonce that results in last 4 bytes with 0's ?
That is a really good question. Sadly I don't have your answer.
The datasheet has little/no info on it that can lead to any concrete answers.
February 10, 2018, 06:01:58 PM
vh, I was wondering if these 2pac checks against difficulty ? Datasheet says 4 bytes from byte position 36 to 39 set as ticket mask for difficulty.
But gekko driver code seems only setting ticket_mask at 39th byte position. What extactly is this ticket_mask?
I tried setting Network difficulty as below and seemed it work but later found its not always returning true nonce for every sample worked example I was using.
I think these chips keep iterating from 0 to max nonce and return every nonce which result in hash with first 4 bytes with 0. Is that true ?
...
Appreciate if you could help me here. Thanks !!!
For a valid ticket mask, think of network mask and CIDR notation.
When visualizing a CIDR in bit form, a mask with 0's scattered between 1's is not valid.
Starting at 4GHs, every time the hash rate double(s) its worth tacking a bit onto the mask.
If the 2Pac ever push past 1TH(s), then I'll add a todo to check if the other bytes do what they are suppose to.
--
The chip iterates 2^32 nonces instead of 0 to max nonce.
To experiment with SNO you probably need to pair it with HCN.
Thanks, appreciate for your explanation. for 100mhz, ticket mask is set as 31 (0x1f)
So..
Ticket mask tells number of bits to use for validating all 0's ?
Or
Ticket mask is only 4 bytes whereas hash is 32 byte,
So does that means this device only masking last 4 bytes and will return any nonce that results in last 4 bytes with 0's ?
Or
I'm no expert when it comes to binary operations, but if we ignore the fact of hashrate this device produce and above statement is not true, my understanding below is correct ?
take example of this current target
0000000000000000-0000000000000000-00000000f8e96100-0000000000000000
and its binary conversion of last 16 bytes:
0000000000000000000000000000000011111000111010010110000100000000-0000000000000000000000000000000000000000000000000000000000000000
If I have to create mask to satisfy current target, it should be like this ?
0000000000000000000000000000000000000000000000000000000111111111-1111111111111111111111111111111111111111111111111111111111111111
How to represent this in 4 bytes of ticket mask ? or each byte represent each 8 byte chunk if hash ?
February 10, 2018, 09:57:01 AM
Yes.
On startup it will report it as a Terminus:
[2018-02-10 14:48:01.563] Loaded configuration file /home/pi/.cgminer/cgminer.conf
[2018-02-10 14:48:01.805] GSD 0: 2Pac BM1384 Bitcoin Miner (10000961)
[2018-02-10 14:48:01.879] GSD 1: 2Pac BM1384 Bitcoin Miner (10011754)
[2018-02-10 14:48:01.959] GSE 0: Terminus BM1384 Bitcoin Miner (10010025)
[2018-02-10 14:48:02.033] GSC 0: Compac BM1384 Bitcoin Miner (10009179)
[2018-02-10 14:48:02.104] GSC 1: Compac BM1384 Bitcoin Miner (10002354)
The top status screen:
2: GSE 10010025: COMPAC-8 225.00MHz HW:0 | 161.2G / 98.64Gh/s WU:1081.5/m
On startup it will report it as a Terminus:
[2018-02-10 14:48:01.563] Loaded configuration file /home/pi/.cgminer/cgminer.conf
[2018-02-10 14:48:01.805] GSD 0: 2Pac BM1384 Bitcoin Miner (10000961)
[2018-02-10 14:48:01.879] GSD 1: 2Pac BM1384 Bitcoin Miner (10011754)
[2018-02-10 14:48:01.959] GSE 0: Terminus BM1384 Bitcoin Miner (10010025)
[2018-02-10 14:48:02.033] GSC 0: Compac BM1384 Bitcoin Miner (10009179)
[2018-02-10 14:48:02.104] GSC 1: Compac BM1384 Bitcoin Miner (10002354)
The top status screen:
2: GSE 10010025: COMPAC-8 225.00MHz HW:0 | 161.2G / 98.64Gh/s WU:1081.5/m
Very excited to see these. Thanks guys!
February 10, 2018, 09:50:23 AM
Yes.
On startup it will report it as a Terminus:
[2018-02-10 14:48:01.563] Loaded configuration file /home/pi/.cgminer/cgminer.conf
[2018-02-10 14:48:01.805] GSD 0: 2Pac BM1384 Bitcoin Miner (10000961)
[2018-02-10 14:48:01.879] GSD 1: 2Pac BM1384 Bitcoin Miner (10011754)
[2018-02-10 14:48:01.959] GSE 0: Terminus BM1384 Bitcoin Miner (10010025)
[2018-02-10 14:48:02.033] GSC 0: Compac BM1384 Bitcoin Miner (10009179)
[2018-02-10 14:48:02.104] GSC 1: Compac BM1384 Bitcoin Miner (10002354)
The top status screen:
2: GSE 10010025: COMPAC-8 225.00MHz HW:0 | 161.2G / 98.64Gh/s WU:1081.5/m
On startup it will report it as a Terminus:
[2018-02-10 14:48:01.563] Loaded configuration file /home/pi/.cgminer/cgminer.conf
[2018-02-10 14:48:01.805] GSD 0: 2Pac BM1384 Bitcoin Miner (10000961)
[2018-02-10 14:48:01.879] GSD 1: 2Pac BM1384 Bitcoin Miner (10011754)
[2018-02-10 14:48:01.959] GSE 0: Terminus BM1384 Bitcoin Miner (10010025)
[2018-02-10 14:48:02.033] GSC 0: Compac BM1384 Bitcoin Miner (10009179)
[2018-02-10 14:48:02.104] GSC 1: Compac BM1384 Bitcoin Miner (10002354)
The top status screen:
2: GSE 10010025: COMPAC-8 225.00MHz HW:0 | 161.2G / 98.64Gh/s WU:1081.5/m
February 10, 2018, 09:45:47 AM
Question. Are Terminus still listed as Compac-8?
February 10, 2018, 09:43:57 AM
New version of code is available.
As before, you don't need to update immediately if you are happy with your current setup.
windows build:
http://23.108.83.14/images/cgminer-4.10.0-windows-gekko-4a3f595.7z
notes:
merged in upstream cgminer
- Fix to configuration saving
- some other stuff
add frequency validation:
- Attempts to match reported frequency with requested frequency.
improved terminus support:
- Terminus R808, yay.
corrected state meaning:
- OFF = Needs some physical attention. Previously reported ZOMBIE state.
- ZOMBIE = USB Miner Unplugged.
installation:
rename folder -> checkout (see first post) -> autogen -> make
or
pull -> autogen -> make
* if you have trouble, move back to different version.
As before, you don't need to update immediately if you are happy with your current setup.
windows build:
http://23.108.83.14/images/cgminer-4.10.0-windows-gekko-4a3f595.7z
notes:
merged in upstream cgminer
- Fix to configuration saving
- some other stuff
add frequency validation:
- Attempts to match reported frequency with requested frequency.
improved terminus support:
- Terminus R808, yay.
corrected state meaning:
- OFF = Needs some physical attention. Previously reported ZOMBIE state.
- ZOMBIE = USB Miner Unplugged.
installation:
rename folder -> checkout (see first post) -> autogen -> make
or
pull -> autogen -> make
* if you have trouble, move back to different version.
February 10, 2018, 09:42:57 AM
vh, I was wondering if these 2pac checks against difficulty ? Datasheet says 4 bytes from byte position 36 to 39 set as ticket mask for difficulty.
But gekko driver code seems only setting ticket_mask at 39th byte position. What extactly is this ticket_mask?
I tried setting Network difficulty as below and seemed it work but later found its not always returning true nonce for every sample worked example I was using.
I think these chips keep iterating from 0 to max nonce and return every nonce which result in hash with first 4 bytes with 0. Is that true ?
...
Appreciate if you could help me here. Thanks !!!
For a valid ticket mask, think of network mask and CIDR notation.
When visualizing a CIDR in bit form, a mask with 0's scattered between 1's is not valid.
Starting at 4GHs, every time the hash rate double(s) its worth tacking a bit onto the mask.
If the 2Pac ever push past 1TH(s), then I'll add a todo to check if the other bytes do what they are suppose to.
--
The chip iterates 2^32 nonces instead of 0 to max nonce.
To experiment with SNO you probably need to pair it with HCN.
February 10, 2018, 08:19:39 AM
Your hub sucks. Read the last 5 pages for at least one other person's this exact problem and solution.
Jump to: