Topic: GekkoScience Compac BM1384 Stickminer Official Support Thread - page 127. (Read 268015 times)
September 14, 2015, 05:49:17 PM
It's been awhile but I thought I remember Windows having a problem running too many sticks. That's why many opted to using a Pi.
September 14, 2015, 05:39:15 PM
here is valid hash
note the zombies the hub was only able to run 7 sticks see second screen shots I still get drop outs
note the zombies the hub was only able to run 7 sticks see second screen shots I still get drop outs
September 14, 2015, 05:33:09 PM
CGMiner recognizes the sticks, but they don't mine.
./cgminer -o stratum+tcp://peercoin.ecoining.com:3336/#skipcbcheck -u blackbird.2 -p 12345 --compac-freq 150
./cgminer -o stratum+tcp://peercoin.ecoining.com:3336/#skipcbcheck -u blackbird.2 -p 12345 --compac-freq 150
what are you running the sticks in .
A powered hub?
that reading you have does happen.
run 1 stick for 10 minutes and see if you get some valid hash.
September 14, 2015, 05:30:27 PM
CGMiner recognizes the sticks, but they don't mine.
./cgminer -o stratum+tcp://peercoin.ecoining.com:3336/#skipcbcheck -u blackbird.2 -p 12345 --compac-freq 150
./cgminer -o stratum+tcp://peercoin.ecoining.com:3336/#skipcbcheck -u blackbird.2 -p 12345 --compac-freq 150
September 14, 2015, 04:19:33 PM
So flat edge flush with bottom would be what voltage about?
It would depend which way you turned it. Did you turn right or left and how much? Could be .8 or .55 depending on that or between.
Not sure what you mean but no, it's always the same voltage. About 0.68V.
--
novak
Sorry about that I must be not understanding. With variable voltage screw how is it always the same? Or do you mean same voltage at certain spots on it?
Thanks for time on my questions, I do appreciate it.
Yeah, what I'm trying to say is: If the potentiometer is at a given position, it should always output the same voltage. The position he specified is flat edge against the bottom, so 180 degrees from 0.55V.
yeah it must affect the windows build. I can run two sticks at freq 350 get 0 hw nice speeds like 18-19gh a stick
yet I can not run 3 sticks on the same hub at freq 175 and get correct speeds.
Basically on windows 7 and 10
1 stick = really good
2 sticks = really good
3 or more = ?
yet I can not run 3 sticks on the same hub at freq 175 and get correct speeds.
Basically on windows 7 and 10
1 stick = really good
2 sticks = really good
3 or more = ?
Certainly unique. I'll check it out.
EDIT: Can't reproduce that at all on windows 7. What hub are you using and has it had this sort of trouble before?
--
novak
September 14, 2015, 04:17:40 PM
Yeah a compiled version that supports both would be a huge help for me
September 14, 2015, 04:14:15 PM
yeah it must affect the windows build. I can run two sticks at freq 350 get 0 hw nice speeds like 18-19gh a stick
yet I can not run 3 sticks on the same hub at freq 175 and get correct speeds.
Basically on windows 7 and 10
1 stick = really good
2 sticks = really good
3 or more = ?
yet I can not run 3 sticks on the same hub at freq 175 and get correct speeds.
Basically on windows 7 and 10
1 stick = really good
2 sticks = really good
3 or more = ?
September 14, 2015, 04:14:10 PM
So flat edge flush with bottom would be what voltage about?
It would depend which way you turned it. Did you turn right or left and how much? Could be .8 or .55 depending on that or between.
Not sure what you mean but no, it's always the same voltage. About 0.68V.
--
novak
Sorry about that I must be not understanding. With variable voltage screw how is it always the same? Or do you mean same voltage at certain spots on it?
Thanks for time on my questions, I do appreciate it.
September 14, 2015, 04:09:25 PM
That one might be on me for failing to gut all the icarus related stuff out of compac drivers. I've been collecting some small things that need to be repaired and I'll probably post an updated version soon. As far as your fix where you deleted the duplicate lines that's fine unless you don't build with --enable-icarus, because there are still apparently references to opt_anu_freq in driver-gekko.c. As I said, I have them cleaned up in my current working version and should have it out for you guys soon. I'll try to test with the u2 as well.
Thanks for looking into this. There are other compile problems with usbutils.c, which I've just worked through. Now I'm seeing problems with driver-gekko.c.
Unfortunately I'm out of time for the next few hours. So I won't be able to poke at this anymore.
But none of these are difficult problems. Looks like it's just some clean up to dis-entangle your gekko implementation from the same named code and variables for icarus.
If you get a clean build before I do, I'd be happy to take your source updates and rebuild for the Pi.
I've already got most of it done, I just need to test it thoroughly before I post it.
--
novak
September 14, 2015, 04:02:30 PM
That one might be on me for failing to gut all the icarus related stuff out of compac drivers. I've been collecting some small things that need to be repaired and I'll probably post an updated version soon. As far as your fix where you deleted the duplicate lines that's fine unless you don't build with --enable-icarus, because there are still apparently references to opt_anu_freq in driver-gekko.c. As I said, I have them cleaned up in my current working version and should have it out for you guys soon. I'll try to test with the u2 as well.
Thanks for looking into this. There are other compile problems with usbutils.c, which I've just worked through. Now I'm seeing problems with driver-gekko.c.
Unfortunately I'm out of time for the next few hours. So I won't be able to poke at this anymore.
But none of these are difficult problems. Looks like it's just some clean up to dis-entangle your gekko implementation from the same named code and variables for icarus.
If you get a clean build before I do, I'd be happy to take your source updates and rebuild for the Pi.
September 14, 2015, 03:47:33 PM
Oh, oh. I tried to build with icarus and gekko support (following my own recipe above) and I got a compile error:
Novak, could this be a copy/paste issue where a variable got reused without being renamed?
Code:
make[2]: Entering directory '/var/www/minera/minera-bin/src/cgminer-gekko'
CC cgminer-cgminer.o
cgminer.c:237:7: error: redefinition of ‘opt_anu_freq’
cgminer.c:229:7: note: previous definition of ‘opt_anu_freq’ was here
cgminer.c:240:7: error: redefinition of ‘opt_rock_freq’
cgminer.c:232:7: note: previous definition of ‘opt_rock_freq’ was here
Makefile:782: recipe for target 'cgminer-cgminer.o' failed
make[2]: *** [cgminer-cgminer.o] Error 1
Novak, could this be a copy/paste issue where a variable got reused without being renamed?
That one might be on me for failing to gut all the icarus related stuff out of compac drivers. I've been collecting some small things that need to be repaired and I'll probably post an updated version soon. As far as your fix where you deleted the duplicate lines that's fine unless you don't build with --enable-icarus, because there are still apparently references to opt_anu_freq in driver-gekko.c. As I said, I have them cleaned up in my current working version and should have it out for you guys soon. I'll try to test with the u2 as well.
Does cgminer-gekko come with xnsub for nicehash or do I need to patch it in myself?
It's the same as stock 4.9.2, so, no.
So flat edge flush with bottom would be what voltage about?
It would depend which way you turned it. Did you turn right or left and how much? Could be .8 or .55 depending on that or between.
Not sure what you mean but no, it's always the same voltage. About 0.68V.
--
novak
September 14, 2015, 03:46:07 PM
If this is Minera do you mind uploading a image if you got it to work with both icarus and gekko? Currently i'm using icarus, but eventually once I get production one it would be great to plug in and it uses compac.
I can try. But first we need to be able to build with both features on. I'm still running into compile problems (see my edits above).
After that, if I have a working build, it will be a lot easier for me to post just the fixed binary. Maybe you, or mindtrip, could test with that (it's simple to install the updated binary to an existing installed minera mod). I can't test because I don't have a U2.
If that works, then I can take the time to re-image and re-post the updated minera mod.
Also, is there any other mining hardware likely to be used with the minera cgminer-gekko mod that are off by default? I'd rather turn them all on now rather than keep re-posting updates.
September 14, 2015, 03:37:31 PM
Oh, oh. I tried to build with icarus and gekko support (following my own recipe above) and I got a compile error:
Novak, could this be a copy/paste issue where a variable got reused without being renamed?
Code:
make[2]: Entering directory '/var/www/minera/minera-bin/src/cgminer-gekko'
CC cgminer-cgminer.o
cgminer.c:237:7: error: redefinition of ‘opt_anu_freq’
cgminer.c:229:7: note: previous definition of ‘opt_anu_freq’ was here
cgminer.c:240:7: error: redefinition of ‘opt_rock_freq’
cgminer.c:232:7: note: previous definition of ‘opt_rock_freq’ was here
Makefile:782: recipe for target 'cgminer-cgminer.o' failed
make[2]: *** [cgminer-cgminer.o] Error 1
Novak, could this be a copy/paste issue where a variable got reused without being renamed?
Turns out there were a couple of duplicate lines of code. I removed them and it compiles now.
Here's what the relevant section of cgminer.c code looks like without the duplicate lines:
Code:
#ifdef USE_ICARUS
char *opt_icarus_options = NULL;
char *opt_icarus_timing = NULL;
float opt_anu_freq = 250;
float opt_au3_freq = 225;
int opt_au3_volt = 775;
float opt_rock_freq = 270;
#endif
#ifdef USE_GEKKO
char *opt_gekko_options = NULL;
char *opt_gekko_timing = NULL;
float opt_compac_freq = 125;
#endif
bool opt_worktime;
If this is Minera do you mind uploading a image if you got it to work with both icarus and gekko? Currently i'm using icarus, but eventually once I get production one it would be great to plug in and it uses compac.
September 14, 2015, 03:33:46 PM
Oh, oh. I tried to build with icarus and gekko support (following my own recipe above) and I got a compile error:
Novak, could this be a copy/paste issue where a variable got reused without being renamed?
Code:
make[2]: Entering directory '/var/www/minera/minera-bin/src/cgminer-gekko'
CC cgminer-cgminer.o
cgminer.c:237:7: error: redefinition of ‘opt_anu_freq’
cgminer.c:229:7: note: previous definition of ‘opt_anu_freq’ was here
cgminer.c:240:7: error: redefinition of ‘opt_rock_freq’
cgminer.c:232:7: note: previous definition of ‘opt_rock_freq’ was here
Makefile:782: recipe for target 'cgminer-cgminer.o' failed
make[2]: *** [cgminer-cgminer.o] Error 1
Novak, could this be a copy/paste issue where a variable got reused without being renamed?
Turns out there were a couple of duplicate lines of code. I removed them and it compiles now.
Here's what the relevant section of cgminer.c code looks like without the duplicate lines:
Code:
#ifdef USE_ICARUS
char *opt_icarus_options = NULL;
char *opt_icarus_timing = NULL;
float opt_anu_freq = 250;
float opt_au3_freq = 225;
int opt_au3_volt = 775;
float opt_rock_freq = 270;
#endif
#ifdef USE_GEKKO
char *opt_gekko_options = NULL;
char *opt_gekko_timing = NULL;
float opt_compac_freq = 125;
#endif
bool opt_worktime;
EDIT: Unfortunately there are more build errors in usbutils.c. They're probably the same kind of thing. I'll take a look, but I might run out of time before I have to go to a dentist appointment.
Novak, since you're the author of these changes maybe it makes sense for you to try building with both icarus and gekko on. I'm sure you'll see the same compile problems. They should be simple to resolve.
September 14, 2015, 03:30:37 PM
Trying CGMiner now. Getting a "Failed to initiate device" error. It recognizes the devices.
Using ./cgminer -o stratum+tcp://peercoin.ecoining.com:3336/ -u blackbird.2 -p 12345 --compac-freq 150
Using ./cgminer -o stratum+tcp://peercoin.ecoining.com:3336/ -u blackbird.2 -p 12345 --compac-freq 150
I would like to help, but I have not seen that error specifically. Can I get a little more info about your setup? What OS, How are you powering, did you rebuild cgminer,etc? Maybe get a little more cgminer output?
I posted a question for you on another thread do you know if I can run older U2's in the same instance of cgminer or can I only stick to the compacs id like to fill the rest of the hub with my older U2's and ahve only 1 pi 2 running them all 
I don't know if they will detect correctly, as the icarus driver specifically can detect anything with approximately the correct chips. You can try, you'd need top build with --enable-icarus and --enable-gekko.
Novak can you provide a diagram showing the voltage adjustment position in relation to voltage I use the flat surface as a guide and with it directly flush with USB port I have been able to get to 250 mhz or so no HW errors I dont have a volt meter handy to test what voltage that brings me up to
Here you go:
--
novak
So flat edge flush with bottom would be what voltage about?
It would depend which way you turned it. Did you turn right or left and how much? Could be .8 or .55 depending on that or between.
September 14, 2015, 03:27:54 PM
Trying CGMiner now. Getting a "Failed to initiate device" error. It recognizes the devices.
Using ./cgminer -o stratum+tcp://peercoin.ecoining.com:3336/ -u blackbird.2 -p 12345 --compac-freq 150
Using ./cgminer -o stratum+tcp://peercoin.ecoining.com:3336/ -u blackbird.2 -p 12345 --compac-freq 150
I would like to help, but I have not seen that error specifically. Can I get a little more info about your setup? What OS, How are you powering, did you rebuild cgminer,etc? Maybe get a little more cgminer output?
I posted a question for you on another thread do you know if I can run older U2's in the same instance of cgminer or can I only stick to the compacs id like to fill the rest of the hub with my older U2's and ahve only 1 pi 2 running them all
I don't know if they will detect correctly, as the icarus driver specifically can detect anything with approximately the correct chips. You can try, you'd need top build with --enable-icarus and --enable-gekko.
Novak can you provide a diagram showing the voltage adjustment position in relation to voltage I use the flat surface as a guide and with it directly flush with USB port I have been able to get to 250 mhz or so no HW errors I dont have a volt meter handy to test what voltage that brings me up to
Here you go:
--
novak
So flat edge flush with bottom would be what voltage about?
September 14, 2015, 03:27:09 PM
Here you go:
--
novak
--
novak
Thank you novak! I was afraid of turning it much on my own. This explains a lot.
Has anyone used the RPI 1 B with it and RPI 2? I was wondering if there is any noticeable difference for this with the RPI 2 that is worth the upgrade cost of getting another PI. Was not sure if worth buying one or not.
September 14, 2015, 03:14:03 PM
Does cgminer-gekko come with xnsub for nicehash or do I need to patch it in myself?
September 14, 2015, 03:07:30 PM
Oh, oh. I tried to build with icarus and gekko support (following my own recipe above) and I got a compile error:
Novak, could this be a copy/paste issue where a variable got reused without being renamed?
Code:
make[2]: Entering directory '/var/www/minera/minera-bin/src/cgminer-gekko'
CC cgminer-cgminer.o
cgminer.c:237:7: error: redefinition of ‘opt_anu_freq’
cgminer.c:229:7: note: previous definition of ‘opt_anu_freq’ was here
cgminer.c:240:7: error: redefinition of ‘opt_rock_freq’
cgminer.c:232:7: note: previous definition of ‘opt_rock_freq’ was here
Makefile:782: recipe for target 'cgminer-cgminer.o' failed
make[2]: *** [cgminer-cgminer.o] Error 1
Novak, could this be a copy/paste issue where a variable got reused without being renamed?
September 14, 2015, 02:28:10 PM
I posted a question for you on another thread do you know if I can run older U2's in the same instance of cgminer or can I only stick to the compacs id like to fill the rest of the hub with my older U2's and ahve only 1 pi 2 running them all
I don't know if they will detect correctly, as the icarus driver specifically can detect anything with approximately the correct chips. You can try, you'd need top build with --enable-icarus and --enable-gekko.
mindtrip, are you using my Minera mod? If so, I didn't build it with --enable-icarus. I only used --enable-gekko, because originally I was building this for me and I only have sticks, not U2's.
That said, it should be easy to rebuild cgminer and add Icarus support. Here's what the steps would be after ssh'ing in as the "minera" user:
Code:
cp /var/www/minera/minera-bin/custom/cgminer-gekko /var/www/minera/minera-bin/custom/cgminer-gekko_saved
cd /var/www/minera/minera-bin/src/cgminer-gekko
./configure --enable-icarus --enable-gekko
make
sudo make install
cp cgminer ../../custom/cgminer-gekko
Hopefully you won't have to do a "make clean". I suspect that since you'll be changing the config above that cleaning probably won't be necessary.
After the above, you should be able to restart the miner from minera, and it will be running the updated cgminer with icarus and gekko support.
Of course enabling U2 support doesn't guarantee that it will work. But at least you'd be able to test at this point.
If something goes wrong, you'll have a backup of the original mod cgminer binary (the cgminer-gekko_saved created in the first step).
Jump to: