-
Notifications
You must be signed in to change notification settings - Fork 22
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
267 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,267 @@ | ||
# Raspberry Pi | ||
|
||
Although we are currently not providing installation images for Raspberry Pi, we are investigating whether doing so would be feasible and beneficial. | ||
|
||
__NOTE:__ This page is intended for technically advanced users and developers, not for end users. This page is work in progress. Instructions are brief and assume prior knowledge with the subject | ||
|
||
This page describes how to run the main components of helloSystem (referred to collectively as helloDesktop) on Raspberry Pi 3 and Raspberry Pi 4 devices, starting with the official FreeBSD 13 image that does not even contain Xorg. | ||
|
||
It describes how to build and set up the main components of helloSystem by hand, so this is a good walkthrough in case you are interested in bringing up the helloDesktop on other systems as well. | ||
|
||
If there is enough interest, we might eventually provide readymade helloSystem images for Raspberry Pi in the future. This depends on how usable helloSystem will be on the Raspberry Pi (e.g., whether we can get decent graphics performance). | ||
|
||
## Prerequisites | ||
|
||
* Raspberry Pi 3 Model B or B+, Raspberry Pi 4 Model B, or Raspberry Pi 400 | ||
* Suitable power supply | ||
* Class-1 or faster microSD card with at least 8 GB of memory | ||
* HDMI display | ||
* Keyboard and mouse (we recommend the official Raspberry Pi keyboard since helloSystem can automatically detect its language) | ||
* Ethernet (WLAN is not yet covered on this page) | ||
|
||
## Preparing | ||
|
||
* Install the official FreeBSD 13 image (not FreeBSD 14) to a microSD card | ||
* Copy this file to the microSD card you are running the Raspberry Pi from. You will need it because you will not have an internet browser at hand | ||
* Edit `config.txt` in the `MSDOSBOOT` partition to contain the correct resolution for your screen. Apparently the screen resolution is not autodetected on the Raspberry Pi? | ||
|
||
``` | ||
hdmi_safe=0 | ||
framebuffer_width=1920 | ||
framebuffer_height=1080 | ||
disable_overscan=1 | ||
``` | ||
|
||
__NOTE:__ Please let us know if you know how to get screen resolution autodetection working on FreeBSD with Raspberry Pi | ||
|
||
## Booting into the system | ||
|
||
We will be doing all subsequent steps on the Raspberry Pi system itself since we are assuming you don't have any other 64-bit ARM (`aarch64`) machines at hand. | ||
|
||
* Insert the microSD card into the Raspberry Pi | ||
* Attach keyboard and mouse (we recommend the official Raspberry Pi keyboard since helloSystem can automatically detect its language) | ||
* Attach the display (on the Raspberry Pi 4, the display needs to be attached to the HDMI port next to the USB type C power port) | ||
* Attach Ethernet | ||
* Power on the Raspberry Pi | ||
* After some time you should land in a login screen | ||
* Log in with `root`, password `root` | ||
* Install some basic software with `pkg install -y xorg xterm nano openbox fluxbox` | ||
|
||
__NOTE:__ `fluxbox` is not strictly needed and can be removed later on, but it gives us a graphical desktop session while we are working on installing helloDesktop | ||
|
||
## Starting a graphical session | ||
|
||
Start Xorg with | ||
|
||
``` | ||
echo startfluxbox > ~/.xinitrc | ||
startx | ||
``` | ||
|
||
Doing it like this is the easiest way since the display `DISPLAY` environment variable and other things will be set automatically. | ||
|
||
## Compiling and installing helloDesktop core components | ||
|
||
### launch | ||
|
||
The `launch` command is central to helloSystem and is used to launch applications throughout the system. | ||
|
||
``` | ||
git clone https://github.com/helloSystem/launch | ||
cd launch/ | ||
mkdir build | ||
cd build/ | ||
cmake .. | ||
make -j4 | ||
./launch | ||
make install | ||
cd ../../ | ||
``` | ||
|
||
### Menu | ||
|
||
``` | ||
pkg install -y git-lite cmake pkgconf qt5-qmake qt5-buildtools kf5-kdbusaddons kf5-kwindowsystem libdbusmenu-qt5 | ||
git clone https://github.com/helloSystem/Menu | ||
cd Menu | ||
mkdir build | ||
cd build | ||
cmake .. | ||
make -j4 | ||
make install | ||
ln -s /usr/local/bin/menubar /usr/local/bin/Menu # Workaround for the 'launch' command to find it | ||
cd ../../ | ||
``` | ||
|
||
### Filer | ||
|
||
``` | ||
git clone https://github.com/helloSystem/Filer | ||
cd Filer/ | ||
mkdir build | ||
cd build/ | ||
pkg install -y libfm | ||
cmake .. | ||
make -j4 | ||
make install | ||
ln -s /usr/local/bin/filer-qt /usr/local/bin/Filer # Workaround for the 'launch' command to find it | ||
cd ../../ | ||
``` | ||
|
||
__NOTE:__ It seems like Filer refuses to start if D-Bus is missing. We should change it so that it can also work without D-Bus and at prints a clear warning if D-Bus is missing. Currently all you see if D-Bus is missing is the following: `** (process:3691): WARNING **: The directory '~/Templates' doesn't exist, ignoring it`, and then Filer exits | ||
|
||
### Dock | ||
|
||
``` | ||
pkg install -y <...> | ||
git clone https://github.com/helloSystem/Dock | ||
cd Dock | ||
mkdir build | ||
cd build | ||
cmake .. | ||
make -j4 | ||
make install | ||
ln -s /usr/local/bin/cyber-dock /usr/local/bin/Dock # Workaround for the 'launch' command to find it | ||
cd ../../ | ||
``` | ||
|
||
### QtPlugin | ||
|
||
``` | ||
git clone https://github.com/helloSystem/QtPlugin | ||
cd QtPlugin/ | ||
mkdir build | ||
cd build/ | ||
pkg install -y libqtxdg | ||
cmake .. | ||
make -j4 | ||
make install | ||
cp stylesheet.qss /usr/local/etc/xdg/ | ||
cd ../../ | ||
``` | ||
|
||
### Icons and other assets | ||
|
||
Install icons and other helloSystem assets that are not packaged as FreeBSD packages (yet). It is easiest to run `bash`, then `export uzip=/`, and then run the corresponding sections of https://raw.githubusercontent.com/helloSystem/ISO/experimental/settings/script.hello. Here are some examples. | ||
|
||
For the system icons: | ||
|
||
``` | ||
pkg install -y wget | ||
wget -c -q http://archive.ubuntu.com/ubuntu/pool/universe/x/xubuntu-artwork/xubuntu-icon-theme_16.04.2_all.deb | ||
tar xf xubuntu-icon-theme_16.04.2_all.deb | ||
tar xf data.tar.xz | ||
mkdir -p "${uzip}"/usr/local/share/icons/ | ||
mv ./usr/share/icons/elementary-xfce "${uzip}"/usr/local/share/icons/ | ||
mv ./usr/share/doc/xubuntu-icon-theme/copyright "${uzip}"/usr/local/share/icons/elementary-xfce/ | ||
sed -i -e 's|usr/share|usr/local/share|g' "${uzip}"/usr/local/share/icons/elementary-xfce/copyright | ||
rm "${uzip}"/usr/local/share/icons/elementary-xfce/copyright-e | ||
wget "https://raw.githubusercontent.com/helloSystem/hello/master/branding/computer-hello.png" -O "${uzip}"/usr/local/share/icons/elementary-xfce/devices/128/computer-hello.png | ||
``` | ||
|
||
For the system fonts: | ||
|
||
``` | ||
wget -c -q https://github.com/ArtifexSoftware/urw-base35-fonts/archive/20200910.zip | ||
unzip -q 20200910.zip | ||
mkdir -p "${uzip}/usr/local/share/fonts/TTF/" | ||
cp -R urw-base35-fonts-20200910/fonts/*.ttf "${uzip}/usr/local/share/fonts/TTF/" | ||
rm -rf urw-base35-fonts-20200910/ 20200910.zip | ||
``` | ||
|
||
Proceed similarly for the cursor theme, wallpaper, applications from the helloSystem/Utilities repository, and other assets. | ||
|
||
### Installing required packages | ||
|
||
Install every package that is not commented out in https://raw.githubusercontent.com/helloSystem/ISO/experimental/settings/packages.hello that are installable. | ||
|
||
__NOTE:__ Not every package will be installable. This probably means that the package in question has not been compiled for the `aarch64` architecture on FreeBSD 13 yet. | ||
|
||
To enable `automount`, run `service devd restart`. | ||
|
||
### Installing overlays | ||
|
||
``` | ||
git clone https://github.com/helloSystem/ISO | ||
cp -Rfv ISO/overlays/uzip/hello/files/ / | ||
cp -Rfv ISO/overlays/uzip/localize/files/ / | ||
cp -Rfv ISO/overlays/uzip/openbox-theme/files/ / | ||
cp -Rfv ISO/overlays/uzip/mountarchive/files/ / | ||
``` | ||
|
||
__NOTE:__ If we provided the temporary packages that are used in the helloSystem ISO build process for download, then one could just install those instead of having to do the above | ||
|
||
### Editing start-hello | ||
|
||
Edit the `start-hello` script | ||
|
||
``` | ||
################################# | ||
# Details to be inserted here | ||
################################# | ||
``` | ||
|
||
### Starting helloDesktop session | ||
|
||
``` | ||
echo start-hello > ~/.xinitrc | ||
killall Xorg | ||
``` | ||
|
||
Type `startx` to start an Xorg session; it should now load a helloDesktop session | ||
|
||
### Adding a user | ||
|
||
Added a new user with Applications -> Preferences -> Users | ||
|
||
``` | ||
cp /home/user/.openbox* . | ||
cp -r /home/user/.config/* .config/ | ||
``` | ||
|
||
## Known issues | ||
|
||
__NOTE:__ Any help in improving the situation is appreciated. | ||
|
||
### Missing login window | ||
|
||
The `slim` package is missing, hence we don't have a login window at the moment. | ||
|
||
### Missing drop shadows | ||
|
||
We could not get drop shadows to work yet. | ||
|
||
__NOTE:__ Please let us know if you know how to enable compositing on FreeBSD on the Raspberry Pi | ||
|
||
### Lacking functionality due to missing packages | ||
|
||
Due to missing packages in FreeBSD for `aarch64`, some functionality is currently unavailable, including: | ||
* Global keyboard shortcuts | ||
* Screenshots | ||
|
||
### D-Bus issues | ||
|
||
Something is not quite right: | ||
|
||
``` | ||
root@generic:~ # /usr/local/sbin/avahi-daemon | ||
Found user 'avahi' (UID 558) and group 'avahi' (GID 558). | ||
Successfully dropped root privileges. | ||
avahi-daemon 0.8 starting up. | ||
WARNING: No NSS support for mDNS detected, consider installing nss-mdns! | ||
dbus_bus_get_private(): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory | ||
WARNING: Failed to contact D-Bus daemon. | ||
avahi-daemon 0.8 exiting. | ||
``` | ||
|
||
D-Bus is so complicated. | ||
What is supposed to provide `/var/run/dbus/system_bus_socket` and why are we missing it? | ||
|
||
### Web browser | ||
|
||
The Falkon browser can be launched on a Raspberry Pi 4 with 512 MB RAM, but trying to load more than the most basic web pages such as http://frogfind.com/ leads to an instant crash, presumably due to a lack of memory. | ||
|
||
__NOTE:__ Please let us know the results with Raspberry Pi models that have more memory | ||
|
||
__NOTE:__ Please let us know if you know how to use RAM compression on FreeBSD |