OK, thank You, will have a look at it!
Posts by pakovec2
-
-
I'd guess that after power outage the RPi is being booted before the HDMI source (AVR or TV) is on, so we don't detect it and fall back to the default Pulse (BT) output. It's fixed by powering up devices in the correct order (HDMI source first, then RPi) or worst-case by caching EDID data from the HDMI connection and configuring the kernel to read the cache at startup so it believes the HDMI source is connected.
IIRC .. run "getedid" from the console.
Thanks. That might be it part of the problem. Tke RPi runs pretty much constantly (if no unrequested shutdowns/reboots), whereas I turn off the audio HDMI. Is there a way to
a) fix the setting, so it doesn't change it automaticallyor
b) change it from command line?Thx
-
Hello everybody,
recently with high winds, we often get a power failure, crashing some of my systems.
With my LibreELEC I then often find, that no sound comes out, and the Audio Output is changed.
When working, I use "ALSA: vc4-hdmi-0 (vc4hdmi0), ONK HTX-22HDX on HDMI" - position #4 in the list of available Output devices.
After crash/startup it's changed to "PULSE: Default, Bluetooth Audio (PULSEAUDIO)" - position #5 in the list.
How to change the default one, or how to change it from command line, so I don't have to start up my video just to play some music?
pastekodi: http://ix.io/3UVe
journalctl: http://ix.io/3UVi
PS: the logs will probably not show anything - after a "clean reboot" the output does not change, so now it's working.
-
OK, combination of things worked. Seems like the system was not fully started before turning on the projector (streaming via HDMI), and clicking few things in the interface.
Then, also the part of HTTP control was disabled, so had to set up that as well (the password requirement here seems to be new?).
Thanks to all for advice
-
Yet another logs command? Thanks, learning constantly.
Pastekodi:
Journalctl:
Thanks
-
OK, so I ran it on a display, to see, what's coming up there, and it's stuck on a startup check, last OK message is:
[ OK ] Reached target System Time Synchronized.
The system doesn't even come on, so can't deal with anything in Kodi, only with the shell commands.
Any ideas, please?
-
You need to enable the appropriate Kodi settings:
Services - Control - Allow remote control via HTTP option
Well, that step could be next, once the system even comes up. It's stuck in the boot phase...
-
Downgraded even more (to 9.2.8) and it still isn't running. Any advice, please? Seems I am missing something global meanwhile
-
Downgraded to 10.0.0, same issue -
Failed to connect to 192.168.2.8 port 8080: Connection refused
Logs:
-
-
Hello,
tried to update my LibreELEC from command line (via SSH), by 'wget'-ing the .gz file and reboot-ing.
The RPi itself is accessible via SSH, however the Kodi interface is not (neither via Chorus from local PC, nor via Yatse from Mobile).
Seems like the Kodi service is not running at all. Any advice, please?
PS: I haven't checked the direct system yet, as it's connected via HDMI to a projector, and it's not dark enough outside