That's what I thought about the U3's seeing as they are externally powered they must draw a very small amount. Not sure how to check that on the U3 Pcb, I'll take a look tomorrow.
I got the multimeter out and it's running 680-690mv so pretty good on the voltage/ghs aspect I assume.
I'll grab a y cable and see what happens with a bit of fiddling. I'm not complaining at all about the stick though (incase its come across that way). It's works great and constantly gets the highest share on cgminer, most of the time beating my s3's lol. I just like tinkering and can never leave anything alone in its standard form for long lol.
Thanks for the help as always.
Topic: GekkoScience Compac BM1384 Stickminer Official Support Thread - page 44. (Read 268030 times)
i have 5 compacs running on this hub, so far no issues.. its running off a r1.
http://www.amazon.com/Upgraded-Anker-SuperSpeed-Including-Charging/dp/B005NGQWL2
http://www.amazon.com/Upgraded-Anker-SuperSpeed-Including-Charging/dp/B005NGQWL2
That would help if you're seeing voltage sag. The buck trips out when the input voltage gets below 4V, which can happen with a high source impedance. It's also a problem when the sticks are super overclocked even on a good hub, because input current transients during switching cycles of the Vcore regulator can get crazy high and cause brief voltage sags. At the levels you're running that's probably not the problem but it could be.
Anyways. Yeah, a "Y" cable would probably help. If it does, you can figure the limit is how much current can be supplied to one port. If it doesn't, it's probably a system-wide limit. I don't know how much power a U3 pulls from USB but it's probably next to nothing.
Anyways. Yeah, a "Y" cable would probably help. If it does, you can figure the limit is how much current can be supplied to one port. If it doesn't, it's probably a system-wide limit. I don't know how much power a U3 pulls from USB but it's probably next to nothing.
Got it set at around 0.6-0.7 I think (will get a multimeter on the connections soon). Its getting about 12-13ghs at 230mhz. Im only running the one stick along with the 2 U3's on the same hub so don't think im pushing it too far. Would a "y" cable help with the power aspect, by spreading it across 2 ports?
Not sure how many sticks you have, but at about 640mV 200MHz one stick pulls about 800mA. So if you're running 3 sticks at 230Mhz you've maxed out the hub. If the hub's wiring will handle the juice, you could try using a higher-current 5V source for it and see if you can take them farther. Cranking the voltage way up for a slight frequency increase actually makes the power draw substantially worse.
MHz = GH/.055
MHz = GH/.055
So im running cgminer 4.9.2 (gecko edition) on my laptop and im running a 7 port usb 2.0 powered hub (2.5amp) with my gekko and 2xU3's plugged in. Just out of curiosity I tried turning the freq up on the gekko to see what I could get. Managed to get it upto 230mhz which is now stable. I tried getting it upto 250mhz but even with the voltage turned right up it wouldn't have it.
Now my question is; is the hub the limiting factor in this?
Thanks.
p.s. I bought a USB 2.0 hub as I was planning on running my "usb miners" on a raspi sometime in the future.
Thanks for the help as always
Now my question is; is the hub the limiting factor in this?
Thanks.
p.s. I bought a USB 2.0 hub as I was planning on running my "usb miners" on a raspi sometime in the future.
Thanks for the help as always
Any of these will fix any privacy issues. My favorite, naturally, is win10-unfuck,
https://github.com/W4RH4WK/Debloat-Windows-10
https://github.com/dfkt/win10-unfuck
https://github.com/10se1ucgo/DisableWinTracking
https://github.com/Nummer/Destroy-Windows-10-Spying
https://github.com/rand0m1ze/win10sanitizer
https://github.com/hulr/BetterPrivacy
https://github.com/W4RH4WK/Debloat-Windows-10
https://github.com/dfkt/win10-unfuck
https://github.com/10se1ucgo/DisableWinTracking
https://github.com/Nummer/Destroy-Windows-10-Spying
https://github.com/rand0m1ze/win10sanitizer
https://github.com/hulr/BetterPrivacy
If anyone is using win10 as a miner host; unless your a Network Engineer or CCNA I highly recommend either:
Set the computer on fire and start over with a different OS
Zero the hard drive and start over with a different OS
Never allow that computer to connect to a network of any kind for any reason, then start over with a different OS
This will alienate Microsoft so it can do less harm
Set the computer on fire and start over with a different OS
Zero the hard drive and start over with a different OS
Never allow that computer to connect to a network of any kind for any reason, then start over with a different OS
This will alienate Microsoft so it can do less harm
Not to mention all the various spyware and telemetry stuff they have built in, to radio home to Microsoft servers and let 'em know what you're up to all the time. I like that some entire countries were outlawing the use of Win10 because of security risks.
You made sure to copy over the zlib.dll or whichever it's called?
Also, Win10 sucks. I'll probably never officially acknowledge support for Win10 because I'll never have a computer running it to test anything on. But a couple folks on here have used it with success.
Win10 does suck. Windows pumped it full with added things they assume their customers need, but really it's just microsoft being sold out by a few companies and it drags down performance in basically every area. The only computer that I have running Win10 is a dell 11 series laptop, and it's at 80c idling because of all the extra features on there dragging it down. Don't do it, don't upgrade! My compac works fine on W10 though, but since I use a rpi to control my compacs it's useless. Also, Win10 sucks. I'll probably never officially acknowledge support for Win10 because I'll never have a computer running it to test anything on. But a couple folks on here have used it with success.
You made sure to copy over the zlib.dll or whichever it's called?
Also, Win10 sucks. I'll probably never officially acknowledge support for Win10 because I'll never have a computer running it to test anything on. But a couple folks on here have used it with success.
Also, Win10 sucks. I'll probably never officially acknowledge support for Win10 because I'll never have a computer running it to test anything on. But a couple folks on here have used it with success.
win10 64 bit
I tested in Linux then it all works fine.
I tested in Linux then it all works fine.
What is your OS?
win32 binary: gekkoscience.com/misc/cgminer-gekko-win32.zip
The current version supports bitshopper compacs as well, and can be (and is, in the case of windows) compiled with icarus support.
win32 binary: gekkoscience.com/misc/cgminer-gekko-win32.zip
The current version supports bitshopper compacs as well, and can be (and is, in the case of windows) compiled with icarus support.
Hi
I download latest gekkoscience.com/misc/cgminer-gekko-win32.zip
but when I run it
Cgminer.exe application error the application was unable to start correctly 0xc00007b click ok to close the application
I tried the earlier version for win32 and that works fine but no support for eu versions of sticks.
I download latest gekkoscience.com/misc/cgminer-gekko-win32.zip
but when I run it
Cgminer.exe application error the application was unable to start correctly 0xc00007b click ok to close the application
I tried the earlier version for win32 and that works fine but no support for eu versions of sticks.
well it happens that my neighbour has the tools I need, so I'll be working on my heatsinks this afternoon.
I also received a superbpag hub last week and all 6 sticks have been running flawlessly at 310Mhs...
So modding is on its way to be finished !
------ edit---
drilling tapering done, wasn't as tricky as I thought it would.
I had to remove the usb doctors as they cause problems when only 1 cable is connected...
I also received a superbpag hub last week and all 6 sticks have been running flawlessly at 310Mhs...
So modding is on its way to be finished !
------ edit---
drilling tapering done, wasn't as tricky as I thought it would.
I had to remove the usb doctors as they cause problems when only 1 cable is connected...
And if you want to run a U3 or most other stickminers, you'll need to --enable-icarus as well.
cgminer addition:
earlier instructions basically as described, then
wget http://gekkoscience.com/misc/cgminer-gekko.tar.gz
tar xzf cgminer-gekko.tar.gz
cd cgminer-gekko-rev2 #this is where there are some differences
sudo apt-get install autotools-dev libtool libusb-dev libudev-dev
./configure --enable-gekko
make
this should compile a cgminer in the dir you are in.. so you can run it by
./cgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr --compac-freq 150
fill in your own bitcoin username (after -u)
earlier instructions basically as described, then
wget http://gekkoscience.com/misc/cgminer-gekko.tar.gz
tar xzf cgminer-gekko.tar.gz
cd cgminer-gekko-rev2 #this is where there are some differences
sudo apt-get install autotools-dev libtool libusb-dev libudev-dev
./configure --enable-gekko
make
this should compile a cgminer in the dir you are in.. so you can run it by
./cgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr --compac-freq 150
fill in your own bitcoin username (after -u)
I used this method off the first page to set up everything. So, I thought this would take care of it. I did use a different dependency set though I believe. The RPi does provide enough power to run it at 125 as thats what I am doing now, though I know if I want to run it higher I will need a powered USB. I think I fixed the issue with restarting as I did have too many devices plugged in the the RPi and it wasn't getting enough juice. However, after hashing fine for hours, does the power issue explain it failing when the pool hit a block?
If you want to run the sticks on linux, you'll need either bfgminer or cgminer. Either way you are probably going to have to compile them, but I've had little trouble with this so it's probably just a matter of running a few simple commands.
Here's what you'd do to get cgminer on linux going:
1. Open a terminal.
2. wget http://gekkoscience.com/misc/cgminer-gekko.tar.gz
This downloads the file- you can save it from your browser instead, it's the same thing.
3. tar -xvzf cgminer-gekko.tar.gz
This extracts the files. which are compressed (like a zip file for linux)
4. cd cgminer-gekko
Enters the cgminer-gekko folder you just extracted.
5. sudo apt-get install build-essential autoconf automake libtool
You need to install the dependencies for cgminer.
6. ./autogen.sh
This will generate a configure script for you which will set up compiling for your system.
7. ./configure --enable-gekko
This will configure the build. This is the most likely place to have anything go wrong, if it does, let me know exactly what's up. Odds are it would be some package that you should have installed.
8. make
Performs the build. If you get an error there- again, let me know details.
You are ready to run cgminer. This should look something like:
./cgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr --compac-freq 150
Although if you don't have permissions setup you may have to become root or use sudo, eg,
sudo ./cgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr --compac-freq 150
cgminer should now detect any compacs plugged in while it is running. Obviously you'll use a slightly different command to launch cgminer, if you use that one you'll be mining for us! Most pools even post example commands, let me know if you need help figuring it out.
--
novak
[/quote]If you want to run the sticks on linux, you'll need either bfgminer or cgminer. Either way you are probably going to have to compile them, but I've had little trouble with this so it's probably just a matter of running a few simple commands.
Here's what you'd do to get cgminer on linux going:
1. Open a terminal.
2. wget http://gekkoscience.com/misc/cgminer-gekko.tar.gz
This downloads the file- you can save it from your browser instead, it's the same thing.
3. tar -xvzf cgminer-gekko.tar.gz
This extracts the files. which are compressed (like a zip file for linux)
4. cd cgminer-gekko
Enters the cgminer-gekko folder you just extracted.
5. sudo apt-get install build-essential autoconf automake libtool
You need to install the dependencies for cgminer.
6. ./autogen.sh
This will generate a configure script for you which will set up compiling for your system.
7. ./configure --enable-gekko
This will configure the build. This is the most likely place to have anything go wrong, if it does, let me know exactly what's up. Odds are it would be some package that you should have installed.
8. make
Performs the build. If you get an error there- again, let me know details.
You are ready to run cgminer. This should look something like:
./cgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr --compac-freq 150
Although if you don't have permissions setup you may have to become root or use sudo, eg,
sudo ./cgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr --compac-freq 150
cgminer should now detect any compacs plugged in while it is running. Obviously you'll use a slightly different command to launch cgminer, if you use that one you'll be mining for us! Most pools even post example commands, let me know if you need help figuring it out.
--
novak
thant novak writeup is partially incorrect now because last time I used it, it was cgminer-gekko-rev2.
I will provide instructions in the next post.
Also, to reiterate, make sure it's spelled correctly. Because if your command line says "compaq-freq" it won't work, on account of this stick miner is in no way associated with a defunct PC manufacturer.
@connersc
Plus with the compac directly plugged into the Pi, it may be causing heat problems in the USB chip from pulling the power to run the compac.
It may have just happened to hit some over temp cut-out just as the block was found (just a guess ??).
Plus with the compac directly plugged into the Pi, it may be causing heat problems in the USB chip from pulling the power to run the compac.
It may have just happened to hit some over temp cut-out just as the block was found (just a guess ??).
Jump to: