If installing again save the installation log to the stick (menu point 3) and post it.
I tried doing this and it said to find the logs in /flash/logs, but don't see a logs directory in the install's /flash after doing so, nor any new files on the USB drive.
Log file here. I had to boot to a live Linux from USB and edit the Kodi install's syslinux.cfg on the SSD to add ssh in order to get in since I couldn't enable it from the installation wizard with no GUI access.
How would it install if it can't write to the SSD? Also, why would previous versions work? Is there a config file somewhere that I can turn on verbose logging without going through the GUI?
I can't actually get into the installed version to turn logging on. When I SSH into it the /logfiles directory is empty.
I've been running LibreElec on an old Sandy Bridge machine for ages. Previously I posted here about an issue with newer (v12+) versions not working here. Rather than necro that thread I figured I'd post a new one.
I tried the latest nightly versions of 12 and 13 as recommended in that thread and found that running Kodi live from those images on USB works fine. Display drivers are clearly working. But if I install either of these versions (anything later than 11.06 really) to a SATA drive I just get a blank screen. Kodi is clearly running, I can access it via SSH. But I get no display. I've tried installing to three different SSDs.
Any ideas?
Can confirm calibration works under Estuary.
Same issue here with version 12. No resolution?
Legacy build would probably work, yes.
So using legacy the installer prompt comes up, but upon choosing the installer option I immediately get a blank screen. Same thing happens with the 11.95 version, but the 11.06 installer works normally. Is 11.06 going to be the last version a Sandy Bridge machine is capable of running?
I've been running version 11 for a while on an old Sandy Bridge desktop. Upon upgrading to 12 I get no HDMI signal from either port. Checking the log (https://paste.libreelec.tv/ample-mite.log) I'm seeing:
2024-07-16 11:33:37.945 T:1548 error <general>: libva error: /usr/lib/dri/iHD_drv_video.so init failed
2024-07-16 11:33:37.945 T:1548 info <general>: VAAPI::Close - closing decoder context
2024-07-16 11:33:37.945 T:1548 info <general>: CApplication::CreateGUI - using the gbm windowing system
2024-07-16 11:33:37.945 T:1548 info <general>: Checking resolution 16
2024-07-16 11:33:37.948 T:1548 info <general>: GL_VENDOR = Intel
2024-07-16 11:33:37.948 T:1548 info <general>: GL_RENDERER = Mesa Intel(R) HD Graphics 2000 (SNB GT1)
2024-07-16 11:33:37.948 T:1548 info <general>: GL_VERSION = OpenGL ES 3.0 Mesa 24.0.5I've tried adding the following lines to /storage/.config/kodi.conf but Kodi doesn't load at all with them present (despite no signal I can tell when it's running because the Yatse Android remote connects once it's up):
MESA_LOADER_DRIVER_OVERRIDE=i965
LIBVA_DRIVER_NAME=i965Is Sandy Bridge just no longer supported? Would a fresh install using Generic Legacy solve this?
Tried installing 19.4 today on an old 2nd gen (Sandy Bridge) machine and xorg fails to start. 18.9 still works properly. I assume this has something to do with the newer Linux kernel (5.10 instead of 5.1), but unsure as I don't see other Linux users complaining about this generation of CPU no longer working. Is there anything I can do to pull an updated driver or something?