Which Version should i use?

milo · March 7, 2023 at 6:55 AM

Hello I have a

Intel NUC-Kit D54250WYK Mini-PC (Core i5-4250U)

which version of the libreeelec 11 I need to use?

**chewitt** · March 7, 2023 at 9:22 AM

The Generic (not Generic-Legacy) x86_64 image should run on that system AFAIK.

milo · March 7, 2023 at 9:31 AM

I have now lafacy installes....how can I change to generic?

**CvH** · March 7, 2023 at 9:48 AM

Quote from milo

how can I change to generic

I would stay at legacy for now, we have reports about even more recent NUCs and they are basically broken for the "normal" generic build.

You can "update" to the other image by just copy over the downloaded image to the update folder.

milo · March 9, 2023 at 5:19 PM

Quote from CvH

I would stay at legacy for now, we have reports about even more recent NUCs and they are basically broken for the "normal" generic build.
You can "update" to the other image by just copy over the downloaded image to the update folder.

Is there an issue open to follow when it's solved?

**chewitt** · March 10, 2023 at 4:23 AM

I think calling Generic "broken" because you can't use the Chrome browser add-on is a little over-dramatic. For the majority of users it works great. For a minority that need specific features currently tied to Xorg the GBM image is a regressive step; but they are the minority.

**CvH** · March 10, 2023 at 4:13 PM

Quote from chewitt

I think calling Generic "broken" because you can't use the Chrome browser add-on is a little over-dramatic

the "broken" is about the not properly working video playback for all kind of media types at LE while using GBM IF you have a effected system like an older Intel or AMD

milo · March 14, 2023 at 2:22 PM

I installed today generic not lafacy and there was just a black screen not possible to see anything......

**heitbaum** · March 14, 2023 at 3:12 PM

Hi milo - if Generic is not working and Generic-legacy is. Could you please share your logs from both Generic and Generic-legacy and we can take a look at them to see why Generic is not working on this PC.

milo · March 14, 2023 at 3:30 PM

Hey heitbaum

see here

generic:

http://ix.io/4qOg

generic legacy:

http://ix.io/4qOj

**heitbaum** · March 14, 2023 at 5:20 PM

Output looks “right for both now” - but it is using the onboard intel graphics.

im assuming the the intel graphics is connected to this pc.

Strange thing in the logs is that it shows on both as the hdmi not connected. (Search for kmsprint) but I can see SAMSUNG on the ALSA configuration

Generic

2023-03-14 16:52:43.356 T:1362 error <general>: libva error: /usr/lib/dri/iHD_drv_video.so init failed

2023-03-14 16:52:43.357 T:1362 info <general>: VAAPI::Close - closing decoder context

2023-03-14 16:52:43.357 T:1362 info <general>: CApplication::CreateGUI - using the gbm windowing system

2023-03-14 16:52:43.357 T:1362 info <general>: Checking resolution 16

2023-03-14 16:52:43.359 T:1362 info <general>: GL_VENDOR = Intel

2023-03-14 16:52:43.359 T:1362 info <general>: GL_RENDERER = Mesa Intel(R) HD Graphics 5000 (HSW GT3)

2023-03-14 16:52:43.359 T:1362 info <general>: GL_VERSION = OpenGL ES 3.2 Mesa 22.3.5

2023-03-14 16:52:43.359 T:1362 info <general>: GL_SHADING_LANGUAGE_VERSION = OpenGL ES GLSL ES 3.20

Generic-legacy

2023-03-14 16:58:48.072 T:1417 info <general>: GL_VENDOR = Intel

2023-03-14 16:58:48.072 T:1417 info <general>: GL_RENDERER = Mesa Intel(R) HD Graphics 5000 (HSW GT3)

2023-03-14 16:58:48.072 T:1417 info <general>: GL_VERSION = 4.6 (Compatibility Profile) Mesa 22.3.5

milo · March 14, 2023 at 5:22 PM

Quote from heitbaum

Output looks “right for both now” - but it is using the onboard intel graphics (not the nvidia).
im assuming the the intel graphics is not available to be connected to on this pc.
I believe steps #6 onwards in this post will disable the intel card.

Post

RE: Radeon RX Vega 56 stuck at boot logo

There is no i915.ko module to be blacklisted, the graphic drivers are part of the kernel.

Follow this post and add initcall_blacklist=i915_init.

mglae

November 4, 2019 at 3:50 PM

Generic
2023-03-14 16:52:43.356 T:1362 error <general>: libva error: /usr/lib/dri/iHD_drv_video.so init failed
2023-03-14 16:52:43.357 T:1362 info <general>: VAAPI::Close - closing decoder context
2023-03-14 16:52:43.357 T:1362 info <general>: CApplication::CreateGUI - using the gbm windowing system
2023-03-14 16:52:43.357 T:1362 info <general>: Checking resolution 16
2023-03-14 16:52:43.359 T:1362 info <general>: GL_VENDOR = Intel
2023-03-14 16:52:43.359 T:1362 info <general>: GL_RENDERER = Mesa Intel(R) HD Graphics 5000 (HSW GT3)
2023-03-14 16:52:43.359 T:1362 info <general>: GL_VERSION = OpenGL ES 3.2 Mesa 22.3.5
2023-03-14 16:52:43.359 T:1362 info <general>: GL_SHADING_LANGUAGE_VERSION = OpenGL ES GLSL ES 3.20
Generic-legacy
2023-03-14 16:58:48.072 T:1417 info <general>: GL_VENDOR = Intel
2023-03-14 16:58:48.072 T:1417 info <general>: GL_RENDERER = Mesa Intel(R) HD Graphics 5000 (HSW GT3)
2023-03-14 16:58:48.072 T:1417 info <general>: GL_VERSION = 4.6 (Compatibility Profile) Mesa 22.3.5

Display More

So what does it mean? Why it is disconnected? I have no Nvidia card in this pic only the standard Intel graphic.

**heitbaum** · March 14, 2023 at 5:44 PM

Quote from milo

So what does it mean? Why it is disconnected? I have no Nvidia card in this pic only the standard Intel graphic.

Sorry edited my response - 2 different support responses - and I was confusing myself.

This is my kmsprint.

nuc12:~ # kmsprint

Connector 0 (236) HDMI-A-1 (connected)

Encoder 0 (235) TMDS

Crtc 0 (80) 1920x1080@60.00 148.500 1920/88/44/148/+ 1080/4/5/36/+ 60 (60.00) P|D

Plane 1 (40) fb-id: 288 (crtcs: 0) 0,0 1920x1080 -> 0,0 1920x1080 (C8 RG16 XR24 XB24 AR24 AB24 XR30 XB30 AR30 AB30 XR4H XB4H AR4H AB4H YUYV YVYU UYVY VYUY NV12 P010 P012 P016 Y210 Y212 Y216 XYUV XV30 XV36 XV48)

FB 288 1920x1080 XR30

Connector 1 (246) HDMI-A-2 (disconnected)

Encoder 1 (245) TMDS

Connector 2 (250) DP-1 (disconnected)

Encoder 2 (249) TMDS

Connector 3 (260) DP-2 (disconnected)

Encoder 7 (259) TMDS

Connector 4 (269) DP-3 (disconnected)

Encoder 12 (268) TMDS

Connector 5 (278) DP-4 (disconnected)

Encoder 17 (277) TMDS

Where as Generic-legacy of your’s shows

========== kmsprint ==========

Connector 0 (77) HDMI-A-1 (disconnected)

Encoder 0 (76) TMDS

Crtc 0 (45) 1920x1080@60.00 148.500 1920/88/44/148/+ 1080/4/5/36/+ 60 (60.00)

Plane 0 (31) fb-id: 98 (crtcs: 0) 0,0 1920x1080 -> 0,0 1920x1080 (C8 RG16 XR24 XB24 XR30 XB30 XB4H)

FB 98 1920x1080 XR24

Connector 1 (85) DP-1 (disconnected)

Encoder 1 (84) TMDS

Connector 2 (92) HDMI-A-2 (disconnected)

Encoder 1 (84) TMDS

And your Generic shows nothing

milo · March 14, 2023 at 6:58 PM

Okay....

and what is now wrong? Is it a software issue or? heitbaum

**heitbaum** · March 16, 2023 at 10:24 AM

I’m not sure. I’ll drag out my nuc6 on the weekend and see what kmsprint shows. (It is skylake - so not the same but - worth a check.

**heitbaum** · April 13, 2023 at 12:46 PM

milo

I think I might have stumbled on why there are issues with older intel video cards (well I hope)

Can you please run these 2 commands and share the output with me.

systemctl status kodi

ldd /usr/lib/dri/iris_dri.so

milo · April 27, 2023 at 8:02 PM

heitbaum

Code

● kodi.service - Kodi Media Center
     Loaded: loaded (/usr/lib/systemd/system/kodi.service; disabled; prese     Active: active (running) since Thu 2023-04-27 20:40:08 CEST; 20min ag    Process: 1421 ExecStartPre=/usr/lib/kodi/kodi-config (code=exited, sta   Main PID: 1426 (kodi.sh)
      Tasks: 61 (limit: 8947)
     Memory: 558.3M
        CPU: 9min 51.613s
     CGroup: /system.slice/kodi.service
             ├─1426 /bin/sh /usr/lib/kodi/kodi.sh --standalone -fs
             └─1430 /usr/lib/kodi/kodi.bin --standalone -fs
Apr 27 20:40:08 htpc systemd[1]: Starting kodi.service...
Apr 27 20:40:08 htpc systemd[1]: Started kodi.service.
Apr 27 20:40:09 htpc kodi.sh[1430]: libva info: VA-API version 1.17.0
Apr 27 20:40:09 htpc kodi.sh[1430]: libva info: Trying to open /usr/lib/drApr 27 20:40:09 htpc kodi.sh[1430]: libva info: Found init function __vaDrApr 27 20:40:09 htpc kodi.sh[1430]: libva error: /usr/lib/dri/iHD_drv_videApr 27 20:40:09 htpc kodi.sh[1430]: libva info: va_openDriver() returns 1
Apr 27 20:40:09 htpc kodi.sh[1430]: Failed to open VDPAU backend libvdpa

Display More

Code

ldd /usr/lib/dri/iris_dri.so
        linux-vdso.so.1 => linux-vdso.so.1 (0x00007ffdfdbd9000)
        libglapi.so.0 => /usr/lib/libglapi.so.0 (0x00007feb05fb1000)
        libdrm.so.2 => /usr/lib/libdrm.so.2 (0x00007feb05f9c000)
        libLLVM-15.so => /usr/lib/libLLVM-15.so (0x00007feb02606000)
        libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007feb025db000)
        libz.so.1 => /usr/lib/libz.so.1 (0x00007feb025c2000)
        libdrm_radeon.so.1 => /usr/lib/libdrm_radeon.so.1 (0x00007feb025b5000)
        libelf.so.1 => /usr/lib/libelf.so.1 (0x00007feb0259d000)
        libdrm_amdgpu.so.1 => /usr/lib/libdrm_amdgpu.so.1 (0x00007feb02592000)
        libdrm_intel.so.1 => /usr/lib/libdrm_intel.so.1 (0x00007feb0256d000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007feb02353000)
        libm.so.6 => /usr/lib/libm.so.6 (0x00007feb02278000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007feb02258000)
        libc.so.6 => /usr/lib/libc.so.6 (0x00007feb02098000)
        /usr/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007feb0761d000)
        libpciaccess.so.0 => /usr/lib/libpciaccess.so.0 (0x00007feb0208c000)

Display More

**heitbaum** · April 28, 2023 at 4:32 PM

2 more commands please (as without the “| cat” the log isn’t showing the whole error)

ldd /usr/lib/dri/iHD_drv_video.so

systemctl status kodi | cat

Which Version should i use?

Intel NUC-Kit D54250WYK Mini-PC (Core i5-4250U)

RE: Radeon RX Vega 56 stuck at boot logo

Similar Threads

Vorke z6 plus dtb / wifi+bt in kodi / VFD : which dtb ?

Rpi 4, green artifacts with 10.0.2 - 10.0.4 version on ff-h264_v4l2m2m-drm_prime streams

is it possible to downgrade python version without use a old image libreelec ?