Olimex Support Forum

OLinuXino Android / Linux boards and System On Modules => A10 => Topic started by: kruno on February 19, 2014, 07:00:38 PM

Title: Lime - es2gears libEGL warning: DRI2: failed to open lima
Post by: kruno on February 19, 2014, 07:00:38 PM
using the latest sd card image from:
http://olimex.wordpress.com/2014/01/15/building-debian-linux-bootable-sd-card-with-hardware-accelerated-video-decoding-and-kernel-3-4-for-a10-olinuxino-lime/

root@a10Lime:~# es2gears
libEGL warning: DRI2: failed to open lima (search paths /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)
EGL_VERSION = 1.4 (DRI2)
vertex shader info:
fragment shader info:
info:
78 frames in 5.0 seconds = 15.501 FPS

Any help is appreciated.
Title: Re: Lime - es2gears libEGL warning: DRI2: failed to open lima
Post by: fw72 on March 10, 2014, 12:24:18 PM
Did you find out how to solve this problem? I'm stuck at the same point...  :-\
Title: Re: Lime - es2gears libEGL warning: DRI2: failed to open lima
Post by: Metanurb on June 03, 2014, 03:20:25 PM
I have the same problem here  :(
Title: [SOLVED] Re: Lime - es2gears libEGL warning: DRI2: failed to open lima
Post by: Metanurb on June 03, 2014, 04:25:25 PM
I got it running with the sunxi-mali drivers.

git clone https://github.com/linux-sunxi/sunxi-mali.git
cd sunxi-mali
git submodule init
git submodule update
sudo make install

# move the lima drivers out of the search path:
sudo mkdir /usr/lib/arm-linux-gnueabihf/bak
sudo mv /usr/lib/arm-linux-gnueabihf/libGLES* /usr/lib/arm-linux-gnueabihf/bak
sudo mv /usr/lib/arm-linux-gnueabihf/libEGL* /usr/lib/arm-linux-gnueabihf/bak


gl2gears then runs with 50 FPS
And after I resized the window suddenly with 60, also sometimes the cpu usage is at ~5% then it jumps to 50%.


edit:
after a reboot it's now running with ~150 FPS!?
Title: Re: Lime - es2gears libEGL warning: DRI2: failed to open lima
Post by: onefang on July 27, 2014, 11:45:21 PM
I'm having the same problem on an A20 board.  Using the sunxi-mali drivers didn't help.  Is there a particular revision or branch you used?  Any other clues?