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!

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?

Hello,

Is that possible to create an highdiff port on the solo pool ? ( i lurked on the ckpool github doesn't find it )

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

Correct, you just won't be able to solo mine using the device. You can solo mine on a pool like ckpool though or just mine normally through any pool you wish

Where should we check for Apollo 2 mining binaries? I don't see anything new here: https://github.com/jstefanop/Apollo-Miner-Binaries

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?

Quantum Random Number Generators should be used in mining hardware for truly random nonce generation. QRNG Chips are being sold by ID Quantique (although I have no idea about the cost) - Why are these chips not widespread in all miner hardware by now? Perhaps the cost? Technological immaturity? I know there are some arguments of quantum resistant technologies which seemingly make QRNG less meaningful, but those technologies are not certain to work for future generations of quantum computers. Nonce's optimally should be generated by true sources of randomness.

I didn't get a satscard...

anyone know what to do with the satscards? I'm in UK and haven't come across these before. 

OK, I see and agree, they must be cross labeled or not reading assigned values. Also agree that some pools need separate Id's depending on how data is sent/received. I have a few GPU rigs on NiceHash and all cards on each rig have their own ID's

Hopefully Monday's update will address some of these issues as we are still in a Beta version.

Hello all, any suggestions as to what the best way is to connect Gen I full Node with the New Apollo II?
Thanks for your help!

So the Apollo BTC (MCU1) recognized the Hashboard  (hashboard #0 Standard unit).

It started to hash and I started seeing activity on Braiins, although lower than 6+ TH/s
After 5-10 min, I got this error in the dashboard saying the Hashboard #0 is not Active

What is weird is it shows the standard unit is hashing but the Apollo BTC is not, what I see on the pool it looks like the Apollo BTC is actually mining at 2TH/s and the Standard unit is not.

https://gyazo.com/dfe922d3b8b19ac8d7cdd60d85f8ae30

https://gyazo.com/fb9a2fa0ee93a929906bc6cdf5d63167



EDIT: After restarting the miner and the hashboard being active again, I noticed in the "show all data>pools" tab that the hashboard was showing 0 (By the way there is an issue with the labelling, it inverts the 2 boards Apollo BTC should be #0) so I thought maybe it's an issue with miningrigrentals.com so I switched to Braiins pool directly.
Restarted and now the standard unit showed some activity in the pools tab. Although after a few minutes, it dropped again and saying inactive.

https://gyazo.com/e4791f6cf7605178d248f979a9bdc87e

Again, the reporting is wrong, the Apollo BTC is actually mining at 2TH/s and the standard unit is inactive, it doesn't show 0 on the screenshot but the current overall hashrate in the background only shows 2Th/s

Hello so I flashed the new os 2 on my Apollo mcu1 seems to work. No hashrate from my dashboard like I said on support by email.

I have a question is that possible to point other miners on my own solo node for the solo mining or it’s exclusive for the Apollo ?

MCU1 full node with Apollo 2 Standard attached to USB.
Using  v2.0.4-beta

Noticed that hash rate to NiceHash is only a fraction of actual mining.
When looking at the stats only shows one of the 2 miners (Apollo2) reporting data at no more than fraction (1.2 TH) of actual rate (5.8TH).
Apollo BTC is showing 1.9 TH and 0TH on NiceHash account.

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.

Apollo 1 wifi has been bullet proof so does the Apollo 2 use an inferior interface? I'm using the 2 at the same distance as I've always used the 1.  Nothing seems to be working to resolve the wifi conenction issue.  Hard wiring seems the only solution which kind of makes the whole concept a bit pointless. 

and now after an hour's use, the other unit has dropped off the wifi and won't reconnect.  Brilliant.  Never had any issues like this with the Apollo 1 units.  Right now I have 2 expensive bricks taking up space in my office