update installation scripts #284
Conversation
jaxxzer
force-pushed
the
setup-clean
branch
2 times, most recently
from
5b2e98c
to
62d0373
Compare
jaxxzer
force-pushed
the
setup-clean
branch
2 times, most recently
from
384be42
to
115530c
Compare
| screen \ | ||
| npm \ | ||
| nodejs \ | ||
| gstreamer1.0-tools \ |
There was a problem hiding this comment.
Maybe we should specify the versions like this:
sudo apt-get install gstreamer1.0-tools=1.4.4-2
|
|
||
| # append 'enable_uart=1' line to /boot/config.txt | ||
| run_step echo "enable_uart=1" | sudo tee -a /boot/config.txt | ||
|
|
There was a problem hiding this comment.
remember to change the password!
|
create a log file |
|
|
jaxxzer
force-pushed
the
setup-clean
branch
2 times, most recently
from
705503c
to
a168c31
Compare
jaxxzer
changed the title
|
Failing in 3B+ latest Raspbian buster |
|
I did run it here, but the webpage is not available: I rebooted after finishing the commands in your previous comment. |
|
@patrickelectric can you check ~/.webui.log? |
|
this package is well outdated and beyond support installation is broken on updated node version 10 in the past we were using version 5
this was needed in the past to install gstreamer > 1.8 with proper v4l2src support this is now available from the package manager
this is far out of date
this is required to correctly enumerate /dev/autopilot when a pixhawk is plugged
|
Hey guys, let me know if you need help testing. I will set up some pi's on the bench here. |
|
Hi @chrisfraser be free to run the commands in the PR body to test it :) |
|
double check permissions on config files under ~ |
|
@jaxxzer does your install script assume the RPi system
I'll continue debugging this for my use tomorrow, but info on the intent would be useful so I don't make a heap of changes that could be easily fixed with a single line or two run/changed somewhere else. |
|
Turns out the |
|
If you are interested I could look into implementing a CI which builds an image based on raspian (pi-gen) with the install scripts installed and deploys it to a given emulated raspberry pi version (f.i. 3B+). This is done by emulating the different raspberry pi's with Docker+QEMU, then running some test to check if the image works on the given hardware. Moreover, the same Docker+QEMU emulation can be used to develop images much faster, as on the physical raspberrypi itself as normal laptops have much more processing power. In case you use this process already to build images in house, it would be great to share or point to where to find, as it makes customizing released images much faster. By the way, I have refurbished a ROV with you software, but I am not involved with ROV's anymore. This would be a way for me to give back to your great project as it was nice being able to use it. |
|
The issues @Eliot-Insight had were caused by a PyPI setup issue in I've avoided that actual bug by specifying the relevant library version, and rebased the rest of these changes onto companion 0.0.29 here. It's very likely that's the last update that will occur for this side of things before an upcoming major release that actually has official support for the more recent Raspberry Pi boards. |
|
Use BlueOS :-) |
Companion can be installed on a vanilla raspbian image like this:
This is working on pi 3 and pi 4.
We've lost webterminal support. I recommend using chrome terminal extension to replace the functionality (make ssh easy on windows).
TODO fetch br master branch + tags and checkout stable