I have a few old computers laying around. Any suggestions on how to utilize the power supply from one of them?
Just plug one of the 6pin PCIE cables into the R606 connector. |
|
|
|
I agree, in the past on a reboot it would always work its way up to the 750 target and land at ~1Th/s
It seems like maybe this is a hardware issue since I haven't changed anything in software or settings... I'm just not really sure how to interpret it or how to test it.
Any ideas?
The only time I couldn't get mine over 200Mhz is when I had it connected through a USB 2.0 hub. Are you plugged directly into the USB Port on the Pi 4? Try both the 2.0 and 3.0 Ports on it. Verify your Power Supply is good. I use an ATX computer P/S. |
|
|
|
--------------------------------------------------------------------------------
SB management [P]ool management ettings [D]isplay options [Q]uit
0: GSI 10040368: BM1387:12+ 175.00MHz T:31 P:25 (26:18) | 9.0% WU:^ 7% | 23.45G / 19.23Gh/s WU:268.6/m
--------------------------------------------------------------------------------
It' really odd that your Freq is 175Mhz but your Target is 31Mhz and Plateau is 25Mhz. I don't recall ever seeing something like that. |
|
|
|
I have a problem i can't get it higher then 100mhz cgminer keeps starting on 100mhz en don't get any higher
Did you check and see if you have a .conf file? That may be overriding your command line. |
|
|
|
|
Mining isn't going to stop.
|
|
|
|
|
Also, there is a support thread for this unit. It would be best to use it instead of starting a new thread.
|
|
|
|
Just curious, what are you all using as you're difficulty setting with the newpacs? I'm at 512 right now, but I'd like to know your opinions.
Just let the pool adjust. It only matters for the pool to report a reasonably accurate hash rate for your equipment. Most pools adjust for a rate of 18 shares per minute. |
|
|
|
Thinking of replacing the fan before trying to overclock higher, what RPM you think the fan should have to be able to cool down the unit efficiently?
In my experience going over 750Mhz just consumes more power with minimal increases in hash rate. Use a power meter and plot your curve on power consumption and hash rate for your device. |
|
|
|
Unfortunately 20.04 is only available in the LTS version not the prebuild version which pi requires. Does anyone know if I can run bfgminer on these newpacs? For whatever reason I can compile that.
Well just use the Raspberry OS. It's made for it after all. BFG Miner doesn't support newpacs. They developed their own version of CGMiner to support these. I think I am just missing some package that it requires to compile, but I just don't know which one. The packages that it lists are fairly minimum, as the compiling would error out it would give you a clue to what was missing, for example libz. I am looking for a way to figure out what might be missing but the error message is not descriptive. Is there a way to debug the compile? If you look through this thread you will see many posts about people having trouble using Ubuntu .10 versions. The fix was always to use the LTS release. Raspbian is known to work fine and well. |
|
|
|
Unfortunately 20.04 is only available in the LTS version not the prebuild version which pi requires. Does anyone know if I can run bfgminer on these newpacs? For whatever reason I can compile that.
Well just use the Raspberry OS. It's made for it after all. BFG Miner doesn't support newpacs. They developed their own version of CGMiner to support these. |
|
|
|
As far as I know all the dependencies that required were installed. Running Ubuntu 20.10 on Raspberry Pi.
If you need to use Ubuntu for some reason, use an LTS version such as 20.04. I think the .10's are beta's. On a Pi it's probably best to use rasbian. If you do decide to try the raspberry OS then these instructions are a little more detailed than the top post. https://bitcointalk.org/index.php?topic=5053833.msg50968875#msg50968875 |
|
|
|
protocol will be changed to allow for emptying dead stagnant wallets.
I should hope NOT. There is now way to tell if a coin is lost or a wallet is in cold storage for ones future children or grandchildren. |
|
|
|
I've recently added a second Newpac to my Sipolar hub. The original unit would run steady at about 50GH at a frequency of 225. When I add a second unit to the hub, both units fall to an ASIC plateau of 180, even though the second unit when run alone also runs solid at 225.
Is this potentially an issue with the hub?
Maybe the hub isn't supplying enough power for two. |
|
|
|
Has anyone found a pool that accepts less than .001 BTC that they like?
kano.is will payout less than that, but your hash rate needs to be above the dust level which is probably around 500Ghs or so. Asking about pools tends to get a bit ugly sometimes as we all have differing opinions on what constitutes a good pool to us. |
|
|
|
Well that tool a while but I'm now at 150MHz................ I finally found and changed the cgminer.conf file. It was hiding at : /root/.cgminer/cgminer.conf
I think it ends in .conf
THANKS ! Glad to hear it. I've never saved a configuration the .conf file before so I know very little about. I like doing things from a command line. However on my Pi 4 I did create a .sh file which contains my command line, which is quite lengthy since I have 4 or 5 fail over's. Make sure you have good cooling on your sticks as you ramp up your frequency. |
|
|
|
Am I to believe that it is impossible to change the frequency with the argument " --gekko-newpac-freq xxx" once compiled?
I can change frequencies. |
|
|
|
Any thoughts on which of them to look for the frequency parameter or whit it might be called so I can search for it?
I think it ends in .conf |
|
|
|
by target - I think he is meaning in cgminer - see where I circled?
Yep, you are correct sir.  |
|
|
|
Shure I'll try...From the top........... 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? Target??? the only reference is in my script which I changed to "gekko-newpac-freq 150". cgminer version 4.11.1 - Started: [2021-04-09 10:31:15.987]
--------------------------------------------------------------------------------
(5s):1.545T (1m):1.095T (5m):368.0G (15m):135.8G (avg):786.7Gh/s
A:16380 R:0 HW:1 WU:11021.8/m
Connected to nya.kano.is diff 8.19K with stratum as user os2sam.r606
Block: 9990ceed... Diff:23.1T Started: [10:31:15.987] Best share: 14.7K
--------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
0: GSI 10040114: BM1387:12+ 550.00MHz T:650 P:499 (11:6) | 90.8% WU:^72% | 757.2G / 543.1Gh/s WU:7600.5/m
1: GSI 10040033: BM1387:12+ 600.00MHz T:650 P:491 (10:5) | 81.8% WU:^66% | 793.4G / 544.5Gh/s WU:7617.5/m In CGMiner you should see T:150 where mine above says T:650. That is the target CGMiner is trying for. If you didn't see the T:150 then something is telling CGMiner to target 100 Mhz instead. Someone asked to check your .conf file for conflicting commands. |
|
|
|
So its been over 18 hours and I'm still mining at 100 Mhz.
I just don't know where to look from here.
Three people have asked you multiple questions. You could try answering some of them, maybe. |
|
|
|
|
Show Posts
