I know it is only made for the raspberry pi 3 and 4, but on the installation page it says it can be installed on alternate hardware using the github. If it’s possible, how do you install it from there and what do you have to do to make it work on a raspberry pi 2? Thanks.
Hi Ben,
In the github repository, you can check the README where it points to a folder for custom installations, it’s available on the quick links.
1 Like
Thanks, I checked the Readme and I can see two options for commands that I would enter in the raspberry pi terminal, but I don’t understand what adjustments I would have to make and possible other things I would have to do to run the command on my raspberry pi 2 and have it successfully install Blueos (as entering the command how it is doesn’t work)
Hi Ben,
You just need to run the command in the README of the install folder, as pointed in my previous comment. Did you run it ? What was the output ?
Hello, I tried running that command and this is the output:
Checking if network and remote are available: https://raw.githubusercontent.com/bluerobotics/blueos-docker/master
Starting hardware configuration.
Detecting board type
Detected BCM28XX via device tree
Configuring BCM28XX board (Raspberry Pi zero, 1, 2, 3)..
- Enable I2C, SPI and UART.
dtparam=i2c_arm=on
dtparam=spi=on
dtoverlay=spi1-3cs
dtoverlay=uart1
- Set up kernel modules.
bcm2835-v4l2
i2c-bcm2835
i2c-dev
- Configure serial.
- Enable cgroup with memory and cpu
Checking for blocked wifi and bluetooth.
bash: line 93: rfkill: command not found
I then tried downloading install.sh onto the raspberry pi and removing the code related to rfkill, and running it and this was the output this time:
Checking if network and remote are available: https://raw.githubusercontent.com/bluerobotics/blueos-docker/master
Starting hardware configuration.
Detecting board type
Detected BCM28XX via device tree
Configuring BCM28XX board (Raspberry Pi zero, 1, 2, 3)..
- Enable I2C, SPI and UART.
dtparam=i2c_arm=on
dtparam=spi=on
dtoverlay=spi1-3cs
dtoverlay=uart1
- Set up kernel modules.
bcm2835-v4l2
i2c-bcm2835
i2c-dev
- Configure serial.
- Enable cgroup with memory and cpu
Checking for blocked wifi and bluetooth.
Checking for available space.
Checking for docker.
install.sh: line 109: docker: command not found
# Executing docker install script, commit: c2de0811708b6d9015ed1a2c80f02c9b70c8ce7b
+ sh -c apt-get update -qq >/dev/null
W: Failed to fetch http://raspberrypi.collabora.com/dists/wheezy/Release.gpg Could not resolve 'raspberrypi.collabora.com'
W: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/wheezy/main/binary-armhf/Packages 404 Not Found
W: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/wheezy/contrib/binary-armhf/Packages 404 Not Found
W: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/wheezy/non-free/binary-armhf/Packages 404 Not Found
W: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/wheezy/rpi/binary-armhf/Packages 404 Not Found
W: Some index files failed to download. They have been ignored, or old ones used instead.
+ sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
E: There are problems and -y was used without --force-yes
Failed to start docker, something may be wrong.
Hi Ben,
From the log it appears that the OS that you are running for the PI 2 is a bit old and the linux repository that is used to install packages does not exist anymore, how old is this image ? Did you use the raspberry installation tool ?
About the rfkill, the script was not created initially to work with systems that does not have this command, since it’s pretty common. I have just updated our install script to allow skipping this step if the command is not found. But It’ll only be available after our next stable release, that should happen next week.
Thanks for your help, I upgraded Raspberry Pi OS and ran the command again and it completed with no errors, but when I turn on the raspberry pi it still boots to raspberry pi OS instead of BlueOS. I tried booting the raspberry pi with an ethernet cable connected to a computer with blueos.local open, but it didn’t show up there. So what would I have to do now? Thanks.
Hi Ben,
First, on the raspberry, do a sudo docker ps to see if blueos-bootstrap and blueos-core are running.
If they are not running, run the command on the quick install guide as pointed in my previous comment.
If they are indeed running, you should be able to access BlueOS on your browser using the IP address of the raspberry. blueos.local will work if your OS has support do mDNS, you can check this simple guide before we have the official documentation live.
Thanks, it works now.