Pandaboard ES: /usr/lib/arm-linux-gnueabihf/dri/omap_dri.so missing -> Only software rendering

[Till Kamppeter]

I have installed Raring on a Pandaboard ES with 8GB SD card and 1920x1080 HDMI monitor. The desktop shows up in the correct resolution and can be used. Problem is that the desktop is slow and videos play as slide shows causing a high processor load. So I checked whether there is any problem with hardware acceleration for the graphics.

In /var/log/Xorg.0.log I found the following:

[ 80877.168] (EE) AIGLX error: dlopen of /usr/lib/arm-linux-gnueabihf/dri/omap_dri.so failed (/usr/lib/arm-linux-gnueabihf/dri/omap_dri.so: cannot open shared object file: No such file or directory)
[ 80877.168] (EE) AIGLX: reverting to software rendering
[ 80877.168] (II) AIGLX: Screen 0 is not DRI capable
[ 80877.220] (II) AIGLX: Loaded and initialized swrast

So it seems that hardware acceleration fails due to a missing file. I looked into the source of the pvr-omap4 and searched also the internet for the omap_dri.so fiule and did not find it, nor a method to create it.

Can someone add this file to the package and perhaps make it also available to me as a workaround for the time being?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[psamuel (persaudsamuel)]

Cuantos monitores tienes conectado???

[Till Kamppeter (till-kamppeter)]

I have only one monitor, connected to the HDMI output of the Pandaboard.

[Olivier Naudan (o-naudan)]

TI supports the Ubuntu distributions from Maverick to Precise, excluding Quantal and Raring unfortunately.
The Raring kernel (version 3.5.0-216-omap4 #23) is not compatible with any known PVR user-space library.
By the way, omap_dri.so library is not provided by TI and not needed.

For a full OMAP hardware acceleration, the latest distribution is Ubuntu Precise + TI release PPA e.g. kernel version 3.4.0-1489.22 and pvr-omap4 version 1.9.0.7.1.5-2.

More details on http://omappedia.org/wiki/Ubuntu_Pre-built_Binaries_Guide

[Till Kamppeter (till-kamppeter)]

Does this mean that this hardware is considered EOL by TI? Should we not use another ARM platform as ARM desktop test sample then?

[Tom Gall (tom-gall)]

I disagree. omap_dri.so is needed. I just tripped across this on raring, while trying to run some OpenGL / OpenGL ES2 code.

(the GL messages here is due to libwaffle loading both GLES and GL at the same time.. yes it's correct, this all works on intel and it should work on ARM without warning or error)
tgall@neso:~/bld/piglit$ export LIBGL_DEBUG="verbose"
tgall@neso:~/bld/piglit$ bin/minmax_gles2
libGL: OpenDriver: trying /usr/lib/arm-linux-gnueabihf/dri/tls/omap_dri.so
libGL: OpenDriver: trying /usr/lib/arm-linux-gnueabihf/dri/omap_dri.so
libGL error: dlopen /usr/lib/arm-linux-gnueabihf/dri/omap_dri.so failed (/usr/lib/arm-linux-gnueabihf/dri/omap_dri.so: cannot open shared object file: No such file or directory)
libGL: OpenDriver: trying ${ORIGIN}/dri/tls/omap_dri.so
libGL: OpenDriver: trying ${ORIGIN}/dri/omap_dri.so
libGL error: dlopen ${ORIGIN}/dri/omap_dri.so failed (${ORIGIN}/dri/omap_dri.so: cannot open shared object file: No such file or directory)
libGL: OpenDriver: trying /usr/lib/dri/tls/omap_dri.so
libGL: OpenDriver: trying /usr/lib/dri/omap_dri.so
libGL error: dlopen /usr/lib/dri/omap_dri.so failed (/usr/lib/dri/omap_dri.so: cannot open shared object file: No such file or directory)
libGL error: unable to load driver: omap_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: omap

Even switching to mesa privded EGL & libGLESv2 instead of the TI binaries yields the following:

tgall@neso:~/bld/piglit$ bin/minmax_gles2
libEGL warning: failed to create a pipe screen for omap
libEGL warning: DRI2: failed to open omap (search paths /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)

[Tom Gall (tom-gall)]

Actually I misread Olivier is correct omap_dri.so would normally be needed by OpenGL but it's not something that TI ever provided. Still X ought to know better and not complain.