AreXibOS - fast deployment OS for Xibo CMS Linux players (Unofficial Player)

Get Help Xibo Player for Linux
1

It has been said we will be notified of player dev progress.
Still waiting for that notification…

If you expecting/waiting something that will magicaly save your old devices from Windows 10 EOL in production … you could also check AreXibOS fast deployment OS for Arexibo unofficial Xibo Linux player.

You can test this ISO installation in Virtual Machine Manager on Linux or burn ISO to USB for bare metal install.

Download here:
https://m1r0.de/iso/Arexibos.x86_64-42.3-1.1.iso

AreXibOS is based on Fedora 42 Server x86_64 and latest Arexibo unofficial Xibo Linux player:

Internet is required for OS initial installation (~15 minutes).

AreXIBOS Player inital authorization video:

Cockpit panel on port https://:9090
SSH://:22
user: tv
pass: tv

Minimum requirements:
Internet: Online
CPU: Quad core
RAM: 4GB
GPU: IntelHD or AMD (512Mb+)
Disk: 10GB

(Without video files: dual core CPU/2GBRAM/256MB GPU)

Arexibo unofficial Xibo Linux Player Xibo CMS compatibility evaluation:
+++ = veryfied
++ = confirmed
+ = only tested

Schedule:
Layout +++
Action -
Overlay — i think it default returns to Default layout, no matter on priority or display order set
Interupt +++
Campaign +++
Video/Image +++ sometimes freeze video over its total play lenghth time and then continues to run from start after some “random” delay (strange time behaviour)
Playlist +++
Data connector - never used this function

Dayparting +++
Campaigns +++
Layouts +++
Playlists +++
Media +++ (PDF management of display time/per page no respected)
Datasets +++ (i did only marquee scroller test had some problems displaying: some tickers were not built on init, sometimes does not show on first run, works after reboot)
Displays +++ (generaly all basic functions works but need to confirm ALL of display functions work separatley, for now i have xmr problems described below …)
Display Groups +++
Sync Groups – (did not work as expected, somehow xmr is not connecting properly.)
Display settings +++ (Gets applyed to player but must recheck tcp://*:9505 and Display port 9696 , does it need allow WAN?! cant get any scan on these ports. 2 devices connect xmr(get screenchots) and two does not.)

NOT TESTED:
Player version
Commands
Modules
Transitions
Tasks

###END
BR

P.S.

I have several PC’s running Arexibos with single layout and one playlist with 20h video playtime, 2x text scroller modules, 4 custom javascript modules on screen and picture playlist module running for two months without break on CMS 4.0.1.0

P.S.S.
If you dont see hostname on inital UI display, press “cancel” to reload !

4 Likes
2

Successfully ssh’ed in with the new password you provided, however it says auth: command not found.

3

can you show me list of what is content of /home/tv/.local/bin ?
can you run Arexibo from there ?

This is Arexibo code to authorizre:

arexibo --host https://my.cms/ --key $SERVER_KEY /home/tv/Downloads/ax.data

  1. Just in case this is auth script /home/tv/.local/bin/auth :
#!/bin/bash
clear
echo "#############################"
echo "### AreXibOS registration ###"
echo "#############################"
echo "AUTH : Enter Xibo CMS server address:"
read address
echo "AUTH : Enter Xibo CMS server password:"
read password
echo "AUTH : Preparing registration request!"
arexibo --host $address --key $password /home/tv/Downloads/ax.data
echo "AUTH : In case of registration error, doublecheck your connection details!"
echo "##################################################################################"
echo "### Please authorize this display ID in Xibo CMS server: $HOSTNAME ###"
echo "### Display will now restart and wait for authorization from Xibo CMS server!  ###"
echo "##################################################################################"
sleep 1
/bin/cp /home/tv/.local/bin/startup /home/tv/.local/bin/gnome-kiosk-script
restart
  1. This is Arexibo startup script:
    Copy startup script over /home/tv/.local/bin/gnome-kiosk-script
### Arexibo
sleep 1
wpctl set-volume @DEFAULT_SINK@ 95%
sleep 1
arexibo --allow-offline /home/tv/Downloads/ax.data/
exec "$0" "$@"
sleep 3

Reboot or restart gdm or pkill gdm

  1. Arexibo should now have all in place for startup after authorization !

  2. Just in case this is latest Arexibo build on Fedora 42: http://m1r0.de/ks/42/xiox/arexibo

Hope this should get you going.

BR

4

BOOM, THIS WORKED!

image
image3027×114 6.46 KB

5

So this worked in my VM environment, but the image you provided refuses to see our tiny pc’s emmc storage. Do you know of any way around this? I’m able to install Fedora on it manually, but your image refuses to find the storage :frowning: .

6

Thanks for report on VM and disk detection!!!

Glad you got it connected to CMS even through it was VM !

Interesting thing with disk, EMMC disk detection, i have never had problem installed on EMMC but that is on TWO PC only, could you take some screenshots from anaconda installer ouput ( press CTRL+B + 1-6 )?

For storage, OS system is set to auto partition all detected drives and autoformat them with --nolvm and --nohome options so there is not much I can do atm except look at anaconda logs and check that out first.

It would be very helpfull if i could see this before Fedora 43 is out and maybe able to set some fix for EMMC disks.

What you can do for now, Download Fedora 42 Workstation and install on EMMC PC, setup RPMFusion with QT and rust and then try download player from my server for test !

Good LUCK!

1 Like
7

I might have one option to try for EMMC solution for Fedora 43 release !

Do you use UEFI of BIOS boot ?

What CPU’s are in those machines ?

Autopartitioning scheme:

zerombr
clearpart --all --initlabel --disklabel=gpt
autopart --nolvm --nohome

QTWebEngine install

dnf update -y
dnf install qt6-qtwebengine gstreamer1-plugin-libav gstreamer1-plugin-openh264 rust -y
dnf swap ffmpeg-free ffmpeg --allowerasing -y
dnf swap libavcodec-free libavcodec-freeworld --allowerasing -y

1 Like
8

Just to confirm, just loaded Fedora 42 iso on DE3450 Aopen PC which is Intel Celeron CPU.
Disk detection passed white dots in 1/4 screen and continued to install !
Downloading 1004 packages !

9

UEFI. They’re Intel Atom x5-Z8350 with Intel x5-E8000 Integrated Graphics (i915). They’re MINISFORUM Z83-F miniPC’s. Thank you for all of your help on this btw. I should be able to figure it out manually, just rollout will be kind of rough. Your scripts worked so well on VM install.

On your newest comment: I left it overnight (15+ hours) and it was still getting dots :(.

10

Thanks for kind words, info and for testing!

What type of disk/controller is in that machine ?

What program are you using to burn ISO ?

Can you dd ISO to USB ?

If disk detection dots takes more space then half screen on one horizontal line of screen its over and goes in loop. On disk dot detection screen you can use anaconda installer comands such as CTRL+B (1-6) virtual terminal to get anaconda installation process output which is used for debuging.

Try out manual installation process to get hang of general installation idea of QT6, Rust and FFMPEG and by then I will prepare F43 for beta testing, that could be by end of week since i already have ISO downloaded localy.

If you get blocked anywhere during manual install, drop note and we try fix to it.

And my PC just finished installation and waiting for user authorization screen :slight_smile:

BR

1 Like
11

AreXibOS 43 release: http://m1r0.de/iso/arx.f43-03.11.2025-03:59.iso

Fixed: sending commands from Xibo CMS to Arexibo player:
“reboot” “restart(display)” and “shutdown”

(XMR server must be operational with port open to work properly or otherwise use scheduling option to send commands ! )

Tested and confirmed boot to UI on VM and in PC with m2 storage.

Xibo CMS send command to Arexibo player:

Also it is a must to burn ISO to dedicated USB, not custom partitioning or VENTOY like configurations !

I use this tool: https://flathub.org/en/apps/org.fedoraproject.MediaWriter

1 Like
12

I burnt the AreXibo Fedora 43 iso using rufus in DD mode onto a 2GB thumb drive. The included setup (and usage) scripts are so handy and really help streamline an install. Be mindful that after connecting to your CMS for the first time and initial sync that reboot may and likely will be required (or gdm kill as 0x0 pointed out) or you will likely receive errors.

I’m the IT Director of a metallurgical foundry in Wisconsin, USA and we have to have safety/information monitors posted throughout our facilities with training/safety videos, company notices of meetings/etc., and we utilize the time/date and weather widgets as well. Xibo in general has given us a powerful platform in which to be able to roll this out on less than ideal tiny PC configurations (thanks budgets!). I really appreciate that AreXibo keeps it stripped down and to the point for not only resource management, but also ease of rebooting/recovery in the event of an outage. Over the past 3 years I have made it my cause to remove as many bloated/slow Windows installs as possible so we can remain a well oiled machine in the event of power outage, equipment failure, etc.

I wish that I had known about this solution back when I was in banking. We paid outside vendors many thousands of dollars per screen for lobby TV solutions that weren’t 1/10th of what Xibo provides.

1 Like
13

Hello @Eddie_Woolf,

Thank you for your kind words, usage report info and testing/reporting f43 beta release !

Glad that you managed to install it without disk detection problem !
Few people who used Rufus to burn AreXibo.f42 reported same disk detection problem which seems to be fixed for AreXibo.f43 release.

I dont know if DD is default mode on Rufus, but I will note down that if burning ISO with Rufus, users should use DD mode** (I never used Rufus myself).

BR

14

ISO is actually default/recommended so you can access the file system on the card in other OS’es, but I’ve always had exponentially more luck writing in DD with any linux distro and using rufus.

-Eddie

1 Like
15

Hello 0x0
Greetings to the entire Linux beta testing community.

The dd command is a Linux tool used from the terminal. There are also graphical applications that internally use this command to write disk images, ISOs, and other files in Linux.

I just downloaded the latest version of Arexibo (page 43), and the reboot and shutdown commands sent from the CMS are now working.

I added the Wi-Fi card drivers to the test mini PC, as they are not included in the ISO.

I will perform more tests and report back with the results.

Thanks for the new version.

1 Like
16

Hello pacwcbs,

thank you for testing and report for 43, your report has been great help for fixing sending commands from CMS !

Could you give some more info on Wifi drivers and device you are using ?

Can you find your Wifi driver here: start [ELRepo Wiki] ?

BR!

17

Hi 0x0

thanks to you and the Arexibo developers.

I’m very happy to contribute to this project.

To add and activate the drivers, you’ll always need to run the following commands, depending on your Wi-Fi network card. In my case, it’s an Intel card, and the commands to add and activate them are as follows:

You must be logged in with administrator privileges.

sudo dnf --enablerepo=updates-testing install iwlwifi-mld-firmware

sudo dnf install iwlwifi-mvm-firmware iwlwifi-dvm-firmware

sudo modprobe iwlwifi

Finally, restart your computer.

sudo reboot

When your computer starts up, press CTRL + ALT + F1 to access the login screen and connect to the Wi-Fi network.

It should now work.

1 Like
18

Thank you very much for your good work about Arexibos.

I successfully installed 42 in a VM (KVM), but logging in with the tv account and tv password does not work with ssh or in a terminal (Ctrl+Alt+F1). We also do not know the password for the admin account, which I assume is the root account.

19

Thank you for your kind words !
Sent you msg with new version and login details.

20

Sory but with this link http://m1r0.de/iso/arx.f43.x86_64-43_Beta-1.3.iso I am not downloading the ISO, but a very small 196-byte file…