Pages:
Author

Topic: GekkoScience NewPac / Terminus R606 (BM1387) Official Support Thread - page 18. (Read 61918 times)

legendary
Activity: 3583
Merit: 1094
Think for yourself
That was my thought too.  Johnny closed his pool and the thread.

I changed "gekko-newpac-freq 100" to "gekko-newpac-freq 150"

And I saw no change in frequency..... It stayed at 100.

Does the target say 150?

How long did you wait?  The auto tune can take a while.
hero member
Activity: 2534
Merit: 623
I thought bravo mining pool was closed?

Also we need more info on your setup. What hub, what OS etc etc etc
newbie
Activity: 19
Merit: 2
I've been successfully using from 1 to four gekkoscience newpac miners for a few weeks now.

Today I decided to try my hand at overclocking them.

Using the following type command:
"cgminer -o stratum+tcp://stratum.bravo-mining.com:3333 -user - password -p x --suggested diff 1 --gekko-newpac-freq 100"

I changed "gekko-newpac-freq 100" to "gekko-newpac-freq 150"

And I saw no change in frequency..... It stayed at 100.
Power cycling did not accomplish anything.

Any suggestions?

TNX
newbie
Activity: 22
Merit: 0
Thanx! i will try to find a way how to do that, im not so good at what to write to add the furries.

Hope some one can fill me in what to write in the terminal to make it work.

I'm not sure what you mean by "write in the terminal"?

When you compile the CGMiner source code you need to enable support for each type of miner you have.
Sorry, thats right idk how to enable the support for each type of miner.
legendary
Activity: 3583
Merit: 1094
Think for yourself
Thanx! i will try to find a way how to do that, im not so good at what to write to add the furries.

Hope some one can fill me in what to write in the terminal to make it work.

I'm not sure what you mean by "write in the terminal"?

When you compile the CGMiner source code you need to enable support for each type of miner you have.
newbie
Activity: 22
Merit: 0
thanx for the tip, but cgminer dont detect them its like there is no support for them in the cg 4.11.1. bfgminer do detect them can i run both cg and bfg at the same time with the same usb hub?
I don't know how it works on a mac, but in linux i would recompile Cgminer and add the option for the furries.
In the Github directory of Cgminer you can find the options to add the furries.
https://github.com/ckolivas/cgminer

in the "ASIC-README" file you can find the options. I don't know anything about furries, so maybe someone else here can fill it in about what you need.

Thanx! i will try to find a way how to do that, im not so good at what to write to add the furries.

Hope some one can fill me in what to write in the terminal to make it work.
member
Activity: 88
Merit: 85
thanx for the tip, but cgminer dont detect them its like there is no support for them in the cg 4.11.1. bfgminer do detect them can i run both cg and bfg at the same time with the same usb hub?
I don't know how it works on a mac, but in linux i would recompile Cgminer and add the option for the furries.
In the Github directory of Cgminer you can find the options to add the furries.
https://github.com/ckolivas/cgminer

in the "ASIC-README" file you can find the options. I don't know anything about furries, so maybe someone else here can fill it in about what you need.



newbie
Activity: 22
Merit: 0
thanx for the tip, but cgminer dont detect them its like there is no support for them in the cg 4.11.1. bfgminer do detect them can i run both cg and bfg at the same time with the same usb hub?
legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
Try running cgminer from a different directory as a separate instance just for the BF sticks?
newbie
Activity: 22
Merit: 0
Ok everything works with the new pac on osx cgminer-4.11.1, but i have searched for a fix how to make cgminer-4.11.1 detect the old RedFury and Bi•Fury but i cant get it to work.

Any one got a fix for this?
newbie
Activity: 21
Merit: 0
Correct, they are on USB still. I figured it out with the help of someone else.
I ran cmd cgminer -n and saw what it was seeing, they'd moved from 2:3 & 2:5 to 2:22 & 2:27 after I added the second hub
legendary
Activity: 3583
Merit: 1094
Think for yourself
CGMiner doesn't use com ports.  It uses the winusb driver.

Doesn't Zadig give the USB device number.  Also I thought there was a CGMiner command line option for that as well?
legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
My guess is that Win is treating the USB connections as com ports (COM2, COM3, etc). If it is, ja Winbloze has a nasty habit of not reusing vacant ports and reassigning them when a USB connection is changed. Our laser systems use 4 COM ports for monitoring and when I used to use RS232-USB converters that used to raise hell when even just unplugging a cable and then plugging it back into the same connector. Win would give them a new COM port and I'd have to either cnage the monitor program to use the new port or go into Win and fix it...

If that is the case you need to go into Device Manager and see what COM ports have been assigned and remove any not actually being used.
newbie
Activity: 21
Merit: 0
I've got 3xMoonlander2's and 2xNewpacs both mining on a W10 machine. I had them all on the same hub, and called out the Newpac addresses in their .bat files to keep the miners from scanning & finding the moonlanders. Before I did this, cgminer would see the moonlanders and not know what to do with them - throwing up an error.

In the process of moving the moonlanders to a 2nd hub, I think the address of the first hub changed, so now my "--USB 2:4,2:3" is incorrect because the miner doesn't find the newpac at that address. I've tried digging around in device manager to figure out the address again but nothing I've tried works.

I removed the --USB argument from the bat's and have them mining again, with the constant "ML WTF is this" errors scrolling by.
I have them both called out by serial number individually in their respective bat's. That doesn't stop CGminer from scanning and seeing the moonlanders.
It wasn't until I called out the USB ports via the --USB tag that I got it to stop scanning. And it was all working fine until I added the 2nd USB hub.

How can I definitely determine the (new?) address of my newpacs so the cgminer knows where to find them and not bother scanning for other devices?
newbie
Activity: 16
Merit: 0
hy guys, is there any chance of gettin the Newpack to run with minepeon? I've got CGminer 4.11.1  and are able to run Nanofurys with this but was wondering what it would need to get a the Newpack to run? Anyone any suggestions?

thx Ray
newbie
Activity: 21
Merit: 0
Look through the top post and mstroziers installation instructions on page 28.  There are a couple methods to pick specific devices.

GOT IT!! Thank you.
legendary
Activity: 3583
Merit: 1094
Think for yourself
How do I get cgminer to stop scanning/trying to grab the Moonlanders I have running on the same machine/hub?

Look through the top post and mstroziers installation instructions on page 28.  There are a couple methods to pick specific devices.
newbie
Activity: 21
Merit: 0
How do I get cgminer to stop scanning/trying to grab the Moonlanders I have running on the same machine/hub?
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Verified that works!  Yay solo mining with newpacs on bitcoind v0.21!  Thanks 100knot2dae!

Do you want to submit this patch to vh's cgminer?  I can also do so if you'd like.
How did you verify it?

Did you get it to submit a block and bitcoin accepted it?
Or are you just running it and hoping it works?

Just mining with it will not mean it works.

... and if you don't run it on the full bitcoin network, ensure it's a 64 bit block, or it's not a full test.
hero member
Activity: 2534
Merit: 623
Try using the instructions by mstrozier on page 28. Worked great for me on my Pi4.
Pages:
Jump to: