hifiberry-os
hifiberry-os copied to clipboard
hifiberry
HDMI display permanently disabled
My RPi is connected to display using HDMI. From version 20220228 is the option "Use connected display" permanently disabled. During boot is the HiFiBerry logo shown on the display, but then the display turns off and cannot be turned on. In the previous version, it works correctly.
I have also observed this behavior.
Somewhere between hifiberryos-20211105-pi3.img and the update to 20220228 the feature has been broken. Selecting the feature through the web interface turns on the display for ~1 second and then it goes off again, the checkbox in the control panel also reverts to unchecked.
While we are thinking about HDMI, does it support audio out?
I have the DAC+ DSP, it would be beyond cool if the DSP could send audio back to the pi and have it bundled as multichannel PCM sent via HDMI using ALSA.
Just think of all of the AVR's out there that have could be upcycled into fully active 2 or 3-way front end with master volume, amplification, and sub out.
I can confirm this bug. It looks like the UI just crashed. I hope we can find a fix for this.
Well what has worked for me so far as a temporary measure was to change the overlay in the config.txt file from
dtoverlay=vc4-fkms-v3d,audio=off
to
dtoverlay=vc4-kms-v3d-pi4,audio=off
BUT the splash screen doesn't work anymore.
I did have to recycle the display toggle in the GUI though. After making this change the toggle was showing a tick, but I just had a blinking cursor. It probably was in the process of sorting the screen out before I impatiently cycled the toggle. Anyway, it works now.
I'm using a Pi4 model B rev 1.5.
Aug 01 14:42:05 zenberry systemd[1]: Starting Weston, a Wayland compositor, as a system service... Aug 01 14:42:05 zenberry systemd[1]: weston.service: Main process exited, code=exited, status=1/FAILURE Aug 01 14:42:05 zenberry systemd[1]: weston.service: Failed with result 'exit-code'. Aug 01 14:42:05 zenberry systemd[1]: Failed to start Weston, a Wayland compositor, as a system service.
and
Aug 01 14:42:05 zenberry systemd[1]: Dependency failed for Local web brower to display web interface. Aug 01 14:42:05 zenberry systemd[1]: cog.service: Job cog.service/start failed with result 'dependency'.
I think this is the issue. I still need to setup a dev environment to even begin looking into this.
I seem to have fixed this. I will send a PR through when I get my ducks in a row. But in the meantime: the problem was the with the Weston service. It was complaining of no input device detected. I haven't tried yet, but I would assume that plugging a mouse or keyboard into the pi would cause it to start correctly. But, for me at least, that isn't going to happen. To fix it you need to edit /usr/lib/systemd/system/weston.service add --continue-without-input to the ExecStart line like this:
ExecStart=/usr/bin/weston --continue-without-input --backend=drm-backend.so --modules=systemd-notify.so
After you save the file you need to run `systemctl daemon-reload' and then turn the external display on again via the settings menu.
I've tried it on the first version that broke and the latest one and it seems to be working.
I then also added hdmi_force_hotplug=1 to my /boot/config.txt so it doesn't keep resetting the display or freaking out if nothing is plugged in/switched on at boot.
@charliesjc : Thanks for the input. No need for a PR for this small change, I'll just add it.
Okay, perfect. Thanks. That reply was so quick it was like you were sitting there waiting for my next move!
Change: https://github.com/hifiberry/hifiberry-os/commit/8ec9f8e219ca74d6cd45893524a266a60478b653
Change: 8ec9f8e
I forgot to mention that one of the things Weston was complaining about was permissions for /var/run/weston. They are set to 0755 and should be 0700. It doesn't seem to make a difference to its function but it does throw a warning.