Posted this in announcement thread by mistake, deleted that post. sorry
Got my full package miner today and the whole thing looks awesome. From the packaging to the power supply and especially the miner itself. Plugged it in and connected to the IP address with no problems. The dashboards look great.
couple issues for me. First was the package had a packing slip that showed what I paid for it. Might not want to have that sitting on porch for too long.
Second, can a wireless usb dongle keyboard be plugged into device?
UPDATE, Miner ran fine for 30 minutes with all default settings and then stopped. choosing miner restart does nothing. So trying to stop node and its appears to try to stop for a minute, but then back to the dashboard. I know I should not just power off right?
After 50 minutes of uptime the fan is starting to howl. I'll check the screws first.
Taking a step back. I've powered off and disabled the miner while the node syncs. once the sync is complete I will try mining again
Topic: Official FutureBit Apollo BTC Software/Image and Support thread - page 123. (Read 48695 times)
Jstefanop, sorry if my post seemed like I was moaning. I’m not really. Its all to be expected with a first batch. The fit and finish of it all is superb and love the fact its all contained in one unit.
I must have a duff fan as no matter what I did it still wouldn’t be quiet
I’m waiting for a couple to turn up. No point paying postage from the US for such a small thing.
I’m just eager for the update to get the web UI sorted aswell as the shutdown button etc
I must have a duff fan as no matter what I did it still wouldn’t be quiet
I’m waiting for a couple to turn up. No point paying postage from the US for such a small thing. I’m just eager for the update to get the web UI sorted aswell as the shutdown button etc
DaveF, I was thinking exactly the same thing. Could be an issue with the existing fan. I’ve ordered a couple of different variants myself as I never got a reply from support after the initial query regarding the LED.
I suppose it all depends on the starting voltage of the fan. Most 12v fans have a starting voltage of 5v so if that was to dip lower then it would stop and struggle to start again. As you said 3.3 to 5v is a tighter margin so should hopefully be ok *crosses fingers*.
Its all trial and error at the moment. To be fair the heatsink is keeping it below 75c under moderate loads (when updating the node). So it may well be ok in my circumstances to run passively. But I just don’t like the idea of it.
I suppose it all depends on the starting voltage of the fan. Most 12v fans have a starting voltage of 5v so if that was to dip lower then it would stop and struggle to start again. As you said 3.3 to 5v is a tighter margin so should hopefully be ok *crosses fingers*.
Its all trial and error at the moment. To be fair the heatsink is keeping it below 75c under moderate loads (when updating the node). So it may well be ok in my circumstances to run passively. But I just don’t like the idea of it.
Initial it was supposed to ship passively cooled, but hashboard running + initial blockchain synced was causing it to overheat so we had to add the fan just for syncing. You can probably get away with disconnecting the fan (its the black and red wire on the bottom of the unit) if it has already synced, just make sure temps dont go over 85c.
Super pissed at the supplier of these fans, they are complete garbage...just send us an email and well send you a replacement. BTW for some units the fans are fine, just the two screws that hold it down have become loose making the vibration noise. Tightening the screws should fix this.
DaveF, I was thinking exactly the same thing. Could be an issue with the existing fan. I’ve ordered a couple of different variants myself as I never got a reply from support after the initial query regarding the LED.
I suppose it all depends on the starting voltage of the fan. Most 12v fans have a starting voltage of 5v so if that was to dip lower then it would stop and struggle to start again. As you said 3.3 to 5v is a tighter margin so should hopefully be ok *crosses fingers*.
Its all trial and error at the moment. To be fair the heatsink is keeping it below 75c under moderate loads (when updating the node). So it may well be ok in my circumstances to run passively. But I just don’t like the idea of it.
I suppose it all depends on the starting voltage of the fan. Most 12v fans have a starting voltage of 5v so if that was to dip lower then it would stop and struggle to start again. As you said 3.3 to 5v is a tighter margin so should hopefully be ok *crosses fingers*.
Its all trial and error at the moment. To be fair the heatsink is keeping it below 75c under moderate loads (when updating the node). So it may well be ok in my circumstances to run passively. But I just don’t like the idea of it.
Can the CPU fan run from any of the 5v/GND GPIO pins? Or does it have to be run through the proprietary connector you guys have made?
CPU Fan Connector is attached to the 3.3v power, if you connect it to the 5v pins it will spin nearly twice as fast and be super loud.
I know in the olden days of PC cooling (go back to the mid 90s) under-volting a fan could cause issues. Back then people tried to run 12V fans off the 5V rail to reduce noise since for the most part you did not need the airflow that you need in todays PCs. But, it caused a lot of them not to spin at times. Once they started moving, even with a flick of a finger they kept spinning. I know there is a big difference between a case fan and the little one on the CPU and 5 to 12 is a much larger gap then 3.3 to 5 but could that be causing some of the early death issues? I actually have one coming in from you to replace mine that died.
-Dave
Hi
Any news of the 32 Bits Linux version for my Raspberry?
Regards
Any news of the 32 Bits Linux version for my Raspberry?
Regards
Thanks.
No source code will be available?
If not, then please make sure Raspberry Pi zero and 2 is available.
Some peeple use Raspbian, some Debian or Manjaro on Pis and so on. I don't know how is that all compatible with each other.
Debian uses different architecture on Pi zero than Raspbian as far as I understand.
No source code will be available?
If not, then please make sure Raspberry Pi zero and 2 is available.
Some peeple use Raspbian, some Debian or Manjaro on Pis and so on. I don't know how is that all compatible with each other.
Debian uses different architecture on Pi zero than Raspbian as far as I understand.
Came home from work today, and the miner had timed itself out. No big deal because I Restarted my miner and it was up and running again no issues. Only thing is now it is starting to make an awful sound every couple seconds. I have a feeling this noise is coming from the fan since it is a moving part. has anyone else run into this issue yet? If so what is the remedy. Should I safely stop the unit from mining and safely shut down the node till i find the culprit or is it safe? Operating temperature is fine. Everything looks great besides this weird sound. have been running in ECO mode since the unit came online. Haven't messed with any settings. Maybe something is coming loose or starting to?? Any help would be greatly appreciated!
Yes others have the same issue. It's the CPU fan on the SBC, temps will be fine it will just be noisy. I've temporarily unplugged mine until support sends me another one
Came home from work today, and the miner had timed itself out. No big deal because I Restarted my miner and it was up and running again no issues. Only thing is now it is starting to make an awful sound every couple seconds. I have a feeling this noise is coming from the fan since it is a moving part. has anyone else run into this issue yet? If so what is the remedy. Should I safely stop the unit from mining and safely shut down the node till i find the culprit or is it safe? Operating temperature is fine. Everything looks great besides this weird sound. have been running in ECO mode since the unit came online. Haven't messed with any settings. Maybe something is coming loose or starting to?? Any help would be greatly appreciated!
Can the CPU fan run from any of the 5v/GND GPIO pins? Or does it have to be run through the proprietary connector you guys have made?
CPU Fan Connector is attached to the 3.3v power, if you connect it to the 5v pins it will spin nearly twice as fast and be super loud.
Sweet good to know. I'll hook it upto a spare 3.3v & GND if the replacement I've bought arrives with a different connector.
jstefanop, any news on standalone apollo miner? Still waiting for any support for older Raspberry Pi's. https://github.com/jstefanop/Apollo-Miner-Binaries/releases/ shows nothing new since the release, unfortunately. Thanks.
Need to get the critical fixes out for our main unit, and then will focus on this.
Thanks. Please keep up the good work. Ubuntu system updates compatibility for full unit are more important I can imagine, as well as other things. We don't want to run outdated systems in our networks.
Will be waiting for new standalone release
Can the CPU fan run from any of the 5v/GND GPIO pins? Or does it have to be run through the proprietary connector you guys have made?
CPU Fan Connector is attached to the 3.3v power, if you connect it to the 5v pins it will spin nearly twice as fast and be super loud.
jstefanop, any news on standalone apollo miner? Still waiting for any support for older Raspberry Pi's. https://github.com/jstefanop/Apollo-Miner-Binaries/releases/ shows nothing new since the release, unfortunately. Thanks.
Need to get the critical fixes out for our main unit, and then will focus on this.
jstefanop, any news on standalone apollo miner? Still waiting for any support for older Raspberry Pi's. https://github.com/jstefanop/Apollo-Miner-Binaries/releases/ shows nothing new since the release, unfortunately. Thanks.
Seems like the Bitcoin block or index are a corrupt and not allowing my Apollo BTC full node to keep running past this block.
The entries from the log are below:
2021-06-22T22:28:27Z LevelDB read failure: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z You can use -debug=leveldb to get more complete diagnostic messages
2021-06-22T22:28:27Z Error: Error reading from database, shutting down.
2021-06-22T22:28:27Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
I have rerun the bitcoind program with the -debug option and I get the same log entries.
I was looking thru the -help contents and it seems -reindex might be the answer, but I wanted to check with the group here to see if there was a better option.
The entries from the log are below:
2021-06-22T22:28:27Z LevelDB read failure: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z You can use -debug=leveldb to get more complete diagnostic messages
2021-06-22T22:28:27Z Error: Error reading from database, shutting down.
2021-06-22T22:28:27Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
I have rerun the bitcoind program with the -debug option and I get the same log entries.
I was looking thru the -help contents and it seems -reindex might be the answer, but I wanted to check with the group here to see if there was a better option.
Delete that file. It will be recreated. Bitcoin Core will reindex everything itself when missing file is discovered.
Seems like the Bitcoin block or index are a corrupt and not allowing my Apollo BTC full node to keep running past this block.
The entries from the log are below:
2021-06-22T22:28:27Z LevelDB read failure: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z You can use -debug=leveldb to get more complete diagnostic messages
2021-06-22T22:28:27Z Error: Error reading from database, shutting down.
2021-06-22T22:28:27Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
I have rerun the bitcoind program with the -debug option and I get the same log entries.
I was looking thru the -help contents and it seems -reindex might be the answer, but I wanted to check with the group here to see if there was a better option.
The entries from the log are below:
2021-06-22T22:28:27Z LevelDB read failure: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
2021-06-22T22:28:27Z You can use -debug=leveldb to get more complete diagnostic messages
2021-06-22T22:28:27Z Error: Error reading from database, shutting down.
2021-06-22T22:28:27Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/399540.ldb
I have rerun the bitcoind program with the -debug option and I get the same log entries.
I was looking thru the -help contents and it seems -reindex might be the answer, but I wanted to check with the group here to see if there was a better option.
...
Yes, this was the original plan, unfortunately to containerize the app was too much work to make it in time for release. This will also make it easy to install the web app on any other system so the standard units can have a nice UI as well.
I would highly suggest against this.Yes, this was the original plan, unfortunately to containerize the app was too much work to make it in time for release. This will also make it easy to install the web app on any other system so the standard units can have a nice UI as well.
'Containerized' apps require the producer of the container to regularly update the container whenever a problem is found with any software included in the container, and thus also require each person running the container to update their container when this happens.
The long term result of this is: most people running old, out of date software in their container, usually with various known security issues.
If instead the OS (like ubuntu) is allowed to update the 'system', this solves that issue for hardware that no one bothers to check.
The basic issue is that this device is expected to be directly connected to the internet, so a design leading to commonly unpatched security issues is problematic.
Can the CPU fan run from any of the 5v/GND GPIO pins? Or does it have to be run through the proprietary connector you guys have made?
Hey guys make sure if your connected to the system with the monitor you DO NOT do any system level updates (ie ubuntu asking you to update the kernel etc). Even though we tried to keep the system and 'app" as separate as possible the full node system is still really an embedded system with lots of system level tweaks to make it work. If you update the system lots of these will be will be wiped and youll be left with a bricked system until you reflash the SD card.
Mainly a suggestion for a future release:Package the "app" as a container (Docker for example) and map the necessary i/o connections directly to it. That way all the dependencies and changes needed by your own implementation can stay as you want without a risk of a system update making modifications and on the Ubuntu side the system updates and package installs (which may also pull updates as dependencies) can be used without having to worry of something getting unintentionally modified. That could also make reseting the setup back to defaults easier since it would just be a matter of discarding the container and starting a clean one.
Yes, this was the original plan, unfortunately to containerize the app was too much work to make it in time for release. This will also make it easy to install the web app on any other system so the standard units can have a nice UI as well.
Hey guys make sure if your connected to the system with the monitor you DO NOT do any system level updates (ie ubuntu asking you to update the kernel etc). Even though we tried to keep the system and 'app" as separate as possible the full node system is still really an embedded system with lots of system level tweaks to make it work. If you update the system lots of these will be will be wiped and youll be left with a bricked system until you reflash the SD card.
Mainly a suggestion for a future release:Package the "app" as a container (Docker for example) and map the necessary i/o connections directly to it. That way all the dependencies and changes needed by your own implementation can stay as you want without a risk of a system update making modifications and on the Ubuntu side the system updates and package installs (which may also pull updates as dependencies) can be used without having to worry of something getting unintentionally modified. That could also make reseting the setup back to defaults easier since it would just be a matter of discarding the container and starting a clean one.
Jump to: