 Show Posts
|
|
Pages: [1]
|
Newbie questions...
I have 3 Apollo BTC miners up and running with no issues. Full node downloaded in 1.5 days. :-)
I have a controller and 2 standard units. I am running in turbo mode. Hash rate is ~3.1 I see all 3 in the dashboard.
Is there any way to increase the power on one of the standard units that is running with a 500W power supply? The other 2 are running the 200W PS. If they all need to be managed by the same rules, I will buy 2 more 500W power supplies if that allows me to increase the hash rate . If I do that, how do push all three to the 3.8TH/s limit? Do I need to adjust the power in "Custom Miner Mode"? If so, how high should I go?
Thank you in advance for your help/advice.
"*Our FutureBit 200W power supply is limited to ~ 3 TH/s, 3.8 TH/s is only achievable with an external > 300 watt power supply" +1 for this question. What are recommended settings for 3.8 TH/s? For now, I have been going as far as 85/55, resulting in approx. 3,4TH/s@0,07W/GHs (with a 0,9% error rate). Guess you have to push the freq up to 60 to get the full 3,8TH/s (provided you have a capable PSU ofc!) Each hardware has its own sweet spot, so you have to try out what works best for you. I have two units but cannot get the second one to fire using miner_start_all. Any chance you'd be willing to help me work through this? |
|
|
|
|
I cannot get the second miner to work. (2x standard units, run by hackintosh running latest ubuntu)
Running start_all produces "Started" but my second miner does not begin to run. Red light continues to flash.
Could this be a worker issue with the pool I'm connecting to? Do I need to differentiate the workers somehow with regards to the pool?
Also, when I try to run "screen" the system tells me there are no screens to display. None of the screen commands yield anything.
|
|
|
|
Double-check your USB node drive is plugged in the USB port in the back of your Apollo, properly formatted with the folder name "Bitcoin" in the root directory, and press the Start button below.
30 minutes later, several times, nothing but the same message, but it is mining finally for extended hours.
Shoot us an email (reply to your order email). Well trouble shoot node drive...most likely a ssd connection issue. I emailed you guys and posted on here but have yet to get a response. Going on three weeks with only one miner working. Time is money. Help a brother out. |
|
|
|
... and now for a little but of fun  I can actually answer if the apollo is coded to be able to find blocks or not now. Someone decided to risk testing it (solo) on KanoPool and take that risk for apollo. But since most around here seem to think I don't know what I'm talking about, and various people like making false accusations about me, I'll leave it up to the people who sold you the software to verify it, as it should have been done in the first place. We have not released any solo mining capability, and when we do that will be obviously tested rigorously on our end via testnet and unit tests. What you are talking about is testing YOUR pool code on whether it can successfully submit a block. You obviously already know we are submitting valid shares. Since your pool has not submitted a valid block in nearly a year maybe your code should be more in question than ours  Funny, again, showing that you actually have no idea about how to properly test a miner. Well, you have spent your time dealing with scamcoins, now you've come to sell a miner to real miners, you need to brush up a bit on reality. Dude we get it and you’re awesome but can you have this discussion elsewhere? Us suckers just want help with the miners we bought. Thanks. |
|
|
|
Hi ! My miner is always inactive and I can't change de pool config. (I did changed it in the Pools section of the menu but the config stay the same in the Dashboard)  Can you help me please  This looks like you are using the wrong worker name. Have you set up an account on slushpool and named your worker the same? In the image it says your worker is jstefanop, which is the creator of futurebit and is in the apollo_start.sh file by default. Change that info to your slushpool info. |
|
|
|
|
Bought two standard units. I'm a linux amateur, probably should have bought a full unit. Have been able to configure start_apollo.sh file and get one miner running. Connected to a hackintosh running ubuntu. I cannot figure out how to get second miner running.
./miner_start_all.sh returns "line 8: screen: command not found" two times, then says "Started." Yet I can't see the worker in the pool, and red light stays solid. How do I get the second miner running? How do I open a second instance?
Appreciate any advice, but please talk slow for the dummy.
Also, was hoping to run each miner via its own rpi, but cannot find a way to run a stable 64-bit os on the rpis to install the 64-bit apollo software. Is 32-bit coming? Any suggestions for running these via rpi? Appreciate the help. Learning as I go but I have to start somewhere.
Thanks.
|
|
|
|
|
Hey all, new here and not very well educated on messing with hardware, but I want to try.
I mined for 18 months or so with my Giant N, and it's been weird and buggy here and there and I think one of my boards is half dead. Baikal no longer responds to my emails.
Now I cannot interface with the miner. The main page (logging into the ip in browser) works, but none of the other pages show anything of substance. Miner/Settings/Backup are all blank minus the Scripta links and Load/Temperature readouts.
I am hoping to reflash the firmware, but I don't know where to get it, and I've seen the scammer posts here. I'll continue to try to contact Baikal.
In the meantime, is there anything I can do in Terminal? I'm raw at BASH but learning. Further, can I take apart the ASIC and start messing with it? Where can I learn that?
Thanks in advance.
|
|
|
|
|
