I am currently attempting to manually install BlueOS onto a Raspberry Pi 4 with Raspberry Pi OS Bullseye; however, I am having some issues opening BlueOS after running the installation script. I do not observe any errors during execution of the script (though I have attached the output of the script for confirmation). Here are some of the things that I have tried and looked into:
When I later attempt to establish a connection with the Raspberry Pi after running the installation script, I am unable to recognize the BlueOS IP address (192.168.2.2).
Interestingly, I am able to identify the IP address of the DVL mounted onto my system.
I did some inspection of the BlueOS Docker images, and noticed that the blueos-core image frequently restarts (every minute or less), though I’m not convinced that this is causing the problem.
As a debugging step, I configured the /etc/dhcpcd.conf file on the Pi to assign 192.168.2.2 as the static IP address with the IP address 192.168.2.1 as the server. After applying these settings, I am able to SSH into the Pi using the assigned static IP address, but am still unable to open the BlueOS interface.
I am considering pulling an older version to see if the current version is broken, but wanted to check first to see if there were some installation/setup steps that I might have missed.
EDIT: I have tried both master and version 1.1.0-beta.26 to no avail.
After giving the Pi a bit longer to configure using version 1.1.0-beta.26, I was able to establish a connection. It seems like this is an issue with master at the moment.
Firstly, I’m glad you were able to sort out your issue, and sorry to hear there were problems when you first started out. Thanks for the detailed breakdown of what you tried and what wasn’t working the way you expected - that’s definitely helpful
The core image is not expected to restart when you haven’t explicitly told it to do so (e.g. with a restart command or when updating versions), so I’d guess it was failing to start up correctly (hence no interface) and was being restarted automatically by BlueOS-bootstrap.
I’m not aware of anything missing from the install script (it should perform all the necessary setup as long as it has an internet connection), and your installation output file shows the process at least thought it was successful.
Given you’ve managed to get it working on a versioned release, my main guess is that you happened to install master when it was in a broken state, which may have just been unlucky timing. That said, I’m curious why you opted to install 1.1.0-beta.26 when 1.1.0-beta.27 was released two weeks ago - were you not aware that that’s available, or were you testing this a while ago?
If you were doing your initial master install attempts around the time beta.26 was released then that may explain the failed startups, because both beta.24 and beta.25 had some issues with repeated rebooting. If not then we may need to look into this further, in which case it would be helpful to know which RAM variant of the RPi4 you’re using, and which Bullseye version you’re running so we can try to replicate your results and find and fix any installation issues
… I’m curious why you opted to install 1.1.0-beta.26 when 1.1.0-beta.27 was released two weeks ago - were you not aware that that’s available, or were you testing this a while ago?
I tried both master and 1.1.0-beta.27 and observed the issue in both versions. 1.1.0-beta.26 was the first version that I was able to successfully install and run. I believe that the issue is being caused by the repeated rebooting in both versions. I will note that I did attempt to install the 1.1.0-beta.27 core image from 1.1.0-beta.26 and the issue reappeared.
… it would be helpful to know which RAM variant of the RPi4 you’re using, and which Bullseye version you’re running
I attempted installation of both versions on the 2GB and 8GB versions and the error persisted across versions. I did not try checking the RAM usage during my debugging, unfortunately. I am running the latest stable version of Raspberry Pi OS Lite (the version that you get when running the Pi Imager).
To be sure, since you are installing BlueOS from the install script, did you change your raspberry pi password ? If so, the system will not work as expected, the passwd should be raspberry.
That certainly could have been the problem I have updated the password since then to the expected password, but I have not yet tried to reinstall 1.1.0-beta.27. I’ll give that another shot at a future date, and provide some feedback regarding the process. Thank you for the support!
Beta.28 should start and run fine if the user changed the default password, an alert will show up on BlueOS UI.
In parallel, we are working to add support to custom password, but no guarantees on that.
I have updated the password since then to the expected password, but I have not yet tried to reinstall