Topic: Official FutureBit Apollo LTC Image and Support thread - page 52. (Read 49938 times)
Cool, I got to try the latest firmware today when I get home
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.
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.
good to know, cheers
sometimes it may help adding /#skipcbcheck at the end of the pool adress in case of dead,unknow status 
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.
Besides from that it's spot on.
I am mining at Sigmapool now for a few days, this pool is very stable with the Apollo.
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.
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.
Well everything is quiet here so I guess the new image is working better than I hoped
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:
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.
Code:
pagetitle="The new dashboard title comes here within these quotes"
sed -i -e "s#.* #${pagetitle} #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. 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
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.
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
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
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
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.
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
Code:
sudo systemctl restart rsyslog
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...
). 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).
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
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.
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.
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...
). 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...
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#.* #${pagetitle} #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.
Oh, you screwed then 
If prohashing uses password field to determine worker, then it's very strange behaviour. Yeah, I get it, you are not able to determine which Apollo you looking for just by looking at Apollos dashboard. They would be all the same to you.
I, for a change, use pool where my login is username.workername, I can determine which Apollo I'm looking at just by looking at the dashboard because my username there will be all I need to see.
Another suggestion for you then:
Setup up your router, so MAC address or Apollo is assigned to static IP. That way, they have same IPs forever.
If prohashing uses password field to determine worker, then it's very strange behaviour. Yeah, I get it, you are not able to determine which Apollo you looking for just by looking at Apollos dashboard. They would be all the same to you.I, for a change, use pool where my login is username.workername, I can determine which Apollo I'm looking at just by looking at the dashboard because my username there will be all I need to see.
Another suggestion for you then:
Setup up your router, so MAC address or Apollo is assigned to static IP. That way, they have same IPs forever.
Anyway, not a big problem. I can go to pools page and read Password field.
Oh, you screwed then If prohashing uses password field to determine worker, then it's very strange behaviour. Yeah, I get it, you are not able to determine which Apollo you looking for just by looking at Apollos dashboard. They would be all the same to you.
I, for a change, use pool where my login is username.workername, I can determine which Apollo I'm looking at just by looking at the dashboard because my username there will be all I need to see.
Another suggestion for you then:
Setup up your router, so MAC address or Apollo is assigned to static IP. That way, they have same IPs forever.
If prohashing uses password field to determine worker, then it's very strange behaviour. Yeah, I get it, you are not able to determine which Apollo you looking for just by looking at Apollos dashboard. They would be all the same to you.I, for a change, use pool where my login is username.workername, I can determine which Apollo I'm looking at just by looking at the dashboard because my username there will be all I need to see.
Another suggestion for you then:
Setup up your router, so MAC address or Apollo is assigned to static IP. That way, they have same IPs forever.
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...
). 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...
You can recognize your miners by worker in your pool, visible on the same dashboard page you mentioned. Just open dashboard page, scroll down, there will be your pool address and worker name. Name them accordingly - youraccount.Apollo1 and youraccount.Apollo2 workers. Job done.
Sorry. I have not any worker name field in webgui. Sometimes I have that info at Username field (but not always). My pool address do not show any worker name in Dashboard.
Screenshot: https://www.dropbox.com/s/zl3y6qb2mb1htcx/noworkername.png?dl=0
How can i know my worker name?
I can see my workername with Litecoinpool AT USERNAME field, but not all pools works the same way.
EDIT: prohashing uses password field to put workername, and that field, of course, is not visible at Dashboard.
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...
). 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...
You can recognize your miners by worker in your pool, visible on the same dashboard page you mentioned. Just open dashboard page, scroll down, there will be your pool address and worker name. Name them accordingly - youraccount.Apollo1 and youraccount.Apollo2 workers. Job done.
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...
). 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...
Jump to: