potentabit
Newbie
 Offline
Activity: 14
Merit: 0
|
 |
April 16, 2024, 12:22:06 PM |
|
EDIT: No luck with asicboost..
Make sure you have the latest update installed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, which will follow the rules of the network no matter what miners do. Even if every miner decided to create 1000 bitcoins per block, full nodes would stick to the rules and reject those blocks.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
azereki
Newbie
Offline
Activity: 6
Merit: 0
|
|
April 17, 2024, 12:46:30 AM
Last edit: April 17, 2024, 01:04:16 AM by azereki |
|
Want to get this tested here by a few of you since we dont have a lot of MCU1 devices left to test.
Below feedback would be appreciated:
OS detects internal board and starts up fine
OS detects and starts up external USB Standard units (both Apollo BTC or if any MCU1 owners have an Apollo II standard yet)
Was able to flash an Apollo BTC Full MCU1 and plug in via USB to Apollo 2 Full, it was detected and started contributing hashing. It appears to be a little finnicky if you are manipulating the web dashboard for both units simultaneously. For example, it was initially showing both units and hashboards on the Apollo 2 miner page. After restarting the Apollo 1, it seems to be operating independently with no apparent communication with the the Apollo 2. Both are mining and contributing hashrate to the pool. Also doesn't appear that the Apollo I node wants to start up, but this may be by design when connected via USB? I never updated the SSD on it, so ostensibly it couldn't fit the blockchain right now anyway. Testing further, seems Apollo II device and 2.0.4 OS aren't connecting to Apollo I standard units even after several minutes, maybe just a USB issue? |
|
|
|
|
jstefanop (OP)
Legendary
Offline
Activity: 2093
Merit: 1396
|
|
April 18, 2024, 04:33:59 PM |
|
Want to get this tested here by a few of you since we dont have a lot of MCU1 devices left to test.
Below feedback would be appreciated:
OS detects internal board and starts up fine
OS detects and starts up external USB Standard units (both Apollo BTC or if any MCU1 owners have an Apollo II standard yet)
Was able to flash an Apollo BTC Full MCU1 and plug in via USB to Apollo 2 Full, it was detected and started contributing hashing. It appears to be a little finnicky if you are manipulating the web dashboard for both units simultaneously. For example, it was initially showing both units and hashboards on the Apollo 2 miner page. After restarting the Apollo 1, it seems to be operating independently with no apparent communication with the the Apollo 2. Both are mining and contributing hashrate to the pool. Also doesn't appear that the Apollo I node wants to start up, but this may be by design when connected via USB? I never updated the SSD on it, so ostensibly it couldn't fit the blockchain right now anyway. Testing further, seems Apollo II device and 2.0.4 OS aren't connecting to Apollo I standard units even after several minutes, maybe just a USB issue? Yea UI is only designed to register the internal SSD drive node. When you restart the miner you should see the USB standard units start flashing their front LEDs, if they dont then that means the system is not seeing them. Try a different USB port/USB hub. USB hubs seem to fix most USB issues on this controller. |
|
|
|
Bamieater
Newbie
Offline
Activity: 2
Merit: 0
|
|
April 19, 2024, 11:01:54 AM |
|
My miner is crashing, and restarting every 10-20 minutes. To my feeling it's happening the moment new blocks are mined. The node falls back a couple of hundred blocks after the restart, i.e. the current block was 838879 and the node would start syncing at 838663 again. MCU1 board. This behaviour was also happening before, and I was hoping the upgrade would fix this. This sounds like a corrupted SSD drive. You might need to reformat the drive and start syncing again. Can also try a re-indexing the node before you reformat the drive. I've reformatted the SSD drive, and started syncing again. Once the node was synced, I enabled mining again on ECO mode. I could observe on the miner uptime that restarts were still happening. After a bit more than a day of mining, the whole web interface became unreachable. Anything else I can troubleshoot? |
|
|
|
|
|
Sledge0001
|
|
April 19, 2024, 03:21:28 PM |
|
My miner is crashing, and restarting every 10-20 minutes. To my feeling it's happening the moment new blocks are mined. The node falls back a couple of hundred blocks after the restart, i.e. the current block was 838879 and the node would start syncing at 838663 again. MCU1 board. This behaviour was also happening before, and I was hoping the upgrade would fix this. This sounds like a corrupted SSD drive. You might need to reformat the drive and start syncing again. Can also try a re-indexing the node before you reformat the drive. I've reformatted the SSD drive, and started syncing again. Once the node was synced, I enabled mining again on ECO mode. I could observe on the miner uptime that restarts were still happening. After a bit more than a day of mining, the whole web interface became unreachable. Anything else I can troubleshoot? Check to make sure the CPU fan is still working on the MCU unit. It may be gunked up or dead. That would cause the MCU to overheat and crap out on you. |
|
|
|
|
|
|
jstefanop (OP)
Legendary
Offline
Activity: 2093
Merit: 1396
|
|
April 20, 2024, 01:16:02 AM |
|
Getting to those next week, fixing some last UI bugs for now and still working overtime to get as many units as we can out to you guys next week |
|
|
|
jstefanop (OP)
Legendary
Offline
Activity: 2093
Merit: 1396
|
|
April 20, 2024, 02:00:45 AM |
|
FYI Main support page for Apollo II/BTC is up that has consolidated a lot of the info found here in an easy to read page with relevant links etc https://www.futurebit.io/apollo-btc-supportWe are also working on a revamped support site and knowledge base that is long overdue...these forums have served FutureBit well for nearly a decade but after 100+ pages and 2k+ posts I think its time to retire  |
|
|
|
WeAreAllSatNak
Newbie
Offline
Activity: 2
Merit: 0
|
|
April 20, 2024, 02:36:59 PM |
|
Getting to those next week, fixing some last UI bugs for now and still working overtime to get as many units as we can out to you guys next week Thank you for the quick update! I've got my standard unit Apollo 2, just waiting for the binaries so I can run it via external PC. |
|
|
|
|
potentabit
Newbie
Offline
Activity: 14
Merit: 0
|
|
April 20, 2024, 04:14:02 PM |
|
|
|
|
|
|
Omarko
Member
Offline
Activity: 72
Merit: 10
|
|
April 21, 2024, 09:09:41 PM |
|
hi all, I have Apollo II full Node on the way hopefully in May, cant wait!
question - can I pre-download the bitcoin ledger in advance and then copy it onto the SSD once I get the Apollo II? Just want to save time and manage bandwidth as dont want the node downloading at full rate when I get it clogging up internet for few days as I use it for work etc so wanted to set a controlled download now eg using Bitcoin Core and let it run for a week or two on limited bandwidth. How can I then transfer it onto the Apollo II nvme SSD?
thanks in advance!
|
|
|
|
|
|
heslo
|
|
April 22, 2024, 05:04:53 AM
Last edit: April 22, 2024, 06:34:03 AM by heslo |
|
Those with an Apollo2 mining to their own node.... anyone having issues with stats not showing up? My mining page shows shares are being accepted but when I go to the solo mining page it just says "Waiting for first share"
Running the v2.0.4 beta if that helps. I'm thinking I might have to do an SD reflash? I did an OTA update from 2.0.3 and am wondering if that's caused something to break?
EDIT: Reflashed the SD and everything works as expected again. I assume I was right and something didn't work 100% in the OTA upgrade.
I'll keep this here as an FYI for anyone else that might have this issue
|
|
|
|
|
dking1111
Newbie
Offline
Activity: 1
Merit: 0
|
|
April 23, 2024, 01:53:23 AM |
|
I just got my Apollo II USB today. I've been running an Apollo I via USB. I plugged in my Apollo II updated the port (linux sh script) and it keeps spitting out the following error:
MsPacket: version mismatch: act 0xd167 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 67 d1 21 00 a3 00 ... 00 00 00 00 00 00 00 00
I don't get any shares on my pool
|
|
|
|
|
BlazeB
Newbie
Offline
Activity: 7
Merit: 0
|
|
April 24, 2024, 03:05:42 PM |
|
Those with an Apollo2 mining to their own node.... anyone having issues with stats not showing up? My mining page shows shares are being accepted but when I go to the solo mining page it just says "Waiting for first share"
Running the v2.0.4 beta if that helps. I'm thinking I might have to do an SD reflash? I did an OTA update from 2.0.3 and am wondering if that's caused something to break?
EDIT: Reflashed the SD and everything works as expected again. I assume I was right and something didn't work 100% in the OTA upgrade.
I'll keep this here as an FYI for anyone else that might have this issue
This is a bug. I too had the same issue and after contacting support they said, " if you are mining to solo ckpool or ocean pool then switch to solo mining you need to update the BTC address field (delete the last letter and re-enter for example) for it to properly update the local solo pool URL." |
|
|
|
|
|
heslo
|
|
April 24, 2024, 10:36:04 PM |
|
Those with an Apollo2 mining to their own node.... anyone having issues with stats not showing up? My mining page shows shares are being accepted but when I go to the solo mining page it just says "Waiting for first share"
Running the v2.0.4 beta if that helps. I'm thinking I might have to do an SD reflash? I did an OTA update from 2.0.3 and am wondering if that's caused something to break?
EDIT: Reflashed the SD and everything works as expected again. I assume I was right and something didn't work 100% in the OTA upgrade.
I'll keep this here as an FYI for anyone else that might have this issue
This is a bug. I too had the same issue and after contacting support they said, " if you are mining to solo ckpool or ocean pool then switch to solo mining you need to update the BTC address field (delete the last letter and re-enter for example) for it to properly update the local solo pool URL." Ah, that makes sense cos I was mining to ckpool before my own node as I was waiting for it to sync. Good to know! Definitely a fringe case but hopefully now they know about it they'll fix it |
|
|
|
|
jstefanop (OP)
Legendary
Offline
Activity: 2093
Merit: 1396
|
|
April 25, 2024, 12:09:48 AM |
|
I just got my Apollo II USB today. I've been running an Apollo I via USB. I plugged in my Apollo II updated the port (linux sh script) and it keeps spitting out the following error:
MsPacket: version mismatch: act 0xd167 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 67 d1 21 00 a3 00 ... 00 00 00 00 00 00 00 00
I don't get any shares on my pool
All Apollo BTC units need to upgrade to Apollo OS 2 for Apollo II support. See details/instructions/links on our support page: https://www.futurebit.io/apollo-btc-support |
|
|
|
sorensenes
Newbie
Offline
Activity: 4
Merit: 0
|
|
April 27, 2024, 01:33:45 AM |
|
I just got an Apollo II and it will connect over ethernet, but when I try to connect to my wifi it keeps giving me the same error - 'secrets were required but not provided'. I have never seen an error like that before and am not sure what to do. I know I've put in the right password for the wifi. Any insight from anyone on how to navigate this error?
|
|
|
|
|
cipherbreak
Newbie
Offline
Activity: 3
Merit: 0
|
 |
April 27, 2024, 10:55:07 PM
Last edit: April 28, 2024, 09:58:33 PM by cipherbreak |
|
Hello!
I just received my Apollo 2 full node, and the basics are working great so far (I also have my Apollo BTC hooked up to it via USB, and they're both hashing away while the blockchain is still doing its initial sync). I hope there are more features to control various things soon, like the power/fan/voltage settings for each miner individually and such!
I'd also like to see an easy way to setup remote access to Ubuntu via the web GUI, thru standard RDP apps like Windows RDP... because I have had no issues getting in via SSH, but the Apollo 2 full node doesn't seem to work with ANY of my standard 4k monitors to access the Ubuntu GUI (no signal), and enabling xRDP or GnomeRDP through SSH terminal, using the usual methods, has not worked for me so far - I get a login screen when I RDP in, which loads and works properly and I can seemingly successfully login to, followed by a blank greenish background screen where I can only see my mouse pointer and not do anything else. This blank/green screen is a common issue with Ubuntu 20.04 and 22.04 and xRDP, but none of the usual methods of solving it work for me so far, and I've tried every solution I can find a thread about or that Bing Copilot can possibly suggest... editing the xRDP.ini file in various ways (adding an [xrdp1] section with various settings like -1 for the port), and modifying /home/$USER/.xsessionrc with some GNOME/Ubuntu related lines. No luck with that stuff. I can seemingly connect and authenticate just fine, but something about the Apollo 2's standard 22.04 image is causing rendering issues or something over RDP specifically that can't seem to be fixed in the usual ways.
Anyone have any suggestion on a good easy way to get RDP from Windows working into the Apollo 2, from SSH commands only because I can't access the GUI (Ubuntu or Gnome, the full desktop GUI) in any fashion yet?
Thanks!
|
|
|
|
|
johnstewart
Newbie
Offline
Activity: 23
Merit: 1
|
|
April 29, 2024, 12:00:21 PM |
|
Hello,
Is that possible to create an highdiff port on the solo pool ? ( i lurked on the ckpool github doesn't find it )
|
|
|
|
|
jstefanop (OP)
Legendary
Offline
Activity: 2093
Merit: 1396
|
|
April 29, 2024, 03:27:55 PM |
|
Hello,
Is that possible to create an highdiff port on the solo pool ? ( i lurked on the ckpool github doesn't find it )
We will add options to solo UI for this in future updates, but for now you would need to edit the ckpool.conf file (opt/apolloapi/backend/ckpool/ckpool.conf) and add the following line to change the start diff "startdiff": 8000, |
|
|
|
|
