Use dmesg|less to check for logged errors.
It is most likely a defect file system. You can try to repair remotely, but in worst case (a real damaged file system) you stuck with a not booting system afterwards.
First identify the device: mount|grep ' /storage '. I'm assuming /dev/sda2.
Then force a fsck and reboot:
e2fsck -fy /dev/sda2
systemctl --no-block rebootGood luck.
chewitt systemd-time-wait-sync does hang randomly on Generic because ntp slew adjusts are not detected. There has to be a jump adjust in the beginning (only be used if the time error is >0.5sec).
Assuming the initial RTC value is always "good enough" we can disable systemd-time-wait-sync on this platform with a drop-in file:
[Unit]
ConditionArchitecture=!x86-64Having done a bit more reading I have a suspicion we need to start using systemd to handle NTP as this adds a new systemd .target for when the initial NTP sync has completed, which would be useful in this scenario.
Or conman start to support /run/systemd/timesync/synchonized for reliability ...
On RPIs (or any other devices without RTC) time-sync.target already may work today. Start enabling the needed service:
systemctl enable systemd-time-wait-syncReboot a few times and check:
systemctl status systemd-time-wait-sync
systemctl status time-sync.targetIf time-sync.target is always reached the dependency can be added to the wireguard unit.
Then connect the device again and just use the getedid script.
Get an EDID file from a different monitor supporting all the modes and follow the instructions for Intel devices.
The attached EDID file is only missing the 25Hz mode.
If you miss the initial automatic repository update (i.e. due to missing network connection) no addons can be installed. You have to trigger the update manually via the Sideblade Menu of the addon settings.
Are there an errors logged? Use journalctl -u pulseaudio|paste and post the URL.
pactl load-module module-native-protocol-tcp auth-ip-acl=192.168.0.0/24 auth-anonymous=1 succeed without error on my Generic installation.
Use pactl to load the module, see Pulseaudio [LibreELEC.wiki]
This is a known issue. See Add Wireguard support.
Additional it is reported that the default route is always set to the wireguard device.
Just a thought for a workaround: use wireguard without connman.
Do cp /etc/connman/main.conf /storage/.config/connman_main.conf and add ,wg to the NetworkInterfaceBlacklist line. Reboot.
Then configure wireguard using the wg command.
Use journalctl -u kodi-autostart to see error/log messages from boot.
You can try to disable the LVDS device in the kernel.
The kernel name may differ from the xorg name. Verify it with:
ls /sys/class/drmRemove the cardX- prefix and memorize the device name.
Edit the kernel command line:
mount -o remount,rw /flash
nano /flash/syslinux.cfgAdd video=LVDS1:d to the APPEND line (replace the found device name). Save the file and reboot.
chewitt In 9.2.2 LibreELEC-settings is still at 6f6ca1e4, not including the regdom backport.
rosede ssh into your system and use the command linked in post #2. Please replace US with your country.
Set your regulatory domain: Fresh install raspberry pi 4 5ghz wifi not working
Maybe there is something in the logs. Please post the resulting URLs of:
pastekodi
xrandr --verbose|pasteAccording to LinuxTV there is no driver for the remote control: Hauppauge WinTV-quadHD (DVB-T/T2/C) - LinuxTVWiki
libreelec is not arch linux?
Definitely: Compile [LibreELEC.wiki] 
There are rumors that option -o IPQoS=throughput is required in some ssh client/server combinations. Just try.
2020-04-12 06:47:51.414 T:2320466800 NOTICE: ADDON: service.bluetooth-audio v9.2.0.102 installedBluetooth Audio Device Changer is setting the defined default audio device when starting. Change the addon setting.