Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
OpenGL
#11
Sure, that's exactly what I did - I launched all above from xterm under running X session.
Reply
#12
try to add the X11 mali location to the the command: 
Code:
LD_LIBRARY_PATH=/usr/lib/GLSHIM:/usr/lib

edit: can you describe your steps to install? I can try to reproduce the error
Reply
#13
(06-12-2018, 02:43 PM)alexkidd Wrote: try to add the X11 mali location to the the command: 
Code:
LD_LIBRARY_PATH=/usr/lib/GLSHIM:/usr/lib

edit: can you describe your steps to install? I can try to reproduce the error

I didn't install anything since mali is already incorporated, fbturbo and glshim installed, just checked (according to howto in tread - modprobe etc) that everything is in place - and it seems it is. Just added device permissions which weren't there (/etc/udev/rules.d/).


Suspicious things I noticed:

Code:
cat /var/log/Xorg.0.log | grep \(EE\)
...
[ 46696.815] (EE) AIGLX error: dlopen of /usr/lib/arm-linux-gnueabihf/dri/lima_dri.so failed (/usr/lib/arm-linux-gnueabihf/dri/lima_dri.so: cannot open shared object file: No such file or directory)
...


and


Code:
cat /var/log/Xorg.0.log | grep FBTURBO
...
[ 46696.782] (II) FBTURBO(0): [DRI2] Setup complete
[ 46696.782] (II) FBTURBO(0): [DRI2]   DRI driver: lima
[ 46696.782] (II) FBTURBO(0): using DRI2 integration for Mali GPU (UMP buffers)
[ 46696.782] (II) FBTURBO(0): Mali binary drivers can only accelerate EGL/GLES
[ 46696.782] (II) FBTURBO(0): so AIGLX/GLX is expected to fail or fallback to software
...



Seems that it's related to sans-ltd post "that libglshim is missing alternative information."
Will try to cehck today and get back.
Reply
#14
[Solved]
Seems that 
LD_LIBRARY_PATH=/usr/lib/GLSHIM:/usr/lib
worked like a charm - even on fresh system, no additional steps needed.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)