@goldyfruit When I first installed just the Pi OS and booted, a rainbow colored square appeared on the screen for a few seconds. Then the console output scrolled by until it was done booting. After I installed OVOS, no rainbow and no console messages appear on the screen even while it is booting. Is this expected behavior, or is it a clue, maybe that something messed with the screen driver during the install?
@goldyfruit This time I started from scratch. I definitely used Trixie 64 lite. The first time I booted it all was well. Then I tried rebooting again. This time it did not connect to the WiFi, so I plugged in a CAT5 connection. After updating the dist installing git and curl (which was already there) and starting the install, I got this (which I have never seen before)
➤ Installing Ansible requirements in Python virtualenv… [done]
➤ Looking for automated scenario… [done]
➤ Scan I2C bus for hardware auto-detection…[\e[31mfail\e[0m]
Upload the log on https://paste.uoi.io website? (yes/no) yes
[\e[31mfail\e[0m]
Upload the log on https://paste.uoi.io website? (yes/no) y
➤ Unable to finalize the process, please check /var/log/ovos-installer.log for more details.
➤ Please share this URL with us “https://paste.uoi.io/cfg2”
bfisher@Mycroft3:
Some I2c problem? Or the OVOS update is broken?
Tried again and got this log URL: dpaste/bXX3 (Python) (except that I can’t paste in exactly in here but the bXX3 is the unique part). It seems to indicate that a file is missing:
avrdude: error while loading shared libraries: libgpiod.so.2: cannot open shared object file: No such file or directory
Someone on Matrix had the same issue, I created a PR.
This doesn’t sound like a Mark II except if you connected some extras HAT/I2C to the Raspberry Pi. 
PR is merged, let me know if that fix your issue.
@goldyfruit: Ok, it installs now. Current status: No GUI (see later). Voice from Mycroft appears in a couple minutes saying it is ready. At the point it can answer “What time is it” and “what is the temperature”. Not very reliably, though. It often either does not understand or answer a different question (about notifications). Also, “Hey Mycroft” gives a very soft ‘gong’ prompt, but I can barely hear it. The Mycroft answers are at the normal volume.
Regarding the GUI. I tried the systemctl command suggested at the end of the install:
(ovos) bfisher@Mycroft3:~ $ sudo systemctl status ovos-gui.service
× ovos-gui.service - Open Voice OS - GUI
Loaded: loaded (/etc/systemd/system/ovos-gui.service; enabled; preset: enabled)
Active: failed (Result: signal) since Tue 2026-03-10 14:00:50 EDT; 4s ago
Duration: 344ms
Invocation: 699ea51a91ca412eab54ded3c6855195
Docs: Components - Open Voice OS Container Documentation
Process: 1779 ExecStart=/usr/bin/ovos-shell (code=killed, signal=ABRT)
Main PID: 1779 (code=killed, signal=ABRT)
Mar 10 14:00:50 Mycroft3 systemd[1]: ovos-gui.service: Scheduled restart job, restart counter is at 5.
Mar 10 14:00:50 Mycroft3 systemd[1]: ovos-gui.service: Start request repeated too quickly.
Mar 10 14:00:50 Mycroft3 systemd[1]: ovos-gui.service: Failed with result ‘signal’.
Mar 10 14:00:50 Mycroft3 systemd[1]: Failed to start ovos-gui.service - Open Voice OS - GUI.
(ovos) bfisher@Mycroft3:~ $
=====================
Were you talking to me when you said it did not appear to be a MkII? All I can say is that I bought a MkII from Mycroft. After a few weeks it failed (power supply). At the point they said they would send a new one if I returned the old one. So what I have is a replacement, but unless they hid something inside it is a bog-standard Mk II that I have never opened.
More about the GUI:
journalctl -u ovos-gui.service with time yields
Mar 10 14:00:44 Mycroft3 systemd[1]: ovos-gui.service: Scheduled restart job, restart counter is at 1.
Mar 10 14:00:44 Mycroft3 systemd[1]: Started ovos-gui.service - Open Voice OS - GUI.
Mar 10 14:00:44 Mycroft3 ovos-shell[1766]: no screens available, assuming 24-bit color
Mar 10 14:00:44 Mycroft3 ovos-shell[1766]: Cannot create window: no screens available
Mar 10 14:00:44 Mycroft3 systemd[1]: ovos-gui.service: Main process exited, code=killed, status=6/ABRT
Mar 10 14:00:44 Mycroft3 systemd[1]: ovos-gui.service: Failed with result ‘signal’.
Starting it manually yields:
(ovos) bfisher@Mycroft3:~ $ /usr/bin/ovos-shell
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin “xcb” in “” even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
Aborted
(I am well aware that Qt can be a PITA!)
This is expected, you need to pass many environment variables as the systemd unit does.
Did you enable the tuning via the ovos-installer?
Yes, I enabled turning but not overclocking. So you are saying that the errors that come from running ovos-shell directly are not related to the errors that are shown by journalctl on the GUI. Ok, but clearly the fact that the GUI dies within a second is why I don’t have a GUI display.
”No Screens Available” in the systemd log must be important, right? @goldyfruit
Thanks for the great tutorial!
1 Like