Linux version info and install instructions

The latest version is not installing on the Pi4 or Pi5.
Running a vanilla install of Raspbian Desktop 64bit.

Using the instructions above, we have errors with:
realdash depends on libgpiod; however:

  • Package libgpiod is not installed.*

dpkg: error processing package realdash (–install):

  • dependency problems - leaving unconfigured*
    Processing triggers for gnome-menus (3.36.0-1) …
    Processing triggers for desktop-file-utils (0.26-1) …
    Processing triggers for mailcap (3.69) …
    Errors were encountered while processing:
  • realdash*

Try to install with:
sudo apt-get install libgpiod
Error message:
Package libgpiod is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package ‘libgpiod’ has no installation candidate

So I tried to ignore it:
sudo dpkg -i --ignore-depends=libgpiod Downloads/realdash-mrd_2.3.8-1_arm64.deb

The install passes and seems to work

I tried multiple times already, no luck. Just out of curiosity I tried the armhf version also, and surprisingly that installed with no errors. But obviously the app doesn’t run since it’s 32 bit.

I might just need to try a fresh OS install, idk

Interesting. I have the previous version on my other Pi4, I’ll probably just copy it over and try running that version for now.

Did you get it to work at all? That is about where i am at with it.

The previous version worked for me

Oh man, we messed up with the dependency on the deb- package. It is supposed to be ‘gpiod’ instead of ‘libgpiod’. I will build new package asap.

1 Like

New deb packages now available on MRD.

1 Like

Can confirm the 2.3.8.2 version works on the Pi4 with no issues

1 Like

The previous version also works on bullseye pi4b and bookworm on pi5

Hello,
RD cannot be installed on a Rock 5B with Armbian 24.02. (5.10.160 XFCE).
Armbian is a fresh new installation.

sudo apt-get update
sudo apt-get dist upgrade
sudo apt install libopenal1 libvlc5 libssl1.1 espeak-ng sudo dpkg -i realdash-mrd_2.3.8-2_arm64.deb
sudo apt install libssl-dev
sudo apt --fix-broken install sudo dpkg -i --ignore-depends=libssl1.1
…I did them all in sequence

realdash-mrd_2.3.8-2_arm64.deb is a very fresh download.


I get these error messages when installing RD:

I also get the same error messages with older Armbian or RD versions.
I’m really at a loss now and ask for your help!..

I have no idea what ‘lintian/profile.pm’ is and how it is related to Debian package installation, sorry :frowning:

I don’t know anything about Lintian and the ‘known_vendors’ thing really, but these links might provide some useful info:

https://www.chiark.greenend.org.uk/doc/lintian/lintian.html#vendor-profiles
https://wiki.debian.org/Lintian/Vendors

The Lintian man page might have some relevant info too.

Also, I’d check the mentioned lines in Profile.pm, and try to figure out what it’s trying to do…

Hello, I’m trying to get realdash running on a raspberry pi that is running a basic Yocto OS image. The yocto image is essentially the core image with xfce desktop running. I created a realdash recipe to include all the dependencies listed above, but Yocto doesn’t pull from pre-build apt repos. It builds everything from scratch using the versions available in the given Yocto release (I’m using their Nanbield release right now)

Once I fine tuned the dependencies, I no longer get any faults about missing .so files. But now it flashes a window on the screen for a split second and crashes. I have more log files showing what libs are in /usr/lib, etc, but I’m not sure how to attach that here.

Below is the output when I run “valgrind realdash”. Seems that it’s crashing at the XOpenDisplay() and XFlush() function calls?

I’m guessing the versions of the various libraries are slightly different than the ones you’ve tested against. Any suggestions on how I could debug this further?

realdash-yocto-crash

Hi guys
The best version of Linux for a install RD
Is debian bullseye last release

know of a way to enable autorun at login for bullseye? thanks for any help

Hey mate, sounds like youre having some suscess with linux setup.
Could i trouble you for any advice on running a quick boot linux setup on Rpi4 ?
looking for a faster boot and mainly just opening realdash in fullscreen on boot and not maximized but still in window.

Thanks for ny help, Jim

Jim,

I don’t have an RPI4 setup to run realdash on. Are you using Raspberry Pi OS? I have based my installs on a very stripped down Debian os that just boots to a wayland shell and starts realdash. Everything else is configured through ssh. Are you familiar with linux?

If you run the command systemd-analyze blame and systemd-analyze crtitical-chain in a terminal the results will tell you what processes are taking the longest in the linux boot process. I have found that disabling the network auto ip assignments and setting static ip address reduces the boot times significantly.

Hi mate,
Firstly thank you for the reply. Im not running the original Pi OS, Im running the lite version of Debian Bullseye With Lxte graphical interface. Install is about 0.8gb. The image is on Raspberry Pi imager under custom OS packages.

I wasnt aware you could boot Realdash from a shell? thats cool ! I thought you had to run if from graphical interface. Can i ask how long your Debian & weyland takes from power up to real dash loading?
I would like to be able to boot from shell and strait into fullscreen realdash :slight_smile:

Jim,

I can’t comment on the boot times on a Raspberry Pi device as I have moved away from using them. One thing I remember about the Pi devices is that they use a binary blob boot loader that was difficult to customize.

I am not technically starting Realdash from a command prompt, but starting the weston composter which is built on wayland (xwindows replacement) and weston is auto launching realdash.

You may want to look at running the latest pi image as my understanding is it has wayland built in and may other improvements. You can check this out: https://hackaday.com/2023/10/13/debian-bookworm-comes-to-the-raspberry-pi-and-wayland-is-now-default/

As far as boot times that is going to very dependent on which style small board computer, operating system, and how stripped down you want to make it.

My current project a x86_64 Gmktek ultra mini pc will boot realdash in about 2 seconds after the bios initialization splash screen. The bios initialization takes longer than anything else and is the limiting factor. Obviously, it costs more than a raspbery pi 4 about 139 us dollars but was worth it for my application.

I wonder if I should post a youtube video or something to explain it. If you’re interested in that it would take me a week or so as I am pretty busy at work currently.

3 Likes