We currently do internal tests on LE 12. No issues so far. Maybe official release next week. ![]()
You can configure LE as NAS, or you can autostart Kodi on Raspberry Pi OS.
We currently do internal tests on LE 12. No issues so far. Maybe official release next week. ![]()
You can configure LE as NAS, or you can autostart Kodi on Raspberry Pi OS.
With projector (at HDMI-0) and AVR (at HDMI-1) powered on, run getedid delete and getedid create again.
Do you get an error message after one of those commands?
And I think any OS (including the linux too) is good to be rebooted periodically, so then why not every night... Less issues... Less headache.
I'm using an RPi3B as an always-on NAS (only Ethernet, Raspberry Pi OS). No periodical reboot needed. It just works. I suggest to figure out, which add-on breaks stable usage.
I can log in via smb to the LibreELEC-Generic.x86_64-9.2.6.img version works
Not helpful. Continue with the suggestion from chewitt :
If no, does "live" or "run" modes work (running from USB)?
If it does boot with a black screen, you should be able to login by SSH afterwards. In that case...
Well same here, Im using LibreELEC-RPi5.aarch64-11.95.2.img.gz with a RPI5...
Use the latest nightly build instead: Download
Did you tried Generic-legacy variants? That's needed for Nvidia graphics.
You are using a banned add-on. That means no support.
If you want to continue, open a new thread, and post a clean log with an URL from our own log server (pastekodi result).
Use this thread: Simultaneous Audio Output
Next time post your complete setup first. ![]()
I haven’t really used the file manager a ton. Is this something I can do if I plug a mouse in? Like just copy and paste that onto the USB drive?
Yes.
I admit I ought to have tried swapping ports sooner but cie la vie!
Create new EDID: Click!
Chromebox is pretty exotic here, so problems are expected. The kodi.log is at /storage/.kodi/temp. If you can access that folder somehow, upload the log as attachment. We need a log from LE 12 Beta 2.
Update to LE 12 Beta 2. If the issue persists...
However, I have no display output so I cannot use the GUI as you suggest in step 1 for enabling the debug log mode.
Create an advancedsettings.xml file, and set log level to value 1. Then you're logging permanently, and invisible for GUI.