[gr4vity]

Hi,

Can someone post the following command output for RPI4?

Code: [Select]

glxinfo | grep OpenGL
If it looks like this then something is wrong

Code: [Select]

OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 9.0.1, 128 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.3.2
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.1 Mesa 19.3.2
OpenGL shading language version string: 1.40
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 19.3.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:

That is software rendering.

Best Regards.

[gr4vity]

Okay, i confirm that there is something wrong with the RPI4 MLD build.

Correct OpenGL command output should be as follows

Code: [Select]

pi@raspberrypi:~ $ glxinfo | grep OpenGL

OpenGL vendor string: Broadcom
OpenGL renderer string: V3D 4.2
OpenGL version string: 2.1 Mesa 21.3.6 - kisak-mesa PPA
OpenGL shading language version string: 1.20
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 21.3.6 - kisak-mesa PPA
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:
I used kisak mesa drivers on my RPi OS, Vulkan is working as well.

[clausmuus]

That's interesting.
Do you know, if the mesa drivers are used therefore?
And witch MLD software does need the OpenGL drivers?

[gr4vity]

Hi Claus.
Kodi version which i compiled uses OpenGL mesa drivers, that probably explains why Kodi doesn't work on MLD for RPI4.
vdr-plugin-xineliboutput uses OpenGL mesa drivers.

Best Regards.

[clausmuus]

We do not include the V3D driver, because we have no apps that need it.It is not necessary for video decoding.

[gr4vity]

But how can Kodi work without V3D driver?
Do you have any Kodi version that works on RPI4?

Best Regards.

[clausmuus]

I think not

[gr4vity]

I can build a new kernel and test Kodi 19 if you send me a working config which will not cause kernel panic.
Or you are satisfied with vdr-plugin-softhddevice-drm
 and don't want Kodi ... i don't understand 

I built kernel 5.15.11 in MLD dev container and Kodi is working as you see in screenshot but if i used the same kernel in MLD i'll get kernel panic.

[clausmuus]

You can use the kernel config, that is checked in into GIT. That's the config we build the MLD with.

[clausmuus]

I don't know, but you can see this if you checkout that file.

[gr4vity]

If it wasn't updated then it will cause kernel panic again.
It's so irritating to spend 2 hours building the kernel then get kernel panic.
Besides Kodi will not work if i used the same config.
If i tell me how to modify git config file to work with MLD I will modify it myself.

[clausmuus]

If you use the MLD dev environment, and take the MLD kernel package, the resulting kernel is exactly the same as the MLD images include.
In the kernel folder you can call "make menuconfig" to change the kernel configuration. After that a simple "make" will build the changed kernel package. This will not rebuild the whole kernel, but only the necessary part of it. This needs mostly only a view minutes. To rebuild the whole kernel you must do a "make clean" first.
To also build all depended packages, you can do a "make all_depends" in the kernel folder.

[gr4vity]

Hi Claus,

It may take minutes to build the kernel if you are using USB 3.0 stick or SSD HD but i'm using an old USB 2.0 stick.
It takes a long time.
I deleted the kernel folder then created a new one using make checkout
The config file was updated in 2020 for kernel 4.19.97
I will wait till you update MLD kernel and config file then i will buy a new USB 3.0 stick and try again.

Best Regards.

[clausmuus]

If you use the buster branch, with is the right for the MLD-5.5 then you will see that the last changes was made 09.2021
http://minidvblinux.de/git/?a=shortlog&p=kernel&h=refs/heads/buster

Also we do not compile on the RPI but on a x86'er with qemu ARM emulation in docker.

[clausmuus]

Hi,
we do not use cross compile. We use a ARM emulation. That's like a virtual machine. Cross compile would be much faster, but it is not possible for the MLD build system.
Only the kernel package Makefile contains some preparation for cross compile, but since we do not use it for years, I think ist's not ready to use now.