Official FutureBit Apollo LTC Image and Support thread

[jstefanop]

I call my miners Apollo1 y Apollo2 (not too much original names hum...  ).  I put a couple of quality labels on each (on top and front).

But, no way to know what miner I am monitoring when using webgui... only by IP.

I will like a lot a simple text field for assigning each miner a name. If visible at dashboard, you can identify your miners very easy.

Maybe too stupid request, but really easy to implement ha ha...

Next release will have a custom hostname for each device tied to a UID..this will be required due to to a new setup process I am testing that will not require an ethernet cable (Apollo will generate its own hotspot like "FutureBit-9D2FA" and you'll be be able to setup with just a wifi enabled device (smartphone/laptop etc).

[whiteogre]

There could be a small issue with the latest release. The added watchdog appears to be a little bit chatty causing the syslog to be filled with

Code:

watchdog: watchdog0: watchdog did not stop!

messages at a rate of about 12 every minute. Normally that wouldn't be an issue, but the /var/log mountpoint on the Apollo is ram disk sized to 50MB regardless of the used sd card size. It's filled at around 53% after install and there doesn't appear to be any cleanup or logrotate for this mountpoint active. As a result, the mountpoint will be full in around 2 weeks at the current rate. Most likely not all system services will be happy once no more logs can be written.

Yea this is hardcoded in the kernel source and didn't have time to remove it. Even if the log fills its not a huge deal but will have a process to clean up the logs next release.

It only requires one line in /etc/rsyslog.d/50-default.conf after the first comment block (before /var/log/syslog is defined) to filter that specific kernel message out:

Code:

:msg, contains, "watchdog did not stop!" stop

followed by

Code:

sudo systemctl restart rsyslog

[jstefanop]

There could be a small issue with the latest release. The added watchdog appears to be a little bit chatty causing the syslog to be filled with

Code:

watchdog: watchdog0: watchdog did not stop!

messages at a rate of about 12 every minute. Normally that wouldn't be an issue, but the /var/log mountpoint on the Apollo is ram disk sized to 50MB regardless of the used sd card size. It's filled at around 53% after install and there doesn't appear to be any cleanup or logrotate for this mountpoint active. As a result, the mountpoint will be full in around 2 weeks at the current rate. Most likely not all system services will be happy once no more logs can be written.

Yea this is hardcoded in the kernel source and didn't have time to remove it. Even if the log fills its not a huge deal but will have a process to clean up the logs next release.

It only requires one line in /etc/rsyslog.d/50-default.conf after the first comment block (before /var/log/syslog is defined) to filter that specific kernel message out:

Code:

:msg, contains, "watchdog did not stop!" stop

followed by

Code:

sudo systemctl restart rsyslog

Thats a cool trick. Ill probably need to do some kernel level modifications for next release anyway so I should get around to recompiling the kernel though 

[VictorGT]

This falls to the category of "do only if you know you can copypaste and follow the instructions" but here's how you can change the page title of the dashboard of each unit. The title is what's visible in the browser window bar or tab bar, not on the page itself. You need to connect via ssh to the mcu (the login and password has been mentioned in earlier posts) and then run the following two commands. Edit only the first one to match the wanted title but don't touch the second line:

Code:

pagetitle="The new dashboard title comes here within these quotes"
sed -i -e "s#<title>.*</title>#<title>${pagetitle}</title>#g" /opt/apolloapi/build/index.html

Reload the dashboard in the browser and that should be it. The original title is "Apollo miner web dashboard" if you forgot to write it down.

Thanks. I think a I can do both things  . I will try this.

[jstefanop]

Well everything is quiet here so I guess the new image is working better than I hoped 

[philipma1957]

Well everything is quiet here so I guess the new image is working better than I hoped 

no issues dead solid at midspeed setting


121 mh speed

63c temp miner
46c temp mcu

fan on manual  20% = 2760 rpm

Nice gear.

[vsc-miner]

Latest firmware is pretty solid. 2 miners have been running 5 days no issues so far. both at Balanced mode, fan is in automatic setting. ~121 Mh/s, Miners temp ~65-68C, MCU temp ~40-47C. The miner which had the locking incident always runs at a higher temperature but within the same range. Keep it solid.

[wttbs]

I am mining at Sigmapool now for a few days, this pool is very stable with the Apollo.

[henrik80]

Only issue I noticed is: the miner goes inactive/dead when connected to auto exchanging pools like zergpool or blockmasters etc and then it comes back again after x amount of time. Guess it's BFGMiner not liking something the pool does?

Besides from that it's spot on.

[stef942]

sometimes it may help adding /#skipcbcheck at the end of the pool adress in case of dead,unknow status 

[henrik80]

good to know, cheers

[psycodad]

Only issue I noticed is: the miner goes inactive/dead when connected to auto exchanging pools like zergpool or blockmasters etc and then it comes back again after x amount of time. Guess it's BFGMiner not liking something the pool does?

Besides from that it's spot on.

As mentionned before, make sure you do not have a backup pool configured when trying to mine on a multi/profitswitching pool.

[HagssFIN]

Cool, I got to try the latest firmware today when I get home

[huntingthesnark]

Cool, I got to try the latest firmware today when I get home

Just to check - updating to new firmware process is same as original setup? Format SD, etcher new firmware image, reinsert/restart?

[jstefanop]

Cool, I got to try the latest firmware today when I get home

Just to check - updating to new firmware process is same as original setup? Format SD, etcher new firmware image, reinsert/restart?

Yep! Unless you want to backup your settings instead of start from scratch. Just use the backup/restore options in the settings panel.

[whiteogre]

The number in the "current hashrate" box appears to still be some sort of all uptime average instead of "right now". The uptime of my unit is now a little over 7 days and today during few hours without external network connectivity I noticed that the front led of the unit had stopped flashing red (as expected). The dashboard was still claiming the hashrate to be over 95 Mh/s when it should have shown a zero. The only thing in the dashboard (apart from the red led not flashing) that pointed to some ongoing issue was the green line below the uptime having turned red and the small "Last share" text telling how long had been from the last share.

Once network connectivity was restored, the red led came on for about 10 seconds until if went back to the normal flashing routine. At least I didn't have to reboot the unit.

[HereToday]

Same as most other reports here. Upgrade works fine.

Cool temps in balanced mode, 30% fan, been running steady for many days.

The fan sounds a lot better, much more 'solid'

Trouble free mining!

[cereal7802]

Downloaded the apollo_image_1-29.img.zip image and on initial boot it went straight into the dashboard like nothing was wrong. I went to disable the donation pool and add my own and then the miner doesn't start. I only get that the api is refused and it never shows a hashrate. If I enable the donation again, it works fine. I would much rather this donation option was removed entirely. if people want to provide charity for a purchased device, then they can manually enter the info. Having it on by default and have issues where it refuses to work without it sounds like theft to me.




Update:

This doesn't look right. I suspect the interface is writing the config wrong.

Code:

  
      {
            "quota": "99;us.litecoinpool.org:3333",
            "user": "USERNAMEHERE",
            "pass": "PASSWORDHERE"
        },
        {
            "quota": "1;stratum+tcp://us.litecoinpool.org:3333",
            "user": "jstefanop.a1",
            "pass": "a1"
        }

[philipma1957]

Downloaded the apollo_image_1-29.img.zip image and on initial boot it went straight into the dashboard like nothing was wrong. I went to disable the donation pool and add my own and then the miner doesn't start. I only get that the api is refused and it never shows a hashrate. If I enable the donation again, it works fine. I would much rather this donation option was removed entirely. if people want to provide charity for a purchased device, then they can manually enter the info. Having it on by default and have issues where it refuses to work without it sounds like theft to me.




Update:

This doesn't look right. I suspect the interface is writing the config wrong.

Code:

  
      {
            "quota": "99;us.litecoinpool.org:3333",
            "user": "USERNAMEHERE",
            "pass": "PASSWORDHERE"
        },
        {
            "quota": "1;stratum+tcp://us.litecoinpool.org:3333",
            "user": "jstefanop.a1",
            "pass": "a1"
        }

okay  you simply filled out your info wrong


wait for me to link a proper config
I don't pay him a dime  I solo mine and that is it.



no donation zip just the solo pool

[TheYankeesWin!]

Phil didn't you send the developer of this gear some ltc last year?