Text missing in v18 Leia
#16
Finally the log file should be here. Hope you can get to it and it is some help to you.
 https://paste.ubuntu.com/p/5zdZwV53K3/
Reply
#17
@Chevydean

You may have marked the log as Private as it is asking for username and password details to access it.
My Signature
Links to : Official:Forum rules (wiki) | Official:Forum rules/Banned add-ons (wiki) | Debug Log (wiki)
Links to : HOW-TO:Create Music Library (wiki) | HOW-TO:Create_Video_Library (wiki)  ||  Artwork (wiki) | Basic controls (wiki) | Import-export library (wiki) | Movie sets (wiki) | Movie universe (wiki) | NFO files (wiki) | Quick start guide (wiki)
Reply
#18
there, i fixed it
Do not PM or e-mail Team-Kodi members directly asking for support.
Always read the Forum rules, Kodi online-manual, FAQ, Help and Search the forum before posting.
Reply
#19
Quote:13:54:42.073 T:140161885870208  NOTICE: GL_RENDERER = Mesa DRI Intel® 945GM
13:54:42.073 T:140161885870208  NOTICE: GL_VERSION = 1.4 Mesa 18.0.0-rc5
13:54:42.073 T:140161885870208  NOTICE: GL_SHADING_LANGUAGE_VERSION = 1.20

We need version 1.5 or later.

Edit: Try 
Code:
MESA_GL_VERSION_OVERRIDE=2.1 kodi

Perhaps your driver has the extensions required but just does not expose them.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#20
Now this is way over my head.   It is not a big deal with me and this laptop as I just use to play around.  I thought it might be an issue that needed to be corrected.  I don't want to waste your time as you spent more than I expected with me. 

Thank for your responses and help.
Reply
#21
(2018-06-30, 21:59)Chevydean Wrote: Now this is way over my head.   It is not a big deal with me and this laptop as I just use to play around.  I thought it might be an issue that needed to be corrected.  I don't want to waste your time as you spent more than I expected with me. 

Thank for your responses and help.
 Open a terminal and type in:

MESA_GL_VERSION_OVERRIDE=2.1 kodi

and press return on the keyboard
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#22
Kodi 18 came up but still no text.
Reply
#23
Image
Reply
#24
Not related - fix your system, please. To get away the error: sudo apt-get install libvdpau-va-gl1

I think you should use OpenELEC 2.0 this will work out of the box I think.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#25
hello @fritsch ,
Quote: Could you please set MESA into debugging and find out what it does not like? There we can see if it for example announces 2.1 but is not capable of using it. You might also want to toy around with forcing a specific GL_VERSION (e.g. a lower version) to see if that's make a difference. Kodi development goes forward "Fixed Pipelines" are something of the past. They require huge syncs with CPU that are expensive and not good in performance. Therefore this codepath will die for a very good reason :-)
if you give me some guidance on howto set MESA into debugging state, i'd be up for it. never done that before.
here is what i tried so far:

i updated my le pc to Milhouse x86_x64 LE build #0630 from today/yesterday.
the system updated fine and rebooted.

kodi showed up with no fonts.
so i went in with ssh
stopped the kodi-service:
Code:
systemctl stop kodi

i also have:
Quote:14:26:41.109 T:139994140145792   ERROR: failed to create EGL context
14:26:41.115 T:139994140145792  NOTICE: Using visual 0x20
14:26:41.135 T:139994140145792  NOTICE: VDPAU::CreateContext - creating decoder context
14:26:41.136 T:139994140145792  NOTICE: vdp_device = 0x69572068 vdp_st = 0x01
14:26:41.136 T:139994140145792   ERROR: (VDPAU) unable to init VDPAU - vdp_st = 0x1.  Falling back.
14:26:41.137 T:139994140145792  NOTICE: GL_VENDOR = Intel Open Source Technology Center
14:26:41.137 T:139994140145792  NOTICE: GL_RENDERER = Mesa DRI Intel® 945G
14:26:41.137 T:139994140145792  NOTICE: GL_VERSION = 1.4 Mesa 18.1.1
14:26:41.137 T:139994140145792  NOTICE: GL_SHADING_LANGUAGE_VERSION = 1.20
14:26:41.137 T:139994140145792  NOTICE: GL_EXTENSIONS = GL_3DFX_texture_compression_FXT1 GL_AMD_shader_trinary_minmax GL_ANGLE_texture_compression$
14:26:41.160 T:139994140145792   ERROR: CYUVShaderGLSL::CYUVShaderGLSL - failed to open file gl_shader_frag_texture_lim.glsl
14:26:41.161 T:139994140145792  NOTICE: GL: No pixel shader, fixed pipeline in use
in my logs.

so i tried what you mentioned before.

first:
Code:
LIBGL_ALWAYS_SOFTWARE=yes /usr/lib/kodi/kodi.bin

brought:
Quote:LibreELEC:~/.kodi/temp # LIBGL_ALWAYS_SOFTWARE=yes /usr/lib/kodi/kodi.bin
libEGL warning: DRI2: failed to open swrast (search paths /usr/lib/dri)
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
Segmentation fault
kodi does not start.

when i only set the var and start kodi right after :
Quote:LibreELEC:~/.kodi/temp # LIBGL_ALWAYS_SOFTWARE=yes
LibreELEC:~/.kodi/temp # /usr/lib/kodi/kodi.bin
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
kodi starts up like before but still no fonts...

then i tried:
Quote:LibreELEC:~/.kodi/temp # MESA_GL_VERSION_OVERRIDE=2.1 /usr/lib/kodi/kodi.bin
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i915_drv_video.so
libva info: va_openDriver() returns -1
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
kodi starts but still no fonts.

Image


GL_VERSION successfully changed though. Here is the log after the process from above:
Quote:14:43:30.232 T:140506528278656 WARNING: Failed to get an OpenGL context supporting core profile 3.2,                               using le$
14:43:30.267 T:140506528278656  NOTICE: Using visual 0x20
14:43:30.272 T:140506528278656  NOTICE: VDPAU::CreateContext - creating decoder context
14:43:30.272 T:140506528278656  NOTICE: vdp_device = 0x69572068 vdp_st = 0x01
14:43:30.273 T:140506528278656   ERROR: (VDPAU) unable to init VDPAU - vdp_st = 0x1.  Falling back.
14:43:30.273 T:140506528278656  NOTICE: GL_VENDOR = Intel Open Source Technology Center
14:43:30.273 T:140506528278656  NOTICE: GL_RENDERER = Mesa DRI Intel® 945G
14:43:30.273 T:140506528278656  NOTICE: GL_VERSION = 2.1 Mesa 18.1.1
14:43:30.273 T:140506528278656  NOTICE: GL_SHADING_LANGUAGE_VERSION = 1.20
14:43:30.273 T:140506528278656  NOTICE: GL_EXTENSIONS = GL_3DFX_texture_compression_FXT1 GL_AMD_shader_trinary_minmax GL_ANGLE_texture_comp$
14:43:30.291 T:140506528278656   ERROR: CYUVShaderGLSL::CYUVShaderGLSL - failed to open file gl_shader_frag_texture_lim.glsl
14:43:30.292 T:140506528278656  NOTICE: GL: No pixel shader, fixed pipeline in use


forcing a specific GL_VERSION (e.g. a lower version) , does not make a difference.
also tried these:
Quote:LibreELEC:~ # MESA_GL_VERSION_OVERRIDE=1.3 /usr/lib/kodi/kodi.bin
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
^CExiting application
LibreELEC:~ # MESA_GL_VERSION_OVERRIDE=1.2 /usr/lib/kodi/kodi.bin
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
^CExiting application
LibreELEC:~ # MESA_GL_VERSION_OVERRIDE=1.1 /usr/lib/kodi/kodi.bin
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
^CExiting application
LibreELEC:~ # MESA_GL_VERSION_OVERRIDE=1.0 /usr/lib/kodi/kodi.bin
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
^CExiting application

no success, kodi starts fine but the ui looks unchanged, no fonts, no text like on the image above.
Quote:Kodi development goes forward "Fixed Pipelines" are something of the past. They require huge syncs with CPU that are expensive and not good in performance. Therefore this codepath will die for a very good reason :-)

That's great and totally fine with me. I do not want to be in the way here. Evolution goes forward.
I'm just trying to find a way so i can still keep my old hardware, that still does the job. I'm trying to avoid producing more trash as long as the hardware is not broken.

It would be great if there could be something like a check, that checks the gpu and if it's not supported any longer, post a readable message (remember, fonts are invicible)
or changes the kodi startup service in libreelec to have the necessary startup variables.
Reply
#26
Suggested way: Use old hardware with old software -> 17.6 I don't know of anything else to get it running for you.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#27
Is inputstream.adaptive working with 17.6? I've been using leia for almost a year, and i use mainly youtube and netflix.
Leia works great till millhouse build #1004 2017. I'm downgrading back to that version for now, so no worries.
I was hoping to to get to the latest version of inputstream.adaptive because the snapshot of #1004 is fairly old but yeah, i can't have everything..

anyways still thx for help @fritsch
Reply
#28
(2018-07-02, 01:31)winux Wrote: Is inputstream.adaptive working with 17.6?

nope
Reply
#29
For virtual machines on VMware use this to display text and fonts:

https://kb.vmware.com/s/article/1003746
 
  1. In VMware Player, open the virtual machine's .vmx file using a text editor.
    For more information on editing, see Editing the .vmx file of a VMware Workstation and VMware Player Virtual machine(2057902)
    Locate the entry virtualHW.version = "8".
  2. Change the above entry to:
    virtualHW.version = "12"
  3. Save and close the .vmx file.
  4. Note: Changes made to the .vmx file do not take effect until the next time VMware Workstation or VMware Player is opened.
I changed hardware version to "14" because I use the vmware player 14.
Reply
#30
Please try again with tomorrow's nightly. Fernet has spotted a GL2.x compatibiity issue.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply

Logout Mark Read Team Forum Stats Members Help
Text missing in v18 Leia0