[x86-64] Blank screen when installed, live mode works fine

TheAmorphous · May 31, 2025 at 6:59 PM

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?

**Da Flex** · May 31, 2025 at 8:36 PM

Please provide a full debug log.

How to post a log (wiki)

1. Enable debugging in Settings>System Settings>Logging
2. Restart Kodi
3. Replicate the problem
4. Generate a log URL (do not post/upload logs to the forum)

use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

TheAmorphous · May 31, 2025 at 9:39 PM

I can't actually get into the installed version to turn logging on. When I SSH into it the /logfiles directory is empty.

**Da Flex** · May 31, 2025 at 11:21 PM

If you don't get any log files, then we already found the cause of the issue. Kodi has no write access on your SATA drive.

TheAmorphous · May 31, 2025 at 11:59 PM

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?

**chewitt** · June 1, 2025 at 8:31 AM

The /storage/logfiles directory is not a persistent log storage location. It maps to the \\LIBREELEC\Logfiles Samba share and a zip archive of logs will be auto-generated when the Samba share is accessed over the network. If you have not accessed the Samba share from the network there will (correctly) be no files in the directory.

Run "journalctl | paste" and share the URL generated so we can see the system log (Kodi debug logs are unlikely to be useful).

**Da Flex** · June 1, 2025 at 9:09 AM

Quote from TheAmorphous

I can't actually get into the installed version to turn logging on. When I SSH into it the /logfiles directory is empty.

Nobody was talking about that folder before.

Activate log level 1 at advancedsettings.xml, and reboot. Then run pastekodi from SSH, and post the resulting URL.

**mglae** · June 1, 2025 at 10:31 AM

If installing again save the installation log to the stick (menu point 3) and post it.

Some nitpicking:

Quote from TheAmorphous

I can access it via SSH.

After a fresh install ssh is disabled by default. It must be enabled by the installation Wizard, LE Settings Addon or ssh kernel parameter. Did you do anything?

TheAmorphous · June 2, 2025 at 6:34 PM

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.

Edit: Here is a log running the same nightly in live version from the USB installer (where I actually get a display signal and everything works normally). Nothing is jumping out at me as different. GL-RENDERER detects the same correct GPU both ways...

Edit 2: Found this in the install version:

Code

info <general>: GUI format 720x400, Display No Output: 720x400

whereas the live version has this:

Code

info <general>: GUI format 1920x1080, Display HDMI3: 1920x1080 @ 60.00Hz

What would cause the HDMI display to not be detected when installed but fine when run live?

TheAmorphous · June 2, 2025 at 7:15 PM

Quote from mglae

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.

**chewitt** · June 3, 2025 at 2:33 PM

I'd be interested to see the "pastekodi" output from an LE13 nightly 'Generic' image (not Generic-Legacy)

TheAmorphous · June 3, 2025 at 3:39 PM

Here is a log from LibreELEC-Generic.x86_64-13.0-nightly-20250602-2f1a31d. Oddly enough I can actually get a signal from this one and get into Kodi, BUT the colors are all funky and psychedelic looking. Like it's running in EGA or something.

**chewitt** · June 4, 2025 at 1:56 PM

Code

warning <general>: [display-info] EDID parser warnings:
warning <general>: [display-info] ----------------------------------------------
warning <general>: [display-info] Block 0, Base EDID:
warning <general>: [display-info]   Some but not all primaries coordinates are unset.
warning <general>: [display-info] 
warning <general>: [display-info] Block 1, CTA-861 Extension Block:
warning <general>: [display-info]   Video Capability Data Block: Set Selectable RGB Quantization to avoid interop issues.
warning <general>: [display-info] 
warning <general>: [display-info] ----------------------------------------------
info <general>: [display-info] make: 'AccuScene Corporation Ltd' model: 'ASLFHD'
info <general>: Found resolution 1920x1080 with 1920x1080 @ 60.000000 Hz
info <general>: Found resolution 1920x1080 with 1920x1080 @ 59.940063 Hz
info <general>: Found resolution 1280x720 with 1280x720 @ 60.000000 Hz
info <general>: Found resolution 1280x720 with 1280x720 @ 59.940063 Hz
info <general>: Found resolution 640x480 with 640x480 @ 60.000000 Hz

Display More

The limited number of resolutions/modes suggests to me that you're hooked up to a monitor? .. which is flagging some warnings about EDID data. Most devices flag some kind of EDID warning, but this is showing unusual ones for primaries/quantization which are related to colour .. and you're reporting weird colours.

If you connect the device to another HDMI device (ideally a normal TV) is anything different?

TheAmorphous · June 4, 2025 at 2:44 PM

That was plugged into a monitor, yes. I started using it for testing when I couldn't get a signal to the projector this device is normally used with. This is a pastekodi with the 13 nightly generic plugged into the projector. Same bad colors.

Edit: I notice there are no EDID warnings when plugged into this same monitor when booting live from the 12 nightly USB. No odd colors and everything works normally when running it that way.

**mglae** · June 4, 2025 at 4:36 PM

Did you try different HDMI cables? May solve such weird HDMI issues.

Quote from TheAmorphous

but don't see a logs directory in the install's /flash after doing so, nor any new files on the USB drive.

They are saved to the stick.

Quote from TheAmorphous

I had to boot to a live Linux from USB and edit the Kodi install's syslinux.cfg on the SSD to add ssh

While still in installer you can switch console with Alt-F3 and use the debug shell to mount and modify the file(s).

TheAmorphous · June 4, 2025 at 6:05 PM

Quote from mglae

Did you try different HDMI cables? May solve such weird HDMI issues.

Yup. Multiple cables, multiple SSDs, multiple monitors (one monitor, one projector). Everything works fine with installed version 11.06 and earlier. Everything works fine in 12/13 when "live" from USB. 12/13 installed either yields no signal at all or the funky color palette.

**chewitt** · June 5, 2025 at 7:42 AM

XML

<?xml version="1.0" encoding="utf-8" ?>
<advancedsettings version="1.0">
  <!-- enable debug logging -->
  <loglevel hide="false">1</loglevel>
</advancedsettings>

First, create /storage/.kodi/userdata/advancedsettings.xml with that ^ content so Kodi is in debug mode for logs.

Second, run "vainfo | paste" and share the URL.

Now two things to experiment with:

a) Force the HDMI connector colourspace profile to Broadcast RGB:

Code

systemctl stop kodi
kmstest -c HDMI-A-3 -P "Broadcast RGB=1" < /dev/null
systemctl start kodi

Any different? - run "pastekodi" and share the URL again.

b) Force Kodi to use the i965 driver profile:

Code

MESA_LOADER_DRIVER_OVERRIDE=i965
LIBVA_DRIVER_NAME=i965

Create /storage/.config/kodi.conf with that ^ content, then reboot and run "pastekodi" and share the URL again. Also run "vainfo |paste" and share the URL.

I'm not expecting to acomplish anything .. but we'll have more information to review.

EDIT: 3rd thing: Do you have a DP to HDMI connector? .. i.e. connect to the DP socket not an HDMI socket. It would be interesting to see if that changes anything. I'm also wondering if the board has native HDMI connectors or internally they are DP with an LSPCON chip providing HDMI .. in which case have you ever updated the BIOS and/or LSPCON firmware?

**mglae** · June 5, 2025 at 5:49 PM

chewitt There is no i965 mesa driver any more in LE. Current intel gallium mesa drivers are i915, crocus and iris.

Libva i965 still exist and is auto-loaded according to the logs.

[x86-64] Blank screen when installed, live mode works fine

Similar Threads

Nightly Builds