[x86-64] Videos freeze due to CPU at 100% on mini PC

    I have been using Kodi on an Amazon Fire TV stick for many years. Now I want to move the media center to a mini PC with LibreELEC. To do this, I successfully installed the current version 12.2.1 build LibreELEC-Generic.x86_64-12.2.1.img.gz on a GMKtec G3 Plus (Intel Twin Lake N150). Unfortunately, I'm already having massive problems playing videos (1080p) with the default settings. The playback freezes after a few seconds, even though the video counter continues to run. The situation is similar when streaming IPTV. Every few seconds, the image stops and the buffer reloads. Apparently, after a few seconds, the CPU is at 100% capacity (top -d 1).

    In the meantime, I have done some research and found out the following with SSH:

    • lspci | grep -i vga
      returns
      00:02.0 VGA compatible controller: Intel Corporation Alder Lake-N [Intel Graphics]
    • cat /proc/cpuinfo | grep -i model
      returns
      model : 190
      model name : Intel(R) N150
      model : 190
      model name : Intel(R) N150
      model : 190
      model name : Intel(R) N150
      model : 190
      model name : Intel(R) N150
    • vainfo
      returns
      Trying display: drm
      libva info: VA-API version 1.22.0
      libva info: Trying to open /usr/lib/dri/iHD_drv_video.so
      libva info: Found init function __vaDriverInit_1_22
      libva info: va_openDriver() returns 0
      vainfo: VA-API version: 1.22 (libva 2.22.0)
      vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 25.2.6 (6209f5a)
      vainfo: Supported profile and entrypoints
      VAProfileNone : VAEntrypointVideoProc
      ...
    • find /usr/lib/modules -type f | wc -l
      returns 0
    • lsmod | grep i915
      returns nothing

    To be honest, I don't have much experience with Linux yet as you may already see.

    Is it possible that there are issues with the graphics driver? How can I get LibreELEC working on this device? I would love to do so in order to get rid of this Fie TV stick. Many thanks!

    Any suggestions are highly appreciated!

    Thank you! Here you are:

    https://paste.libreelec.tv/free-bug.log

    I hope this helps?!

    I forgot to mention the following:

    • The mini PC is currently connected to a HP monitor (w/o sound) for installation purposes and will be moved to be connected to an LG TV once its Kodi instance works.
    • The videos are stored on a Synology NAS in the local network.
    • The Kodi database is located in a MariaDB there as well.
    • The Kodi instance on that FireTV Stick runs flawlessly and performs well with the same settings.
    Code
    2025-11-23 12:12:46.454 T:900     error <general>: SMBFile->Open: Unable to open file : 'smb://192.168.178.13/VIDEO/SPIELFILME/JAMES%20BOND/James%20Bond%20007%20-%20In%20t%c3%b6dlicher%20Mission%20(1981).mkv'
                                                   unix_err:'16' error : 'Invalid argument'
2025-11-23 12:12:46.454 T:900     error <general>: CFileCache::Open - <smb://192.168.178.13/VIDEO/SPIELFILME/JAMES BOND/James Bond 007 - In tödlicher Mission (1981).mkv> failed to open
2025-11-23 12:12:46.454 T:900     error <general>: InputStream: Error opening, smb://192.168.178.13/VIDEO/SPIELFILME/JAMES BOND/James Bond 007 - In tödlicher Mission (1981).mkv

    The first error looks like Kodi is configured to use the default HDMI device (#0) when the active/connected HDMI device is #2 so the alsa audio sink cannot be opened.

    The second error is related to SMB (invalid argument) so check that you are using a valid IP/path and credentials in sources.xml and the SMB protocol versions used by the Kodi SMB client are correct for the NAS.

    Thank you very much for looking into it, chewitt !

    Quote from chewitt

    The second error is related to SMB (invalid argument) so check that you are using a valid IP/path and credentials in sources.xml and the SMB protocol versions used by the Kodi SMB client are correct for the NAS.

    This one is already fixed. Due to another reinstallation of LibreELEC, I forgot to put in the credentials for the share once again. This one works (i.e. video files can be accessed) now so that it cannot be the issue.

    Quote from chewitt

    The first error looks like Kodi is configured to use the default HDMI device (#0) when the active/connected HDMI device is #2 so the alsa audio sink cannot be opened.

    How and where can I fix that? The mini PC provides 2 HDMI ports. I tried both but no difference in behavior.

    Thank you, Da Flex!

    As mentioned the mini PC is not connected to its final destination TV. Do I have to repeat this HDMI setup again once it is connected there?

    Quote

    Note: Your devices should all be turned on and you should have a screen and audio working. Otherwise the EDID information isn't provided properly and this How-To won't work.

    As I can read here in the wiki, audio has to work. As the device is currently connected to a standard monitor without speakers, I wonder if this may contribute to all the issues?

    Quote from mibane

    As mentioned the mini PC is not connected to its final destination TV. Do I have to repeat this HDMI setup again once it is connected there?

    "Preferred setup" means "final destination", so yes.

    Quote from mibane

    As I can read here in the wiki, audio has to work. As the device is currently connected to a standard monitor without speakers, I wonder if this may contribute to all the issues?

    If LE /Kodi can't find any audio output device, then I guess it's possible that issues like yours appear.

    Quote from mibane

    As I can read here in the wiki, audio has to work. As the device is currently connected to a standard monitor without speakers, I wonder if this may contribute to all the issues?

    Kodi appears to read some HDMI audio capabilities from the DRM driver layer, but the EDID data from the monitor presumably shows no speakers so Kodi ends up running in circles trying and failing to open an audio sink. This eventually fails but only after generating a ton of log noise. It will be more productive (and less log-noisy) to run tests with the TV. You must also run "getedid delete" as the previous inappropriate advice to run it will force the kernel to always see the monitor (with no speakers) attached instead of the TV .. thus guaranteeing bad results.