Author

Topic: GekkoScience Compac BM1384 Stickminer Official Support Thread - page 119. (Read 268015 times)

legendary
Activity: 1456
Merit: 1000
you have to try the linux 7 build .

night and day over windows.
Looking forward to it, it's on the to do list.  Going to try Debian on usb and Ubuntu on an old laptop.

You will love it and not go back to windows on one machine.  Always could do RPI like I did aswell.

But it's so much nicer then messing with Windows drivers.   It just works great in linux.
legendary
Activity: 1274
Merit: 1000
Have you tried adding the:     -S compac:all      to the bat?

I've seen that for U3's you add -S antminer:all for bfg to see the U3 sometimes, so wondering if it might have carried over to the compac (Novak stripped icarus down for compac and rebuilt it for cgminer, so did Luke jr do the same??).

EDIT: Just a thought to, is the "compac" maybe supposed to be "Compac"?  Don't know if it would make a difference or not, but?.....

The "-S compac:all" was only necessary for the engineering sticks, the production sticks don't need it.  But yes, I did try just in case, and it made no difference.

I'm fairly certain Compac or compac makes no difference.  The readme has compac, I tried capitalizing it just for giggles and nothing changed.


you have to try the linux 7 build .

night and day over windows.
Looking forward to it, it's on the to do list.  Going to try Debian on usb and Ubuntu on an old laptop.

legendary
Activity: 1456
Merit: 1000
Any peticular flavor of Debian being used?
My sticks arrived promptly.

I think most are using just new stable releases.  I have used regular debian and raspberian (built on debian).    Both work fine for me.

Linux really is much easier then microsoft on these miners.  Only part that was hard for me was RPI and my hub, but that was a RPI problem not compac problem.
hero member
Activity: 924
Merit: 1000
Any peticular flavor of Debian being used?
My sticks arrived promptly.
legendary
Activity: 3500
Merit: 6320
Crypto Swap Exchange
So there's a miss-type in my OP and I do, in fact, have the leading 0 in my batch file.  I tried omitting the leading 0 and still no effect, just to be sure.  It's as if bfgminer is ignorning the --set compac command on this computer.  Could it be related to my comms error I wonder?

Same here, no matter what speed I put in they hash at the same rate.

-Dave
legendary
Activity: 3374
Merit: 1859
Curmudgeonly hardware guy
I was going to ask, is the voltage set high enough? They come from my bench at about 610mV, which according to Bitmain charts they'll run 150MHz at 600mV but you might have gotten a slightly slow chip. Another question is temperature.

Regarding status lights, to be quite frank I don't care much about any sneering. I rarely consider form when designing something (for the most part I don't care what it looks like so long as it works) but the Compac's lights and colors were very specific and deliberate. Someone doesn't like it, all the circuitry is right there and can be modified pretty easily.
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
I only have 3 Compaq stick miners.  I have 1 stick that throws a lot more errors than the other 2. It doesn't matter if I run them direct from the PC in a hub or if I run the one unit solo, it still throws a lot of errors.  I've tried different computers and 2 different hubs and I'm running BFGMIner with:

bfgminer.exe -o stratum+tcp://solo.ckpool.org:3333 -u 1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.bmoscatosticks -p x -S rockminer:all --set rockminer:clock=280 --set compac:clock=x0b83 --api-listen --api-allow W:10.0.0/24



The compac's look pretty good look at the percentage it is not big.   If you compare to the U3 it appears is on with it the U3 is most of your errors.

But .04 percent should not considered "a lot more".  You should be good.

I guess I should've added that the stick in question has actually crashed once after running for 2 days straight.

did you turn pot from +  12 oclock   to 1 oclock   some sticks (I have 20)  want a touch more power.
if the + is at 1 oclock move to 2 oclock
if the + is at 2 oclock move to 3 oclock

the turn is clockwise
sr. member
Activity: 361
Merit: 267
I only have 3 Compaq stick miners.  I have 1 stick that throws a lot more errors than the other 2. It doesn't matter if I run them direct from the PC in a hub or if I run the one unit solo, it still throws a lot of errors.  I've tried different computers and 2 different hubs and I'm running BFGMIner with:

bfgminer.exe -o stratum+tcp://solo.ckpool.org:3333 -u 1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.bmoscatosticks -p x -S rockminer:all --set rockminer:clock=280 --set compac:clock=x0b83 --api-listen --api-allow W:10.0.0/24



The compac's look pretty good look at the percentage it is not big.   If you compare to the U3 it appears is on with it the U3 is most of your errors.

But .04 percent should not considered "a lot more".  You should be good.

I guess I should've added that the stick in question has actually crashed once after running for 2 days straight.
legendary
Activity: 4354
Merit: 3614
what is this "brake pedal" you speak of?
@ sidehack and anyone: status light are highly useful to me as I glance at the setup and I know its working at least somewhat. I dont nend to check my webpage (I have a local web server for the house)

just saying to people to sneer at them
legendary
Activity: 1456
Merit: 1000
I only have 3 Compaq stick miners.  I have 1 stick that throws a lot more errors than the other 2. It doesn't matter if I run them direct from the PC in a hub or if I run the one unit solo, it still throws a lot of errors.  I've tried different computers and 2 different hubs and I'm running BFGMIner with:

bfgminer.exe -o stratum+tcp://solo.ckpool.org:3333 -u 1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.bmoscatosticks -p x -S rockminer:all --set rockminer:clock=280 --set compac:clock=x0b83 --api-listen --api-allow W:10.0.0/24



The compac's look pretty good look at the percentage it is not big.   If you compare to the U3 it appears is on with it the U3 is most of your errors.

But .04 percent should not considered "a lot more".  You should be good.
sr. member
Activity: 361
Merit: 267
I only have 3 Compaq stick miners.  I have 1 stick that throws a lot more errors than the other 2. It doesn't matter if I run them direct from the PC in a hub or if I run the one unit solo, it still throws a lot of errors.  I've tried different computers and 2 different hubs and I'm running BFGMIner with:

bfgminer.exe -o stratum+tcp://solo.ckpool.org:3333 -u 1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.bmoscatosticks -p x -S rockminer:all --set rockminer:clock=280 --set compac:clock=x0b83 --api-listen --api-allow W:10.0.0/24

legendary
Activity: 4354
Merit: 3614
what is this "brake pedal" you speak of?
@ Luke-Jr:   can BFGMiner run as a service under windows? I figure probably but I am in a rush lately, sorry. but I will run cgminer 24/7 as my goto miner not your stuff.. personal decision so dont ask about it but I will try it

@ anyone:   I am really trying to closely watch this thread for nix scripts, (Debian seems popular on OLD notebooks which I have many so no Pi for me) but apologies real life is my priority .. I do intend to run cgminer/BFGMiner under windows and Ubuntu.. well.. soonish

@sidehack and novak:   are your scripts and setup at your shop posted, just tell me if its here in a thread and I will just find it, not waste your time. if not please do

EDIT: Doh! I am in a hurry right now
sr. member
Activity: 331
Merit: 250
New hardware fixed part of my problem.

2) edit - new usb hub and ran 2 sticks on xp laptop just fine, old hub was crap, will update soon >2 sticksplug in a second stick and all goes to hell, LIBSUB_ERROR out the wazoo and both sticks only hash around 2GH.  I didn't try more than 2 sticks.


Any ideas what's going on here?  The errors on the Win7 box are very confusing, I did not expect any issues there.  I'm thinking most of the fail on the XP machine is probably just the fact that my old WinXP box is old so I'm not too concerned there (gotta build a new computer one day...), but I can run 6 nanofury usb sticks on it at the same time no problem.  In fact I can run the 6 nanofury sticks in one instance of cgminer and 1 compac stick in cgminer-gekko at the same time (pictured below), zero issues, so I'm at a loss why more than 1 compac grinds it to a halt.
http://i60.tinypic.com/28vxerk.jpg


you have to try the linux 7 build .

night and day over windows.

Only thing is, if you use an older computer around the pentium cpu time that does not have PAE, you have to use an older version of linux (some where around Ubuntu 10.04 or similar) with a NON PAE kernel (or is it PEA? one of the 2).
sr. member
Activity: 358
Merit: 255
I am no Linux expert but it's the way to go. Debian works great as a controller, have used it on BBB, PI, Odroid, banana PI as well as just about any old PC.
The most usb devices I have had running on one Debian ARM machine was 43 5-chip orbs, 2x hab's, 10x OSM on a odroid-x2 with 3 screen session one each cgminer build instance.

legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
New hardware fixed part of my problem.

2) edit - new usb hub and ran 2 sticks on xp laptop just fine, old hub was crap, will update soon >2 sticksplug in a second stick and all goes to hell, LIBSUB_ERROR out the wazoo and both sticks only hash around 2GH.  I didn't try more than 2 sticks.


Any ideas what's going on here?  The errors on the Win7 box are very confusing, I did not expect any issues there.  I'm thinking most of the fail on the XP machine is probably just the fact that my old WinXP box is old so I'm not too concerned there (gotta build a new computer one day...), but I can run 6 nanofury usb sticks on it at the same time no problem.  In fact I can run the 6 nanofury sticks in one instance of cgminer and 1 compac stick in cgminer-gekko at the same time (pictured below), zero issues, so I'm at a loss why more than 1 compac grinds it to a halt.
http://i60.tinypic.com/28vxerk.jpg


you have to try the linux 7 build .

night and day over windows.
legendary
Activity: 1274
Merit: 1000
New hardware fixed part of my problem.

2) edit - new usb hub and ran 2 sticks on xp laptop just fine, old hub was crap, will update soon >2 sticksplug in a second stick and all goes to hell, LIBSUB_ERROR out the wazoo and both sticks only hash around 2GH.  I didn't try more than 2 sticks.


Any ideas what's going on here?  The errors on the Win7 box are very confusing, I did not expect any issues there.  I'm thinking most of the fail on the XP machine is probably just the fact that my old WinXP box is old so I'm not too concerned there (gotta build a new computer one day...), but I can run 6 nanofury usb sticks on it at the same time no problem.  In fact I can run the 6 nanofury sticks in one instance of cgminer and 1 compac stick in cgminer-gekko at the same time (pictured below), zero issues, so I'm at a loss why more than 1 compac grinds it to a halt.
http://i60.tinypic.com/28vxerk.jpg

sr. member
Activity: 331
Merit: 250
First, no hub with bfgminer using .bat = bfgminer.exe -o [pool] -u [user] -p [pass] --set compac:clock=x0b83

1) bfgminer530 will not see the sticks on my old WinXP box.  Neither starting bfg with them (or just 1) plugged in nor hot plugging while bfg is running wakes them up.  The program just sits there and asks me to add hardware.

2) bfgminer530 on my Win7 box sees the sticks, however I get comms errors.  Here is just 1 stick:
http://i57.tinypic.com/317gjkp.jpg

3) when I plug a 2nd stick in the errors happen twice as often:
http://i57.tinypic.com/k3q70p.jpg


This has dropped back several pages and I'm still struggling with the Comms error, I cannot figure out what is causing it.  Any one have any suggestions?

And here's another issue to toss around, on my Win7 box the --set compac:clock tag in my .bat file for bfgminer has no effect on the sticks.  I tried several different values and the sticks always hashed at the same rate.  I tried omitting the command from my batch file entirely and the sticks hashed the same.  What's going on?

About the only thing I can think of, is try changing this: --set compac:clock=x0b83  to this: --set compac:clock=0x0b83

Not up on building and running under windows, so don't know if it needs that leading 0 or not.

So there's a miss-type in my OP and I do, in fact, have the leading 0 in my batch file.  I tried omitting the leading 0 and still no effect, just to be sure.  It's as if bfgminer is ignorning the --set compac command on this computer.  Could it be related to my comms error I wonder?

Have you tried adding the:     -S compac:all      to the bat?

I've seen that for U3's you add -S antminer:all for bfg to see the U3 sometimes, so wondering if it might have carried over to the compac (Novak stripped icarus down for compac and rebuilt it for cgminer, so did Luke jr do the same??).

EDIT: Just a thought to, is the "compac" maybe supposed to be "Compac"?  Don't know if it would make a difference or not, but?.....
legendary
Activity: 1274
Merit: 1000
First, no hub with bfgminer using .bat = bfgminer.exe -o [pool] -u [user] -p [pass] --set compac:clock=x0b83

1) bfgminer530 will not see the sticks on my old WinXP box.  Neither starting bfg with them (or just 1) plugged in nor hot plugging while bfg is running wakes them up.  The program just sits there and asks me to add hardware.

2) bfgminer530 on my Win7 box sees the sticks, however I get comms errors.  Here is just 1 stick:
http://i57.tinypic.com/317gjkp.jpg

3) when I plug a 2nd stick in the errors happen twice as often:
http://i57.tinypic.com/k3q70p.jpg


This has dropped back several pages and I'm still struggling with the Comms error, I cannot figure out what is causing it.  Any one have any suggestions?

And here's another issue to toss around, on my Win7 box the --set compac:clock tag in my .bat file for bfgminer has no effect on the sticks.  I tried several different values and the sticks always hashed at the same rate.  I tried omitting the command from my batch file entirely and the sticks hashed the same.  What's going on?

About the only thing I can think of, is try changing this: --set compac:clock=x0b83  to this: --set compac:clock=0x0b83

Not up on building and running under windows, so don't know if it needs that leading 0 or not.

So there's a miss-type in my OP and I do, in fact, have the leading 0 in my batch file.  I tried omitting the leading 0 and still no effect, just to be sure.  It's as if bfgminer is ignorning the --set compac command on this computer.  Could it be related to my comms error I wonder?
legendary
Activity: 1167
Merit: 1009
I just ordered some more sticks so ll test to see how many I can get working on my 49 Port hub soon
sr. member
Activity: 331
Merit: 250
First, no hub with bfgminer using .bat = bfgminer.exe -o [pool] -u [user] -p [pass] --set compac:clock=x0b83

1) bfgminer530 will not see the sticks on my old WinXP box.  Neither starting bfg with them (or just 1) plugged in nor hot plugging while bfg is running wakes them up.  The program just sits there and asks me to add hardware.

2) bfgminer530 on my Win7 box sees the sticks, however I get comms errors.  Here is just 1 stick:
http://i57.tinypic.com/317gjkp.jpg

3) when I plug a 2nd stick in the errors happen twice as often:
http://i57.tinypic.com/k3q70p.jpg


This has dropped back several pages and I'm still struggling with the Comms error, I cannot figure out what is causing it.  Any one have any suggestions?

And here's another issue to toss around, on my Win7 box the --set compac:clock tag in my .bat file for bfgminer has no effect on the sticks.  I tried several different values and the sticks always hashed at the same rate.  I tried omitting the command from my batch file entirely and the sticks hashed the same.  What's going on?



you have an old xp laptop you can't upgrade further on the windows stepladder use Unbuntu 12.04 (that is the highest i can use on my old only good for xp laptops)

Been wanting to build a linux machine for a while, may as well start out with the old laptop, good idea.  Thanks, I'll get back when I get around to installing it.

About the only thing I can think of, is try changing this: --set compac:clock=x0b83  to this: --set compac:clock=0x0b83

Not up on building and running under windows, so don't know if it needs that leading 0 or not.
Jump to: